Yeah, I don't see any particular value in having classes for each event - I am just trying to be make things as similar as possible with the ORM.

Interestingly I also found the event classes in commons (ttps://github.com/doctrine/common/tree/master/lib/Doctrine/Common/Persistence/Event) but I thought it would have been strange to use them as they talk about Entities and use `->getObjectManager()`. I don't know if at somepoint in the future all of the Doctrine projects will use ObjectManager as a standard.

Actually, I just had a quick look at the ORM events and there is some differentiating logic between the various non-lifecycle events, whereas currently we do not have any differentiating logic, `onClear`, `onFlush`, `postFlush` and `preFlush` are basically the same. So +1 for dropping them. We can subclass the replacement (hmm - UnitOfWorkEvent?, DocumentManagerEvent?)