Understanding PROPAGATION_NESTED PROPAGATION_NESTED uses a single physical transaction with multiple savepoints that it can roll back to. Such partial rollbacks let an inner transaction scope trigger a rollback transaction despite some operations having been rolled back. This setting is typically mapped onto JDBC savepoints, so it works only with JDBC resource transactions. See Spring’s DataSourceTransactionManager. getConnection and can therefore be used in any case. The DataSourceTransactionManager class supports savepoints (PROPAGATION_NESTED), custom isolation levels, and timeouts that get applied as appropriate JDBC

Connection if "doBegin" fails * DataSourceTransactionManager manages nested transactions via JDBC 3.0 Savepoints * DataSourceTransactionObject implements SavepointManager to allow for savepoint management via HibernateTransactionManager and JdoTransactionManager allow to manage nested transactions via JDBC 3.0 Savepoints * SessionFactoryUtils and PersistenceManagerFactoryUtils log error on cleanup failure rather than

Connection if "doBegin" fails * DataSourceTransactionManager manages nested transactions via JDBC 3.0 Savepoints * DataSourceTransactionObject implements SavepointManager to allow for savepoint management via HibernateTransactionManager and JdoTransactionManager allow to manage nested transactions via JDBC 3.0 Savepoints * SessionFactoryUtils and PersistenceManagerFactoryUtils log error on cleanup failure rather than

Connection if "doBegin" fails * DataSourceTransactionManager manages nested transactions via JDBC 3.0 Savepoints * DataSourceTransactionObject implements SavepointManager to allow for savepoint management via HibernateTransactionManager and JdoTransactionManager allow to manage nested transactions via JDBC 3.0 Savepoints * SessionFactoryUtils and PersistenceManagerFactoryUtils log error on cleanup failure rather than

Connection if "doBegin" fails * DataSourceTransactionManager manages nested transactions via JDBC 3.0 Savepoints * DataSourceTransactionObject implements SavepointManager to allow for savepoint management via HibernateTransactionManager and JdoTransactionManager allow to manage nested transactions via JDBC 3.0 Savepoints * SessionFactoryUtils and PersistenceManagerFactoryUtils log error on cleanup failure rather than

Connection if "doBegin" fails * DataSourceTransactionManager manages nested transactions via JDBC 3.0 Savepoints * DataSourceTransactionObject implements SavepointManager to allow for savepoint management via HibernateTransactionManager and JdoTransactionManager allow to manage nested transactions via JDBC 3.0 Savepoints * SessionFactoryUtils and PersistenceManagerFactoryUtils log error on cleanup failure rather than

Connection if "doBegin" fails * DataSourceTransactionManager manages nested transactions via JDBC 3.0 Savepoints * DataSourceTransactionObject implements SavepointManager to allow for savepoint management via HibernateTransactionManager and JdoTransactionManager allow to manage nested transactions via JDBC 3.0 Savepoints * SessionFactoryUtils and PersistenceManagerFactoryUtils log error on cleanup failure rather than

Connection if "doBegin" fails * DataSourceTransactionManager manages nested transactions via JDBC 3.0 Savepoints * DataSourceTransactionObject implements SavepointManager to allow for savepoint management via HibernateTransactionManager and JdoTransactionManager allow to manage nested transactions via JDBC 3.0 Savepoints * SessionFactoryUtils and PersistenceManagerFactoryUtils log error on cleanup failure rather than

Connection if "doBegin" fails * DataSourceTransactionManager manages nested transactions via JDBC 3.0 Savepoints * DataSourceTransactionObject implements SavepointManager to allow for savepoint management via HibernateTransactionManager and JdoTransactionManager allow to manage nested transactions via JDBC 3.0 Savepoints * SessionFactoryUtils and PersistenceManagerFactoryUtils log error on cleanup failure rather than

Connection if "doBegin" fails * DataSourceTransactionManager manages nested transactions via JDBC 3.0 Savepoints * DataSourceTransactionObject implements SavepointManager to allow for savepoint management via HibernateTransactionManager and JdoTransactionManager allow to manage nested transactions via JDBC 3.0 Savepoints * SessionFactoryUtils and PersistenceManagerFactoryUtils log error on cleanup failure rather than