I agree. However, if you read his question, it states that he was "losing his data" because it was stored in the request. Save state fixes that. It was never mentioned that the data was too large to stay in the request. But since it probably is, the solution you provided is best.
On 4/25/06, Werner Punz <[EMAIL PROTECTED]> wrote: > Geoff Longo schrieb: > > Have you looked into the saveState component? > > http://wiki.apache.org/myfaces/SaveState > > > > On 4/25/06, Werner Punz <[EMAIL PROTECTED]> wrote: > >> [EMAIL PROTECTED] schrieb: > >>> I have a Datatable which has thousands of items in it. I get this items > >>> via a database. I don't want to store them in the session, because this > >>> will kill the session... > >>> > >>> So I put it into request scope.. The problem now is the the datascroller > >>> doesn't work anymore, because I loose the list, because it's only in > >>> request scope... > >>> > >>> What would be the best way to overcome this problem? > >>> > >> Using a datamodel overcomes this problem. > >> There is a wiki entry in the myfaces wiki which describes exactly > >> on how to write your own custom data models. > >> > >> > > > savestate does not make sense in this case, savestating thousands of > datasets is quite a performance hit. > A custom data model is way better for achiving the required results. > The interfaces is somewhat generic though so it is a little bit of work > to implement one of those. > >
