Uploaded image for project: 'ModeShape'
  1. ModeShape
  2. MODE-1498

Support JTA transactions

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Major
    • 3.0.0.Alpha5
    • 3.0.0.Alpha1
    • JCR, Transactions
    • None

    Description

      ModeShape 3 should support participating in (local and distributed) JTA transactions, allowing ModeShape repositories to be used within:

      • clients that explicitly manage user transactions (see Section 21.2 of the JSR-283 specification);
      • EJBs that use container-managed transactions; and
      • EJBs that use bean-managed transactions.

      Additionally, clients should be able to explicitly enlist a Session (i.e., a XAResource) with an XA transaction, and even allow a single Session to be used across multiple (sequential) transactions or multiple Sessions to be enlisted within a single transaction (see Section 21.4 of the JSR-283 specification).

      When a client enlists only a single ModeShape Session in a transaction, ideally only a single XAResource would be enlisted in the transaction so that transaction managers can optimize the 2PC across a single resource into a 1PC. This means that ideally ModeShape would not register both its own XAResource and Infinispan's XAResource.

      Attachments

        Issue Links

          is blocked by

          Task - Represents a small unit of work that is not end-user facing. MODE-1503 Test JTA support with XA transactions

          • 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

          Task - Represents a small unit of work that is not end-user facing. MODE-1504 Test container managed transactions

          • 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
          is related to

          Feature Request - Feature requests from customers and/or users MODE-1499 Provide JCA Resource Adapter

          • 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

          Sub-task - The sub-task of the issue MODE-1158 Implement XAResource for Session

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) MODE-1123 ModeShape should participate in local JTA transactions

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Activity

            People

              rhauch Randall Hauch (Inactive)
              rhauch Randall Hauch (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: