Component / ArtifactId / URI | Description | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
AHC /
| To call external HTTP services using Async Http Client | |||||||||||||||||
AHC-WS /
| To exchange data with external Websocket servers using Async Http Client | |||||||||||||||||
AMQP /
| For Messaging with AMQP protocol | |||||||||||||||||
APNS /
| For sending notifications to Apple iOS devicesAtom | |||||||||||||||||
Atmosphere-Websocket / | atom
| atom:atomUri
| To exchange data with external Websocket clients using Atmosphere | |||||||||||||||
Atom /
| Working with Apache Working with Apache Abdera for atom integration, such as consuming an atom feed. | |||||||||||||||||
Avro /
| Working with Apache Avro for data serialization. | |||||||||||||||||
| For working with Amazon's CloudWatch (CW). | |||||||||||||||||
| For working with Amazon's DynamoDB (DDB). | |||||||||||||||||
| For working with Amazon's SimpleDB DynamoDB Streams (SDBDDB Streams). | |||||||||||||||||
| For working with Amazon's Simple Email Service (SESElastic Compute Cloud (EC2). | |||||||||||||||||
| For Messaging working with Amazon's Simple Notification Service SimpleDB (SNSSDB). | |||||||||||||||||
| For Messaging working with Amazon's Simple Queue Email Service (SQSSES). | |||||||||||||||||
| For working Messaging with Amazon's Simple Storage Notification Service (S3SNS). | |||||||||||||||||
| Uses the Bean Binding to bind message exchanges to beans in the Registry. Is also used for exposing and invoking POJO (Plain Old Java Objects). | Bean Validation / camel-bean-validatorFor Messaging with Amazon's Simple Queue Service (SQS). | ||||||||||||||||
| bean
| validator:something[
| Validates the payload of a message using the Java Validation API (JSR 303 and JAXP Validation) and its reference implementation Hibernate Validator | For Messaging with Amazon's Simple Workflow Service (SWF). | ||||||||||||||
AWS-S3 / camel-awsBrowse / camel-core
| Provides a simple BrowsableEndpoint which can be useful for testing, visualisation tools or debugging. The exchanges sent to the endpoint are all available to be browsed. |
| For working with Amazon's Simple Storage Service (S3). | |||||||||||||||
Bean / | ||||||||||||||||||
Code Block | none | none | ||||||||||||||||
cache://cacheName[?options]
| The cache component facilitates creation of caching endpoints and processors using EHCache as the cache implementation. | Class /
| Uses the Bean Binding to bind message exchanges to beans in the Registry. Is also used for exposing and invoking POJO (Plain Old Java Objects).CMIS | |||||||||||||||
Beanstalk / | cmis
| cmis
| /cmisServerUrl
| Uses the Apache Chemistry client API to interface with CMIS supporting CMS | For working with Amazon's Beanstalk. | |||||||||||||
Bean Validator /
| Used to deliver messages using the jetty cometd implementation of the bayeux protocol | Validates the payload of a message using the Java Validation API (JSR 303 and JAXP Validation) and its reference implementation Hibernate Validator | ||||||||||||||||
Box / | Context / camel-context
| |||||||||||||||||
context:camelContextId:localEndpointName[?options]
| Used to refer to endpoints within a separate CamelContext to provide a simple black box composition approach so that routes can be combined into a CamelContext and then used as a black box component inside other routes in other CamelContexts | |||||||||||||||||
Code Block | none | none | ||||||||||||||||
controlbus:command[?options]
|
| For uploading, downloading and managing files, managing files, folders, groups, collaborations, etc. on Box.com. | ||||||||||||||||
Braintree /
| Component for interacting with Braintree Payments via Braintree Java SDK | |||||||||||||||||
Browse / | ControlBus EIP that allows to send messages to Endpoints for managing and monitoring your Camel applications. | CouchDB / camel-couchdb
| To integrate with Apache CouchDB. |
| Provides a simple BrowsableEndpoint which can be useful for testing, visualisation tools or debugging. The exchanges sent to the endpoint are all available to be browsed. | |||||||||||||
Cache /
| Used to sign and verify exchanges using the Signature Service of the Java Cryptographic Extension. | |||||||||||||||||
Code Block | none | none | ||||||||||||||||
cxf:<bean:cxfEndpoint|//someAddress>[?options]
| Working with Apache CXF for web services integration | The cache component facilitates creation of caching endpoints and processors using EHCache as the cache implementation. | ||||||||||||||||
Cassandra /
| For integrating with Apache Cassandra. | |||||||||||||||||
Class /
| Proceess the exchange using a JAX WS or JAX RS annotated bean from the registry. Requires less configuration than the above CXF Component | CXFRS / camel-cxfUses the Bean Binding to bind message exchanges to beans in the Registry. Is also used for exposing and invoking POJO (Plain Old Java Objects). | ||||||||||||||||
Chronicle Engine /
| cxfrs:<bean:rsEndpoint|//address>
|
Working with Apache CXF for REST services integration | Chronicle Engine is a high performance, low latency, reactive processing framework. | |||||||||||||||
Chunk /
| for working with Data Formats as if it was a regular Component supporting Endpoints and URIs. | Generates a response using a Chunk template | ||||||||||||||||
CMIS /
| For load & soak testing the DataSet provides a way to create huge numbers of messages for sending to Components or asserting that they are consumed correctly | Uses the Apache Chemistry client API to interface with CMIS supporting CMS | ||||||||||||||||
Cometd /
| Synchronous call to another endpoint from same CamelContext. | Direct-VM / camel-coreUsed to deliver messages using the jetty cometd implementation of the bayeux protocol | ||||||||||||||||
Consul /
| direct-vm
| someName
|
Synchronous call to another endpoint in another CamelContext running in the same JVM. | For interfacing with an Consul. | ||||||||||||||
Context /
| To lookup domain information and run DNS queries using DNSJava | |||||||||||||||||
Disruptor / camel-disruptor
| To provide the implementation of SEDA which is based on disruptor | |||||||||||||||||
Used to refer to endpoints within a separate CamelContext to provide a simple black box composition approach so that routes can be combined into a CamelContext and then used as a black box component inside other routes in other CamelContexts | ||||||||||||||||||
ControlBus /
| ControlBus EIP that allows to send messages to Endpoints for managing and monitoring your Camel applications. | |||||||||||||||||
CouchDB /
| To integrate with Apache CouchDB. | |||||||||||||||||
Crypto (Digital Signatures) /
EJB / camel-ejb
| Uses the Bean Binding to bind message exchanges to EJBs. It works like the Bean component but just for accessing EJBs. Supports EJB 3.0 onwards. | Used to sign and verify exchanges using the Signature Service of the Java Cryptographic Extension. | ||||||||||||||||
CXF /
| Working with Apache CXF for web services integration | |||||||||||||||||
CXF Bean /
| Proceess the exchange using a JAX WS or JAX RS annotated bean from the registry. Requires less configuration than the above CXF Component | |||||||||||||||||
CXFRS /
| Working with Apache CXF for REST services integration | |||||||||||||||||
DataFormat /
| for working with Data Formats as if it was a regular Component supporting Endpoints and URIs. | |||||||||||||||||
DataSet /
| For load & soak testing the DataSet provides a way to create huge numbers of messages for sending to Components or asserting that they are consumed correctly | |||||||||||||||||
Direct /
| Synchronous call to another endpoint from same CamelContext. | |||||||||||||||||
Direct-VM /
| Synchronous call to another endpoint in another CamelContext running in the same JVM. | |||||||||||||||||
DNS /
| To lookup domain information and run DNS queries using DNSJava | |||||||||||||||||
Disruptor /
| To provide the implementation of SEDA which is based on disruptor | |||||||||||||||||
Docker /
| To communicate with Docker | |||||||||||||||||
Dozer /
| To convert message body using the Dozer type converter library. | |||||||||||||||||
Dropbox /
| The dropbox: component allows you to treat Dropbox remote folders as a producer or consumer of messages. | |||||||||||||||||
EJB /
| Uses the Bean Binding to bind message exchanges to EJBs. It works like the Bean component but just for accessing EJBs. Supports EJB 3.0 onwards. | |||||||||||||||||
Ehcache /
| The cache component facilitates creation of caching endpoints and processors using Ehcache 3 as the cache implementation. | |||||||||||||||||
ElasticSearch /
| For interfacing with an ElasticSearch server. | |||||||||||||||||
Etcd /
| For interfacing with an Etcd key value store. | |||||||||||||||||
Spring Event /
| Working with Spring ApplicationEvents | |||||||||||||||||
EventAdmin /
| Receiving OSGi EventAdmin events | |||||||||||||||||
Exec /
| For executing system commands | |||||||||||||||||
Facebook /
| Providing access to all of the Facebook APIs accessible using Facebook4J | |||||||||||||||||
File /
| Sending messages to a file or polling a file or directory. | |||||||||||||||||
Flatpack /
| Processing fixed width or delimited files or messages using the FlatPack library | |||||||||||||||||
Flink /
| Bridges Camel connectors with Apache Flink tasks. | |||||||||||||||||
FOP /
| Renders the message into different output formats using Apache FOP | |||||||||||||||||
FreeMarker /
| Generates a response using a FreeMarker template | |||||||||||||||||
FTP /
| Sending and receiving files over FTP. | |||||||||||||||||
FTPS /
| Sending and receiving files over FTP Secure (TLS and SSL). | |||||||||||||||||
Ganglia /
| Sends values as metrics to the Ganglia performance monitoring system using gmetric4j. Can be used along with JMXetric. | |||||||||||||||||
| Used by web applications to implement an OAuth consumer. See also Camel Components for Google App Engine. | |||||||||||||||||
| Provides connectivity to the URL fetch service of Google App Engine but can also be used to receive messages from servlets. See also Camel Components for Google App Engine. | |||||||||||||||||
| Supports interaction with Git repositories | |||||||||||||||||
| Supports interaction with Github | |||||||||||||||||
| Used by Camel applications outside Google App Engine (GAE) for programmatic login to GAE applications. See also Camel Components for Google App Engine. | |||||||||||||||||
| Supports asynchronous message processing on Google App Engine by using the task queueing service as message queue. See also Camel Components for Google App Engine. | |||||||||||||||||
Google Calendar / camel-google-calendar
| Supports interaction with Google Calendar's REST API. | |||||||||||||||||
Google Drive / camel-google-drive
| Supports interaction with Google Drive's REST API. | |||||||||||||||||
Google Mail / camel-google-mail
| Supports interaction with Google Mail's REST API. | |||||||||||||||||
| Supports sending of emails via the mail service of Google App Engine. See also Camel Components for Google App Engine. | |||||||||||||||||
Gora /
| Supports to work with NoSQL databases using the Apache Gora framework. | |||||||||||||||||
| Grape component allows you to fetch, load and manage additional jars when CamelContext is running. | |||||||||||||||||
Geocoder /
| Supports looking up geocoders for an address, or reverse lookup geocoders from an address. | |||||||||||||||||
Google Guava EventBus /
| The Google Guava EventBus allows publish-subscribe-style communication between components without requiring the components to explicitly register with one another (and thus be aware of each other). This component provides integration bridge between Camel and Google Guava EventBus infrastructure. | |||||||||||||||||
| Hazelcast is a data grid entirely implemented in Java (single jar). This component supports map, multimap, seda, queue, set, atomic number and simple cluster support. | |||||||||||||||||
HBase /
| For reading/writing from/to an HBase store (Hadoop database) | |||||||||||||||||
HDFS /
| For reading/writing from/to an HDFS filesystem using Hadoop 1.x | |||||||||||||||||
HDFS2 /
| For reading/writing from/to an HDFS filesystem using Hadoop 2.x | |||||||||||||||||
Hipchat /
| For sending/receiving messages to Hipchat using v2 API | |||||||||||||||||
HL7 /
| For working with the HL7 MLLP protocol and the HL7 data format using the HAPI library | |||||||||||||||||
Infinispan /
| For reading/writing from/to Infinispan distributed key/value store and data grid | |||||||||||||||||
HTTP /
| For calling out to external HTTP servers using Apache HTTP Client 3.x | |||||||||||||||||
HTTP4 /
| For calling out to external HTTP servers using Apache HTTP Client 4.x | |||||||||||||||||
iBATIS /
| Performs a query, poll, insert, update or delete in a relational database using Apache iBATIS | |||||||||||||||||
Ignite /
| Apache Ignite In-Memory Data Fabric is a high-performance, integrated and distributed in-memory platform for computing and transacting on large-scale data sets in real-time, orders of magnitude faster than possible with traditional disk-based or flash technologies. It is designed to deliver uncompromised performance for a wide set of in-memory computing use cases from high performance computing, to the industry most advanced data grid, highly available service grid, and streaming. | |||||||||||||||||
IMAP /
| For interfacing with an ElasticSearch server. | Receiving email using IMAP | ||||||||||||||||
IMAPS / | ||||||||||||||||||
Code Block | none | none | ||||||||||||||||
spring-event://default
| Working with Spring ApplicationEvents | EventAdmin / camel-eventadmin
| ... | |||||||||||||||
IRC / | Receiving OSGi EventAdmin events | Exec /
| For executing system commandsFacebook / IRC communication | |||||||||||||||
IronMQ / | facebook
| facebook
| //endpoint
|
Providing access to all of the Facebook APIs accessible using Facebook4J | For working with IronMQ a elastic and durable hosted message queue as a service. | |||||||||||||
JavaSpace /
| Sending messages to a file or polling a file or directory.Flatpack / camel-flatpackand receiving messages through JavaSpace | |||||||||||||||||
jBPM /
| flatpack
| [fixed|delim]:configFile
| Processing fixed width or delimited files or messages using the FlatPack library | Sending messages through kie-remote-client API to jBPM. | ||||||||||||||
jcache / | FOP / camel-fop
| fop
| outputFormat
|
Renders the message into different output formats using Apache FOP | The JCache component facilitates creation of caching endpoints and processors using JCache / jsr107 as the cache implementation. | |||||||||||||
jclouds /
| Generates a response using a FreeMarker template | For interacting with cloud compute & blobstore service via jclouds | ||||||||||||||||
JCR /
| Storing a message in a JCR compliant repository like Apache Jackrabbit | |||||||||||||||||
JDBC / | Sending and receiving files over FTP. | FTPS / camel-ftp
| Sending and receiving files over FTP Secure (TLS and SSL). | For performing JDBC queries and operations | ||||||||||||||
Jetty /
| Used by web applications to implement an OAuth consumer. See also Camel Components for Google App Engine. | GHttp / camel-gaeFor exposing or consuming services over HTTP | ||||||||||||||||
JGroups /
| ghttp
| contextPath
| Provides connectivity to the URL fetch service of Google App Engine but can also be used to receive messages from servlets. See also Camel Components for Google App Engine. | The | ||||||||||||||
JIRA / | GLogin / camel-gae
| glogin
| For interacting with JIRA | |||||||||||||||
JMS /
| Used by Camel applications outside Google App Engine (GAE) for programmatic login to GAE applications. See also Camel Components for Google App Engine. | Working with JMS providers | ||||||||||||||||
JMX /
| Supports asynchronous message processing on Google App Engine by using the task queueing service as message queue. See also Camel Components for Google App Engine. | For working with JMX notification listeners | ||||||||||||||||
JPA /
| Supports sending of emails via the mail service of Google App Engine. See also Camel Components for Google App Engine. | For using a database as a queue via the JPA specification for working with OpenJPA, Hibernate or TopLink | ||||||||||||||||
JOLT / | Geocoder / camel-geocoder
| geocoder:<address|latlng:latitude,longitude>
|
Supports looking up geocoders for an address, or reverse lookup geocoders from an address. | The jolt: component allows you to process a JSON messages using an JOLT specification. This can be ideal when doing JSON to JSON transformation. | ||||||||||||||
Jsch /
| The Google Guava EventBus allows publish-subscribe-style communication between components without requiring the components to explicitly register with one another (and thus be aware of each other). This component provides integration bridge between Camel and Google Guava EventBus infrastructure. | Support for the scp protocol | ||||||||||||||||
JT/400 /
| Hazelcast is a data grid entirely implemented in Java (single jar). This component supports map, multimap, seda, queue, set, atomic number and simple cluster support. | For integrating with data queues on an AS/400 (aka System i, IBM i, i5, ...) system | ||||||||||||||||
Kafka / | HBase / camel-hbase
| hbase
| table
|
For producing to or consuming from Apache Kafka message brokers. | ||||||||||||||
Kestrel /
| For reading/writing from/to an HDFS filesystemproducing to or consuming from Kestrel queues | |||||||||||||||||
Krati /
| For working with the HL7 MLLP protocol and the HL7 model using the HAPI library | For producing to or consuming to Krati datastores | ||||||||||||||||
Kubernetes / | Infinispan / camel-infinispan
| infinispan
| //hostName
|
For reading/writing from/to Infinispan distributed key/value store and data grid | For integrating your application with Kubernetes standalone or on top of OpenShift. | |||||||||||||
Kura /
| For deploying Camel OSGi routes into the Eclipse Kura M2M container. | |||||||||||||||||
Language /
| For calling out to external HTTP servers using Apache HTTP Client 3.x | Executes Languages scripts | ||||||||||||||||
LDAP /
| For calling out to external HTTP servers using Apache HTTP Client 4.x | Performing searches on LDAP servers (<scope> must be one of object|onelevel|subtree) | ||||||||||||||||
LinkedIn / | iBATIS / camel-ibatis
| ibatis
| statementName
| ?
| Performs a query, poll, insert, update or delete in a relational database using Apache iBATIS | Component for retrieving LinkedIn user profiles, connections, companies, groups, posts, etc. using LinkedIn REST API. | ||||||||||||
Log /
| Receiving email using IMAP | Uses Jakarta Commons Logging to log the message exchange to some underlying logging system like log4j | ||||||||||||||||
Lucene /
| ... | Uses Apache Lucene to perform Java-based indexing and full text based searches using advanced analysis/tokenization capabilities | ||||||||||||||||
Lumberjack / | IRC / camel-irc
| irc:[login@]hostName
| /#room[?options]
For IRC communication | Uses the Lumberjack protocol for retrieving logs (from Filebeat for instance) | ||||||||||||||
Metrics / | JavaSpace / camel-javaspace
| javaspace:jini://hostName
|
Sending and receiving messages through JavaSpace | Uses Metrics to collect application statistics directly from Camel routes. | ||||||||||||||
MINA /
| For interacting with cloud compute & blobstore service via jclouds | Working with Apache MINA 1.x | ||||||||||||||||
MINA2 /
| Storing a message in a JCR compliant repository like Apache Jackrabbit | Working with Apache MINA 2.x | ||||||||||||||||
Mock /
| For performing JDBC queries and operationsJetty / camel-jettytesting routes and mediation rules using mocks | |||||||||||||||||
MLLP /
| jetty
| hostName[
| ]
| /resourceUri][
|
For exposing services over HTTP | The MLLP component is specifically designed to handle the nuances of the MLLP protocol and provide the functionality required by Healthcare providers to communicate with other systems using the MLLP protocol | ||||||||||||
MongoDB / | JGroups / camel-jgroups
| jgroups
| clusterName
| The | ||||||||||||||
Code Block | none | none | Interacts with MongoDB databases and collections. Offers producer endpoints to perform CRUD-style operations and more against databases and collections, as well as consumer endpoints to listen on collections and dispatch objects to Camel routes | |||||||||||||||
MongoDB GridFS / | ||||||||||||||||||
jms:[queue:|topic:]destinationName[?options]
| Working with JMS providers | JMX / camel-jmx
| jmx://platform
| Sending and receiving files via MongoDB's GridFS system. Note: for Camel < 2.19, the URI syntax is gridfs:dbName[?options] | ||||||||||||||
MQTT / | For working with JMX notification listeners | JPA / camel-jpa
| For using a database as a queue via the JPA specification for working with OpenJPA, Hibernate or TopLink | Component for communicating with MQTT M2M message brokers | ||||||||||||||
MSV /
| Support for the scp protocol | Validates the payload of a message using the MSV Library | ||||||||||||||||
Mustache /
| For integrating with data queues on an AS/400 (aka System i, IBM i, i5, ...) system | Generates a response using a Mustache template | ||||||||||||||||
MVEL /
| For producing to or consuming from Kestrel queues | Generates a response using an MVEL template | ||||||||||||||||
MyBatis /
| For producing to or consuming to Krati datastores | Performs a query, poll, insert, update or delete in a relational database using MyBatis | ||||||||||||||||
Nagios /
| Executes Languages scripts | |||||||||||||||||
NATS / | LDAP / camel-ldap
| ldap
| host[:port][
|
Performing searches on LDAP servers (<scope> must be one of object|onelevel|subtree) |
| For messaging with the NATS platform. | ||||||||||||
Netty /
| Uses Jakarta Commons Logging to log the message exchange to some underlying logging system like log4j |
| Working with TCP and UDP protocols using Java NIO based capabilities offered by the Netty project | |||||||||||||||
Netty4 / | Lucene / camel-lucene
| lucene:searcherName:<insert|query>
| Uses Apache Lucene to perform Java-based indexing and full text based searches using advanced analysis/tokenization capabilities | Working with TCP and UDP protocols using Java NIO based capabilities offered by the Netty project | ||||||||||||||
Netty HTTP /
| Working with Apache MINA 1.x | Netty HTTP server and client using the Netty project | ||||||||||||||||
Netty4 HTTP / | MINA2 / camel-mina2
| mina2:[tcp|udp|vm]:host[:port]
| Working with Apache MINA 2Netty HTTP server and client using the Netty project 4.x | |||||||||||||||
Olingo2 / | core
| mock:name
| For testing routes and mediation rules using mocks | Communicates with OData 2.0 services using Apache Olingo 2.0. | ||||||||||||||
Openshift /
| Interacts with MongoDB databases and collections. Offers producer endpoints to perform CRUD-style operations and more against databases and collections, as well as consumer endpoints to listen on collections and dispatch objects to Camel routes | To manage your Openshift applications. | ||||||||||||||||
OptaPlanner /
| Component for communicating with MQTT M2M message brokers | Solves the planning problem contained in a message with OptaPlanner. | ||||||||||||||||
Paho / | MSV / camel-msv
| msv
| someLocalOrRemoteResource
| Validates the payload of a message using the MSV Library | Paho component provides connector for the MQTT messaging protocol using the Paho library. | |||||||||||||
Pax-Logging /
| Generates a response using a Mustache template | |||||||||||||||||
Code Block | none | none | mvel:templateName
| Receiving Pax-Logging events in OSGi | ||||||||||||||
PDF /
|
Generates a response using an MVEL template | MyBatis / camel-mybatisAllows to work with Apache PDFBox PDF documents | ||||||||||||||||
PGEvent /
| mybatis
| //statementName
|
Allows for Producing/Consuming PostgreSQL events related to the LISTEN/NOTIFY commands added since PostgreSQL 8.3 |
POP3 / | Performs a query, poll, insert, update or delete in a relational database using MyBatis | Nagios / camel-nagios
| Receiving email using POP3 and JavaMail | |||||||||||
POP3S /
| Working with TCP and UDP protocols using Java NIO based capabilities offered by the Netty project | ... | ||||||||||||
Printer /
| Netty HTTP server and client using the Netty project |
| The printer component facilitates creation of printer endpoints to local, remote and wireless printers. The endpoints provide the ability to print camel directed payloads when utilized on camel routes. | |||||||||||
Properties /
| Solves the planning problem contained in a message with OptaPlanner. | The properties component facilitates using property placeholders directly in endpoint URI definitions. | ||||||||||||
Quartz /
| Receiving Pax-Logging events in OSGi |
| Provides a scheduled delivery of messages using the Quartz 1.x scheduler | |||||||||||
Quartz2 /
| Receiving email using POP3 and JavaMail | Provides a scheduled delivery of messages using the Quartz 2.x scheduler | ||||||||||||
Quickfix /
| ... |
| Implementation of the QuickFix for Java engine which allow to send/receive FIX messages | |||||||||||
RabbitMQ /
| The printer component facilitates creation of printer endpoints to local, remote and wireless printers. The endpoints provide the ability to print camel directed payloads when utilized on camel routes. | Component for integrating with RabbitMQ | ||||||||||||
Ref / Properties /
| The properties component facilitates using property placeholders directly in endpoint uri definitions. |
| Component for lookup of existing endpoints bound in the Registry. | |||||||||||
Rest / | Quartz / camel-quartz
| quartz://groupName/timerName
|
Provides a scheduled delivery of messages using the Quartz 1.x scheduler | Component for consuming Restful resources supporting the Rest DSL and plugins to other Camel rest components. | ||||||||||
Restlet /
| Provides a scheduled delivery of messages using the Quartz 2.x scheduler | Component for consuming and producing Restful resources using Restlet | ||||||||||||
REST Swagger / camel-rest-swagger | Quickfix / camel-quickfix
| quickfix:configFile
| Implementation of the QuickFix for Java engine which allow to send/receive FIX messages | Component for accessing REST resources using Swagger specification as configuration. | ||||||||||
RMI /
| Component for integrating Working with RabbitMQRMI | |||||||||||||
| Component for lookup of existing endpoints bound in the Registry. |
| Validates the payload of a message using RelaxNG Compact Syntax | |||||||||||
RNG /
| Component for consuming and producing Restful resources using Restlet | Validates the payload of a message using RelaxNG | ||||||||||||
Routebox /
| Working with RMI |
| Facilitates the creation of specialized endpoints that offer encapsulation and a strategy/map based indirection service to a collection of camel routes hosted in an automatically created or user injected camel context | |||||||||||
RSS /
| Validates the payload of a message using RelaxNG Compact Syntax | Working with ROME for RSS integration, such as consuming an RSS feed. | ||||||||||||
Salesforce /
| Validates the payload of a message using RelaxNG | To integrate with Salesforce | ||||||||||||
SAP NetWeaver /
| Facilitates the creation of specialized endpoints that offer encapsulation and a strategy/map based indirection service to a collection of camel routes hosted in an automatically created or user injected camel context | To integrate with SAP NetWeaver Gateway | ||||||||||||
Scheduler /
| Working with ROME for RSS integration, such as consuming an RSS feed. |
| Used to generate message exchanges when a scheduler fires. The scheduler has more functionality than the timer component. | |||||||||||
schematron / | Salesforce / camel-salesforce
| salesforce:topic[?
| To integrate with Salesforce | Camel component of Schematron which supports to validate the XML instance documents. | ||||||||||
SEDA /
| To integrate with SAP NetWeaver Gateway | SEDA / camel-coreAsynchronous call to another endpoint in the same CamelContext | ||||||||||||
ServiceNow /
| seda
| someName
| ]
Asynchronous call to another endpoint in the same Camel Context
| Camel component for ServiceNow | ||||||||||
SERVLET /
| For exposing services over HTTP through the servlet which is deployed into the Web container. | |||||||||||||
SFTP /
| Sending and receiving files over SFTP (FTP over SSH). | |||||||||||||
Sip /
| Publish/Subscribe communication capability using the Telecom SIP protocol. RFC3903 - Session Initiation Protocol (SIP) Extension for Event | |||||||||||||
SIPS /
| ... | |||||||||||||
SJMS /
| A ground up implementation of a JMS client | |||||||||||||
SJMS Batch /
| ... | SJMS / camel-sjmsA specialized JMS component for highly-performant transactional batch consumption from a queue. | ||||||||||||
Slack /
| sjms:[queue:|topic:]destinationName
|
A ground up implementation of a JMS clientThe slack component allows you to connect to an instance of Slack and delivers a message contained in the message body via a pre established Slack incoming webhook . | ||||||||||||
SMTP /
| Sending email using SMTP and JavaMail | |||||||||||||
SMTP /
| ... | |||||||||||||
SMPP /
| To send and receive SMS using Short Messaging Service Center using the JSMPP library | |||||||||||||
SMPPS /
| ... | |||||||||||||
SNMP /
| Polling OID values and receiving traps using SNMP via SNMP4J library | |||||||||||||
Solr /
| Uses the Solrj client API to interface with an Apache Lucene Solr server | |||||||||||||
Apache Spark /
| Polling OID values and receiving traps using SNMP via SNMP4J library | Bridges Apache Spark computations with Camel endpoints. | ||||||||||||
Spark-rest / | Solr / camel-solr
| solr
| hostName[:port]/solr
|
Uses the Solrj client API to interface with an Apache Lucene Solr serverFor easily defining REST services endpoints using Spark REST Java library. | ||||||||||
Splunk /
| For working with Splunk | |||||||||||||
SpringBatch /
| To bridge Camel and Spring Batch | |||||||||||||
SpringIntegration /
| The bridge component of Camel and Spring Integration | |||||||||||||
Spring LDAP /
| Camel wrapper for Spring LDAP | |||||||||||||
Spring Redis /
| Component for consuming and producing from Redis key-value store Redis | |||||||||||||
Spring Web Services /
| Client-side support for accessing web services, and server-side support for creating your own contract-first web services using Spring Web Services | |||||||||||||
SQL /
| Performing SQL queries using JDBC | |||||||||||||
SQL Stored Procedure /
| Performing SQL queries using Stored Procedure calls | |||||||||||||
SSH component /
| For sending commands to a SSH server | |||||||||||||
StAX /
| Process messages through a SAX ContentHandler. | |||||||||||||
Stream /
| Read or write to an input/output/error/file stream rather like unix pipes | |||||||||||||
Stomp /
| For communicating with Stomp compliant message brokers, like Apache ActiveMQ or ActiveMQ Apollo | |||||||||||||
StringTemplate /
| Generates a response using a String Template | |||||||||||||
Stub /
| Allows you to stub out some physical middleware endpoint for easier testing or debugging | |||||||||||||
Telegram /
| Allows | you to stub out some physical middleware endpoint for easier testing or debuggingto exchange data with the Telegram messaging network | ||||||||||||
Test /
| Creates a Mock endpoint which expects to receive all the message bodies that could be polled from the given underlying endpoint | |||||||||||||
Timer /
| Used to generate message exchanges when a timer fires You can only consume events from this endpoint. | |||||||||||||
Twitter /
| A twitter endpoint | |||||||||||||
Undertow /
| HTTP server and client using the light-weight Undertow server. | |||||||||||||
Validation /
| Validates the payload of a message using XML Schema and JAXP Validation | |||||||||||||
Velocity /
| Generates a response using an Apache Velocity template | |||||||||||||
Vertx /
| Working with the vertx event bus | |||||||||||||
VM /
| Asynchronous call to another endpoint in the same JVM | |||||||||||||
Weather /
| Polls the weather information from Open Weather Map | |||||||||||||
Websocket /
| Communicating with Websocket clients | |||||||||||||
XML Security /
| Used to sign and verify exchanges using the XML signature specification. | |||||||||||||
XMPP /
| Working with XMPP and Jabber | |||||||||||||
XQuery /
| Generates a response using an XQuery template | |||||||||||||
XSLT /
| Generates a response using an XSLT template | |||||||||||||
Yammer /
| Allows you to interact with the Yammer enterprise social network | |||||||||||||
Zookeeper /
| Working with ZooKeeper cluster(s) |