[[vertx-component]]
= Vert.x Component
//THIS FILE IS COPIED: EDIT THE SOURCE FILE:
:page-source: components/camel-vertx/src/main/docs/vertx-component.adoc
:docTitle: Vert.x
:artifactId: camel-vertx
:description: Send and receive messages to/from Vert.x Event Bus.
:since: 2.12
:supportLevel: Stable
:component-header: Both producer and consumer are supported
include::{cq-version}@camel-quarkus:ROOT:partial$reference/components/vertx.adoc[opts=optional]

*Since Camel {since}*

*{component-header}*

The Vert.x component is for working with the http://vertx.io/[Vertx]
https://vertx.io/docs/vertx-core/java/#event_bus[EventBus].

The vertx https://vertx.io/docs/vertx-core/java/#event_bus[EventBus]
sends and receives JSON events.

[NOTE]
====
The version of Vert.x, used by the component, requires at least Java 1.8 at
runtime.
====

Maven users will need to add the following dependency to their `pom.xml`
for this component:

[source,xml]
------------------------------------------------------------
<dependency>
    <groupId>org.apache.camel</groupId>
    <artifactId>camel-vertx</artifactId>
    <version>x.x.x</version>
    <!-- use the same version as your Camel core version -->
</dependency>
------------------------------------------------------------

== URI format

[source,java]
---------------------------
vertx:channelName[?options]
---------------------------

== Options



// component options: START
The Vert.x component supports 9 options, which are listed below.



[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
| *host* (common) | Hostname for creating an embedded clustered EventBus |  | String
| *port* (common) | Port for creating an embedded clustered EventBus |  | int
| *timeout* (common) | Timeout in seconds to wait for clustered Vertx EventBus to be ready. The default value is 60. | 60 | int
| *vertx* (common) | *Autowired* To use the given vertx EventBus instead of creating a new embedded EventBus |  | Vertx
| *vertxOptions* (common) | Options to use for creating vertx |  | VertxOptions
| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. | false | boolean
| *autowiredEnabled* (advanced) | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | boolean
| *vertxFactory* (advanced) | To use a custom VertxFactory implementation |  | VertxFactory
|===
// component options: END




// endpoint options: START
The Vert.x endpoint is configured using URI syntax:

----
vertx:address
----

with the following path and query parameters:

=== Path Parameters (1 parameters):


[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
| *address* | *Required* Sets the event bus address used to communicate |  | String
|===


=== Query Parameters (6 parameters):


[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
| *pubSub* (common) | Whether to use publish/subscribe instead of point to point when sending to a vertx endpoint. |  | Boolean
| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
| *exceptionHandler* (consumer) | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. |  | ExceptionHandler
| *exchangePattern* (consumer) | Sets the exchange pattern when the consumer creates an exchange. There are 3 enums and the value can be one of: InOnly, InOut, InOptionalOut |  | ExchangePattern
| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. | false | boolean
| *synchronous* (advanced) | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | boolean
|===
// endpoint options: END



Whether to use publish/subscribe instead of point to
point when sending to a vertx endpoint.

-----------------------------------------------------------------------------------------------
You can append query options to the URI in the following format, ?option=value&option=value&...
-----------------------------------------------------------------------------------------------

== Connecting to the existing Vert.x instance

If you would like to connect to the Vert.x instance already existing in
your JVM, you can set the instance on the component level:

[source,java]
-----------------------------------------------------
Vertx vertx = ...;
VertxComponent vertxComponent = new VertxComponent();
vertxComponent.setVertx(vertx);
camelContext.addComponent("vertx", vertxComponent);
-----------------------------------------------------


include::{page-component-version}@camel-spring-boot::page$vertx-starter.adoc[]
