> Also, do you think this would be a correct to do: > > Have a User Interface with the three methods as existing in > the current User Object Create a DefaultUserImpl (same as the > existing User Object )for this interface for simple use cases. > > Users can then implement/extend this User Interface instead > of having to use the DefaultUserImpl. This way, you can > easily manage the password.
We'd need to be careful doing this. User is an object the majority of Acegi Security end users will be directly using via their custom DAO implementations. Having said that, it's easy enough to do. Just create a new UserDetails interface and make the existing User implement it. That way nobody's existing code will break. I'm not clear how managing the password would be easier in this situation? Ben ------------------------------------------------------- This SF.Net email is sponsored by: GNOME Foundation Hackers Unite! GUADEC: The world's #1 Open Source Desktop Event. GNOME Users and Developers European Conference, 28-30th June in Norway http://2004/guadec.org _______________________________________________ Acegisecurity-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
