The bridge requires a CamelContext. It will find the endpoint from the context. The bridge needs to be started
before being used. Be aware the the start method is asynchronous. You can use
start to be notified when the bridge has been started.

Inbound mapping

Inbound mapping associates a Camel endpoint to an event bus address. Messages received on this endpoint are
transformed to event bus messages.

The snippet above shows different ways to configure an inbound mapping:

you can configure the Camel endpoint either using the Endpoint object or its uri

you can disables the header copy (Camel message headers are copied to the event bus message)

you can uses publish instead of send to broadcast the message to all event bus consumers

you can configures the type of the event bus message body. If not set it uses the Camel message payload. If
sets, it looks in the Camel context for a converter between the Camel message payload and the desired type.

If send is used (so not publish), and when the Camel exchange expect a reply (In Out exchange), the Vert.x
code expect as reply to the sent message. When the reply arrives it is propagated to the exchange:

If when you send the message on the event bus you register a reply handler, it configures the Camel exchange to
expect a response (it uses the request-reply pattern of the EIP). The response is passed in the reply body. If the
route fails, you get a reply failure (recipient failure), with the message as cause: