[DATAGRAPH-256] Move ChainedTransactionManager from Spring Data Neo4j to Spring Framework Created: 22/Jan/12  Updated: 02/Sep/17  Resolved: 02/Sep/17

Status: Closed
Project: Spring Data Neo4j
Component/s: CORE
Affects Version/s: None
Fix Version/s: None

Type: Refactoring Priority: Minor
Reporter: Andrei Tuzhilin Assignee: Unassigned
Resolution: Won't Fix Votes: 7
Labels: transactions
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relate
relates to SPR-3844 Provide a "best efforts" 1PC transact... Open
relates to DATACMNS-310 Integrate best-effort TransactionMana... Closed
Last updater: Nicolas Mervaillie

 Description   

The ChainedTransactionManager from the Spring Data Neo4j project (in package org.springframework.data.neo4j.transaction) is a viable option for any application using multiple data sources without the option to use XA transactions (e.g., Tomcat Servlet container environment or performance wise).

It's also very useful to add some annotation-based support to define chained transaction order.



 Comments   
Comment by Donnchadh O Donnabhain [ 19/Jun/12 ]

See also SPR-3844 .

Comment by Chris Beams [ 19/Jun/12 ]

Moved this issue to DATAGRAPH so the team there can evaluate the idea and then get in touch with the SPR team if they see fit.

Comment by Giovanni Botta [ 04/Apr/13 ]

Does this class work with Spring 3? Thanks!

Comment by Donnchadh O Donnabhain [ 05/Apr/13 ]

It seems to be built against Spring 3.1 but I haven't tried it myself.

Comment by Andrei Tuzhilin [ 05/Apr/13 ]

It works with 3.1 and 3.2

It has a major bug though, see https://jira.springsource.org/browse/DATAGRAPH-191

Comment by Nicolas Mervaillie [ 02/Sep/17 ]

In order to give users a better vision of what’s happening on SDN, we are bulk closing several issues because they are no more relevant, or related to old and un-maintained SDN versions.
We tried to keep the issues that are still relevant, like feature requests that are still absent from SDN. However, some may have been closed by error. If so, please feel free to reopen.

Generated at Fri Nov 15 02:33:13 UTC 2019 using Jira 7.13.8#713008-sha1:1606a5c1e7006e1ab135aac81f7a9566b2dbc3a6.