I have been thinking about this problem a little further and I don't think that adding a static id on the zone is going to work. The problem that I have is that this Zone lives inside a component. This component could be used multiple times and that would break the uniqueness of the id of the zone.
Does tapestry have the concept of scope? This seems like it would solve the potential problem of partial updates and changing ids. If the Zone is changing then the changes within that zone's scope should be able to handle the updated references. Does that make sense? Is something like this possible with the current code-base (T5.0.18)? -- View this message in context: http://www.nabble.com/-T5--Nested-Zones-tp21060828p21073771.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
