Uploaded image for project: 'Spring Framework'
  1. Spring Framework
  2. SPR-3844

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

    Details

    • Type: New Feature
    • Status: Open
    • Priority: 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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                juergen.hoeller Juergen Hoeller
                Reporter:
                juergen.hoeller Juergen Hoeller
                Last updater:
                Juergen Hoeller
              • Votes:
                68 Vote for this issue
                Watchers:
                59 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Days since last comment:
                  5 years, 2 weeks, 3 days ago