Hi,
there are multiple factors involved here:
A) PageSettings#recreateBookmarkablePagesAfterExpiry
B) is your page bookmarkable
C) PageSettings#callListenerAfterExpiry
D) ExceptionSettings#ajaxErrorHandlingStrategy
Depending on their combination of trues a session timeout will result in
- a new page instance ignoring the last request (default A and B true)
- a new page instance applying the last request (A, B, C true)
- the error page (A false, default D->REDIRECT_TO_ERROR_PAGE)
- triggering of JS failure handler (A false, D->INVOKE_FAILURE_HANDLER)
Use INVOKE_FAILURE_HANDLER, then you can handle the failure in
JavaScript and do whatever you want.
This can be done by your AjaxBehaviors or global listeners:
https://ci.apache.org/projects/wicket/guide/7.x/single.html#_global_listeners
Have fun
Sven
Am 23.03.2018 um 06:02 schrieb Ernesto Reinaldo Barreiro:
I had the impression redirecting to home page was standard behavior
On Thu, Mar 22, 2018 at 9:28 PM, Entropy <[email protected]> wrote:
When wicket times out, and the user clicks something ajax oriented, they
just
get an error in the page in javascript. No message or redirect to the Home
page or anything. We'd prefer to redirect them to a home page as if they
first arrived in the app.
Is there a way to accomplish that? I saw some threads about session
timeouts but they didn't seem to want what we want.
--
Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-
f1842947.html
---------------------------------------------------------------------
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]
