Well, I thought I would post a note about what I did to actually get this to work. I think that this still seems like a work around and that tapestry should make the dealings of its generated internal ids more transparent. Also, I didn't come up with this on my own, so thank Fanf for pointing me in this direction.
The first thing I did was in my component I injected the RenderSupport object. This object has a method allocateClientId that I called on the zone during the setup render. This method returns the client id of the zone which I put into a persistent property on the component. In the template, I gave the zone both a t:id="zoneName" and an id="prop:zoneId". All of the components that needed to reference the zone used zone="prop:zoneId". These seems to work for the most part, but I don't think it is very clear on how to do it. Hope this helps somone else that might need it. -- View this message in context: http://www.nabble.com/-T5--Nested-Zones-tp21060828p21115259.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
