Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-2627

EJB container-transaction configuration with ejb-jar.xml leads to wrong transaction behavior

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 8.0.0.Alpha2
    • None
    • EJB, Transactions
    • None

      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 

         <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>

        1. arquillian-jpa.zip
          18 kB
        2. wildfly-src-7.2.0.Final-TransactionBug.patch
          3 kB

              dlloyd@redhat.com David Lloyd
              nbumm Norbert Bumm (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: