The source is open... :)
On 4/10/08, jimmyau <[EMAIL PROTECTED]> wrote: > Can myfaces ppl come in and explain where it is store when the setting is in > server? > > ----- Original Message ----- > From: "Werner Punz" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: 2008/04/10 9:47 PM ii > Subject: Re: How does t:saveState work? > > > > Rogerio Pereira schrieb: > >> saveState never save objects in session, this component is used to > >> avoid session overload, saveState serializes all objects somewhere in > >> you filesystem. > >> > > > > This is not entirely true savestate uses the standard jsf save and restory > > cycle to store the data. It simply serializes the referenced bean and > > deserialises it. > > It now depends on the save and restore settings of the jsf implementation > > where the data is stored. > > If you have client side state saving it will store the data into the > > browser, if you have server side it depends on where the server side state > > saving is stored to. Depending on the settings it stores it into the > > session or somewhere else. > > > > Werner > > > > > > -- > > This message has been scanned for viruses and > > dangerous content by MailScanner, and is > > believed to be clean. > > > > > > > > > > -- > > No virus found in this incoming message. > > Checked by AVG. Version: 7.5.519 / Virus Database: 269.22.11/1368 - > > Release Date: 4/9/2008 4:20 PM > > > > > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > >
