Hazelcast
Since Camel 2.7
The hazelcast- component allows you to work with the Hazelcast distributed data grid / cache. Hazelcast is a in memory data grid, entirely written in Java (single jar). It offers a great palette of different data stores like map, multi map (same key, n values), queue, list and atomic number. The main reason to use Hazelcast is its simple cluster support. If you have enabled multicast on your network you can run a cluster with hundred nodes with no extra configuration. Hazelcast can simply configured to add additional features like n copies between nodes (default is 1), cache persistence, network configuration (if needed), near cache, eviction and so on. For more information consult the Hazelcast documentation on http://www.hazelcast.com/docs.jsp.
Hazelcast components
See the following for usage of each component:
- Hazelcast Atomic Number
-
Increment, decrement, set, etc. Hazelcast atomic number (a grid wide number).
- Hazelcast Instance
-
Consume join/leave events of a cache instance in a Hazelcast cluster.
- Hazelcast List
-
Perform operations on Hazelcast distributed list.
- Hazelcast Map
-
Perform operations on Hazelcast distributed map.
- Hazelcast Multimap
-
Perform operations on Hazelcast distributed multimap.
- Hazelcast Queue
-
Perform operations on Hazelcast distributed queue.
- Hazelcast Replicated Map
-
Perform operations on Hazelcast replicated map.
- Hazelcast Ringbuffer
-
Perform operations on Hazelcast distributed ringbuffer.
- Hazelcast SEDA
-
Asynchronously send/receive Exchanges between Camel routes running on potentially distinct JVMs/hosts backed by Hazelcast BlockingQueue.
- Hazelcast Set
-
Perform operations on Hazelcast distributed set.
- Hazelcast Topic
-
Send and receive messages to/from Hazelcast distributed topic.
Installation
Maven users will need to add the following dependency to their pom.xml
for this component:
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-hazelcast</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel core version -->
</dependency>
Using hazelcast reference
By its name
<bean id="hazelcastLifecycle" class="com.hazelcast.core.LifecycleService"
factory-bean="hazelcastInstance" factory-method="getLifecycleService"
destroy-method="shutdown" />
<bean id="config" class="com.hazelcast.config.Config">
<constructor-arg type="java.lang.String" value="HZ.INSTANCE" />
</bean>
<bean id="hazelcastInstance" class="com.hazelcast.core.Hazelcast" factory-method="newHazelcastInstance">
<constructor-arg type="com.hazelcast.config.Config" ref="config"/>
</bean>
<camelContext xmlns="http://camel.apache.org/schema/spring">
<route id="testHazelcastInstanceBeanRefPut">
<from uri="direct:testHazelcastInstanceBeanRefPut"/>
<setHeader name="CamelHazelcastOperationType">
<constant>put</constant>
</setHeader>
<to uri="hazelcast-map:testmap?hazelcastInstanceName=HZ.INSTANCE"/>
</route>
<route id="testHazelcastInstanceBeanRefGet">
<from uri="direct:testHazelcastInstanceBeanRefGet" />
<setHeader name="CamelHazelcastOperationType">
<constant>get</constant>
</setHeader>
<to uri="hazelcast-map:testmap?hazelcastInstanceName=HZ.INSTANCE"/>
<to uri="seda:out" />
</route>
</camelContext>
By instance
<bean id="hazelcastInstance" class="com.hazelcast.core.Hazelcast"
factory-method="newHazelcastInstance" />
<bean id="hazelcastLifecycle" class="com.hazelcast.core.LifecycleService"
factory-bean="hazelcastInstance" factory-method="getLifecycleService"
destroy-method="shutdown" />
<camelContext xmlns="http://camel.apache.org/schema/spring">
<route id="testHazelcastInstanceBeanRefPut">
<from uri="direct:testHazelcastInstanceBeanRefPut"/>
<setHeader name="CamelHazelcastOperationType">
<constant>put</constant>
</setHeader>
<to uri="hazelcast-map:testmap?hazelcastInstance=#hazelcastInstance"/>
</route>
<route id="testHazelcastInstanceBeanRefGet">
<from uri="direct:testHazelcastInstanceBeanRefGet" />
<setHeader name="CamelHazelcastOperationType">
<constant>get</constant>
</setHeader>
<to uri="hazelcast-map:testmap?hazelcastInstance=#hazelcastInstance"/>
<to uri="seda:out" />
</route>
</camelContext>
Configuring HazelcastInstance on component
You can also configure the hazelcast instance on the component which will then be used by all hazelcast endpoints.
In the example above we setup this for the hazelcast map component and setup hazelcast via verbose <bean>
configurations.
<bean id="config" class="com.hazelcast.config.Config">
<constructor-arg type="java.lang.String" value="HZ.INSTANCE" />
<propety name="networkConfig" ref="myNetworkConfig"/>
</bean>
<bean id="myNetworkConfig" class="com.hazelcast.config.NetworkConfig">
<propety name="port">1234</propety>
</bean>
<bean id="myHazelcastInstance" class="com.hazelcast.core.Hazelcast" factory-method="newHazelcastInstance">
<constructor-arg type="com.hazelcast.config.Config" ref="config"/>
</bean>
<bean id="hazelcast" class="org.apache.camel.component.hazelcast.map.HazelcastMapComponent">
<propety name="hazelcastInstance" ref="myHazelcastInstance"/>
</bean>
Publishing hazelcast instance as an OSGI service
If operating in an OSGI container and you would want to use one instance of hazelcast across all bundles in the same container. You can publish the instance as an OSGI service and bundles using the cache al need is to reference the service in the hazelcast endpoint.
Bundle A create an instance and publishes it as an OSGI service
<bean id="config" class="com.hazelcast.config.FileSystemXmlConfig">
<argument type="java.lang.String" value="${hazelcast.config}"/>
</bean>
<bean id="hazelcastInstance" class="com.hazelcast.core.Hazelcast" factory-method="newHazelcastInstance">
<argument type="com.hazelcast.config.Config" ref="config"/>
</bean>
<!-- publishing the hazelcastInstance as a service -->
<service ref="hazelcastInstance" interface="com.hazelcast.core.HazelcastInstance" />
Bundle B uses the instance
<!-- referencing the hazelcastInstance as a service -->
<reference ref="hazelcastInstance" interface="com.hazelcast.core.HazelcastInstance" />
<camelContext xmlns="http://camel.apache.org/schema/blueprint">
<route id="testHazelcastInstanceBeanRefPut">
<from uri="direct:testHazelcastInstanceBeanRefPut"/>
<setHeader name="CamelHazelcastOperationType">
<constant>put</constant>
</setHeader>
<to uri="hazelcast-map:testmap?hazelcastInstance=#hazelcastInstance"/>
</route>
<route id="testHazelcastInstanceBeanRefGet">
<from uri="direct:testHazelcastInstanceBeanRefGet" />
<setHeader name="CamelHazelcastOperationType">
<constant>get</constant>
</setHeader>
<to uri="hazelcast-map:testmap?hazelcastInstance=#hazelcastInstance"/>
<to uri="seda:out" />
</route>
</camelContext>
Spring Boot Auto-Configuration
When using hazelcast with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
<dependency>
<groupId>org.apache.camel.springboot</groupId>
<artifactId>camel-hazelcast-starter</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel core version -->
</dependency>
The component supports 85 options, which are listed below.
Name | Description | Default | Type |
---|---|---|---|
camel.component.hazelcast-atomicvalue.autowired-enabled |
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 |
camel.component.hazelcast-atomicvalue.customizer.hazelcast-instance.enabled |
Enable or disable the cache-manager customizer. |
true |
Boolean |
camel.component.hazelcast-atomicvalue.customizer.hazelcast-instance.override |
Configure if the cache manager eventually set on the component should be overridden by the customizer. |
false |
Boolean |
camel.component.hazelcast-atomicvalue.enabled |
Whether to enable auto configuration of the hazelcast-atomicvalue component. This is enabled by default. |
Boolean |
|
camel.component.hazelcast-atomicvalue.hazelcast-instance |
The hazelcast instance reference which can be used for hazelcast endpoint. If you don’t specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. The option is a com.hazelcast.core.HazelcastInstance type. |
HazelcastInstance |
|
camel.component.hazelcast-atomicvalue.hazelcast-mode |
The hazelcast mode reference which kind of instance should be used. If you don’t specify the mode, then the node mode will be the default. |
node |
String |
camel.component.hazelcast-atomicvalue.lazy-start-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 |
camel.component.hazelcast-instance.autowired-enabled |
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 |
camel.component.hazelcast-instance.bridge-error-handler |
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 |
camel.component.hazelcast-instance.enabled |
Whether to enable auto configuration of the hazelcast-instance component. This is enabled by default. |
Boolean |
|
camel.component.hazelcast-instance.hazelcast-instance |
The hazelcast instance reference which can be used for hazelcast endpoint. If you don’t specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. The option is a com.hazelcast.core.HazelcastInstance type. |
HazelcastInstance |
|
camel.component.hazelcast-instance.hazelcast-mode |
The hazelcast mode reference which kind of instance should be used. If you don’t specify the mode, then the node mode will be the default. |
node |
String |
camel.component.hazelcast-list.autowired-enabled |
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 |
camel.component.hazelcast-list.bridge-error-handler |
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 |
camel.component.hazelcast-list.customizer.hazelcast-instance.enabled |
Enable or disable the cache-manager customizer. |
true |
Boolean |
camel.component.hazelcast-list.customizer.hazelcast-instance.override |
Configure if the cache manager eventually set on the component should be overridden by the customizer. |
false |
Boolean |
camel.component.hazelcast-list.enabled |
Whether to enable auto configuration of the hazelcast-list component. This is enabled by default. |
Boolean |
|
camel.component.hazelcast-list.hazelcast-instance |
The hazelcast instance reference which can be used for hazelcast endpoint. If you don’t specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. The option is a com.hazelcast.core.HazelcastInstance type. |
HazelcastInstance |
|
camel.component.hazelcast-list.hazelcast-mode |
The hazelcast mode reference which kind of instance should be used. If you don’t specify the mode, then the node mode will be the default. |
node |
String |
camel.component.hazelcast-list.lazy-start-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 |
camel.component.hazelcast-map.autowired-enabled |
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 |
camel.component.hazelcast-map.bridge-error-handler |
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 |
camel.component.hazelcast-map.customizer.hazelcast-instance.enabled |
Enable or disable the cache-manager customizer. |
true |
Boolean |
camel.component.hazelcast-map.customizer.hazelcast-instance.override |
Configure if the cache manager eventually set on the component should be overridden by the customizer. |
false |
Boolean |
camel.component.hazelcast-map.enabled |
Whether to enable auto configuration of the hazelcast-map component. This is enabled by default. |
Boolean |
|
camel.component.hazelcast-map.hazelcast-instance |
The hazelcast instance reference which can be used for hazelcast endpoint. If you don’t specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. The option is a com.hazelcast.core.HazelcastInstance type. |
HazelcastInstance |
|
camel.component.hazelcast-map.hazelcast-mode |
The hazelcast mode reference which kind of instance should be used. If you don’t specify the mode, then the node mode will be the default. |
node |
String |
camel.component.hazelcast-map.lazy-start-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 |
camel.component.hazelcast-multimap.autowired-enabled |
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 |
camel.component.hazelcast-multimap.bridge-error-handler |
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 |
camel.component.hazelcast-multimap.customizer.hazelcast-instance.enabled |
Enable or disable the cache-manager customizer. |
true |
Boolean |
camel.component.hazelcast-multimap.customizer.hazelcast-instance.override |
Configure if the cache manager eventually set on the component should be overridden by the customizer. |
false |
Boolean |
camel.component.hazelcast-multimap.enabled |
Whether to enable auto configuration of the hazelcast-multimap component. This is enabled by default. |
Boolean |
|
camel.component.hazelcast-multimap.hazelcast-instance |
The hazelcast instance reference which can be used for hazelcast endpoint. If you don’t specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. The option is a com.hazelcast.core.HazelcastInstance type. |
HazelcastInstance |
|
camel.component.hazelcast-multimap.hazelcast-mode |
The hazelcast mode reference which kind of instance should be used. If you don’t specify the mode, then the node mode will be the default. |
node |
String |
camel.component.hazelcast-multimap.lazy-start-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 |
camel.component.hazelcast-queue.autowired-enabled |
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 |
camel.component.hazelcast-queue.bridge-error-handler |
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 |
camel.component.hazelcast-queue.customizer.hazelcast-instance.enabled |
Enable or disable the cache-manager customizer. |
true |
Boolean |
camel.component.hazelcast-queue.customizer.hazelcast-instance.override |
Configure if the cache manager eventually set on the component should be overridden by the customizer. |
false |
Boolean |
camel.component.hazelcast-queue.enabled |
Whether to enable auto configuration of the hazelcast-queue component. This is enabled by default. |
Boolean |
|
camel.component.hazelcast-queue.hazelcast-instance |
The hazelcast instance reference which can be used for hazelcast endpoint. If you don’t specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. The option is a com.hazelcast.core.HazelcastInstance type. |
HazelcastInstance |
|
camel.component.hazelcast-queue.hazelcast-mode |
The hazelcast mode reference which kind of instance should be used. If you don’t specify the mode, then the node mode will be the default. |
node |
String |
camel.component.hazelcast-queue.lazy-start-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 |
camel.component.hazelcast-replicatedmap.autowired-enabled |
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 |
camel.component.hazelcast-replicatedmap.bridge-error-handler |
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 |
camel.component.hazelcast-replicatedmap.customizer.hazelcast-instance.enabled |
Enable or disable the cache-manager customizer. |
true |
Boolean |
camel.component.hazelcast-replicatedmap.customizer.hazelcast-instance.override |
Configure if the cache manager eventually set on the component should be overridden by the customizer. |
false |
Boolean |
camel.component.hazelcast-replicatedmap.enabled |
Whether to enable auto configuration of the hazelcast-replicatedmap component. This is enabled by default. |
Boolean |
|
camel.component.hazelcast-replicatedmap.hazelcast-instance |
The hazelcast instance reference which can be used for hazelcast endpoint. If you don’t specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. The option is a com.hazelcast.core.HazelcastInstance type. |
HazelcastInstance |
|
camel.component.hazelcast-replicatedmap.hazelcast-mode |
The hazelcast mode reference which kind of instance should be used. If you don’t specify the mode, then the node mode will be the default. |
node |
String |
camel.component.hazelcast-replicatedmap.lazy-start-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 |
camel.component.hazelcast-ringbuffer.autowired-enabled |
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 |
camel.component.hazelcast-ringbuffer.customizer.hazelcast-instance.enabled |
Enable or disable the cache-manager customizer. |
true |
Boolean |
camel.component.hazelcast-ringbuffer.customizer.hazelcast-instance.override |
Configure if the cache manager eventually set on the component should be overridden by the customizer. |
false |
Boolean |
camel.component.hazelcast-ringbuffer.enabled |
Whether to enable auto configuration of the hazelcast-ringbuffer component. This is enabled by default. |
Boolean |
|
camel.component.hazelcast-ringbuffer.hazelcast-instance |
The hazelcast instance reference which can be used for hazelcast endpoint. If you don’t specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. The option is a com.hazelcast.core.HazelcastInstance type. |
HazelcastInstance |
|
camel.component.hazelcast-ringbuffer.hazelcast-mode |
The hazelcast mode reference which kind of instance should be used. If you don’t specify the mode, then the node mode will be the default. |
node |
String |
camel.component.hazelcast-ringbuffer.lazy-start-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 |
camel.component.hazelcast-seda.autowired-enabled |
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 |
camel.component.hazelcast-seda.bridge-error-handler |
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 |
camel.component.hazelcast-seda.customizer.hazelcast-instance.enabled |
Enable or disable the cache-manager customizer. |
true |
Boolean |
camel.component.hazelcast-seda.customizer.hazelcast-instance.override |
Configure if the cache manager eventually set on the component should be overridden by the customizer. |
false |
Boolean |
camel.component.hazelcast-seda.enabled |
Whether to enable auto configuration of the hazelcast-seda component. This is enabled by default. |
Boolean |
|
camel.component.hazelcast-seda.hazelcast-instance |
The hazelcast instance reference which can be used for hazelcast endpoint. If you don’t specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. The option is a com.hazelcast.core.HazelcastInstance type. |
HazelcastInstance |
|
camel.component.hazelcast-seda.hazelcast-mode |
The hazelcast mode reference which kind of instance should be used. If you don’t specify the mode, then the node mode will be the default. |
node |
String |
camel.component.hazelcast-seda.lazy-start-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 |
camel.component.hazelcast-set.autowired-enabled |
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 |
camel.component.hazelcast-set.bridge-error-handler |
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 |
camel.component.hazelcast-set.customizer.hazelcast-instance.enabled |
Enable or disable the cache-manager customizer. |
true |
Boolean |
camel.component.hazelcast-set.customizer.hazelcast-instance.override |
Configure if the cache manager eventually set on the component should be overridden by the customizer. |
false |
Boolean |
camel.component.hazelcast-set.enabled |
Whether to enable auto configuration of the hazelcast-set component. This is enabled by default. |
Boolean |
|
camel.component.hazelcast-set.hazelcast-instance |
The hazelcast instance reference which can be used for hazelcast endpoint. If you don’t specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. The option is a com.hazelcast.core.HazelcastInstance type. |
HazelcastInstance |
|
camel.component.hazelcast-set.hazelcast-mode |
The hazelcast mode reference which kind of instance should be used. If you don’t specify the mode, then the node mode will be the default. |
node |
String |
camel.component.hazelcast-set.lazy-start-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 |
camel.component.hazelcast-topic.autowired-enabled |
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 |
camel.component.hazelcast-topic.bridge-error-handler |
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 |
camel.component.hazelcast-topic.customizer.hazelcast-instance.enabled |
Enable or disable the cache-manager customizer. |
true |
Boolean |
camel.component.hazelcast-topic.customizer.hazelcast-instance.enabled |
Enable or disable the cache-manager customizer. |
true |
Boolean |
camel.component.hazelcast-topic.customizer.hazelcast-instance.override |
Configure if the cache manager eventually set on the component should be overridden by the customizer. |
false |
Boolean |
camel.component.hazelcast-topic.customizer.hazelcast-instance.override |
Configure if the cache manager eventually set on the component should be overridden by the customizer. |
false |
Boolean |
camel.component.hazelcast-topic.enabled |
Whether to enable auto configuration of the hazelcast-topic component. This is enabled by default. |
Boolean |
|
camel.component.hazelcast-topic.hazelcast-instance |
The hazelcast instance reference which can be used for hazelcast endpoint. If you don’t specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. The option is a com.hazelcast.core.HazelcastInstance type. |
HazelcastInstance |
|
camel.component.hazelcast-topic.hazelcast-mode |
The hazelcast mode reference which kind of instance should be used. If you don’t specify the mode, then the node mode will be the default. |
node |
String |
camel.component.hazelcast-topic.lazy-start-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 |