I used UOW::getIdentityMap for collecting messages because any loaded entity might issue messages.

Consider a classic DDD example. AddOrderItem command is being handled. An Aggregate Root Order is retrieved from its repository. Order::addItem() method is called and an item is added to the incapsulated Item[] collection. OrderItemAdded event is recorded. In this case the aggregate root Order has not changed from the Doctrine POV, so it's not in the $uow->getScheduledEntityUpdates() array. That's why we need to check all managed entities by iterating over the identity map.

After a discussion with @weaverryan , I added an event hook EntityMessagePreDispatchEvent. It allows to add custom stamps to the dispatched message.

@Nyholm , @sroze , @weaverryan , looking forward to your reviews :-)

I like this PR, but you took my ideas* and improved the implementation =)

I would like to see a review from @ruudk or @sroze.

* my ideas: The ideas that I took from Simplebus.

@Nyholm Even though I'm maintainer of SimpleBus I never used this functionality with SimpleBus. It was already there when I joined. Therefore I cannot really review this functionality.

@sroze , any news about this PR?

Perhaps @weaverryan can help us figure out what to do here?

I’m using this in a project and just noticed something: when an entity is deleted, its messages won’t be recorded

I’m using this in a project and just noticed something: when an entity is deleted, its messages won’t be recorded

I tried collecting the message recording entities on the preFlush events but I’m having trouble accessing entities that are scheduled for removal because they became orphaned

I’ve moved the message recording into the entities' collection owner for now

@vudaltsov can you check out the comment from @mathroc about the delete problem? I don't know the internals, but possibly we need to grab the entity map before flush, store it on a property, then in postFlush() merge those entities with the entity map at that moment to get a full list?

We've just moved away from master as the main branch to use 5.x instead. Unfortunately, I cannot reopen the PR and change the target branch to 5.x. Can you open a new PR referencing this one to not loose the discussion? Thank you for your understanding and for your help.