, December 01, 2003 8:38 PM
To: Tomcat Users List
Subject: Re: Argument Type Mismatch
ahha - the session won't have the password. But the Realm will. (or might not
depending on implementation). Actually - the Principal could have the
password if it extends GenericPrincipal. If not, you could
as optimally as any implementation creating the
pairing with Session ID (which is a 1 time shot anyway).
Justin
-Original Message-
From: Tim Funk [mailto:[EMAIL PROTECTED]
Sent: Monday, December 01, 2003 8:38 PM
To: Tomcat Users List
Subject: Re: Argument Type Mismatch
ahha - the session
In server.xml, Listeners are LifeCycleListeners
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/catalina/docs/api/org/apache/catalina/LifecycleListener.html
-Tim
Hart, Justin wrote:
Listener className=class inheriting from SessionListener/
I get an argument type mismatch error parsing my
PROTECTED]
Sent: Monday, December 01, 2003 7:29 PM
To: Tomcat Users List
Subject: Re: Argument Type Mismatch
In server.xml, Listeners are LifeCycleListeners
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/catalina/docs/api/org/apache/catalina/LifecycleListener.html
-Tim
Hart, Justin wrote
is it possible, if at all, to add my own SessionListener?
Justin
-Original Message-
From: Tim Funk [mailto:[EMAIL PROTECTED]
Sent: Monday, December 01, 2003 7:29 PM
To: Tomcat Users List
Subject: Re: Argument Type Mismatch
In server.xml, Listeners are LifeCycleListeners
http
not happening? How
is it possible, if at all, to add my own SessionListener?
Justin
-Original Message-
From: Tim Funk [mailto:[EMAIL PROTECTED]
Sent: Monday, December 01, 2003 7:29 PM
To: Tomcat Users List
Subject: Re: Argument Type Mismatch
In server.xml, Listeners
]
Sent: Monday, December 01, 2003 8:10 PM
To: Tomcat Users List
Subject: Re: Argument Type Mismatch
Ahh, I see. Why implement SessionListener which is tomcat specific when you
can implement the Servlet specific ones in web.xml?
Look at the code for SingleSignOn or any code that utilizes it as to how
