This is a side-effect of Tapestry's static structure approach. A component X embedded in the template of component Y is instantiated as an object attached to object Y. This instantiation happens once, at page load time.
For X to be recursive (to contain an X), we would need to instantiate X and as part of that, instantiation another X to place inside the first X. To create the second X we need to instantiate a third X ... you can see where this goes. In theory, we could construct the component heirarchy for the page on an as-needed basis, but that might cause its own problems (including performance issues) and a while different set of lazy abstractions! On Mon, Apr 5, 2010 at 2:07 PM, Pierce T. Wetter III <pie...@paceap.com> wrote: > > Just out of curiosity, why no recursive components? I re-implemented my > navigation menu using a solution I found on Google, but it would have been a > lot simpler if the menu items had been recursive instead having to use > delegate stuff that felt very much like voodoo... > > Pierce > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
