How to handle session timeout with wicket ajax requests?

I have found an ugly workaround for this, the wicket devs obviously do not see demand to handle ajax session expiration on the client side.

I have found an ugly workaround for this, the wicket devs obviously do not see demand to handle ajax session expiration on the client side. Have a look at the solution here: https://issues.apache.org/jira/browse/WICKET-3081.

Yup, that's all I could've come up with too, I'm afraid. The only thing else you can do is to prevent the timeout in the first place my having a component on your page that regularly updates itself (but that's a bit ugly). – Sean Patrick Floyd Sep 28 '10 at 14:11.

The session expired page usually appears when your pages are not bookmarkable and you make a request for a page to the server but the server has a different version of the page that you have requested. It shouldn't have anything to do with the session time out which is defined in the web. Xml file.As a good practice, your pages should have a constructor with PageParameters.

Also be careful with the popup pages because they usually generate these kind of errors when they are not using PageParameters.

We're having PageParameters and all this stuff. But if there's any component depending on the page state, e.g. An ajax component, the user will be redirected to the SessionExpiredPage when an ajax request goes out after the session has timed out. – PeterP Oct 14 '10 at 9:31 check your web.

Xml for the session timeout configuration – virgium03 Oct 14 '10 at 10:01.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.