You can try to get round this on the client side with JavaScript but to do
things robustly you need to handle this server side.
How do you handle the navigation, validation and processing from your JSP?
Have a look at the State pattern, this works really well for an encapsulated
approach to this, and can easily be extended to cope with both forward and
backward navigation.
If that doesn't make sense then give me a shout,
Kev
> -Original Message-
> From: Ray Brown [mailto:[EMAIL PROTECTED]]
> Sent: 22 February 2001 00:44
> To: Orion-Interest
> Subject: RE: Bowser back buttons and jsp
>
>
> What is an example of the errors?
>
> I use a nice freebie menu system, written in JavaScript, for
> my apps and if the user uses the "Back" button (provided by
> the browser) and the page has not fully been written by the
> browser, the browser decides not to display the page at all.
> If you request to view the source, it's there. Is this the\
> kind of error you mean? [This occurs under NS4.5 on Apache
> or Orion]
>
> Ray
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of
> [EMAIL PROTECTED]
> Sent: Wednesday, February 21, 2001 3:49 PM
> To: Orion-Interest
> Subject: Bowser back buttons and jsp
>
>
>
> This question doesn't really apply to the webserver in
> general. I have
> developed an ecommerce application using java beans and jsp.
> Unfortunately, during qa testing, one problem keeps coming up. If you
> click the back button on the browser and ignore the
> navigation built into
> the system, you encounter errors. I've researched if there
> was a way to
> disable the browser navigation options via javascript or some
> other way but
> I found that this is not really possible. What I was
> wondering is how do
> other java professionals handle this problem? Has anyone
> ever ran into
> this?
>
>
>
>
