On Wed, 03 Sep 2014 16:31:50 -0300, John <j...@quivinco.com> wrote:
doesn't the t:id need to be unqiue as well, or does the framework handle this?
t:id must be unique inside the template, but that's the Tapestry server-side component id, not the HTML client-side id. So t:id and id are completely different things, even if id is defined based on t:id if you don't bind the id parameter. Lance's suggestion is the way to go.
-- 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
