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

Messaging transaction integrations should use capability requirements

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Unresolved
    • Major
    • None
    • None
    • JMS
    • None

    Description

      Once WFLY-11166 and WFLY-11174 are complete the various messaging resources that create services that depend on the services associated with the new transactions and jca capabilities should themselves declare capabilities and add the needed capability requirements.

      These look to be the pooled connection factory resources and the jms bridge resources

      Attachments

        Issue Links

          is blocked by

          Sub-task - The sub-task of the issue WFLY-11166 Create capabilities for TransactionManager, UserTransaction and TransactionSynchronizationRegistry

          • 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

          Bug - A problem that impairs or prevents the functions of the product. WFLY-11174 TransactionIntegration should be exposed as a capability

          • 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.
          • Coding In Progress

          Activity

            People

              ehugonne1@redhat.com Emmanuel Hugonnet
              bstansbe@redhat.com Brian Stansberry
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: