Renzo Tomaselli schrieb:
Hi Tobias, I know nothing about Seam, but I had a table refresh
problem in the past, when my user was allowed to change colum
layout/composition on the fly.
In order to refresh the table children, I had to call:
((UIXTable)table).resetStampState();
where - of course - I got the actual component through the binding
attribute.
Model contents - e.g. rows - can change happily from request to
request, provided that you feed the table value attribute through a
properly up-to-date own CollectionModel. Btw, I assume using
request-scoped beans here.
Hi Renzo!
Thanks for your reply!
The binding already happens in the request scope. I have a List of
entitys as value to the table, which contents can change, but this way,
I dont get the model changed.
So I need to give a CollectionModel instead ? How do I setup my own
collectionModel? Can you give me any hints or links to that? Im pretty
new to Trinidad, Seam and even to Java :-)
Thanks,
Tobias
