public class DatabaseEventFlusher extends AbstractEventFlusher
eventHandlers| Constructor and Description |
|---|
DatabaseEventFlusher() |
| Modifier and Type | Method and Description |
|---|---|
void |
afterSessionsFlush(CommandContext commandContext)
Called when the
Session have been successfully flushed. |
void |
closeFailure(CommandContext commandContext)
Called when the
CommandContext has not been successully closed due to an exception that happened. |
void |
closing(CommandContext commandContext)
Called when the
CommandContext is being closed, but no 'close logic' has been executed. |
addEventHandler, closed, getEventHandlers, setEventHandlerspublic void closing(CommandContext commandContext)
CommandContextCloseListenerCommandContext 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)public void afterSessionsFlush(CommandContext commandContext)
CommandContextCloseListenerSession 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)public void closeFailure(CommandContext commandContext)
CommandContextCloseListenerCommandContext 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.Copyright © 2016 Alfresco. All rights reserved.