Ray Krueger wrote:
I like the idea as well, my only question is (and I've been wondering
this for a while), why do we target the class and not the bean name?
<init-param>
<param-name>targetClass</param-name>
<param-value>net.sf.acegisecurity.FilterChain</param-value>
</init-param>
Instead of...
<init-param>
<param-name>targetBean</param-name>
<param-value>filterChain</param-value>
</init-param>
There's no strong reason Ray. It's just most webapps will only have one
instance of each class, so using class is a way of delivering better
documentation of what the filter is actually doing. This particularly
helps with support.
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
