I
Ignacio de Cordoba
Hi there,
I am having a problem when managing an excepcion in the first request
to a JSP page.
The exception makes tomcat correctly show the custom JSP error page,
but I cannot work with the builtin "session" object in that JSP page
as it doesn't persist... When I get out of the JSP and go to otheeone,
a new session is created and I loose all attributes I have put in the
previous session.
This only happens when there is no session object... I mean, the error
JSP page seems uncapable of creating a session object. Is this a
normal behaviour?
I need to get a session to store there the originating JSP that throws
it, to get there after doing the login process.
Thanks for any help/ideas on this,
Ignacio de Córdoba
I am having a problem when managing an excepcion in the first request
to a JSP page.
The exception makes tomcat correctly show the custom JSP error page,
but I cannot work with the builtin "session" object in that JSP page
as it doesn't persist... When I get out of the JSP and go to otheeone,
a new session is created and I loose all attributes I have put in the
previous session.
This only happens when there is no session object... I mean, the error
JSP page seems uncapable of creating a session object. Is this a
normal behaviour?
I need to get a session to store there the originating JSP that throws
it, to get there after doing the login process.
Thanks for any help/ideas on this,
Ignacio de Córdoba