That's really going to be fully dependent on your applications configuration.
Maybe break up your Spring xml files so that all the acegi stuff is in
it's own file. Then have your app load the right file based on the
environment you want.
The full file has all the normal Acegi stuff in it. The test
environment file would have one single bean in it:
On 9/14/07, Chris Berry <[EMAIL PROTECTED]> wrote:
> Greetings,
> I was wondering if there was a way to conveniently switch off all the Acegi
> Servlet Filters
> In testing we generally want to run over straight http
> And sometimes in Staging we just want to switch off SSL
> Today, I am using two different web.xml files; one w/ the Filters commented
> out, and the other not.
> And it is a PITA to switch back and forth (comment/uncomment) -- or I have
> to violate DRY and make copies of the "real" web.xml
>
> Is there some convenient way to tell Acegi just to "short-circuit" the
> FilterChainProxy??
> Using some kind of variable on startup??
>
> Thanks,
> -- Chris
>
>
> S'all good --- chriswberry at gmail dot com
>
>
>
>
> -
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
> ___
> Home: http://acegisecurity.org
> Acegisecurity-developer mailing list
> Acegisecurity-developer@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
>
>
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Home: http://acegisecurity.org
Acegisecurity-developer mailing list
Acegisecurity-developer@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
