I had the same problem, but it was caused by myself. Actually I had
bound the same interceptor during for class level und method level
interception, like
bindInterceptor(any(), annotatedWith(Interceptors.class),
javaxInterceptor);
bindInterceptor(annotatedWith(Interceptors.class), any(),
javaxInterceptor);
If both - @Interceptors at class and method level - are found, the
interceptor is called twice. This could be solved by
bindInterceptor(any(), annotatedWith(Interceptors.class),
javaxInterceptor);
bindInterceptor(annotatedWith(Interceptors.class),
not(annotatedWith(Interceptors.class)), javaxInterceptor);
Maybe you made a similar mistake while configuring the interceptor?
On Sep 12, 2:06 pm, "Anthony MULLER" <
anthony.mul...@gmail.com> wrote:
> Hmmm... With debugger, when I looked to MethodInvocation instance given to
> invoke() method, I saw something quite strange.
>
> in the "proxy" field of "mi" (MethodInvocation instance), there are many
> "CGLIB$CALLBACK_" fields... Ok...
>
> BUT : I found two similars CGLIB$CALLBACK_0 and CGLIB$CALLBACK_1
>
> The target methods are respectively :
>
> public volatile com.xxx.MyObject
> com.xxx.MyObjectServiceImpl.createXXX(com.xxx.Session)
> public com.xxx.MyObject
> com.xxx.MyObjectServiceImpl.createXXX(com.xxx.Session)
>
> So, the same method is present twice, with just "volatile" as difference...
>
> Why???
>
> Another method into the same class doesn't have this behaviour (interceptor
> calling interceptor again calling the real method...)
>
> Regards,
> Anthony MÜLLER
>
> 2008/9/12 Anthony MULLER <
anthony.mul...@gmail.com>