> Is @Property so hard or awful?
No, it isn't. But for me these kind of objects have temporary character. I
really don't like them to pollute my page classes.
Maybe its just me, but if I need a property just to iterate over a list it
feels like it could be optimized.... tapestry is reducing needed code
whereever possible. In this particular case I think its hard to understand why
it breaks with this rule. Especially because var: is available and iterates
over the object fine: callit .toString() method if displayed.
But accessing the properties of an object that is there fails... its just
something I would not have expected.
Piero
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
