> >An alternative to that would be a two-tier service implementation like
> >the
> >SecurityService, which used UserManager class to handle user data
> >storage and
> >authentication separately from authorization.
>
> I must say I don't completely understand why you don't use the
> EngineContext service which is currently defined in Jetspeed.
> It answers exactly the expressed need and works perfectly.
> If it fits a generic Turbine need, let's just move it to the Turbine
> service package...
I'm just looking at it now. Would it make sense to have a service
that deals with the servlet config instead? We can easily
access the context from the servlet config.
jvz.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
