myfaces-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Robinson" <andrew.rw.robin...@gmail.com>
Subject Re: javax.faces.ViewState contents?
Date Thu, 23 Aug 2007 15:33:48 GMT
The entire component tree is saved using saveState, I wasn't referring
to the saveState component, but ranter the saveState method on the
StateHandler interface

On 8/23/07, Ken McArthur <ken.mcarthur@adsea.com> wrote:
>
> You mention what I believed to be true.  Since my simple page with a 70kb
> ViewState is not requesting saveState for anything, I suspect it must be
> something else that's being serialized.  Any ideas on what else it could be?
>
>
>
> On 8/23/07, Andrew Robinson <andrew.rw.robinson@gmail.com> wrote:
> > Anything that is returned from saveState on any object implementing
> > StateHolder is saved into the view state. (All UIComponents implement
> > StateHolder)
> >
> > On 8/23/07, Ken McArthur < ken.mcarthur@adsea.com> wrote:
> > >
> > > With client state saving, I was under the impression that only managed
> beans
> > > in session scope or used in t:saveState would be serialized into the
> hidden
> > > javax.faces.ViewState variable.  However, my application's creating
> > > ViewStates in pages with very simple forms that are almost 70 kb long!
> > >
> > > I'm thinking that if I serialized all managed beans in all scopes +
> resource
> > > bundle, it might come to about that.
> > >
> > > Do you know what specifically is stored in ViewState?  Put in other
> words,
> > > what is best way to architect application to minimize size of ViewState
> > > while still using client state saving?
> > >
> > > Thanks, I appreciate any advice,
> > > Ken
> >
>
>
>
> --
> 303-619-6607
> http://adsea.com

Mime
View raw message