The server-side support for back buttons in MyFaces only ensures that the data held by JSF components doesn't get confused by back-buttons. Of course this issue is irrelevant when using client-side state-saving.
However in either case, if there are any session-scoped backing beans being used by the app then they get out-of-sync with the GUI when back buttons are pressed, regardless. Simple jsf apps can be written without session-scoped beans, but it takes some effort to avoid them in larger apps. The t:saveState tag doesn't really scale ;-) Regards, Simon On Tue, 2007-08-07 at 16:45 -0400, Mike Kienenberger wrote: > I'm not entirely certain, but setting this parameter to 1 might solve > the problem for you if you use server-side state-saving. However, I > use client-side state-saving so I can't say for sure. > > <context-param> > <param-name>org.apache.myfaces.NUMBER_OF_VIEWS_IN_SESSION</param-name> > <param-value>1</param-value> > <description>Only applicable if state saving method is > "server" (= default). > Defines the amount (default = 20) of the latest > views are stored in session. > </description> > </context-param> > > > On 8/6/07, Escalada Sergio <[EMAIL PROTECTED]> wrote: > > Hello. > > I am using MyFaces 1.1.5, Tomahawk 1.1.6 in my WEB Aplication, and i > > have a requirement mandatory to disable the browser back button while > > the user is interacting with the aplication. The requirement is really > > serious and compromise the usability of the aplication, can anyone tell > > me if it is possible to do anything to avoid the use of the browser back > > button?, or at least to control the use of it trying to avoid the > > consecuences it carry. > > > > Thanks in advance, sorry for my english. > >
