Martin,
Firstly Antelope uses fulcrum security (e.g. the next generation
Turbine Security). To make this back compatible there is a
TurbineUserAdaptor that maps TurbineUser calls onto Fulcrum security calls.
A number of the TurbineUser calls have not yet been mapped.
The Session service appears to depend on the TurbineUser object
being placed in the Session - I had a look in all the likely places
(SessionValidator, TurbineUser, SecurityService, RunDataService, RunData)
and can't see anywhere it does this. Has anyone used the session service
successfully recently?
I am not sure how to fix this - the place to start would be to find
where Turbine does/did put the user into the session. A clue to this (I
suspect) is logoutuser uses AccessControlList.SESSION_KEY whereas other
places use TurbineUser.SESSION_KEY.
Thanks
Ben
> -----Original Message-----
> From: Martin Wendel [mailto:[EMAIL PROTECTED]
> Sent: 07 July 2004 00:07
> To: 'Turbine Users List'
> Subject: RE: SessionService working?
>
> Nothing on this?
>
> /Martin
>
> -----Original Message-----
> From: Martin Wendel [mailto:[EMAIL PROTECTED]
> Sent: 6. juli 2004 01:24
> To: 'Turbine Users List'
> Subject: RE: SessionService working?
>
> 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]
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
> Scanned for viruses by MessageLabs
>
Scanned for viruses by MessageLabs. The integrity and security of this message cannot
be guaranteed. This email is intended for the named recipient only, and may contain
confidential information and proprietary material. Any unauthorised use or disclosure
is prohibited.
