- All Known Subinterfaces:
- All Known Implementing Classes:
Note that savepoints can only work within an active transaction. Just use this programmatic savepoint handling for advanced needs; else, a subtransaction with PROPAGATION_NESTED is preferable.
This interface is inspired by JDBC's Savepoint mechanism but is independent of any specific persistence technology.
createSavepointCreate a new savepoint. You can roll back to a specific savepoint via
rollbackToSavepoint, and explicitly release a savepoint that you don't need anymore via
Note that most transaction managers will automatically release savepoints at transaction completion.
- a savepoint object, to be passed into
NestedTransactionNotSupportedException- if the underlying transaction does not support savepoints
TransactionException- if the savepoint could not be created, for example because the transaction is not in an appropriate state
- See Also:
rollbackToSavepointRoll back to the given savepoint.
The savepoint will not be automatically released afterwards. You may explicitly call
releaseSavepoint(Object)or rely on automatic release on transaction completion.
releaseSavepointExplicitly release the given savepoint.
Note that most transaction managers will automatically release savepoints on transaction completion.
Implementations should fail as silently as possible if proper resource cleanup will eventually happen at transaction completion.