I've been trying to dig through the code, and reading up on the different stuff. It looks like it does listen, it should initialize, and I call the TurbineService statically to get the information.
So perhaps it is something with the Antelope/2.4 pipeline that hooks into this and changes it? I would have thought a listener wouldn't really care as to what it did use.. but maybe I'm wrong. Seems really odd... /Martin -----Original Message----- From: Martin Wendel [mailto:[EMAIL PROTECTED] Sent: 5. juli 2004 17:46 To: 'Turbine Users List' Subject: SessionService working? Calling TurbineSession.getActiveUsers().size() returns 0... I have setup a listner in the web.xml: <listener> <listener-class> org.apache.turbine.services.session.SessionListener </listener-class> </listener> Put in the following in TR.props: services.SessionService.classname=org.apache.turbine.services.session.Turbin eSessionService services.SessionService.earlyInit=true tool.session.sessionmgt = org.apache.turbine.services.session.SessionTool So I should be all set to go? Btw, how does this work if you use multiple tomcat's for load balancing? /Martin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
