Thanks for your reply Thiago. Unfortunately, correct me if I'm wrong, the ComponentModel (as of version 5.1.0.5, that I'm using) only returns the components that were annotated with @InjectComponent or @Component in the containing page or parent component, that makes it of little use :(
I'm sure that info must be hiding in other place in the code... Greetings! Thiago H. de Paula Figueiredo wrote: > > On Thu, 08 Jul 2010 00:04:55 -0300, Juan Isern <[email protected]> > 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: [email protected] > For additional commands, e-mail: [email protected] > > > -- View this message in context: http://old.nabble.com/Page-component-tree-model-tp29090350p29121830.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
