Hi Marc, I was following this thread as I am looking at a similar situation.
So did you make your own object extend the Acegi user object? Thanks! On 4/8/08, mschipperheyn <[EMAIL PROTECTED]> wrote: > > Never mind. Rolling your own is actually quite easy once you start to read > the reference docs. > > Cheers, > > Marc > > > mschipperheyn wrote: > > > > Hi, > > > > I've started to work on the web part of my app and quickly realized I need > > to configure ACEGI for this. So far, I have ignored the app_user and > > app_role stuff and just created my own user class because of it's more > > specialized nature. Now, I'm finding that I don't want to build all this > > Acegi stuff when it's working out of the box on app_user. So, I'm > > wondering about the best usage scenario here. Should I change my user to > > extend app_user (how to handle storage), or try to reference it (ugly). Or > > is the answer: suck it up and pick up the Acegi manual? > > > > Cheers, > > > > Marc > > > > -- > View this message in context: > http://www.nabble.com/Acegi-and-app_user.-Recommended-use-of-custom-user-classes-tp16556921s2369p16572058.html > Sent from the AppFuse - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
