Ben Alex wrote:
For the small minority of people who have chosen NOT to extend User
(which goes against our recommendations, but there are legitimate
scenarios such as having a domain object that already represents the
user), I don't think adding two methods to their implementation is
going to cause much concern - especially as they can simply return false.
I have just written the two additional exceptions, events,
DaoAuthenticationProvider integration and
PasswordDaoAuthenticationProvider integration. I deprecated the old User
constructor. It's now all in CVS HEAD.
Best regards
Ben
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Home: http://acegisecurity.sourceforge.net
Acegisecurity-developer mailing list
Acegisecurity-developer@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
