Yesterday I opened a feature request for recursive components, https://issues.apache.org/jira/browse/TAP5-739, and had it closed for the reasons described there (basically, 'not possible').
First of all, thanks Thiago for taking the time to describe the issue and the pointer to a technique as a workaround. Here's my question about the suggested workaround (which I'll call the 'use MarkupWriter' technique). I have two reasons why I want to avoid a markupwriter: 1) We have many components already designed that fit in a tree structure (10 now, but easily 200 later). We would like to have the template in a tml file, so that a UI designer can contribute without being a Java expert on our numerous templates. 2) More importantly, components allow us to associate behavior (ajax, forms, actionlinks, etc) with our components in a very clean, modular way. With a MarkupWriter technique, I believe we lose both. Does anyone have any suggestions as to how we can pull off recursion of components (or something like it), while achieving #1 and #2? Thanks for any help, Seth -- View this message in context: http://n2.nabble.com/Stuck-on-implementing-recursion-%28or-something-like-it%29-cleanly-tp3032700p3032700.html Sent from the Tapestry Users 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
