[DATACMNS-310] Integrate best-effort TransactionManager from Spring Data Neo4j Created: 12/Apr/13  Updated: 09/Sep/13  Resolved: 31/May/13

Status: Closed
Project: Spring Data Commons
Component/s: Core
Affects Version/s: None
Fix Version/s: 1.6 M1

Type: New Feature Priority: Major
Reporter: Oliver Drotbohm Assignee: Oliver Drotbohm
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relate
is related to SPR-3844 Provide a "best efforts" 1PC transact... Open
is related to DATAGRAPH-256 Move ChainedTransactionManager from S... Closed
Last updater: Trevor Marshall

 Comments   
Comment by Giovanni Botta [ 31/May/13 ]

When is this going to be released and available in maven?

Comment by Oliver Drotbohm [ 04/Jun/13 ]

1.6 M1 release is already built and available in the milestone repositories. Note, that the relevant Neo4j module version hasn't been released yet and the release made is not officially announced yet.

Comment by Giovanni Botta [ 10/Jul/13 ]

Thank you Oliver, one more question: which Maven dependency do I need in order to have the ChainedTransactionManager only? Trying to keep my dependencies slim

Comment by Oliver Drotbohm [ 11/Jul/13 ]

Spring Data Commons 1.6 M1 or better. Actually, the purpose of this ticket was to remove the need to depend on the Neo4j module just to get access to the ChainedTranctionManager. The class itself only depends on spring-tx in turn so if you're not using anything else but this class you can probably exclude some of the additional dependencies we rely on transitively for other stuff.

Comment by Giovanni Botta [ 25/Jul/13 ]

Hello again,
one last question: is the ChainedTransactionManager supposed to be a singleton? Can I have multiple instances managing transactions in different threads?
Thanks

Generated at Sat Nov 23 01:22:03 UTC 2019 using Jira 7.13.8#713008-sha1:1606a5c1e7006e1ab135aac81f7a9566b2dbc3a6.