Re: [Springframework-developer] Let's add Acegi-SEcurity's FilterToBeanProxy directly to Spring

[Colin S. <col...@ex...>]

I don't see that much choice in the matter, since the lifecycle of the 
Filter is clearly defined. Really it lives as a subset of the lifecycle 
of the webapp and associated appcontext.

But I have no problem with delaying. Anybody that really needs it can 
still use it by linking to Acegi, or ripping it out of the latter...


jürgen höller [werk3AT] wrote:

>Colin,
>
>Actually, I'd prefer to defer this till 1.1.2.
>
>There are a couple of design issues to discuss there, for example initialization of a javax.servlet.Filter bean in a Spring context: pass through the FilterConfig there from the filter proxy in web.xml? Who really drives the lifecycle of the target bean then?
>
>Anyway, please let's not add this on such short notice...
>
>Juergen
>
>
>-----Original Message-----
>From: spr...@li...
>[mailto:spr...@li...]On Behalf
>Of Colin Sampaleanu
>Sent: Monday, September 27, 2004 5:46 PM
>To: spr...@li...
>Subject: [Springframework-developer] Let's add Acegi-SEcurity's
>FilterToBeanProxy directly to Spring
>
>
>For about 2-3 months I've been meaning to but kept forgetting to add the 
>Acegi-Security project's FilterToBeanProxy to Spring itself, since it's 
>very useful for anybody doing filter-based stuff with Spring. Anybody 
>mind if I add it in for 1.1.1, even at this late stage?
>  
>http://www.jdocs.org/acegi/0.6/api/net/sf/acegisecurity/util/FilterToBeanProxy.html
>
>Both Ben and I originally worked on it. It's obviously working and well 
>tested.
>  
>