Carlos Sanchez wrote:
Using my proposed syntax each filter configuration can be separated in
different files and reused, furthermore there are many bean
definitions that can be bundled with acegi out of the box.
Spring is about using POJOs, avoiding complex hierarchies and interface implementations as it's done with EJB. It's a difference
between using Spring as a tool to help development or developing for Spring, which avoids reuse.
Carlos, let's say people were going to break their application out into
different IoC XMLs, and their application had different Filters they'd
like to load using this utility class. Let's also say we went with the
more consolidated syntax, ie someFilter=/*. People could easily achieve
separate XMLs containing their Filters by defining multiple
FilterToBeanProxy references in web.xml to separate "aggregator"
Filters. Alternatively, they could have one master "aggregator" Filter
which refers to child aggregator Filters in other IoC XML
configurations. After all, the aggregator is just another implementation
of Filter. As such I'm not sure how the consolidated syntax (which IMHO
is simpler and more attractive) represents a disadvantage. I'm open to
comments though.
Cheers
Ben
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Home: http://acegisecurity.sourceforge.net
Acegisecurity-developer mailing list
Acegisecurity-developer@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
