Hey Manfred, On 6/21/05, Manfred Geiler <[EMAIL PROTECTED]> wrote: > What do you mean by "preserveDataModel is too aggressive"?
I agreed with Kalle's statement that storing the whole data model would be too much. Now it is clear that only the visible information is preserved. :-) However, it does look like the preserveDataModel approach might be further optimized by storing just the primary key for each row, rather than the entire row data. This might require a sub-interface of DataModel to add get/setRowKey, to support automatic wrapping as a StateHolder. Btw, the "preserveDataModel" attribute is not required if the end user specifies the model via an EL binding, right? In that case, the default saveAttachedState processing for all bindings should take effect. Kind Regards, John Fallows.
