backward compatibility broken with 1.2 RC2

[sjivan]

I'm using Acegi 0.8.1 that uses the method

org.springframework.util.PathMatcher#match(String path, String url)

In versions of Spring 1.2 RC1 and below this was an abstract class with a static method but in Spring 1.2 RC2 this has been changed to an interface and as a result I get a runtime exception.

<Apr 19, 2005 8&#58;49&#58;55 AM EDT> <Error> <HTTP> <BEA-101020> <&#91;ServletContext&#40;id=11283772,name=tbr,context-path=/tbr&#41;&#93; Serv
let failed with Exception
java.lang.IncompatibleClassChangeError
        at net.sf.acegisecurity.intercept.web.PathBasedFilterInvocationDefinitionMap.lookupAttributes&#40;PathBasedFilterInv
ocationDefinitionMap.java&#58;116&#41;
        at net.sf.acegisecurity.intercept.web.AbstractFilterInvocationDefinitionSource.getAttributes&#40;AbstractFilterInvoc
ationDefinitionSource.java&#58;47&#41;
        at net.sf.acegisecurity.util.FilterChainProxy.doFilter&#40;FilterChainProxy.java&#58;165&#41;
        at net.sf.acegisecurity.util.FilterToBeanProxy.doFilter&#40;FilterToBeanProxy.java&#58;125&#41;
        at weblogic.servlet.internal.FilterChainImpl.doFilter&#40;FilterChainImpl.java&#58;27&#41;
        at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run&#40;WebAppServletContext.java&#58;6356&#41;
        at weblogic.security.acl.internal.AuthenticatedSubject.doAs&#40;AuthenticatedSubject.java&#58;317&#41;
        at weblogic.security.service.SecurityManager.runAs&#40;SecurityManager.java&#58;118&#41;
        at weblogic.servlet.internal.WebAppServletContext.invokeServlet&#40;WebAppServletContext.java&#58;3635&#41;
        at weblogic.servlet.internal.ServletRequestImpl.execute&#40;ServletRequestImpl.java&#58;2585&#41;
        at weblogic.kernel.ExecuteThread.execute&#40;ExecuteThread.java&#58;197&#41;
        at weblogic.kernel.ExecuteThread.run&#40;ExecuteThread.java&#58;170&#41;

Sanjiv

[Ben Alex]

This has been fixed in Acegi Security CVS. Release 0.8.2 will be released in the next 24 hours to correct this issue with Spring 1.2-RC2.