On Fri, 03 Dec 2010 09:54:54 -0200, Christian Koller
<christian.kol...@net-m.ch> wrote:
Any ideas how to solve this?
Tapestry components ids are static, period. HTML ids are dynamic.
If I use a literal as the id, then it works, but then all the generated
timeSlot components within the loop will have the same id.
If I use afterwards the persist annotation within the timeSlot component
all the generated timeSlots share this session value because the id is
the same.
The explanation is not correct. You have a single TimeSlot component
instance in your template which is rendered n times. Instead of relying in
@Persist inside the component, pass the info as a parameter.
--
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
