On Wed, 07 Mar 2012 13:41:02 -0300, Jochen Frey <joc...@jochenfrey.com>
wrote:
Thanks guys!
Hi!
I have a lot of components that are re-used either in loops, or just
embedded in multiple components (often in the same page).
The pattern that Paul and Thiago are suggesting works fine if that
component occurs a single time on a page. However, if you use it
multiple times, the client side zoneId (as well as the Tapestry JS
initializers) are not unique any more, which causes the same zone to be
updated all the time, no matter which EventLink got the click.
Again, provide the id yourself, in this case dinamically
(id="${generatedId}"). When you don't provide the id yourself, Tapestry
components generate a random one when it finds the original id, based in
t:id, is already taken.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
