State problems: contrib:Table in loop

[Alexei Orishchenko <le...@gmail.com>]

The page contains loop that renders contrib:Table on each iteration (list of
users, orders for each user).
I have problems with pagers of these tables. For example, I go to the 2nd
page in the table for 2nd user but the page isn't changed. Seems, the
Tapestry stores 1 table state for these tables.

Any thoughts how to store separate state for each table / fix pager problem?
-- 
View this message in context: http://www.nabble.com/State-problems%3A-contrib%3ATable-in-loop-tf3929526.html#a11144951
Sent from the Tapestry - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org

Re: State problems: contrib:Table in loop

[Steve Shucker <ss...@vmsinfo.com>]

You need to specify the "tableSessionStoreManager" property.

If the loop iterates over something that's stored in the session anyway, 
you can add a Serializable field to that object (or wrap it in another 
object containing this field) and implement the two methods of 
ITableSessionStoreManager to load and save the state there.  It's not 
always an appropriate solution, but it is the easiest.

-Steve

Alexei Orishchenko wrote:
> The page contains loop that renders contrib:Table on each iteration (list of
> users, orders for each user).
> I have problems with pagers of these tables. For example, I go to the 2nd
> page in the table for 2nd user but the page isn't changed. Seems, the
> Tapestry stores 1 table state for these tables.
>
> Any thoughts how to store separate state for each table / fix pager problem?
>   

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org