MYFACES-539 is not releated to preserveDataModel. Please open a new ticket for that. It would nice if someone can provide a patch with an idea how we can solve that.
2005/9/8, Mike Kienenberger <[EMAIL PROTECTED]>: > Do one of the committers want to usurp MYFACES-539 to represent this > optimization improvement? Otherwise, MYFACES-539 should probably be > closed and another issue should be opened. > > -Mike > > On 9/1/05, Mathias Brökelmann <[EMAIL PROTECTED]> wrote: > > > a) If the dataTable is defined with its preserveDataModel set to "true", > > > then the data from your backend will be requested twice: > > > > > > 1) One in the RENDER PHASE by the HtmlTableRenderer as a consequence of > > > the > > > execution of the HtmlTableTag doEndTag() method (obviously to be able to > > > 'paint' the data in the view) > > > 2) Another one again in the RENDER PHASE, but this time due to the > > > execution of the ViewTag doAfterBody() method, that in turn calls the > > > UIViewRoot processSaveState() method, and then the HtmlDataTable > > > saveState() > > > method. More precisely, when saving the state of the dataTable, as we have > > > set preservedDataModel to "true", the data is again request from the > > > backend > > > to be serialized and stored in the session (if server state saving) or the > > > client (if client state saving, gzipping and base 64 enconding it). > > > > The second time is not necessary but it is implemented as You said. > > We should change this because that would make it possible (at least > > theoretically) that the data changed between the two calls. > > > > Regards, > > > > Mathias > > > -- Mathias
