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
