[jboss-jira] [JBoss JIRA] (WFLY-1168) MDB is looking up UserTransaction even if it isn't Bean Managed
[
https://issues.jboss.org/browse/WFLY-1168?page=com.atlassian.jira.plugin....
]
Stuart Douglas commented on WFLY-1168:
--------------------------------------
It looks like this will not affect EAP 6.1 as far as I can tell.
Perosnally I would be ok with just backing out the commits that caused this. Even though
it is the spec behaviour it is not tested, and it does represent a backwards incompatible
change from EAP 6.1.
Otherwise JCA is going to have to come up with a different way to get the UserTransaction
other than looking it up from JNDI, such as getting it directly from the UserTransaction
service.
MDB is looking up UserTransaction even if it isn't Bean Managed
---------------------------------------------------------------
Key: WFLY-1168
URL: https://issues.jboss.org/browse/WFLY-1168
Project: WildFly
Issue Type: Feature Request
Reporter: Stefano Maestri
Assignee: Stuart Douglas
Investigating on a use case I've seen that MDB comes to
org.jboss.jca.adapters.jdbc.WrapperDataSource looking up for UT. It fails with this
exception
javax.naming.NamingException: JBAS014237: Only session and message-driven beans with
bean-managed transaction demarcation are allowed to access UserTransaction [Root exception
is java.lang.IllegalStateException: JBAS014237: Only session and message-driven beans with
bean-managed transaction demarcation are allowed to access UserTransaction]
the problem is exposed running
org.jboss.as.test.integration.ejb.mdb.MDBTestCase
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira