Class SpringHibernateTransactionOperations
- All Implemented Interfaces:
- SynchronousTransactionManager<org.hibernate.Session>,- TransactionManager,- TransactionOperations<org.hibernate.Session>
- Since:
- 1.0.0
- Author:
- graemerocher
- 
Method SummaryModifier and TypeMethodDescriptionvoidcommit(TransactionStatus<org.hibernate.Session> status) Commit the given transaction, with regard to its status.<R> Rexecute(TransactionDefinition definition, TransactionCallback<org.hibernate.Session, R> callback) Execute a transaction within the context of the function.Optional<? extends TransactionStatus<?>>Find optional propagated transaction status.org.hibernate.SessionObtains the connection for the current transaction.TransactionStatus<org.hibernate.Session>getTransaction(TransactionDefinition definition) Return a currently active transaction or create a new one, according to the specified propagation behavior.booleanCheck if the connection exists.voidrollback(TransactionStatus<org.hibernate.Session> status) Perform a rollback of the given transaction.Methods inherited from class java.lang.Objectclone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, waitMethods inherited from interface io.micronaut.transaction.TransactionOperationsexecuteRead, executeWrite
- 
Method Details- 
findTransactionStatusDescription copied from interface:TransactionOperationsFind optional propagated transaction status.- Specified by:
- findTransactionStatusin interface- TransactionOperations<org.hibernate.Session>
- Returns:
- The transaction status.
 
- 
getConnectionpublic org.hibernate.Session getConnection()Description copied from interface:TransactionOperationsObtains the connection for the current transaction.- Specified by:
- getConnectionin interface- TransactionOperations<org.hibernate.Session>
- Returns:
- The connection
 
- 
hasConnectionpublic boolean hasConnection()Description copied from interface:TransactionOperationsCheck if the connection exists.- Specified by:
- hasConnectionin interface- TransactionOperations<org.hibernate.Session>
- Returns:
- True if transaction exists
 
- 
executepublic <R> R execute(TransactionDefinition definition, TransactionCallback<org.hibernate.Session, R> callback) Description copied from interface:TransactionOperationsExecute a transaction within the context of the function.- Specified by:
- executein interface- TransactionOperations<org.hibernate.Session>
- Type Parameters:
- R- The result
- Parameters:
- definition- The transaction definition
- callback- The call back
- Returns:
- The result
 
- 
getTransactionpublic TransactionStatus<org.hibernate.Session> getTransaction(TransactionDefinition definition) throws TransactionException Description copied from interface:SynchronousTransactionManagerReturn a currently active transaction or create a new one, according to the specified propagation behavior.Note that parameters like isolation level or timeout will only be applied to new transactions, and thus be ignored when participating in active ones. Furthermore, not all transaction definition settings will be supported by every transaction manager: A proper transaction manager implementation should throw an exception when unsupported settings are encountered. An exception to the above rule is the read-only flag, which should be ignored if no explicit read-only mode is supported. Essentially, the read-only flag is just a hint for potential optimization. - Specified by:
- getTransactionin interface- SynchronousTransactionManager<org.hibernate.Session>
- Parameters:
- definition- the TransactionDefinition instance (can be- nullfor defaults), describing propagation behavior, isolation level, timeout etc.
- Returns:
- transaction status object representing the new or current transaction
- Throws:
- TransactionException- in case of lookup, creation, or system errors
- IllegalTransactionStateException- if the given transaction definition cannot be executed (for example, if a currently active transaction is in conflict with the specified propagation behavior)
- See Also:
 
- 
commitDescription copied from interface:SynchronousTransactionManagerCommit the given transaction, with regard to its status. If the transaction has been marked rollback-only programmatically, perform a rollback.If the transaction wasn't a new one, omit the commit for proper participation in the surrounding transaction. If a previous transaction has been suspended to be able to create a new one, resume the previous transaction after committing the new one. Note that when the commit call completes, no matter if normally or throwing an exception, the transaction must be fully completed and cleaned up. No rollback call should be expected in such a case. If this method throws an exception other than a TransactionException, then some before-commit error caused the commit attempt to fail. For example, an O/R Mapping tool might have tried to flush changes to the database right before commit, with the resulting DataAccessException causing the transaction to fail. The original exception will be propagated to the caller of this commit method in such a case. - Specified by:
- commitin interface- SynchronousTransactionManager<org.hibernate.Session>
- Parameters:
- status- object returned by the- getTransactionmethod
- Throws:
- UnexpectedRollbackException- in case of an unexpected rollback that the transaction coordinator initiated
- HeuristicCompletionException- in case of a transaction failure caused by a heuristic decision on the side of the transaction coordinator
- TransactionSystemException- in case of commit or system errors (typically caused by fundamental resource failures)
- IllegalTransactionStateException- if the given transaction is already completed (that is, committed or rolled back)
- TransactionException- if something goes wrong during commit
- See Also:
 
- 
rollbackDescription copied from interface:SynchronousTransactionManagerPerform a rollback of the given transaction.If the transaction wasn't a new one, just set it rollback-only for proper participation in the surrounding transaction. If a previous transaction has been suspended to be able to create a new one, resume the previous transaction after rolling back the new one. Do not call rollback on a transaction if commit threw an exception. The transaction will already have been completed and cleaned up when commit returns, even in case of a commit exception. Consequently, a rollback call after commit failure will lead to an IllegalTransactionStateException. - Specified by:
- rollbackin interface- SynchronousTransactionManager<org.hibernate.Session>
- Parameters:
- status- object returned by the- getTransactionmethod
- Throws:
- TransactionSystemException- in case of rollback or system errors (typically caused by fundamental resource failures)
- IllegalTransactionStateException- if the given transaction is already completed (that is, committed or rolled back)
- TransactionException- if something goes wrong during rollback
 
 
-