What happens when you dispatch a message to a message bus(es) depends on its

middlewares(and their order). By default, themiddlewares configured for each

bus looks like this.

collection of middleware(and their order). By default, themiddleware configured

for eachbus looks like this:

1. ``logging`` middleware. Responsible of logging the beginning and the end of the

message within the bus.

2. _Your ownmiddlewares__

2. _Your owncollection ofmiddleware__

3. ``route_messages`` middleware. Will route the messages your configured to their

corresponding sender and stop the middleware chain.

4. ``call_message_handler`` middleware. Will call the message handler(s) for the

given message.

Adding your ownmiddlewares

Adding your ownmiddleware

As described in the component documentation, you can add your ownmiddlewares

As described in the component documentation, you can add your ownmiddleware

within the buses to add some extra capabilities like this:

..code-block::yaml

Note that if the service is abstract, then a child service will be created per bus.

Disabling defaultmiddlewares

Disabling defaultmiddleware

If you don't want the defaultmiddlewaresto be present on your bus, you can disable

them like this:

If you don't want the defaultcollection of middlewareto be present on your bus,

you can disablethem like this:

..code-block::yaml

Your own Transport