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.

> -----Original Message-----
> From: bryan ( [EMAIL PROTECTED]) <[EMAIL PROTECTED]>
> Date: Wed, 26 Jan 2005 15:37:11 +0000
> Subject: Re: [Acegisecurity-developer] Reducing the number of 
> filters needed in web.xml
> To: acegisecurity-developer@lists.sourceforge.net
> 
> 
> .................. a *lot* more verbose.
> 
> We already use the syntax that I suggested for the security 
> roles and it is perfectly adequate.
> 
> I find that an extremely convoluted solution. Remember that 
> people also have to configure another 20 or so XML files for 
> the average web app these days.
> 
> XML is not a magic hammer, we don't want to end up with 
> another STRUTS at the end of this.
> 
> --b
> 
> 
> On Tue, 25 Jan 2005 23:28:31 +0100, Carlos Sanchez 
> <[EMAIL PROTECTED]> wrote:
> > To sum up,
> >
> > I'll create a class called 
> net.sf.acegisecurity.FilterChain, with a property called filters.
> >
> > 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?
> >
> > If we use this one we lose validation, so another option could be:
> >
> > <bean id="filterMapping" abstract="true" 
> class="net.sf.acegisecurity.FilterMapping">
> >     <property name="mapping"><value>/*</value></property>
> > </bean>
> >
> > <bean id="channelProcessingFilterMapping" parent="filterMapping">
> >     <property name="filter"><ref 
> > local="channelProcessingFilter"/></property>
> > </bean>
> >
> > <bean id="authenticationProcessingFilterMapping" 
> parent="filterMapping">
> >     <property name="filter"><ref 
> > local="authenticationProcessingFilter"/></property>
> > </bean>
> >
> > <bean id="filterChain" class="net.sf.acegisecurity.FilterChain">
> >     <property name="filters">
> >         <list>
> >             <ref local="channelProcessingFilterMapping"/>
> >             <ref local="authenticationProcessingFilterMapping"/>
> >         </list>
> >     </property>
> > </bean>
> >
> > More verbose, sure, but allows validation and avoids 
> parsing and it's unlikely to change from one app to another.
> > If you are using XML you should avoid parsing text, that's 
> the goal of XML. The problem is that Spring DTD is a bit verbose.
> >
> > On Mon, 24 Jan 2005 11:15:03 +1100, Ben Alex 
> <[EMAIL PROTECTED]> wrote:
> > > bryan ( [EMAIL PROTECTED]) wrote:
> > >
> > > >
> > > ><bean id="filterChain" class="net.sf.acegisecurity.FilterChain">
> > > >
> > > ><property name="filters">
> > > >        <value>
> > > >            channelProcessingFilter=/*
> > > >            authenticationProcessingFilter=/*
> > > >            basicProcessingFilter=/*
> > > >            sessionIntegrationFilter=/*
> > > >            securityEnforcementFilter=/*
> > > >        </value>
> > > >    </property>
> > > >
> > > ></bean>
> > > >
> > > >
> > > >
> > > >
> > > +1, especially using the syntax shown above as it's nice 
> and intuitive.
> > >
> > >
> > > -------------------------------------------------------
> > > 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
> > >
> >
> > -------------------------------------------------------
> > 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
> >
> 
> -------------------------------------------------------
> 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
> 




-------------------------------------------------------
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

Reply via email to