You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
only the first handler for the RoomBooked event (OrderBeerOnRoomBooked) is executed, the output of the other handler is never visible. Upon interchanging them:
only the message from NewBookingsFinancialReport is displayed. From this observation I deduce that in the current implementation of EventGroupProcessors executes only the first handler for a specific event type and ignores all others.
The text was updated successfully, but these errors were encountered:
Any updates regarding this? 6 months later and it is still an issue, I spent some hours trying to figuring out why my code didn't work when it actually was the lib that returned after the first execution
Agree this would be a good change. The only workaround seems to be multiple handler groups but that can create a huge mess. If you have a domain with 10 events and need a second handler for 1 of them, you now have a group with 9 extra handlers returning nil just to ack messages. You can turn on AckOnUnknownEvent but that's a terrible idea since you have to turn it on for the entire processor.
When running the example basic/5-cqrs-protobuf, using the group handlers (
watermill v1.3.5
,watermill-amqp/v2 v2.1.0
)only the first handler for the RoomBooked event (OrderBeerOnRoomBooked) is executed, the output of the other handler is never visible. Upon interchanging them:
only the message from NewBookingsFinancialReport is displayed. From this observation I deduce that in the current implementation of EventGroupProcessors executes only the first handler for a specific event type and ignores all others.
The text was updated successfully, but these errors were encountered: