Defines the resource-level transaction capabilities of Hibernate, centered around the org.hibernate.resource.transaction.spi.TransactionCoordinator contract.

An instance of TransactionCoordinator may be constructed using a org.hibernate.resource.transaction.spi.TransactionCoordinatorBuilder, which is a org.hibernate.service.Service and available via the org.hibernate.boot.registry.StandardServiceRegistry.

Resource-local transaction

A resource-local transaction is exposed to the application as an instance of org.hibernate.Transaction, allowing full control over the transaction lifecycle. That control flows from the Transaction into the TransactionCoordinator via its exposed org.hibernate.resource.transaction.spi.TransactionCoordinator.TransactionDriver.

Physical transaction

It is the underlying physical transaction which ultimately controls the database transaction. This might be:

• a JTA transaction, represented by a jakarta.transaction.Transaction or jakarta.transaction.UserTransaction, or
• a "JDBC transaction", as expressed via the JDBC java.sql.Connection.

The corresponding concrete implementations of TransactionCoordinator manage the necessary bridging.

Local Synchronization

The Hibernate transaction API allows the application itself to register JTA jakarta.transaction.Synchronization objects with the TransactionCoordinator. These local Synchronizations work in all transaction environments.

See org.hibernate.Transaction#registerSynchronization and org.hibernate.resource.transaction.spi.SynchronizationRegistry for additional details.