OK I am a little late to this thread as I have two weeks of emails (for work and open source) to catch up on. Please be patient with me if this has already been mentioned ...
Just wanted to make sure that everyone was aware that you can use forceId and forceIdIndex together to get ids like foo[0], foo[1], foo[2], etc. That would seem to handle the case of using a component inside a datatable (at least that's what I wrote it for.) sean On 6/21/05, John Fallows <[EMAIL PROTECTED]> wrote: > 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. >
