Marty - thanks for the help.
Actually even with client state saving, the Trinidad framework save state
on the server (and actually, I have the State saving method set to client)
and just a token on the client. I'm not sure of all the things going on
here, I'm just reporting what I am seeing.
Thanks for the suggestion of saveState. I'll look at it.
Also, I am using Seam and for anyone reference I wrote another email
describing the solution I came up with that uses the "Page Actions" found
in Seam.
Thanks again for your help,
Chris....
Marty Bergerud wrote:
You can save the page's "viewstate" on the browser by adding this entry
to your web.xml file
<context-param>
<param-name>javax.faces.STATE_SAVING_METHOD</param-name>
<param-value>client</param-value>
</context-param>
That way the page view is restored even after a session timeout.
You can also use the <t:saveState> tag as in...
<t:saveState id="saveDialogBean" value="#{dialogBean}"/>
Marty
*Chris Hane <[EMAIL PROTECTED]>*
06/29/2007 02:49 PM
Please respond to
"MyFaces Discussion" <[email protected]>
To
MyFaces Discussion <[email protected]>
cc
Subject
Refresh View after HTTPSession Timeout
I have a generic search screen (standard input form) that displays the
results on the "next" page using a <tr:table>.
If the user hits the refresh button any time prior to the HTTPSession
timeout, then the form is resubmitted and the search generated again (could
display different results if the underlying data has been updated - which
is what we want to happen).
If the user leaves (for a time greater than the HTTPSession timeout) the
results screen, comes back and hits the refresh button after the timeout,
the "Find" screen is displayed again.
I am using Trinidad 1.0 Myfaces 1.1, Jboss 4.0.x, Seam 1.2p1 with client
side state saving.
One of the first errors in the log is:
2007-06-29 15:35:17,593 ERROR [STDERR] Jun 29, 2007 3:35:17 PM
org.apache.myfaces.trinidadinternal.application.StateManagerImpl
restoreView SEVERE: Could not find saved view state for token 7cad43c0
Which is why I'm assuming it is the HTTPSession timeout.
Is there anything I can do so that the "refresh" will re-run the search and
not show the Find screen?
Thanks,
Chris....
