On Thu, 01 Mar 2012 10:49:34 -0300, Tonne indie <indieto...@gmail.com>
wrote:
- Using the Grid component inside a Loop leads to erroneous sorting
behavior.
Example: 1 Grid, used inside a loop leads to 3 rendered grids on the
client.
Changing the sort of one of them, sorts all grids since the sorting
links don't have a clue which one to sort.
Even granted that we have a GridModel for each iterable (i have to
admit
i haven't tested it yet) won't change that issue, does it?!
I don't think so. Remember that when you have a component (for example,
Grid) instance inside a loop you have just one Grid instance being
rendered n times. This component persists its current page and sort column
info in @Persist fields. Both facts, together, explain what you're seeing.
Am I getting something wrong or is the tapestry grid component simply not
intended to be used inside a loop?
I guess it can be reworked to work inside loops.
--
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
