Comments are welcome. -- Renzo
Hi, I'm using tr:table successfully since long time. Now I wonder about
changing row composition (e.g. adding/removing rows) at runtime from
javascript.
In case there are input fields, I expect a mismatch while restoring view
since expected rows do not match submitted ones.
The question is: can I manage this situation from within the collection
model - which should expect a row index higher than previously rendered
- or does UIXTable component turn everything into a mess ?
In theory I might forget about any previous row set and accept the
current set as submitted, but I suspect that unchanged input fields are
not sent to the involved beans.
Or I might forget about using tr:table and use h:panelGrid, managing
rows by hand. But I still wonder about how restore view will manage
input fields not found in the saved view.
