Re: Back button problems

[Jonathan Eric Miller]

Thanks for all the replies. If I do switch to client-side state saving one 
issue that I'm wondering about is beans with DataModels in them. For some 
god forsaken reason, they aren't Serializable. Anyone know why that is?

Jon
----- Original Message ----- 
From: "Heath Borders" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; "MyFaces Discussion" 
<myfaces-user@incubator.apache.org>
Sent: Monday, March 07, 2005 3:00 PM
Subject: Re: Back button problems


If you search the archives, I'm sure you can find more details, but
here's the short version:
If you're using server-side state saving, the spec requires that you
save a copy of the serialized component-tree state on the session.
The spec also says that if a request comes in for a view that is has
not been serialized in the session that the lifecycle must just render
the view, save a serialized copy on the session and do nothing more.
Thus, if the user clicks the back button, the saved view is out of
synch, so anything they do on that page will just result in a
redisplay of the same page.  Then, the saved view is in synch again,
and they can do what they want.
Client-side state saving doesn't have this problem.  The easy solution
is just to use that.