Component / ArtifactId / URI
ActiveMQ / activemq-camel
For JMS Messaging with Apache ActiveMQ
ActiveMQ Broker / activemq-camel
For internal message routing in the ActiveMQ broker using Camel.
Activiti / activiti-camel
For working with Activiti, a light-weight workflow and Business Process Management (BPM) platform which supports BPMN 2
|Couchbase||Working with Couchbase NoSQL document database|
For using a db4o datastore as a queue via the db4o library
Working with the Esper Library for Event Stream Processing
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.
|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.|
|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.|
For using a database as a queue via the Hibernate library
JBI / servicemix-camel
For JBI integration such as working with Apache ServiceMix
This component provides access to remote file systems over the CIFS/SMB networking protocol by using the JCIFS library.
NMR / servicemix-nmr
Integration with the Normalized Message Router BUS in ServiceMix 4.x
Scalate / scalate-camel
Uses the given Scalate template to transform the message
to bee clarified
Component for producing to Neo4j datastore using the Spring Data Neo4j library
The VitualBox component uses the webservice API that exposes VirtualBox functionality and consumes events generated by virtual machines.
The ZeroMQ component allows you to consumer or produce messages using ZeroMQ.