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
SPR-3844 Provide a "best efforts" 1PC transaction manager out of the box
DATACMNS-310 Integrate best-effort TransactionManager from Spring Data Neo4j
7 votes, 12 watchers
The text was updated successfully, but these errors were encountered:
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.