Vadim Pesochinskiy wrote:

IMH Acegi needs a facade bean, which would administer wiring and setting up default behaviour.

We try to use sensible defaults (implemented in the Java classes) to minimise XML where possible.

A variety of approaches are available to further reduce XML configuration:

- Use a BeanPostProcessor
- Make beans BeanFactoryAware, using DefaultListableBeanFactory to find likely collaborators and wire them
- Use autowiring and inner beans more often
- Use abstract beans as per Craig Walls' approach


I actually prefer Craig's approach. Abstract beans are a standard Spring capability, and people who invest time in learning it receive benefits beyond Acegi Security. I believe the other approaches obfuscate the configuration source, which will increase difficulty when customising configuration or troubleshooting. However, I invite people who wish to write contributions that adopt these alternative approaches to submit them for inclusion in the project.

Cheers
Ben


------------------------------------------------------- This SF.Net email is sponsored by: New Crystal Reports XI. Version 11 adds new functionality designed to reduce time involved in creating, integrating, and deploying reporting solutions. Free runtime info, new features, or free trial, at: http://www.businessobjects.com/devxi/728 _______________________________________________ Home: http://acegisecurity.sourceforge.net Acegisecurity-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer

Reply via email to