On Mar 15, 2007, at 12:22 PM, Prasad Kashyap wrote:
This ? http://rifers.org/paste/show/3951
Oh, ok! I meant the "other" bean class... yea that's the ticket! :-
P Ok, so maybe I need some glasses. :)
The funny thing is I was thinking "Where is the interceptor stack
declared, should be in the bean class... I'll know more if I can see
that"
Anyway, now I realize the @AroundInvoke is *on* the bean class, which
is fine, but technically you don't have any interceptors to exclude.
The bean itself doesn't count as an interceptor and can't exclude
itself via @Exclude(Class|Default)Interceptors or add itself via
@Interceptors.
If you throw the @AroundInvoke in another class (even an inner class
of the bean) and tack it onto the bean with an @Interceptors
({MyInterceptor.class}) then it can be excluded.
-David
Cheers
Prasad
On 3/15/07, David Blevins <[EMAIL PROTECTED]> wrote:
On Mar 15, 2007, at 11:30 AM, Prasad Kashyap wrote:
> This is my bean class. http://rifers.org/paste/show/3951
> getContextData() is annotated with the @ExcludeClassInterceptors
tag.
>
> This is my itest file http://rifers.org/paste/show/3953
> test02_excludeClassInterceptors() fails.
Hmm... Can you post the bean class too?
-David
>
> Cheers
> Prasad
>
