Carlos Sanchez wrote:
About the syntax, I looked at <map>, that would suit here, but Spring application context don't allow beans as keys, maybe a lack of
functionality?
Just use a custom PropertyEditor that works at a String level. The
PropertyEditor would identify name/value pairs, and create its own
internal Map. The name part of the pair would be a filter bean name that
could be looked up from the application context (sure, you lose XML
validation of the beans being present, but it's tolerable compared with
a more verbose and confusing syntax). The value part of the pair would
be the filter mapping. The filter mapping syntax is one to consider.
Most people seem to prefer Ant Paths, so this might be a more suitable
default (perhaps the only option?) than regular expressions. Remember
this new class will need to make the decision as to which filters to
delegate to. Also, I'd vote for it going into net.sf.acegisecurity.util,
where FilterToBeanProxy is located. What is the consensus?
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
