Components
Component references are references used to place a component in an assembly. Apache Component references provides various references that offers services for messaging, sending data, notifcations and various other services that can not only resolve easy messaging and transferring data but also provide securing of data.
Below is the list of components that are provided by Apache Camel.
Core Components
Below is the list of core components that are provided by Apache Camel.
Number of Core Components: 26 in 1 JAR artifacts (1 deprecated)
| Component | Artifact | Status | Since | Description |
|---|---|---|---|---|
camel-core |
1.0 |
The bean component is for invoking Java beans from Camel. |
||
camel-core |
deprecated |
2.11 |
The binding component is used for as a of wrapping an Endpoint in a contract with a data format. |
|
camel-core |
1.3 |
The browse component is used for viewing the messages received on endpoints that supports BrowsableEndpoint. |
||
camel-core |
2.4 |
The Class Component is for invoking Java Classes (Java beans) from Camel. |
||
camel-core |
2.11 |
The controlbus component provides easy management of Camel applications based on the Control Bus EIP pattern. |
||
camel-core |
2.12 |
The dataformat component is used for working with Data Formats as if it was a regular Component supporting Endpoints and URIs. |
||
camel-core |
1.3 |
The dataset component provides a mechanism to easily perform load & soak testing of your system. |
||
camel-core |
1.0 |
The direct component provides direct, synchronous call to another endpoint from the same CamelContext. |
||
camel-core |
2.10 |
The direct-vm component provides direct, synchronous call to another endpoint from any CamelContext in the same JVM. |
||
camel-core |
1.0 |
The file component is used for reading or writing files. |
||
camel-core |
2.5 |
The language component allows you to send a message to an endpoint which executes a script by any of the supported Languages in Camel. |
||
camel-core |
1.1 |
The log component logs message exchanges to the underlying logging mechanism. |
||
camel-core |
1.0 |
The mock component is used for testing routes and mediation rules using mocks. |
||
camel-core |
2.3 |
The properties component is used for using property placeholders in endpoint uris. |
||
camel-core |
1.2 |
The ref component is used for lookup of existing endpoints bound in the Registry. |
||
camel-core |
2.14 |
The rest component is used for either hosting REST services (consumer) or calling external REST services (producer). |
||
camel-core |
2.16 |
The rest-api component is used for providing Swagger API of the REST services which has been defined using the rest-dsl in Camel. |
||
camel-core |
2.21 |
The saga component provides access to advanced options for managing the flow in the Saga EIP. |
||
camel-core |
2.15 |
The scheduler component is used for generating message exchanges when a scheduler fires. |
||
camel-core |
1.1 |
The seda component provides asynchronous call to another endpoint from any CamelContext in the same JVM. |
||
camel-core |
2.10 |
The stub component provides a simple way to stub out any physical endpoints while in development or testing. |
||
camel-core |
1.3 |
The test component extends the mock component by on startup to pull messages from another endpoint to set the expected message bodies. |
||
camel-core |
1.0 |
The timer component is used for generating message exchanges when a timer fires. |
||
camel-core |
1.1 |
Validates the payload of a message using XML Schema and JAXP Validation. |
||
camel-core |
1.1 |
The vm component provides asynchronous call to another endpoint from the same CamelContext. |
||
camel-core |
1.3 |
Transforms the message using a XSLT template. |
Components
Below is the list of non-core components that are provided by Apache Camel.
Number of Non-Core Components: 293 in 210 JAR artifacts (26 deprecated)
| Component | Artifact | Status | Since | Description |
|---|---|---|---|---|
camel-ahc |
2.8 |
To call external HTTP services using Async Http Client. |
||
camel-ahc-ws |
2.14 |
To exchange data with external Websocket servers using Async Http Client. |
||
camel-amqp |
1.2 |
Messaging with AMQP protocol using Apache QPid Client. |
||
camel-flink |
2.18 |
The flink component can be used to send DataSet jobs to Apache Flink cluster. |
||
camel-pulsar |
2.24 |
Camel Apache Pulsar Component |
||
camel-spark |
2.17 |
The spark component can be used to send RDD or DataFrame jobs to Apache Spark cluster. |
||
camel-apns |
2.8 |
For sending notifications to Apple iOS devices. |
||
camel-as2 |
2.22 |
Component used for transferring data secure and reliable over the internet using the AS2 protocol. |
||
camel-asterisk |
2.18 |
The asterisk component is used to interact with Asterisk PBX Server. |
||
camel-atmos |
2.15 |
The atmos component is used for integrating with EMC’s Atomos Storage. |
||
camel-atmosphere-websocket |
2.14 |
To exchange data with external Websocket clients using Atmosphere. |
||
camel-atom |
1.2 |
The atom component is used for consuming Atom RSS feeds. |
||
camel-atomix |
2.20 |
The atomix-map component is used to access Atomix’s distributed map. |
||
camel-atomix |
2.20 |
The atomix-messaging component is used to access Atomix’s group messaging. |
||
camel-atomix |
2.20 |
The atomix-multimap component is used to access Atomix’s distributed multi map. |
||
camel-atomix |
2.20 |
The atomix-queue component is used to access Atomix’s distributed queue. |
||
camel-atomix |
2.20 |
The atomix-set component is used to access Atomix’s distributed set. |
||
camel-atomix |
2.20 |
The atomix-value component is used to access Atomix’s distributed value. |
||
camel-avro |
2.10 |
Working with Apache Avro for data serialization. |
||
Summary of AWS components |
||||
camel-aws |
2.11 |
The aws-cw component is used for sending metrics to an Amazon CloudWatch. |
||
camel-aws |
2.10 |
The aws-ddb component is used for storing and retrieving data from Amazon’s DynamoDB service. |
||
camel-aws |
2.17 |
The aws-ddbstream component is used for working with Amazon DynamoDB Streams. |
||
camel-aws |
2.16 |
The aws-ec2 is used for managing Amazon EC2 instances. |
||
camel-aws |
2.23 |
The aws-iam is used for managing Amazon IAM |
||
camel-aws |
2.17 |
The aws-kinesis component is for consuming and producing records from Amazon Kinesis Streams. |
||
camel-aws |
2.19 |
The aws-kinesis-firehose component is used for producing Amazon’s Kinesis Firehose streams. |
||
camel-aws |
2.21 |
The aws-kms is used for managing Amazon KMS |
||
camel-aws |
2.20 |
The aws-lambda is used for managing and invoking functions from Amazon Lambda. |
||
camel-aws |
2.21 |
The aws-mq is used for managing Amazon MQ instances. |
||
camel-aws |
2.8 |
The aws-s3 component is used for storing and retrieving objecct from Amazon S3 Storage Service. |
||
camel-aws |
2.9 |
The aws-ses component is used for sending emails with Amazon’s SES service. |
||
camel-aws |
2.8 |
The aws-sns component is used for sending messages to an Amazon Simple Notification Topic. |
||
camel-aws |
2.6 |
The aws-sqs component is used for sending and receiving messages to Amazon’s SQS service. |
||
camel-aws |
2.13 |
The aws-swf component is used for managing workflows from Amazon Simple Workflow. |
||
camel-aws |
2.9 |
The aws-sdb component is for storing and retrieving data from/to Amazon’s SDB service. |
||
Summary of Azure components |
||||
camel-azure |
2.19 |
The azure-blob component is used for storing and retrieving blobs from Azure Storage Blob Service. |
||
camel-azure |
2.19 |
The azure-queue component is used for storing and retrieving messages from Azure Storage Queue Service. |
||
camel-bean-validator |
2.3 |
The Validator component performs bean validation of the message body using the Java Bean Validation API. |
||
camel-beanstalk |
2.15 |
The beanstalk component is used for job retrieval and post-processing of Beanstalk jobs. |
||
camel-bonita |
2.19 |
Used for communicating with a remote Bonita BPM process engine. |
||
camel-box |
2.14 |
For uploading downloading and managing files folders groups collaborations etc on box DOT com. |
||
camel-braintree |
2.17 |
The braintree component is used for integrating with the Braintree Payment System. |
||
camel-caffeine |
2.20 |
The caffeine-cache component is used for integration with Caffeine Cache. |
||
camel-caffeine |
2.20 |
The caffeine-loadcache component is used for integration with Caffeine Load Cache. |
||
camel-context |
deprecated |
2.7 |
The context component allows to send/receive messages between Camel routes in a black box way. |
|
camel-cassandraql |
2.15 |
The cql component aims at integrating Cassandra 2.0 using the CQL3 API (not the Thrift API). |
||
camel-chronicle |
deprecated |
2.18 |
The camel chronicle-engine component let you leverage the power of OpenHFT’s Chronicle-Engine. |
|
camel-chunk |
2.15 |
Transforms the message using a Chunk template. |
||
camel-cmis |
2.11 |
The cmis component uses the Apache Chemistry client API and allows you to add/read nodes to/from a CMIS compliant content repositories. |
||
camel-coap |
2.16 |
The coap component is used for sending and receiving messages from COAP capable devices. |
||
camel-cometd |
2.0 |
The cometd component is a transport for working with the Jetty implementation of the cometd/bayeux protocol. |
||
camel-consul |
2.18 |
The camel consul component allows you to work with Consul, a distributed, highly available, datacenter-aware, service discovery and configuration system. |
||
camel-corda |
2.23 |
The corda component uses the corda-rpc to interact with corda nodes. |
||
camel-couchbase |
2.19 |
Represents a Couchbase endpoint that can query Views with a Poll strategy and/or produce various type of operations. |
||
camel-couchdb |
2.11 |
The couchdb component is used for integrate with CouchDB databases. |
||
camel-crypto |
2.3 |
The crypto component is used for signing and verifying exchanges using the Signature Service of the Java Cryptographic Extension (JCE). |
||
camel-crypto-cms |
2.20 |
The crypto cms component is used for encrypting data in CMS Enveloped Data format, decrypting CMS Enveloped Data, signing data in CMS Signed Data format, and verifying CMS Signed Data. |
||
camel-cxf |
1.0 |
The cxf component is used for SOAP WebServices using Apache CXF. |
||
camel-cxf |
2.0 |
The cxfrs component is used for JAX-RS REST services using Apache CXF. |
||
camel-digitalocean |
2.19 |
The DigitalOcean component allows you to manage Droplets and resources within the DigitalOcean cloud. |
||
camel-disruptor |
2.12 |
The disruptor component provides asynchronous SEDA behavior using LMAX Disruptor. |
||
camel-dns |
2.7 |
To lookup domain information and run DNS queries using DNSJava. |
||
camel-docker |
2.15 |
The docker component is used for managing Docker containers. |
||
camel-dozer |
2.15 |
The dozer component provides the ability to map between Java beans using the Dozer mapping library. |
||
camel-drill |
2.19 |
The drill component gives you the ability to quering into apache drill cluster. |
||
camel-dropbox |
2.14 |
For uploading, downloading and managing files, folders, groups, collaborations, etc on dropbox DOT com. |
||
camel-cache |
deprecated |
2.1 |
The cache component enables you to perform caching operations using EHCache as the Cache Implementation. |
|
camel-ehcache |
2.18 |
The ehcache component enables you to perform caching operations using Ehcache as cache implementation. |
||
camel-ejb |
deprecated |
2.4 |
The ejb component is for invoking EJB Java beans from Camel. |
|
camel-elasticsearch-rest |
2.21 |
The elasticsearch component is used for interfacing with ElasticSearch server using REST API. |
||
camel-elasticsearch |
deprecated |
2.11 |
The elasticsearch component is used for interfacing with ElasticSearch server. |
|
camel-elasticsearch5 |
deprecated |
2.19 |
The elasticsearch component is used for interfacing with ElasticSearch server using 5.x API. |
|
camel-elsql |
2.16 |
The elsql component is an extension to the existing SQL Component that uses ElSql to define the SQL queries. |
||
camel-etcd |
2.18 |
The camel etcd component allows you to work with Etcd, a distributed reliable key-value store. |
||
camel-exec |
2.3 |
The exec component can be used to execute OS system commands. |
||
camel-facebook |
2.14 |
The Facebook component provides access to all of the Facebook APIs accessible using Facebook4J. |
||
camel-fhir |
2.23 |
The fhir component is used for working with the FHIR protocol (health care). |
||
camel-flatpack |
1.4 |
The flatpack component supports fixed width and delimited file parsing via the FlatPack library. |
||
camel-fop |
2.10 |
The fop component allows you to render a message into different output formats using Apache FOP. |
||
camel-freemarker |
2.10 |
Transforms the message using a FreeMarker template. |
||
camel-ftp |
1.1 |
The ftp component is used for uploading or downloading files from FTP servers. |
||
camel-ftp |
2.2 |
The ftps (FTP secure SSL/TLS) component is used for uploading or downloading files from FTP servers. |
||
camel-ganglia |
2.15 |
The ganglia component is used for sending metrics to the Ganglia monitoring system. |
||
camel-geocoder |
2.12 |
The geocoder component is used for looking up geocodes (latitude and longitude) for a given address, or reverse lookup. |
||
camel-git |
2.16 |
The git component is used for working with git repositories. |
||
camel-github |
2.15 |
The github component is used for integrating Camel with github. |
||
camel-google-bigquery |
2.20 |
Google BigQuery data warehouse for analytics. |
||
camel-google-bigquery |
2.23 |
Google BigQuery data warehouse for analytics (using SQL queries). |
||
camel-google-calendar |
2.15 |
The google-calendar component provides access to Google Calendar. |
||
camel-google-calendar |
2.23 |
The google-calendar component provides access to Google Calendar in a streaming mode. |
||
camel-google-drive |
2.14 |
The google-drive component provides access to Google Drive file storage service. |
||
camel-google-mail |
2.15 |
The google-mail component provides access to Google Mail. |
||
camel-google-mail |
2.22 |
The google-mail component provides access to Google Mail. |
||
camel-google-pubsub |
2.19 |
Messaging client for Google Cloud Platform PubSub Service |
||
camel-google-sheets |
2.23 |
The google-sheets component provides access to Google Sheets. |
||
camel-google-sheets |
2.23 |
The google-sheets component provides access to Google Sheets. |
||
camel-gora |
2.14 |
The gora component allows you to work with NoSQL databases using the Apache Gora framework. |
||
camel-grape |
2.16 |
Grape component allows you to fetch, load and manage additional jars when CamelContext is running. |
||
camel-grpc |
2.19 |
The gRPC component allows to call and expose remote procedures via HTTP/2 with protobuf dataformat |
||
camel-guava-eventbus |
2.10 |
The guava-eventbus component provides integration bridge between Camel and Google Guava EventBus. |
||
2.7 |
Summary of Hazelcast components |
|||
camel-hazelcast |
2.7 |
The hazelcast-atomicvalue component is used to access Hazelcast atomic number, which is an object that simply provides a grid wide number (long). |
||
camel-hazelcast |
2.7 |
The hazelcast-instance component is used to consume join/leave events of the cache instance in the cluster. |
||
camel-hazelcast |
2.7 |
The hazelcast-list component is used to access Hazelcast distributed list. |
||
camel-hazelcast |
2.7 |
The hazelcast-map component is used to access Hazelcast distributed map. |
||
camel-hazelcast |
2.7 |
The hazelcast-multimap component is used to to access Hazelcast distributed multimap. |
||
camel-hazelcast |
2.7 |
The hazelcast-queue component is used to access Hazelcast distributed queue. |
||
camel-hazelcast |
2.16 |
The hazelcast-replicatedmap component is used to access Hazelcast replicated map. |
||
camel-hazelcast |
2.16 |
The hazelcast-ringbuffer component is used to access Hazelcast distributed ringbuffer. |
||
camel-hazelcast |
2.7 |
The hazelcast-seda component is used to access Hazelcast BlockingQueue. |
||
camel-hazelcast |
2.7 |
The camel Endpoint to access Hazelcast distributed set. |
||
camel-hazelcast |
2.15 |
The hazelcast-topic component is used to access Hazelcast distributed topic. |
||
camel-hbase |
2.10 |
For reading/writing from/to an HBase store (Hadoop database). |
||
camel-hdfs |
deprecated |
2.8 |
For reading/writing from/to an HDFS filesystem using Hadoop 1.x. |
|
camel-hdfs2 |
2.14 |
For reading/writing from/to an HDFS filesystem using Hadoop 2.x. |
||
camel-hipchat |
2.15 |
The hipchat component supports producing and consuming messages from/to Hipchat service. |
||
camel-http |
deprecated |
1.0 |
For calling out to external HTTP servers using Apache HTTP Client 3.x. |
|
camel-http4 |
2.3 |
For calling out to external HTTP servers using Apache HTTP Client 4.x. |
||
camel-ibatis |
deprecated |
1.2 |
Performs a query, poll, insert, update or delete in a relational database using Apache iBATIS. |
|
camel-iec60870 |
2.20 |
IEC 60870 component used for telecontrol (supervisory control and data acquisition) such as controlling electric power transmission grids and other geographically widespread control systems. |
||
camel-iec60870 |
2.20 |
IEC 60870 component used for telecontrol (supervisory control and data acquisition) such as controlling electric power transmission grids and other geographically widespread control systems. |
||
2.17 |
Summary of Ignite components |
|||
camel-ignite |
2.17 |
The Ignite Cache endpoint is one of camel-ignite endpoints which allows you to interact with an Ignite Cache. |
||
camel-ignite |
2.17 |
The Ignite Compute endpoint is one of camel-ignite endpoints which allows you to run compute operations on the cluster by passing in an IgniteCallable, an IgniteRunnable, an IgniteClosure, or collections of them, along with their parameters if necessary. |
||
camel-ignite |
2.17 |
The Ignite Events endpoint is one of camel-ignite endpoints which allows you to receive events from the Ignite cluster by creating a local event listener. |
||
camel-ignite |
2.17 |
The Ignite ID Generator endpoint is one of camel-ignite endpoints which allows you to interact with Ignite Atomic Sequences and ID Generators. |
||
camel-ignite |
2.17 |
The Ignite Messaging endpoint is one of camel-ignite endpoints which allows you to send and consume messages from an Ignite topic. |
||
camel-ignite |
2.17 |
The Ignite Queue endpoint is one of camel-ignite endpoints which allows you to interact with Ignite Queue data structures. |
||
camel-ignite |
2.17 |
The Ignite Sets endpoint is one of camel-ignite endpoints which allows you to interact with Ignite Set data structures. |
||
camel-infinispan |
2.13 |
For reading/writing from/to Infinispan distributed key/value store and data grid. |
||
camel-influxdb |
2.18 |
The influxdb component allows you to interact with InfluxDB, a time series database. |
||
camel-iota |
2.23 |
Component for integrate IOTA DLT |
||
camel-ipfs |
2.23 |
The camel-ipfs component provides access to the Interplanetary File System (IPFS). |
||
camel-irc |
1.1 |
The irc component implements an IRC (Internet Relay Chat) transport. |
||
camel-ironmq |
2.17 |
The ironmq provides integration with IronMQ an elastic and durable hosted message queue as a service. |
||
camel-javaspace |
deprecated |
2.1 |
Sending and receiving messages through JavaSpace. |
|
camel-websocket-jsr356 |
2.23 |
Camel WebSocket using JSR356 (javax) |
||
camel-jbpm |
2.6 |
The jbpm component provides integration with jBPM (Business Process Management). |
||
camel-jcache |
2.17 |
The jcache component enables you to perform caching operations using JSR107/JCache as cache implementation. |
||
camel-jclouds |
2.9 |
For interacting with cloud compute & blobstore service via jclouds. |
||
camel-jcr |
1.3 |
The jcr component allows you to add/read nodes to/from a JCR compliant content repository. |
||
camel-jdbc |
1.2 |
The jdbc component enables you to access databases through JDBC, where SQL queries are sent in the message body. |
||
camel-jetty9 |
1.2 |
The jetty component provides HTTP-based endpoints for consuming and producing HTTP requests. |
||
camel-websocket |
2.10 |
The websocket component provides websocket endpoints with Jetty for communicating with clients using websocket. |
||
camel-jgroups |
2.13 |
The jgroups component provides exchange of messages between Camel and JGroups clusters. |
||
camel-jgroups-raft |
2.24 |
The jgroups component provides exchange of messages between Camel and JGroups clusters. |
||
camel-jing |
1.1 |
Validates the payload of a message using RelaxNG Syntax using Jing library. |
||
camel-jira |
deprecated |
2.15 |
The jira component interacts with the JIRA issue tracker. |
|
camel-jms |
1.0 |
The jms component allows messages to be sent to (or consumed from) a JMS Queue or Topic. |
||
camel-jmx |
2.6 |
The jmx component allows to receive JMX notifications. |
||
camel-jolt |
2.16 |
The jolt component allows you to process a JSON messages using an JOLT specification (such as JSON-JSON transformation). |
||
camel-jpa |
1.0 |
The jpa component enables you to store and retrieve Java objects from databases using JPA. |
||
camel-json-validator |
2.20 |
Validates the payload of a message using NetworkNT JSON Schema library. |
||
camel-jt400 |
1.5 |
The jt400 component allows you to exchanges messages with an AS/400 system using data queues or program call. |
||
camel-kafka |
2.13 |
The kafka component allows messages to be sent to (or consumed from) Apache Kafka brokers. |
||
camel-kestrel |
deprecated |
2.6 |
The kestrel component allows messages to be sent to (or consumed from) Kestrel brokers. |
|
camel-krati |
deprecated |
2.9 |
The krati allows the use krati datastores and datasets inside Camel. |
|
camel-kubernetes |
deprecated |
2.17 |
Use splitted kubernetes components instead of this composite component. |
|
2.17 |
Summary of Kubernetes components |
|||
camel-kubernetes |
2.17 |
The Kubernetes Configmaps component provides a producer to execute kubernetes configmap operations. |
||
camel-kubernetes |
2.20 |
The Kubernetes Nodes component provides a producer to execute kubernetes node operations and a consumer to consume node events. |
||
camel-kubernetes |
2.23 |
The Kubernetes HPA component provides a producer to execute kubernetes hpa operations and a consumer to consume HPA events. |
||
camel-kubernetes |
2.23 |
The Kubernetes Jobs component provides a producer to execute kubernetes job operations |
||
camel-kubernetes |
2.17 |
The Kubernetes Namespaces component provides a producer to execute kubernetes namespace operations and a consumer to consume namespace events. |
||
camel-kubernetes |
2.17 |
The Kubernetes Nodes component provides a producer to execute kubernetes node operations and a consumer to consume node events. |
||
camel-kubernetes |
2.17 |
The Kubernetes Persistent Volumes component provides a producer to execute kubernetes persistent volume operations. |
||
camel-kubernetes |
2.17 |
The Kubernetes Persistent Volumes Claims component provides a producer to execute kubernetes persistent volume claim operations. |
||
camel-kubernetes |
2.17 |
The Kubernetes Pods component provides a producer to execute kubernetes pod operations and a consumer to consume pod events. |
||
camel-kubernetes |
2.17 |
The Kubernetes Replication Controllers component provides a producer to execute kubernetes replication controller operations and a consumer to consume replication controller events. |
||
camel-kubernetes |
2.17 |
The Kubernetes Resources Quota component provides a producer to execute kubernetes resources quota operations. |
||
camel-kubernetes |
2.17 |
The Kubernetes Secrets component provides a producer to execute kubernetes secret operations. |
||
camel-kubernetes |
2.17 |
The Kubernetes Service Accounts component provides a producer to execute service account operations. |
||
camel-kubernetes |
2.17 |
The Kubernetes Service Accounts component provides a producer to execute service operations and a consumer to consume service events. |
||
camel-ldap |
1.5 |
The ldap component allows you to perform searches in LDAP servers using filters as the message payload. |
||
camel-ldif |
2.20 |
The ldif component allows you to do updates on an LDAP server from a LDIF body content. |
||
camel-linkedin |
2.14 |
The linkedin component is used for retrieving LinkedIn user profiles, connections, companies, groups, posts, etc. |
||
camel-lucene |
2.2 |
To insert or query from Apache Lucene databases. |
||
camel-lumberjack |
2.18 |
The lumberjack retrieves logs sent over the network using the Lumberjack protocol. |
||
camel-mail |
1.0 |
To send or receive emails using imap/pop3 or smtp protocols. |
||
camel-master |
2.20 |
Represents an endpoint which only becomes active when the CamelClusterView has the leadership. |
||
camel-metrics |
2.14 |
To collect various metrics directly from Camel routes using the DropWizard metrics library. |
||
camel-micrometer |
2.22 |
To collect various metrics directly from Camel routes using the Micrometer library. |
||
camel-mina |
deprecated |
1.0 |
Socket level networking using TCP or UDP with the Apache Mina 1.x library. |
|
camel-mina2 |
2.10 |
Socket level networking using TCP or UDP with the Apache Mina 2.x library. |
||
camel-mllp |
2.17 |
Provides functionality required by Healthcare providers to communicate with other systems using the MLLP protocol. |
||
camel-mongodb |
deprecated |
2.10 |
Component for working with documents stored in MongoDB database. |
|
camel-mongodb3 |
2.19 |
Component for working with documents stored in MongoDB database. |
||
camel-mongodb-gridfs |
2.18 |
Component for working with MongoDB GridFS. |
||
camel-mqtt |
deprecated |
2.10 |
Component for communicating with MQTT M2M message brokers using FuseSource MQTT Client. |
|
camel-msv |
1.1 |
Validates the payload of a message using the MSV Library. |
||
camel-mustache |
2.12 |
Transforms the message using a Mustache template. |
||
camel-mvel |
2.12 |
Transforms the message using a MVEL template. |
||
camel-mybatis |
2.7 |
Performs a query, poll, insert, update or delete in a relational database using MyBatis. |
||
camel-mybatis |
2.22 |
Performs a query, insert, update or delete in a relational database using MyBatis. |
||
camel-nagios |
2.3 |
To send passive checks to Nagios using JSendNSCA. |
||
camel-nats |
2.17 |
The nats component allows you produce and consume messages from NATS. |
||
camel-netty |
deprecated |
2.3 |
Socket level networking using TCP or UDP with the Netty 3.x library. |
|
camel-netty-http |
deprecated |
2.12 |
Netty HTTP server and client using the Netty 3.x library. |
|
camel-netty4 |
2.14 |
Socket level networking using TCP or UDP with the Netty 4.x library. |
||
camel-netty4-http |
2.14 |
Netty HTTP server and client using the Netty 4.x library. |
||
camel-nsq |
2.23 |
Represents a nsq endpoint. |
||
camel-olingo2 |
2.14 |
Communicates with OData 2.0 services using Apache Olingo. |
||
camel-olingo4 |
2.19 |
Communicates with OData 4.0 services using Apache Olingo OData API. |
||
camel-milo |
2.19 |
Connect to OPC UA servers using the binary protocol for acquiring telemetry data |
||
camel-milo |
2.19 |
Make telemetry data available as an OPC UA server |
||
camel-openshift |
deprecated |
2.14 |
To manage your Openshift 2.x applications. |
|
camel-kubernetes |
2.17 |
The Kubernetes Build Config component provides a producer to execute kubernetes build config operations. |
||
camel-kubernetes |
2.17 |
The Openshift Builds component provides a producer to execute openshift build operations. |
||
2.19 |
Summary of Openstack components |
|||
camel-openstack |
2.19 |
The openstack-cinder component allows messages to be sent to an OpenStack block storage services. |
||
camel-openstack |
2.19 |
The openstack-glance component allows messages to be sent to an OpenStack image services. |
||
camel-openstack |
2.19 |
The openstack-keystone component allows messages to be sent to an OpenStack identity services. |
||
camel-openstack |
2.19 |
The openstack-neutron component allows messages to be sent to an OpenStack network services. |
||
camel-openstack |
2.19 |
The openstack-nova component allows messages to be sent to an OpenStack compute services. |
||
camel-openstack |
2.19 |
The openstack-swift component allows messages to be sent to an OpenStack object storage services. |
||
camel-optaplanner |
2.13 |
Solves the planning problem contained in a message with OptaPlanner. |
||
camel-eventadmin |
2.6 |
The eventadmin component can be used in an OSGi environment to receive OSGi EventAdmin events and process them. |
||
camel-paxlogging |
2.6 |
The paxlogging component can be used in an OSGi environment to receive PaxLogging events and process them. |
||
camel-paho |
2.16 |
Component for communicating with MQTT M2M message brokers using Eclipse Paho MQTT Client. |
||
camel-pdf |
2.16 |
The pdf components provides the ability to create, modify or extract content from PDF documents. |
||
camel-pgevent |
2.15 |
The pgevent component allows for producing/consuming PostgreSQL events related to the listen/notify commands. |
||
camel-printer |
2.1 |
The printer component is used for sending messages to printers as print jobs. |
||
camel-pubnub |
2.19 |
To send and receive messages to PubNub data stream network for connected devices. |
||
camel-quartz |
deprecated |
1.0 |
Provides a scheduled delivery of messages using the Quartz 1.x scheduler. |
|
camel-quartz2 |
2.12 |
Provides a scheduled delivery of messages using the Quartz 2.x scheduler. |
||
camel-quickfix |
2.1 |
The quickfix component allows to send Financial Interchange (FIX) messages to the QuickFix engine. |
||
camel-rabbitmq |
2.12 |
The rabbitmq component allows you produce and consume messages from RabbitMQ instances. |
||
camel-reactive-streams |
2.19 |
Reactive Camel using reactive streams |
||
camel-rest-swagger |
2.19 |
An awesome REST endpoint backed by Swagger specifications. |
||
camel-restlet |
deprecated |
2.0 |
Component for consuming and producing Restful resources using Restlet. |
|
camel-rmi |
deprecated |
1.0 |
The rmi component is for invoking Java RMI beans from Camel. |
|
camel-routebox |
deprecated |
2.6 |
The routebox component allows to send/receive messages between Camel routes in a black box way. |
|
camel-rss |
2.0 |
The rss component is used for consuming RSS feeds. |
||
camel-salesforce |
2.12 |
The salesforce component is used for integrating Camel with the massive Salesforce API. |
||
camel-sap-netweaver |
2.12 |
The sap-netweaver component integrates with the SAP NetWeaver Gateway using HTTP transports. |
||
camel-schematron |
2.15 |
Validates the payload of a message using the Schematron Library. |
||
camel-jsch |
2.10 |
To copy files using the secure copy protocol (SCP). |
||
camel-service |
2.22 |
Represents an endpoint which is registered to a Service Registry such as Consul, Etcd. |
||
camel-servicenow |
2.18 |
The servicenow component is used to integrate Camel with ServiceNow cloud services. |
||
camel-servlet |
2.0 |
To use a HTTP Servlet as entry for Camel routes when running in a servlet container. |
||
camel-ftp |
1.1 |
The sftp (FTP over SSH) component is used for uploading or downloading files from SFTP servers. |
||
camel-sjms |
2.11 |
The sjms component (simple jms) allows messages to be sent to (or consumed from) a JMS Queue or Topic (uses JMS 1.x API). |
||
camel-sjms |
2.16 |
The sjms-batch component is a specialized for highly performant, transactional batch consumption from a JMS queue. |
||
camel-sjms2 |
2.19 |
The sjms2 component (simple jms) allows messages to be sent to (or consumed from) a JMS Queue or Topic (uses JMS 2.x API). |
||
camel-sip |
2.5 |
To send and receive messages using the SIP protocol (used in telco and mobile). |
||
camel-slack |
2.16 |
The slack component allows you to send messages to Slack. |
||
camel-smpp |
2.2 |
To send and receive SMS using a SMSC (Short Message Service Center). |
||
camel-snmp |
2.1 |
The snmp component gives you the ability to poll SNMP capable devices or receiving traps. |
||
camel-solr |
2.9 |
The solr component allows you to interface with an Apache Lucene Solr server. |
||
camel-spark-rest |
2.14 |
The spark-rest component is used for hosting REST services which has been defined using Camel rest-dsl. |
||
camel-splunk |
2.13 |
The splunk component allows to publish or search for events in Splunk. |
||
Summary of Spring components |
||||
camel-spring-batch |
2.10 |
The spring-batch component allows to send messages to Spring Batch for further processing. |
||
camel-spring |
1.4 |
The spring-event component allows to listen for Spring Application Events. |
||
camel-spring-integration |
1.4 |
Bridges Camel with Spring Integration. |
||
camel-spring-ldap |
2.11 |
The spring-ldap component allows you to perform searches in LDAP servers using filters as the message payload. |
||
camel-spring-redis |
2.11 |
The spring-redis component allows sending and receiving messages from Redis. |
||
camel-spring-ws |
2.6 |
The spring-ws component is used for SOAP WebServices using Spring WebServices. |
||
camel-sql |
1.4 |
The sql component allows you to work with databases using JDBC SQL queries. |
||
camel-sql |
2.17 |
The sql component allows you to work with databases using JDBC Stored Procedure queries. |
||
camel-ssh |
2.10 |
The ssh component enables access to SSH servers such that you can send an SSH command, and process the response. |
||
camel-stax |
2.9 |
The stax component allows messages to be process through a SAX ContentHandler. |
||
camel-stomp |
2.12 |
The stomp component is used for communicating with Stomp compliant message brokers. |
||
camel-stream |
1.3 |
The stream: component provides access to the system-in, system-out and system-err streams as well as allowing streaming of file and URL. |
||
camel-stringtemplate |
1.2 |
Transforms the message using a String template. |
||
camel-telegram |
2.18 |
The telegram component provides access to the Telegram Bot API. |
||
camel-thrift |
2.20 |
The Thrift component allows to call and expose remote procedures (RPC) with Apache Thrift data format and serialization mechanism |
||
camel-tika |
2.19 |
This component integrates with Apache Tika to extract content and metadata from thousands of file types. |
||
camel-twilio |
2.20 |
The Twilio component allows you to interact with the Twilio REST APIs using Twilio Java SDK. |
||
camel-twitter |
deprecated |
2.10 |
Use twitter-directmessage, twitter-search, twitter-streaming and twitter-timeline instead of this component. |
|
2.10 |
Summary of Twitter components |
|||
camel-twitter |
2.10 |
The Twitter Direct Message Component consumes/produces user’s direct messages. |
||
camel-twitter |
2.10 |
The Twitter Search component consumes search results. |
||
camel-twitter |
2.10 |
The Twitter Streaming component consumes twitter statuses using Streaming API. |
||
camel-twitter |
2.10 |
The Twitter Timeline component consumes twitter timeline or update the status of specific user. |
||
camel-undertow |
2.16 |
The undertow component provides HTTP and WebSocket based endpoints for consuming and producing HTTP/WebSocket requests. |
||
camel-velocity |
1.2 |
Transforms the message using a Velocity template. |
||
camel-vertx |
2.12 |
The vertx component is used for sending and receive messages from a vertx event bus. |
||
camel-weather |
2.12 |
Polls the weather information from Open Weather Map. |
||
camel-web3j |
2.22 |
The web3j component uses the Web3j client API and allows you to add/read nodes to/from a web3j compliant content repositories. |
||
camel-wordpress |
2.21 |
Integrates Camel with Wordpress. |
||
camel-xchange |
2.21 |
The camel-xchange component provide access to many bitcoin and altcoin exchanges for trading and accessing market data. |
||
camel-xmlrpc |
deprecated |
2.11 |
The xmlrpc component is used for sending messages to a XML RPC service. |
|
camel-xmlsecurity |
2.12 |
Used to sign and verify exchanges using the XML signature specification. |
||
camel-xmpp |
1.0 |
To send and receive messages from a XMPP (chat) server. |
||
camel-saxon |
1.0 |
Transforms the message using a XQuery template using Saxon. |
||
camel-yammer |
2.12 |
The yammer component allows you to interact with the Yammer enterprise social network. |
||
camel-zendesk |
2.19 |
Allows producing messages to manage Zendesk ticket, user, organization, etc. |
||
camel-zookeeper |
2.9 |
The zookeeper component allows interaction with a ZooKeeper cluster. |
||
camel-zookeeper-master |
2.19 |
Represents an endpoint which only becomes active when it obtains the master lock |