AntUrlPathMatcher backwards compatibility

[stoicflame]

Finally got around to trying this out myself. I'm not seeing your error, but I am seeing a different error that was introduced with some recent changes that Luke made to spring security. This is what mine looks like:

java.lang.ClassCastException: org.springframework.beans.factory.config.RuntimeBeanReference cannot be cast to java.util.List
	at org.springframework.security.oauth.config.OAuthProviderBeanDefinitionParser.findFilterChain(OAuthProviderBeanDefinitionParser.java:190)
	at org.springframework.security.oauth.config.OAuthProviderBeanDefinitionParser.parse(OAuthProviderBeanDefinitionParser.java:167)

Can you verify that you've done a "clean install" from the project root? I'm wondering if you haven't compiled the changes in the parent pom and in the runtime library...

Currently in the process of figuring out the fix for the CCE. It would be nice if you could get to the point where you're reproducing what I'm seeing.

[raziel]

Hey, thanks, and sorry. I was missing the clean (I was just running mvn install).

And now I can reproduce the same issue you have.

So meanwhile I'll be working with 3.1.0.M2.

[stoicflame]

I just pushed a fix that incorporates the changes that Luke made to support multiple filter chains. All tests pass.

The only thing left to do before merging this branch is figuring out how to handle backwards compatability with 3.0.

[raziel]

Awesome! I just tried it.

So, if filter-chain-ref is not provided, and there are more than one filter chain then I uses the last one in the map?

This has always been the default behaviour, right?

That could explain why when I used the module in my project back in december it had a weird behaviour: I have more than one filter chain.

[stoicflame]

Yes, that's correct.