Nope; being able to modify the component hierarchy is forbidden in any and all versions of Tapestry. You very rarely need to and when you do, there are other techniques besides creating components dynamically.
Tapestrys pooling approach to scalability and state persistence (and a number of other things) is predicated on all pages being equivalent and storing no user-specific state. Modifying a page's structure for a particular user would be considered user-specific state. On 6/1/07, Andrea Chiumenti <[EMAIL PROTECTED]> wrote:
So if I understand there is no way to dynamically inject components into a page. Is this possible in Tap 5 ? On 6/1/07, Jesse Kuhnert <[EMAIL PROTECTED]> wrote: > It's done that way to prevent people from trying to modify the component > structure. There's no telling what will happen if you try to modify it > somehow. Almost assuredly it will break something. > > On 6/1/07, Andrea Chiumenti <[EMAIL PROTECTED]> wrote: > > > > Can anybody tell me why getComponents is an immutable Map and what > > shold happen is this map is overridden with a mutable one ? > > > > Thx, > > kiuma > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Jesse Kuhnert > Tapestry/Dojo team member/developer > > Open source based consulting work centered around > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com
