On Mar 28, 2007, at 10:51 AM, Prasad Kashyap wrote:
Unfortunately, no :-(
hhmm...
On 3/28/07, David Blevins <[EMAIL PROTECTED]> wrote:
This is the same exclude issue as before. Should be fixed now.
I'm loving these tests you're writing....
-David
On Mar 27, 2007, at 8:20 PM, Prasad Kashyap wrote:
> I have an ejb-jar with 3 beans and a default interceptor with
wildcard
> "*" that applies to all beans.
>
> Problem 1:
> ---------------
>
> In FirstBean, I specify an @ExcludeDefault for a method. This
sticks.
> In SecondBean, I specify an <exclude-default-interceptor> for one
> method of the bean. It is ignored.
> In ThirdBean, I specify an <exclude-default-interceptor> for the
whole
> class. It is ignored.
Can you paste an example <exclude-default-interceptor> declaration?
The annotations are processed into the xml and the actual work is
done against the xml data, so I can't imagine a scenario where the
xml doesn't do it's job and the annotation does.
-David
>
>
> Problem 2:
> ---------------
> I now specify an @ExcludeDefaultInterceptor at the class level.
Only
> the lifecycle events are excluded. The methods calls are still
> intercepted.
>
>
> Cheers
> Prasad
>
