Norbert Bumm created WFLY-2627: ---------------------------------- Summary: EJB container-transaction configuration with ejb-jar.xml leads to wrong transaction behavior Key: WFLY-2627 URL: https://issues.jboss.org/browse/WFLY-2627 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB, Transactions Environment: jdk1.7.0_45_x64, Windows 7 Reporter: Norbert Bumm Assignee: David Lloyd If there is a global transaction declaration for “Supports” and a “Required” declaration for a specific Method the “Required” gets ignored. I first encountered the problem with an old 2.1 EJB, but the problem is also there with a 3.1 EJB with deployment descriptor. It works correct with annotations. ejb-jar.xml snippet {code:xml} <container-transaction> <method> <ejb-name>UserDAOImpl</ejb-name> <method-name>*</method-name> </method> <trans-attribute>Supports</trans-attribute> </container-transaction> <container-transaction> <method> <ejb-name>UserDAOImpl</ejb-name> <method-intf>Local</method-intf> <method-name>createUser</method-name> </method> <trans-attribute>Required</trans-attribute> </container-transaction> {code} -- 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