Rodney Schneider <[EMAIL PROTECTED]> writes:
> Turbine uses the standard HttpSession interface from the servlet
> api, and these sessions are managed by your servlet
> container. [...]> You should then be able to get the User object
> from the session like this:
>
> User user = (User) session.getAttribute(User.SESSION_KEY);
Uh huh.... Interesting. I had found a work-around before I got your
reply which goes like this:
User user = DefaultTurbineRunData.getUserFromSession(session);
Unfortunately, when I tried to continue that approach to get ACL info,
I hit a wall: there aren't any other directly-callable methods.
So I went back to your mail. I looked at what else was stored in the
session with session.getAttributeNames() and it showed turbine.User
and turbine.AccessControlList -- and only those. Fortunately, they're
enough for my needs right now: User and AccessContolList.
But I was wondering how I would have known that those useful entities
would be put there by Turbine, and why other useful objects are not put
there. I'm trying to understand why Turbine does what it does.
Thanks again.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
