You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@myfaces.apache.org by Nitin Deshmukh <de...@yahoo.com> on 2008/04/10 14:53:17 UTC
How does t:saveState work?
Hi,
I am trying to find out how saveState works? does it
save objects in the session or keeps it in a hidden
variable or what does it do?
any guidance or pointing in the right direction will
be helpful.
Thanks,
Nitin
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Re: How does t:saveState work?
Posted by jimmyau <ji...@privasia.com>.
So this is the advantage and disadvantage of open source is it?
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Re: How does t:saveState work?
Posted by Andrew Robinson <an...@gmail.com>.
The source is open... :)
On 4/10/08, jimmyau <ji...@privasia.com> wrote:
> Can myfaces ppl come in and explain where it is store when the setting is in
> server?
>
> ----- Original Message -----
> From: "Werner Punz" <we...@gmail.com>
> To: <us...@myfaces.apache.org>
> 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.
>
>
Re: How does t:saveState work?
Posted by jimmyau <ji...@privasia.com>.
Can myfaces ppl come in and explain where it is store when the setting is in
server?
----- Original Message -----
From: "Werner Punz" <we...@gmail.com>
To: <us...@myfaces.apache.org>
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.
Re: How does t:saveState work?
Posted by Werner Punz <we...@gmail.com>.
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
Re: How does t:saveState work?
Posted by Rogerio Pereira <ro...@gmail.com>.
saveState never save objects in session, this component is used to
avoid session overload, saveState serializes all objects somewhere in
you filesystem.
2008/4/10, Nitin Deshmukh <de...@yahoo.com>:
> Hi,
>
> I am trying to find out how saveState works? does it
> save objects in the session or keeps it in a hidden
> variable or what does it do?
>
> any guidance or pointing in the right direction will
> be helpful.
>
> Thanks,
>
> Nitin
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
--
Yours truly (Atenciosamente),
Rogério (_rogerio_)
http://faces.eti.br
"Faça a diferença! Ajude o seu país a crescer, não retenha
conhecimento, distribua e aprenda mais." (http://faces.eti.br/?p=45)