Mark St Godard wrote:
Does it make sense for this to be refactored to have a single
AuthenticationFailureEvent...(class or interface) with the 7 subclasses or
implementors?
i.e.
AuthenticationEvent
AuthenticationSuccessEvent extends AuthenticationEvent
AuthenticationFailureEvent extends AuthenticationEvent
(all auth fail events subclass above OR make an interface
(marker perhaps) for AuthenticationFailureEvent ?)
Hi Mark
I went with a common abstract superclass, AuthenticationFailureEvent.
Now in CVS.
Cheers
Ben
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Home: http://acegisecurity.sourceforge.net
Acegisecurity-developer mailing list
Acegisecurity-developer@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
