Aug 1st, 2012, 11:10 AM
@Async versus RegexpMethodPointcutAdvisor
I'm using spring configuration that :
- intercepts some methods using @Async annotations
- intercepts the same methods using a RegexpMethodPointcutAdvisor using an home made interceptor registered with org.springframework.aop.framework.autoproxy.Defaul tAdvisorAutoProxyCreator
- intercepts the same methods using the same method (RegexpMethodPointcut...) in order to manage transaction (such as documentation explains to do).
I have many beans that matches RegexpMethodPointcutAdvisor patterns.
Some of them are intercepted whereas others only have @Async interception.
Is there a conflict between annotation interception and declaration interception ?
I'm using Spring 3.1.
Thanks for you
Tags for this Thread