This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/master by this push:
new 491a240 Regen
491a240 is described below
commit 491a240a8c04547691b2e43a6d2e6834c238e227
Author: Claus Ibsen <[email protected]>
AuthorDate: Wed Feb 13 07:15:20 2019 +0100
Regen
---
.../src/main/docs/rest-swagger-component.adoc | 10 +-
components/readme.adoc | 943 +--------------------
core/camel-core/readme.adoc | 2 +-
docs/components/modules/ROOT/nav.adoc | 2 +-
.../modules/ROOT/pages/aws-lambda-component.adoc | 3 +
.../modules/ROOT/pages/hl7-dataformat.adoc | 161 +---
.../modules/ROOT/pages/hl7terser-language.adoc | 135 +++
.../modules/ROOT/pages/rest-swagger-component.adoc | 22 +-
.../modules/ROOT/pages/telegram-component.adoc | 2 +
.../modules/ROOT/pages/terser-language.adoc | 44 -
.../camel-spring-boot-dependencies/pom.xml | 2 +-
11 files changed, 165 insertions(+), 1161 deletions(-)
diff --git
a/components/camel-rest-swagger/src/main/docs/rest-swagger-component.adoc
b/components/camel-rest-swagger/src/main/docs/rest-swagger-component.adoc
index 97144f0..f8b30b6 100644
--- a/components/camel-rest-swagger/src/main/docs/rest-swagger-component.adoc
+++ b/components/camel-rest-swagger/src/main/docs/rest-swagger-component.adoc
@@ -149,13 +149,13 @@ The component supports 10 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.rest-swagger.base-path* | API basePath, for example /v2.
Default is unset, if set overrides the value present in Swagger specification.
| | String
-| *camel.component.rest-swagger.component-name* | Name of the Camel component
that will perform the requests. The compnent must be present in Camel registry
and it must implement RestProducerFactory service provider interface. If not
set CLASSPATH is searched for single component that implements
RestProducerFactory SPI. Can be overriden in endpoint configuration. | | String
-| *camel.component.rest-swagger.consumes* | What payload type this component
capable of consuming. Could be one type, like application/json or multiple
types as application/json, application/xml; q=0.5 according to the RFC7231.
This equates to the value of Accept HTTP header. If set overrides any value
found in the Swagger specification. Can be overriden in endpoint configuration
| | String
+| *camel.component.rest-swagger.component-name* | Name of the Camel component
that will perform the requests. The component must be present in Camel registry
and it must implement RestProducerFactory service provider interface. If not
set CLASSPATH is searched for single component that implements
RestProducerFactory SPI. Can be overridden in endpoint configuration. | |
String
+| *camel.component.rest-swagger.consumes* | What payload type this component
capable of consuming. Could be one type, like application/json or multiple
types as application/json, application/xml; q=0.5 according to the RFC7231.
This equates to the value of Accept HTTP header. If set overrides any value
found in the Swagger specification. Can be overridden in endpoint configuration
| | String
| *camel.component.rest-swagger.enabled* | Enable rest-swagger component |
true | Boolean
-| *camel.component.rest-swagger.host* | Scheme hostname and port to direct the
HTTP requests to in the form of https://hostname:port. Can be configured at the
endpoint, component or in the correspoding REST configuration in the Camel
Context. If you give this component a name (e.g. petstore) that REST
configuration is consulted first, rest-swagger next, and global configuration
last. If set overrides any value found in the Swagger specification,
RestConfiguration. Can be overriden in end [...]
-| *camel.component.rest-swagger.produces* | What payload type this component
is producing. For example application/json according to the RFC7231. This
equates to the value of Content-Type HTTP header. If set overrides any value
present in the Swagger specification. Can be overriden in endpoint
configuration. | | String
+| *camel.component.rest-swagger.host* | Scheme hostname and port to direct the
HTTP requests to in the form of https://hostname:port. Can be configured at the
endpoint, component or in the correspoding REST configuration in the Camel
Context. If you give this component a name (e.g. petstore) that REST
configuration is consulted first, rest-swagger next, and global configuration
last. If set overrides any value found in the Swagger specification,
RestConfiguration. Can be overridden in en [...]
+| *camel.component.rest-swagger.produces* | What payload type this component
is producing. For example application/json according to the RFC7231. This
equates to the value of Content-Type HTTP header. If set overrides any value
present in the Swagger specification. Can be overridden in endpoint
configuration. | | String
| *camel.component.rest-swagger.resolve-property-placeholders* | Whether the
component should resolve property placeholders on itself when starting. Only
properties which are of String type can use property placeholders. | true |
Boolean
-| *camel.component.rest-swagger.specification-uri* | Path to the Swagger
specification file. The scheme, host base path are taken from this
specification, but these can be overriden with properties on the component or
endpoint level. If not given the component tries to load swagger.json resource.
Note that the host defined on the component and endpoint of this Component
should contain the scheme, hostname and optionally the port in the URI syntax
(i.e. https://api.example.com:8080). Can [...]
+| *camel.component.rest-swagger.specification-uri* | Path to the Swagger
specification file. The scheme, host base path are taken from this
specification, but these can be overriden with properties on the component or
endpoint level. If not given the component tries to load swagger.json resource.
Note that the host defined on the component and endpoint of this Component
should contain the scheme, hostname and optionally the port in the URI syntax
(i.e. https://api.example.com:8080). Can [...]
| *camel.component.rest-swagger.ssl-context-parameters* | Customize TLS
parameters used by the component. If not set defaults to the TLS parameters set
in the Camel context. The option is a
org.apache.camel.support.jsse.SSLContextParameters type. | | String
| *camel.component.rest-swagger.use-global-ssl-context-parameters* | Enable
usage of global SSL context parameters. | false | Boolean
|===
diff --git a/components/readme.adoc b/components/readme.adoc
index 72b3e73..c744985 100644
--- a/components/readme.adoc
+++ b/components/readme.adoc
@@ -1,7 +1,7 @@
==== Components
// components: START
-Number of Components: 290 in 210 JAR artifacts (0 deprecated)
+Number of Components: 29 in 24 JAR artifacts (0 deprecated)
[width="100%",cols="4,1,5",options="header"]
|===
@@ -10,666 +10,51 @@ Number of Components: 290 in 210 JAR artifacts (0
deprecated)
| link:camel-activemq/src/main/docs/activemq-component.adoc[ActiveMQ]
(camel-activemq) +
`activemq:destinationType:destinationName` | 1.0 | The activemq component
allows messages to be sent to (or consumed from) Apache ActiveMQ. This
component extends the Camel JMS component.
-| link:camel-ahc/src/main/docs/ahc-component.adoc[AHC] (camel-ahc) +
-`ahc:httpUri` | 2.8 | To call external HTTP services using Async Http Client.
-
-| link:camel-ahc-ws/src/main/docs/ahc-ws-component.adoc[AHC Websocket]
(camel-ahc-ws) +
-`ahc-ws:httpUri` | 2.14 | To exchange data with external Websocket servers
using Async Http Client.
-
-| link:camel-amqp/src/main/docs/amqp-component.adoc[AMQP] (camel-amqp) +
-`amqp:destinationType:destinationName` | 1.2 | Messaging with AMQP protocol
using Apache QPid Client.
-
-| link:camel-flink/src/main/docs/flink-component.adoc[Apache Flink]
(camel-flink) +
-`flink:endpointType` | 2.18 | The flink component can be used to send DataSet
jobs to Apache Flink cluster.
-
-| link:camel-spark/src/main/docs/spark-component.adoc[Apache Spark]
(camel-spark) +
-`spark:endpointType` | 2.17 | The spark component can be used to send RDD or
DataFrame jobs to Apache Spark cluster.
-
-| link:camel-apns/src/main/docs/apns-component.adoc[APNS] (camel-apns) +
-`apns:name` | 2.8 | For sending notifications to Apple iOS devices.
-
-| link:camel-as2/camel-as2-component/src/main/docs/as2-component.adoc[AS2]
(camel-as2) +
-`as2:apiName` | 2.22 | Component used for transferring data secure and
reliable over the internet using the AS2 protocol.
-
-| link:camel-asterisk/src/main/docs/asterisk-component.adoc[Asterisk]
(camel-asterisk) +
-`asterisk:name` | 2.18 | The asterisk component is used to interact with
Asterisk PBX Server.
-
-| link:camel-atmos/src/main/docs/atmos-component.adoc[Atmos] (camel-atmos) +
-`atmos:name/operation` | 2.15 | The atmos component is used for integrating
with EMC's Atomos Storage.
-
-|
link:camel-atmosphere-websocket/src/main/docs/atmosphere-websocket-component.adoc[Atmosphere
Websocket] (camel-atmosphere-websocket) +
-`atmosphere-websocket:servicePath` | 2.14 | To exchange data with external
Websocket clients using Atmosphere.
-
-| link:camel-atom/src/main/docs/atom-component.adoc[Atom] (camel-atom) +
-`atom:feedUri` | 1.2 | The atom component is used for consuming Atom RSS feeds.
-
-| link:camel-atomix/src/main/docs/atomix-map-component.adoc[Atomix Map]
(camel-atomix) +
-`atomix-map:resourceName` | 2.20 | The atomix-map component is used to access
Atomix's distributed map.
-
-| link:camel-atomix/src/main/docs/atomix-messaging-component.adoc[Atomix
Messaging] (camel-atomix) +
-`atomix-messaging:resourceName` | 2.20 | The atomix-messaging component is
used to access Atomix's group messaging.
-
-| link:camel-atomix/src/main/docs/atomix-multimap-component.adoc[Atomix
MultiMap] (camel-atomix) +
-`atomix-multimap:resourceName` | 2.20 | The atomix-multimap component is used
to access Atomix's distributed multi map.
-
-| link:camel-atomix/src/main/docs/atomix-queue-component.adoc[Atomix Queue]
(camel-atomix) +
-`atomix-queue:resourceName` | 2.20 | The atomix-queue component is used to
access Atomix's distributed queue.
-
-| link:camel-atomix/src/main/docs/atomix-set-component.adoc[Atomix Set]
(camel-atomix) +
-`atomix-set:resourceName` | 2.20 | The atomix-set component is used to access
Atomix's distributed set.
-
-| link:camel-atomix/src/main/docs/atomix-value-component.adoc[Atomix Value]
(camel-atomix) +
-`atomix-value:resourceName` | 2.20 | The atomix-value component is used to
access Atomix's distributed value.
-
-| link:camel-avro/src/main/docs/avro-component.adoc[Avro] (camel-avro) +
-`avro:transport:host:port/messageName` | 2.10 | Working with Apache Avro for
data serialization.
-
-| link:camel-aws/src/main/docs/aws-cw-component.adoc[AWS CloudWatch]
(camel-aws) +
-`aws-cw:namespace` | 2.11 | The aws-cw component is used for sending metrics
to an Amazon CloudWatch.
-
-| link:camel-aws/src/main/docs/aws-ddb-component.adoc[AWS DynamoDB]
(camel-aws) +
-`aws-ddb:tableName` | 2.10 | The aws-ddb component is used for storing and
retrieving data from Amazon's DynamoDB service.
-
-| link:camel-aws/src/main/docs/aws-ddbstream-component.adoc[AWS DynamoDB
Streams] (camel-aws) +
-`aws-ddbstream:tableName` | 2.17 | The aws-ddbstream component is used for
working with Amazon DynamoDB Streams.
-
-| link:camel-aws/src/main/docs/aws-ec2-component.adoc[AWS EC2] (camel-aws) +
-`aws-ec2:label` | 2.16 | The aws-ec2 is used for managing Amazon EC2 instances.
-
-| link:camel-aws/src/main/docs/aws-ecs-component.adoc[AWS ECS] (camel-aws) +
-`aws-ecs:label` | 3.0 | The aws-kms is used for managing Amazon ECS
-
-| link:camel-aws/src/main/docs/aws-eks-component.adoc[AWS EKS] (camel-aws) +
-`aws-eks:label` | 3.0 | The aws-kms is used for managing Amazon EKS
-
-| link:camel-aws/src/main/docs/aws-iam-component.adoc[AWS IAM] (camel-aws) +
-`aws-iam:label` | 2.23 | The aws-iam is used for managing Amazon IAM
-
-| link:camel-aws/src/main/docs/aws-kinesis-component.adoc[AWS Kinesis]
(camel-aws) +
-`aws-kinesis:streamName` | 2.17 | The aws-kinesis component is for consuming
and producing records from Amazon Kinesis Streams.
-
-| link:camel-aws/src/main/docs/aws-kinesis-firehose-component.adoc[AWS Kinesis
Firehose] (camel-aws) +
-`aws-kinesis-firehose:streamName` | 2.19 | The aws-kinesis-firehose component
is used for producing Amazon's Kinesis Firehose streams.
-
-| link:camel-aws/src/main/docs/aws-kms-component.adoc[AWS KMS] (camel-aws) +
-`aws-kms:label` | 2.21 | The aws-kms is used for managing Amazon KMS
-
-| link:camel-aws/src/main/docs/aws-lambda-component.adoc[AWS Lambda]
(camel-aws) +
-`aws-lambda:function` | 2.20 | The aws-lambda is used for managing and
invoking functions from Amazon Lambda.
-
-| link:camel-aws/src/main/docs/aws-mq-component.adoc[AWS MQ] (camel-aws) +
-`aws-mq:label` | 2.21 | The aws-mq is used for managing Amazon MQ instances.
-
-| link:camel-aws/src/main/docs/aws-s3-component.adoc[AWS S3 Storage Service]
(camel-aws) +
-`aws-s3:bucketNameOrArn` | 2.8 | The aws-s3 component is used for storing and
retrieving objecct from Amazon S3 Storage Service.
-
-| link:camel-aws/src/main/docs/aws-ses-component.adoc[AWS Simple Email
Service] (camel-aws) +
-`aws-ses:from` | 2.9 | The aws-ses component is used for sending emails with
Amazon's SES service.
-
-| link:camel-aws/src/main/docs/aws-sns-component.adoc[AWS Simple Notification
System] (camel-aws) +
-`aws-sns:topicNameOrArn` | 2.8 | The aws-sns component is used for sending
messages to an Amazon Simple Notification Topic.
-
-| link:camel-aws/src/main/docs/aws-sqs-component.adoc[AWS Simple Queue
Service] (camel-aws) +
-`aws-sqs:queueNameOrArn` | 2.6 | The aws-sqs component is used for sending and
receiving messages to Amazon's SQS service.
-
-| link:camel-aws/src/main/docs/aws-swf-component.adoc[AWS Simple Workflow]
(camel-aws) +
-`aws-swf:type` | 2.13 | The aws-swf component is used for managing workflows
from Amazon Simple Workflow.
-
-| link:camel-aws/src/main/docs/aws-sdb-component.adoc[AWS SimpleDB]
(camel-aws) +
-`aws-sdb:domainName` | 2.9 | The aws-sdb component is for storing and
retrieving data from/to Amazon's SDB service.
-
-| link:camel-azure/src/main/docs/azure-blob-component.adoc[Azure Storage Blob
Service] (camel-azure) +
-`azure-blob:containerOrBlobUri` | 2.19 | The azure-blob component is used for
storing and retrieving blobs from Azure Storage Blob Service.
-
-| link:camel-azure/src/main/docs/azure-queue-component.adoc[Azure Storage
Queue Service] (camel-azure) +
-`azure-queue:containerAndQueueUri` | 2.19 | The azure-queue component is used
for storing and retrieving messages from Azure Storage Queue Service.
-
| link:../core/camel-core/src/main/docs/bean-component.adoc[Bean] (camel-core)
+
`bean:beanName` | 1.0 | The bean component is for invoking Java beans from
Camel.
-| link:camel-bean-validator/src/main/docs/bean-validator-component.adoc[Bean
Validator] (camel-bean-validator) +
-`bean-validator:label` | 2.3 | The Validator component performs bean
validation of the message body using the Java Bean Validation API.
-
-| link:camel-beanstalk/src/main/docs/beanstalk-component.adoc[Beanstalk]
(camel-beanstalk) +
-`beanstalk:connectionSettings` | 2.15 | The beanstalk component is used for
job retrieval and post-processing of Beanstalk jobs.
-
-| link:camel-bonita/src/main/docs/bonita-component.adoc[Bonita] (camel-bonita)
+
-`bonita:operation` | 2.19 | Used for communicating with a remote Bonita BPM
process engine.
-
-| link:camel-box/camel-box-component/src/main/docs/box-component.adoc[Box]
(camel-box) +
-`box:apiName/methodName` | 2.14 | For uploading downloading and managing files
folders groups collaborations etc on box DOT com.
-
-| link:camel-braintree/src/main/docs/braintree-component.adoc[Braintree]
(camel-braintree) +
-`braintree:apiName/methodName` | 2.17 | The braintree component is used for
integrating with the Braintree Payment System.
-
| link:camel-browse/src/main/docs/browse-component.adoc[Browse] (camel-browse)
+
`browse:name` | 1.3 | The browse component is used for viewing the messages
received on endpoints that supports BrowsableEndpoint.
-| link:camel-caffeine/src/main/docs/caffeine-cache-component.adoc[Caffeine
Cache] (camel-caffeine) +
-`caffeine-cache:cacheName` | 2.20 | The caffeine-cache component is used for
integration with Caffeine Cache.
-
-| link:camel-caffeine/src/main/docs/caffeine-loadcache-component.adoc[Caffeine
LoadCache] (camel-caffeine) +
-`caffeine-loadcache:cacheName` | 2.20 | The caffeine-loadcache component is
used for integration with Caffeine Load Cache.
-
-| link:camel-cassandraql/src/main/docs/cql-component.adoc[Cassandra CQL]
(camel-cassandraql) +
-`cql:beanRef:hosts:port/keyspace` | 2.15 | The cql component aims at
integrating Cassandra 2.0 using the CQL3 API (not the Thrift API).
-
-| link:camel-chunk/src/main/docs/chunk-component.adoc[Chunk] (camel-chunk) +
-`chunk:resourceUri` | 2.15 | Transforms the message using a Chunk template.
-
| link:../core/camel-core/src/main/docs/class-component.adoc[Class]
(camel-core) +
`class:beanName` | 2.4 | The Class Component is for invoking Java Classes
(Java beans) from Camel.
-| link:camel-cm-sms/src/main/docs/cm-sms-component.adoc[CM SMS Gateway]
(camel-cm-sms) +
-`cm-sms:host` | 2.18 | The cm-sms component allows to integrate with CM SMS
Gateway.
-
-| link:camel-cmis/src/main/docs/cmis-component.adoc[CMIS] (camel-cmis) +
-`cmis:cmsUrl` | 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.
-
-| link:camel-coap/src/main/docs/coap-component.adoc[CoAP] (camel-coap) +
-`coap:uri` | 2.16 | The coap component is used for sending and receiving
messages from COAP capable devices.
-
-| link:camel-cometd/src/main/docs/cometd-component.adoc[CometD] (camel-cometd)
+
-`cometd:host:port/channelName` | 2.0 | The cometd component is a transport for
working with the Jetty implementation of the cometd/bayeux protocol.
-
-| link:camel-consul/src/main/docs/consul-component.adoc[Consul] (camel-consul)
+
-`consul:apiEndpoint` | 2.18 | The camel consul component allows you to work
with Consul, a distributed, highly available, datacenter-aware, service
discovery and configuration system.
-
| link:camel-controlbus/src/main/docs/controlbus-component.adoc[Control Bus]
(camel-controlbus) +
`controlbus:command:language` | 2.11 | The controlbus component provides easy
management of Camel applications based on the Control Bus EIP pattern.
-| link:camel-corda/src/main/docs/corda-component.adoc[corda] (camel-corda) +
-`corda:url` | 2.23 | The corda component uses the corda-rpc to interact with
corda nodes.
-
-| link:camel-couchbase/src/main/docs/couchbase-component.adoc[Couchbase]
(camel-couchbase) +
-`couchbase:protocol:hostname:port` | 2.19 | Represents a Couchbase endpoint
that can query Views with a Poll strategy and/or produce various type of
operations.
-
-| link:camel-couchdb/src/main/docs/couchdb-component.adoc[CouchDB]
(camel-couchdb) +
-`couchdb:protocol:hostname:port/database` | 2.11 | The couchdb component is
used for integrate with CouchDB databases.
-
-| link:camel-crypto/src/main/docs/crypto-component.adoc[Crypto (JCE)]
(camel-crypto) +
-`crypto:cryptoOperation:name` | 2.3 | The crypto component is used for signing
and verifying exchanges using the Signature Service of the Java Cryptographic
Extension (JCE).
-
-| link:camel-crypto-cms/src/main/docs/crypto-cms-component.adoc[Crypto CMS]
(camel-crypto-cms) +
-`crypto-cms:cryptoOperation:name` | 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.
-
-| link:camel-cxf/src/main/docs/cxf-component.adoc[CXF] (camel-cxf) +
-`cxf:beanId:address` | 1.0 | The cxf component is used for SOAP WebServices
using Apache CXF.
-
-| link:camel-cxf/src/main/docs/cxfrs-component.adoc[CXF-RS] (camel-cxf) +
-`cxfrs:beanId:address` | 2.0 | The cxfrs component is used for JAX-RS REST
services using Apache CXF.
-
| link:camel-dataformat/src/main/docs/dataformat-component.adoc[Data Format]
(camel-dataformat) +
`dataformat:name:operation` | 2.12 | The dataformat component is used for
working with Data Formats as if it was a regular Component supporting Endpoints
and URIs.
| link:../core/camel-core/src/main/docs/dataset-component.adoc[Dataset]
(camel-core) +
`dataset:name` | 1.3 | The dataset component provides a mechanism to easily
perform load & soak testing of your system.
-|
link:camel-digitalocean/src/main/docs/digitalocean-component.adoc[DigitalOcean]
(camel-digitalocean) +
-`digitalocean:operation` | 2.19 | The DigitalOcean component allows you to
manage Droplets and resources within the DigitalOcean cloud.
-
| link:camel-direct/src/main/docs/direct-component.adoc[Direct] (camel-direct)
+
`direct:name` | 1.0 | The direct component provides direct, synchronous call
to another endpoint from the same CamelContext.
| link:camel-directvm/src/main/docs/direct-vm-component.adoc[Direct VM]
(camel-directvm) +
`direct-vm:name` | 2.10 | The direct-vm component provides direct, synchronous
call to another endpoint from any CamelContext in the same JVM.
-| link:camel-disruptor/src/main/docs/disruptor-component.adoc[Disruptor]
(camel-disruptor) +
-`disruptor:name` | 2.12 | The disruptor component provides asynchronous SEDA
behavior using LMAX Disruptor.
-
-| link:camel-dns/src/main/docs/dns-component.adoc[DNS] (camel-dns) +
-`dns:dnsType` | 2.7 | To lookup domain information and run DNS queries using
DNSJava.
-
-| link:camel-docker/src/main/docs/docker-component.adoc[Docker] (camel-docker)
+
-`docker:operation` | 2.15 | The docker component is used for managing Docker
containers.
-
-| link:camel-dozer/src/main/docs/dozer-component.adoc[Dozer] (camel-dozer) +
-`dozer:name` | 2.15 | The dozer component provides the ability to map between
Java beans using the Dozer mapping library.
-
-| link:camel-drill/src/main/docs/drill-component.adoc[Drill] (camel-drill) +
-`drill:host` | 2.19 | The drill component gives you the ability to quering
into apache drill cluster.
-
-| link:camel-dropbox/src/main/docs/dropbox-component.adoc[Dropbox]
(camel-dropbox) +
-`dropbox:operation` | 2.14 | For uploading, downloading and managing files,
folders, groups, collaborations, etc on dropbox DOT com.
-
-| link:camel-ehcache/src/main/docs/ehcache-component.adoc[Ehcache]
(camel-ehcache) +
-`ehcache:cacheName` | 2.18 | The ehcache component enables you to perform
caching operations using Ehcache as cache implementation.
-
-| link:camel-ejb/src/main/docs/ejb-component.adoc[EJB] (camel-ejb) +
-`ejb:beanName` | 2.4 | The ejb component is for invoking EJB Java beans from
Camel.
-
-|
link:camel-elasticsearch-rest/src/main/docs/elasticsearch-rest-component.adoc[Elastichsearch
Rest] (camel-elasticsearch-rest) +
-`elasticsearch-rest:clusterName` | 2.21 | The elasticsearch component is used
for interfacing with ElasticSearch server using REST API.
-
-| link:camel-elsql/src/main/docs/elsql-component.adoc[ElSQL] (camel-elsql) +
-`elsql:elsqlName:resourceUri` | 2.16 | The elsql component is an extension to
the existing SQL Component that uses ElSql to define the SQL queries.
-
-| link:camel-etcd/src/main/docs/etcd-component.adoc[etcd] (camel-etcd) +
-`etcd:namespace/path` | 2.18 | The camel etcd component allows you to work
with Etcd, a distributed reliable key-value store.
-
-| link:camel-exec/src/main/docs/exec-component.adoc[Exec] (camel-exec) +
-`exec:executable` | 2.3 | The exec component can be used to execute OS system
commands.
-
-| link:camel-facebook/src/main/docs/facebook-component.adoc[Facebook]
(camel-facebook) +
-`facebook:methodName` | 2.14 | The Facebook component provides access to all
of the Facebook APIs accessible using Facebook4J.
-
-| link:camel-fhir/camel-fhir-component/src/main/docs/fhir-component.adoc[FHIR]
(camel-fhir) +
-`fhir:apiName/methodName` | 2.23 | The fhir component is used for working with
the FHIR protocol (health care).
-
| link:camel-file/src/main/docs/file-component.adoc[File] (camel-file) +
`file:directoryName` | 1.0 | The file component is used for reading or writing
files.
-| link:camel-flatpack/src/main/docs/flatpack-component.adoc[Flatpack]
(camel-flatpack) +
-`flatpack:type:resourceUri` | 1.4 | The flatpack component supports fixed
width and delimited file parsing via the FlatPack library.
-
-| link:camel-fop/src/main/docs/fop-component.adoc[FOP] (camel-fop) +
-`fop:outputType` | 2.10 | The fop component allows you to render a message
into different output formats using Apache FOP.
-
-| link:camel-freemarker/src/main/docs/freemarker-component.adoc[Freemarker]
(camel-freemarker) +
-`freemarker:resourceUri` | 2.10 | Transforms the message using a FreeMarker
template.
-
-| link:camel-ftp/src/main/docs/ftp-component.adoc[FTP] (camel-ftp) +
-`ftp:host:port/directoryName` | 1.1 | The ftp component is used for uploading
or downloading files from FTP servers.
-
-| link:camel-ftp/src/main/docs/ftps-component.adoc[FTPS] (camel-ftp) +
-`ftps:host:port/directoryName` | 2.2 | The ftps (FTP secure SSL/TLS) component
is used for uploading or downloading files from FTP servers.
-
-| link:camel-ganglia/src/main/docs/ganglia-component.adoc[Ganglia]
(camel-ganglia) +
-`ganglia:host:port` | 2.15 | The ganglia component is used for sending metrics
to the Ganglia monitoring system.
-
-| link:camel-geocoder/src/main/docs/geocoder-component.adoc[Geocoder]
(camel-geocoder) +
-`geocoder:address:latlng` | 2.12 | The geocoder component is used for looking
up geocodes (latitude and longitude) for a given address, or reverse lookup.
-
-| link:camel-git/src/main/docs/git-component.adoc[Git] (camel-git) +
-`git:localPath` | 2.16 | The git component is used for working with git
repositories.
-
-| link:camel-github/src/main/docs/github-component.adoc[GitHub] (camel-github)
+
-`github:type/branchName` | 2.15 | The github component is used for integrating
Camel with github.
-
-|
link:camel-google-bigquery/src/main/docs/google-bigquery-component.adoc[Google
BigQuery] (camel-google-bigquery) +
-`google-bigquery:projectId:datasetId:tableName` | 2.20 | Google BigQuery data
warehouse for analytics.
-
-|
link:camel-google-bigquery/src/main/docs/google-bigquery-sql-component.adoc[Google
BigQuery Standard SQL] (camel-google-bigquery) +
-`google-bigquery-sql:query` | 2.23 | Google BigQuery data warehouse for
analytics (using SQL queries).
-
-|
link:camel-google-calendar/src/main/docs/google-calendar-component.adoc[Google
Calendar] (camel-google-calendar) +
-`google-calendar:apiName/methodName` | 2.15 | The google-calendar component
provides access to Google Calendar.
-
-|
link:camel-google-calendar/src/main/docs/google-calendar-stream-component.adoc[Google
Calendar Stream] (camel-google-calendar) +
-`google-calendar-stream:index` | 2.23 | The google-calendar component provides
access to Google Calendar in a streaming mode.
-
-| link:camel-google-drive/src/main/docs/google-drive-component.adoc[Google
Drive] (camel-google-drive) +
-`google-drive:apiName/methodName` | 2.14 | The google-drive component provides
access to Google Drive file storage service.
-
-| link:camel-google-mail/src/main/docs/google-mail-component.adoc[Google Mail]
(camel-google-mail) +
-`google-mail:apiName/methodName` | 2.15 | The google-mail component provides
access to Google Mail.
-
-|
link:camel-google-mail/src/main/docs/google-mail-stream-component.adoc[Google
Mail Stream] (camel-google-mail) +
-`google-mail-stream:index` | 2.22 | The google-mail component provides access
to Google Mail.
-
-| link:camel-google-pubsub/src/main/docs/google-pubsub-component.adoc[Google
Pubsub] (camel-google-pubsub) +
-`google-pubsub:projectId:destinationName` | 2.19 | Messaging client for Google
Cloud Platform PubSub Service
-
-| link:camel-google-sheets/src/main/docs/google-sheets-component.adoc[Google
Sheets] (camel-google-sheets) +
-`google-sheets:apiName/methodName` | 2.23 | The google-sheets component
provides access to Google Sheets.
-
-|
link:camel-google-sheets/src/main/docs/google-sheets-stream-component.adoc[Google
Sheets Stream] (camel-google-sheets) +
-`google-sheets-stream:apiName` | 2.23 | The google-sheets component provides
access to Google Sheets.
-
-| link:camel-gora/src/main/docs/gora-component.adoc[Gora] (camel-gora) +
-`gora:name` | 2.14 | The gora component allows you to work with NoSQL
databases using the Apache Gora framework.
-
-| link:camel-grape/src/main/docs/grape-component.adoc[Grape] (camel-grape) +
-`grape:defaultCoordinates` | 2.16 | The grape component allows you to fetch,
load and manage additional jars when CamelContext is running.
-
-| link:camel-grpc/src/main/docs/grpc-component.adoc[gRPC] (camel-grpc) +
-`grpc:host:port/service` | 2.19 | The gRPC component allows to call and expose
remote procedures via HTTP/2 with protobuf dataformat
-
-| link:camel-guava-eventbus/src/main/docs/guava-eventbus-component.adoc[Guava
EventBus] (camel-guava-eventbus) +
-`guava-eventbus:eventBusRef` | 2.10 | The guava-eventbus component provides
integration bridge between Camel and Google Guava EventBus.
-
-|
link:camel-hazelcast/src/main/docs/hazelcast-atomicvalue-component.adoc[Hazelcast
Atomic Number] (camel-hazelcast) +
-`hazelcast-atomicvalue:cacheName` | 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).
-
-|
link:camel-hazelcast/src/main/docs/hazelcast-instance-component.adoc[Hazelcast
Instance] (camel-hazelcast) +
-`hazelcast-instance:cacheName` | 2.7 | The hazelcast-instance component is
used to consume join/leave events of the cache instance in the cluster.
-
-| link:camel-hazelcast/src/main/docs/hazelcast-list-component.adoc[Hazelcast
List] (camel-hazelcast) +
-`hazelcast-list:cacheName` | 2.7 | The hazelcast-list component is used to
access Hazelcast distributed list.
-
-| link:camel-hazelcast/src/main/docs/hazelcast-map-component.adoc[Hazelcast
Map] (camel-hazelcast) +
-`hazelcast-map:cacheName` | 2.7 | The hazelcast-map component is used to
access Hazelcast distributed map.
-
-|
link:camel-hazelcast/src/main/docs/hazelcast-multimap-component.adoc[Hazelcast
Multimap] (camel-hazelcast) +
-`hazelcast-multimap:cacheName` | 2.7 | The hazelcast-multimap component is
used to to access Hazelcast distributed multimap.
-
-| link:camel-hazelcast/src/main/docs/hazelcast-queue-component.adoc[Hazelcast
Queue] (camel-hazelcast) +
-`hazelcast-queue:cacheName` | 2.7 | The hazelcast-queue component is used to
access Hazelcast distributed queue.
-
-|
link:camel-hazelcast/src/main/docs/hazelcast-replicatedmap-component.adoc[Hazelcast
Replicated Map] (camel-hazelcast) +
-`hazelcast-replicatedmap:cacheName` | 2.16 | The hazelcast-replicatedmap
component is used to access Hazelcast replicated map.
-
-|
link:camel-hazelcast/src/main/docs/hazelcast-ringbuffer-component.adoc[Hazelcast
Ringbuffer] (camel-hazelcast) +
-`hazelcast-ringbuffer:cacheName` | 2.16 | The hazelcast-ringbuffer component
is used to access Hazelcast distributed ringbuffer.
-
-| link:camel-hazelcast/src/main/docs/hazelcast-seda-component.adoc[Hazelcast
SEDA] (camel-hazelcast) +
-`hazelcast-seda:cacheName` | 2.7 | The hazelcast-seda component is used to
access Hazelcast BlockingQueue.
-
-| link:camel-hazelcast/src/main/docs/hazelcast-set-component.adoc[Hazelcast
Set] (camel-hazelcast) +
-`hazelcast-set:cacheName` | 2.7 | The camel Endpoint to access Hazelcast
distributed set.
-
-| link:camel-hazelcast/src/main/docs/hazelcast-topic-component.adoc[Hazelcast
Topic] (camel-hazelcast) +
-`hazelcast-topic:cacheName` | 2.15 | The hazelcast-topic component is used to
access Hazelcast distributed topic.
-
-| link:camel-hbase/src/main/docs/hbase-component.adoc[HBase] (camel-hbase) +
-`hbase:tableName` | 2.10 | For reading/writing from/to an HBase store (Hadoop
database).
-
-| link:camel-hdfs2/src/main/docs/hdfs2-component.adoc[HDFS2] (camel-hdfs2) +
-`hdfs2:hostName:port/path` | 2.14 | For reading/writing from/to an HDFS
filesystem using Hadoop 2.x.
-
-| link:camel-hipchat/src/main/docs/hipchat-component.adoc[Hipchat]
(camel-hipchat) +
-`hipchat:protocol:host:port` | 2.15 | The hipchat component supports producing
and consuming messages from/to Hipchat service.
-
-| link:camel-http4/src/main/docs/http4-component.adoc[HTTP4] (camel-http4) +
-`http4:httpUri` | 2.3 | For calling out to external HTTP servers using Apache
HTTP Client 4.x.
-
-| link:camel-iec60870/src/main/docs/iec60870-client-component.adoc[IEC 60870
Client] (camel-iec60870) +
-`iec60870-client:uriPath` | 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.
-
-| link:camel-iec60870/src/main/docs/iec60870-server-component.adoc[IEC 60870
Server] (camel-iec60870) +
-`iec60870-server:uriPath` | 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.
-
-| link:camel-ignite/src/main/docs/ignite-cache-component.adoc[Ignite Cache]
(camel-ignite) +
-`ignite-cache:cacheName` | 2.17 | The Ignite Cache endpoint is one of
camel-ignite endpoints which allows you to interact with an Ignite Cache.
-
-| link:camel-ignite/src/main/docs/ignite-compute-component.adoc[Ignite
Compute] (camel-ignite) +
-`ignite-compute:endpointId` | 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.
-
-| link:camel-ignite/src/main/docs/ignite-events-component.adoc[Ignite Events]
(camel-ignite) +
-`ignite-events:endpointId` | 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.
-
-| link:camel-ignite/src/main/docs/ignite-idgen-component.adoc[Ignite ID
Generator] (camel-ignite) +
-`ignite-idgen:name` | 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.
-
-| link:camel-ignite/src/main/docs/ignite-messaging-component.adoc[Ignite
Messaging] (camel-ignite) +
-`ignite-messaging:topic` | 2.17 | The Ignite Messaging endpoint is one of
camel-ignite endpoints which allows you to send and consume messages from an
Ignite topic.
-
-| link:camel-ignite/src/main/docs/ignite-queue-component.adoc[Ignite Queues]
(camel-ignite) +
-`ignite-queue:name` | 2.17 | The Ignite Queue endpoint is one of camel-ignite
endpoints which allows you to interact with Ignite Queue data structures.
-
-| link:camel-ignite/src/main/docs/ignite-set-component.adoc[Ignite Sets]
(camel-ignite) +
-`ignite-set:name` | 2.17 | The Ignite Sets endpoint is one of camel-ignite
endpoints which allows you to interact with Ignite Set data structures.
-
-| link:camel-infinispan/src/main/docs/infinispan-component.adoc[Infinispan]
(camel-infinispan) +
-`infinispan:cacheName` | 2.13 | For reading/writing from/to Infinispan
distributed key/value store and data grid.
-
-| link:camel-influxdb/src/main/docs/influxdb-component.adoc[InfluxDB]
(camel-influxdb) +
-`influxdb:connectionBean` | 2.18 | The influxdb component allows you to
interact with InfluxDB, a time series database.
-
-| link:camel-iota/src/main/docs/iota-component.adoc[IOTA] (camel-iota) +
-`iota:name` | 2.23 | Component for integrate IOTA DLT
-
-| link:camel-ipfs/src/main/docs/ipfs-component.adoc[IPFS] (camel-ipfs) +
-`ipfs:host:port/cmd` | 2.23 | The camel-ipfs component provides access to the
Interplanetary File System (IPFS).
-
-| link:camel-irc/src/main/docs/irc-component.adoc[IRC] (camel-irc) +
-`irc:hostname:port` | 1.1 | The irc component implements an IRC (Internet
Relay Chat) transport.
-
-| link:camel-ironmq/src/main/docs/ironmq-component.adoc[IronMQ] (camel-ironmq)
+
-`ironmq:queueName` | 2.17 | The ironmq provides integration with IronMQ an
elastic and durable hosted message queue as a service.
-
-|
link:camel-websocket-jsr356/src/main/docs/websocket-jsr356-component.adoc[Javax
Websocket] (camel-websocket-jsr356) +
-`websocket-jsr356:/resourceUri` | 2.23 | Camel WebSocket using JSR356 (javax)
-
-| link:camel-jbpm/src/main/docs/jbpm-component.adoc[JBPM] (camel-jbpm) +
-`jbpm:connectionURL` | 2.6 | The jbpm component provides integration with jBPM
(Business Process Management).
-
-| link:camel-jcache/src/main/docs/jcache-component.adoc[JCache] (camel-jcache)
+
-`jcache:cacheName` | 2.17 | The jcache component enables you to perform
caching operations using JSR107/JCache as cache implementation.
-
-| link:camel-jclouds/src/main/docs/jclouds-component.adoc[JClouds]
(camel-jclouds) +
-`jclouds:command:providerId` | 2.9 | For interacting with cloud compute &
blobstore service via jclouds.
-
-| link:camel-jcr/src/main/docs/jcr-component.adoc[JCR] (camel-jcr) +
-`jcr:host/base` | 1.3 | The jcr component allows you to add/read nodes to/from
a JCR compliant content repository.
-
| link:camel-jdbc/src/main/docs/jdbc-component.adoc[JDBC] (camel-jdbc) +
`jdbc:dataSourceName` | 1.2 | The jdbc component enables you to access
databases through JDBC, where SQL queries are sent in the message body.
-| link:camel-jetty9/src/main/docs/jetty-component.adoc[Jetty 9] (camel-jetty9)
+
-`jetty:httpUri` | 1.2 | The jetty component provides HTTP-based endpoints for
consuming and producing HTTP requests.
-
-| link:camel-websocket/src/main/docs/websocket-component.adoc[Jetty Websocket]
(camel-websocket) +
-`websocket:host:port/resourceUri` | 2.10 | The websocket component provides
websocket endpoints with Jetty for communicating with clients using websocket.
-
-| link:camel-jgroups/src/main/docs/jgroups-component.adoc[JGroups]
(camel-jgroups) +
-`jgroups:clusterName` | 2.13 | The jgroups component provides exchange of
messages between Camel and JGroups clusters.
-
-| link:camel-jgroups-raft/src/main/docs/jgroups-raft-component.adoc[JGroups
raft] (camel-jgroups-raft) +
-`jgroups-raft:clusterName` | 2.24 | The jgroups component provides exchange of
messages between Camel and JGroups clusters.
-
-| link:camel-jing/src/main/docs/jing-component.adoc[Jing] (camel-jing) +
-`jing:resourceUri` | 1.1 | Validates the payload of a message using RelaxNG
Syntax using Jing library.
-
| link:camel-jms/src/main/docs/jms-component.adoc[JMS] (camel-jms) +
`jms:destinationType:destinationName` | 1.0 | The jms component allows
messages to be sent to (or consumed from) a JMS Queue or Topic.
-| link:camel-jmx/src/main/docs/jmx-component.adoc[JMX] (camel-jmx) +
-`jmx:serverURL` | 2.6 | The jmx component allows to receive JMX notifications.
-
-| link:camel-jolt/src/main/docs/jolt-component.adoc[JOLT] (camel-jolt) +
-`jolt:resourceUri` | 2.16 | The jolt component allows you to process a JSON
messages using an JOLT specification (such as JSON-JSON transformation).
-
-| link:camel-jpa/src/main/docs/jpa-component.adoc[JPA] (camel-jpa) +
-`jpa:entityType` | 1.0 | The jpa component enables you to store and retrieve
Java objects from databases using JPA.
-
-| link:camel-json-validator/src/main/docs/json-validator-component.adoc[JSON
Schema Validator] (camel-json-validator) +
-`json-validator:resourceUri` | 2.20 | Validates the payload of a message using
NetworkNT JSON Schema library.
-
-| link:camel-jt400/src/main/docs/jt400-component.adoc[JT400] (camel-jt400) +
-`jt400:userID:password/systemName/objectPath.type` | 1.5 | The jt400 component
allows you to exchanges messages with an AS/400 system using data queues or
program call.
-
-| link:camel-kafka/src/main/docs/kafka-component.adoc[Kafka] (camel-kafka) +
-`kafka:topic` | 2.13 | The kafka component allows messages to be sent to (or
consumed from) Apache Kafka brokers.
-
-|
link:camel-kubernetes/src/main/docs/kubernetes-config-maps-component.adoc[Kubernetes
ConfigMap] (camel-kubernetes) +
-`kubernetes-config-maps:masterUrl` | 2.17 | The Kubernetes Configmaps
component provides a producer to execute kubernetes configmap operations.
-
-|
link:camel-kubernetes/src/main/docs/kubernetes-deployments-component.adoc[Kubernetes
Deployments] (camel-kubernetes) +
-`kubernetes-deployments:masterUrl` | 2.20 | The Kubernetes Nodes component
provides a producer to execute kubernetes node operations and a consumer to
consume node events.
-
-| link:camel-kubernetes/src/main/docs/kubernetes-hpa-component.adoc[Kubernetes
HPA] (camel-kubernetes) +
-`kubernetes-hpa:masterUrl` | 2.23 | The Kubernetes HPA component provides a
producer to execute kubernetes hpa operations and a consumer to consume HPA
events.
-
-| link:camel-kubernetes/src/main/docs/kubernetes-job-component.adoc[Kubernetes
Job] (camel-kubernetes) +
-`kubernetes-job:masterUrl` | 2.23 | The Kubernetes Jobs component provides a
producer to execute kubernetes job operations
-
-|
link:camel-kubernetes/src/main/docs/kubernetes-namespaces-component.adoc[Kubernetes
Namespaces] (camel-kubernetes) +
-`kubernetes-namespaces:masterUrl` | 2.17 | The Kubernetes Namespaces component
provides a producer to execute kubernetes namespace operations and a consumer
to consume namespace events.
-
-|
link:camel-kubernetes/src/main/docs/kubernetes-nodes-component.adoc[Kubernetes
Nodes] (camel-kubernetes) +
-`kubernetes-nodes:masterUrl` | 2.17 | The Kubernetes Nodes component provides
a producer to execute kubernetes node operations and a consumer to consume node
events.
-
-|
link:camel-kubernetes/src/main/docs/kubernetes-persistent-volumes-component.adoc[Kubernetes
Persistent Volume] (camel-kubernetes) +
-`kubernetes-persistent-volumes:masterUrl` | 2.17 | The Kubernetes Persistent
Volumes component provides a producer to execute kubernetes persistent volume
operations.
-
-|
link:camel-kubernetes/src/main/docs/kubernetes-persistent-volumes-claims-component.adoc[Kubernetes
Persistent Volume Claim] (camel-kubernetes) +
-`kubernetes-persistent-volumes-claims:masterUrl` | 2.17 | The Kubernetes
Persistent Volumes Claims component provides a producer to execute kubernetes
persistent volume claim operations.
-
-|
link:camel-kubernetes/src/main/docs/kubernetes-pods-component.adoc[Kubernetes
Pods] (camel-kubernetes) +
-`kubernetes-pods:masterUrl` | 2.17 | The Kubernetes Pods component provides a
producer to execute kubernetes pod operations and a consumer to consume pod
events.
-
-|
link:camel-kubernetes/src/main/docs/kubernetes-replication-controllers-component.adoc[Kubernetes
Replication Controller] (camel-kubernetes) +
-`kubernetes-replication-controllers:masterUrl` | 2.17 | The Kubernetes
Replication Controllers component provides a producer to execute kubernetes
replication controller operations and a consumer to consume replication
controller events.
-
-|
link:camel-kubernetes/src/main/docs/kubernetes-resources-quota-component.adoc[Kubernetes
Resources Quota] (camel-kubernetes) +
-`kubernetes-resources-quota:masterUrl` | 2.17 | The Kubernetes Resources Quota
component provides a producer to execute kubernetes resources quota operations.
-
-|
link:camel-kubernetes/src/main/docs/kubernetes-secrets-component.adoc[Kubernetes
Secrets] (camel-kubernetes) +
-`kubernetes-secrets:masterUrl` | 2.17 | The Kubernetes Secrets component
provides a producer to execute kubernetes secret operations.
-
-|
link:camel-kubernetes/src/main/docs/kubernetes-service-accounts-component.adoc[Kubernetes
Service Account] (camel-kubernetes) +
-`kubernetes-service-accounts:masterUrl` | 2.17 | The Kubernetes Service
Accounts component provides a producer to execute service account operations.
-
-|
link:camel-kubernetes/src/main/docs/kubernetes-services-component.adoc[Kubernetes
Services] (camel-kubernetes) +
-`kubernetes-services:masterUrl` | 2.17 | The Kubernetes Service Accounts
component provides a producer to execute service operations and a consumer to
consume service events.
-
| link:camel-language/src/main/docs/language-component.adoc[Language]
(camel-language) +
`language:languageName:resourceUri` | 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.
-| link:camel-ldap/src/main/docs/ldap-component.adoc[LDAP] (camel-ldap) +
-`ldap:dirContextName` | 1.5 | The ldap component allows you to perform
searches in LDAP servers using filters as the message payload.
-
-| link:camel-ldif/src/main/docs/ldif-component.adoc[LDIF] (camel-ldif) +
-`ldif:ldapConnectionName` | 2.20 | The ldif component allows you to do updates
on an LDAP server from a LDIF body content.
-
-|
link:camel-linkedin/camel-linkedin-component/src/main/docs/linkedin-component.adoc[Linkedin]
(camel-linkedin) +
-`linkedin:apiName/methodName` | 2.14 | The linkedin component is used for
retrieving LinkedIn user profiles, connections, companies, groups, posts, etc.
-
| link:camel-log/src/main/docs/log-component.adoc[Log] (camel-log) +
`log:loggerName` | 1.1 | The log component logs message exchanges to the
underlying logging mechanism.
-| link:camel-lucene/src/main/docs/lucene-component.adoc[Lucene] (camel-lucene)
+
-`lucene:host:operation` | 2.2 | To insert or query from Apache Lucene
databases.
-
-| link:camel-lumberjack/src/main/docs/lumberjack-component.adoc[Lumberjack]
(camel-lumberjack) +
-`lumberjack:host:port` | 2.18 | The lumberjack retrieves logs sent over the
network using the Lumberjack protocol.
-
-| link:camel-mail/src/main/docs/mail-component.adoc[Mail] (camel-mail) +
-`imap:host:port` | 1.0 | To send or receive emails using imap/pop3 or smtp
protocols.
-
-| link:camel-master/src/main/docs/master-component.adoc[Master] (camel-master)
+
-`master:namespace:delegateUri` | 2.20 | Represents an endpoint which only
becomes active when the CamelClusterView has the leadership.
-
-| link:camel-metrics/src/main/docs/metrics-component.adoc[Metrics]
(camel-metrics) +
-`metrics:metricsType:metricsName` | 2.14 | To collect various metrics directly
from Camel routes using the DropWizard metrics library.
-
-| link:camel-micrometer/src/main/docs/micrometer-component.adoc[Micrometer]
(camel-micrometer) +
-`micrometer:metricsType:metricsName` | 2.22 | To collect various metrics
directly from Camel routes using the Micrometer library.
-
-| link:camel-mina2/src/main/docs/mina2-component.adoc[Mina2] (camel-mina2) +
-`mina2:protocol:host:port` | 2.10 | Socket level networking using TCP or UDP
with the Apache Mina 2.x library.
-
-| link:camel-mllp/src/main/docs/mllp-component.adoc[MLLP] (camel-mllp) +
-`mllp:hostname:port` | 2.17 | Provides functionality required by Healthcare
providers to communicate with other systems using the MLLP protocol.
-
| link:../core/camel-core/src/main/docs/mock-component.adoc[Mock] (camel-core)
+
`mock:name` | 1.0 | The mock component is used for testing routes and
mediation rules using mocks.
-| link:camel-mongodb3/src/main/docs/mongodb3-component.adoc[MongoDB]
(camel-mongodb3) +
-`mongodb3:connectionBean` | 2.19 | Component for working with documents stored
in MongoDB database.
-
-|
link:camel-mongodb-gridfs/src/main/docs/mongodb-gridfs-component.adoc[MongoDB
GridFS] (camel-mongodb-gridfs) +
-`mongodb-gridfs:connectionBean` | 2.18 | Component for working with MongoDB
GridFS.
-
-| link:camel-mqtt/src/main/docs/mqtt-component.adoc[MQTT] (camel-mqtt) +
-`mqtt:name` | 2.10 | Component for communicating with MQTT M2M message brokers
using FuseSource MQTT Client.
-
-| link:camel-msv/src/main/docs/msv-component.adoc[MSV] (camel-msv) +
-`msv:resourceUri` | 1.1 | Validates the payload of a message using the MSV
Library.
-
-| link:camel-mustache/src/main/docs/mustache-component.adoc[Mustache]
(camel-mustache) +
-`mustache:resourceUri` | 2.12 | Transforms the message using a Mustache
template.
-
-| link:camel-mvel/src/main/docs/mvel-component.adoc[MVEL] (camel-mvel) +
-`mvel:resourceUri` | 2.12 | Transforms the message using a MVEL template.
-
-| link:camel-mybatis/src/main/docs/mybatis-component.adoc[MyBatis]
(camel-mybatis) +
-`mybatis:statement` | 2.7 | Performs a query, poll, insert, update or delete
in a relational database using MyBatis.
-
-| link:camel-mybatis/src/main/docs/mybatis-bean-component.adoc[MyBatis Bean]
(camel-mybatis) +
-`mybatis-bean:beanName:methodName` | 2.22 | Performs a query, insert, update
or delete in a relational database using MyBatis.
-
-| link:camel-nagios/src/main/docs/nagios-component.adoc[Nagios] (camel-nagios)
+
-`nagios:host:port` | 2.3 | To send passive checks to Nagios using JSendNSCA.
-
-| link:camel-nats/src/main/docs/nats-component.adoc[Nats] (camel-nats) +
-`nats:servers` | 2.17 | The nats component allows you produce and consume
messages from NATS.
-
-| link:camel-netty4/src/main/docs/netty4-component.adoc[Netty4] (camel-netty4)
+
-`netty4:protocol:host:port` | 2.14 | Socket level networking using TCP or UDP
with the Netty 4.x library.
-
-| link:camel-netty4-http/src/main/docs/netty4-http-component.adoc[Netty4 HTTP]
(camel-netty4-http) +
-`netty4-http:protocol:host:port/path` | 2.14 | Netty HTTP server and client
using the Netty 4.x library.
-
-| link:camel-nsq/src/main/docs/nsq-component.adoc[NSQ] (camel-nsq) +
-`nsq:lookupServer` | 2.23 | Represents a nsq endpoint.
-
-|
link:camel-olingo2/camel-olingo2-component/src/main/docs/olingo2-component.adoc[Olingo2]
(camel-olingo2) +
-`olingo2:apiName/methodName` | 2.14 | Communicates with OData 2.0 services
using Apache Olingo.
-
-|
link:camel-olingo4/camel-olingo4-component/src/main/docs/olingo4-component.adoc[Olingo4]
(camel-olingo4) +
-`olingo4:apiName/methodName` | 2.19 | Communicates with OData 4.0 services
using Apache Olingo OData API.
-
-| link:camel-milo/src/main/docs/milo-client-component.adoc[OPC UA Client]
(camel-milo) +
-`milo-client:endpointUri` | 2.19 | Connect to OPC UA servers using the binary
protocol for acquiring telemetry data
-
-| link:camel-milo/src/main/docs/milo-server-component.adoc[OPC UA Server]
(camel-milo) +
-`milo-server:itemId` | 2.19 | Make telemetry data available as an OPC UA server
-
-|
link:camel-kubernetes/src/main/docs/openshift-build-configs-component.adoc[Openshift
Build Config] (camel-kubernetes) +
-`openshift-build-configs:masterUrl` | 2.17 | The Kubernetes Build Config
component provides a producer to execute kubernetes build config operations.
-
-|
link:camel-kubernetes/src/main/docs/openshift-builds-component.adoc[Openshift
Builds] (camel-kubernetes) +
-`openshift-builds:masterUrl` | 2.17 | The Openshift Builds component provides
a producer to execute openshift build operations.
-
-| link:camel-openstack/src/main/docs/openstack-cinder-component.adoc[OpenStack
Cinder] (camel-openstack) +
-`openstack-cinder:host` | 2.19 | The openstack-cinder component allows
messages to be sent to an OpenStack block storage services.
-
-| link:camel-openstack/src/main/docs/openstack-glance-component.adoc[OpenStack
Glance] (camel-openstack) +
-`openstack-glance:host` | 2.19 | The openstack-glance component allows
messages to be sent to an OpenStack image services.
-
-|
link:camel-openstack/src/main/docs/openstack-keystone-component.adoc[OpenStack
Keystone] (camel-openstack) +
-`openstack-keystone:host` | 2.19 | The openstack-keystone component allows
messages to be sent to an OpenStack identity services.
-
-|
link:camel-openstack/src/main/docs/openstack-neutron-component.adoc[OpenStack
Neutron] (camel-openstack) +
-`openstack-neutron:host` | 2.19 | The openstack-neutron component allows
messages to be sent to an OpenStack network services.
-
-| link:camel-openstack/src/main/docs/openstack-nova-component.adoc[OpenStack
Nova] (camel-openstack) +
-`openstack-nova:host` | 2.19 | The openstack-nova component allows messages to
be sent to an OpenStack compute services.
-
-| link:camel-openstack/src/main/docs/openstack-swift-component.adoc[OpenStack
Swift] (camel-openstack) +
-`openstack-swift:host` | 2.19 | The openstack-swift component allows messages
to be sent to an OpenStack object storage services.
-
-| link:camel-optaplanner/src/main/docs/optaplanner-component.adoc[OptaPlanner]
(camel-optaplanner) +
-`optaplanner:configFile` | 2.13 | Solves the planning problem contained in a
message with OptaPlanner.
-
-| link:camel-eventadmin/src/main/docs/eventadmin-component.adoc[OSGi
EventAdmin] (camel-eventadmin) +
-`eventadmin:topic` | 2.6 | The eventadmin component can be used in an OSGi
environment to receive OSGi EventAdmin events and process them.
-
-| link:camel-paxlogging/src/main/docs/paxlogging-component.adoc[OSGi PAX
Logging] (camel-paxlogging) +
-`paxlogging:appender` | 2.6 | The paxlogging component can be used in an OSGi
environment to receive PaxLogging events and process them.
-
-| link:camel-paho/src/main/docs/paho-component.adoc[Paho] (camel-paho) +
-`paho:topic` | 2.16 | Component for communicating with MQTT M2M message
brokers using Eclipse Paho MQTT Client.
-
-| link:camel-pdf/src/main/docs/pdf-component.adoc[PDF] (camel-pdf) +
-`pdf:operation` | 2.16 | The pdf components provides the ability to create,
modify or extract content from PDF documents.
-
-| link:camel-pgevent/src/main/docs/pgevent-component.adoc[PostgresSQL Event]
(camel-pgevent) +
-`pgevent:host:port/database/channel` | 2.15 | The pgevent component allows for
producing/consuming PostgreSQL events related to the listen/notify commands.
-
-| link:camel-printer/src/main/docs/lpr-component.adoc[Printer] (camel-printer)
+
-`lpr:hostname:port/printername` | 2.1 | The printer component is used for
sending messages to printers as print jobs.
-
| link:camel-properties/src/main/docs/properties-component.adoc[Properties]
(camel-properties) +
`properties:key` | 2.3 | The properties component is used for using property
placeholders in endpoint uris.
-| link:camel-pubnub/src/main/docs/pubnub-component.adoc[PubNub] (camel-pubnub)
+
-`pubnub:channel` | 2.19 | To send and receive messages to PubNub data stream
network for connected devices.
-
-| link:camel-quartz2/src/main/docs/quartz2-component.adoc[Quartz2]
(camel-quartz2) +
-`quartz2:groupName/triggerName` | 2.12 | Provides a scheduled delivery of
messages using the Quartz 2.x scheduler.
-
-| link:camel-quickfix/src/main/docs/quickfix-component.adoc[QuickFix]
(camel-quickfix) +
-`quickfix:configurationName` | 2.1 | The quickfix component allows to send
Financial Interchange (FIX) messages to the QuickFix engine.
-
-| link:camel-rabbitmq/src/main/docs/rabbitmq-component.adoc[RabbitMQ]
(camel-rabbitmq) +
-`rabbitmq:exchangeName` | 2.12 | The rabbitmq component allows you produce and
consume messages from RabbitMQ instances.
-
-|
link:camel-reactive-streams/src/main/docs/reactive-streams-component.adoc[Reactive
Streams] (camel-reactive-streams) +
-`reactive-streams:stream` | 2.19 | Reactive Camel using reactive streams
-
| link:camel-ref/src/main/docs/ref-component.adoc[Ref] (camel-ref) +
`ref:name` | 1.2 | The ref component is used for lookup of existing endpoints
bound in the Registry.
@@ -679,204 +64,36 @@ Number of Components: 290 in 210 JAR artifacts (0
deprecated)
| link:camel-rest/src/main/docs/rest-api-component.adoc[REST API] (camel-rest)
+
`rest-api:path/contextIdPattern` | 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.
-| link:camel-rest-swagger/src/main/docs/rest-swagger-component.adoc[REST
Swagger] (camel-rest-swagger) +
-`rest-swagger:specificationUri#operationId` | 2.19 | An awesome REST endpoint
backed by Swagger specifications.
-
-| link:camel-restlet/src/main/docs/restlet-component.adoc[Restlet]
(camel-restlet) +
-`restlet:protocol:host:port/uriPattern` | 2.0 | Component for consuming and
producing Restful resources using Restlet.
-
-| link:camel-rmi/src/main/docs/rmi-component.adoc[RMI] (camel-rmi) +
-`rmi:hostname:port/name` | 1.0 | The rmi component is for invoking Java RMI
beans from Camel.
-
-| link:camel-rss/src/main/docs/rss-component.adoc[RSS] (camel-rss) +
-`rss:feedUri` | 2.0 | The rss component is used for consuming RSS feeds.
-
| link:camel-saga/src/main/docs/saga-component.adoc[Saga] (camel-saga) +
`saga:action` | 2.21 | The saga component provides access to advanced options
for managing the flow in the Saga EIP.
-|
link:camel-salesforce/camel-salesforce-component/src/main/docs/salesforce-component.adoc[Salesforce]
(camel-salesforce) +
-`salesforce:operationName:topicName` | 2.12 | The salesforce component is used
for integrating Camel with the massive Salesforce API.
-
-| link:camel-sap-netweaver/src/main/docs/sap-netweaver-component.adoc[SAP
NetWeaver] (camel-sap-netweaver) +
-`sap-netweaver:url` | 2.12 | The sap-netweaver component integrates with the
SAP NetWeaver Gateway using HTTP transports.
-
| link:camel-scheduler/src/main/docs/scheduler-component.adoc[Scheduler]
(camel-scheduler) +
`scheduler:name` | 2.15 | The scheduler component is used for generating
message exchanges when a scheduler fires.
-| link:camel-schematron/src/main/docs/schematron-component.adoc[Schematron]
(camel-schematron) +
-`schematron:path` | 2.15 | Validates the payload of a message using the
Schematron Library.
-
-| link:camel-jsch/src/main/docs/scp-component.adoc[SCP] (camel-jsch) +
-`scp:host:port/directoryName` | 2.10 | To copy files using the secure copy
protocol (SCP).
-
| link:camel-seda/src/main/docs/seda-component.adoc[SEDA] (camel-seda) +
`seda:name` | 1.1 | The seda component provides asynchronous call to another
endpoint from any CamelContext in the same JVM.
-| link:camel-service/src/main/docs/service-component.adoc[Service]
(camel-service) +
-`service:serviceName:delegateUri` | 2.22 | Represents an endpoint which is
registered to a Service Registry such as Consul, Etcd.
-
-|
link:camel-servicenow/camel-servicenow-component/src/main/docs/servicenow-component.adoc[ServiceNow]
(camel-servicenow) +
-`servicenow:instanceName` | 2.18 | The servicenow component is used to
integrate Camel with ServiceNow cloud services.
-
-| link:camel-servlet/src/main/docs/servlet-component.adoc[Servlet]
(camel-servlet) +
-`servlet:contextPath` | 2.0 | To use a HTTP Servlet as entry for Camel routes
when running in a servlet container.
-
-| link:camel-ftp/src/main/docs/sftp-component.adoc[SFTP] (camel-ftp) +
-`sftp:host:port/directoryName` | 1.1 | The sftp (FTP over SSH) component is
used for uploading or downloading files from SFTP servers.
-
-| link:camel-sjms/src/main/docs/sjms-component.adoc[Simple JMS] (camel-sjms) +
-`sjms:destinationType:destinationName` | 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).
-
-| link:camel-sjms/src/main/docs/sjms-batch-component.adoc[Simple JMS Batch]
(camel-sjms) +
-`sjms-batch:destinationName` | 2.16 | The sjms-batch component is a
specialized for highly performant, transactional batch consumption from a JMS
queue.
-
-| link:camel-sjms2/src/main/docs/sjms2-component.adoc[Simple JMS2]
(camel-sjms2) +
-`sjms2:destinationType:destinationName` | 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).
-
-| link:camel-sip/src/main/docs/sip-component.adoc[SIP] (camel-sip) +
-`sip:uri` | 2.5 | To send and receive messages using the SIP protocol (used in
telco and mobile).
-
-| link:camel-slack/src/main/docs/slack-component.adoc[Slack] (camel-slack) +
-`slack:channel` | 2.16 | The slack component allows you to send messages to
Slack.
-
-| link:camel-smpp/src/main/docs/smpp-component.adoc[SMPP] (camel-smpp) +
-`smpp:host:port` | 2.2 | To send and receive SMS using a SMSC (Short Message
Service Center).
-
-| link:camel-snmp/src/main/docs/snmp-component.adoc[SNMP] (camel-snmp) +
-`snmp:host:port` | 2.1 | The snmp component gives you the ability to poll SNMP
capable devices or receiving traps.
-
-| link:camel-solr/src/main/docs/solr-component.adoc[Solr] (camel-solr) +
-`solr:url` | 2.9 | The solr component allows you to interface with an Apache
Lucene Solr server.
-
-| link:camel-spark-rest/src/main/docs/spark-rest-component.adoc[Spark Rest]
(camel-spark-rest) +
-`spark-rest:verb:path` | 2.14 | The spark-rest component is used for hosting
REST services which has been defined using Camel rest-dsl.
-
-| link:camel-splunk/src/main/docs/splunk-component.adoc[Splunk] (camel-splunk)
+
-`splunk:name` | 2.13 | The splunk component allows to publish or search for
events in Splunk.
-
-| link:camel-spring-batch/src/main/docs/spring-batch-component.adoc[Spring
Batch] (camel-spring-batch) +
-`spring-batch:jobName` | 2.10 | The spring-batch component allows to send
messages to Spring Batch for further processing.
-
| link:camel-spring/src/main/docs/spring-event-component.adoc[Spring Event]
(camel-spring) +
`spring-event:name` | 1.4 | The spring-event component allows to listen for
Spring Application Events.
-|
link:camel-spring-integration/src/main/docs/spring-integration-component.adoc[Spring
Integration] (camel-spring-integration) +
-`spring-integration:defaultChannel` | 1.4 | Bridges Camel with Spring
Integration.
-
-| link:camel-spring-ldap/src/main/docs/spring-ldap-component.adoc[Spring LDAP]
(camel-spring-ldap) +
-`spring-ldap:templateName` | 2.11 | The spring-ldap component allows you to
perform searches in LDAP servers using filters as the message payload.
-
-| link:camel-spring-redis/src/main/docs/spring-redis-component.adoc[Spring
Redis] (camel-spring-redis) +
-`spring-redis:host:port` | 2.11 | The spring-redis component allows sending
and receiving messages from Redis.
-
-| link:camel-spring-ws/src/main/docs/spring-ws-component.adoc[Spring
WebService] (camel-spring-ws) +
-`spring-ws:type:lookupKey:webServiceEndpointUri` | 2.6 | The spring-ws
component is used for SOAP WebServices using Spring WebServices.
-
-| link:camel-sql/src/main/docs/sql-component.adoc[SQL] (camel-sql) +
-`sql:query` | 1.4 | The sql component allows you to work with databases using
JDBC SQL queries.
-
-| link:camel-sql/src/main/docs/sql-stored-component.adoc[SQL Stored Procedure]
(camel-sql) +
-`sql-stored:template` | 2.17 | The sql component allows you to work with
databases using JDBC Stored Procedure queries.
-
-| link:camel-ssh/src/main/docs/ssh-component.adoc[SSH] (camel-ssh) +
-`ssh:host:port` | 2.10 | The ssh component enables access to SSH servers such
that you can send an SSH command, and process the response.
-
-| link:camel-stax/src/main/docs/stax-component.adoc[StAX] (camel-stax) +
-`stax:contentHandlerClass` | 2.9 | The stax component allows messages to be
process through a SAX ContentHandler.
-
-| link:camel-stomp/src/main/docs/stomp-component.adoc[Stomp] (camel-stomp) +
-`stomp:destination` | 2.12 | The stomp component is used for communicating
with Stomp compliant message brokers.
-
-| link:camel-stream/src/main/docs/stream-component.adoc[Stream] (camel-stream)
+
-`stream:kind` | 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.
-
-|
link:camel-stringtemplate/src/main/docs/string-template-component.adoc[String
Template] (camel-stringtemplate) +
-`string-template:resourceUri` | 1.2 | Transforms the message using a String
template.
-
| link:camel-stub/src/main/docs/stub-component.adoc[Stub] (camel-stub) +
`stub:name` | 2.10 | The stub component provides a simple way to stub out any
physical endpoints while in development or testing.
-| link:camel-telegram/src/main/docs/telegram-component.adoc[Telegram]
(camel-telegram) +
-`telegram:type/authorizationToken` | 2.18 | The telegram component provides
access to the Telegram Bot API.
-
| link:../core/camel-core/src/main/docs/test-component.adoc[Test] (camel-core)
+
`test:name` | 1.3 | The test component extends the mock component by on
startup to pull messages from another endpoint to set the expected message
bodies.
-| link:camel-thrift/src/main/docs/thrift-component.adoc[Thrift] (camel-thrift)
+
-`thrift:host:port/service` | 2.20 | The Thrift component allows to call and
expose remote procedures (RPC) with Apache Thrift data format and serialization
mechanism
-
-| link:camel-tika/src/main/docs/tika-component.adoc[Tika] (camel-tika) +
-`tika:operation` | 2.19 | This component integrates with Apache Tika to
extract content and metadata from thousands of file types.
-
| link:camel-timer/src/main/docs/timer-component.adoc[Timer] (camel-timer) +
`timer:timerName` | 1.0 | The timer component is used for generating message
exchanges when a timer fires.
-| link:camel-twilio/src/main/docs/twilio-component.adoc[Twilio] (camel-twilio)
+
-`twilio:apiName/methodName` | 2.20 | The Twilio component allows you to
interact with the Twilio REST APIs using Twilio Java SDK.
-
-|
link:camel-twitter/src/main/docs/twitter-directmessage-component.adoc[Twitter
Direct Message] (camel-twitter) +
-`twitter-directmessage:user` | 2.10 | The Twitter Direct Message Component
consumes/produces user's direct messages.
-
-| link:camel-twitter/src/main/docs/twitter-search-component.adoc[Twitter
Search] (camel-twitter) +
-`twitter-search:keywords` | 2.10 | The Twitter Search component consumes
search results.
-
-| link:camel-twitter/src/main/docs/twitter-streaming-component.adoc[Twitter
Streaming] (camel-twitter) +
-`twitter-streaming:streamingType` | 2.10 | The Twitter Streaming component
consumes twitter statuses using Streaming API.
-
-| link:camel-twitter/src/main/docs/twitter-timeline-component.adoc[Twitter
Timeline] (camel-twitter) +
-`twitter-timeline:timelineType` | 2.10 | The Twitter Timeline component
consumes twitter timeline or update the status of specific user.
-
-| link:camel-undertow/src/main/docs/undertow-component.adoc[Undertow]
(camel-undertow) +
-`undertow:httpURI` | 2.16 | The undertow component provides HTTP and WebSocket
based endpoints for consuming and producing HTTP/WebSocket requests.
-
| link:camel-validator/src/main/docs/validator-component.adoc[Validator]
(camel-validator) +
`validator:resourceUri` | 1.1 | Validates the payload of a message using XML
Schema and JAXP Validation.
-| link:camel-velocity/src/main/docs/velocity-component.adoc[Velocity]
(camel-velocity) +
-`velocity:resourceUri` | 1.2 | Transforms the message using a Velocity
template.
-
-| link:camel-vertx/src/main/docs/vertx-component.adoc[Vert.x] (camel-vertx) +
-`vertx:address` | 2.12 | The vertx component is used for sending and receive
messages from a vertx event bus.
-
| link:camel-vm/src/main/docs/vm-component.adoc[VM] (camel-vm) +
`vm:name` | 1.1 | The vm component provides asynchronous call to another
endpoint from the same CamelContext.
-| link:camel-weather/src/main/docs/weather-component.adoc[Weather]
(camel-weather) +
-`weather:name` | 2.12 | Polls the weather information from Open Weather Map.
-
-| link:camel-web3j/src/main/docs/web3j-component.adoc[Web3j Ethereum
Blockchain] (camel-web3j) +
-`web3j:nodeAddress` | 2.22 | The web3j component uses the Web3j client API and
allows you to add/read nodes to/from a web3j compliant content repositories.
-
-| link:camel-wordpress/src/main/docs/wordpress-component.adoc[Wordpress]
(camel-wordpress) +
-`wordpress:operationDetail` | 2.21 | Integrates Camel with Wordpress.
-
-| link:camel-xchange/src/main/docs/xchange-component.adoc[XChange]
(camel-xchange) +
-`xchange:name` | 2.21 | The camel-xchange component provide access to many
bitcoin and altcoin exchanges for trading and accessing market data.
-
-| link:camel-xmlsecurity/src/main/docs/xmlsecurity-component.adoc[XML
Security] (camel-xmlsecurity) +
-`xmlsecurity:command:name` | 2.12 | Used to sign and verify exchanges using
the XML signature specification.
-
-| link:camel-xmpp/src/main/docs/xmpp-component.adoc[XMPP] (camel-xmpp) +
-`xmpp:host:port/participant` | 1.0 | To send and receive messages from a XMPP
(chat) server.
-
-| link:camel-saxon/src/main/docs/xquery-component.adoc[XQuery] (camel-saxon) +
-`xquery:resourceUri` | 1.0 | Transforms the message using a XQuery template
using Saxon.
-
| link:camel-xslt/src/main/docs/xslt-component.adoc[XSLT] (camel-xslt) +
`xslt:resourceUri` | 1.3 | Transforms the message using a XSLT template.
-| link:camel-yammer/src/main/docs/yammer-component.adoc[Yammer] (camel-yammer)
+
-`yammer:function` | 2.12 | The yammer component allows you to interact with
the Yammer enterprise social network.
-
-| link:camel-zendesk/src/main/docs/zendesk-component.adoc[Zendesk]
(camel-zendesk) +
-`zendesk:methodName` | 2.19 | Allows producing messages to manage Zendesk
ticket, user, organization, etc.
-
-| link:camel-zookeeper/src/main/docs/zookeeper-component.adoc[ZooKeeper]
(camel-zookeeper) +
-`zookeeper:serverUrls/path` | 2.9 | The zookeeper component allows interaction
with a ZooKeeper cluster.
-
-|
link:camel-zookeeper-master/src/main/docs/zookeeper-master-component.adoc[ZooKeeper
Master] (camel-zookeeper-master) +
-`zookeeper-master:groupName:consumerEndpointUri` | 2.19 | Represents an
endpoint which only becomes active when it obtains the master lock
-
|===
// components: END
@@ -884,101 +101,19 @@ Number of Components: 290 in 210 JAR artifacts (0
deprecated)
==== Data Formats
// dataformats: START
-Number of Data Formats: 45 in 35 JAR artifacts (0 deprecated)
+Number of Data Formats: 4 in 1 JAR artifacts (0 deprecated)
[width="100%",cols="4,1,5",options="header"]
|===
| Data Format | Available From | Description
-| link:camel-asn1/src/main/docs/asn1-dataformat.adoc[ASN.1 File] (camel-asn1)
| 2.20 | The ASN.1 data format is used for file transfer with
telecommunications protocols.
-
-| link:camel-avro/src/main/docs/avro-dataformat.adoc[Avro] (camel-avro) | 2.14
| The Avro data format is used for serialization and deserialization of
messages using Apache Avro binary dataformat.
-
-| link:camel-barcode/src/main/docs/barcode-dataformat.adoc[Barcode]
(camel-barcode) | 2.14 | The Barcode data format is used for creating barccode
images (such as QR-Code)
-
-| link:camel-base64/src/main/docs/base64-dataformat.adoc[Base64]
(camel-base64) | 2.11 | The Base64 data format is used for base64 encoding and
decoding.
-
-| link:camel-beanio/src/main/docs/beanio-dataformat.adoc[BeanIO]
(camel-beanio) | 2.10 | The BeanIO data format is used for working with flat
payloads (such as CSV, delimited, or fixed length formats).
-
-| link:camel-bindy/src/main/docs/bindy-dataformat.adoc[Bindy CSV]
(camel-bindy) | 2.0 | The Bindy data format is used for working with flat
payloads (such as CSV, delimited, fixed length formats, or FIX messages).
-
-| link:camel-bindy/src/main/docs/bindy-dataformat.adoc[Bindy Fixed Length]
(camel-bindy) | 2.0 | The Bindy data format is used for working with flat
payloads (such as CSV, delimited, fixed length formats, or FIX messages).
-
-| link:camel-bindy/src/main/docs/bindy-dataformat.adoc[Bindy Key Value Pair]
(camel-bindy) | 2.0 | The Bindy data format is used for working with flat
payloads (such as CSV, delimited, fixed length formats, or FIX messages).
-
-| link:camel-boon/src/main/docs/boon-dataformat.adoc[Boon] (camel-boon) | 2.16
| Boon data format is used for unmarshal a JSon payload to POJO or to marshal
POJO back to JSon payload.
-
-| link:camel-crypto/src/main/docs/crypto-dataformat.adoc[Crypto (Java
Cryptographic Extension)] (camel-crypto) | 2.3 | Crypto data format is used for
encrypting and decrypting of messages using Java Cryptographic Extension.
-
-| link:camel-csv/src/main/docs/csv-dataformat.adoc[CSV] (camel-csv) | 1.3 |
The CSV data format is used for handling CSV payloads.
-
-|
link:camel-fhir/camel-fhir-component/src/main/docs/fhirJson-dataformat.adoc[FHIR
JSon] (camel-fhir) | 2.21 | The FHIR JSon data format is used to
marshall/unmarshall to/from FHIR objects to/from JSON.
-
-|
link:camel-fhir/camel-fhir-component/src/main/docs/fhirXml-dataformat.adoc[FHIR
XML] (camel-fhir) | 2.21 | The FHIR XML data format is used to
marshall/unmarshall from/to FHIR objects to/from XML.
-
-| link:camel-flatpack/src/main/docs/flatpack-dataformat.adoc[Flatpack]
(camel-flatpack) | 2.1 | The Flatpack data format is used for working with flat
payloads (such as CSV, delimited, or fixed length formats).
-
| link:../core/camel-core/src/main/docs/gzip-dataformat.adoc[GZip]
(camel-core) | 2.0 | The GZip data format is a message compression and
de-compression format (which works with the popular gzip/gunzip tools).
-| link:camel-hl7/src/main/docs/hl7-dataformat.adoc[HL7] (camel-hl7) | 2.0 |
The HL7 data format can be used to marshal or unmarshal HL7 (Health Care) model
objects.
-
-| link:camel-ical/src/main/docs/ical-dataformat.adoc[iCal] (camel-ical) | 2.12
| The iCal dataformat is used for working with iCalendar messages.
-
-| link:camel-jacksonxml/src/main/docs/jacksonxml-dataformat.adoc[JacksonXML]
(camel-jacksonxml) | 2.16 | JacksonXML data format is used for unmarshal a XML
payload to POJO or to marshal POJO back to XML payload.
-
| link:../core/camel-core/src/main/docs/serialization-dataformat.adoc[Java
Object Serialization] (camel-core) | 2.12 | Serialization is a data format
which uses the standard Java Serialization mechanism to unmarshal a binary
payload into Java objects or to marshal Java objects into a binary blob.
-| link:camel-jaxb/src/main/docs/jaxb-dataformat.adoc[JAXB] (camel-jaxb) | 1.0
| JAXB data format uses the JAXB2 XML marshalling standard to unmarshal an XML
payload into Java objects or to marshal Java objects into an XML payload.
-
-| link:camel-jibx/src/main/docs/jibx-dataformat.adoc[JiBX] (camel-jibx) | 2.6
| JiBX data format is used for unmarshal a XML payload to POJO or to marshal
POJO back to XML payload.
-
-| link:camel-fastjson/src/main/docs/json-fastjson-dataformat.adoc[JSon
Fastjson] (camel-fastjson) | 2.20 | JSon data format is used for unmarshal a
JSon payload to POJO or to marshal POJO back to JSon payload.
-
-| link:camel-gson/src/main/docs/json-gson-dataformat.adoc[JSon GSon]
(camel-gson) | 2.10 | JSon data format is used for unmarshal a JSon payload to
POJO or to marshal POJO back to JSon payload.
-
-| link:camel-jackson/src/main/docs/json-jackson-dataformat.adoc[JSon Jackson]
(camel-jackson) | 2.0 | JSon data format is used for unmarshal a JSon payload
to POJO or to marshal POJO back to JSon payload.
-
-| link:camel-johnzon/src/main/docs/json-johnzon-dataformat.adoc[JSon Johnzon]
(camel-johnzon) | 2.18 | JSon data format is used for unmarshal a JSon payload
to POJO or to marshal POJO back to JSon payload.
-
-| link:camel-xstream/src/main/docs/json-xstream-dataformat.adoc[JSon XStream]
(camel-xstream) | 2.0 | JSon data format is used for unmarshal a JSon payload
to POJO or to marshal POJO back to JSon payload.
-
-| link:camel-lzf/src/main/docs/lzf-dataformat.adoc[LZF Deflate Compression]
(camel-lzf) | 2.17 | The LZF data format is a message compression and
de-compression format (uses the LZF deflate algorithm).
-
-| link:camel-mail/src/main/docs/mime-multipart-dataformat.adoc[MIME Multipart]
(camel-mail) | 2.17 | The MIME Multipart data format can marshal a Camel
message with attachments into a Camel message having a MIME-Multipart message
as message body (and no attachments), and vise-versa when unmarshalling.
-
-| link:camel-crypto/src/main/docs/pgp-dataformat.adoc[PGP] (camel-crypto) |
2.9 | PGP data format is used for encrypting and decrypting of messages using
Java Cryptographic Extension and PGP.
-
-| link:camel-protobuf/src/main/docs/protobuf-dataformat.adoc[Protobuf]
(camel-protobuf) | 2.2 | The Protobuf data format is used for serializing
between Java objects and the Google Protobuf protocol.
-
-| link:camel-rss/src/main/docs/rss-dataformat.adoc[RSS] (camel-rss) | 2.1 |
RSS data format is used for working with RSS sync feed Java Objects and
transforming to XML and vice-versa.
-
-| link:camel-soap/src/main/docs/soapjaxb-dataformat.adoc[SOAP] (camel-soap) |
2.3 | SOAP is a data format which uses JAXB2 and JAX-WS annotations to marshal
and unmarshal SOAP payloads.
-
| link:../core/camel-core/src/main/docs/string-dataformat.adoc[String
Encoding] (camel-core) | 2.12 | String data format is a textual based format
that supports character encoding.
-| link:camel-syslog/src/main/docs/syslog-dataformat.adoc[Syslog]
(camel-syslog) | 2.6 | The Syslog dataformat is used for working with RFC3164
and RFC5424 messages (logging and monitoring).
-
-| link:camel-tarfile/src/main/docs/tarfile-dataformat.adoc[Tar File]
(camel-tarfile) | 2.16 | The Tar File data format is a message compression and
de-compression format of tar files.
-
-| link:camel-thrift/src/main/docs/thrift-dataformat.adoc[Thrift]
(camel-thrift) | 2.20 | The Thrift data format is used for serialization and
deserialization of messages using Apache Thrift binary dataformat.
-
-| link:camel-tagsoup/src/main/docs/tidyMarkup-dataformat.adoc[TidyMarkup]
(camel-tagsoup) | 2.0 | TidyMarkup data format is used for parsing HTML and
return it as pretty well-formed HTML.
-
-|
link:camel-univocity-parsers/src/main/docs/univocity-csv-dataformat.adoc[uniVocity
CSV] (camel-univocity-parsers) | 2.15 | The uniVocity CSV data format is used
for working with CSV (Comma Separated Values) flat payloads.
-
-|
link:camel-univocity-parsers/src/main/docs/univocity-fixed-dataformat.adoc[uniVocity
Fixed Length] (camel-univocity-parsers) | 2.15 | The uniVocity Fixed Length
data format is used for working with fixed length flat payloads.
-
-|
link:camel-univocity-parsers/src/main/docs/univocity-tsv-dataformat.adoc[uniVocity
TSV] (camel-univocity-parsers) | 2.15 | The uniVocity TSV data format is used
for working with TSV (Tabular Separated Values) flat payloads.
-
-| link:camel-xmlsecurity/src/main/docs/secureXML-dataformat.adoc[XML Security]
(camel-xmlsecurity) | 2.0 | The XML Security data format facilitates encryption
and decryption of XML payloads.
-
-| link:camel-xstream/src/main/docs/xstream-dataformat.adoc[XStream]
(camel-xstream) | 1.3 | XSTream data format is used for unmarshal a XML payload
to POJO or to marshal POJO back to XML payload.
-
-| link:camel-snakeyaml/src/main/docs/yaml-snakeyaml-dataformat.adoc[YAML
SnakeYAML] (camel-snakeyaml) | 2.17 | YAML is a data format to marshal and
unmarshal Java objects to and from YAML.
-
| link:../core/camel-core/src/main/docs/zip-dataformat.adoc[Zip Deflate
Compression] (camel-core) | 2.12 | Zip Deflate Compression data format is a
message compression and de-compression format (not zip files).
-
-| link:camel-zipfile/src/main/docs/zipfile-dataformat.adoc[Zip File]
(camel-zipfile) | 2.11 | The Zip File data format is a message compression and
de-compression format of zip files.
|===
// dataformats: END
@@ -986,7 +121,7 @@ Number of Data Formats: 45 in 35 JAR artifacts (0
deprecated)
==== Expression Languages
// languages: START
-Number of Languages: 18 in 9 JAR artifacts (1 deprecated)
+Number of Languages: 12 in 3 JAR artifacts (0 deprecated)
[width="100%",cols="4,1,5",options="header"]
|===
@@ -1000,20 +135,10 @@ Number of Languages: 18 in 9 JAR artifacts (1 deprecated)
| link:../core/camel-core/src/main/docs/file-language.adoc[File] (camel-core)
| 1.1 | For expressions and predicates using the file/simple language
-| link:camel-groovy/src/main/docs/groovy-language.adoc[Groovy] (camel-groovy)
| 1.3 | To use Groovy scripts in Camel expressions or predicates.
-
| link:../core/camel-core/src/main/docs/header-language.adoc[Header]
(camel-core) | 1.5 | To use a Camel Message header in expressions or predicates.
-| link:camel-hl7/src/main/docs/hl7terser-language.adoc[HL7 Terser] (camel-hl7)
| 2.11 | To use HL7 terser scripts in Camel expressions or predicates.
-
-| link:camel-script/src/main/docs/javaScript-language.adoc[JavaScript]
(camel-script) | 1.0 | *deprecated* To use JavaScript in Camel expressions or
predicates.
-
| link:camel-jsonpath/src/main/docs/jsonpath-language.adoc[JsonPath]
(camel-jsonpath) | 2.13 | To use JsonPath in Camel expressions or predicates.
-| link:camel-mvel/src/main/docs/mvel-language.adoc[MVEL] (camel-mvel) | 2.0 |
To use MVEL scripts in Camel expressions or predicates.
-
-| link:camel-ognl/src/main/docs/ognl-language.adoc[OGNL] (camel-ognl) | 1.1 |
To use OGNL scripts in Camel expressions or predicates.
-
| link:../core/camel-core/src/main/docs/ref-language.adoc[Ref] (camel-core) |
2.8 | Reference to an existing Camel expression or predicate, which is looked
up from the Camel registry.
| link:../core/camel-core/src/main/docs/simple-language.adoc[Simple]
(camel-core) | 1.1 | To use Camels built-in Simple language in Camel
expressions or predicates.
@@ -1025,8 +150,6 @@ Number of Languages: 18 in 9 JAR artifacts (1 deprecated)
| link:../core/camel-core/src/main/docs/xtokenize-language.adoc[XML Tokenize]
(camel-core) | 2.14 | To use Camel message body or header with a XML tokenizer
in Camel expressions or predicates.
| link:../core/camel-core/src/main/docs/xpath-language.adoc[XPath]
(camel-core) | 1.1 | To use XPath (XML) in Camel expressions or predicates.
-
-| link:camel-saxon/src/main/docs/xquery-language.adoc[XQuery] (camel-saxon) |
1.0 | To use XQuery (XML) in Camel expressions or predicates.
|===
// languages: END
@@ -1034,73 +157,15 @@ Number of Languages: 18 in 9 JAR artifacts (1 deprecated)
==== Miscellaneous Components
// others: START
-Number of Miscellaneous Components: 31 in 31 JAR artifacts (0 deprecated)
+Number of Miscellaneous Components: 2 in 2 JAR artifacts (0 deprecated)
[width="100%",cols="4,1,5",options="header"]
|===
| Component | Available From | Description
-| link:camel-blueprint/src/main/docs/blueprint.adoc[Blueprint]
(camel-blueprint) | 2.4 | Using Camel with OSGi Blueprint
-
-| link:camel-cdi/src/main/docs/cdi.adoc[CDI] (camel-cdi) | 2.10 | Using Camel
with CDI
-
-| link:camel-cxf-transport/src/main/docs/cxf-transport.adoc[CXF Transport]
(camel-cxf-transport) | 2.8 | Camel Transport for Apache CXF
-
-| link:camel-headersmap/src/main/docs/headersmap.adoc[Headersmap]
(camel-headersmap) | 2.20 | Fast case-insensitive headers map implementation
-
-| link:camel-hystrix/src/main/docs/hystrix.adoc[Hystrix] (camel-hystrix) |
2.18 | Circuit Breaker EIP using Netflix Hystrix
-
-| link:camel-jasypt/src/main/docs/jasypt.adoc[Jasypt] (camel-jasypt) | 2.5 |
Security using Jasypt
-
-| link:camel-kura/src/main/docs/kura.adoc[Kura] (camel-kura) | 2.15 | Using
Camel with Eclipse Kura (OSGi)
-
-| link:camel-leveldb/src/main/docs/leveldb.adoc[LevelDB] (camel-leveldb) |
2.10 | Using LevelDB as persistent EIP store
-
-| link:camel-lra/src/main/docs/lra.adoc[Lra] (camel-lra) | 2.21 | Camel saga
binding for Long-Running-Action framework
-
-| link:camel-opentracing/src/main/docs/opentracing.adoc[OpenTracing]
(camel-opentracing) | 2.19 | Distributed tracing using OpenTracing
-
-| link:camel-reactor/src/main/docs/reactor.adoc[Reactor] (camel-reactor) |
2.20 | Reactor based back-end for Camel's reactive streams component
-
-| link:camel-ribbon/src/main/docs/ribbon.adoc[Ribbon] (camel-ribbon) | 2.18 |
Using Netflix Ribbon for client side load balancing
-
-| link:camel-rxjava2/src/main/docs/rxjava2.adoc[Rxjava2] (camel-rxjava2) |
2.22 | RxJava2 based back-end for Camel's reactive streams component
-
-| link:camel-shiro/src/main/docs/shiro.adoc[Shiro] (camel-shiro) | 2.5 |
Security using Shiro
-
-| link:camel-spring-boot/src/main/docs/spring-boot.adoc[Spring Boot]
(camel-spring-boot) | 2.15 | Using Camel with Spring Boot
-
-| link:camel-spring-cloud/src/main/docs/spring-cloud.adoc[Spring Cloud]
(camel-spring-cloud) | 2.19 | Camel Cloud integration with Spring Cloud
-
-| link:camel-spring-cloud-consul/src/main/docs/spring-cloud-consul.adoc[Spring
Cloud Consul] (camel-spring-cloud-consul) | 2.19 | Camel Cloud integration with
Spring Cloud Consul
-
-|
link:camel-spring-cloud-netflix/src/main/docs/spring-cloud-netflix.adoc[Spring
Cloud Netflix] (camel-spring-cloud-netflix) | 2.19 | Camel Cloud integration
with Spring Cloud Netflix
-
-|
link:camel-spring-cloud-zookeeper/src/main/docs/spring-cloud-zookeeper.adoc[Spring
Cloud Zookeeper] (camel-spring-cloud-zookeeper) | 2.19 | Camel Cloud
integration with Spring Cloud Zookeeper
-
-| link:camel-spring-javaconfig/src/main/docs/spring-javaconfig.adoc[Spring
Java Configuration] (camel-spring-javaconfig) | 2.0 | Using Camel with Spring
Java Configuration
-
-| link:camel-spring-security/src/main/docs/spring-security.adoc[Spring
Security] (camel-spring-security) | 2.3 | Security using Spring Security
-
-| link:camel-swagger-java/src/main/docs/swagger-java.adoc[Swagger Java]
(camel-swagger-java) | 2.16 | Rest-dsl support for using swagger api-doc
-
| link:camel-test/src/main/docs/test.adoc[Test] (camel-test) | 2.9 | Camel
unit testing
-| link:camel-test-blueprint/src/main/docs/test-blueprint.adoc[Test Blueprint]
(camel-test-blueprint) | 2.10 | Camel unit testing with OSGi Blueprint
-
-| link:camel-test-cdi/src/main/docs/test-cdi.adoc[Test CDI] (camel-test-cdi) |
2.17 | Camel unit testing with CDI
-
-| link:camel-test-karaf/src/main/docs/test-karaf.adoc[Test Karaf]
(camel-test-karaf) | 2.18 | Camel integration testing with Apache Karaf
-
| link:camel-test-spring/src/main/docs/test-spring.adoc[Test Spring]
(camel-test-spring) | 2.10 | Camel unit testing with Spring
-
-| link:camel-testcontainers/src/main/docs/testcontainers.adoc[Testcontainers]
(camel-testcontainers) | 2.22 | Camel support for testcontainers
-
-|
link:camel-testcontainers-spring/src/main/docs/testcontainers-spring.adoc[Testcontainers
Spring] (camel-testcontainers-spring) | 2.22 | Camel unit testing with Spring
and testcontainers
-
-| link:camel-aws-xray/src/main/docs/aws-xray.adoc[XRay] (camel-aws-xray) |
2.21 | Distributed tracing using AWS XRay
-
-| link:camel-zipkin/src/main/docs/zipkin.adoc[Zipkin] (camel-zipkin) | 2.18 |
Distributed message tracing using Zipkin
|===
// others: END
diff --git a/core/camel-core/readme.adoc b/core/camel-core/readme.adoc
index 681438a..9934525 100644
--- a/core/camel-core/readme.adoc
+++ b/core/camel-core/readme.adoc
@@ -41,7 +41,7 @@ Number of Components: 5 in 1 JAR artifacts (0 deprecated)
// dataformats: START
-Number of Data Formats: 4 in 35 JAR artifacts (0 deprecated)
+Number of Data Formats: 4 in 1 JAR artifacts (0 deprecated)
[width="100%",cols="4,1,5",options="header"]
|===
diff --git a/docs/components/modules/ROOT/nav.adoc
b/docs/components/modules/ROOT/nav.adoc
index 27fb18c..38ca6e0 100644
--- a/docs/components/modules/ROOT/nav.adoc
+++ b/docs/components/modules/ROOT/nav.adoc
@@ -137,7 +137,7 @@
* xref:headersmap.adoc[HeadersMap]
* xref:hipchat-component.adoc[Hipchat Component]
* xref:hl7-dataformat.adoc[HL7 DataFormat]
-* xref:terser-language.adoc[HL7 Terser Language]
+* xref:hl7terser-language.adoc[HL7 Terser Language]
* xref:http4-component.adoc[HTTP4 Component]
* xref:hystrix.adoc[Hystrix Component]
* xref:ical-dataformat.adoc[iCal DataFormat]
diff --git a/docs/components/modules/ROOT/pages/aws-lambda-component.adoc
b/docs/components/modules/ROOT/pages/aws-lambda-component.adoc
index c596986..c039cbe 100644
--- a/docs/components/modules/ROOT/pages/aws-lambda-component.adoc
+++ b/docs/components/modules/ROOT/pages/aws-lambda-component.adoc
@@ -193,6 +193,9 @@ The default is 3 seconds.|No
- createEventSourceMapping
- deleteEventSourceMapping
- listEventSourceMapping
+- listTags
+- tagResource
+- untagResource
### Example
diff --git a/docs/components/modules/ROOT/pages/hl7-dataformat.adoc
b/docs/components/modules/ROOT/pages/hl7-dataformat.adoc
index d676a43..4c8e20b 100644
--- a/docs/components/modules/ROOT/pages/hl7-dataformat.adoc
+++ b/docs/components/modules/ROOT/pages/hl7-dataformat.adoc
@@ -228,7 +228,7 @@ The HL7 dataformat supports 2 options, which are listed
below.
=== Spring Boot Auto-Configuration
-The component supports 5 options, which are listed below.
+The component supports 3 options, which are listed below.
@@ -238,11 +238,9 @@ The component supports 5 options, which are listed below.
| *camel.dataformat.hl7.content-type-header* | Whether the data format should
set the Content-Type header with the type from the data format if the data
format is capable of doing so. For example application/xml for data formats
marshalling to XML, or application/json for data formats marshalling to JSon
etc. | false | Boolean
| *camel.dataformat.hl7.enabled* | Enable hl7 dataformat | true | Boolean
| *camel.dataformat.hl7.validate* | Whether to validate the HL7 message Is by
default true. | true | Boolean
-| *camel.language.terser.enabled* | Enable terser language | true | Boolean
-| *camel.language.terser.trim* | Whether to trim the value to remove leading
and trailing whitespaces and line breaks | true | Boolean
|===
// spring-boot-auto-configure options: END
-ND
+
* `marshal` = from Message to byte stream (can be used when responding
using the HL7 MLLP codec)
@@ -360,30 +358,6 @@ that was used to parse the message
All headers except `CamelHL7Context `are `String` types. If a header
value is missing, its value is `null`.
-=== Options
-
-The HL7 Data Format supports the following options:
-
-[width="100%",cols="10%,10%,80%",options="header",]
-|===
-|Option |Default |Description
-
-|`validate` |true |Whether the HAPI Parser should validate the message using
the default
-validation rules. It is recommended to use the `parser` or `hapiContext`
-option and initialize it with the desired HAPI
-http://hl7api.sourceforge.net/base/apidocs/ca/uhn/hl7v2/validation/ValidationContext.html[`ValidationContext`]
-
-|`parser` |`ca.uhn.hl7v2.parser.GenericParser` |Custom parser to be used. Must
be of type
-http://hl7api.sourceforge.net/base/apidocs/ca/uhn/hl7v2/parser/Parser.html[`ca.uhn.hl7v2.parser.Parser`].
-Note that
-http://hl7api.sourceforge.net/base/apidocs/ca/uhn/hl7v2/parser/GenericParser.html[`GenericParser`]
-also allows to parse XML-encoded HL7v2 messages
-
-|`hapiContext` |`ca.uhn.hl7v2.DefaultHapiContext` |*Camel 2.14:* Custom HAPI
context that can define a custom parser,
-custom ValidationContext etc. This gives you full control over the HL7
-parsing and rendering process.
-|===
-
=== Dependencies
To use HL7 in your Camel routes you'll need to add a dependency on
@@ -447,134 +421,3 @@ repository].
</dependency>
----
-=== Terser language
-
-http://hl7api.sourceforge.net[HAPI] provides a
-http://hl7api.sourceforge.net/base/apidocs/ca/uhn/hl7v2/util/Terser.html[Terser]
-class that provides access to fields using a commonly used terse
-location specification syntax. The Terser language allows to use this
-syntax to extract values from messages and to use them as expressions
-and predicates for filtering, content-based routing etc.
-
-Sample:
-
-[source,java]
-----
-import static org.apache.camel.component.hl7.HL7.terser;
-
- // extract patient ID from field QRD-8 in the QRY_A19 message above and put
into message header
- from("direct:test1")
- .setHeader("PATIENT_ID",terser("QRD-8(0)-1"))
- .to("mock:test1");
-
- // continue processing if extracted field equals a message header
- from("direct:test2")
- .filter(terser("QRD-8(0)-1").isEqualTo(header("PATIENT_ID"))
- .to("mock:test2");
-----
-
-=== HL7 Validation predicate
-
-Often it is preferable to first parse a HL7v2 message and in a separate
-step validate it against a HAPI
-http://hl7api.sourceforge.net/base/apidocs/ca/uhn/hl7v2/validation/ValidationContext.html[ValidationContext].
-
-Sample:
-
-[source,java]
-----
-import static org.apache.camel.component.hl7.HL7.messageConformsTo;
-import ca.uhn.hl7v2.validation.impl.DefaultValidation;
-
- // Use standard or define your own validation rules
- ValidationContext defaultContext = new DefaultValidation();
-
- // Throws PredicateValidationException if message does not validate
- from("direct:test1")
- .validate(messageConformsTo(defaultContext))
- .to("mock:test1");
-----
-
-=== HL7 Validation predicate using the HapiContext (Camel 2.14)
-
-The HAPI Context is always configured with a
-http://hl7api.sourceforge.net/base/apidocs/ca/uhn/hl7v2/validation/ValidationContext.html[ValidationContext]
-(or a
-http://hl7api.sourceforge.net/base/apidocs/ca/uhn/hl7v2/validation/builder/ValidationRuleBuilder.html[ValidationRuleBuilder]),
-so you can access the validation rules indirectly. Furthermore, when
-unmarshalling the HL7DataFormat forwards the configured HAPI context in
-the `CamelHL7Context` header, and the validation rules of this context
-can be easily reused:
-
-[source,java]
-----
-import static org.apache.camel.component.hl7.HL7.messageConformsTo;
-import static org.apache.camel.component.hl7.HL7.messageConforms
-
- HapiContext hapiContext = new DefaultHapiContext();
- hapiContext.getParserConfiguration().setValidating(false); // don't validate
during parsing
-
- // customize HapiContext some more ... e.g. enforce that PID-8 in ADT_A01
messages of version 2.4 is not empty
- ValidationRuleBuilder builder = new ValidationRuleBuilder() {
- @Override
- protected void configure() {
- forVersion(Version.V24)
- .message("ADT", "A01")
- .terser("PID-8", not(empty()));
- }
- };
- hapiContext.setValidationRuleBuilder(builder);
-
- HL7DataFormat hl7 = new HL7DataFormat();
- hl7.setHapiContext(hapiContext);
-
- from("direct:test1")
- .unmarshal(hl7) // uses the GenericParser returned from
the HapiContext
- .validate(messageConforms()) // uses the validation rules returned from
the HapiContext
- // equivalent with
.validate(messageConformsTo(hapiContext))
- // route continues from here
-----
-
-=== HL7 Acknowledgement expression
-
-A common task in HL7v2 processing is to generate an acknowledgement
-message as response to an incoming HL7v2 message, e.g. based on a
-validation result. The `ack` expression lets us accomplish this very
-elegantly:
-
-[source,java]
-----
-import static org.apache.camel.component.hl7.HL7.messageConformsTo;
-import static org.apache.camel.component.hl7.HL7.ack;
-import ca.uhn.hl7v2.validation.impl.DefaultValidation;
-
- // Use standard or define your own validation rules
- ValidationContext defaultContext = new DefaultValidation();
-
- from("direct:test1")
- .onException(Exception.class)
- .handled(true)
- .transform(ack()) // auto-generates negative ack because of exception
in Exchange
- .end()
- .validate(messageConformsTo(defaultContext))
- // do something meaningful here
-
- // acknowledgement
- .transform(ack())
-----
-
-=== More Samples
-
-In the following example, a plain `String` HL7 request is sent to an HL7
-listener that sends back a response:
-
-In the next sample, HL7 requests from the HL7 listener are routed to the
-business logic, which is implemented as plain POJO registered in the
-registry as `hl7service`.
-
-Then the Camel routes using the `RouteBuilder` may look as follows:
-
-Note that by using the HL7 DataFormat the Camel message headers are
-populated with the fields from the MSH segment. The headers are
-particularly useful for filtering or content-based routing as shown in
-the example above.
diff --git a/docs/components/modules/ROOT/pages/hl7terser-language.adoc
b/docs/components/modules/ROOT/pages/hl7terser-language.adoc
new file mode 100644
index 0000000..69a237c
--- /dev/null
+++ b/docs/components/modules/ROOT/pages/hl7terser-language.adoc
@@ -0,0 +1,135 @@
+[[hl7terser-language]]
+== HL7 Terser Language
+*Available as of Camel version 2.11*
+*Available as of Camel version 2.11*
+
+
+
+http://hl7api.sourceforge.net[HAPI] provides a
+http://hl7api.sourceforge.net/base/apidocs/ca/uhn/hl7v2/util/Terser.html[Terser]
+class that provides access to fields using a commonly used terse
+location specification syntax. The Terser language allows to use this
+syntax to extract values from messages and to use them as expressions
+and predicates for filtering, content-based routing etc.
+
+=== HL7 Terser Language options
+
+// language options: START
+The HL7 Terser language supports 1 options, which are listed below.
+
+
+
+[width="100%",cols="2,1m,1m,6",options="header"]
+|===
+| Name | Default | Java Type | Description
+| trim | true | Boolean | Whether to trim the value to remove leading and
trailing whitespaces and line breaks
+|===
+// language options: END
+
+
+== Samples:
+
+[source,java]
+----
+ import static org.apache.camel.component.hl7.HL7.hl7terser;
+
+ // extract patient ID from field QRD-8 in the QRY_A19 message above and put
into message header
+ from("direct:test1")
+ .setHeader("PATIENT_ID", hl7terser("QRD-8(0)-1"))
+ .to("mock:test1");
+
+ // continue processing if extracted field equals a message header
+ from("direct:test2")
+ .filter(hl7terser("QRD-8(0)-1").isEqualTo(header("PATIENT_ID"))
+ .to("mock:test2");
+----
+
+=== HL7 Validation predicate
+
+Often it is preferable to first parse a HL7v2 message and in a separate
+step validate it against a HAPI
+http://hl7api.sourceforge.net/base/apidocs/ca/uhn/hl7v2/validation/ValidationContext.html[ValidationContext].
+
+Sample:
+
+[source,java]
+----
+import static org.apache.camel.component.hl7.HL7.messageConformsTo;
+import ca.uhn.hl7v2.validation.impl.DefaultValidation;
+
+ // Use standard or define your own validation rules
+ ValidationContext defaultContext = new DefaultValidation();
+
+ // Throws PredicateValidationException if message does not validate
+ from("direct:test1")
+ .validate(messageConformsTo(defaultContext))
+ .to("mock:test1");
+----
+
+=== HL7 Validation predicate using the HapiContext (Camel 2.14)
+
+The HAPI Context is always configured with a
+http://hl7api.sourceforge.net/base/apidocs/ca/uhn/hl7v2/validation/ValidationContext.html[ValidationContext]
+(or a
+http://hl7api.sourceforge.net/base/apidocs/ca/uhn/hl7v2/validation/builder/ValidationRuleBuilder.html[ValidationRuleBuilder]),
+so you can access the validation rules indirectly. Furthermore, when
+unmarshalling the HL7DataFormat forwards the configured HAPI context in
+the `CamelHL7Context` header, and the validation rules of this context
+can be easily reused:
+
+[source,java]
+----
+import static org.apache.camel.component.hl7.HL7.messageConformsTo;
+import static org.apache.camel.component.hl7.HL7.messageConforms
+
+ HapiContext hapiContext = new DefaultHapiContext();
+ hapiContext.getParserConfiguration().setValidating(false); // don't validate
during parsing
+
+ // customize HapiContext some more ... e.g. enforce that PID-8 in ADT_A01
messages of version 2.4 is not empty
+ ValidationRuleBuilder builder = new ValidationRuleBuilder() {
+ @Override
+ protected void configure() {
+ forVersion(Version.V24)
+ .message("ADT", "A01")
+ .terser("PID-8", not(empty()));
+ }
+ };
+ hapiContext.setValidationRuleBuilder(builder);
+
+ HL7DataFormat hl7 = new HL7DataFormat();
+ hl7.setHapiContext(hapiContext);
+
+ from("direct:test1")
+ .unmarshal(hl7) // uses the GenericParser returned from
the HapiContext
+ .validate(messageConforms()) // uses the validation rules returned from
the HapiContext
+ // equivalent with
.validate(messageConformsTo(hapiContext))
+ // route continues from here
+----
+
+=== HL7 Acknowledgement expression
+
+A common task in HL7v2 processing is to generate an acknowledgement
+message as response to an incoming HL7v2 message, e.g. based on a
+validation result. The `ack` expression lets us accomplish this very
+elegantly:
+
+[source,java]
+----
+import static org.apache.camel.component.hl7.HL7.messageConformsTo;
+import static org.apache.camel.component.hl7.HL7.ack;
+import ca.uhn.hl7v2.validation.impl.DefaultValidation;
+
+ // Use standard or define your own validation rules
+ ValidationContext defaultContext = new DefaultValidation();
+
+ from("direct:test1")
+ .onException(Exception.class)
+ .handled(true)
+ .transform(ack()) // auto-generates negative ack because of exception
in Exchange
+ .end()
+ .validate(messageConformsTo(defaultContext))
+ // do something meaningful here
+
+ // acknowledgement
+ .transform(ack())
+----
\ No newline at end of file
diff --git a/docs/components/modules/ROOT/pages/rest-swagger-component.adoc
b/docs/components/modules/ROOT/pages/rest-swagger-component.adoc
index a467a3b..f8b30b6 100644
--- a/docs/components/modules/ROOT/pages/rest-swagger-component.adoc
+++ b/docs/components/modules/ROOT/pages/rest-swagger-component.adoc
@@ -92,11 +92,11 @@ The REST Swagger component supports 9 options, which are
listed below.
|===
| Name | Description | Default | Type
| *basePath* (producer) | API basePath, for example /v2. Default is unset, if
set overrides the value present in Swagger specification. | | String
-| *componentName* (producer) | Name of the Camel component that will perform
the requests. The compnent must be present in Camel registry and it must
implement RestProducerFactory service provider interface. If not set CLASSPATH
is searched for single component that implements RestProducerFactory SPI. Can
be overriden in endpoint configuration. | | String
-| *consumes* (producer) | What payload type this component capable of
consuming. Could be one type, like application/json or multiple types as
application/json, application/xml; q=0.5 according to the RFC7231. This equates
to the value of Accept HTTP header. If set overrides any value found in the
Swagger specification. Can be overriden in endpoint configuration | | String
-| *host* (producer) | Scheme hostname and port to direct the HTTP requests to
in the form of https://hostname:port. Can be configured at the endpoint,
component or in the correspoding REST configuration in the Camel Context. If
you give this component a name (e.g. petstore) that REST configuration is
consulted first, rest-swagger next, and global configuration last. If set
overrides any value found in the Swagger specification, RestConfiguration. Can
be overriden in endpoint configuratio [...]
-| *produces* (producer) | What payload type this component is producing. For
example application/json according to the RFC7231. This equates to the value of
Content-Type HTTP header. If set overrides any value present in the Swagger
specification. Can be overriden in endpoint configuration. | | String
-| *specificationUri* (producer) | Path to the Swagger specification file. The
scheme, host base path are taken from this specification, but these can be
overriden with properties on the component or endpoint level. If not given the
component tries to load swagger.json resource. Note that the host defined on
the component and endpoint of this Component should contain the scheme,
hostname and optionally the port in the URI syntax (i.e.
https://api.example.com:8080). Can be overriden in end [...]
+| *componentName* (producer) | Name of the Camel component that will perform
the requests. The component must be present in Camel registry and it must
implement RestProducerFactory service provider interface. If not set CLASSPATH
is searched for single component that implements RestProducerFactory SPI. Can
be overridden in endpoint configuration. | | String
+| *consumes* (producer) | What payload type this component capable of
consuming. Could be one type, like application/json or multiple types as
application/json, application/xml; q=0.5 according to the RFC7231. This equates
to the value of Accept HTTP header. If set overrides any value found in the
Swagger specification. Can be overridden in endpoint configuration | | String
+| *host* (producer) | Scheme hostname and port to direct the HTTP requests to
in the form of https://hostname:port. Can be configured at the endpoint,
component or in the correspoding REST configuration in the Camel Context. If
you give this component a name (e.g. petstore) that REST configuration is
consulted first, rest-swagger next, and global configuration last. If set
overrides any value found in the Swagger specification, RestConfiguration. Can
be overridden in endpoint configurati [...]
+| *produces* (producer) | What payload type this component is producing. For
example application/json according to the RFC7231. This equates to the value of
Content-Type HTTP header. If set overrides any value present in the Swagger
specification. Can be overridden in endpoint configuration. | | String
+| *specificationUri* (producer) | Path to the Swagger specification file. The
scheme, host base path are taken from this specification, but these can be
overriden with properties on the component or endpoint level. If not given the
component tries to load swagger.json resource. Note that the host defined on
the component and endpoint of this Component should contain the scheme,
hostname and optionally the port in the URI syntax (i.e.
https://api.example.com:8080). Can be overridden in en [...]
| *sslContextParameters* (security) | Customize TLS parameters used by the
component. If not set defaults to the TLS parameters set in the Camel context |
| SSLContextParameters
| *useGlobalSslContext Parameters* (security) | Enable usage of global SSL
context parameters. | false | boolean
| *resolveProperty Placeholders* (advanced) | Whether the component should
resolve property placeholders on itself when starting. Only properties which
are of String type can use property placeholders. | true | boolean
@@ -118,7 +118,7 @@ with the following path and query parameters:
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
-| *specificationUri* | Path to the Swagger specification file. The scheme,
host base path are taken from this specification, but these can be overriden
with properties on the component or endpoint level. If not given the component
tries to load swagger.json resource. Note that the host defined on the
component and endpoint of this Component should contain the scheme, hostname
and optionally the port in the URI syntax (i.e. https://api.example.com:8080).
Overrides component configuration. [...]
+| *specificationUri* | Path to the Swagger specification file. The scheme,
host base path are taken from this specification, but these can be overridden
with properties on the component or endpoint level. If not given the component
tries to load swagger.json resource from the classpath. Note that the host
defined on the component and endpoint of this Component should contain the
scheme, hostname and optionally the port in the URI syntax (i.e.
http://api.example.com:8080). Overrides compo [...]
| *operationId* | *Required* ID of the operation from the Swagger
specification. | | String
|===
@@ -149,13 +149,13 @@ The component supports 10 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.rest-swagger.base-path* | API basePath, for example /v2.
Default is unset, if set overrides the value present in Swagger specification.
| | String
-| *camel.component.rest-swagger.component-name* | Name of the Camel component
that will perform the requests. The compnent must be present in Camel registry
and it must implement RestProducerFactory service provider interface. If not
set CLASSPATH is searched for single component that implements
RestProducerFactory SPI. Can be overriden in endpoint configuration. | | String
-| *camel.component.rest-swagger.consumes* | What payload type this component
capable of consuming. Could be one type, like application/json or multiple
types as application/json, application/xml; q=0.5 according to the RFC7231.
This equates to the value of Accept HTTP header. If set overrides any value
found in the Swagger specification. Can be overriden in endpoint configuration
| | String
+| *camel.component.rest-swagger.component-name* | Name of the Camel component
that will perform the requests. The component must be present in Camel registry
and it must implement RestProducerFactory service provider interface. If not
set CLASSPATH is searched for single component that implements
RestProducerFactory SPI. Can be overridden in endpoint configuration. | |
String
+| *camel.component.rest-swagger.consumes* | What payload type this component
capable of consuming. Could be one type, like application/json or multiple
types as application/json, application/xml; q=0.5 according to the RFC7231.
This equates to the value of Accept HTTP header. If set overrides any value
found in the Swagger specification. Can be overridden in endpoint configuration
| | String
| *camel.component.rest-swagger.enabled* | Enable rest-swagger component |
true | Boolean
-| *camel.component.rest-swagger.host* | Scheme hostname and port to direct the
HTTP requests to in the form of https://hostname:port. Can be configured at the
endpoint, component or in the correspoding REST configuration in the Camel
Context. If you give this component a name (e.g. petstore) that REST
configuration is consulted first, rest-swagger next, and global configuration
last. If set overrides any value found in the Swagger specification,
RestConfiguration. Can be overriden in end [...]
-| *camel.component.rest-swagger.produces* | What payload type this component
is producing. For example application/json according to the RFC7231. This
equates to the value of Content-Type HTTP header. If set overrides any value
present in the Swagger specification. Can be overriden in endpoint
configuration. | | String
+| *camel.component.rest-swagger.host* | Scheme hostname and port to direct the
HTTP requests to in the form of https://hostname:port. Can be configured at the
endpoint, component or in the correspoding REST configuration in the Camel
Context. If you give this component a name (e.g. petstore) that REST
configuration is consulted first, rest-swagger next, and global configuration
last. If set overrides any value found in the Swagger specification,
RestConfiguration. Can be overridden in en [...]
+| *camel.component.rest-swagger.produces* | What payload type this component
is producing. For example application/json according to the RFC7231. This
equates to the value of Content-Type HTTP header. If set overrides any value
present in the Swagger specification. Can be overridden in endpoint
configuration. | | String
| *camel.component.rest-swagger.resolve-property-placeholders* | Whether the
component should resolve property placeholders on itself when starting. Only
properties which are of String type can use property placeholders. | true |
Boolean
-| *camel.component.rest-swagger.specification-uri* | Path to the Swagger
specification file. The scheme, host base path are taken from this
specification, but these can be overriden with properties on the component or
endpoint level. If not given the component tries to load swagger.json resource.
Note that the host defined on the component and endpoint of this Component
should contain the scheme, hostname and optionally the port in the URI syntax
(i.e. https://api.example.com:8080). Can [...]
+| *camel.component.rest-swagger.specification-uri* | Path to the Swagger
specification file. The scheme, host base path are taken from this
specification, but these can be overriden with properties on the component or
endpoint level. If not given the component tries to load swagger.json resource.
Note that the host defined on the component and endpoint of this Component
should contain the scheme, hostname and optionally the port in the URI syntax
(i.e. https://api.example.com:8080). Can [...]
| *camel.component.rest-swagger.ssl-context-parameters* | Customize TLS
parameters used by the component. If not set defaults to the TLS parameters set
in the Camel context. The option is a
org.apache.camel.support.jsse.SSLContextParameters type. | | String
| *camel.component.rest-swagger.use-global-ssl-context-parameters* | Enable
usage of global SSL context parameters. | false | Boolean
|===
diff --git a/docs/components/modules/ROOT/pages/telegram-component.adoc
b/docs/components/modules/ROOT/pages/telegram-component.adoc
index bc928b0..1d9f3ba 100644
--- a/docs/components/modules/ROOT/pages/telegram-component.adoc
+++ b/docs/components/modules/ROOT/pages/telegram-component.adoc
@@ -194,6 +194,8 @@ The following message bodies are allowed for a producer
endpoint (messages of ty
| `OutgoingDocumentMessage` | To send a file to a chat (any media type)
| `SendLocationMessage` | To send a location (setSendLocation)
| `EditMessageLiveLocationMessage` | To send changes to a live location
(editMessageLiveLocation)
+| `StopMessageLiveLocationMessage` | To stop updating a live location message
sent by the bot or via the bot (for inline bots) before live_period expires
(stopMessageLiveLocation)
+| `SendVenueMessage` | To send information about a venue (sendVenue)
| `byte[]` | To send any media type supported. It requires the
`CamelTelegramMediaType` header to be set to the appropriate media type
| `String` | To send a text message to a chat. It gets converted automatically
into a `OutgoingTextMessage`
diff --git a/docs/components/modules/ROOT/pages/terser-language.adoc
b/docs/components/modules/ROOT/pages/terser-language.adoc
deleted file mode 100644
index f643635..0000000
--- a/docs/components/modules/ROOT/pages/terser-language.adoc
+++ /dev/null
@@ -1,44 +0,0 @@
-[[terser-language]]
-== HL7 Terser Language
-### Terser language
-*Available as of Camel version 2.11.0*
-
-
-http://hl7api.sourceforge.net[HAPI] provides a
-http://hl7api.sourceforge.net/base/apidocs/ca/uhn/hl7v2/util/Terser.html[Terser]
-class that provides access to fields using a commonly used terse
-location specification syntax. The Terser language allows to use this
-syntax to extract values from messages and to use them as expressions
-and predicates for filtering, content-based routing etc.
-
-Sample:
-
-[source,java]
---------------------------------------------------------------------------------------------------
-import static org.apache.camel.component.hl7.HL7.terser;
-...
-
- // extract patient ID from field QRD-8 in the QRY_A19 message above and put
into message header
- from("direct:test1")
- .setHeader("PATIENT_ID",terser("QRD-8(0)-1"))
- .to("mock:test1");
-
- // continue processing if extracted field equals a message header
- from("direct:test2")
- .filter(terser("QRD-8(0)-1").isEqualTo(header("PATIENT_ID"))
- .to("mock:test2");
---------------------------------------------------------------------------------------------------
-
-### Terser Language options
-
-// language options: START
-The HL7 Terser language supports 1 options, which are listed below.
-
-
-
-[width="100%",cols="2,1m,1m,6",options="header"]
-|===
-| Name | Default | Java Type | Description
-| trim | true | Boolean | Whether to trim the value to remove leading and
trailing whitespaces and line breaks
-|===
-// language options: END
\ No newline at end of file
diff --git
a/platforms/spring-boot/spring-boot-dm/camel-spring-boot-dependencies/pom.xml
b/platforms/spring-boot/spring-boot-dm/camel-spring-boot-dependencies/pom.xml
index db7792c..eba5f00 100644
---
a/platforms/spring-boot/spring-boot-dm/camel-spring-boot-dependencies/pom.xml
+++
b/platforms/spring-boot/spring-boot-dm/camel-spring-boot-dependencies/pom.xml
@@ -3433,7 +3433,7 @@
<dependency>
<groupId>org.knowm.xchange</groupId>
<artifactId>xchange-core</artifactId>
- <version>4.3.14</version>
+ <version>4.3.15</version>
</dependency>
<dependency>
<groupId>org.mozilla</groupId>
