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. On Mon, 07 Mar 2005 20:54:19 +0000, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Does this have to do with parameters in the URL query parameters? I noticed > that in the Sun RI, the lifecycle stops short unless the request method is a > post or put. I'm not sure if this is true for the latest Sun RI. > > When using the back button, does the target page have query parameter > arguments? > > > > What state saving method are you using? client or server? > > > > The back-button problem is a conflict between the HTML spec and the > > JSF spec. Thus, it should appear in all implementations that > > correctly follow the spec. > > > > > > On Mon, 7 Mar 2005 13:18:38 -0600, Jonathan Eric Miller > > <[EMAIL PROTECTED]> wrote: > > > I think I do remember reading something about a back button problem in > > > Faces > > > in general. However, the problem that I'm seeing, only happens with > > > MyFaces > > > and not the RI. > > > > > > Jon > > > > > > ----- Original Message ----- > > > From: "Martin Marinschek" <[EMAIL PROTECTED]> > > > To: "MyFaces Discussion" <[email protected]>; > > > <[EMAIL PROTECTED]> > > > Sent: Monday, March 07, 2005 10:48 AM > > > Subject: Re: Back button problems > > > > > > > Well, if it is the back browser issue Jonathan is talking about, that > > > > shouldn't work in the RI either, so it must be something else? > > > > > > > > regards, > > > > > > > > Martin > > > > > > > > > > > > On Mon, 7 Mar 2005 10:45:43 -0600, Heath Borders > > > > <[EMAIL PROTECTED]> wrote: > > > >> This can be fixed by switching to client-side state saving. There is > > > >> no fix for server-side state saving. > > > >> > > > >> On Mon, 7 Mar 2005 10:15:50 -0600, Jonathan Eric Miller > > > >> <[EMAIL PROTECTED]> wrote: > > > >> > I'm guessing that this a known issue. I just switched from the JSF RI > > > >> > to > > > >> > MyFaces and I pretty much have everything work alright. However, I > > > >> > found > > > >> > that if I use the Web browser back button to go back a page and then > > > >> > click a > > > >> > button, it doesn't work correctly. I redisplays the same page. Then, > > > >> > if > > > >> > you > > > >> > click the button again it does what it's supposed to. Has anyone else > > > >> > ran > > > >> > into this problem? > > > >> > > > > >> > Jon > > > >> > > > > >> > > > > >> > > > >> -- > > > >> -Heath Borders-Wing > > > >> [EMAIL PROTECTED] > > > >> > > > > > > > > > > > > > > > > -- > > -Heath Borders-Wing > > [EMAIL PROTECTED] > -- -Heath Borders-Wing [EMAIL PROTECTED]
