On Thu, 08 Jul 2010 00:04:55 -0300, Juan Isern <juanis...@gmail.com> wrote:
I think that I'm needing something more powerful than that, because I'd
need to process the complete component tree in one single step in a
single place in the code.
That's exactly the component model that Tapestry uses internally. If you
need to process it, you need to do it yourself. It's not hard: just create
a recursive method using the ComponentModel methods to get the information
you need.
--
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
