Once the session expires... this code never gets called by tomcat. So I
am not really sure what you are thinking about?
-Dennis
that is cause you have protected every single resource in your webapp and
require login for that.
hence, every single resource is bound by the session existing or not.
ip Hanik - Dev Lists [mailto:[EMAIL PROTECTED]
Sent: Monday, February 20, 2006 11:46 AM
To: Tomcat Users List
Subject: Re: Help with detecting session timeout
no, that is not true, this could be your servlet (note, this assumes
your session was created by another JSP/servlet.
note, you can also do re
--- "Klotz Jr, Dennis" <[EMAIL PROTECTED]> wrote:
> Greetings to all.
>
> I hope everyone had a great weekend. :) I've run
> into a problem that I
> can't find any answers for and I am hopeful that one
> of you has the time
> to respond.
>
> Given:
> * Tomcat 5.5.15
> * Applet using jvm 1.5
> *
ay, February 20, 2006 11:24 AM
To: Tomcat Users List
Subject: Re: Help with detecting session timeout
in your servlet, you can do
...
if ( session_has_timed_out) {
response.setError(505,"Session has timed out");
return;
}
then in your applet, you can catch the 505,
Filip
n for responding.
-Dennis
-Original Message-
From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED]
Sent: Monday, February 20, 2006 11:24 AM
To: Tomcat Users List
Subject: Re: Help with detecting session timeout
in your servlet, you can do
...
if ( session_has_timed_out) {
response.setErro
in your servlet, you can do
...
if ( session_has_timed_out) {
response.setError(505,"Session has timed out");
return;
}
then in your applet, you can catch the 505,
Filip
Klotz Jr, Dennis wrote:
Greetings to all.
I hope everyone had a great weekend. :) I've run into a problem that I
c
From an applet? There probably is no easy answer... any solution would
involve either polling the server from the servlet, or pushing the
status out to the servlet... the later should be doable from a
SessionListener... record the remote IP when the session is created, and
send a ping to it wh
