Since we're on a major migration process of this website, some component documents here are out of sync right now. In the meantime you may want to look at the early version of the new website
https://camel.apache.org/staging/
We would very much like to receive any feedback on the new site, please join the discussion on the Camel user mailing list.

Component / ArtifactId / URI

License

Description

ActiveMQactivemq-camel

activemq:[queue|topic:]destinationName

Apache

For JMS Messaging with Apache ActiveMQ.

ActiveMQ Brokeractivemq-camel

broker:[queue|topic:]destinationName

Apache

For internal message routing in the ActiveMQ broker using Camel.

Activitiactiviti-camel

activiti:camelProcess:serviceTask

Apache

For working with Activiti, a light-weight workflow and Business Process Management (BPM) platform which supports BPMN 2.

Bluetooth camel-bluetooth / rhiot.io

bluetooth:label

Apache

Camel Bluetooth component can retrieve information about the Bluetooth devices available within the device range.

Couchbasecamel-couchbase / camel-extra

couchbase:protocol://host[:port]/bucket

Couchbase

Working with Couchbase NoSQL document database.

Db4ocamel-db4o / camel-extra

db4o://className

GPL

For using a db4o datastore as a queue via the db4o library.

Espercamel-esper / camel-extra

esper:name

GPL

Working with the Esper Library for Event Stream Processing.

Fabric AMQmq-fabric-camel / fabric8

amq:[queue|topic:]destinationName

Apache

The amq: endpoint works exactly like the activemq: endpoint in Apache Camel; only it uses the fabric to automatically discover the broker. So there is no configuration required; it'll just work out of the box and automatically discover whatever ActiveMQ message brokers are available; with failover and load balancing.

Fabric Fabricfabric-camel / fabric8

fabric:logicalName:camelEndpointUri

Apache

The fabric: endpoint uses Fabric's discovery mechanism to expose physical sockets, HTTP endpoints, etc. into the runtime registry using a logical name so that clients can use the existing Camel Load Balancer.

Fabric Masterfabric-camel / fabric8

master:clusterName:camelEndpointUri

Apache

The master: endpoint provides a way to ensure only a single consumer in a cluster consumes from a given endpoint; with automatic failover if that JVM dies.

Framebuffer  / camel-framebuffer / rhiot.io

framebuffer://name

Apache

Camel Framebuffer component can be used to manage any Linux Framebuffer.

gpsdcamel-gpsd / rhiot.io

gpsd:label[?options]

Apache

Camel GPSD component can be used to read current GPS information from GPS devices.

Hibernatecamel-hibernate / camel-extra

hibernate://entityName

GPL

For using a database as a queue via the Hibernate library.

JBIservicemix-camel

jbi:serviceName

Apache

For JBI integration such as working with Apache ServiceMix.

JCIFScamel-jcifs / camel-extra

smb://user@server.example.com/sharename?password=secret&localWorkDirectory=/tmp

LGPL

This component provides access to remote file systems over the CIFS/SMB networking protocol by using the JCIFS library.

kura-cloudcamel-kura / rhiot.io

kura-wifi:networkInterface/ssid

Apache

Camel Kura Cloud component interacts directly with Kura CloudService.

kura-wificamel-kura / rhiot.io

kura-wifi:networkInterface/ssid

Apache

Camel Kura WiFi component can be used to retrieve the information about the WiFi access spots available within the device range.

NMRservicemix-nmr

nmr://serviceName

Apache

Integration with the Normalized Message Router BUS in ServiceMix 4.x.

OpenIMAJcamel-openimaj / rhiot.io

pi4j-gpio://gpioId[?options]

Apache

Camel OpenIMAJ component can be used to detect faces in images.

pi4j-gpiocamel-pi4j / rhiot.io

pi4j-gpio://gpioId[?options]

Apache

GPIO Component for RaspberryPi based on pi4j lib.

pi4j-i2ccamel-pi4j / rhiot.io

pi4j-i2c://busId/deviceId[?options]

Apache

i2c Component for RaspberryPi based on pi4j lib.

PubNubcamel-pubnub / rhiot.io

 pubnub://pubnubEndpointType:channel[?options]

Apache

Camel PubNub component. More information rhiot.io project.

RCodecamel-rcode / camel-extra

rcode://host[:port]/operation[?options]

LGPL

Uses Rserve to integrate Camel with the statistics environment R.

Scalatescalate-camel

scalate:templateName

Apache

Uses the given Scalate template to transform the message.

Smookscamel-smooks / camel-extra

unmarshal(edi)

GPL

For working with EDI parsing using the Smooks library. This component is deprecated as Smooks now provides Camel integration out of the box.

Spring Neo4jcamel-spring-neo4j / camel-extra

spring-neo4j:http://hostname[:port]/database[?options]

TBA

Component for producing to Neo4j datastore using the Spring Data Neo4j library.

Tinkerforgecamel-tinkerforge / rhiot.io

tinkerforge:[//hostname[:port]]/devicetype/uid/[?options]

Apache

The tinkerforge component allows interaction with Tinkerforge bricklets. It uses the standard Java bindings to connects to brickd. For more information see the rhiot.io.

VirtualBoxcamel-virtualbox / camel-extra

virtualbox:machine[?options]

GPL V2

The VitualBox component uses the webservice API that exposes VirtualBox functionality and consumes events generated by virtual machines.

Webcamcamel-webcam / rhiot.io

webcam:label[?options]

Apache

Camel Webcam component can be used to capture still images and detect motion.

ZeroMQcamel-zeromq / camel-extra

zeromq:(tcp|ipc)://hostname:port

LGPL

The ZeroMQ component allows you to consumer or produce messages using ZeroMQ.

© 2004-2015 The Apache Software Foundation.
Apache Camel, Camel, Apache, the Apache feather logo, and the Apache Camel project logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners.
Graphic Design By Hiram