[
https://jira.jboss.org/browse/EJBTHREE-2120?page=com.atlassian.jira.plugi...
]
Carlo de Wolf updated EJBTHREE-2120:
------------------------------------
Description:
Current metadata resolving logic uses AOP advisor.resolveAnnotation on a method. Since the
method can be used both in a remote and local interface (via inheritance) we can't
differentiate properly and an override listed below fails:
<container-transaction>
<description>Never for method sameMethod on remote
intf</description>
<method>
<ejb-name>TxBean</ejb-name>
<method-intf>Remote</method-intf>
<method-name>sameMethod</method-name>
</method>
<trans-attribute>Never</trans-attribute>
</container-transaction>
<container-transaction>
<description>Mandatory for method sameMethod on local
intf</description>
<method>
<ejb-name>TxBean</ejb-name>
<method-intf>Local</method-intf>
<method-name>sameMethod</method-name>
</method>
<trans-attribute>Mandatory</trans-attribute>
</container-transaction>
Tx logic doesn't take method-intf type into acount
--------------------------------------------------
Key: EJBTHREE-2120
URL:
https://jira.jboss.org/browse/EJBTHREE-2120
Project: EJB 3.0
Issue Type: Bug
Components: transactions
Reporter: Carlo de Wolf
Fix For: bom-as6-0.1.3
Current metadata resolving logic uses AOP advisor.resolveAnnotation on a method. Since
the method can be used both in a remote and local interface (via inheritance) we can't
differentiate properly and an override listed below fails:
<container-transaction>
<description>Never for method sameMethod on remote
intf</description>
<method>
<ejb-name>TxBean</ejb-name>
<method-intf>Remote</method-intf>
<method-name>sameMethod</method-name>
</method>
<trans-attribute>Never</trans-attribute>
</container-transaction>
<container-transaction>
<description>Mandatory for method sameMethod on local
intf</description>
<method>
<ejb-name>TxBean</ejb-name>
<method-intf>Local</method-intf>
<method-name>sameMethod</method-name>
</method>
<trans-attribute>Mandatory</trans-attribute>
</container-transaction>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira