I think there might be another problem at play here because when you refresh your outer zone, your form and zone are both re-rendered. I have numerous situations like this in my app which work fine. It more sounds like the scripts passed along in the response JSON from your outerZone are not handled correctly and thus not initializing the zone properly. This can be due to some other javascript failing.
What is the exact behavior you are getting and what errors are occurring? Cheers, Joost On Tue, Apr 28, 2009 at 3:38 AM, Hugo Palma <hugo.pa...@xpand-it.com> wrote: > I have a template that looks something like this: > > <div t:type="zone" t:id="outerZone"> > > <form t:type="form" t:zone="innerZone"> > </form> > > <div t:type="zone" t:id="innerZone"> > </div> > </div> > > The problem is figuring out the id of the innerZone in order to pass > it to the form. Because the innerZone is itself inside a zone once the > outerZone gets updated a new id is generated to the innerZone making > the id i passed to the form an invalid one. I also tried something > like: > > <form t:type="form" t:zone="prop:innerZone.clientId"> > > but it doesn't work either. > Any ideas on how i could make this work ? > Thanks. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
