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 a SessionListener gets registered. I am guessing that you'll actuall need to implement a no-op Vavle that registers the Listener on initialization of the Vavle. But thats just a no code look swag.

-Tim

Hart, Justin wrote:

I thought that there was something related to that, is it that it must implement LifeCycleListener & SessionListener, or is SessionListener just 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 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 server.xml... Is there something wrong with this line?




--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to