Uploaded image for project: 'JBoss Transaction Manager'
  1. JBoss Transaction Manager
  2. JBTM-1699

Changes to the transaction SPI

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Unresolved
    • Major
    • None
    • None
    • Application Server Integration
    • None

    Description

      wildfly is using a number of our internal com.arjuna interfaces which we would like to resolve by providing the same functionality in the transactions SPI.
      Additionally the current SPI contains a number of unused classes which need removing.

      I have created https://github.com/jbosstm/jboss-transaction-spi to manage the changes. To avoid any potential confusion and to make it clear who is responsible for the SPI we will be changing the package names.

      Attachments

        Issue Links

          incorporates

          Enhancement - An enhancement or refactoring of existing functionality JBTM-1641 EAP 6.1 CNFE org.jboss.tm.TxManager (from Module org.jboss.jboss-transaction-spi:main)

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JBTM-1970 SPI additions for enlisting XA resources

          • 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
          relates to

          Feature Request - Feature requests from customers and/or users JBTM-1558 Prune redundant code from jboss-transaction-spi

          • Optional - The request should be considered desirable but is not an immediate necessity.
          • Open

          Feature Request - Feature requests from customers and/or users JBTM-1556 provide way for Synchronization.afterCompletion callee to know if the Reaper thread is calling

          • 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

            Public project attachment banner

              context keys: [headless, issue, helper, isAsynchronousRequest, project, action, user]
              current Project key: JBTM

              People

                rhn-engineering-mmusgrov Michael Musgrove
                rhn-engineering-mmusgrov Michael Musgrove
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:

                  Time Tracking

                    Estimated:
                    Original Estimate - 1 week, 3 days
                    1w 3d
                    Remaining:
                    Remaining Estimate - 1 week, 3 days
                    1w 3d
                    Logged:
                    Time Spent - Not Specified
                    Not Specified