| org.springframework.transaction.PlatformTransactionManager
All known Subclasses: org.springframework.transaction.support.AbstractPlatformTransactionManager,
| Method Summary | |
| void | commit(TransactionStatus status)
Commit the given transaction, with regard to its status. | | TransactionStatus | getTransaction(TransactionDefinition definition)
Return 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 thrown 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. | | void | rollback(TransactionStatus status)
Perform 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. |
| commit | | void commit(TransactionStatus status) throws TransactionException(Code) | | Commit 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.
Parameters:
status - object returned by the getTransaction method
throws:
TransactionException - in case of commit or system errors
throws:
IllegalTransactionStateException - if the given transactionis already completed (that is, committed or rolled back)
See Also: TransactionStatus.setRollbackOnly |
| getTransaction | | TransactionStatus getTransaction(TransactionDefinition definition) throws TransactionException(Code) | | Return 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 thrown 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.
Parameters:
definition - TransactionDefinition instance (can be null for defaults),describing propagation behavior, isolation level, timeout etc. transaction status object representing the new or current transaction
throws:
TransactionException - in case of lookup, creation, or system errors
throws:
IllegalTransactionStateException - if the given transaction definitioncannot be executed (for example, if a currently active transaction is inconflict with the specified propagation behavior)
See Also: TransactionDefinition.getPropagationBehavior
See Also: TransactionDefinition.getIsolationLevel
See Also: TransactionDefinition.getTimeout
See Also: TransactionDefinition.isReadOnly |
| rollback | | void rollback(TransactionStatus status) throws TransactionException(Code) | | Perform 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.
Parameters:
status - object returned by the getTransaction method
throws:
TransactionException - in case of system errors
throws:
IllegalTransactionStateException - if the given transactionis already completed (that is, committed or rolled back) |
|
|