I don't think that what you are trying to do with the browser back
button is supported through server-side state saving and session beans.
The "problem" you are having actually sounds like the correct behaviour
for these settings. You may consider client-side state, t:saveState, or
some other approach. These links may get you started:
[1] http://wiki.apache.org/myfaces/How_JSF_State_Management_Works
[2] http://wiki.apache.org/myfaces/SaveState
[3]
http://bugs.sakaiproject.org/confluence/pages/viewpage.action?pageId=4981&showComments=true
Regards,
Jeff Bischoff
Kenneth L Kurz & Associates, Inc.
Chris Pro wrote:
Hi
I've got a problem with the browser back button.
The "detai.jsf" got several commandLinks. One of them is showing "detai.jsf" again, with another product. In some case the commandLink A isn't rendered. If
the back button is pressed, the page before with the commandLink is shown. But when I click on that commandLink the action is not invoked?
I've got the same problem with the dataTable. There I was able to eliminate that back button problem with preserveDataModel="true". But for a normal
commandLink (t:commandLink or h:commandLink) there isn't a method like that, or?
In other words:
1. detail.jsf (with commandLink A) -> detail.jsf (without commandLink A)
2. backButton to the first detail.jsf (with commandLink A)
3. Click on commandLink A -> nothing happens. It looks like the action is
disappeared!?
Some more information:
-STATE_SAVING_METHOD = Server
-Managed-Bean = Session
Could some please give me a hint to resolve that problem?
Thanks a lot!
