[
https://issues.jboss.org/browse/AS7-5331?page=com.atlassian.jira.plugin.s...
]
Dominik Pospisil edited comment on AS7-5331 at 8/10/12 4:21 AM:
----------------------------------------------------------------
Yes, exactlly, CMT bean. That is what I was trying to say - you can have CMT bean and yet
use @Resource UserTransaction interface and execute method on it successfuly.
TransactionIIOPInvocationTestCase not only shows that you can inject UserTransaction into
CMT bean but also you can actually use it.
was (Author: dpospisil):
Yes, exactlly, CMT bean. That is what I was trying to say - you can have CMT bean and
yet use @Resource UserTransaction interface and execute method on it successfuly.
@Resource UserTransaction should not be allowed in CMT beans
------------------------------------------------------------
Key: AS7-5331
URL:
https://issues.jboss.org/browse/AS7-5331
Project: Application Server 7
Issue Type: Bug
Components: EJB, Transactions
Affects Versions: 7.1.2.Final (EAP)
Reporter: Dominik Pospisil
Assignee: jaikiran pai
Currently, it seems then @Resource UserTransaction injection is allowed in CMT beans and
injects
container managed transaction. In AS/EAP5 this would throw an exception which I think is
correct as
this violates EJB 3.0 & 3.1 specs.
Section 16.12 of the EJB 3.1 specification says:
The container must make the UserTransaction interface available to the enterprise beans
that are
allowed to use this interface (only session and message-driven beans with bean-managed
transaction
demarcation are allowed to use this interface) either through injection using the
Resource annotation
or in JNDI under the name java:comp/UserTransaction, in addition to through the
EJBContext
interface. The authenticationType and shareable elements of the Resource annotation
must not be specified.
In my interpretation the statement "only session and message-driven beans with
bean-managed transaction
demarcation are allowed to use this interface" would mean that other beans are
prohibited to use this
interface. Allowing such beans to use this interface is specification violation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira