Using some kind of HttpSessionBindingListener won't solve the problem since
I don't want to know if certain objects are removed from a session. Even if
I knew this, what could I do with it? When the next request arrives it is
assigned a new session ID and there is no way for me to see that both
sessions are related in any kind of way.
Using request.isRequestedSessionIdValid() at any place behind
processLocale() will also not help since at that moment the session has been
created and will be valid every time. And session.isNew() won't help either
because then I do not know if the session is only new because the user
accessed the site for the first time or if his old session was timed out...
My current solution is to override the process() of ActionServlet in my own
servlet class and to check for deprecated sessions first. Then I call
super.process(). Providing a processSession() method for this purpose would
be a more elegant way in my opinion.
This could also solve the problem that somebody has to put a set of default
objects into every new session. E.g. we use a TempHolder object in order not
to clutter the session context with temporary objects.
Andreas
> -----Original Message-----
> From: Jonathan Asbell [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, June 06, 2001 1:58 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Handling session timeouts
>
>
> implement something using the HttpSessionBindingListener. We could
> serialize the data, or at least know that we lost the session data
>
>
