Uploaded image for project: 'WildFly Transaction Client'
  1. WildFly Transaction Client
  2. WFTC-13

Client does not verify transaction availability where JTA-CDI requires IllegalStateException

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • None
    • 1.0.0.Beta7
    • None
    • Hide

      Running Narayana cdi integration test - e.g. ConcurrentTransactionalTest

      cd ArjunaJTA/cdi
      mvn test -Parq -Dtest=ConcurrentTransactionalTest
      
      Show
      Running Narayana cdi integration test - e.g. ConcurrentTransactionalTest cd ArjunaJTA/cdi mvn test -Parq -Dtest=ConcurrentTransactionalTest

      It seems that the transactional client does not fully follow the JTA specification regarding CDI integration. Test in Narayana currently show divergence from

      3.7 Transactional Annotation:
      If an attempt is made to call any method of the UserTransaction interface from within the scope of a bean or method annotated with @Transactional and a Transactional.TxType other than NOT_SUPPORTED or NEVER, an IllegalStateException must be thrown.

      What I can see there is difference between prior transaction spi and the new one in checking availability of transaction.
      https://github.com/jbosstm/jboss-transaction-spi/blob/master/src/main/java/org/jboss/tm/usertx/client/ServerVMClientUserTransaction.java#L216
      vs.
      https://github.com/wildfly/wildfly-transaction-client/blob/master/src/main/java/org/wildfly/transaction/client/LocalUserTransaction.java#L59

              ochaloup@redhat.com Ondrej Chaloupka (Inactive)
              ochaloup@redhat.com Ondrej Chaloupka (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: