Thank you guys, the solution works fine without much changes to the component. Only had generate clientID's dynamically
On Thu, Feb 19, 2015 at 8:34 PM, Thiago H de Paula Figueiredo < thiag...@gmail.com> wrote: > On Thu, 19 Feb 2015 17:17:01 -0200, Sumanth <roasteddra...@gmail.com> > wrote: > > Well I can certainly try the way you have suggested, but wouldn't it be >> better tif tapestry can handle it? Because, I know that we need to >> specify client id for the zone when we use it, so generally a static client >> id will be given to these component eg : <t:zone t:id="Hello" id="hello" > >> but if >> the zone is inside another component then shouldn't tapestry generate >> unique id for this zone like componentid_zoneid? >> > > It wouldn't work for components inside a loop: the same component instance > is rendered as many times as there are objects to iterate. > > > -- > Thiago H. de Paula Figueiredo > Tapestry, Java and Hibernate consultant and developer > http://machina.com.br > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
