On Mar 16, 2007, at 2:06 PM, Prasad Kashyap wrote:
Thanx.
On that count, then we are having a problem with this kinda
interception too.
The interception from a superclass (both bean's and interceptor's) is
not being invoked.
Let me post the patch soon. Continue to use the same JIRA ?
Right, as I mentioned we don't support that yet. Well, we didn't. I
went and fixed it after you posted. Just checked it in.
It turns out we do have an issue of some sort with exclusions.
Fixing that now.
Who needs a TCK when we've got you! :) Great work!
-David
Cheers
Prasad
On 3/16/07, David Blevins <[EMAIL PROTECTED]> wrote:
On Mar 16, 2007, at 11:27 AM, Prasad Kashyap wrote:
> May I please draw your attention to section 12.3.1 of the ejb-core
> spec. The section is titled, "Multiple Business Method Interceptor
> Methods"
>
> After reading bullets 2 and 4, I can conclude that an interceptor's
> superclass @AroundInvoke method is first invoked after which the
> interceptor's @AroundInvoke method is invoked. Am I right ?
>
> Next, it is also my understanding that you do not have to
explicitly
> list the interceptor's superclass in the @Interceptors({})
annotation.
> If the child interceptor is listed, then any superclass
interceptor is
> automatically invoked. Is that a correct understanding ?
Right on both counts. An exception is when the child class overrides
the super class's AroundInvoke method (same with PostCreate,
PreDestroy, PrePassivate and PrePassivate), in which case the super
class's method is then "disabled" and now not invoked as part of the
chain. We don't actually support that yet, but we need to.
-David
