> It appears that the best way to go about this is to have my custom User > class either implement org.apache.turbine.om.security.User or extend > org.apache.turbine.com.security.TurbineUser. I'm preparing my own User / > Permissions schema, so I'll probably do the former. Then I'd set the "User" > field in RunData, which requires an org.apache.turbine.om.security.User. > That gives me the impression of being session-persistent, and the RunData is > available globally to the Context. > > Does this seem to be the best solution to everyone out there?
No. The RunData is not session-persistent. It's available to each velocity template within a request, but it's rebuilt on reach request, given that, by nature, HTTP is a stateless protocol. As Cameron noted, the TurbineUser's setTemp or the RunData's getSession are currently the only means of persisting objects across page requests. - Stephen -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
