Here are two examples that handle clientids in a loop: - Simple, around AJAX EventLinks: http://jumpstart.doublenegative.com.au/jumpstart/examples/ajax/eventlinksinaloop - More complex, around AJAX Forms: http://jumpstart.doublenegative.com.au/jumpstart/examples/ajax/formsinaloop
HTH, Geoff > On 28 May 2015, at 4:33 am, Thiago H de Paula Figueiredo <thiag...@gmail.com> > wrote: > > On Wed, 27 May 2015 11:12:04 -0300, Poggenpohl, Daniel > <daniel.poggenp...@isst.fraunhofer.de> wrote: > >> that could be a method for knowing which zone to update, because I know the >> db id of the represented object. I'll check this out. > > Yep, that's a good idea. If you really to use the HTML ids of HTML elements > generated by Tapestry, it's usually a good idea to provide them explicitly, > because otherwise they may be generated randomly, such as when inside a loop. > > -- > 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 > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
