Application server-specific integration

Spring的事务抽象通常与应用程序服务器无关。此外,Spring的 JtaTransactionManager 类(可以选择执行 JTA UserTransactionTransactionManager 对象的 JNDI 查找)自动检测后者的位置,后者因应用程序服务器而异。访问 JTA TransactionManager 可增强事务语义——特别是支持事务挂起。有关详细信息,请参阅https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/transaction/jta/JtaTransactionManager.html[JtaTransactionManager] javadoc。

Spring’s transaction abstraction is generally application server-agnostic. Additionally, Spring’s JtaTransactionManager class (which can optionally perform a JNDI lookup for the JTA UserTransaction and TransactionManager objects) autodetects the location for the latter object, which varies by application server. Having access to the JTA TransactionManager allows for enhanced transaction semantics — in particular, supporting transaction suspension. See the JtaTransactionManager javadoc for details.

Spring 的 JtaTransactionManager 是在 Jakarta EE 应用程序服务器上运行的标准选择,并且已知可在所有常见服务器上运行。高级功能(例如事务挂起)也可以在多个服务器上使用(包括 GlassFish、JBoss 和 Geronimo),而无需任何特殊配置。

Spring’s JtaTransactionManager is the standard choice to run on Jakarta EE application servers and is known to work on all common servers. Advanced functionality, such as transaction suspension, works on many servers as well (including GlassFish, JBoss and Geronimo) without any special configuration required.