This callback does not mean that the transaction will actually be committed. A rollback decision can still occur after this method has been called. This callback is rather meant to perform work that's only relevant if a commit still has a chance to happen, such as flushing SQL statements to the database.
Note that exceptions will get propagated to the commit caller and cause a rollback of the transaction. @param readOnly whether the transaction is defined as read-only transaction @throws RuntimeException in case of errors; will be propagated to the caller(note: do not throw TransactionException subclasses here!) @see #beforeCompletion
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|