Brandon Keepers wrote:
Is there a good reason for requiring constructor args instead of
setter methods for properties? I don't intend to start a flame war
about constructor vs. setter injection, but I do think the setters
should at least be an option, especially to be consistent with the
rest of the acegi configuration.
In the future more and more of Acegi Security will use constructor
injection for mandatory properties, and setter injection for optional
properties (optional meaning null is acceptable, or the class provides
an acceptable default). We are moving away from having invalid objects
and requiring InitializingBean to detect missing properties.
Best regards
Ben
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Home: http://acegisecurity.org
Acegisecurity-developer mailing list
Acegisecurity-developer@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
