Uploaded image for project: 'Application Server 3 4 5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-3060

classes calling TxManager.getInstance instead of using the locator

    XMLWordPrintable

Details

    Description

      The following classes are calling TxManager.getInstance to obtain a TransactionManager instead of using TransactionManagerLocator.getInstance().locate(). This prevents alternative TransactionManagers from being used.

      testsuite/src/main/org/jboss/test/jca/test/AbstractPoolingStressTest.java
      testsuite/src/main/org/jboss/test/jca/test/PoolingUnitTestCase.java
      testsuite/src/main/org/jboss/test/jca/test/XATxConnectionManagerUnitTestCase.java
      testsuite/src/main/org/jboss/test/tm/test/AbstractTransactionLocalStressTest.java
      testsuite/src/main/org/jboss/test/tm/test/TransactionLocalUnitTestCase.java
      testsuite/src/main/org/jboss/test/txtimer/test/TimedMockObject.java
      testsuite/src/main/org/jboss/test/txtimer/test/TransactionalTimerTestCase.java

      Attachments

        Issue Links

          is related to

          Task - Represents a small unit of work that is not end-user facing. JBTM-46 Register JIRA issues on AS 4.0.3SP1

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              adrian.brock Adrian Brock (Inactive)
              kconner@redhat.com Kevin Conner (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: