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 devices | |||||||||||||||
Atmosphere-Websocket /
| To exchange data with external Websocket clients using Atmosphere | |||||||||||||||
Atom /
| 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 DynamoDB Streams (DDB Streams). | |||||||||||||||
| For working with Amazon's Elastic Compute Cloud (EC2). | |||||||||||||||
| For working with Amazon's SimpleDB (SDB). | |||||||||||||||
| For working with Amazon's Simple Email Service (SES). | |||||||||||||||
| For Messaging with Amazon's Simple Notification Service (SNS). | |||||||||||||||
| For Messaging with Amazon's Simple Queue Service (SQS). | |||||||||||||||
| For Messaging with Amazon's Simple Workflow Service (SWF). | |||||||||||||||
| For working with Amazon's Simple Storage Service (S3). | |||||||||||||||
Bean /
| 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). | |||||||||||||||
Beanstalk /
| For working with Amazon's Beanstalk. | |||||||||||||||
Bean Validator /
| Validates the payload of a message using the Java Validation API (JSR 303 and JAXP Validation) and its reference implementation Hibernate Validator | |||||||||||||||
Box /
| 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 /
| 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 /
| The cache component facilitates creation of caching endpoints and processors using EHCache as the cache implementation. | |||||||||||||||
Cassandra /
| For integrating with Apache Cassandra. | |||||||||||||||
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 | |||||||||||||||
Chronicle Engine / | cmis
| cmis
| /cmisServerUrl
| Chronicle Engine is a high performance, low latency, reactive processing framework. | ||||||||||||
Chunk /
| Generates a response using a Chunk template | |||||||||||||||
CMIS /
| Uses the Apache Chemistry client API Uses the Apache Chemistry client API to interface with CMIS supporting CMS | |||||||||||||||
Cometd /
| Used to deliver messages using the jetty cometd implementation of the bayeux protocolContext | |||||||||||||||
Consul / | context
| context
| camelContextId:localEndpointName
| For interfacing with an Consul. | ||||||||||||
Context /
| Used to refer to 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) /
| 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 | |||||||||||||||
DropboxDocker /
| The dropbox: component allows you to treat Dropbox remote folders as a producer or consumer of messages. | To communicate with Docker | ||||||||||||||
Dozer / | EJB / camel-ejb
| 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.ElasticSearch | |||||||||||||||
Ehcache / | elasticsearch
| elasticsearch
| clusterName
|
For interfacing with an ElasticSearch server. | 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 / 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 libraryFOP | |||||||||||||||
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 DriveCalendar / camel-google-drivecalendar
| Supports interaction with Google DriveCalendar's REST API. | |||||||||||||||
GMail Google Drive / camel-google-gaedrive
| 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. | Geocoder |||||||||||||||
geocoder |
| 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. | |||||||||||||||
Code Block | none | none | ||||||||||||||
github://endpoint[?options]
| For interacting with GitHub | |||||||||||||||
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 / | hl7
| mina2
| tcp:
| hostName
| [
| For sending/receiving messages to Hipchat using v2 API | ||||||||||
HL7 /
| For ]For working with the HL7 MLLP protocol and the HL7 model 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 iBATISIMAP | |||||||||||||||
Ignite / | mail
| imap
| /[username@]hostName[:port]
|
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 /
| Receiving email using IMAP | |||||||||||||||
IMAPS /
| ... | |||||||||||||||
IRC /
| For IRC communication | |||||||||||||||
IronMQ /
| For working with IronMQ a elastic and durable hosted message queue as a service. | |||||||||||||||
JavaSpace / | Receiving email using IMAP | IMAPS / camel-mail
| ... | Sending and receiving messages through JavaSpace | ||||||||||||
jBPM / | IRC / camel-irc
| irc
| [login@]
| #room
| For IRC communication | Sending messages through kie-remote-client API to jBPM. | ||||||||||
jcache / | JavaSpace / camel-javaspace
| javaspace:jini://hostName
|
Sending and receiving messages through JavaSpaceThe JCache component facilitates creation of caching endpoints and processors using JCache / jsr107 as the cache implementation. | |||||||||||||
jclouds /
| For interacting with cloud compute & blobstore service via jclouds | |||||||||||||||
JCR /
| Storing a message in a JCR compliant repository like Apache Jackrabbit | |||||||||||||||
JDBC /
| For performing JDBC queries and operations | |||||||||||||||
Jetty /
| For exposing or consuming services over HTTP | |||||||||||||||
JGroups /
| The | |||||||||||||||
JIRA /
| For interacting with JIRA | |||||||||||||||
JMS /
| Working with JMS providers | |||||||||||||||
JMX /
| For working with JMX notification listeners | |||||||||||||||
JPA /
| For using a database as a queue via the JPA specification for working with OpenJPA, Hibernate or TopLink | |||||||||||||||
JOLT /
| 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 / |
For using a database as a queue via the JPA specification for working with OpenJPA, Hibernate or TopLink | Jsch /
| Support for the scp protocol | |||||||||||||
JT/400 /
| For integrating with data queues on an AS/400 (aka System i, IBM i, i5, ...) system | |||||||||||||||
Kafka /
| For producing to or consuming from Apache Kafka message brokers. | |||||||||||||||
Kestrel /
| For producing to or consuming from Kestrel queues | |||||||||||||||
Krati /
| For producing to or consuming to Krati datastores | |||||||||||||||
Kubernetes /
| 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 producing to or consuming to Krati datastores | Language /
| Executes Languages scripts | |||||||||||||
LDAP /
| Performing searches on LDAP servers (<scope> must be one of object|onelevel|subtree) | |||||||||||||||
LinkedIn /
| Component for retrieving LinkedIn user profiles, connections, companies, groups, posts, etc. using LinkedIn REST API. | |||||||||||||||
Log /
| 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 /
| Uses the Lumberjack protocol for retrieving logs (from Filebeat for instance) | |||||||||||||||
Metrics /
| Uses Metrics to collect application statistics directly from Camel routes. | |||||||||||||||
MINA /
| Working with Apache MINA 1.x | |||||||||||||||
MINA2 /
| Working with Apache MINA 2.x | |||||||||||||||
Mock /
| For testing routes and mediation rules using mocks | |||||||||||||||
MLLP /
| 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 /
| For testing routes and mediation rules using mocks | |||||||||||||||
Code Block | none | none | ||||||||||||||
mongodb:connectionBean[?options]
| 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 | 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 /
| Sending and receiving files via MongoDB's GridFS system. Note: for Camel < 2.19, the URI syntax is gridfs:dbName[?options] | |||||||||||||||
| Component for communicating with MQTT M2M message brokers | |||||||||||||||
MSV /
| Validates the payload of a message using the MSV Library | |||||||||||||||
Mustache /
| Generates a response using a Mustache template | |||||||||||||||
MVEL /
| Generates a response using an MVEL template | |||||||||||||||
MyBatis /
| Performs a query, poll, insert, update or delete in a relational database using MyBatis | |||||||||||||||
Nagios /
| ||||||||||||||||
NATS /
|
Sending passive checks to Nagios using JSendNSCA
| For messaging with the NATS platform. | ||||||||||||||
Netty /
| Working with TCP and UDP protocols using Java NIO based capabilities offered by the Netty project | |||||||||||||||
Netty4 /
| Working with TCP and UDP protocols using Java NIO based capabilities offered by the Netty project | |||||||||||||||
Netty HTTP /
| Netty HTTP server and client using the Netty project | |||||||||||||||
Netty4 HTTP /
| Netty HTTP server and client using the Netty project 4.x | |||||||||||||||
Olingo2 /
| Communicates with OData 2.0 services using Apache Olingo 2.0..0. | |||||||||||||||
Openshift /
| To manage your Openshift applications. | |||||||||||||||
OptaPlanner /
| Solves the planning problem contained in a message with OptaPlanner. | |||||||||||||||
Paho / | Openshift / camel-openshift
| openshift
| clientId
| To manage your Openshift applications. | Paho component provides connector for the MQTT messaging protocol using the Paho library. | |||||||||||
Pax-Logging /
| Receiving Pax-Logging events in OSGi | |||||||||||||||
PDF /
|
Solves the planning problem contained in a message with OptaPlanner. | Pax-Logging Allows to work with Apache PDFBox PDF documents | ||||||||||||||
PGEvent / | / camel-paxlogging
| |||||||||||||||
paxlogging:appender
|
| Allows for Producing/Consuming PostgreSQL events related to the LISTEN/NOTIFY commands added since PostgreSQL 8.3 |
POP3 /
| Receiving email using POP3 and JavaMail | |||||||||||||
POP3S /
| ... | |||||||||||||
Printer /
| 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 /
| The properties component facilitates using property placeholders directly in endpoint uri URI definitions. | |||||||||||||
Quartz /
| Provides a scheduled delivery of messages using the Quartz 1.x scheduler | |||||||||||||
Quartz2 /
| 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 /
| Component for integrating with RabbitMQ | |||||||||||||
Ref /
| Component for lookup of existing endpoints bound in the Registry. | |||||||||||||
Rest /
| Component for consuming Restful resources supporting the Rest DSL and plugins to other Camel rest components. | |||||||||||||
Restlet /
| Component for consuming and producing Restful resources using RestletRestful resources using Restlet | |||||||||||||
REST Swagger / camel-rest-swagger
| Component for accessing REST resources using Swagger specification as configuration. | |||||||||||||
RMI /
| Working with RMI | |||||||||||||
RNC /
| Validates the payload of a message using RelaxNG Compact Syntax | |||||||||||||
RNG /
| Validates the payload of a message using RelaxNG | |||||||||||||
Routebox /
| 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 /
| Working with ROME for RSS integration, such as consuming an RSS feed. | |||||||||||||
Salesforce /
| To integrate with Salesforce | |||||||||||||
SAP NetWeaver /
| To integrate with SAP NetWeaver Gateway | |||||||||||||
Scheduler /
| Used to generate message exchanges when a scheduler fires. The scheduler has more functionality than the timer component. | |||||||||||||
schematron /
| Camel component of Schematron which supports to validate the XML instance documents. | |||||||||||||
SEDA /
| Asynchronous call to another endpoint in the same Camel Contextendpoint in the same CamelContext | |||||||||||||
ServiceNow /
| 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 / camel-sip Code Block | | none | none | ||||||||||
sips://user@hostName[:port][?options]
| ... | |||||||||||||
SIPS /
| ... | |||||||||||||
SJMS /
| A ground up implementation of a JMS client | |||||||||||||
SJMS Batch /
| A specialized JMS component for highly-performant transactional batch consumption from a queue. | |||||||||||||
Slack / | SJMS / camel-sjms
| 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 /
| Bridges Apache Spark computations with Camel endpoints. | |||||||||||||
Spark-rest /
| For easily defining REST services endpoints using Spark REST Java library. | |||||||||||||
Splunk /
| For working with Splunk | |||||||||||||
SpringBatch / | boot
| Camel auto-configuration for Spring Boot applications. | SpringBatch / camel-
| |||||||||||
|
Code Block | | none | none | ||||||||||
|
://jobName[?options] |
To bridge Camel and Spring Batch
SpringIntegration / camel-spring-integration
Code Block | ||||
---|---|---|---|---|
| ||||
spring-integration:defaultChannelName[?options] |
The bridge component of Camel and Spring Integration
Spring LDAP / camel-spring-ldap
Code Block | ||||
---|---|---|---|---|
| ||||
spring-ldap:springLdapTemplateBean[?options] |
Camel wrapper for Spring LDAP
Spring Redis / camel-spring-redis
Code Block | ||||
---|---|---|---|---|
| ||||
spring-redis://hostName:port[?options] |
Component for consuming and producing from Redis key-value store Redis
Spring Web Services / camel-spring-ws
Code Block | ||||
---|---|---|---|---|
| ||||
spring-ws:[mapping-type:]address[?options] |
Client-side support for accessing web services, and server-side support for creating your own contract-first web services using Spring Web Services
SQL / camel-sql
Code Block | ||||
---|---|---|---|---|
| ||||
sql:select * from table where id=#[?options] |
Performing SQL queries using JDBC
SQL Stored Procedure / camel-sql
Code Block | ||||
---|---|---|---|---|
| ||||
sql-stored:template[?options] |
Performing SQL queries using Stored Procedure calls
SSH component / camel-ssh
Code Block | ||||
---|---|---|---|---|
| ||||
ssh:[username[:password]@]hostName[:port][?options] |
For sending commands to a SSH server
StAX / camel-stax
Code Block | ||||
---|---|---|---|---|
| ||||
stax:(contentHandlerClassName|#myHandler) |
Process messages through a SAX ContentHandler.
Stream / camel-stream
Code Block | ||||
---|---|---|---|---|
| ||||
stream:[in|out|err|file|header|url][?options] |
Read or write to an input/output/error/file stream rather like unix pipes
Stomp / camel-stomp
Code Block | ||||
---|---|---|---|---|
| ||||
stomp:queue:destinationName[?options] |
For communicating with Stomp compliant message brokers, like Apache ActiveMQ or ActiveMQ Apollo
StringTemplate / camel-stringtemplate
Code Block | ||||
---|---|---|---|---|
| ||||
string-template:templateName[?options] |
Generates a response using a String Template
Stub / camel-core
Code Block | ||||
---|---|---|---|---|
| ||||
stub:someOtherCamelUri[?options]
|
Allows you to stub out some physical middleware endpoint for easier testing or debugging
Telegram / camel-
telegram
Code Block | ||||
---|---|---|---|---|
|
telegram://bots/authToken[?options] |
Allows
to exchange data with the Telegram messaging network
Test / camel-spring
Code Block | ||||
---|---|---|---|---|
| ||||
test:expectedMessagesEndpointUri[?options] |
Creates a Mock endpoint which expects to receive all the message bodies that could be polled from the given underlying endpoint
Timer / camel-core
Code Block | ||||
---|---|---|---|---|
| ||||
timer:timerName[?options] |
Used to generate message exchanges when a timer fires You can only consume events from this endpoint.
Twitter / camel-twitter
Code Block | ||||
---|---|---|---|---|
| ||||
twitter://endpoint[?options] |
A twitter endpoint
Undertow / camel-undertow
Code Block | ||||
---|---|---|---|---|
| ||||
undertow://host:port/context-path[?options] |
HTTP server and client using the light-weight Undertow server.
Validation / camel-core
(camel-spring for Camel 2.8 or older)
Code Block | ||||
---|---|---|---|---|
| ||||
validation:someLocalOrRemoteResource[?options] |
Validates the payload of a message using XML Schema and JAXP Validation
Velocity / camel-velocity
Code Block | ||||
---|---|---|---|---|
| ||||
velocity:templateName[?options] |
Generates a response using an Apache Velocity template
Vertx / camel-vertx
Code Block | ||||
---|---|---|---|---|
| ||||
vertx:eventBusName |
Working with the vertx event bus
VM / camel-core
Code Block | ||||
---|---|---|---|---|
| ||||
vm:queueName[?options] |
Asynchronous call to another endpoint in the same JVM
Weather / camel-weather
Code Block | ||||
---|---|---|---|---|
| ||||
wweather://name[?options] |
Polls the weather information from Open Weather Map
Websocket / camel-websocket
Code Block | ||||
---|---|---|---|---|
| ||||
websocket://hostname[:port][/resourceUri][?options] |
Communicating with Websocket clients
XML Security / camel-xmlsecurity
Code Block | ||||
---|---|---|---|---|
| ||||
xmlsecurity:<sign|verify>:name[?options] |
Used to sign and verify exchanges using the XML signature specification.
XMPP / camel-xmpp
Code Block | ||||
---|---|---|---|---|
| ||||
xmpp://[login@]hostname[:port][/participant][?options] |
Working with XMPP and Jabber
XQuery / camel-saxon
Code Block | ||||
---|---|---|---|---|
| ||||
xquery:someXQueryResource |
Generates a response using an XQuery template
XSLT / camel-core
(camel-spring for Camel 2.8 or older)
Code Block | ||||
---|---|---|---|---|
| ||||
xslt:templateName[?options] |
Generates a response using an XSLT template
Yammer / camel-yammer
Code Block | ||||
---|---|---|---|---|
| ||||
yammer://function[?options] |
Allows you to interact with the Yammer enterprise social network
Zookeeper / camel-zookeeper
Code Block | ||||
---|---|---|---|---|
| ||||
zookeeper://zookeeperServer[:port][/path][?options] |
Working with ZooKeeper cluster(s)
...