简体繁体 English

Neo4j + Jotm迁移，缺少事务的类/接口

[英]Neo4j + Jotm migration, absent transaction's classes/interfaces

原文 2015-04-16 13:57:55 4 1 neo4j/ spring-data-neo4j/ data-migration/ transactional/ jotm

I'm using Neo4j 1.8.9 + Jotm with ALRubinger's solution : How to enlist XAResource with existing Transaction? 我正在将Neo4j 1.8.9 + Jotm与ALRubinger的解决方案一起使用：如何使用现有的Transaction征募XAResource？ , everything working fine, but few days ago I started migration to Neo4j 2.2.1 and came across to the next problem - neo4j-kernel.jar have no more: TransactionManagerProvider,AbstractTransactionManager,TransactionStateFactory etc. ，一切正常，但是几天前我开始迁移到Neo4j 2.2.1，遇到了下一个问题-neo4j-kernel.jar不再有： TransactionManagerProvider，AbstractTransactionManager，TransactionStateFactory等。

The classes was deleted from 2.1.8 version, I'm tried to use Spring Data Neo4j » 3.3.0.RELEASE but they use neo4j-kernel 2.1.7 and it's the same implementation that i had before. 这些类已从2.1.8版本中删除，我尝试使用Spring Data Neo4j»3.3.0.RELEASE，但是它们使用neo4j-kernel 2.1.7，这与我以前的实现相同。

Where did they moved all the classes/interfaces? 他们将所有的类/接口移到了哪里？ Another jar? 另一个罐子？ More simple solution? 更简单的解决方案？

1 个解决方案

JTA as a internal implementation detail has been removed in Neo4j, quoting from the release notes : 从发行说明中引用，Neo4j中已删除了JTA作为内部实现的详细信息：

The use of separate transactions logs for the graph and the indexes, co-ordinated by an XA system, has been replaced by a singular transactional management and one unified transaction log. 由XA系统协调的图形和索引使用单独的事务日志，已由单个事务管理和一个统一的事务日志取代。 This substantially reduces resource overhead and improves scalability. 这大大减少了资源开销并提高了可伸缩性。 Note that as result of this, the previously exposed XA and JTA functionalities have been removed. 请注意，其结果是，先前公开的XA和JTA功能已被删除。