Re: Wicket Session timeout & ajax

2018-03-23 Thread Sven Meier
Wicket 6 should be similar. If you think there is a problem you can create a quickstart. Sven Am 23. März 2018 14:45:28 MEZ schrieb Entropy : >I should have mentioned, we're in Wicket 6. > >-- >Sent from: >http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html > >-

Re: Wicket Session timeout & ajax

2018-03-23 Thread Entropy
I should have mentioned, we're in Wicket 6. -- Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-

Re: Wicket Session timeout & ajax

2018-03-23 Thread Sven Meier
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

Re: Wicket Session timeout & ajax

2018-03-22 Thread Ernesto Reinaldo Barreiro
I had the impression redirecting to home page was standard behavior On Thu, Mar 22, 2018 at 9:28 PM, Entropy 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.

Wicket Session timeout & ajax

2018-03-22 Thread Entropy
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 so