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
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
or variation.
Thanks,
-- Chris
On Aug 21, 2007, at 9:20 PM, Chris Berry wrote:
Unfortunately, this package isn't well suited for extension.
I could extend PathBasedFilterInvocationDefinitionMap
but since it provides no way to access requestMap pathMatcher
I had to duplicate all of that code
Done
http://opensource.atlassian.com/projects/spring/browse/SEC-531
Cheers,
-- Chris
On Aug 23, 2007, at 1:44 PM, Chris Berry wrote:
Will do.
It sure would be nice to incorporate this back into Acegi.
IMHO, REST will (or is ;-) supplant all other web service
methodologies. Acegi should
Greetings,
I am trying to set up Acegi (using HTTP BASIC Auth) for a set of
RESTful web services (implemented using the Atom Publishing Protocol)
And I have the basic setup running.
But REST complicates matters because the exact same URL is used for
reads and writes, with the HTTP method
unclear how the Property Editors get
wired in...
Thanks,
-- Chris
On Aug 21, 2007, at 7:10 PM, Brian Moseley wrote:
On 8/21/07, Chris Berry [EMAIL PROTECTED] wrote:
Anyway, AFAICT, the solution is to provide a custom
FilterInvocationDefinitionSource
I plan to extend
