I am using hibernate to save my user objects. It needs public getters and setters and also a default constructor. Obviously I have worked around all this, but it would be much nicer to subclass.
Thanks "Ben Alex" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Randy Thornton wrote: > > >I have provided my own AuthenticationDao implementation for my users and > >groups. I have my own user and group implementation that have data other > >than username, password, and capabilities. It would be nice if I could > >subclass off of User instead of having to create a new User object from them > >for all the apis. The problem is that the members of User are all private. > >Can these be changed to protected or is there some special reason for them > >to be private? > > > >Randy > > > > > > > Hi Randy > > I just took a look at User and am wondering what you couldn't achieve by > calling super(). Each of the properties have a getter, and the > constructor performs the setting. Is there a particular use case you > can't accomplish? I don't mind making them protected if needed, but I do > wonder if doing so would reduce the integrity of User, as the > constructor performs checks for non-null values etc. > > Best regards > Ben > > > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > digital self defense, top technical experts, no vendor pitches, > unmatched networking opportunities. Visit www.blackhat.com ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Acegisecurity-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
