]
Stuart Douglas resolved AS7-4586.
---------------------------------
Resolution: Done
CLONE - ejbPassivate method is not called when it's defined in a
superclass
---------------------------------------------------------------------------
Key: AS7-4586
URL:
https://issues.jboss.org/browse/AS7-4586
Project: Application Server 7
Issue Type: Bug
Components: EJB
Affects Versions: 7.1.1.Final
Reporter: Ondřej Chaloupka
Assignee: Stuart Douglas
Fix For: 7.1.2.Final-redhat1
In case that ejbPassivate (or ejbActivate etc.) method is defined in a superclass than
it's not invoked on passivation event.
I suppose that this is slightly related to JBPAPP-8540 but in this case the method from
parent class should be invoked. It's mentioned in EJB3 4.9.3
{quote}
Compatibility Note: If the PostConstruct lifecycle callback interceptor method is the
ejbCreate method, if the PreDestroy lifecycle callback interceptor method is the ejbRemove
method, if the PostActivate lifecycle callback interceptor method is the ejbActivate
method, or if the PrePassivate lifecycle callback interceptor method is the ejbPassivate
method, these callback methods must be implemented on the bean class itself (or on its
superclasses). Except for these cases, the method names can be arbitrary, but must not
start with "ejb" to avoid conflicts with the callback methods defined by the
javax.ejb.EnterpriseBean interfaces.
{quote}
Please check my test:
https://github.com/ochaloup/jboss-as/commit/ab1e4f27565e5c8989aa16a45a0f3...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: