接口 TransactionSynchronization

    • 字段概要

      字段 
      修饰符和类型字段说明
      static intSTATUS_COMMITTED
      Completion status in case of proper commit.
      static intSTATUS_ROLLED_BACK
      Completion status in case of proper rollback.
      static intSTATUS_UNKNOWN
      Completion status in case of heuristic mixed completion or system errors.
    • 方法概要

      所有方法 实例方法 默认方法 
      修饰符和类型方法说明
      default voidafterCommit()
      Invoked after transaction commit.
      default voidafterCompletion​(int status)
      Invoked after transaction commit/rollback.
      default voidbeforeCommit​(boolean readOnly)
      Invoked before transaction commit (before "beforeCompletion").
      default voidbeforeCompletion()
      Invoked before transaction commit/rollback.
      default voidflush()
      Flush the underlying session to the datastore, if applicable: for example, a Hibernate/JPA session.
      default voidresume()
      Resume this synchronization.
      default voidsuspend()
      Suspend this synchronization.
    • 方法详细资料

      • beforeCommit

        default void beforeCommit​(boolean readOnly)
        Invoked before transaction commit (before "beforeCompletion"). Can e.g. flush transactional O/R Mapping sessions to the database.

        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.

        参数:
        readOnly - whether the transaction is defined as read-only transaction
        抛出:
        RuntimeException - in case of errors; will be propagated to the caller (note: do not throw TransactionException subclasses here!)
        另请参阅:
        beforeCompletion()
      • beforeCompletion

        default void beforeCompletion()
        Invoked before transaction commit/rollback. Can perform resource cleanup before transaction completion.

        This method will be invoked after beforeCommit, even when beforeCommit threw an exception. This callback allows for closing resources before transaction completion, for any outcome.

        抛出:
        RuntimeException - in case of errors; will be logged but not propagated (note: do not throw TransactionException subclasses here!)
        另请参阅:
        beforeCommit(boolean), afterCompletion(int)
      • afterCommit

        default void afterCommit()
        Invoked after transaction commit. Can perform further operations right after the main transaction has successfully committed.

        Can e.g. commit further operations that are supposed to follow on a successful commit of the main transaction, like confirmation messages or emails.

        NOTE: The transaction will have been committed already, but the transactional resources might still be active and accessible. As a consequence, any data access code triggered at this point will still "participate" in the original transaction, allowing to perform some cleanup (with no commit following anymore!), unless it explicitly declares that it needs to run in a separate transaction. Hence: Use PROPAGATION_REQUIRES_NEW for any transactional operation that is called from here.

        抛出:
        RuntimeException - in case of errors; will be propagated to the caller (note: do not throw TransactionException subclasses here!)
      • afterCompletion

        default void afterCompletion​(int status)
        Invoked after transaction commit/rollback. Can perform resource cleanup after transaction completion.

        NOTE: The transaction will have been committed or rolled back already, but the transactional resources might still be active and accessible. As a consequence, any data access code triggered at this point will still "participate" in the original transaction, allowing to perform some cleanup (with no commit following anymore!), unless it explicitly declares that it needs to run in a separate transaction. Hence: Use PROPAGATION_REQUIRES_NEW for any transactional operation that is called from here.

        参数:
        status - completion status according to the STATUS_* constants
        抛出:
        RuntimeException - in case of errors; will be logged but not propagated (note: do not throw TransactionException subclasses here!)
        另请参阅:
        STATUS_COMMITTED, STATUS_ROLLED_BACK, STATUS_UNKNOWN, beforeCompletion()