On Wed, 2005-02-02 at 14:51 -0800, Korhonen, Kalle wrote: [...] > > > It's quite understandable that if you are using > > pageScroller together > > > with the dataTable, you have to take care of saving the > > data yourself. > > Hello Kalle, and thanks for your reply. > > I don't understand well why preserveDataModel should not work > > if used with pageScroller. PageScroller is just a "normal" > > component providing pagination, what would differ if I > > implement it in my program instead of using it? > > What I mean is: if the array is correctly restored for my > > application, why it should not work for pageScroller? > > Oh, the reason is simple. Since the preserveDataModel saves only what > the dataTable displays, and pageScrollers divides the data into multiple > pages, preserveDataModel happily remembers only the results displayed on > the first page.
Thanks for the explanation, now this is much clearer to me now :) > > Anyway, since they both are myfaces components, I expect them > > to correctly work together so a warning or something similar > > in the documentation would be welcome. > > I 100% agree with you there. Even better, pageScroller could "take > over", force the preserveDataModel in the datatable to reset to false > and/or have its own preserveDataModel. Volunteering to implement that? > :) :) I'm sorry I'm not skilled enough to add a similar feature, anyway I find it could be useful a feature request on jira to not forget this great suggestion. Can you enter it since you could certainly explain the thing better than me? (otherwise tell me and I'll do it c&p your text above ;) ) Thanks, Alex
