I tried the same thing. I don't know why client side state saving was throwing a NotSerializableException, but I know why you have to submit twice.
Let's say you have two pages: A and B. If you submit a form on page A and navigate to page B, the view that JSF currently has stored is page B. So, if you use the browser's 'back' button to navigate to page A, JSF will take one request to synchronize the page and the view. Then the second request will be normal. I don't think that switching to client side state saving will change this behavior. On Sat, 13 Nov 2004 14:31:06 -0700, Arinaya <[EMAIL PROTECTED]> wrote: > Hello All, > I hope someone can please help me with this -- > > Currently when I navigate back to a form that has previously been submitted, > using the browser back button, I need to click the submit button twice in > order for the form to actually resubmit. The first click seems to reset the > form, clearing any changes that have been made to input fields since > navigating back to the form. > > We are currently using server-side state saving method, and I thought this > might be the problem, so I tried switching this to client, but then the > FacesServlet throws a java.io.NotSerializableException. > > Has anyone had either of these two problems? > How can I get the browser back button to work? > Using MyFaces 1.0.7. > > Thanks, > Arinaya > > -- If you don't have a GMail account, I probably have 5 invites. Just ask! -Heath Borders-Wing [EMAIL PROTECTED]
