The Unit Of Work pattern is a common pattern in enterprise application architectures.
It implements the concept of an "application transaction" that keeps track of:
- dirty objects
- new objects
- removed objects
Read more about it in Martin Fowlers Patterns of Enterprise Application Architecture.
The user implement listeners that allows him to add additional behaviour when specific events are triggered, such as begin, commit, rollback, dispose etc. All listeners must implement that
The Unit Of Work will not commit until all listeners have agreed on that. If for example on listener have set the transaction to rollBackOnly then the whole Unit Of Work transaction will rollback.