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.
-- Renzo
Tobias Kilian wrote:
Any ideas to this? Pleeease...
Hi NG!
Im using a trinidad tr:table inside my seam-application.
The Problem:
It seams, that the table model is only generated once, at the first
attempt to render the table and doesnt change afterwards. Is this
correct? I suppose it could be desired behavior, but that leads me into
trouble..
The Situation:
I have a selectionList on the left side and a tr:table at the right. I
want the tables underlying list to be one of left side's members. So the
selectItems value is #{tableInstance.selectedMaster}, while the tables
value attribute is #{tableInstance.selectedMaster.getSlaves()}" the
selectManyList has partialSubmit=true and is a trigger for the table, so
that works. I can select a master on the left and see all its slaves in
the table. However the tables model is not changing. Thats why the
table's getSelectedRowKeys() gives me wrong indices.
Question:
is their a way to tell the tr:table to refresh its underlying model? How
else could i accomplish this?
Many thanks,
Tobias Kilian
