Re: [Acegisecurity-developer] (no subject)

2008-12-22 Thread Burt Beckwith
That's the correct URL for the core, https://src.springframework.org/svn/spring-security/branches/2.0.x-branch is the url for the whole branch. There's a SSL certificate mismatch - that's probably confusing your client. I use Eclipse and it prompted me to keep the mismatched certificate and

Re: [Acegisecurity-developer] (no subject)

2007-08-23 Thread Chris Berry
I managed to answer this one myself, by trolling the Internet and reading the Acegi source. The final answer was to create a RESTfulDefinitionSource. I used Spring constructor injection to load in the security patterns: bean id=filterInvocationInterceptor

Re: [Acegisecurity-developer] (no subject)

2007-08-23 Thread Ray Krueger
Nice work Chris, any chance you could open some Jiras on that? On 8/23/07, Chris Berry [EMAIL PROTECTED] wrote: I managed to answer this one myself, by trolling the Internet and reading the Acegi source. The final answer was to create a RESTfulDefinitionSource. I used Spring constructor

Re: [Acegisecurity-developer] (no subject)

2007-08-23 Thread Chris Berry
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

Re: [Acegisecurity-developer] (no subject)

2007-08-23 Thread Ray Krueger
Agreed :) And thanks! On 8/23/07, Chris Berry [EMAIL PROTECTED] wrote: 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

Re: [Acegisecurity-developer] (no subject)

2007-08-21 Thread Chris Berry
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. But I could workaround that, what I don't see is how to get around the

Re: [Acegisecurity-developer] (no subject)

2004-08-24 Thread Tim Kettering
Yes, that would work. Thanks. -tim Hi Tim Yes, the design does require the DAO provider know how to interpret the presented AclObjectIdentity. As you know, JdbcDaoImpl (and any BasicAclDao for that matter) needs to be able to create BasicAclEntry[]s in response to the DAO request. Each

Re: [Acegisecurity-developer] (no subject)

2004-08-17 Thread Ben Alex
[EMAIL PROTECTED] wrote: Hello ! I am new to this framework, I have changed the default queries in net.sf.acegisecurity.providers.dao.jdbc.jdbcDaoImpl, and now I want to compile the project again. I guess it should be a simple task to use ant build but It seems that with the distribution file