As for me, I can't use client side state saving because of
AjaxAnywhere. I needed multiple AJAX zones inside of my form.
Unfortunately (with facelets at least) state is saved right below the
form. So with AA and client side state, my state was never updated due
to the fact it was outside of the area AJAX was updating.
Also, I am not a big fan of client side state due to security and performance.
I just hope that Sun figures out a way to have multiple view server
side states. JBoss Seam (which I am using) fixes this for
backing-beans but not for the component tree.
For the JSF RI, there has always been support for multiple view states, but only for separate page URLs. This got addressed in version 1.2.
However, it's not just up to Sun ... the MyFaces implementation of server side state saving is up to the MyFaces developers :-).
-Andrew
Craig
On 3/21/06, Vladimir Coutinho < [EMAIL PROTECTED]> wrote:
> There are others problems saving state in the client?
>
>
> On 3/21/06, Dean Hiller <[EMAIL PROTECTED]> wrote:
> > wow!!! thanks for all the response.
> > cool,
> > dean
> >
> > Aleksei Valikov wrote:
> >
> > > Hi.
> > >
> > > > 3. Use client-side state saving. Then, when users go back, they also
> go
> > > > back to the old state (serialized on the client side).
> > > >
> > >
> > >> We're using the 3rd choice, with no problems. Incidentally, the third
> > >> choice also works nicely if you use pop-up windows and then return to
> > >> the "main" window.
> > >
> > >
> > > This won't work for me. I simply can't switch to the client-side state
> > > saving method.
> > >
> > > * I have very large component trees with hundreds of components. it
> > > would be a killer to serialize and de-serialize them on each request.
> > > * I use a lot of unserializable value/method bindings.
> > >
> > > Bye.
> > > /lexi
> >
> >
> >
>
>
>
>
> --
> Vladimir M Coutinho
