Marco, UIData components (like t:dataList/h:dataTable/t:dataTable/t:newspaperTable/t:columns) use a Flyweight pattern.
http://www.exciton.cs.rice.edu/JavaResources/DesignPatterns/FlyweightPattern.htm What this means is that one component is used multiple times to encode/render and decode/parse your inputs. Each instance of this is row-state data. dataList seems to do the least well with handling the handling of all of these row-state data pieces. Probably dataList should be dumped, and replaced with a custom t:dataTable renderer. I'd recommend trying to switch over to using t:dataTable. Once you do that, you can try using preserveRowStates/preserveDataModel/previousRowDataVar to make your situation work. If you can't make it render like you want, then create your own renderer for t:dataTable, and submit it as a replacement for dataList :) It should just be a matter of deleting all of the generated table tags for the simple layout. On 1/17/06, Marco <[EMAIL PROTECTED]> wrote: > Any suggestions please... > > All i need to do is to update the model from the generated UI components > from the dataList. > > Thanks a lot >
