concept bridge in category mule

This is an excerpt from Manning's book Mule in Action, Second Edition.
Bridge— Directly connects an inbound endpoint to an outbound endpoint
You’ve learned how to build services. It’s just a matter of time before you need to connect two endpoints to share services; for example, you might need to create an API layer to expose internal services to the world, like the ones you created. Or perhaps you might want to wrap a legacy CSV service for JSON support by adding some transformation and adaptation to the bridge.
To simplify the connection of systems, Mule 3 introduced the bridge pattern. The name can’t be more explicit: It’s a bridge that connects an inbound endpoint to an outbound endpoint. No more, no less.
The simplest form of bridge that configures the name, inboundAddress, and outboundAddress will set a request-response conduit and will behave synchronously between its endpoints; any response coming from the outbound endpoint will be routed back to the inbound endpoint. The following listing illustrates such a synchronous bridge.