It looks like this is due to a change in the signature of registerAutoProxyCreatorIfNecessary() in Spring 2.5. The second argument is now of type Element rather than an Object.

The spring-security passes an Element to this method.

Is the solution to add a 'forwards compatible' method signiture to spring-aop-2.0.x ?

Here's a solution that uses reflection.

I tested this in my app that uses spring-2.5, and it gets past this point.

try {
Method method = AopNamespaceUtils.class.getMethod("registerAutoProxyCreatorIfNecessary",new Class[]{ParserContext.class, Element.class});
try {
method.invoke(null, new Object[] {parserContext, element});
}
catch (java.lang.IllegalAccessException e) { AopNamespaceUtils.registerAutoProxyCreatorIfNecessary(parserContext, element); }
catch (java.lang.reflect.InvocationTargetException e) { AopNamespaceUtils.registerAutoProxyCreatorIfNecessary(parserContext, element); } }
}
catch (NoSuchMethodException e) { AopNamespaceUtils.registerAutoProxyCreatorIfNecessary(parserContext, element); }

I've fixed this through reintroducing the Spring 2.0 registerAutoProxyCreatorIfNecessary and forceAutoProxyCreatorToUseClassProxying signatures in Spring 2.5.2.

So this should work fine now when compiling against Spring 2.0 and running on Spring 2.5. It should also work fine when compiling against Spring 2.5 and explicitly casting the source object to Object for picking the Spring 2.0 compatibility signature (instead of the Element one).

Juergen

that's great. thanks.