Allow to disable default FinishesHandlingMessageBeforeHandlingNext about simplebus HOT 8 CLOSED

Sure, if you create a PR for this we can accept it.

from simplebus.

How does FinishesHandlingMessageBeforeHandlingNext forces the serialized commands? I'm not sure that's right.

from simplebus.

This is expected behaviour, if the command handler fails all commands that it has send should not be executed. It is developed like a transaction as the command handler fails all queries are reverted.

For us we have created a separate bus that does not has this middleware.

from simplebus.

The part of the problem is not even with failing but with successful exectution. Calling $bus->handle($command) we expect that command would be handled after call finishes. For async execution we utilize delayed commands with other async tooling, like rabbitmq or jms job queue bundle.

Currently nested calls to handle leads to situations when different machanisms work in a different flows. I.e we call $bus->handle($command) and then the call $eventDispatcher->dispatch($event). And listeners of this event a running at the point of time when $command is not handled yet (but the nature of the event expects it to be finished), so we have to disable this feature.

from simplebus.

I understand that this is intentional behaviour and it suits most of the users. I just ask to make it configurable (with enabled by default, of course, to keep BC)

from simplebus.

@cmodijk I've introduced the simplest solution in #52

from simplebus.

I'm closing this in favor of #52

from simplebus.

Btw there is no real need to close issues prematurely, as Fixes #xx construction will close it for you upon PR merging. Or leave it open for future if PR would pass the review.

from simplebus.