The filter runs on the appropriate (or all) requests and would check if the beans are in the session. If not - redirect.
OR
If all the pages set an error condition - you might be able to use an error mapping directive in web.xml
-Tim
Tarek M. Nabil wrote:
Hi everyone,
I have an application that uses beans stored in the session context. If the user's session times out, he's asked to re-login on his next request. For this, I'm using J2EE security; I'm not doing it myself. After the user is finished with the re-login, he's supposed to complete his request, but the fact that the beans are not in the session anymore produces an error. Unfortunately, those beans are specific to the last request the user made, so I cannot re-initialize them in a listener for session creation.
I was wondering if there's a way to configure security so that after the user logs in he's redirected to a certain page instead of being able to continue his last request.
I know this can be done manually, but I would have to do it in every web component I have which is really tiresome. Any quick solutions?
Any help is appreciated.
I'm sorry that this question is not Tomcat specific, but I tried the servlet-interest list and got no responses.
Thanks, Tarek M. Nabil
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
