Can you just simply track user activity and store it into a persistence layer that do not expires with session and then once session expires redirect them to that last page (after they have logged in?)?. You could add a "check" that sees if the user had some pending actions (that are cleaned out if he signs out) and ask him to resume what the was doing. Of course, you will have to re-create the state of the page they were at.... which might not be easy if that page changed a lot via AJAX interaction e.g. if page contained a table they navigated or filtered via AJAX you will have to take that into account... or just put them in a sort of initial state.
Another possibility is to add an "AJAX hart bit" to such pages to make sure session does not expire while the user is using them... Best, Ernesto On Mon, Dec 28, 2009 at 9:48 AM, Arie Fishler <[email protected]> wrote: > Hi, > > When a client has a page in his browser that he does not touch for a while > and the session expired. after that if he hits an ajax link for example - > an > exception occurs in the wicket level due to the session expired state. > > How can I gracefully handle such a situation assuming that there is no a > single "home page" i can transfer the user. This means that the session > itself had some information on the specific environment the user was in. > > I can think of adding some information on the ajax link that will indicate > that but again the exception happens at the wicket level and if I am > handling the exception not sure how I can retrieve such data. > > Any good methodology here? > > Thanks, > Arie >
