On Fri, 13 May 2011 12:52:36 -0300, Clément Uster
<clement.us...@gmail.com> wrote:
Ok, I understand.
Interesting approach, thanks.
It's one of what I consider one of the hidden gems of Tapestry: its
server-side DOM.
This may cause a lot of pain !
I'm not following you . . .
So, can I conclude that the use of @Property wouldn't be recommended
within components ? Because (even with mixins) you may want to have
access to some properties of the component...
I'd say that you shouldn't use @Property when you think it's interesting
to provide access to other classes.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
