Package org.activiti.engine.impl.interceptor

Interface CommandContextCloseListener

All Known Subinterfaces:
EventFlusher
All Known Implementing Classes:
AbstractEventFlusher, AsyncJobAddedNotification, DatabaseEventFlusher, FailedJobListener, TransactionCommandContextCloseListener, VerifyDeserializedObjectCommandContextCloseListener
@Internal public interface CommandContextCloseListener
A listener that can be used to be notified of lifecycle events of the CommandContext.

  • Method Details

    • closing

      void closing(CommandContext commandContext)
      Called when the CommandContext is being closed, but no 'close logic' has been executed. At this point, the TransactionContext (if applicable) has not yet been committed/rolledback and none of the Session instances have been flushed. If an exception happens and it is not caught in this method: - The Session instances will *not* be flushed - The TransactionContext will be rolled back (if applicable)

    • afterSessionsFlush

      void afterSessionsFlush(CommandContext commandContext)
      Called when the Session have been successfully flushed. When an exception happened during the flushing of the sessions, this method will not be called. If an exception happens and it is not caught in this method: - The Session instances will *not* be flushed - The TransactionContext will be rolled back (if applicable)

    • closed

      void closed(CommandContext commandContext)
      Called when the CommandContext is successfully closed. At this point, the TransactionContext (if applicable) has been successfully committed and no rollback has happened. All Session instances have been closed. Note that throwing an exception here does *not* affect the transaction. The CommandContext will log the exception though.

    • closeFailure

      void closeFailure(CommandContext commandContext)
      Called when the CommandContext has not been successully closed due to an exception that happened. Note that throwing an exception here does *not* affect the transaction. The CommandContext will log the exception though.