Tapestry follows the definition of JavaBeans properties, set by Sun, and in fact, uses the standard Introspector object to identify properties. A setter method must return void.
On Wed, Apr 21, 2010 at 8:30 AM, paha <ch_pa...@yahoo.com> wrote: > > Is there any reason to ignore setters, returning an object itself in > beaneditor & co? I used to write classes, which can be created with chain of > setter calls e.g. > someObject.setSomeValue(value).setAnotherValue(value) > > the problem is, tapestry considers such "properties" read-only. Is it > possible to accept such setters as valid ones in future releases? > > > -- > View this message in context: > http://old.nabble.com/T5.1-Setters-returning-value-tp28288048p28288048.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
