How exactly do you see this implemented? There will be plenty of details to be taken care for. e.g. For how long should this information stay on that Servlet Context? If your application has many users what information should go there?...
Wouldn't it be simpler to have a component instantiation listener, mark the pages you need with some interface and start a kind of "recorder" whenever the user hits one of those pages... I see no much difficulty on implementing this last approach... Ernesto On Mon, Dec 28, 2009 at 10:16 AM, Martin Makundi < martin.maku...@koodaripalvelut.com> wrote: > > 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?)?. > > Maybe wicket could do this automatically using Servlet Context? > > ** > Martin > > > > > Best, > > > > Ernesto > > > > > > > > On Mon, Dec 28, 2009 at 9:48 AM, Arie Fishler <arie....@gmail.com> > 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 > >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
