THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Component / ArtifactId / URI | License | Description |
|---|---|---|
ActiveMQ / activemq-camel activemq:[queue|topic:]destinationName | Apache | For JMS Messaging with Apache ActiveMQ |
ActiveMQ Broker / activemq-camel broker:[queue|topic:]destinationName | Apache | For internal message routing in the ActiveMQ broker using Camel. |
Activiti / activiti-camel activiti:camelProcess:serviceTask | Apache | For working with Activiti, a light-weight workflow and Business Process Management (BPM) platform which supports BPMN 2 |
Couchbase / camel-couchbase in camel-extra couchbase:protocol://host[:port]/bucket | Couchbase | Working with Couchbase NoSQL document database |
Db4o / camel-db4o in camel-extra db4o://className | GPL | For using a db4o datastore as a queue via the db4o library |
Esper / camel-esper in camel-extra esper:name | GPL | Working with the Esper Library for Event Stream Processing |
Fabric AMQ / mq-fabric-camel in 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 Fabric / fabric-camel in 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 Master / fabric-camel in 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. |
Hibernate / camel-hibernate in camel-extra hibernate://entityName | GPL | For using a database as a queue via the Hibernate library |
JBI / servicemix-camel jbi:serviceName | Apache | For JBI integration such as working with Apache ServiceMix |
JCIFS / camel-jcifs in 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. |
NMR / servicemix-nmr nmr://serviceName | Apache | Integration with the Normalized Message Router BUS in ServiceMix 4.x |
pi4j-gpio / camel-pi4j in Camel IoT Labs pi4j-gpio://gpioId[?options] | Apache | GPIO Component for RaspberryPi
|
pi4j-i2c / camel-pi4j pi4j-i2c://busId/deviceId[?options]
| Apache | i2c Component for RaspberryPi
|
RCode / camel-rcode in camel-extra rcode://host[:port]/operation[?options] | LGPL | Uses Rserve to integrate Camel with the statistics environment R |
Scalate / scalate-camel scalate:templateName | Apache | Uses the given Scalate template to transform the message |
Smooks / camel-smooks in 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 Neo4j / camel-spring-neo4j in camel-extra spring-neo4j:http://hostname[:port]/database[?options] | to bee clarified | Component for producing to Neo4j datastore using the Spring Data Neo4j library |
Tinkerforge / camel-tinkerforge in Camel IoT Labs 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. |
VirtualBox / camel-virtualbox in 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. |
ZeroMQ / camel-zeromq in camel-extra. zeromq:(tcp|ipc)://hostname:port | LGPL | The ZeroMQ component allows you to consumer or produce messages using ZeroMQ. |