]
jaikiran pai commented on EJBTHREE-1937:
----------------------------------------
This appears to be a bug in your application code. Let's continue this discussion in
your forum thread. Closing this one
@PostConstruct methods on Multiple default inceptors are not all
called
-----------------------------------------------------------------------
Key: EJBTHREE-1937
URL:
https://jira.jboss.org/jira/browse/EJBTHREE-1937
Project: EJB 3.0
Issue Type: Bug
Environment: OS: Linux kernel 2.6, jdk-1.6.0_13, JBoss [The Oracle] 5.1.0.GA
(build: SVNTag=JBoss_5_1_0_GA date=200905221634)
Reporter: Debasish Ray Chawdhuri
Assignee: jaikiran pai
Attachments: DemoEJB.jar, LoggingInterceptors.jar
It is clearly stated in the EJB 3.0 spec that there can be multiple default interceptors
specified for a single ejb-jar. (Section 12.8.2.1) . It is also written there that the
inceptor methods are invoked in that order (as in the ejb-jar.xml) (section 12.4.1:
Multiple Callback Interceptor Methods for a Life Cycle Callback Event) ["Default
interceptors are invoked in the order of their specification in the deployment
descriptor"] which means there can be multiple default interceptors with callback for
the same life-cycle event.
Now in JBoss, if multiple default interceptors are specified and all of them have
@PostConstruct specified (regardless of whether annotation or deployment descriptor is
used), only the first one specified in ejb-jar.xml is called and the rest are ignored (not
invoked). The problem also persisted in JBoss 5.0.1 GA.
However, the @AroundInvoke methods work just fine (All of them are called in proper
order)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: