The back button is actually a problem with JSF in general as if the user
hits "back" they are now on a different view to the one the server
thinks they have, but it's particularly emphasised in dialogs.
If you don't using dialogs you can overcome it by setting the JSF
save-state to "client". Then the page will send the current view state
to the client along with the view instead of storing against the session
on the server. The drawback is that this increases the amount of data
sent to the client.
Configure it in web.xml like this:
<context-param>
<param-name>javax.faces.STATE_SAVING_METHOD</param-name>
<param-value>client</param-value>
</context-param>
The alternative is to set it to "server" which is the default. I decided
not to use dialogs for just this reason.
Cheers,
Ian.
Apologies for previous empty post - got over-ecited when Brazil scored!
-----Original Message-----
From: Wendy Smoak [mailto:[EMAIL PROTECTED]
Sent: 13 June 2006 18:52
To: Struts Users Mailing List
Subject: Re: [shale] back button issue
On 6/13/06, stephan opitz <[EMAIL PROTECTED]> wrote:
> while rebuiding the login procedure from the use-cases, i found the
> problem with the browser back button...
>
> shale does not know that the actual view was finished.
>
> anybody has some answers?
This is most likely related to SHALE-48 [1]. Unfortunately, there's no
resolution yet. Please comment on the issue if you have any ideas!
[1] http://issues.apache.org/struts/browse/SHALE-48
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
