> From: "Marc Lustig" <[EMAIL PROTECTED]> > > Hi, just another basic question: > > I want to extend org.apache.turbine.om.security.TurbineUser to provide > business logic functionality to my application to use them in Screen > classes, Action classes, Peer classes. > > I adjust TR.props: > > services.SecurityService.user.class=de.geoconnect.audiotex.AudiotexUser > > Q: Is that all I have to do, or is there something else to do? > > JavaDoc/ org.apache.turbine.om.security.TurbineUser says: > "You are welcome to extend this class if you wish to have custom > functionality in your user objects (like accessor methods for custom > attributes). Note* that implementing a different scheme of user data storage > involves writing an implementation of UserManager interface. " > > Q: What is refered here as "a different scheme of user data storage"? > The TurbineUser Peer or what? > > Q: In what case do I have to write an implementation of UserManager > interface? > > Thanks. > > Marc
Hi Marc, I'm afraid you have just grabbed a snake by the tail. From what I understand, the only people that have successfully extended the turbine-user table in turbine 2.2bx have been using the DBSecurity service in fulcrum rather than the one provided with turbine itself. On top of this I think the better option may be to utilise the SecurityService proposal code in fulcrum cvs head from Henning - this seems to add a whole lot of flexibility (IIRC Henning was going to make the internal cvs repository (of the company he works for) containing additional enhancements to fulcrum available for read-only access, but I don't think this has happened yet). I keep saying I am going to look into this, but other things keep cropping up to distract me. HTH, Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
