Think about it this way, once your page has rendered the trees, this list is gone unless it stored it in the html or in the session (bad).
Take a look at the event link that tapestry generates to expand a tree node, I'm betting that it does not contain enough information to determine the loop value. I think the solution involves the tree component generating an eventlink such that it has enough information to determine it's model in the ajax event. -- View this message in context: http://tapestry.1045711.n5.nabble.com/T5-3-s-Tree-in-a-Loop-tp5713347p5713358.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
