Spring Framework
  1. Spring Framework
  2. SPR-3844

Provide a "best efforts" 1PC transaction manager out of the box

    Details

    • Type: New Feature New Feature
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: General Backlog
    • Component/s: Transaction
    • Labels:
      None
    • Last commented by a User:
      true

      Description

      There have been detailed discussions about a "best efforts" transaction strategy that allows any number of local resource transactions to be part of a single Spring-managed transaction. Spring 2.0 already supports synchronized local JMS transactions in that style; this issue is effectively about extending that approach to all of Spring's supported resources.

      Important 'side' features are commit ordering and customizable transaction logging (see SPR-3311). This JIRA issue (together with SPR-3311) serves for tracking requirements, suggestions and contributions, as well as the status of the "best efforts" transaction manager implementation in Spring.

        Issue Links

          Activity

          Hide
          Giovanni Botta added a comment -

          This seems to be working fine, however a major bug was reported: https://jira.springsource.org/browse/DATAGRAPH-191

          Show
          Giovanni Botta added a comment - This seems to be working fine, however a major bug was reported: https://jira.springsource.org/browse/DATAGRAPH-191
          Hide
          Oliver Gierke added a comment -

          I've just fixed the bug in DATAGRAPH-191 and moved the transaction manager implementation into Spring Data Commons as it is not strictly tied to graph database scenarios. We're going to deprecate the class in Neo4j for the next major release and remove it in the next but one release.

          Show
          Oliver Gierke added a comment - I've just fixed the bug in DATAGRAPH-191 and moved the transaction manager implementation into Spring Data Commons as it is not strictly tied to graph database scenarios. We're going to deprecate the class in Neo4j for the next major release and remove it in the next but one release.
          Hide
          Giovanni Botta added a comment -

          Thanks Oliver. Which Spring release will this be included with?

          Show
          Giovanni Botta added a comment - Thanks Oliver. Which Spring release will this be included with?
          Hide
          Oliver Gierke added a comment - - edited

          It will not be in Spring in the first place (although it might be considered for the 4.0 timeframe). We'll see it in Spring Data Commons 1.6 M1, scheduled for end of May. The relevant ticket is here: DATACMNS-310.

          The bugfix will already released with Spring Data Graph as part of the Spring Data Arora SR1 release due this week.

          Show
          Oliver Gierke added a comment - - edited It will not be in Spring in the first place (although it might be considered for the 4.0 timeframe). We'll see it in Spring Data Commons 1.6 M1, scheduled for end of May. The relevant ticket is here: DATACMNS-310 . The bugfix will already released with Spring Data Graph as part of the Spring Data Arora SR1 release due this week.
          Hide
          Giovanni Botta added a comment -

          I didn't realize Spring Data Commons was a separate projects. Thanks

          Show
          Giovanni Botta added a comment - I didn't realize Spring Data Commons was a separate projects. Thanks

            People

            • Assignee:
              Juergen Hoeller
              Reporter:
              Juergen Hoeller
              Last updater:
              Giovanni Botta
            • Votes:
              63 Vote for this issue
              Watchers:
              55 Start watching this issue

              Dates

              • Created:
                Updated:
                Days since last comment:
                1 year, 3 days ago