There are lots of options. They can be serialized and stored in the session, not serialized, serialized and stored in a collection of view states, w/ or w/out encryption, etc. etc. saveState() is always called though.
Dennis Byrne >-----Original Message----- >From: Adam Winer [mailto:[EMAIL PROTECTED] >Sent: Thursday, March 23, 2006 02:27 PM >To: 'MyFaces Discussion', [EMAIL PROTECTED] >Subject: Re: MyFaces Tomahawk > >What do you do with the results of saveState()? Just discard 'em? > >-- Adam > > >On 3/23/06, Martin Marinschek <[EMAIL PROTECTED]> wrote: >> Ok, I didn't know that it was explicitly mentioned in the JSF1.1 spec >> that saveState is not to be called for server-side state saving. >> >> Cause as Manfred implemented that, we do it. >> >> regards, >> >> Martin >> >> On 3/23/06, Dennis Byrne <[EMAIL PROTECTED]> wrote: >> > >As of JSF 1.2, both server-side and client-side state saving will >> > >end up invoking saveState(), because the algorithm for server-side >> > >> > Good, this means t:saveState will work w/ both implementations using >> > server side state saving. >> > >> > >-- Adam >> > >> > Dennis Byrne >> > >> > >> > >> > >> >> >> -- >> >> http://www.irian.at >> >> Your JSF powerhouse - >> JSF Consulting, Development and >> Courses in English and German >> >> Professional Support for Apache MyFaces >> >
