[
https://issues.jboss.org/browse/WFLY-1168?page=com.atlassian.jira.plugin....
]
Jesper Pedersen commented on WFLY-1168:
---------------------------------------
Resource adapters can only be configured using the standard Java types (java.lang.String,
java.lang.Integer, ...). We can look at how we can work around this inside AS in WildFly
8/9, and possibly add support for using TSR.
But it isn't a solution for EAP where the UT lookup must work.
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: Eduardo Martins
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