The cxf: component provides integration with Apache CXF for connecting to JAX-WS services hosted in CXF.

URI format

Options

Name	Required	Description
hazelcastInstance	No	Camel 2.14: 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.
hazelcastInstanceName	No	Camel 2.16: The hazelcast instance reference name 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.
operation	-1	To specify a default operation to use, if no operation header has been provided. deprecated use defaultOperation instead.
defaultOperation	-1	Camel 2.15: To specify a default operation to use, if no operation header has been provided.

Sections

Usage of Map

map cache producer - to("hazelcast:map:foo")

If you want to store a value in a map you can use the map cache producer. The map cache producer provides 5 operations (put, get, update, delete, query). For the first 4 you have to provide the operation inside the "hazelcast.operation.type" header variable. In Java DSL you can use the constants from

org.apache.camel.c
 omponent.hazelcast.HazelcastConstants

Name	Type	Description
`hazelcast.operation.type`	`String`	valid values are: put, delete, get, update, query
`hazelcast.objectId`	`String`	the object id to store / find your object inside the cache (not needed for the query operation)

Name	Type	Description
`CamelHazelcastOperationType`	`String`	valid values are: put, delete, get, update, query Version 2.8 From Camel 2.16: getAll, putIfAbsent, clear.
`CamelHazelcastObjectId`	`String`	the object id to store / find your object inside the cache (not needed for the query operation) Version 2.8

Name

Type

Description

CamelHazelcastOperationType

String

valid values are: put, delete, get, update, query Version 2.8

From Camel 2.16: getAll, putIfAbsent, clear.

CamelHazelcastObjectId

String

the object id to store / find your object inside the cache (not needed for the query operation) Version 2.8

Options

Name	Required	Description
hazelcastInstance	No	Camel 2.14: 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.
hazelcastInstanceName	No	Camel 2.16: The hazelcast instance reference name 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.
operation	-1	To specify a default operation to use, if no operation header has been provided. deprecated use defaultOperation instead.
defaultOperation	-1	Camel 2.15: To specify a default operation to use, if no operation header has been provided.

Sections

Usage of Map

map cache producer - to("hazelcast:map:foo")

Name	Type	Description
`hazelcast.operation.type`	`String`	vali d values are: put, delete, get, update, query
`hazelcast.objectId`	`String`	the object id to store / find your object inside the cache (not needed for the query operation)

Name	Type	Description
`CamelHazelcastOperationType`	`String`	valid values are: put, delete, get, update, query Version 2.8 From Camel 2.16: getAll, putIfAbsent, clear.
`CamelHazelcastObjectId`	`String`	the object id to store / find your object inside the cache (not needed for the query operation) Version 2.8

Name

Type

Description

CamelHazelcastOperationType

String

valid values are: put, delete, get, update, query Version 2.8

From Camel 2.16: getAll, putIfAbsent, clear.

CamelHazelcastObjectId

String

the object id to store / find your object inside the cache (not needed for the query operation) Version 2.8

Sample for put:

Name	Type	Description
`hazelcast.listener.time`	`Long`	time of the event in millis
`hazelcast.listener.type`	`String`	the map consumer sets here "cachelistener"
`hazelcast.listener.action` < /td>	`String`	type of event - here added and removed (and soon envicted)
`hazelcast.objectId`	`String`	the oid of the object
`hazelcast.cache.name`	`String`	the name of the cache - e.g. "foo"
`hazelcast.cache.type`	`String`	the type of the cache - here replicatedmap

Name	Type	Description
`CamelHazelcastListenerTime`	`Long`	time of the event i n millis Version 2.8
`CamelHazelcastListenerType`	`String`	the map consumer sets here "cachelistener" Version 2.8
`CamelHazelcastListenerAction`	`String`	type of event - here added and removed (and soon envicted) Version 2.8
`CamelHazelcastObjectId`	`String`	the oid of the object Version 2.8
`CamelHazelcastCacheName`	`String`	the name of the cache - e.g. "foo" Version 2.8
`CamelHazelcastCacheType`	`String`	the type of the cache - here replicatedmap Version 2.8

HDFS Component

Available as of Camel 2.8

The hdfs component enables you to read and write messages from/to an HDFS file system. HDFS is the distributed file system at the heart of Hadoop.

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

Header Variables inside the response message:

Name	Type	Description
`hazelcast.listener.time`	`Long`	time of the event in millis
`hazelcast.listener.type`	`String`	the map consumer sets here "cachelistener"
`hazelcast.listener.action` < /td>	`String`	type of event - here added and removed (and soon envicted)
`hazelcast.objectId`	`String`	the oid of the object
`hazelcast.cache.name`	`String`	the name of the cache - e.g. "foo"
`hazelcast.cache.type`	`String`	the type of the cache - here replicatedmap

Eviction will be added as feature, soon (this is a Hazelcast issue).

Header variables have changed in Camel 2.8

Name	Type	Description
`CamelHazelcastListenerTime`	`Long`	time of the event i n millis Version 2.8
`CamelHazelcastListenerType`	`String`	the map consumer sets here "cachelistener" Version 2.8
`CamelHazelcastListenerAction`	`String`	type of event - here added and removed (and soon envicted) Version 2.8
`CamelHazelcastObjectId`	`String`	the oid of the object Version 2.8
`CamelHazelcastCacheName`	`String`	the name of the cache - e.g. "foo" Version 2.8
`CamelHazelcastCacheType`	`String`	the type of the cache - here replicatedmap Version 2.8

Usage of Ringbuffer

Avalaible from Camel 2.16

ringbuffer cache producer - to("hazelcast:ringbuffer:foo")

Ringbuffer is a distributed data structure where the data is stored in a ring-like structure. You can think of it as a circular array with a certain capacity. The ringbuffer producer provides 5 operations (add, readonceHead, readonceTail, remainingCapacity, capacity).

Header Variables for the request message:

Name	Type	Description
`hazelcast.operation.type`	`String`	valid values are: add, readonceHead, readonceTail, remainingCapacity, capacity

Header variables have changed in Camel 2.8

Name	Type	Description
`CamelHazelcastOperationType`	`String`	valid values are: put, get, removevalue, delete Version 2.8
`CamelHazelcastObjectId`	`String`	the object id to store / find your object inside the cache Version 2.8

Sample for put:

Java DSL:

+
+

Spring DSL:

+
+

Sample for readonce from head:

Java DSL:

+
+

HDFS Component

Available as of Camel 2.8

The hdfs component enables you to read and write messages from/to an HDFS file system. HDFS is the distributed file system at the heart of Hadoop.

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

CXF Component

When using CXF as a consumer, the CXF Bean Component allows you to factor out how message payloads are received from their processing as a RESTful or SOAP web service. This has the potential of using a multitude of transports to consume web services. The bean component's configuration is also simpler and provides the fastest method to implement web services using Camel and CXF.

When using CXF in streaming modes (see DataFormat option), then also read about Stream caching.

The cxf: component provides integration with Apache CXF for connecting to JAX-WS services hosted in CXF.

+/*]]>*/

CXF Component
- URI format
- Options
  - The descriptions of the dataformats @@ -19953,9 +19953,9 @@ http://java.sun.com/xml/ns/javaee/web-ap </dependency> ]]>

URI format

-
-

Topic support is available as of Camel 2.15.

Options

Name	Required	Description
hazelcastInstance	No	Camel 2.14: 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.
hazelcastInstanceName	No	Camel 2.16: The hazelcast instance reference name 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.
operation	-1	To specify a default operation to use, if no operation header has been provided. deprecated use defaultOperation instead.
defaultOperation	-1	Camel 2.15: To specify a default operation to use, if no operation header has been provided.

You have to use the second prefix to define which type of data store you want to use.

Sections

Usage of #map
Usage of #multimap
Usage of #queue
Usage of #topic
Usage of #list
Usage of #seda
Usage of atomic number
Usage of #cluster support (instance)
Usage of #replicatedmap

Usage of Map

map cache producer - to("hazelcast:map:foo")

Header Variables for the request message:

Name	Type	Description
`hazelcast.operation.type`	`String`	valid values are: put, delete, get, update, query
`hazelcast.objectId`	`String`	the object id to store / find your object inside the cache (not needed for the query operation)

Header variables have changed in Camel 2.8

Name	Type	Description
`CamelHazelcastOperationType`	`String`	valid values are: put, delete, get, update, query Version 2.8 From Camel 2.16: getAll, putIfAbsent, clear.
CamelHazelcastObjectId	`String`	the object id to store / find your object inside the cache (not needed for the query operation) Version 2.8

Name

Type

Description

CamelHazelcastOperationType

String

valid values are: put, delete, get, update, query Version 2.8

From Camel 2.16: getAll, putIfAbsent, clear.

CamelHazelcastObjectId

String

the object id to store / find your object inside the cache (not needed for the query operation) Version 2.8

You can call the samples with:

Topic support is available as of Camel 2.15.

RingBuffer support is available as of Camel 2.16.

Options

Name	Required	Description
hazelcastInstance	No	Camel 2.14: 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.
hazelcastInstanceName	No	Camel 2.16: The hazelcast instance reference name 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.
operation	-1	To speci fy a default operation to use, if no operation header has been provided. deprecated use defaultOperation instead.
defaultOperation	-1	Camel 2.15: To specify a default operation to use, if no operation header has been provided.

You have to use the second prefix to define which type of data store you want to use.

Sections

Usage of #map
Usage of #multimap
Usage of #queue
Usage of #topic
Usage of #list
Usage of #seda
Usage of atomic number
Usage of #cluster support (instance)
Usage of #replicatedmap
Usage of #ringbuffer

Usage of Map

map cache producer - to("hazelcast:map:foo")

Header Variables for the request message:

Name	Type	Description
`hazelcast.operation.type`	`String`	valid values are: put, delete, get, update, query
`hazelcast.objectId`	`String`	the object id to store / find your object inside the cache (not needed for the query operation)

Header variables have changed in Camel 2.8

Name	Type	Description
`CamelHazelcastOperationType`	`String`	valid values are: put, delete, get, update, query Version 2.8 From Camel 2.16: getAll, putIfAbsent, clear.
`CamelHazelcastObjectId`	`String`	the object id to store / find your object inside the cache (not needed for the query operation) Version 2.8

Name

Type

Description

CamelHazelcastOperationType

String

valid values are: put, delete, get, update, query Version 2.8

From Camel 2.16: getAll, putIfAbsent, clear.

CamelHazelcastObjectId

String

the object id to store / find your object inside the cache (not needed for the query operation) Version 2.8

You can call the samples with:

Sample for put:

Java DSL:

@@ -20496,7 +20496,27 @@ template.sendBodyAndHeader("direct:
         .otherwise()
                 .log("fail!");
 ]]>
-

Header Variables inside the response message:

Name	Type	Description
`hazelcast.listener.time`	`Long`	time of the event in millis
`hazelcast.listener.type`	`String`	the map consumer sets here "cachelistener"
`hazelcast.listener.action` < /td>	`String`	type of event - here added and removed (and soon envicted)
`hazelcast.objectId`	`String`	the oid of the object
`hazelcast.cache.name`	`String`	the name of the cache - e.g. "foo"
`hazelcast.cache.type`	`String`	the type of the cache - here replicatedmap

Eviction will be added as feature, soon (this is a Hazelcast issue).

Header variables have changed in Camel 2.8

Name	Type	Description
`CamelHazelcastListenerTime`	`Long`	time of the event i n millis Version 2.8
`CamelHazelcastListenerType`	`String`	the map consumer sets here "cachelistener" Version 2.8
`CamelHazelcastListenerAction`	`String`	type of event - here added and removed (and soon envicted) Version 2.8
`CamelHazelcastObjectId`	`String`	the oid of the object Version 2.8
`CamelHazelcastCacheName`	`String`	the name of the cache - e.g. "foo" Version 2.8
`CamelHazelcastCacheType`	`String`	the type of the cache - here replicatedmap Version 2.8

HDFS Component

Available as of Camel 2.8

The hdfs component enables you to read and write messages from/to an HDFS file system. HDFS is the distributed file system at the heart of Hadoop.

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

Header Variables inside the response message:

Name	Type	Description
`hazelcast.listener.time`	`Long`	time of the event in millis
`hazelcast.listener.type`	`String`	the map consumer sets here "cachelistener"
`hazelcast.listener.action` < /td>	`String`	type of event - here added and removed (and soon envicted)
`hazelcast.objectId`	`String`	the oid of the object
`hazelcast.cache.name`	`String`	the name of the cache - e.g. "foo"
`hazelcast.cache.type`	`String`	the type of the cache - here replicatedmap

Eviction will be added as feature, soon (this is a Hazelcast issue).

Header variables have changed in Camel 2.8

Name	Type	Description
`CamelHazelcastListenerTime`	`Long`	time of the event i n millis Version 2.8
`CamelHazelcastListenerType`	`String`	the map consumer sets here "cachelistener" Version 2.8
`CamelHazelcastListenerAction`	`String`	type of event - here added and removed (and soon envicted) Version 2.8
`CamelHazelcastObjectId`	`String`	the oid of the object Version 2.8
`CamelHazelcastCacheName`	`String`	the name of the cache - e.g. "foo" Version 2.8
`CamelHazelcastCacheType`	`String`	the type of the cache - here replicatedmap Version 2.8

Usage of Ringbuffer

Avalaible from Camel 2.16

ringbuffer cache producer - to("hazelcast:ringbuffer:foo")

Header Variables for the request message:

Name	Type	Description
`hazelcast.operation.type`	`String`	valid values are: add, readonceHead, readonceTail, remainingCapacity, capacity

Header variables have changed in Camel 2.8

Name	Type	Description
`CamelHazelcastOperationType`	`String`	valid values are: put, get, removevalue, delete Version 2.8
`CamelHazelcastObjectId`	`String`	the object id to store / find your object inside the cache Version 2.8

Sample for put:

Java DSL:

+
+

Spring DSL:

+
+

Sample for readonce from head:

Java DSL:

+
+

HDFS Component

Available as of Camel 2.8

The hdfs component enables you to read and write messages from/to an HDFS file system. HDFS is the distributed file system at the heart of Hadoop.

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

See Also

CXF Component

URI format

Options

Sections

Usage of Map

map cache producer - to("hazelcast:map:foo")

Options

Sections

Usage of Map

map cache producer - to("hazelcast:map:foo")

Sample for put:

HDFS Component

Usage of Ringbuffer

ringbuffer cache producer - to("hazelcast:ringbuffer:foo")

Sample for put:

Sample for readonce from head:

HDFS Component

See Also

CXF Component

URI format

Options

Sections

Usage of Map

map cache producer - to("hazelcast:map:foo")

Options

Sections

Usage of Map

map cache producer - to("hazelcast:map:foo")

Sample for put:

HDFS Component

Usage of Ringbuffer

ringbuffer cache producer - to("hazelcast:ringbuffer:foo")

Sample for put:

Sample for readonce from head:

HDFS Component