After that small sidestep back to the back button problem: when the view state is stored in the html on client side any request will submit the view state. So if you go back in browser history using the back button and then submit a form the old view state will be submitted, too, and the view will be restored exactly in the state it was when the respective page was rendered.
So to make it short: client-side state saving will make the back button work in the way you are looking for. BUT: we have to resolve the NotSerializableException issue first so your are able to use client-side storage.
Best regards, Oliver
[EMAIL PROTECTED] wrote:
We do this aswell here (pop-up). But I searching currently for a solution...
The strange thing for me is that if jsf can make a sync with a request, why can't it
execute the current action aswell in this request...
Chris
*Heath Borders-Wing <[EMAIL PROTECTED]>*
15.11.2004 04:16 Bitte antworten an "MyFaces Discussion"
An: MyFaces Discussion <[EMAIL PROTECTED]>
Kopie: Thema: Re: Back Button problems
I was wondering this as well. I think its in the JSF spec that this occur, but I don't really understand why that needs to be the case.
The short answer is to pop your JSF application up in a new window so that the user cannot use the forward/back buttons. That's what we have done.
On Sun, 14 Nov 2004 17:43:54 -0700, Arinaya <[EMAIL PROTECTED]> wrote:
>
>
> So this is an inherent flaw of JSF then.
> No workaround? Anyone?
>
> Is it possible maybe that when a form is submitted and the View is not
> synchronized with the current page, to do some special magic? Assuming the
> backing bean is still stored on the session, is it possible to process the
> request even though the View is out of synch?
>
> > -----Original Message-----
> > From: Heath Borders-Wing [mailto:[EMAIL PROTECTED]
> > Sent: Sunday, November 14, 2004 12:27 PM
> > To: MyFaces Discussion
> > Subject: Re: Back Button problems
> >
> > I don't think there is a way you coudl do this with
> > javascript because when you hit the back button you aren't
> > talking with the server at all, you are just going through
> > the browser's cache.
> >
> >
> > On Sun, 14 Nov 2004 08:45:08 -0700, Arinaya
> > <[EMAIL PROTECTED]> wrote:
> > > Ok that makes sense.
> > > But is there any way to force JSF to refresh the View when
> > a page is
> > > loaded in the browser?
> > >
> > > Or is it possible to send a request automatically on page
> > load if the
> > > View is not synchronized with the current page?
> > >
> > > I think I could use javascript to do a form submit on page
> > load, but
> > > how would I check the current JSF View using javascript? Is
> > it possible?
> > >
> > > Thanks
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Heath Borders-Wing [mailto:[EMAIL PROTECTED]
> > > > Sent: Sunday, November 14, 2004 8:35 AM
> > > > To: MyFaces Discussion
> > > > Subject: Re: Back Button problems
> > > >
> > > > 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]
> > > >
> > >
> > >
> >
> >
> > --
> > If you don't have a GMail account, I probably have 5 invites.
> > Just ask!
> > -Heath Borders-Wing
> > [EMAIL PROTECTED]
> >
>
>
-- If you don't have a GMail account, I probably have 5 invites. Just ask! -Heath Borders-Wing [EMAIL PROTECTED]
-- Oliver Rossmueller Software Engineer and IT-Consultant Hamburg, Germany http://www.rossmueller.com
