yes, that really is kind of a week point - even though I don't think the data wouldn't be cached here by the application for the duration of the request.
regards, Martin 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 > -- http://www.irian.at Your JSF powerhouse - JSF Trainings in English and German
