-
Bug
-
Resolution: Obsolete
-
Major
-
None
-
None
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>
- is related to
-
JBAS-7334 Drop AOP usage from EJB3
- Closed
-
AS7-905 Setting another transaction-attribute of a SERVICE_ENDPOINT and business view with the same interface class fails
- Resolved
-
EJBTHREE-2167 @TransactionAttribute declared in superclass is ignore & @TransactionAttribute conflict to Deployment Descriptor
- Open