>
> Thanks for the info, just to check that we are doing this the 'right way': We
> created our own user class, which was exactly the same as TurbineUser except
> we don't save to storage and no peers are used. Set up our own LoginUser
> object to validate the u/p, set up a User object, and store it in the session.
> I also had to create a DefaultAccessControl to set the Roles and Permissions
> properly. The turbine default uses peers for getting the security information
> from the db. After all that it seems to be working well. Any other
> gotcha's?
If it is working, then I doubt there are any other gotcha's. ;-)
I know it is a pain to do all that work, but you are essentially just
overriding all of Turbine's default stuff...
Yes, more documentation on this is needed...I'm adding your posts to the
FAQ...
-jon
--
Scarab -
Java Servlet Based - Open Source
Bug/Issue Tracking System
<http://scarab.tigris.org/>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
