You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by zr...@apache.org on 2019/07/29 17:23:19 UTC
[camel] 02/02: CAMEL-13798: re-level all .adoc files
This is an automated email from the ASF dual-hosted git repository.
zregvart pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git
commit f195e1d1b58fea3bd2cb0949e5ce942d03fed4ad
Author: Zoran Regvart <zr...@apache.org>
AuthorDate: Mon Jul 29 17:46:05 2019 +0200
CAMEL-13798: re-level all .adoc files
---
.../main/resources/archetype-resources/readme.adoc | 12 +--
.../src/main/docs/activemq-component.adoc | 14 ++--
.../src/main/docs/ahc-ws-component.adoc | 18 ++---
.../camel-ahc/src/main/docs/ahc-component.adoc | 44 +++++-----
.../camel-amqp/src/main/docs/amqp-component.adoc | 20 ++---
.../camel-apns/src/main/docs/apns-component.adoc | 30 +++----
.../src/main/docs/as2-component.adoc | 16 ++--
.../camel-asn1/src/main/docs/asn1-dataformat.adoc | 10 +--
.../src/main/docs/asterisk-component.adoc | 14 ++--
.../camel-atmos/src/main/docs/atmos-component.adoc | 18 ++---
.../main/docs/atmosphere-websocket-component.adoc | 18 ++---
.../camel-atom/src/main/docs/atom-component.adoc | 20 ++---
.../src/main/docs/atomix-map-component.adoc | 18 ++---
.../src/main/docs/atomix-messaging-component.adoc | 10 +--
.../src/main/docs/atomix-multimap-component.adoc | 10 +--
.../src/main/docs/atomix-queue-component.adoc | 10 +--
.../src/main/docs/atomix-set-component.adoc | 10 +--
.../src/main/docs/atomix-value-component.adoc | 10 +--
.../camel-avro/src/main/docs/avro-component.adoc | 20 ++---
.../camel-avro/src/main/docs/avro-dataformat.adoc | 10 +--
.../src/main/docs/aws-cw-component.adoc | 24 +++---
.../src/main/docs/aws-ddb-component.adoc | 42 +++++-----
.../src/main/docs/aws-ddbstream-component.adoc | 34 ++++----
.../src/main/docs/aws-ec2-component.adoc | 20 ++---
.../src/main/docs/aws-ecs-component.adoc | 22 ++---
.../src/main/docs/aws-eks-component.adoc | 22 ++---
.../src/main/docs/aws-iam-component.adoc | 22 ++---
.../src/main/docs/aws-kinesis-component.adoc | 32 ++++----
.../main/docs/aws-kinesis-firehose-component.adoc | 26 +++---
.../src/main/docs/aws-kms-component.adoc | 22 ++---
.../src/main/docs/aws-lambda-component.adoc | 26 +++---
.../src/main/docs/aws-mq-component.adoc | 20 ++---
.../src/main/docs/aws-msk-component.adoc | 22 ++---
.../src/main/docs/aws-s3-component.adoc | 40 ++++-----
.../src/main/docs/aws-sdb-component.adoc | 30 +++----
.../src/main/docs/aws-ses-component.adoc | 26 +++---
.../src/main/docs/aws-sns-component.adoc | 30 +++----
.../src/main/docs/aws-sqs-component.adoc | 48 +++++------
.../src/main/docs/aws-swf-component.adoc | 32 ++++----
.../camel-aws-xray/src/main/docs/aws-xray.adoc | 12 +--
.../src/main/docs/azure-blob-component.adoc | 26 +++---
.../src/main/docs/azure-queue-component.adoc | 22 ++---
components/camel-azure/src/main/docs/azure.adoc | 2 +-
.../src/main/docs/barcode-dataformat.adoc | 14 ++--
.../src/main/docs/base64-dataformat.adoc | 12 +--
.../src/main/docs/bean-validator-component.adoc | 18 ++---
.../camel-bean/src/main/docs/bean-component.adoc | 18 ++---
.../camel-bean/src/main/docs/bean-language.adoc | 14 ++--
.../camel-bean/src/main/docs/class-component.adoc | 16 ++--
.../src/main/docs/beanio-dataformat.adoc | 14 ++--
.../src/main/docs/beanstalk-component.adoc | 20 ++---
.../src/main/docs/bindy-dataformat.adoc | 44 +++++-----
.../camel-blueprint/src/main/docs/blueprint.adoc | 6 +-
.../src/main/docs/bonita-component.adoc | 18 ++---
.../camel-boon/src/main/docs/boon-dataformat.adoc | 12 +--
.../src/main/docs/box-component.adoc | 48 +++++------
.../src/main/docs/braintree-component.adoc | 60 +++++++-------
.../src/main/docs/browse-component.adoc | 16 ++--
.../src/main/docs/caffeine-cache-component.adoc | 16 ++--
.../main/docs/caffeine-loadcache-component.adoc | 12 +--
.../src/main/docs/cql-component.adoc | 26 +++---
.../camel-cbor/src/main/docs/cbor-dataformat.adoc | 10 +--
components/camel-cdi/src/main/docs/cdi.adoc | 40 ++++-----
.../src/main/docs/chatscript-component.adoc | 12 +--
.../camel-chunk/src/main/docs/chunk-component.adoc | 22 ++---
.../src/main/docs/cm-sms-component.adoc | 12 +--
.../camel-cmis/src/main/docs/cmis-component.adoc | 22 ++---
.../camel-coap/src/main/docs/coap-component.adoc | 14 ++--
.../src/main/docs/cometd-component.adoc | 22 ++---
.../src/main/docs/consul-component.adoc | 14 ++--
.../src/main/docs/controlbus-component.adoc | 18 ++---
.../camel-corda/src/main/docs/corda-component.adoc | 16 ++--
.../src/main/docs/couchbase-component.adoc | 14 ++--
.../src/main/docs/couchdb-component.adoc | 18 ++---
.../src/main/docs/crypto-cms-component.adoc | 14 ++--
.../src/main/docs/crypto-component.adoc | 30 +++----
.../src/main/docs/crypto-dataformat.adoc | 20 ++---
.../camel-crypto/src/main/docs/pgp-dataformat.adoc | 26 +++---
.../camel-csv/src/main/docs/csv-dataformat.adoc | 24 +++---
.../src/main/docs/cxf-transport.adoc | 20 ++---
.../camel-cxf/src/main/docs/cxf-component.adoc | 54 ++++++-------
.../camel-cxf/src/main/docs/cxfrs-component.adoc | 28 +++----
.../src/main/docs/dataformat-component.adoc | 14 ++--
.../src/main/docs/dataset-component.adoc | 32 ++++----
.../src/main/docs/dataset-test-component.adoc | 16 ++--
.../src/main/docs/digitalocean-component.adoc | 40 ++++-----
.../src/main/docs/direct-component.adoc | 16 ++--
.../src/main/docs/direct-vm-component.adoc | 14 ++--
.../src/main/docs/disruptor-component.adoc | 26 +++---
.../camel-dns/src/main/docs/dns-component.adoc | 24 +++---
.../src/main/docs/docker-component.adoc | 18 ++---
.../camel-dozer/src/main/docs/dozer-component.adoc | 24 +++---
.../camel-drill/src/main/docs/drill-component.adoc | 16 ++--
.../src/main/docs/dropbox-component.adoc | 54 ++++++-------
.../src/main/docs/ehcache-component.adoc | 18 ++---
.../camel-ejb/src/main/docs/ejb-component.adoc | 20 ++---
.../main/docs/elasticsearch-rest-component.adoc | 22 ++---
.../camel-elsql/src/main/docs/elsql-component.adoc | 20 ++---
.../camel-etcd/src/main/docs/etcd-component.adoc | 12 +--
.../src/main/docs/eventadmin-component.adoc | 18 ++---
.../camel-exec/src/main/docs/exec-component.adoc | 30 +++----
.../src/main/docs/facebook-component.adoc | 24 +++---
.../src/main/docs/json-fastjson-dataformat.adoc | 8 +-
.../src/main/docs/fhir-component.adoc | 10 +--
.../src/main/docs/fhirJson-dataformat.adoc | 6 +-
.../src/main/docs/fhirXml-dataformat.adoc | 6 +-
.../src/main/docs/file-watch-component.adoc | 22 ++---
.../camel-file/src/main/docs/file-component.adoc | 84 +++++++++----------
.../src/main/docs/flatpack-component.adoc | 32 ++++----
.../src/main/docs/flatpack-dataformat.adoc | 10 +--
.../camel-flink/src/main/docs/flink-component.adoc | 20 ++---
.../camel-fop/src/main/docs/fop-component.adoc | 20 ++---
.../src/main/docs/freemarker-component.adoc | 26 +++---
.../camel-ftp/src/main/docs/ftp-component.adoc | 60 +++++++-------
.../camel-ftp/src/main/docs/ftps-component.adoc | 10 +--
.../camel-ftp/src/main/docs/sftp-component.adoc | 8 +-
.../src/main/docs/ganglia-component.adoc | 22 ++---
.../src/main/docs/geocoder-component.adoc | 18 ++---
.../camel-git/src/main/docs/git-component.adoc | 16 ++--
.../src/main/docs/github-component.adoc | 16 ++--
.../src/main/docs/google-bigquery-component.adoc | 24 +++---
.../main/docs/google-bigquery-sql-component.adoc | 18 ++---
.../src/main/docs/google-calendar-component.adoc | 20 ++---
.../docs/google-calendar-stream-component.adoc | 14 ++--
.../src/main/docs/google-drive-component.adoc | 20 ++---
.../src/main/docs/google-mail-component.adoc | 20 ++---
.../main/docs/google-mail-stream-component.adoc | 14 ++--
.../src/main/docs/google-pubsub-component.adoc | 24 +++---
.../src/main/docs/google-sheets-component.adoc | 20 ++---
.../main/docs/google-sheets-stream-component.adoc | 14 ++--
.../camel-gora/src/main/docs/gora-component.adoc | 24 +++---
.../camel-grape/src/main/docs/grape-component.adoc | 28 +++----
.../camel-grok/src/main/docs/grok-dataformat.adoc | 12 +--
.../src/main/docs/groovy-language.adoc | 22 ++---
.../camel-grpc/src/main/docs/grpc-component.adoc | 26 +++---
.../src/main/docs/json-gson-dataformat.adoc | 8 +-
.../src/main/docs/guava-eventbus-component.adoc | 18 ++---
.../main/docs/hazelcast-atomicvalue-component.adoc | 22 ++---
.../main/docs/hazelcast-instance-component.adoc | 12 +--
.../src/main/docs/hazelcast-list-component.adoc | 22 ++---
.../src/main/docs/hazelcast-map-component.adoc | 24 +++---
.../main/docs/hazelcast-multimap-component.adoc | 22 ++---
.../src/main/docs/hazelcast-queue-component.adoc | 38 ++++-----
.../docs/hazelcast-replicatedmap-component.adoc | 20 ++---
.../main/docs/hazelcast-ringbuffer-component.adoc | 16 ++--
.../src/main/docs/hazelcast-seda-component.adoc | 14 ++--
.../src/main/docs/hazelcast-set-component.adoc | 10 +--
.../src/main/docs/hazelcast-topic-component.adoc | 16 ++--
.../camel-hazelcast/src/main/docs/hazelcast.adoc | 16 ++--
.../camel-hbase/src/main/docs/hbase-component.adoc | 38 ++++-----
.../camel-hdfs2/src/main/docs/hdfs2-component.adoc | 28 +++----
.../src/main/docs/hipchat-component.adoc | 26 +++---
.../camel-hl7/src/main/docs/hl7-dataformat.adoc | 26 +++---
.../src/main/docs/hl7terser-language.adoc | 10 +--
.../camel-http4/src/main/docs/http4-component.adoc | 54 ++++++-------
.../camel-hystrix/src/main/docs/hystrix.adoc | 4 +-
.../camel-ical/src/main/docs/ical-dataformat.adoc | 10 +--
.../src/main/docs/iec60870-client-component.adoc | 12 +--
.../src/main/docs/iec60870-server-component.adoc | 12 +--
.../src/main/docs/ignite-cache-component.adoc | 12 +--
.../src/main/docs/ignite-compute-component.adoc | 14 ++--
.../src/main/docs/ignite-events-component.adoc | 10 +--
.../src/main/docs/ignite-idgen-component.adoc | 10 +--
.../src/main/docs/ignite-messaging-component.adoc | 12 +--
.../src/main/docs/ignite-queue-component.adoc | 12 +--
.../src/main/docs/ignite-set-component.adoc | 12 +--
components/camel-ignite/src/main/docs/ignite.adoc | 14 ++--
.../src/main/docs/infinispan-component.adoc | 22 ++---
.../src/main/docs/influxdb-component.adoc | 16 ++--
.../camel-iota/src/main/docs/iota-component.adoc | 16 ++--
.../camel-ipfs/src/main/docs/ipfs-component.adoc | 18 ++---
.../camel-irc/src/main/docs/irc-component.adoc | 24 +++---
.../src/main/docs/ironmq-component.adoc | 24 +++---
.../src/main/docs/json-jackson-dataformat.adoc | 10 +--
.../src/main/docs/jacksonxml-dataformat.adoc | 28 +++----
components/camel-jasypt/src/main/docs/jasypt.adoc | 16 ++--
.../camel-jaxb/src/main/docs/jaxb-dataformat.adoc | 30 +++----
.../camel-jbpm/src/main/docs/jbpm-component.adoc | 32 ++++----
.../src/main/docs/jcache-component.adoc | 36 ++++-----
.../src/main/docs/jclouds-component.adoc | 34 ++++----
.../camel-jcr/src/main/docs/jcr-component.adoc | 18 ++---
.../camel-jdbc/src/main/docs/jdbc-component.adoc | 26 +++---
.../camel-jetty/src/main/docs/jetty-component.adoc | 42 +++++-----
.../src/main/docs/jgroups-raft-component.adoc | 22 ++---
.../src/main/docs/jgroups-component.adoc | 28 +++----
.../camel-jing/src/main/docs/jing-component.adoc | 16 ++--
.../camel-jira/src/main/docs/jira-component.adoc | 38 ++++-----
.../camel-jms/src/main/docs/jms-component.adoc | 94 +++++++++++-----------
.../camel-jmx/src/main/docs/jmx-component.adoc | 12 +--
.../src/main/docs/json-johnzon-dataformat.adoc | 8 +-
.../camel-jolt/src/main/docs/jolt-component.adoc | 16 ++--
.../camel-jooq/src/main/docs/jooq-component.adoc | 18 ++---
.../camel-jpa/src/main/docs/jpa-component.adoc | 40 ++++-----
.../camel-jsch/src/main/docs/scp-component.adoc | 16 ++--
.../src/main/docs/json-validator-component.adoc | 14 ++--
.../src/main/docs/jsonApi-dataformat.adoc | 6 +-
.../src/main/docs/jsonpath-language.adoc | 28 +++----
.../camel-jt400/src/main/docs/jt400-component.adoc | 28 +++----
.../camel-kafka/src/main/docs/kafka-component.adoc | 32 ++++----
.../docs/kubernetes-config-maps-component.adoc | 12 +--
.../docs/kubernetes-deployments-component.adoc | 12 +--
.../src/main/docs/kubernetes-hpa-component.adoc | 12 +--
.../src/main/docs/kubernetes-job-component.adoc | 12 +--
.../main/docs/kubernetes-namespaces-component.adoc | 12 +--
.../src/main/docs/kubernetes-nodes-component.adoc | 12 +--
...rnetes-persistent-volumes-claims-component.adoc | 12 +--
.../kubernetes-persistent-volumes-component.adoc | 12 +--
.../src/main/docs/kubernetes-pods-component.adoc | 12 +--
...bernetes-replication-controllers-component.adoc | 12 +--
.../docs/kubernetes-resources-quota-component.adoc | 12 +--
.../main/docs/kubernetes-secrets-component.adoc | 12 +--
.../kubernetes-service-accounts-component.adoc | 12 +--
.../main/docs/kubernetes-services-component.adoc | 12 +--
.../camel-kubernetes/src/main/docs/kubernetes.adoc | 12 +--
.../docs/openshift-build-configs-component.adoc | 10 +--
.../src/main/docs/openshift-builds-component.adoc | 10 +--
components/camel-kura/src/main/docs/kura.adoc | 28 +++----
.../src/main/docs/language-component.adoc | 18 ++---
.../camel-ldap/src/main/docs/ldap-component.adoc | 24 +++---
.../camel-ldif/src/main/docs/ldif-component.adoc | 20 ++---
.../camel-leveldb/src/main/docs/leveldb.adoc | 16 ++--
.../src/main/docs/linkedin-component.adoc | 36 ++++-----
.../camel-log/src/main/docs/log-component.adoc | 30 +++----
components/camel-lra/src/main/docs/lra.adoc | 4 +-
.../src/main/docs/lucene-component.adoc | 30 +++----
.../src/main/docs/lumberjack-component.adoc | 18 ++---
.../camel-lzf/src/main/docs/lzf-dataformat.adoc | 12 +--
.../camel-mail/src/main/docs/mail-component.adoc | 50 ++++++------
.../src/main/docs/mime-multipart-dataformat.adoc | 12 +--
.../src/main/docs/master-component.adoc | 20 ++---
.../src/main/docs/metrics-component.adoc | 58 ++++++-------
.../src/main/docs/micrometer-component.adoc | 50 ++++++------
.../src/main/docs/microprofile-config.adoc | 4 +-
.../src/main/docs/milo-client-component.adoc | 24 +++---
.../src/main/docs/milo-server-component.adoc | 14 ++--
.../camel-mina2/src/main/docs/mina2-component.adoc | 28 +++----
.../camel-mllp/src/main/docs/mllp-component.adoc | 22 ++---
.../camel-mock/src/main/docs/mock-component.adoc | 32 ++++----
.../src/main/docs/mongodb-gridfs-component.adoc | 30 +++----
.../src/main/docs/mongodb3-component.adoc | 76 ++++++++---------
.../camel-mqtt/src/main/docs/mqtt-component.adoc | 18 ++---
.../camel-msv/src/main/docs/msv-component.adoc | 16 ++--
.../src/main/docs/mustache-component.adoc | 22 ++---
.../camel-mvel/src/main/docs/mvel-component.adoc | 24 +++---
.../camel-mvel/src/main/docs/mvel-language.adoc | 14 ++--
.../src/main/docs/mybatis-bean-component.adoc | 16 ++--
.../src/main/docs/mybatis-component.adoc | 34 ++++----
.../src/main/docs/nagios-component.adoc | 18 ++---
.../camel-nats/src/main/docs/nats-component.adoc | 14 ++--
.../src/main/docs/netty4-http-component.adoc | 34 ++++----
.../src/main/docs/netty4-component.adoc | 44 +++++-----
.../camel-nsq/src/main/docs/nsq-component.adoc | 12 +--
.../camel-ognl/src/main/docs/ognl-language.adoc | 14 ++--
.../src/main/docs/olingo2-component.adoc | 28 +++----
.../src/main/docs/olingo4-component.adoc | 26 +++---
.../src/main/docs/openstack-cinder-component.adoc | 30 +++----
.../src/main/docs/openstack-glance-component.adoc | 20 ++---
.../main/docs/openstack-keystone-component.adoc | 48 +++++------
.../src/main/docs/openstack-neutron-component.adoc | 42 +++++-----
.../src/main/docs/openstack-nova-component.adoc | 36 ++++-----
.../src/main/docs/openstack-swift-component.adoc | 30 +++----
.../camel-openstack/src/main/docs/openstack.adoc | 2 +-
.../src/main/docs/opentracing.adoc | 14 ++--
.../src/main/docs/optaplanner-component.adoc | 22 ++---
.../camel-paho/src/main/docs/paho-component.adoc | 18 ++---
.../src/main/docs/paxlogging-component.adoc | 16 ++--
.../camel-pdf/src/main/docs/pdf-component.adoc | 16 ++--
.../main/docs/pg-replication-slot-component.adoc | 16 ++--
.../src/main/docs/pgevent-component.adoc | 12 +--
.../camel-printer/src/main/docs/lpr-component.adoc | 24 +++---
.../src/main/docs/properties-component.adoc | 74 ++++++++---------
.../src/main/docs/protobuf-dataformat.adoc | 22 ++---
.../src/main/docs/pubnub-component.adoc | 28 +++----
.../src/main/docs/pulsar-component.adoc | 12 +--
.../src/main/docs/quartz2-component.adoc | 44 +++++-----
.../src/main/docs/quickfix-component.adoc | 60 +++++++-------
.../src/main/docs/rabbitmq-component.adoc | 20 ++---
.../src/main/docs/reactive-executor-vertx.adoc | 8 +-
.../src/main/docs/reactive-streams-component.adoc | 38 ++++-----
.../src/main/docs/reactor-component.adoc | 2 +-
.../camel-ref/src/main/docs/ref-component.adoc | 16 ++--
.../src/main/docs/rest-swagger-component.adoc | 14 ++--
.../src/main/docs/rest-api-component.adoc | 12 +--
.../camel-rest/src/main/docs/rest-component.adoc | 24 +++---
.../src/main/docs/restlet-component.adoc | 28 +++----
components/camel-ribbon/src/main/docs/ribbon.adoc | 6 +-
.../camel-rss/src/main/docs/rss-component.adoc | 22 ++---
.../camel-rss/src/main/docs/rss-dataformat.adoc | 6 +-
.../camel-rxjava2/src/main/docs/rxjava2.adoc | 2 +-
.../camel-saga/src/main/docs/saga-component.adoc | 12 +--
.../src/main/docs/salesforce-component.adoc | 48 +++++------
.../src/main/docs/sap-netweaver-component.adoc | 20 ++---
.../src/main/docs/xquery-component.adoc | 28 +++----
.../camel-saxon/src/main/docs/xquery-language.adoc | 24 +++---
.../src/main/docs/scheduler-component.adoc | 24 +++---
.../src/main/docs/schematron-component.adoc | 18 ++---
.../camel-seda/src/main/docs/seda-component.adoc | 28 +++----
.../src/main/docs/service-component.adoc | 18 ++---
.../src/main/docs/servicenow-component.adoc | 16 ++--
.../src/main/docs/servlet-component.adoc | 28 +++----
components/camel-shiro/src/main/docs/shiro.adoc | 18 ++---
.../camel-sip/src/main/docs/sip-component.adoc | 18 ++---
.../src/main/docs/sjms-batch-component.adoc | 12 +--
.../camel-sjms/src/main/docs/sjms-component.adoc | 46 +++++------
.../camel-sjms2/src/main/docs/sjms2-component.adoc | 50 ++++++------
.../camel-slack/src/main/docs/slack-component.adoc | 20 ++---
.../camel-smpp/src/main/docs/smpp-component.adoc | 30 +++----
.../src/main/docs/yaml-snakeyaml-dataformat.adoc | 12 +--
.../camel-snmp/src/main/docs/snmp-component.adoc | 20 ++---
.../src/main/docs/soapjaxb-dataformat.adoc | 24 +++---
.../camel-solr/src/main/docs/solr-component.adoc | 20 ++---
.../src/main/docs/soroush-component.adoc | 24 +++---
.../src/main/docs/spark-rest-component.adoc | 18 ++---
.../camel-spark/src/main/docs/spark-component.adoc | 30 +++----
.../src/main/docs/splunk-component.adoc | 24 +++---
.../src/main/docs/spring-batch-component.adoc | 26 +++---
.../src/main/docs/spring-boot.adoc | 32 ++++----
.../src/main/docs/spring-cloud-consul.adoc | 2 +-
.../src/main/docs/spring-cloud-netflix.adoc | 4 +-
.../src/main/docs/spring-cloud-zookeeper.adoc | 2 +-
.../src/main/docs/spring-cloud.adoc | 4 +-
.../main/docs/spring-integration-component.adoc | 22 ++---
.../src/main/docs/spring-javaconfig.adoc | 8 +-
.../src/main/docs/spring-ldap-component.adoc | 26 +++---
.../src/main/docs/spring-redis-component.adoc | 20 ++---
.../src/main/docs/spring-security.adoc | 14 ++--
.../src/main/docs/spring-ws-component.adoc | 40 ++++-----
.../camel-spring/src/main/docs/spel-language.adoc | 16 ++--
.../src/main/docs/spring-event-component.adoc | 14 ++--
components/camel-spring/src/main/docs/spring.adoc | 30 +++----
.../camel-sql/src/main/docs/sql-component.adoc | 54 ++++++-------
.../src/main/docs/sql-stored-component.adoc | 24 +++---
.../camel-ssh/src/main/docs/ssh-component.adoc | 20 ++---
.../camel-stax/src/main/docs/stax-component.adoc | 20 ++---
.../camel-stomp/src/main/docs/stomp-component.adoc | 18 ++---
.../src/main/docs/stream-component.adoc | 16 ++--
.../src/main/docs/string-template-component.adoc | 24 +++---
.../camel-stub/src/main/docs/stub-component.adoc | 14 ++--
.../src/main/docs/swagger-java.adoc | 14 ++--
.../src/main/docs/syslog-dataformat.adoc | 16 ++--
.../src/main/docs/tidyMarkup-dataformat.adoc | 12 +--
.../src/main/docs/tarfile-dataformat.adoc | 14 ++--
.../src/main/docs/telegram-component.adoc | 28 +++----
.../src/main/docs/test-blueprint.adoc | 8 +-
.../camel-test-cdi/src/main/docs/test-cdi.adoc | 22 ++---
.../camel-test-karaf/src/main/docs/test-karaf.adoc | 2 +-
.../src/main/docs/test-spring.adoc | 22 ++---
components/camel-test/src/main/docs/test.adoc | 4 +-
.../src/main/docs/testcontainers-spring.adoc | 2 +-
.../src/main/docs/testcontainers.adoc | 2 +-
.../src/main/docs/thrift-component.adoc | 22 ++---
.../src/main/docs/thrift-dataformat.adoc | 20 ++---
.../camel-tika/src/main/docs/tika-component.adoc | 14 ++--
.../camel-timer/src/main/docs/timer-component.adoc | 22 ++---
.../src/main/docs/twilio-component.adoc | 20 ++---
.../main/docs/twitter-directmessage-component.adoc | 12 +--
.../src/main/docs/twitter-search-component.adoc | 12 +--
.../src/main/docs/twitter-streaming-component.adoc | 12 +--
.../src/main/docs/twitter-timeline-component.adoc | 12 +--
.../camel-twitter/src/main/docs/twitter.adoc | 24 +++---
.../src/main/docs/undertow-component.adoc | 22 ++---
.../src/main/docs/univocity-csv-dataformat.adoc | 22 ++---
.../src/main/docs/univocity-fixed-dataformat.adoc | 22 ++---
.../src/main/docs/univocity-tsv-dataformat.adoc | 22 ++---
.../src/main/docs/validator-component.adoc | 16 ++--
.../src/main/docs/velocity-component.adoc | 26 +++---
.../camel-vertx/src/main/docs/vertx-component.adoc | 16 ++--
.../camel-vm/src/main/docs/vm-component.adoc | 16 ++--
.../src/main/docs/weather-component.adoc | 22 ++---
.../camel-web3j/src/main/docs/web3j-component.adoc | 16 ++--
.../src/main/docs/webhook-component.adoc | 14 ++--
.../src/main/docs/websocket-jsr356-component.adoc | 12 +--
.../src/main/docs/websocket-component.adoc | 22 ++---
.../src/main/docs/wordpress-component.adoc | 18 ++---
.../src/main/docs/xchange-component.adoc | 18 ++---
.../src/main/docs/secureXML-dataformat.adoc | 28 +++----
.../src/main/docs/xmlsecurity-component.adoc | 30 +++----
.../camel-xmpp/src/main/docs/xmpp-component.adoc | 18 ++---
.../camel-xpath/src/main/docs/xpath-language.adoc | 40 ++++-----
.../camel-xslt/src/main/docs/xslt-component.adoc | 30 +++----
.../src/main/docs/json-xstream-dataformat.adoc | 12 +--
.../src/main/docs/xstream-dataformat.adoc | 14 ++--
.../src/main/docs/yammer-component.adoc | 24 +++---
.../src/main/docs/zendesk-component.adoc | 20 ++---
.../src/main/docs/gzipdeflater-dataformat.adoc | 10 +--
.../src/main/docs/zipdeflater-dataformat.adoc | 8 +-
.../src/main/docs/zipfile-dataformat.adoc | 14 ++--
components/camel-zipkin/src/main/docs/zipkin.adoc | 18 ++---
.../src/main/docs/zookeeper-master-component.adoc | 20 ++---
.../src/main/docs/zookeeper-component.adoc | 20 ++---
components/readme.adoc | 8 +-
.../src/main/docs/constant-language.adoc | 10 +--
.../src/main/docs/exchangeProperty-language.adoc | 8 +-
core/camel-base/src/main/docs/file-language.adoc | 18 ++---
core/camel-base/src/main/docs/header-language.adoc | 8 +-
core/camel-base/src/main/docs/ref-language.adoc | 8 +-
core/camel-base/src/main/docs/simple-language.adoc | 30 +++----
.../src/main/docs/tokenize-language.adoc | 4 +-
core/camel-core/readme-eip.adoc | 2 +-
core/camel-core/readme.adoc | 2 +-
.../src/main/docs/eips/aggregate-eip.adoc | 34 ++++----
.../src/main/docs/eips/batch-config-eip.adoc | 2 +-
core/camel-core/src/main/docs/eips/bean-eip.adoc | 14 ++--
core/camel-core/src/main/docs/eips/choice-eip.adoc | 6 +-
.../src/main/docs/eips/circuitBreaker-eip.adoc | 2 +-
.../src/main/docs/eips/claimCheck-eip.adoc | 16 ++--
.../main/docs/eips/content-based-router-eip.adoc | 8 +-
.../src/main/docs/eips/content-filter-eip.adoc | 8 +-
.../src/main/docs/eips/convertBodyTo-eip.adoc | 2 +-
.../src/main/docs/eips/customLoadBalancer-eip.adoc | 2 +-
core/camel-core/src/main/docs/eips/delay-eip.adoc | 20 ++---
.../src/main/docs/eips/dynamic-router.adoc | 12 +--
.../src/main/docs/eips/dynamicRouter-eip.adoc | 12 +--
core/camel-core/src/main/docs/eips/enrich-eip.adoc | 18 ++---
.../main/docs/eips/eventDrivenConsumer-eip.adoc | 6 +-
.../src/main/docs/eips/failover-eip.adoc | 6 +-
core/camel-core/src/main/docs/eips/filter-eip.adoc | 10 +--
core/camel-core/src/main/docs/eips/from-eip.adoc | 6 +-
.../camel-core/src/main/docs/eips/hystrix-eip.adoc | 10 +--
.../main/docs/eips/hystrixConfiguration-eip.adoc | 2 +-
.../src/main/docs/eips/idempotentConsumer-eip.adoc | 4 +-
core/camel-core/src/main/docs/eips/inOnly-eip.adoc | 4 +-
core/camel-core/src/main/docs/eips/inOut-eip.adoc | 4 +-
.../src/main/docs/eips/loadBalance-eip.adoc | 14 ++--
core/camel-core/src/main/docs/eips/log-eip.adoc | 18 ++---
core/camel-core/src/main/docs/eips/loop-eip.adoc | 16 ++--
.../camel-core/src/main/docs/eips/marshal-eip.adoc | 6 +-
.../src/main/docs/eips/multicast-eip.adoc | 8 +-
.../src/main/docs/eips/onFallback-eip.adoc | 2 +-
.../src/main/docs/eips/otherwise-eip.adoc | 6 +-
.../src/main/docs/eips/pipeline-eip.adoc | 6 +-
.../src/main/docs/eips/pollEnrich-eip.adoc | 18 ++---
.../camel-core/src/main/docs/eips/process-eip.adoc | 16 ++--
core/camel-core/src/main/docs/eips/random-eip.adoc | 2 +-
.../src/main/docs/eips/recipientList-eip.adoc | 40 ++++-----
.../src/main/docs/eips/removeHeader-eip.adoc | 6 +-
.../src/main/docs/eips/removeHeaders-eip.adoc | 4 +-
.../src/main/docs/eips/removeProperties-eip.adoc | 6 +-
.../src/main/docs/eips/removeProperty-eip.adoc | 6 +-
.../src/main/docs/eips/requestReply-eip.adoc | 4 +-
.../src/main/docs/eips/resequence-eip.adoc | 18 ++---
.../src/main/docs/eips/rollback-eip.adoc | 18 ++---
.../src/main/docs/eips/roundRobin-eip.adoc | 6 +-
.../src/main/docs/eips/routingSlip-eip.adoc | 16 ++--
core/camel-core/src/main/docs/eips/saga-eip.adoc | 26 +++---
core/camel-core/src/main/docs/eips/sample-eip.adoc | 6 +-
core/camel-core/src/main/docs/eips/script-eip.adoc | 8 +-
.../src/main/docs/eips/serviceCall-eip.adoc | 26 +++---
.../camel-core/src/main/docs/eips/setBody-eip.adoc | 6 +-
.../src/main/docs/eips/setHeader-eip.adoc | 6 +-
.../src/main/docs/eips/setOutHeader-eip.adoc | 6 +-
.../src/main/docs/eips/setProperty-eip.adoc | 6 +-
core/camel-core/src/main/docs/eips/sort-eip.adoc | 6 +-
core/camel-core/src/main/docs/eips/split-eip.adoc | 50 ++++++------
core/camel-core/src/main/docs/eips/step-eip.adoc | 8 +-
core/camel-core/src/main/docs/eips/sticky-eip.adoc | 6 +-
core/camel-core/src/main/docs/eips/stop-eip.adoc | 2 +-
.../src/main/docs/eips/stream-config-eip.adoc | 2 +-
.../camel-core/src/main/docs/eips/threads-eip.adoc | 6 +-
.../src/main/docs/eips/throttle-eip.adoc | 10 +--
core/camel-core/src/main/docs/eips/to-eip.adoc | 8 +-
core/camel-core/src/main/docs/eips/toD-eip.adoc | 12 +--
core/camel-core/src/main/docs/eips/topic-eip.adoc | 6 +-
.../src/main/docs/eips/transform-eip.adoc | 4 +-
.../src/main/docs/eips/unmarshal-eip.adoc | 4 +-
.../src/main/docs/eips/validate-eip.adoc | 6 +-
.../src/main/docs/eips/weighted-eip.adoc | 6 +-
core/camel-core/src/main/docs/eips/when-eip.adoc | 6 +-
.../camel-core/src/main/docs/eips/wireTap-eip.adoc | 22 ++---
.../camel-headersmap/src/main/docs/headersmap.adoc | 6 +-
.../src/main/docs/xtokenize-language.adoc | 4 +-
.../modules/ROOT/pages/activemq-component.adoc | 14 ++--
.../modules/ROOT/pages/ahc-component.adoc | 44 +++++-----
.../modules/ROOT/pages/ahc-ws-component.adoc | 18 ++---
.../modules/ROOT/pages/amqp-component.adoc | 20 ++---
.../modules/ROOT/pages/apns-component.adoc | 30 +++----
.../modules/ROOT/pages/as2-component.adoc | 16 ++--
.../modules/ROOT/pages/asn1-dataformat.adoc | 10 +--
.../modules/ROOT/pages/asterisk-component.adoc | 14 ++--
.../modules/ROOT/pages/atmos-component.adoc | 18 ++---
.../ROOT/pages/atmosphere-websocket-component.adoc | 18 ++---
.../modules/ROOT/pages/atom-component.adoc | 20 ++---
.../modules/ROOT/pages/atomix-map-component.adoc | 18 ++---
.../ROOT/pages/atomix-messaging-component.adoc | 10 +--
.../ROOT/pages/atomix-multimap-component.adoc | 10 +--
.../modules/ROOT/pages/atomix-queue-component.adoc | 10 +--
.../modules/ROOT/pages/atomix-set-component.adoc | 10 +--
.../modules/ROOT/pages/atomix-value-component.adoc | 10 +--
.../modules/ROOT/pages/avro-component.adoc | 20 ++---
.../modules/ROOT/pages/avro-dataformat.adoc | 10 +--
.../modules/ROOT/pages/aws-cw-component.adoc | 24 +++---
.../modules/ROOT/pages/aws-ddb-component.adoc | 42 +++++-----
.../ROOT/pages/aws-ddbstream-component.adoc | 34 ++++----
.../modules/ROOT/pages/aws-ec2-component.adoc | 20 ++---
.../modules/ROOT/pages/aws-ecs-component.adoc | 22 ++---
.../modules/ROOT/pages/aws-eks-component.adoc | 22 ++---
.../modules/ROOT/pages/aws-iam-component.adoc | 22 ++---
.../modules/ROOT/pages/aws-kinesis-component.adoc | 32 ++++----
.../ROOT/pages/aws-kinesis-firehose-component.adoc | 26 +++---
.../modules/ROOT/pages/aws-kms-component.adoc | 22 ++---
.../modules/ROOT/pages/aws-lambda-component.adoc | 26 +++---
.../modules/ROOT/pages/aws-mq-component.adoc | 20 ++---
.../modules/ROOT/pages/aws-msk-component.adoc | 22 ++---
.../modules/ROOT/pages/aws-s3-component.adoc | 40 ++++-----
.../modules/ROOT/pages/aws-sdb-component.adoc | 30 +++----
.../modules/ROOT/pages/aws-ses-component.adoc | 26 +++---
.../modules/ROOT/pages/aws-sns-component.adoc | 30 +++----
.../modules/ROOT/pages/aws-sqs-component.adoc | 48 +++++------
.../modules/ROOT/pages/aws-swf-component.adoc | 32 ++++----
docs/components/modules/ROOT/pages/aws-xray.adoc | 12 +--
.../modules/ROOT/pages/azure-blob-component.adoc | 26 +++---
.../modules/ROOT/pages/azure-queue-component.adoc | 22 ++---
docs/components/modules/ROOT/pages/azure.adoc | 2 +-
.../modules/ROOT/pages/barcode-dataformat.adoc | 14 ++--
.../modules/ROOT/pages/base64-dataformat.adoc | 12 +--
.../modules/ROOT/pages/bean-component.adoc | 18 ++---
.../modules/ROOT/pages/bean-language.adoc | 14 ++--
.../ROOT/pages/bean-validator-component.adoc | 18 ++---
.../modules/ROOT/pages/beanio-dataformat.adoc | 14 ++--
.../modules/ROOT/pages/beanstalk-component.adoc | 20 ++---
.../modules/ROOT/pages/bindy-dataformat.adoc | 44 +++++-----
docs/components/modules/ROOT/pages/blueprint.adoc | 6 +-
.../modules/ROOT/pages/bonita-component.adoc | 18 ++---
.../modules/ROOT/pages/boon-dataformat.adoc | 12 +--
.../modules/ROOT/pages/box-component.adoc | 48 +++++------
.../modules/ROOT/pages/braintree-component.adoc | 60 +++++++-------
.../modules/ROOT/pages/browse-component.adoc | 16 ++--
.../ROOT/pages/caffeine-cache-component.adoc | 16 ++--
.../ROOT/pages/caffeine-loadcache-component.adoc | 12 +--
.../modules/ROOT/pages/cbor-dataformat.adoc | 10 +--
docs/components/modules/ROOT/pages/cdi.adoc | 40 ++++-----
.../modules/ROOT/pages/chatscript-component.adoc | 12 +--
.../modules/ROOT/pages/chunk-component.adoc | 22 ++---
.../modules/ROOT/pages/class-component.adoc | 16 ++--
.../modules/ROOT/pages/cm-sms-component.adoc | 12 +--
.../modules/ROOT/pages/cmis-component.adoc | 22 ++---
.../modules/ROOT/pages/coap-component.adoc | 14 ++--
.../modules/ROOT/pages/cometd-component.adoc | 22 ++---
.../modules/ROOT/pages/consul-component.adoc | 14 ++--
.../modules/ROOT/pages/controlbus-component.adoc | 18 ++---
.../modules/ROOT/pages/corda-component.adoc | 16 ++--
.../modules/ROOT/pages/couchbase-component.adoc | 14 ++--
.../modules/ROOT/pages/couchdb-component.adoc | 18 ++---
.../modules/ROOT/pages/cql-component.adoc | 26 +++---
.../modules/ROOT/pages/crypto-cms-component.adoc | 14 ++--
.../modules/ROOT/pages/crypto-component.adoc | 30 +++----
.../modules/ROOT/pages/crypto-dataformat.adoc | 20 ++---
.../modules/ROOT/pages/csv-dataformat.adoc | 24 +++---
.../modules/ROOT/pages/cxf-component.adoc | 54 ++++++-------
.../modules/ROOT/pages/cxf-transport.adoc | 20 ++---
.../modules/ROOT/pages/cxfrs-component.adoc | 28 +++----
.../modules/ROOT/pages/dataformat-component.adoc | 14 ++--
.../modules/ROOT/pages/dataset-component.adoc | 32 ++++----
.../modules/ROOT/pages/dataset-test-component.adoc | 16 ++--
.../modules/ROOT/pages/digitalocean-component.adoc | 40 ++++-----
.../modules/ROOT/pages/direct-component.adoc | 16 ++--
.../modules/ROOT/pages/direct-vm-component.adoc | 14 ++--
.../modules/ROOT/pages/disruptor-component.adoc | 26 +++---
.../modules/ROOT/pages/dns-component.adoc | 24 +++---
.../modules/ROOT/pages/docker-component.adoc | 18 ++---
.../modules/ROOT/pages/dozer-component.adoc | 24 +++---
.../modules/ROOT/pages/drill-component.adoc | 16 ++--
.../modules/ROOT/pages/dropbox-component.adoc | 54 ++++++-------
.../modules/ROOT/pages/ehcache-component.adoc | 18 ++---
.../modules/ROOT/pages/ejb-component.adoc | 20 ++---
.../ROOT/pages/elasticsearch-rest-component.adoc | 22 ++---
.../modules/ROOT/pages/elsql-component.adoc | 20 ++---
.../modules/ROOT/pages/etcd-component.adoc | 12 +--
.../modules/ROOT/pages/eventadmin-component.adoc | 18 ++---
.../modules/ROOT/pages/exec-component.adoc | 30 +++----
.../modules/ROOT/pages/facebook-component.adoc | 24 +++---
.../modules/ROOT/pages/fhir-component.adoc | 10 +--
.../modules/ROOT/pages/fhirJson-dataformat.adoc | 6 +-
.../modules/ROOT/pages/fhirXml-dataformat.adoc | 6 +-
.../modules/ROOT/pages/file-component.adoc | 84 +++++++++----------
.../modules/ROOT/pages/file-watch-component.adoc | 22 ++---
.../modules/ROOT/pages/flatpack-component.adoc | 32 ++++----
.../modules/ROOT/pages/flatpack-dataformat.adoc | 10 +--
.../modules/ROOT/pages/flink-component.adoc | 20 ++---
.../modules/ROOT/pages/fop-component.adoc | 20 ++---
.../modules/ROOT/pages/freemarker-component.adoc | 26 +++---
.../modules/ROOT/pages/ftp-component.adoc | 60 +++++++-------
.../modules/ROOT/pages/ftps-component.adoc | 10 +--
.../modules/ROOT/pages/ganglia-component.adoc | 22 ++---
.../modules/ROOT/pages/geocoder-component.adoc | 18 ++---
.../modules/ROOT/pages/git-component.adoc | 16 ++--
.../modules/ROOT/pages/github-component.adoc | 16 ++--
.../ROOT/pages/google-bigquery-component.adoc | 24 +++---
.../ROOT/pages/google-bigquery-sql-component.adoc | 18 ++---
.../ROOT/pages/google-calendar-component.adoc | 20 ++---
.../pages/google-calendar-stream-component.adoc | 14 ++--
.../modules/ROOT/pages/google-drive-component.adoc | 20 ++---
.../modules/ROOT/pages/google-mail-component.adoc | 20 ++---
.../ROOT/pages/google-mail-stream-component.adoc | 14 ++--
.../ROOT/pages/google-pubsub-component.adoc | 24 +++---
.../ROOT/pages/google-sheets-component.adoc | 20 ++---
.../ROOT/pages/google-sheets-stream-component.adoc | 14 ++--
.../modules/ROOT/pages/gora-component.adoc | 24 +++---
.../modules/ROOT/pages/grape-component.adoc | 28 +++----
.../modules/ROOT/pages/grok-dataformat.adoc | 12 +--
.../modules/ROOT/pages/groovy-language.adoc | 22 ++---
.../modules/ROOT/pages/grpc-component.adoc | 26 +++---
.../ROOT/pages/guava-eventbus-component.adoc | 18 ++---
.../ROOT/pages/gzipdeflater-dataformat.adoc | 10 +--
.../pages/hazelcast-atomicvalue-component.adoc | 22 ++---
.../ROOT/pages/hazelcast-instance-component.adoc | 12 +--
.../ROOT/pages/hazelcast-list-component.adoc | 22 ++---
.../ROOT/pages/hazelcast-map-component.adoc | 24 +++---
.../ROOT/pages/hazelcast-multimap-component.adoc | 22 ++---
.../ROOT/pages/hazelcast-queue-component.adoc | 38 ++++-----
.../pages/hazelcast-replicatedmap-component.adoc | 20 ++---
.../ROOT/pages/hazelcast-ringbuffer-component.adoc | 16 ++--
.../ROOT/pages/hazelcast-seda-component.adoc | 14 ++--
.../ROOT/pages/hazelcast-set-component.adoc | 10 +--
.../ROOT/pages/hazelcast-topic-component.adoc | 16 ++--
docs/components/modules/ROOT/pages/hazelcast.adoc | 16 ++--
.../modules/ROOT/pages/hbase-component.adoc | 38 ++++-----
.../modules/ROOT/pages/hdfs2-component.adoc | 28 +++----
.../modules/ROOT/pages/hipchat-component.adoc | 26 +++---
.../modules/ROOT/pages/hl7-dataformat.adoc | 26 +++---
.../modules/ROOT/pages/hl7terser-language.adoc | 10 +--
.../modules/ROOT/pages/http4-component.adoc | 54 ++++++-------
docs/components/modules/ROOT/pages/hystrix.adoc | 4 +-
.../modules/ROOT/pages/ical-dataformat.adoc | 10 +--
.../ROOT/pages/iec60870-client-component.adoc | 12 +--
.../ROOT/pages/iec60870-server-component.adoc | 12 +--
.../modules/ROOT/pages/ignite-cache-component.adoc | 12 +--
.../ROOT/pages/ignite-compute-component.adoc | 14 ++--
.../ROOT/pages/ignite-events-component.adoc | 10 +--
.../modules/ROOT/pages/ignite-idgen-component.adoc | 10 +--
.../ROOT/pages/ignite-messaging-component.adoc | 12 +--
.../modules/ROOT/pages/ignite-queue-component.adoc | 12 +--
.../modules/ROOT/pages/ignite-set-component.adoc | 12 +--
docs/components/modules/ROOT/pages/ignite.adoc | 14 ++--
.../modules/ROOT/pages/infinispan-component.adoc | 22 ++---
.../modules/ROOT/pages/influxdb-component.adoc | 16 ++--
.../modules/ROOT/pages/iota-component.adoc | 16 ++--
.../modules/ROOT/pages/ipfs-component.adoc | 18 ++---
.../modules/ROOT/pages/irc-component.adoc | 24 +++---
.../modules/ROOT/pages/ironmq-component.adoc | 24 +++---
.../modules/ROOT/pages/jacksonxml-dataformat.adoc | 28 +++----
docs/components/modules/ROOT/pages/jasypt.adoc | 16 ++--
.../modules/ROOT/pages/jaxb-dataformat.adoc | 30 +++----
.../modules/ROOT/pages/jbpm-component.adoc | 32 ++++----
.../modules/ROOT/pages/jcache-component.adoc | 36 ++++-----
.../modules/ROOT/pages/jclouds-component.adoc | 34 ++++----
.../modules/ROOT/pages/jcr-component.adoc | 18 ++---
.../modules/ROOT/pages/jdbc-component.adoc | 26 +++---
.../modules/ROOT/pages/jetty-component.adoc | 42 +++++-----
.../modules/ROOT/pages/jgroups-component.adoc | 28 +++----
.../modules/ROOT/pages/jgroups-raft-component.adoc | 22 ++---
.../modules/ROOT/pages/jing-component.adoc | 16 ++--
.../modules/ROOT/pages/jira-component.adoc | 38 ++++-----
.../modules/ROOT/pages/jms-component.adoc | 94 +++++++++++-----------
.../modules/ROOT/pages/jmx-component.adoc | 12 +--
.../modules/ROOT/pages/jolt-component.adoc | 16 ++--
.../modules/ROOT/pages/jooq-component.adoc | 18 ++---
.../modules/ROOT/pages/jpa-component.adoc | 40 ++++-----
.../ROOT/pages/json-fastjson-dataformat.adoc | 8 +-
.../modules/ROOT/pages/json-gson-dataformat.adoc | 8 +-
.../ROOT/pages/json-jackson-dataformat.adoc | 10 +--
.../ROOT/pages/json-johnzon-dataformat.adoc | 8 +-
.../ROOT/pages/json-validator-component.adoc | 14 ++--
.../ROOT/pages/json-xstream-dataformat.adoc | 12 +--
.../modules/ROOT/pages/jsonApi-dataformat.adoc | 6 +-
.../modules/ROOT/pages/jsonpath-language.adoc | 28 +++----
.../modules/ROOT/pages/jt400-component.adoc | 28 +++----
.../modules/ROOT/pages/kafka-component.adoc | 32 ++++----
.../pages/kubernetes-config-maps-component.adoc | 12 +--
.../pages/kubernetes-deployments-component.adoc | 12 +--
.../ROOT/pages/kubernetes-hpa-component.adoc | 12 +--
.../ROOT/pages/kubernetes-job-component.adoc | 12 +--
.../pages/kubernetes-namespaces-component.adoc | 12 +--
.../ROOT/pages/kubernetes-nodes-component.adoc | 12 +--
...rnetes-persistent-volumes-claims-component.adoc | 12 +--
.../kubernetes-persistent-volumes-component.adoc | 12 +--
.../ROOT/pages/kubernetes-pods-component.adoc | 12 +--
...bernetes-replication-controllers-component.adoc | 12 +--
.../kubernetes-resources-quota-component.adoc | 12 +--
.../ROOT/pages/kubernetes-secrets-component.adoc | 12 +--
.../kubernetes-service-accounts-component.adoc | 12 +--
.../ROOT/pages/kubernetes-services-component.adoc | 12 +--
docs/components/modules/ROOT/pages/kubernetes.adoc | 12 +--
docs/components/modules/ROOT/pages/kura.adoc | 28 +++----
.../modules/ROOT/pages/language-component.adoc | 18 ++---
.../modules/ROOT/pages/ldap-component.adoc | 24 +++---
.../modules/ROOT/pages/ldif-component.adoc | 20 ++---
docs/components/modules/ROOT/pages/leveldb.adoc | 16 ++--
.../modules/ROOT/pages/linkedin-component.adoc | 36 ++++-----
.../modules/ROOT/pages/log-component.adoc | 30 +++----
.../modules/ROOT/pages/lpr-component.adoc | 24 +++---
docs/components/modules/ROOT/pages/lra.adoc | 4 +-
.../modules/ROOT/pages/lucene-component.adoc | 30 +++----
.../modules/ROOT/pages/lumberjack-component.adoc | 18 ++---
.../modules/ROOT/pages/lzf-dataformat.adoc | 12 +--
.../modules/ROOT/pages/mail-component.adoc | 50 ++++++------
.../modules/ROOT/pages/master-component.adoc | 20 ++---
.../modules/ROOT/pages/metrics-component.adoc | 58 ++++++-------
.../modules/ROOT/pages/micrometer-component.adoc | 50 ++++++------
.../modules/ROOT/pages/microprofile-config.adoc | 4 +-
.../modules/ROOT/pages/milo-client-component.adoc | 24 +++---
.../modules/ROOT/pages/milo-server-component.adoc | 14 ++--
.../ROOT/pages/mime-multipart-dataformat.adoc | 12 +--
.../modules/ROOT/pages/mina2-component.adoc | 28 +++----
.../modules/ROOT/pages/mllp-component.adoc | 22 ++---
.../modules/ROOT/pages/mock-component.adoc | 32 ++++----
.../ROOT/pages/mongodb-gridfs-component.adoc | 30 +++----
.../modules/ROOT/pages/mongodb3-component.adoc | 76 ++++++++---------
.../modules/ROOT/pages/mqtt-component.adoc | 18 ++---
.../modules/ROOT/pages/msv-component.adoc | 16 ++--
.../modules/ROOT/pages/mustache-component.adoc | 22 ++---
.../modules/ROOT/pages/mvel-component.adoc | 24 +++---
.../modules/ROOT/pages/mvel-language.adoc | 14 ++--
.../modules/ROOT/pages/mybatis-bean-component.adoc | 16 ++--
.../modules/ROOT/pages/mybatis-component.adoc | 34 ++++----
.../modules/ROOT/pages/nagios-component.adoc | 18 ++---
.../modules/ROOT/pages/nats-component.adoc | 14 ++--
.../modules/ROOT/pages/netty4-component.adoc | 44 +++++-----
.../modules/ROOT/pages/netty4-http-component.adoc | 34 ++++----
.../modules/ROOT/pages/nsq-component.adoc | 12 +--
.../modules/ROOT/pages/ognl-language.adoc | 14 ++--
.../modules/ROOT/pages/olingo2-component.adoc | 28 +++----
.../modules/ROOT/pages/olingo4-component.adoc | 26 +++---
.../pages/openshift-build-configs-component.adoc | 10 +--
.../ROOT/pages/openshift-builds-component.adoc | 10 +--
.../ROOT/pages/openstack-cinder-component.adoc | 30 +++----
.../ROOT/pages/openstack-glance-component.adoc | 20 ++---
.../ROOT/pages/openstack-keystone-component.adoc | 48 +++++------
.../ROOT/pages/openstack-neutron-component.adoc | 42 +++++-----
.../ROOT/pages/openstack-nova-component.adoc | 36 ++++-----
.../ROOT/pages/openstack-swift-component.adoc | 30 +++----
docs/components/modules/ROOT/pages/openstack.adoc | 2 +-
.../components/modules/ROOT/pages/opentracing.adoc | 14 ++--
.../modules/ROOT/pages/optaplanner-component.adoc | 22 ++---
.../modules/ROOT/pages/paho-component.adoc | 18 ++---
.../modules/ROOT/pages/paxlogging-component.adoc | 16 ++--
.../modules/ROOT/pages/pdf-component.adoc | 16 ++--
.../ROOT/pages/pg-replication-slot-component.adoc | 16 ++--
.../modules/ROOT/pages/pgevent-component.adoc | 12 +--
.../modules/ROOT/pages/pgp-dataformat.adoc | 26 +++---
.../modules/ROOT/pages/properties-component.adoc | 74 ++++++++---------
.../modules/ROOT/pages/protobuf-dataformat.adoc | 22 ++---
.../modules/ROOT/pages/pubnub-component.adoc | 28 +++----
.../modules/ROOT/pages/pulsar-component.adoc | 12 +--
.../modules/ROOT/pages/quartz2-component.adoc | 44 +++++-----
.../modules/ROOT/pages/quickfix-component.adoc | 60 +++++++-------
.../modules/ROOT/pages/rabbitmq-component.adoc | 20 ++---
.../ROOT/pages/reactive-executor-vertx.adoc | 8 +-
.../ROOT/pages/reactive-streams-component.adoc | 38 ++++-----
.../modules/ROOT/pages/reactor-component.adoc | 2 +-
.../modules/ROOT/pages/ref-component.adoc | 16 ++--
.../modules/ROOT/pages/rest-api-component.adoc | 12 +--
.../modules/ROOT/pages/rest-component.adoc | 24 +++---
.../modules/ROOT/pages/rest-swagger-component.adoc | 14 ++--
.../modules/ROOT/pages/restlet-component.adoc | 28 +++----
docs/components/modules/ROOT/pages/ribbon.adoc | 6 +-
.../modules/ROOT/pages/rss-component.adoc | 22 ++---
.../modules/ROOT/pages/rss-dataformat.adoc | 6 +-
docs/components/modules/ROOT/pages/rxjava2.adoc | 2 +-
.../modules/ROOT/pages/saga-component.adoc | 12 +--
.../modules/ROOT/pages/salesforce-component.adoc | 48 +++++------
.../ROOT/pages/sap-netweaver-component.adoc | 20 ++---
.../modules/ROOT/pages/scheduler-component.adoc | 24 +++---
.../modules/ROOT/pages/schematron-component.adoc | 18 ++---
.../modules/ROOT/pages/scp-component.adoc | 16 ++--
.../modules/ROOT/pages/secureXML-dataformat.adoc | 28 +++----
.../modules/ROOT/pages/seda-component.adoc | 28 +++----
.../modules/ROOT/pages/service-component.adoc | 18 ++---
.../modules/ROOT/pages/servicenow-component.adoc | 16 ++--
.../modules/ROOT/pages/servlet-component.adoc | 28 +++----
.../modules/ROOT/pages/sftp-component.adoc | 8 +-
docs/components/modules/ROOT/pages/shiro.adoc | 18 ++---
.../modules/ROOT/pages/sip-component.adoc | 18 ++---
.../modules/ROOT/pages/sjms-batch-component.adoc | 12 +--
.../modules/ROOT/pages/sjms-component.adoc | 46 +++++------
.../modules/ROOT/pages/sjms2-component.adoc | 50 ++++++------
.../modules/ROOT/pages/slack-component.adoc | 20 ++---
.../modules/ROOT/pages/smpp-component.adoc | 30 +++----
.../modules/ROOT/pages/snmp-component.adoc | 20 ++---
.../modules/ROOT/pages/soapjaxb-dataformat.adoc | 24 +++---
.../modules/ROOT/pages/solr-component.adoc | 20 ++---
.../modules/ROOT/pages/soroush-component.adoc | 24 +++---
.../modules/ROOT/pages/spark-component.adoc | 30 +++----
.../modules/ROOT/pages/spark-rest-component.adoc | 18 ++---
.../modules/ROOT/pages/spel-language.adoc | 16 ++--
.../modules/ROOT/pages/splunk-component.adoc | 24 +++---
.../modules/ROOT/pages/spring-batch-component.adoc | 26 +++---
.../components/modules/ROOT/pages/spring-boot.adoc | 32 ++++----
.../modules/ROOT/pages/spring-cloud-consul.adoc | 2 +-
.../modules/ROOT/pages/spring-cloud-netflix.adoc | 4 +-
.../modules/ROOT/pages/spring-cloud-zookeeper.adoc | 2 +-
.../modules/ROOT/pages/spring-cloud.adoc | 4 +-
.../modules/ROOT/pages/spring-event-component.adoc | 14 ++--
.../ROOT/pages/spring-integration-component.adoc | 22 ++---
.../modules/ROOT/pages/spring-javaconfig.adoc | 8 +-
.../modules/ROOT/pages/spring-ldap-component.adoc | 26 +++---
.../modules/ROOT/pages/spring-redis-component.adoc | 20 ++---
.../modules/ROOT/pages/spring-security.adoc | 14 ++--
.../modules/ROOT/pages/spring-ws-component.adoc | 40 ++++-----
docs/components/modules/ROOT/pages/spring.adoc | 30 +++----
.../modules/ROOT/pages/sql-component.adoc | 54 ++++++-------
.../modules/ROOT/pages/sql-stored-component.adoc | 24 +++---
.../modules/ROOT/pages/ssh-component.adoc | 20 ++---
.../modules/ROOT/pages/stax-component.adoc | 20 ++---
.../modules/ROOT/pages/stomp-component.adoc | 18 ++---
.../modules/ROOT/pages/stream-component.adoc | 16 ++--
.../ROOT/pages/string-template-component.adoc | 24 +++---
.../modules/ROOT/pages/stub-component.adoc | 14 ++--
.../modules/ROOT/pages/swagger-java.adoc | 14 ++--
.../modules/ROOT/pages/syslog-dataformat.adoc | 16 ++--
.../modules/ROOT/pages/tarfile-dataformat.adoc | 14 ++--
.../modules/ROOT/pages/telegram-component.adoc | 28 +++----
.../modules/ROOT/pages/test-blueprint.adoc | 8 +-
docs/components/modules/ROOT/pages/test-cdi.adoc | 22 ++---
docs/components/modules/ROOT/pages/test-karaf.adoc | 2 +-
.../components/modules/ROOT/pages/test-spring.adoc | 22 ++---
docs/components/modules/ROOT/pages/test.adoc | 4 +-
.../modules/ROOT/pages/testcontainers-spring.adoc | 2 +-
.../modules/ROOT/pages/testcontainers.adoc | 2 +-
.../modules/ROOT/pages/thrift-component.adoc | 22 ++---
.../modules/ROOT/pages/thrift-dataformat.adoc | 20 ++---
.../modules/ROOT/pages/tidyMarkup-dataformat.adoc | 12 +--
.../modules/ROOT/pages/tika-component.adoc | 14 ++--
.../modules/ROOT/pages/timer-component.adoc | 22 ++---
.../modules/ROOT/pages/twilio-component.adoc | 20 ++---
.../pages/twitter-directmessage-component.adoc | 12 +--
.../ROOT/pages/twitter-search-component.adoc | 12 +--
.../ROOT/pages/twitter-streaming-component.adoc | 12 +--
.../ROOT/pages/twitter-timeline-component.adoc | 12 +--
docs/components/modules/ROOT/pages/twitter.adoc | 24 +++---
.../modules/ROOT/pages/undertow-component.adoc | 22 ++---
.../ROOT/pages/univocity-csv-dataformat.adoc | 22 ++---
.../ROOT/pages/univocity-fixed-dataformat.adoc | 22 ++---
.../ROOT/pages/univocity-tsv-dataformat.adoc | 22 ++---
.../modules/ROOT/pages/validator-component.adoc | 16 ++--
.../modules/ROOT/pages/velocity-component.adoc | 26 +++---
.../modules/ROOT/pages/vertx-component.adoc | 16 ++--
.../modules/ROOT/pages/vm-component.adoc | 16 ++--
.../modules/ROOT/pages/weather-component.adoc | 22 ++---
.../modules/ROOT/pages/web3j-component.adoc | 16 ++--
.../modules/ROOT/pages/webhook-component.adoc | 14 ++--
.../modules/ROOT/pages/websocket-component.adoc | 22 ++---
.../ROOT/pages/websocket-jsr356-component.adoc | 12 +--
.../modules/ROOT/pages/wordpress-component.adoc | 18 ++---
.../modules/ROOT/pages/xchange-component.adoc | 18 ++---
.../modules/ROOT/pages/xmlsecurity-component.adoc | 30 +++----
.../modules/ROOT/pages/xmpp-component.adoc | 18 ++---
.../modules/ROOT/pages/xpath-language.adoc | 40 ++++-----
.../modules/ROOT/pages/xquery-component.adoc | 28 +++----
.../modules/ROOT/pages/xquery-language.adoc | 24 +++---
.../modules/ROOT/pages/xslt-component.adoc | 30 +++----
.../modules/ROOT/pages/xstream-dataformat.adoc | 14 ++--
.../ROOT/pages/yaml-snakeyaml-dataformat.adoc | 12 +--
.../modules/ROOT/pages/yammer-component.adoc | 24 +++---
.../modules/ROOT/pages/zendesk-component.adoc | 20 ++---
.../modules/ROOT/pages/zipdeflater-dataformat.adoc | 8 +-
.../modules/ROOT/pages/zipfile-dataformat.adoc | 14 ++--
docs/components/modules/ROOT/pages/zipkin.adoc | 18 ++---
.../modules/ROOT/pages/zookeeper-component.adoc | 20 ++---
.../ROOT/pages/zookeeper-master-component.adoc | 20 ++---
.../modules/ROOT/pages/aggregate-eip.adoc | 34 ++++----
.../modules/ROOT/pages/architecture.adoc | 4 +-
docs/user-manual/modules/ROOT/pages/async.adoc | 40 ++++-----
.../ROOT/pages/asynchronous-routing-engine.adoc | 6 +-
.../modules/ROOT/pages/backlog-tracer.adoc | 12 +--
.../modules/ROOT/pages/backlogdebugger.adoc | 10 +--
.../modules/ROOT/pages/bam-example.adoc | 8 +-
docs/user-manual/modules/ROOT/pages/bam.adoc | 10 +--
.../modules/ROOT/pages/batch-config-eip.adoc | 2 +-
.../modules/ROOT/pages/batch-consumer.adoc | 8 +-
docs/user-manual/modules/ROOT/pages/bean-eip.adoc | 14 ++--
.../modules/ROOT/pages/bean-integration.adoc | 8 +-
docs/user-manual/modules/ROOT/pages/binding.adoc | 10 +--
.../modules/ROOT/pages/book-getting-started.adoc | 36 ++++-----
docs/user-manual/modules/ROOT/pages/books.adoc | 20 ++---
.../modules/ROOT/pages/browsable-endpoint.adoc | 2 +-
docs/user-manual/modules/ROOT/pages/building.adoc | 28 +++----
.../user-manual/modules/ROOT/pages/camel-boot.adoc | 8 +-
.../ROOT/pages/camel-configuration-utilities.adoc | 28 +++----
.../user-manual/modules/ROOT/pages/camel-core.adoc | 2 +
.../modules/ROOT/pages/camel-jar-dependencies.adoc | 14 ++--
.../modules/ROOT/pages/camelcontext.adoc | 4 +-
docs/user-manual/modules/ROOT/pages/cep.adoc | 4 +-
.../user-manual/modules/ROOT/pages/choice-eip.adoc | 6 +-
.../modules/ROOT/pages/circuitBreaker-eip.adoc | 2 +-
.../modules/ROOT/pages/claimCheck-eip.adoc | 16 ++--
.../user-manual/modules/ROOT/pages/clustering.adoc | 6 +-
.../ROOT/pages/commercial-camel-offerings.adoc | 26 +++---
docs/user-manual/modules/ROOT/pages/component.adoc | 6 +-
.../modules/ROOT/pages/componentconfiguration.adoc | 2 +-
.../modules/ROOT/pages/configuring-camel.adoc | 8 +-
...ing-route-startup-ordering-and-autostartup.adoc | 26 +++---
.../modules/ROOT/pages/constant-language.adoc | 10 +--
.../ROOT/pages/content-based-router-eip.adoc | 8 +-
.../modules/ROOT/pages/content-filter-eip.adoc | 8 +-
.../modules/ROOT/pages/contributing.adoc | 2 +-
.../modules/ROOT/pages/convertBodyTo-eip.adoc | 2 +-
.../modules/ROOT/pages/correlation-identifier.adoc | 4 +-
.../modules/ROOT/pages/customLoadBalancer-eip.adoc | 2 +-
.../modules/ROOT/pages/data-format.adoc | 8 +-
.../modules/ROOT/pages/dead-letter-channel.adoc | 34 ++++----
docs/user-manual/modules/ROOT/pages/debugger.adoc | 12 +--
.../modules/ROOT/pages/defaulterrorhandler.adoc | 6 +-
docs/user-manual/modules/ROOT/pages/delay-eip.adoc | 20 ++---
.../modules/ROOT/pages/delay-interceptor.adoc | 10 +--
.../modules/ROOT/pages/dependency-injection.adoc | 2 +-
.../modules/ROOT/pages/dozer-type-conversion.adoc | 6 +-
docs/user-manual/modules/ROOT/pages/dsl.adoc | 4 +-
.../modules/ROOT/pages/dynamic-router.adoc | 12 +--
.../modules/ROOT/pages/dynamicRouter-eip.adoc | 12 +--
.../modules/ROOT/pages/endpoint-completer.adoc | 2 +-
docs/user-manual/modules/ROOT/pages/endpoint.adoc | 4 +-
.../user-manual/modules/ROOT/pages/enrich-eip.adoc | 18 ++---
.../pages/enterprise-integration-patterns.adoc | 16 ++--
.../modules/ROOT/pages/error-handler.adoc | 28 +++----
.../ROOT/pages/error-handling-in-camel.adoc | 20 ++---
.../modules/ROOT/pages/event-message.adoc | 6 +-
.../ROOT/pages/eventDrivenConsumer-eip.adoc | 6 +-
docs/user-manual/modules/ROOT/pages/examples.adoc | 8 +-
.../modules/ROOT/pages/exception-clause.adoc | 72 ++++++++---------
.../modules/ROOT/pages/exchange-pattern.adoc | 2 +-
docs/user-manual/modules/ROOT/pages/exchange.adoc | 4 +-
.../ROOT/pages/exchangeProperty-language.adoc | 8 +-
.../user-manual/modules/ROOT/pages/expression.adoc | 14 ++--
.../modules/ROOT/pages/failover-eip.adoc | 6 +-
docs/user-manual/modules/ROOT/pages/faq.adoc | 18 ++---
.../pages/faq/can-i-get-commercial-support.adoc | 2 +-
.../ROOT/pages/faq/can-i-use-camel-on-java-14.adoc | 2 +-
...loader-issue-of-servicemix-camel-component.adoc | 2 +-
.../pages/faq/does-camel-work-on-ibms-jdk.adoc | 8 +-
.../exception-beandefinitionstoreexception.adoc | 2 +-
...ption-javaxnamingnoinitialcontextexception.adoc | 2 +-
...tion-orgapachecamelnosuchendpointexception.adoc | 4 +-
.../faq/exception-orgxmlsaxsaxparseexception.adoc | 2 +-
...an-i-create-a-custom-component-or-endpoint.adoc | 4 +-
...on-ip-address-from-the-camel-cxf-consumer-.adoc | 2 +-
.../pages/faq/how-can-i-get-the-source-code.adoc | 12 +--
.../faq/how-can-i-stop-a-route-from-a-route.adoc | 10 +--
...ults-with-stacktraces-when-using-camel-cxf.adoc | 2 +-
.../pages/faq/how-do-i-become-a-committer.adoc | 12 +--
.../pages/faq/how-do-i-change-the-logging.adoc | 2 +-
.../ROOT/pages/faq/how-do-i-compile-the-code.adoc | 2 +-
.../pages/faq/how-do-i-configure-endpoints.adoc | 22 ++---
...-endpoints-without-the-value-being-encoded.adoc | 4 +-
...size-for-producercache-or-producertemplate.adoc | 4 +-
...ximum-endpoint-cache-size-for-camelcontext.adoc | 6 +-
.../ROOT/pages/faq/how-do-i-debug-my-route.adoc | 2 +-
.../ROOT/pages/faq/how-do-i-disable-jmx.adoc | 2 +-
.../ROOT/pages/faq/how-do-i-edit-the-website.adoc | 6 +-
.../pages/faq/how-do-i-enable-debug-logging.adoc | 2 +-
...reams-when-debug-logging-messages-in-camel.adoc | 6 +-
...en-consuming-for-example-from-a-ftp-server.adoc | 4 +-
...how-do-i-import-rests-from-other-xml-files.adoc | 2 +-
...ow-do-i-import-routes-from-other-xml-files.adoc | 4 +-
.../faq/how-do-i-invoke-camel-routes-from-jbi.adoc | 2 +-
.../faq/how-do-i-let-jetty-match-wildcards.adoc | 2 +-
...ow-do-i-make-my-jms-endpoint-transactional.adoc | 8 +-
.../ROOT/pages/faq/how-do-i-name-my-routes.adoc | 2 +-
.../pages/faq/how-do-i-restart-camelcontext.adoc | 2 +-
...wn-exception-during-processing-an-exchange.adoc | 2 +-
.../how-do-i-retry-failed-messages-forever.adoc | 2 +-
...om-a-certain-point-back-or-an-entire-route.adoc | 2 +-
...-contexttestsupport-class-in-my-unit-tests.adoc | 2 +-
.../how-do-i-run-activemq-and-camel-in-jboss.adoc | 4 +-
.../how-do-i-run-camel-using-java-webstart.adoc | 4 +-
...chars-when-debug-logging-messages-in-camel.adoc | 6 +-
...do-i-set-the-mep-when-interacting-with-jbi.adoc | 6 +-
...ify-time-period-in-a-human-friendly-syntax.adoc | 2 +-
...h-method-to-use-when-using-beans-in-routes.adoc | 2 +-
.../pages/faq/how-do-i-use-a-big-uber-jar.adoc | 2 +-
.../faq/how-do-i-use-camel-inside-servicemix.adoc | 2 +-
.../pages/faq/how-do-i-use-java-14-logging.adoc | 2 +-
.../modules/ROOT/pages/faq/how-do-i-use-log4j.adoc | 2 +-
...spring-property-placeholder-with-camel-xml.adoc | 4 +-
.../how-do-i-use-uris-with-parameters-in-xml.adoc | 2 +-
...om-processor-which-sends-multiple-messages.adoc | 2 +-
...direct-event-seda-and-vm-endpoints-compare.adoc | 2 +-
...-do-the-timer-and-quartz-endpoints-compare.adoc | 2 +-
.../pages/faq/how-does-camel-compare-to-mule.adoc | 2 +-
.../how-does-camel-compare-to-servicemix-eip.adoc | 6 +-
.../faq/how-does-camel-compare-to-servicemix.adoc | 4 +-
.../faq/how-does-camel-compare-to-synapse.adoc | 2 +-
...how-does-camel-look-up-beans-and-endpoints.adoc | 2 +-
.../faq/how-does-camel-work-with-activemq.adoc | 2 +-
.../faq/how-does-camel-work-with-servicemix.adoc | 4 +-
.../ROOT/pages/faq/how-does-camel-work.adoc | 2 +-
.../faq/how-does-the-camel-api-compare-to.adoc | 2 +-
.../ROOT/pages/faq/how-does-the-website-work.adoc | 2 +-
...hould-i-invoke-my-pojos-or-spring-services.adoc | 4 +-
...kage-applications-using-camel-and-activemq.adoc | 4 +-
...the-camel-cxf-endpoint-from-osgi-platform-.adoc | 2 +-
...-avoid-sending-some-or-all-message-headers.adoc | 8 +-
...e-a-static-camel-converter-method-in-scala.adoc | 2 +-
...http-protocol-headers-in-the-camel-message.adoc | 2 +-
...end-the-same-message-to-multiple-endpoints.adoc | 2 +-
...-without-touching-the-spring-configuration.adoc | 2 +-
.../pages/faq/how-to-use-a-dynamic-uri-in-to.adoc | 2 +-
...-extra-camel-componets-in-servicemix-camel.adoc | 2 +
...-1x-context-xml-from-apache-camel-web-site.adoc | 2 +-
...f-i-use-servicemix-when-should-i-use-camel.adoc | 4 +-
.../modules/ROOT/pages/faq/is-camel-an-esb.adoc | 2 +-
.../ROOT/pages/faq/is-camel-ioc-friendly.adoc | 8 +-
.../modules/ROOT/pages/faq/is-there-an-ide.adoc | 2 +-
...when-adding-and-removing-routes-at-runtime.adoc | 2 +-
.../ROOT/pages/faq/running-camel-standalone.adoc | 2 +-
...-activemq-broker-or-in-another-application.adoc | 8 +-
.../ROOT/pages/faq/using-camel-core-testsjar.adoc | 2 +-
.../using-getin-or-getout-methods-on-exchange.adoc | 8 +-
.../ROOT/pages/faq/what-are-the-dependencies.adoc | 18 ++---
.../modules/ROOT/pages/faq/what-is-a-router.adoc | 2 +-
.../modules/ROOT/pages/faq/what-is-camel.adoc | 2 +-
.../ROOT/pages/faq/what-is-the-license.adoc | 2 +-
.../ROOT/pages/faq/what-jars-do-i-need.adoc | 6 +-
.../pages/faq/what-platforms-are-supported.adoc | 2 +-
...se-when-or-otherwise-in-a-java-camel-route.adoc | 4 +-
.../faq/why-cant-i-use-sign-in-my-password.adoc | 4 +-
...o-many-noclassdeffoundexception-on-startup.adoc | 2 +-
...my-message-lose-its-headers-during-routing.adoc | 2 +-
...use-too-many-threads-with-producertemplate.adoc | 2 +-
...-does-ftp-component-not-download-any-files.adoc | 2 +-
.../why-does-maven-not-download-dependencies.adoc | 2 +-
...-file-consumer-use-the-camel-error-handler.adoc | 4 +-
...jms-route-only-consume-one-message-at-once.adoc | 4 +-
...ge-with-error-handler-not-work-as-expected.adoc | 2 +-
.../pages/faq/why-is-my-message-body-empty.adoc | 2 +-
...is-my-processor-not-showing-up-in-jconsole.adoc | 4 +-
...-the-exception-null-when-i-use-onexception.adoc | 2 +-
.../modules/ROOT/pages/faq/why-the-name-camel.adoc | 2 +-
.../pages/faq/why-use-multiple-camelcontext.adoc | 2 +-
.../modules/ROOT/pages/file-language.adoc | 18 ++---
.../user-manual/modules/ROOT/pages/filter-eip.adoc | 10 +--
.../modules/ROOT/pages/fluent-builders.adoc | 2 +-
docs/user-manual/modules/ROOT/pages/from-eip.adoc | 6 +-
.../modules/ROOT/pages/getting-started.adoc | 8 +-
.../modules/ROOT/pages/graceful-shutdown.adoc | 28 +++----
.../user-manual/modules/ROOT/pages/groovy-dsl.adoc | 16 ++--
.../modules/ROOT/pages/guaranteed-delivery.adoc | 4 +-
docs/user-manual/modules/ROOT/pages/guice.adoc | 10 +--
.../modules/ROOT/pages/header-language.adoc | 8 +-
.../modules/ROOT/pages/health-check.adoc | 6 +-
.../modules/ROOT/pages/hiding-middleware.adoc | 2 +
.../modules/ROOT/pages/http-session-handling.adoc | 18 ++---
.../modules/ROOT/pages/http-session.adoc | 16 ++--
.../modules/ROOT/pages/hystrix-eip.adoc | 10 +--
.../ROOT/pages/hystrixConfiguration-eip.adoc | 2 +-
.../modules/ROOT/pages/idempotentConsumer-eip.adoc | 4 +-
.../user-manual/modules/ROOT/pages/inOnly-eip.adoc | 4 +-
docs/user-manual/modules/ROOT/pages/inOut-eip.adoc | 4 +-
docs/user-manual/modules/ROOT/pages/injector.adoc | 2 +-
docs/user-manual/modules/ROOT/pages/intercept.adoc | 22 ++---
.../inversion-of-control-with-smart-defaults.adoc | 2 +-
docs/user-manual/modules/ROOT/pages/irc-room.adoc | 6 +-
docs/user-manual/modules/ROOT/pages/java-dsl.adoc | 14 ++--
docs/user-manual/modules/ROOT/pages/jmx.adoc | 64 +++++++--------
docs/user-manual/modules/ROOT/pages/jndi.adoc | 2 +-
docs/user-manual/modules/ROOT/pages/json.adoc | 44 +++++-----
docs/user-manual/modules/ROOT/pages/karaf.adoc | 54 ++++++-------
docs/user-manual/modules/ROOT/pages/languages.adoc | 6 +-
docs/user-manual/modules/ROOT/pages/lifecycle.adoc | 10 +--
.../modules/ROOT/pages/loadBalance-eip.adoc | 14 ++--
docs/user-manual/modules/ROOT/pages/log-eip.adoc | 18 ++---
docs/user-manual/modules/ROOT/pages/loop-eip.adoc | 16 ++--
.../modules/ROOT/pages/mailing-lists.adoc | 4 +-
.../modules/ROOT/pages/marshal-eip.adoc | 6 +-
.../modules/ROOT/pages/message-bus.adoc | 4 +-
.../modules/ROOT/pages/message-channel.adoc | 6 +-
.../modules/ROOT/pages/message-endpoint.adoc | 6 +-
.../modules/ROOT/pages/message-router.adoc | 6 +-
.../modules/ROOT/pages/message-translator.adoc | 4 +-
docs/user-manual/modules/ROOT/pages/message.adoc | 2 +-
.../modules/ROOT/pages/multicast-eip.adoc | 8 +-
.../modules/ROOT/pages/onFallback-eip.adoc | 2 +-
.../modules/ROOT/pages/oncompletion.adoc | 18 ++---
.../modules/ROOT/pages/otherwise-eip.adoc | 6 +-
.../modules/ROOT/pages/pipeline-eip.adoc | 6 +-
.../modules/ROOT/pages/point-to-point-channel.adoc | 4 +-
.../modules/ROOT/pages/pojo-consuming.adoc | 3 +-
.../modules/ROOT/pages/pojo-producing.adoc | 6 +-
.../modules/ROOT/pages/pollEnrich-eip.adoc | 18 ++---
docs/user-manual/modules/ROOT/pages/predicate.adoc | 12 +--
.../modules/ROOT/pages/process-eip.adoc | 16 ++--
docs/user-manual/modules/ROOT/pages/processor.adoc | 12 +--
.../modules/ROOT/pages/producertemplate.adoc | 6 +-
.../ROOT/pages/publish-subscribe-channel.adoc | 4 +-
.../user-manual/modules/ROOT/pages/random-eip.adoc | 2 +-
.../modules/ROOT/pages/recipientList-eip.adoc | 40 ++++-----
.../modules/ROOT/pages/ref-language.adoc | 8 +-
docs/user-manual/modules/ROOT/pages/registry.adoc | 2 +-
.../modules/ROOT/pages/release-guide.adoc | 8 +-
.../modules/ROOT/pages/removeHeader-eip.adoc | 6 +-
.../modules/ROOT/pages/removeHeaders-eip.adoc | 4 +-
.../modules/ROOT/pages/removeProperties-eip.adoc | 6 +-
.../modules/ROOT/pages/removeProperty-eip.adoc | 6 +-
.../modules/ROOT/pages/requestReply-eip.adoc | 4 +-
.../modules/ROOT/pages/resequence-eip.adoc | 18 ++---
docs/user-manual/modules/ROOT/pages/rest-dsl.adoc | 46 +++++------
.../modules/ROOT/pages/return-address.adoc | 2 +-
.../modules/ROOT/pages/rollback-eip.adoc | 18 ++---
.../modules/ROOT/pages/roundRobin-eip.adoc | 6 +-
.../modules/ROOT/pages/route-builder.adoc | 4 +-
.../modules/ROOT/pages/route-policy.adoc | 20 ++---
docs/user-manual/modules/ROOT/pages/routes.adoc | 10 +--
.../modules/ROOT/pages/routingSlip-eip.adoc | 16 ++--
docs/user-manual/modules/ROOT/pages/saga-eip.adoc | 26 +++---
.../user-manual/modules/ROOT/pages/sample-eip.adoc | 6 +-
docs/user-manual/modules/ROOT/pages/scala-dsl.adoc | 8 +-
.../user-manual/modules/ROOT/pages/script-eip.adoc | 8 +-
.../modules/ROOT/pages/scripting-languages.adoc | 16 ++--
docs/user-manual/modules/ROOT/pages/security.adoc | 10 +--
.../modules/ROOT/pages/service-registry.adoc | 6 +-
.../modules/ROOT/pages/serviceCall-eip.adoc | 26 +++---
.../modules/ROOT/pages/servicepool.adoc | 10 +--
.../modules/ROOT/pages/servlet-tomcat-example.adoc | 10 +--
.../modules/ROOT/pages/setBody-eip.adoc | 6 +-
.../modules/ROOT/pages/setHeader-eip.adoc | 6 +-
.../modules/ROOT/pages/setOutHeader-eip.adoc | 6 +-
.../modules/ROOT/pages/setProperty-eip.adoc | 6 +-
.../modules/ROOT/pages/simple-language.adoc | 30 +++----
docs/user-manual/modules/ROOT/pages/sort-eip.adoc | 6 +-
docs/user-manual/modules/ROOT/pages/split-eip.adoc | 50 ++++++------
.../modules/ROOT/pages/spring-example.adoc | 2 +-
.../modules/ROOT/pages/spring-testing.adoc | 24 +++---
.../modules/ROOT/pages/spring-xml-extensions.adoc | 2 +-
docs/user-manual/modules/ROOT/pages/spring.adoc | 28 +++----
docs/user-manual/modules/ROOT/pages/step-eip.adoc | 8 +-
.../user-manual/modules/ROOT/pages/sticky-eip.adoc | 6 +-
docs/user-manual/modules/ROOT/pages/stop-eip.adoc | 2 +-
.../modules/ROOT/pages/stream-caching.adoc | 28 +++----
.../modules/ROOT/pages/stream-config-eip.adoc | 2 +-
docs/user-manual/modules/ROOT/pages/support.adoc | 12 +--
docs/user-manual/modules/ROOT/pages/team.adoc | 4 +-
docs/user-manual/modules/ROOT/pages/testing.adoc | 22 ++---
.../modules/ROOT/pages/threading-model.adoc | 22 ++---
.../modules/ROOT/pages/threads-eip.adoc | 6 +-
.../modules/ROOT/pages/throttle-eip.adoc | 10 +--
docs/user-manual/modules/ROOT/pages/to-eip.adoc | 8 +-
docs/user-manual/modules/ROOT/pages/toD-eip.adoc | 12 +--
.../modules/ROOT/pages/tokenize-language.adoc | 4 +-
docs/user-manual/modules/ROOT/pages/topic-eip.adoc | 6 +-
.../modules/ROOT/pages/transactional-client.adoc | 20 ++---
.../ROOT/pages/transactionerrorhandler.adoc | 12 +--
.../modules/ROOT/pages/transform-eip.adoc | 4 +-
.../modules/ROOT/pages/transformer.adoc | 16 ++--
docs/user-manual/modules/ROOT/pages/transport.adoc | 6 +-
.../modules/ROOT/pages/try-catch-finally.adoc | 14 ++--
.../modules/ROOT/pages/type-converter.adoc | 22 ++---
.../modules/ROOT/pages/unmarshal-eip.adoc | 4 +-
docs/user-manual/modules/ROOT/pages/uris.adoc | 2 +-
.../modules/ROOT/pages/user-stories.adoc | 6 +-
.../pages/using-osgi-blueprint-with-camel.adoc | 6 +-
.../ROOT/pages/using-propertyplaceholder.adoc | 62 +++++++-------
.../modules/ROOT/pages/uuidgenerator.adoc | 12 +--
.../modules/ROOT/pages/validate-eip.adoc | 6 +-
docs/user-manual/modules/ROOT/pages/validator.adoc | 16 ++--
.../modules/ROOT/pages/weighted-eip.adoc | 6 +-
docs/user-manual/modules/ROOT/pages/when-eip.adoc | 6 +-
.../modules/ROOT/pages/wireTap-eip.adoc | 22 ++---
.../modules/ROOT/pages/writing-components.adoc | 14 ++--
.../modules/ROOT/pages/xml-configuration.adoc | 4 +-
.../modules/ROOT/pages/xml-reference.adoc | 16 ++--
examples/README.adoc | 6 +-
.../readme.adoc | 14 ++--
.../camel-example-fhir-spring-boot/readme.adoc | 14 ++--
examples/camel-example-google-pubsub/README.adoc | 10 +--
examples/camel-example-grpc-kubernetes/README.adoc | 10 +--
examples/camel-example-java8/readme.adoc | 4 +-
examples/camel-example-jira/README.adoc | 6 +-
examples/camel-example-main-artemis/readme.adoc | 6 +-
examples/camel-example-main-tiny/readme.adoc | 6 +-
examples/camel-example-main/readme.adoc | 8 +-
.../readme.adoc | 6 +-
.../readme.adoc | 6 +-
.../camel-example-reactive-streams/readme.adoc | 4 +-
examples/camel-example-rest-producer/readme.adoc | 8 +-
.../camel-example-spring-boot-activemq/readme.adoc | 8 +-
.../camel-example-spring-boot-amqp/readme.adoc | 8 +-
.../readme.adoc | 4 +-
.../camel-example-spring-boot-geocoder/README.adoc | 8 +-
.../camel-example-spring-boot-grpc/README.adoc | 8 +-
.../readme.adoc | 8 +-
.../README.adoc | 8 +-
.../camel-example-spring-boot-master/readme.adoc | 4 +-
.../camel-example-spring-boot-pojo/README.adoc | 8 +-
.../README.adoc | 10 +--
.../README.adoc | 12 +--
.../readme.adoc | 4 +-
examples/camel-example-spring-boot-xml/readme.adoc | 10 +--
examples/camel-example-spring-boot/readme.adoc | 14 ++--
.../README.adoc | 12 +--
.../README.adoc | 12 +--
examples/camel-example-telegram/README.adoc | 6 +-
.../readme.adoc | 8 +-
examples/camel-example-webhook/readme.adoc | 8 +-
1193 files changed, 10162 insertions(+), 10155 deletions(-)
diff --git a/archetypes/camel-archetype-spring-boot/src/main/resources/archetype-resources/readme.adoc b/archetypes/camel-archetype-spring-boot/src/main/resources/archetype-resources/readme.adoc
index 1fc8d6d..73d6e18 100644
--- a/archetypes/camel-archetype-spring-boot/src/main/resources/archetype-resources/readme.adoc
+++ b/archetypes/camel-archetype-spring-boot/src/main/resources/archetype-resources/readme.adoc
@@ -1,27 +1,27 @@
-== Camel Example Spring Boot
+= Camel Example Spring Boot
This example shows how to work with a simple Apache Camel application using Spring Boot.
The example generates messages using timer trigger, writes them to standard output.
-=== Camel routes
+== Camel routes
The Camel route is located in the `MyCamelRouter` class. In this class the route
starts from a timer, that triggers every 2nd second and calls a Spring Bean `MyBean`
which returns a message, that is routed to a stream endpoint which writes to standard output.
-=== Using Camel components
+== Using Camel components
Apache Camel provides 200+ components which you can use to integrate and route messages between many systems
and data formats. To use any of these Camel components, add the component as a dependency to your project.
-=== How to run
+== How to run
You can run this example using
mvn spring-boot:run
-=== To get info about the routes
+== To get info about the routes
To show a summary of all the routes
@@ -36,7 +36,7 @@ curl -XGET -s http://localhost:8080/camelroutes/{id}/detail
----
-=== More information
+== More information
You can find more information about Apache Camel at the website: http://camel.apache.org/
diff --git a/components/camel-activemq/src/main/docs/activemq-component.adoc b/components/camel-activemq/src/main/docs/activemq-component.adoc
index 13784cb..ab5fc9a 100644
--- a/components/camel-activemq/src/main/docs/activemq-component.adoc
+++ b/components/camel-activemq/src/main/docs/activemq-component.adoc
@@ -1,5 +1,5 @@
[[activemq-component]]
-== ActiveMQ Component
+= ActiveMQ Component
*Available as of Camel version 1.0*
@@ -26,7 +26,7 @@ for this component:
</dependency>
------------------------------------------------------------
-=== URI format
+== URI format
--------------------------------------------
activemq:[queue:|topic:]destinationName[?options]
@@ -41,7 +41,7 @@ activemq:foo
-----------
-=== Component options
+== Component options
// component options: START
The ActiveMQ component supports 85 options, which are listed below.
@@ -139,7 +139,7 @@ The ActiveMQ component supports 85 options, which are listed below.
|===
// component options: END
-=== Endpoint options
+== Endpoint options
// endpoint options: START
@@ -151,7 +151,7 @@ activemq:destinationType:destinationName
with the following path and query parameters:
-==== Path Parameters (2 parameters):
+=== Path Parameters (2 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -162,7 +162,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (92 parameters):
+=== Query Parameters (92 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -264,7 +264,7 @@ with the following path and query parameters:
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
diff --git a/components/camel-ahc-ws/src/main/docs/ahc-ws-component.adoc b/components/camel-ahc-ws/src/main/docs/ahc-ws-component.adoc
index b7f34ae..07d6e55 100644
--- a/components/camel-ahc-ws/src/main/docs/ahc-ws-component.adoc
+++ b/components/camel-ahc-ws/src/main/docs/ahc-ws-component.adoc
@@ -1,5 +1,5 @@
[[ahc-ws-component]]
-== AHC Websocket Component
+= AHC Websocket Component
*Available as of Camel version 2.14*
@@ -25,7 +25,7 @@ their `pom.xml` for this component:
</dependency>
------------------------------------------------------------
-### URI Format
+== URI Format
[source,java]
-------------------------------------------------
@@ -35,7 +35,7 @@ ahc-wss://hostname[:port][/resourceUri][?options]
Will by default use port 80 for ahc-ws and 443 for ahc-wss.
-### AHC-WS Options
+== AHC-WS Options
As the AHC-WS component is based on the AHC component, you can use the
various configuration options of the AHC component.
@@ -74,7 +74,7 @@ ahc-ws:httpUri
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -84,7 +84,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (17 parameters):
+=== Query Parameters (17 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -110,7 +110,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -147,13 +147,13 @@ The component supports 10 options, which are listed below.
-### Writing and Reading Data over Websocket
+== Writing and Reading Data over Websocket
An ahc-ws endpoint can either write data to the socket or read from the
socket, depending on whether the endpoint is configured as the producer
or the consumer, respectively.
-### Configuring URI to Write or Read Data
+== Configuring URI to Write or Read Data
In the route below, Camel will write to the specified websocket
connection.
@@ -199,7 +199,7 @@ And the equivalent Spring sample:
-### See Also
+== See Also
* Configuring Camel
* Component
diff --git a/components/camel-ahc/src/main/docs/ahc-component.adoc b/components/camel-ahc/src/main/docs/ahc-component.adoc
index 21150cb..80e4f8d 100644
--- a/components/camel-ahc/src/main/docs/ahc-component.adoc
+++ b/components/camel-ahc/src/main/docs/ahc-component.adoc
@@ -1,5 +1,5 @@
[[ahc-component]]
-== AHC Component
+= AHC Component
*Available as of Camel version 2.8*
@@ -23,7 +23,7 @@ for this component:
</dependency>
------------------------------------------------------------
-### URI format
+== URI format
[source,java]
---------------------------------------------------
@@ -36,7 +36,7 @@ Will by default use port 80 for HTTP and 443 for HTTPS.
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-### Ahc Endpoint Options
+== Ahc Endpoint Options
@@ -53,7 +53,7 @@ ahc:httpUri
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -63,7 +63,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (15 parameters):
+=== Query Parameters (15 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -87,7 +87,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -130,7 +130,7 @@ The component supports 10 options, which are listed below.
-### AhcComponent Options
+== AhcComponent Options
@@ -174,7 +174,7 @@ propagate those options to
configure/override a custom option. Options set on endpoints will always
take precedence over options from the `AhcComponent`.
-### Message Headers
+== Message Headers
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -200,14 +200,14 @@ a content type, such as `text/html`.
provide a content encoding, such as `gzip`.
|=======================================================================
-### Message Body
+== Message Body
Camel will store the HTTP response from the external server on the OUT
body. All headers from the IN message will be copied to the OUT message,
so headers are preserved during routing. Additionally Camel will add the
HTTP response headers as well to the OUT message headers.
-### Response code
+== Response code
Camel will handle according to the HTTP response code:
@@ -225,7 +225,7 @@ The option, `throwExceptionOnFailure`, can be set to `false` to prevent
the `AhcOperationFailedException` from being thrown for failed response
codes. This allows you to get any response from the remote server.
-### AhcOperationFailedException
+== AhcOperationFailedException
This exception contains the following information:
@@ -235,7 +235,7 @@ This exception contains the following information:
* Response body as a `java.lang.String`, if server provided a body as
response
-### Calling using GET or POST
+== Calling using GET or POST
The following algorithm is used to determine if either `GET` or `POST`
HTTP method should be used: +
@@ -245,7 +245,7 @@ HTTP method should be used: +
4. `POST` if there is data to send (body is not null). +
5. `GET` otherwise.
-### Configuring URI to call
+== Configuring URI to call
You can set the HTTP producer's URI directly form the endpoint URI. In
the route below, Camel will call out to the external server, `oldhost`,
@@ -279,7 +279,7 @@ from("direct:start")
.to("ahc:http://oldhost");
-------------------------------------------------------------
-### Configuring URI Parameters
+== Configuring URI Parameters
The *ahc* producer supports URI parameters to be sent to the HTTP
server. The URI parameters can either be set directly on the endpoint
@@ -300,7 +300,7 @@ from("direct:start")
.to("ahc:http://oldhost");
-------------------------------------------------------------------------------
-### How to set the http method to the HTTP producer
+== How to set the http method to the HTTP producer
The HTTP component provides a way to set the HTTP request method by
setting the message header. Here is an example;
@@ -329,7 +329,7 @@ And the equivalent Spring sample:
</camelContext>
---------------------------------------------------------------------
-### Configuring charset
+== Configuring charset
If you are using `POST` to send data you can configure the `charset`
using the `Exchange` property:
@@ -339,7 +339,7 @@ using the `Exchange` property:
exchange.setProperty(Exchange.CHARSET_NAME, "iso-8859-1");
----------------------------------------------------------
-#### URI Parameters from the endpoint URI
+=== URI Parameters from the endpoint URI
In this sample we have the complete URI endpoint that is just what you
would have typed in a web browser. Multiple URI parameters can of course
@@ -352,7 +352,7 @@ web browser. Camel does no tricks here.
template.sendBody("ahc:http://www.google.com/search?q=Camel", null);
--------------------------------------------------------------------
-#### URI Parameters from the Message
+=== URI Parameters from the Message
[source,java]
---------------------------------------------------------------------
@@ -365,7 +365,7 @@ template.sendBody("ahc:http://www.google.com/search", null, headers);
In the header value above notice that it should *not* be prefixed with
`?` and you can separate parameters as usual with the `&` char.
-#### Getting the Response Code
+=== Getting the Response Code
You can get the HTTP response code from the AHC component by getting the
value from the Out message header with `Exchange.HTTP_RESPONSE_CODE`.
@@ -381,7 +381,7 @@ Exchange exchange = template.send("ahc:http://www.google.com/search", new Proces
int responseCode = out.getHeader(Exchange.HTTP_RESPONSE_CODE, Integer.class);
----------------------------------------------------------------------------------------------
-### Configuring AsyncHttpClient
+== Configuring AsyncHttpClient
The `AsyncHttpClient` client uses a `AsyncHttpClientConfig` to configure
the client. See the documentation at +
@@ -415,7 +415,7 @@ from("direct:start")
.to("ahc:http://localhost:8080/foo?clientConfig.maxRequestRetry=3&clientConfig.followRedirects=true")
---------------------------------------------------------------------------------------------------------
-### SSL Support (HTTPS)
+== SSL Support (HTTPS)
[[AHC-UsingtheJSSEConfigurationUtility]]
Using the JSSE Configuration Utility
@@ -467,7 +467,7 @@ Spring DSL based configuration of endpoint
...
----------------------------------------------------------------------------------
-### See Also
+== See Also
* Configuring Camel
* Component
diff --git a/components/camel-amqp/src/main/docs/amqp-component.adoc b/components/camel-amqp/src/main/docs/amqp-component.adoc
index c795f6f..9abe610 100644
--- a/components/camel-amqp/src/main/docs/amqp-component.adoc
+++ b/components/camel-amqp/src/main/docs/amqp-component.adoc
@@ -1,5 +1,5 @@
[[amqp-component]]
-== AMQP Component
+= AMQP Component
*Available as of Camel version 1.2*
@@ -20,14 +20,14 @@ for this component:
</dependency>
----
-### URI format
+== URI format
[source,java]
----
amqp:[queue:|topic:]destinationName[?options]
----
-### AMQP Options
+== AMQP Options
You can specify all of the various configuration options of the
xref:jms-component.adoc[JMS] component after the destination name.
@@ -141,7 +141,7 @@ amqp:destinationType:destinationName
with the following path and query parameters:
-==== Path Parameters (2 parameters):
+=== Path Parameters (2 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -152,7 +152,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (92 parameters):
+=== Query Parameters (92 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -253,7 +253,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -363,7 +363,7 @@ The component supports 81 options, which are listed below.
-### Usage
+== Usage
As AMQP component is inherited from JMS component, the usage of the
former is almost identical to the latter:
@@ -381,7 +381,7 @@ from(...).
to("amqp:topic:notify");
----
-### Configuring AMQP component
+== Configuring AMQP component
*Creating AMQP 1.0 component*
@@ -457,7 +457,7 @@ AMQPComponent amqp = AMQPComponent.amqpComponent("amqp://localhost:5672?amqp.tra
For reference take a look at the https://qpid.apache.org/releases/qpid-jms-0.29.0/docs/index.html[QPID JMS client configuration]
-### Using topics
+== Using topics
To have using topics working with `camel-amqp` you need to configure the
component to use `topic://` as topic prefix, as shown below:
@@ -478,7 +478,7 @@ Keep in mind that both `AMQPComponent#amqpComponent()` methods and
`AMQPConnectionDetails` pre-configure the component with the topic
prefix, so you don't have to configure it explicitly.
-### See Also
+== See Also
* Configuring Camel
* Component
diff --git a/components/camel-apns/src/main/docs/apns-component.adoc b/components/camel-apns/src/main/docs/apns-component.adoc
index a2fc2c3..64f4a17 100644
--- a/components/camel-apns/src/main/docs/apns-component.adoc
+++ b/components/camel-apns/src/main/docs/apns-component.adoc
@@ -1,5 +1,5 @@
[[apns-component]]
-== APNS Component
+= APNS Component
*Available as of Camel version 2.8*
@@ -31,7 +31,7 @@ for this component:
</dependency>
------------------------------------------------------------
-### URI format
+== URI format
To send notifications:
@@ -47,7 +47,7 @@ To consume feedback:
apns:consumer[?options]
-----------------------
-### Options
+== Options
@@ -77,7 +77,7 @@ apns:name
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -87,7 +87,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (22 parameters):
+=== Query Parameters (22 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -118,7 +118,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -152,7 +152,7 @@ The component supports 4 options, which are listed below.
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-#### Component
+=== Component
The `ApnsComponent` must be configured with a
`com.notnoop.apns.ApnsService`. The service can be created and
@@ -162,20 +162,20 @@ further below for an example. And as well in the
https://github.com/apache/camel/tree/master/components/camel-apns[test
source code].
-##### SSL Setting
+==== SSL Setting
In order to use secure connection, an instance of `org.apache.camel.support.jsse.SSLContextParameters`
should be injected to `org.apache.camel.component.apns.factory.ApnsServiceFactory` which is
used to configure the component. See the test resources for an example.
https://github.com/apache/camel/blob/master/components/camel-apns/src/test/resources/org/apache/camel/component/apns/spring/SpringApnsConsumerTest-context.xml[ssl example]
-### Exchange data format
+== Exchange data format
When Camel will fetch feedback data corresponding to inactive devices,
it will retrieve a List of InactiveDevice objects. Each InactiveDevice
object of the retrieved list will be setted as the In body, and then
processed by the consumer endpoint.
-### Message Headers
+== Message Headers
Camel Apns uses these headers.
@@ -190,7 +190,7 @@ onwards APNS_NOTIFICATION is used for sending message body as
com.notnoop.apns.ApnsNotification types.
|=======================================================================
-### ApnsServiceFactory builder callback
+== ApnsServiceFactory builder callback
`ApnsServiceFactory` comes with the empty callback method that could be
used to configure (or even replace) the default `ApnsServiceBuilder`
@@ -215,9 +215,9 @@ ApnsServiceFactory proxiedApnsServiceFactory = new ApnsServiceFactory(){
};
-------------------------------------------------------------------------------------------
-### Samples
+== Samples
-#### Camel Xml route
+=== Camel Xml route
[source,xml]
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
@@ -273,7 +273,7 @@ ApnsServiceFactory proxiedApnsServiceFactory = new ApnsServiceFactory(){
</beans>
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
-#### Camel Java route
+=== Camel Java route
[[APNS-Createcamelcontextanddeclareapnscomponentprogrammatically]]
Create camel context and declare apns component programmatically
@@ -338,7 +338,7 @@ from("apns:consumer?initialDelay=10&delay=3600&timeUnit=SECONDS")
.to("mock:result");
--------------------------------------------------------------------------
-### See Also
+== See Also
* http://camel.apache.org/component.html[Component]
* http://camel.apache.org/endpoint.html[Endpoint]
diff --git a/components/camel-as2/camel-as2-component/src/main/docs/as2-component.adoc b/components/camel-as2/camel-as2-component/src/main/docs/as2-component.adoc
index 4c61402..5083b02 100644
--- a/components/camel-as2/camel-as2-component/src/main/docs/as2-component.adoc
+++ b/components/camel-as2/camel-as2-component/src/main/docs/as2-component.adoc
@@ -1,5 +1,5 @@
[[as2-component]]
-== AS2 Component
+= AS2 Component
*Available as of Camel version 2.22*
@@ -21,7 +21,7 @@ for this component:
</dependency>
----
-=== URI format
+== URI format
[source]
----
@@ -34,7 +34,7 @@ apiName can be one of:
* server
-=== AS2 Options
+== AS2 Options
// component options: START
@@ -61,7 +61,7 @@ as2:apiName/methodName
with the following path and query parameters:
-==== Path Parameters (2 parameters):
+=== Path Parameters (2 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -72,7 +72,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (33 parameters):
+=== Query Parameters (33 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -114,7 +114,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -171,7 +171,7 @@ The component supports 31 options, which are listed below.
// spring-boot-auto-configure options: END
-=== Client Endpoints:
+== Client Endpoints:
Client endpoints use the endpoint prefix *`client`* followed by the name of a method
and associated options described next. The endpoint URI MUST contain the prefix *`client`*.
@@ -241,7 +241,7 @@ URI Options for _client_
|===
-=== Server Endpoints:
+== Server Endpoints:
Server endpoints use the endpoint prefix *`server`* followed by the name of a method
and associated options described next. The endpoint URI MUST contain the prefix *`server`*.
diff --git a/components/camel-asn1/src/main/docs/asn1-dataformat.adoc b/components/camel-asn1/src/main/docs/asn1-dataformat.adoc
index 4e1065a..991ab0d 100644
--- a/components/camel-asn1/src/main/docs/asn1-dataformat.adoc
+++ b/components/camel-asn1/src/main/docs/asn1-dataformat.adoc
@@ -1,11 +1,11 @@
[[asn1-dataformat]]
-== ASN.1 File DataFormat
+= ASN.1 File DataFormat
*Available as of Camel version 2.20*
The ASN.1 Data Format Data Format [Intoduction to ASN.1](https://www.itu.int/en/ITU-T/asn1/Pages/introduction.aspx) is a Camel Frameworks's data format implementation based on Bouncy Castle's bcprov-jdk15on library and jASN.1's java compiler for the formal notation used for describing data transmitted by telecommunications protocols, regardless of language implementation and physical representation of these data, whatever the application, whether complex or very simple. Messages can be u [...]
-### ASN.1 Data Format Options
+== ASN.1 Data Format Options
// dataformat options: START
The ASN.1 File dataformat supports 3 options, which are listed below.
@@ -21,7 +21,7 @@ The ASN.1 File dataformat supports 3 options, which are listed below.
|===
// dataformat options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -51,7 +51,7 @@ The component supports 4 options, which are listed below.
// spring-boot-auto-configure options: END
ND
-### Unmarshal
+== Unmarshal
There are 3 different ways to unmarshal ASN.1 structured messages. (Usually binary files)
@@ -85,7 +85,7 @@ from("direct:unmarshaldsl")
.to("mock:unmarshaldsl");
-----------------------------------------------------------------------
-### Dependencies
+== Dependencies
To use ASN.1 data format in your camel routes you need to add a dependency on
*camel-asn1* which implements this data format.
diff --git a/components/camel-asterisk/src/main/docs/asterisk-component.adoc b/components/camel-asterisk/src/main/docs/asterisk-component.adoc
index 3b6fdd8..3991823 100644
--- a/components/camel-asterisk/src/main/docs/asterisk-component.adoc
+++ b/components/camel-asterisk/src/main/docs/asterisk-component.adoc
@@ -1,5 +1,5 @@
[[asterisk-component]]
-== Asterisk Component
+= Asterisk Component
*Available as of Camel version 2.18*
@@ -20,14 +20,14 @@ for this component:
</dependency>
------------------------------------------------------------
-### URI format
+== URI format
[source,java]
-------------------------------------------------------------------------------------------------------------------------
asterisk:name[?options]
-------------------------------------------------------------------------------------------------------------------------
-### Options
+== Options
// component options: START
The Asterisk component supports 2 options, which are listed below.
@@ -51,7 +51,7 @@ asterisk:name
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -61,7 +61,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (10 parameters):
+=== Query Parameters (10 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -80,7 +80,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -109,7 +109,7 @@ The component supports 3 options, which are listed below.
// spring-boot-auto-configure options: END
-### Action
+== Action
Supported actions are:
* QUEUE_STATUS, Queue Status
diff --git a/components/camel-atmos/src/main/docs/atmos-component.adoc b/components/camel-atmos/src/main/docs/atmos-component.adoc
index 17aa6fc..6593aef 100644
--- a/components/camel-atmos/src/main/docs/atmos-component.adoc
+++ b/components/camel-atmos/src/main/docs/atmos-component.adoc
@@ -1,5 +1,5 @@
[[atmos-component]]
-== Atmos Component
+= Atmos Component
*Available as of Camel version 2.15*
@@ -12,7 +12,7 @@ https://github.com/emcvipr/dataservices-sdk-java[Atmos Client].
from("atmos:foo/get?remotePath=/path").to("mock:test");
-------------------------------
-### Options
+== Options
// component options: START
@@ -43,7 +43,7 @@ atmos:name/operation
with the following path and query parameters:
-==== Path Parameters (2 parameters):
+=== Path Parameters (2 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -54,7 +54,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (14 parameters):
+=== Query Parameters (14 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -77,7 +77,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -111,7 +111,7 @@ The component supports 7 options, which are listed below.
-### Dependencies
+== Dependencies
To use Atmos in your camel routes you need to add the dependency
on *camel-atmos* which implements this data format.
@@ -132,7 +132,7 @@ the download page for the latest versions).
[[Atmos-Integrations]]
-### Integrations
+== Integrations
When you look at atmos integrations, there is one type of consumer,
GetConsumer, which is a type of ScheduledPollConsumer.
@@ -146,7 +146,7 @@ Whereas there are 4 types of producers which are
* `Move`
* `Put`
-### Examples
+== Examples
These example are taken from tests:
@@ -182,7 +182,7 @@ exhange
DOWNLOADED_FILE, DOWNLOADED_FILES, UPLOADED_FILE, UPLOADED_FILES, FOUND_FILES, DELETED_PATH, MOVED_PATH;
-------------------------------
-### See Also
+== See Also
* Configuring Camel
* Component
diff --git a/components/camel-atmosphere-websocket/src/main/docs/atmosphere-websocket-component.adoc b/components/camel-atmosphere-websocket/src/main/docs/atmosphere-websocket-component.adoc
index 216189e..0bc2824 100644
--- a/components/camel-atmosphere-websocket/src/main/docs/atmosphere-websocket-component.adoc
+++ b/components/camel-atmosphere-websocket/src/main/docs/atmosphere-websocket-component.adoc
@@ -1,5 +1,5 @@
[[atmosphere-websocket-component]]
-== Atmosphere Websocket Component
+= Atmosphere Websocket Component
*Available as of Camel version 2.14*
@@ -30,7 +30,7 @@ their `pom.xml` for this component:
</dependency>
------------------------------------------------------------
-### Atmosphere-Websocket Options
+== Atmosphere-Websocket Options
@@ -67,7 +67,7 @@ atmosphere-websocket:servicePath
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -77,7 +77,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (25 parameters):
+=== Query Parameters (25 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -111,7 +111,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -149,20 +149,20 @@ The component supports 11 options, which are listed below.
-### URI Format
+== URI Format
[source,java]
-----------------------------------------------
atmosphere-websocket:///relative path[?options]
-----------------------------------------------
-### Reading and Writing Data over Websocket
+== Reading and Writing Data over Websocket
An atmopshere-websocket endpoint can either write data to the socket or
read from the socket, depending on whether the endpoint is configured as
the producer or the consumer, respectively.
-### Configuring URI to Read or Write Data
+== Configuring URI to Read or Write Data
In the route below, Camel will read from the specified websocket
connection.
@@ -208,7 +208,7 @@ And the equivalent Spring sample:
-### See Also
+== See Also
* Configuring Camel
* Component
diff --git a/components/camel-atom/src/main/docs/atom-component.adoc b/components/camel-atom/src/main/docs/atom-component.adoc
index a6311bc..0dac79b 100644
--- a/components/camel-atom/src/main/docs/atom-component.adoc
+++ b/components/camel-atom/src/main/docs/atom-component.adoc
@@ -1,5 +1,5 @@
[[atom-component]]
-== Atom Component
+= Atom Component
*Available as of Camel version 1.2*
@@ -22,7 +22,7 @@ for this component:
</dependency>
------------------------------------------------------------
-### URI format
+== URI format
[source,java]
------------------------
@@ -31,7 +31,7 @@ atom://atomUri[?options]
Where *atomUri* is the URI to the Atom feed to poll.
-### Options
+== Options
// component options: START
@@ -58,7 +58,7 @@ atom:feedUri
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -68,7 +68,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (28 parameters):
+=== Query Parameters (28 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -105,7 +105,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -138,7 +138,7 @@ The component supports 3 options, which are listed below.
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-### Exchange data format
+== Exchange data format
Camel will set the In body on the returned `Exchange` with the entries.
Depending on the `splitEntries` flag Camel will either return one
@@ -157,7 +157,7 @@ Depending on the `splitEntries` flag Camel will either return one
Camel can set the `Feed` object on the In header (see `feedHeader`
option to disable this):
-### Message Headers
+== Message Headers
Camel atom uses these headers.
@@ -168,7 +168,7 @@ Camel atom uses these headers.
header.
|=======================================================================
-### Samples
+== Samples
In this sample we poll James Strachan's blog.
@@ -181,7 +181,7 @@ In this sample we want to filter only good blogs we like to a SEDA
queue. The sample also shows how to setup Camel standalone, not running
in any Container or using Spring.
-### See Also
+== See Also
* Configuring Camel
* Component
diff --git a/components/camel-atomix/src/main/docs/atomix-map-component.adoc b/components/camel-atomix/src/main/docs/atomix-map-component.adoc
index 472bd6a..1455e7b 100644
--- a/components/camel-atomix/src/main/docs/atomix-map-component.adoc
+++ b/components/camel-atomix/src/main/docs/atomix-map-component.adoc
@@ -1,5 +1,5 @@
[[atomix-map-component]]
-== Atomix Map Component
+= Atomix Map Component
*Available as of Camel version 2.20*
@@ -16,14 +16,14 @@ Maven users will need to add the following dependency to their pom.xml for this
</dependency>
----
-### URI format
+== URI format
[source,java]
----
atomix-map:mapName
----
-### Options
+== Options
// component options: START
The Atomix Map component supports 6 options, which are listed below.
@@ -51,7 +51,7 @@ atomix-map:resourceName
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -61,7 +61,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (20 parameters):
+=== Query Parameters (20 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -90,7 +90,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -126,7 +126,7 @@ The component supports 10 options, which are listed below.
// spring-boot-auto-configure options: END
-### Headers
+== Headers
[width="100%",cols="10%,10%,20%a,60%",options="header",]
|===
@@ -181,7 +181,7 @@ The component supports 10 options, which are listed below.
|===
-### Configuring the component to connect to an Atomix cluster
+== Configuring the component to connect to an Atomix cluster
The nodes of the Atomix cluster you want to join can be se at Endpoint or component level (recommended), below some examples:
@@ -215,7 +215,7 @@ The nodes of the Atomix cluster you want to join can be se at Endpoint or compon
</beans>
----
-### Usage examples:
+== Usage examples:
* *PUT an element with TTL of 1 second:*
+
diff --git a/components/camel-atomix/src/main/docs/atomix-messaging-component.adoc b/components/camel-atomix/src/main/docs/atomix-messaging-component.adoc
index 296036c..8f40140 100644
--- a/components/camel-atomix/src/main/docs/atomix-messaging-component.adoc
+++ b/components/camel-atomix/src/main/docs/atomix-messaging-component.adoc
@@ -1,5 +1,5 @@
[[atomix-messaging-component]]
-== Atomix Messaging Component
+= Atomix Messaging Component
*Available as of Camel version 2.20*
@@ -17,7 +17,7 @@ for this component:
</dependency>
----
-### URI format
+== URI format
[source,java]
----
@@ -50,7 +50,7 @@ atomix-messaging:resourceName
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -60,7 +60,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (21 parameters):
+=== Query Parameters (21 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -90,7 +90,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
diff --git a/components/camel-atomix/src/main/docs/atomix-multimap-component.adoc b/components/camel-atomix/src/main/docs/atomix-multimap-component.adoc
index 7c97c8b..f274b0f 100644
--- a/components/camel-atomix/src/main/docs/atomix-multimap-component.adoc
+++ b/components/camel-atomix/src/main/docs/atomix-multimap-component.adoc
@@ -1,5 +1,5 @@
[[atomix-multimap-component]]
-== Atomix MultiMap Component
+= Atomix MultiMap Component
*Available as of Camel version 2.20*
@@ -17,7 +17,7 @@ for this component:
</dependency>
----
-### URI format
+== URI format
[source,java]
----
@@ -50,7 +50,7 @@ atomix-multimap:resourceName
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -60,7 +60,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (19 parameters):
+=== Query Parameters (19 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -88,7 +88,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
diff --git a/components/camel-atomix/src/main/docs/atomix-queue-component.adoc b/components/camel-atomix/src/main/docs/atomix-queue-component.adoc
index ca208b5..4cde18f 100644
--- a/components/camel-atomix/src/main/docs/atomix-queue-component.adoc
+++ b/components/camel-atomix/src/main/docs/atomix-queue-component.adoc
@@ -1,5 +1,5 @@
[[atomix-queue-component]]
-== Atomix Queue Component
+= Atomix Queue Component
*Available as of Camel version 2.20*
@@ -17,7 +17,7 @@ for this component:
</dependency>
----
-### URI format
+== URI format
[source,java]
----
@@ -50,7 +50,7 @@ atomix-queue:resourceName
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -60,7 +60,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (18 parameters):
+=== Query Parameters (18 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -87,7 +87,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
diff --git a/components/camel-atomix/src/main/docs/atomix-set-component.adoc b/components/camel-atomix/src/main/docs/atomix-set-component.adoc
index c4debae..22c436f 100644
--- a/components/camel-atomix/src/main/docs/atomix-set-component.adoc
+++ b/components/camel-atomix/src/main/docs/atomix-set-component.adoc
@@ -1,5 +1,5 @@
[[atomix-set-component]]
-== Atomix Set Component
+= Atomix Set Component
*Available as of Camel version 2.20*
@@ -17,7 +17,7 @@ for this component:
</dependency>
----
-### URI format
+== URI format
[source,java]
----
@@ -50,7 +50,7 @@ atomix-set:resourceName
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -60,7 +60,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (19 parameters):
+=== Query Parameters (19 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -88,7 +88,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
diff --git a/components/camel-atomix/src/main/docs/atomix-value-component.adoc b/components/camel-atomix/src/main/docs/atomix-value-component.adoc
index d33e10e..391dea3 100644
--- a/components/camel-atomix/src/main/docs/atomix-value-component.adoc
+++ b/components/camel-atomix/src/main/docs/atomix-value-component.adoc
@@ -1,5 +1,5 @@
[[atomix-value-component]]
-== Atomix Value Component
+= Atomix Value Component
*Available as of Camel version 2.20*
@@ -17,7 +17,7 @@ for this component:
</dependency>
----
-### URI format
+== URI format
[source,java]
----
@@ -50,7 +50,7 @@ atomix-value:resourceName
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -60,7 +60,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (19 parameters):
+=== Query Parameters (19 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -88,7 +88,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
diff --git a/components/camel-avro/src/main/docs/avro-component.adoc b/components/camel-avro/src/main/docs/avro-component.adoc
index 66a2361..ab06fb9 100644
--- a/components/camel-avro/src/main/docs/avro-component.adoc
+++ b/components/camel-avro/src/main/docs/avro-component.adoc
@@ -1,5 +1,5 @@
[[avro-component]]
-== Avro Component
+= Avro Component
*Available as of Camel version 2.10*
@@ -22,7 +22,7 @@ for this component:
</dependency>
------------------------------------------------------------
-### Apache Avro Overview
+== Apache Avro Overview
Avro allows you to define message types and a protocol using a json like
format and then generate java code for the specified types and messages.
@@ -89,7 +89,7 @@ class Value {
_Note: Existing classes can be used only for RPC (see below), not in
data format._
-### Using the Avro data format
+== Using the Avro data format
Using the avro data format is as easy as specifying that the class that
you want to marshal or unmarshal in your route.
@@ -126,7 +126,7 @@ reference it from your route.
In the same manner you can umarshal using the avro data format.
-### Using Avro RPC in Camel
+== Using Avro RPC in Camel
As mentioned above Avro also provides RPC support over multiple
transports such as http and netty. Camel provides consumers and
@@ -165,7 +165,7 @@ got only one parameter, *since 2.12* you can use `singleParameter` URI
option to receive it direcly in the "in" message body without array
wrapping.
-### Avro RPC URI Options
+== Avro RPC URI Options
@@ -199,7 +199,7 @@ avro:transport:host:port/messageName
with the following path and query parameters:
-==== Path Parameters (4 parameters):
+=== Path Parameters (4 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -212,7 +212,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (12 parameters):
+=== Query Parameters (12 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -233,7 +233,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -276,7 +276,7 @@ The component supports 16 options, which are listed below.
-### Avro RPC Headers
+== Avro RPC Headers
[width="100%",cols="20%,80%",options="header",]
|=======================================================================
@@ -286,7 +286,7 @@ The component supports 16 options, which are listed below.
URI (if any)
|=======================================================================
-### Examples
+== Examples
An example of using camel avro producers via http:
diff --git a/components/camel-avro/src/main/docs/avro-dataformat.adoc b/components/camel-avro/src/main/docs/avro-dataformat.adoc
index 661874a..8de8899 100644
--- a/components/camel-avro/src/main/docs/avro-dataformat.adoc
+++ b/components/camel-avro/src/main/docs/avro-dataformat.adoc
@@ -1,5 +1,5 @@
[[avro-dataformat]]
-== Avro DataFormat
+= Avro DataFormat
*Available as of Camel version 2.14*
@@ -22,7 +22,7 @@ for this component:
</dependency>
------------------------------------------------------------
-### Apache Avro Overview
+== Apache Avro Overview
Avro allows you to define message types and a protocol using a json like
format and then generate java code for the specified types and messages.
@@ -89,7 +89,7 @@ class Value {
_Note: Existing classes can be used only for RPC (see below), not in
data format._
-### Using the Avro data format
+== Using the Avro data format
Using the avro data format is as easy as specifying that the class that
you want to marshal or unmarshal in your route.
@@ -127,7 +127,7 @@ reference it from your route.
In the same manner you can umarshal using the avro data format.
-### Avro Dataformat Options
+== Avro Dataformat Options
// dataformat options: START
The Avro dataformat supports 2 options, which are listed below.
@@ -142,7 +142,7 @@ The Avro dataformat supports 2 options, which are listed below.
|===
// dataformat options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
diff --git a/components/camel-aws-cw/src/main/docs/aws-cw-component.adoc b/components/camel-aws-cw/src/main/docs/aws-cw-component.adoc
index 03762ce..7f9dd0e 100644
--- a/components/camel-aws-cw/src/main/docs/aws-cw-component.adoc
+++ b/components/camel-aws-cw/src/main/docs/aws-cw-component.adoc
@@ -1,5 +1,5 @@
[[aws-cw-component]]
-== AWS CloudWatch Component
+= AWS CloudWatch Component
*Available as of Camel version 2.11*
@@ -14,7 +14,7 @@ You must have a valid Amazon Web Services developer account, and be
signed up to use Amazon CloudWatch. More information is available at
https://aws.amazon.com/cloudwatch/[Amazon CloudWatch].
-### URI Format
+== URI Format
[source,java]
----------------------------
@@ -25,7 +25,7 @@ The metrics will be created if they don't already exists. +
You can append query options to the URI in the following format,
`?options=value&option2=value&...`
-### URI Options
+== URI Options
// component options: START
@@ -57,7 +57,7 @@ aws-cw:namespace
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -67,7 +67,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (13 parameters):
+=== Query Parameters (13 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -89,7 +89,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -140,9 +140,9 @@ You have to provide the amazonCwClient in the
Registry or your accessKey and secretKey to access
the https://aws.amazon.com/cloudwatch/[Amazon's CloudWatch].
-### Usage
+== Usage
-#### Message headers evaluated by the CW producer
+=== Message headers evaluated by the CW producer
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -165,7 +165,7 @@ the https://aws.amazon.com/cloudwatch/[Amazon's CloudWatch].
|`CamelAwsCwMetricDimensions` |`Map<String, String>` |A map of dimension names and dimension values.
|=======================================================================
-#### Advanced AmazonCloudWatch configuration
+=== Advanced AmazonCloudWatch configuration
If you need more control over the `AmazonCloudWatch` instance
configuration you can create your own instance and refer to it from the
@@ -194,13 +194,13 @@ AmazonCloudWatch client = new AmazonCloudWatchClient(awsCredentials, clientConfi
registry.bind("client", client);
------------------------------------------------------------------------------------------
-### Automatic detection of AmazonCloudWatch client in registry
+== Automatic detection of AmazonCloudWatch client in registry
The component is capable of detecting the presence of an AmazonCloudWatch bean into the registry.
If it's the only instance of that type it will be used as client and you won't have to define it as uri parameter.
This may be really useful for smarter configuration of the endpoint.
-### Dependencies
+== Dependencies
Maven users will need to add the following dependency to their pom.xml.
@@ -217,7 +217,7 @@ Maven users will need to add the following dependency to their pom.xml.
where `${camel-version`} must be replaced by the actual version of Camel.
-### See Also
+== See Also
* Configuring Camel
* Component
diff --git a/components/camel-aws-ddb/src/main/docs/aws-ddb-component.adoc b/components/camel-aws-ddb/src/main/docs/aws-ddb-component.adoc
index 8c74729..676fd70 100644
--- a/components/camel-aws-ddb/src/main/docs/aws-ddb-component.adoc
+++ b/components/camel-aws-ddb/src/main/docs/aws-ddb-component.adoc
@@ -1,5 +1,5 @@
[[aws-ddb-component]]
-== AWS DynamoDB Component
+= AWS DynamoDB Component
*Available as of Camel version 2.10*
@@ -12,7 +12,7 @@ You must have a valid Amazon Web Services developer account, and be
signed up to use Amazon DynamoDB. More information is available at
https://aws.amazon.com/dynamodb[Amazon DynamoDB].
-### URI Format
+== URI Format
[source,java]
------------------------------
@@ -22,7 +22,7 @@ aws-ddb://domainName[?options]
You can append query options to the URI in the following format,
?options=value&option2=value&...
-### URI Options
+== URI Options
// component options: START
@@ -54,7 +54,7 @@ aws-ddb:tableName
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -64,7 +64,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (15 parameters):
+=== Query Parameters (15 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -88,7 +88,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -141,9 +141,9 @@ You have to provide the amazonDDBClient in the
Registry or your accessKey and secretKey to access
the https://aws.amazon.com/dynamodb[Amazon's DynamoDB].
-### Usage
+== Usage
-#### Message headers evaluated by the DDB producer
+=== Message headers evaluated by the DDB producer
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -196,7 +196,7 @@ the query.
|`CamelAwsDdbUpdateValues` |`Map<String, AttributeValueUpdate>` |Map of attribute name to the new value and action for the update.
|=======================================================================
-#### Message headers set during BatchGetItems operation
+=== Message headers set during BatchGetItems operation
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -208,7 +208,7 @@ the query.
processed with the current response.
|=======================================================================
-#### Message headers set during DeleteItem operation
+=== Message headers set during DeleteItem operation
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -217,7 +217,7 @@ processed with the current response.
|`CamelAwsDdbAttributes` |`Map<String, AttributeValue>` |The list of attributes returned by the operation.
|=======================================================================
-#### Message headers set during DeleteTable operation
+=== Message headers set during DeleteTable operation
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -241,7 +241,7 @@ processed with the current response.
|`CamelAwsDdbTableStatus` |`String` |The status of the table: CREATING, UPDATING, DELETING, ACTIVE
|=======================================================================
-#### Message headers set during DescribeTable operation
+=== Message headers set during DescribeTable operation
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -267,7 +267,7 @@ processed with the current response.
|`CamelAwsDdbWriteCapacity` |`Long` |WriteCapacityUnits property of this table.
|=======================================================================
-#### Message headers set during GetItem operation
+=== Message headers set during GetItem operation
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -277,7 +277,7 @@ processed with the current response.
|=======================================================================
-#### Message headers set during PutItem operation
+=== Message headers set during PutItem operation
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -287,7 +287,7 @@ processed with the current response.
|=======================================================================
-#### Message headers set during Query operation
+=== Message headers set during Query operation
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -304,7 +304,7 @@ consumed during the operation.
|`CamelAwsDdbCount` |`Integer` |Number of items in the response.
|=======================================================================
-#### Message headers set during Scan operation
+=== Message headers set during Scan operation
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -323,7 +323,7 @@ consumed during the operation.
|`CamelAwsDdbScannedCount` |`Integer` |Number of items in the complete scan before any filters are applied.
|=======================================================================
-#### Message headers set during UpdateItem operation
+=== Message headers set during UpdateItem operation
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -333,7 +333,7 @@ consumed during the operation.
|=======================================================================
-#### Advanced AmazonDynamoDB configuration
+=== Advanced AmazonDynamoDB configuration
If you need more control over the `AmazonDynamoDB` instance
configuration you can create your own instance and refer to it from the
@@ -362,13 +362,13 @@ AmazonDynamoDB client = new AmazonDynamoDBClient(awsCredentials, clientConfigura
registry.bind("client", client);
--------------------------------------------------------------------------------------
-### Automatic detection of AmazonDynamoDB client in registry
+== Automatic detection of AmazonDynamoDB client in registry
The component is capable of detecting the presence of an AmazonDynamoDB bean into the registry.
If it's the only instance of that type it will be used as client and you won't have to define it as uri parameter.
This may be really useful for smarter configuration of the endpoint.
-### Dependencies
+== Dependencies
Maven users will need to add the following dependency to their pom.xml.
@@ -385,7 +385,7 @@ Maven users will need to add the following dependency to their pom.xml.
where `$\{camel-version\}` must be replaced by the actual version of Camel.
-### See Also
+== See Also
* Configuring Camel
* Component
diff --git a/components/camel-aws-ddb/src/main/docs/aws-ddbstream-component.adoc b/components/camel-aws-ddb/src/main/docs/aws-ddbstream-component.adoc
index c8d85f9..1c522fe 100644
--- a/components/camel-aws-ddb/src/main/docs/aws-ddbstream-component.adoc
+++ b/components/camel-aws-ddb/src/main/docs/aws-ddbstream-component.adoc
@@ -1,5 +1,5 @@
[[aws-ddbstream-component]]
-== AWS DynamoDB Streams Component
+= AWS DynamoDB Streams Component
*Available as of Camel version 2.17*
@@ -12,7 +12,7 @@ You must have a valid Amazon Web Services developer account, and be
signed up to use Amazon DynamoDB Streams. More information are available
at https://aws.amazon.com/dynamodb/[AWS DynamoDB]
-### URI Format
+== URI Format
[source,java]
------------------------------------
@@ -23,7 +23,7 @@ The stream needs to be created prior to it being used. +
You can append query options to the URI in the following format,
?options=value&option2=value&...
-### URI Options
+== URI Options
// component options: START
@@ -57,7 +57,7 @@ aws-ddbstream:tableName
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -67,7 +67,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (29 parameters):
+=== Query Parameters (29 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -105,7 +105,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -157,7 +157,7 @@ You have to provide the amazonDynamoDbStreamsClient in the
Registry with proxies and relevant credentials
configured.
-### Sequence Numbers
+== Sequence Numbers
You can provide a literal string as the sequence number or provide a
bean in the registry. An example of using the bean would be to save your
@@ -167,7 +167,7 @@ It is an error to provide a sequence number that is greater than the
largest sequence number in the describe-streams result, as this will
lead to the AWS call returning an HTTP 400.
-### Batch Consumer
+== Batch Consumer
This component implements the Batch Consumer.
@@ -175,9 +175,9 @@ This allows you for instance to know how many messages exists in this
batch and for instance let the Aggregator
aggregate this number of messages.
-### Usage
+== Usage
-#### AmazonDynamoDBStreamsClient configuration
+=== AmazonDynamoDBStreamsClient configuration
You will need to create an instance of AmazonDynamoDBStreamsClient and
bind it to the registry
@@ -195,7 +195,7 @@ region.createClient(AmazonDynamoDBStreamsClient.class, null, clientConfiguration
registry.bind("kinesisClient", client);
--------------------------------------------------------------------------------------------------------------------
-#### Providing AWS Credentials
+=== Providing AWS Credentials
It is recommended that the credentials are obtained by using the
http://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/auth/DefaultAWSCredentialsProviderChain.html[DefaultAWSCredentialsProviderChain]
@@ -204,9 +204,9 @@ however, a
different http://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/auth/AWSCredentialsProvider.html[AWSCredentialsProvider]
can be specified when calling createClient(...).
-### Coping with Downtime
+== Coping with Downtime
-#### AWS DynamoDB Streams outage of less than 24 hours
+=== AWS DynamoDB Streams outage of less than 24 hours
The consumer will resume from the last seen sequence number (as
implemented
@@ -214,18 +214,18 @@ for https://issues.apache.org/jira/browse/CAMEL-9515[CAMEL-9515]), so
you should receive a flood of events in quick succession, as long as the
outage did not also include DynamoDB itself.
-#### AWS DynamoDB Streams outage of more than 24 hours
+=== AWS DynamoDB Streams outage of more than 24 hours
Given that AWS only retain 24 hours worth of changes, you will have
missed change events no matter what mitigations are in place.
-### Automatic detection of AmazonDynamoDBStreams client in registry
+== Automatic detection of AmazonDynamoDBStreams client in registry
The component is capable of detecting the presence of an AmazonDynamoDBStreams bean into the registry.
If it's the only instance of that type it will be used as client and you won't have to define it as uri parameter.
This may be really useful for smarter configuration of the endpoint.
-### Dependencies
+== Dependencies
Maven users will need to add the following dependency to their pom.xml.
@@ -242,7 +242,7 @@ Maven users will need to add the following dependency to their pom.xml.
where `$\{camel-version\}` must be replaced by the actual version of Camel.
-### See Also
+== See Also
* Configuring Camel
* Component
diff --git a/components/camel-aws-ec2/src/main/docs/aws-ec2-component.adoc b/components/camel-aws-ec2/src/main/docs/aws-ec2-component.adoc
index b1ab7c9..9767ffa 100644
--- a/components/camel-aws-ec2/src/main/docs/aws-ec2-component.adoc
+++ b/components/camel-aws-ec2/src/main/docs/aws-ec2-component.adoc
@@ -1,5 +1,5 @@
[[aws-ec2-component]]
-== AWS EC2 Component
+= AWS EC2 Component
*Available as of Camel version 2.16*
@@ -12,7 +12,7 @@ You must have a valid Amazon Web Services developer account, and be
signed up to use Amazon EC2. More information is available at
https://aws.amazon.com/ec2/[Amazon EC2].
-### URI Format
+== URI Format
[source,java]
-------------------------
@@ -22,7 +22,7 @@ aws-ec2://label[?options]
You can append query options to the URI in the following format,
?options=value&option2=value&...
-### URI Options
+== URI Options
// component options: START
@@ -54,7 +54,7 @@ aws-ec2:label
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -64,7 +64,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (10 parameters):
+=== Query Parameters (10 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -83,7 +83,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -130,9 +130,9 @@ You have to provide the amazonEc2Client in the
Registry or your accessKey and secretKey to access
the https://aws.amazon.com/ec2/[Amazon EC2] service.
-### Usage
+== Usage
-#### Message headers evaluated by the EC2 producer
+=== Message headers evaluated by the EC2 producer
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -160,7 +160,7 @@ terminate operations on.
|`CamelAwsEC2InstancesTags` |`Collection` |A collection of tags to add or remove from EC2 resources
|=======================================================================
-### Automatic detection of AmazonEC2 client in registry
+== Automatic detection of AmazonEC2 client in registry
The component is capable of detecting the presence of an AmazonEC2 bean into the registry.
If it's the only instance of that type it will be used as client and you won't have to define it as uri parameter.
@@ -183,7 +183,7 @@ Maven users will need to add the following dependency to their pom.xml.
where `$\{camel-version\}` must be replaced by the actual version of Camel.
-### See Also
+== See Also
* Configuring Camel
* Component
diff --git a/components/camel-aws-ecs/src/main/docs/aws-ecs-component.adoc b/components/camel-aws-ecs/src/main/docs/aws-ecs-component.adoc
index 928aa24..77183ff 100644
--- a/components/camel-aws-ecs/src/main/docs/aws-ecs-component.adoc
+++ b/components/camel-aws-ecs/src/main/docs/aws-ecs-component.adoc
@@ -1,5 +1,5 @@
[[aws-ecs-component]]
-== AWS ECS Component
+= AWS ECS Component
*Available as of Camel version 3.0*
@@ -12,7 +12,7 @@ You must have a valid Amazon Web Services developer account, and be
signed up to use Amazon ECS. More information is available at
https://aws.amazon.com/ecs/[Amazon ECS].
-### URI Format
+== URI Format
[source,java]
-------------------------
@@ -22,7 +22,7 @@ aws-ecs://label[?options]
You can append query options to the URI in the following format,
?options=value&option2=value&...
-### URI Options
+== URI Options
// component options: START
@@ -54,7 +54,7 @@ aws-ecs:label
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -64,7 +64,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (10 parameters):
+=== Query Parameters (10 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -83,7 +83,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -130,9 +130,9 @@ You have to provide the amazonECSClient in the
Registry or your accessKey and secretKey to access
the https://aws.amazon.com/ecs/[Amazon ECS] service.
-### Usage
+== Usage
-#### Message headers evaluated by the ECS producer
+=== Message headers evaluated by the ECS producer
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -145,7 +145,7 @@ the https://aws.amazon.com/ecs/[Amazon ECS] service.
|`CamelAwsECSClusterName` |`String` |The cluster name
|=======================================================================
-#### ECS Producer operations
+=== ECS Producer operations
Camel-AWS ECS component provides the following operation on the producer side:
@@ -154,7 +154,7 @@ Camel-AWS ECS component provides the following operation on the producer side:
- describeCluster
- deleteCluster
-### Automatic detection of AmazonECS client in registry
+== Automatic detection of AmazonECS client in registry
The component is capable of detecting the presence of an AmazonECS bean into the registry.
If it's the only instance of that type it will be used as client and you won't have to define it as uri parameter.
@@ -177,7 +177,7 @@ Maven users will need to add the following dependency to their pom.xml.
where `$\{camel-version\}` must be replaced by the actual version of Camel.
-### See Also
+== See Also
* Configuring Camel
* Component
diff --git a/components/camel-aws-eks/src/main/docs/aws-eks-component.adoc b/components/camel-aws-eks/src/main/docs/aws-eks-component.adoc
index a33a1ff..301d948 100644
--- a/components/camel-aws-eks/src/main/docs/aws-eks-component.adoc
+++ b/components/camel-aws-eks/src/main/docs/aws-eks-component.adoc
@@ -1,5 +1,5 @@
[[aws-eks-component]]
-== AWS EKS Component
+= AWS EKS Component
*Available as of Camel version 3.0*
@@ -12,7 +12,7 @@ You must have a valid Amazon Web Services developer account, and be
signed up to use Amazon EKS. More information is available at
https://aws.amazon.com/eks/[Amazon EKS].
-### URI Format
+== URI Format
[source,java]
-------------------------
@@ -22,7 +22,7 @@ aws-eks://label[?options]
You can append query options to the URI in the following format,
?options=value&option2=value&...
-### URI Options
+== URI Options
// component options: START
@@ -54,7 +54,7 @@ aws-eks:label
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -64,7 +64,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (10 parameters):
+=== Query Parameters (10 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -83,7 +83,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -130,9 +130,9 @@ You have to provide the amazonEKSClient in the
Registry or your accessKey and secretKey to access
the https://aws.amazon.com/eks/[Amazon EKS] service.
-### Usage
+== Usage
-#### Message headers evaluated by the EKS producer
+=== Message headers evaluated by the EKS producer
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -151,7 +151,7 @@ the https://aws.amazon.com/eks/[Amazon EKS] service.
|`CamelAwsEKSVPCConfig` |`VPCConfigRequest` |The VPC config for the creations of an EKS cluster
|=======================================================================
-#### EKS Producer operations
+=== EKS Producer operations
Camel-AWS EKS component provides the following operation on the producer side:
@@ -160,7 +160,7 @@ Camel-AWS EKS component provides the following operation on the producer side:
- describeCluster
- deleteCluster
-### Automatic detection of AmazonEKS client in registry
+== Automatic detection of AmazonEKS client in registry
The component is capable of detecting the presence of an AmazonEKS bean into the registry.
If it's the only instance of that type it will be used as client and you won't have to define it as uri parameter.
@@ -183,7 +183,7 @@ Maven users will need to add the following dependency to their pom.xml.
where `$\{camel-version\}` must be replaced by the actual version of Camel.
-### See Also
+== See Also
* Configuring Camel
* Component
diff --git a/components/camel-aws-iam/src/main/docs/aws-iam-component.adoc b/components/camel-aws-iam/src/main/docs/aws-iam-component.adoc
index 4489a77..44b2559 100644
--- a/components/camel-aws-iam/src/main/docs/aws-iam-component.adoc
+++ b/components/camel-aws-iam/src/main/docs/aws-iam-component.adoc
@@ -1,5 +1,5 @@
[[aws-iam-component]]
-== AWS IAM Component
+= AWS IAM Component
*Available as of Camel version 2.23*
@@ -12,7 +12,7 @@ You must have a valid Amazon Web Services developer account, and be
signed up to use Amazon IAM. More information is available at
https://aws.amazon.com/iam/[Amazon IAM].
-### URI Format
+== URI Format
[source,java]
-------------------------
@@ -22,7 +22,7 @@ aws-kms://label[?options]
You can append query options to the URI in the following format,
?options=value&option2=value&...
-### URI Options
+== URI Options
// component options: START
@@ -54,7 +54,7 @@ aws-iam:label
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -64,7 +64,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (10 parameters):
+=== Query Parameters (10 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -83,7 +83,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -130,9 +130,9 @@ You have to provide the amazonKmsClient in the
Registry or your accessKey and secretKey to access
the https://aws.amazon.com/iam/[Amazon IAM] service.
-### Usage
+== Usage
-#### Message headers evaluated by the IAM producer
+=== Message headers evaluated by the IAM producer
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -151,7 +151,7 @@ the https://aws.amazon.com/iam/[Amazon IAM] service.
|`CamelAwsIAMGroupPath` |`String` |The path of an AWS IAM Group
|=======================================================================
-#### IAM Producer operations
+=== IAM Producer operations
Camel-AWS IAM component provides the following operation on the producer side:
@@ -169,7 +169,7 @@ Camel-AWS IAM component provides the following operation on the producer side:
- addUserToGroup
- removeUserFromGroup
-### Automatic detection of AmazonIdentityManagement client in registry
+== Automatic detection of AmazonIdentityManagement client in registry
The component is capable of detecting the presence of an AmazonIdentityManagement bean into the registry.
If it's the only instance of that type it will be used as client and you won't have to define it as uri parameter.
@@ -192,7 +192,7 @@ Maven users will need to add the following dependency to their pom.xml.
where `$\{camel-version\}` must be replaced by the actual version of Camel.
-### See Also
+== See Also
* Configuring Camel
* Component
diff --git a/components/camel-aws-kinesis/src/main/docs/aws-kinesis-component.adoc b/components/camel-aws-kinesis/src/main/docs/aws-kinesis-component.adoc
index 54daab3..ee13b46 100644
--- a/components/camel-aws-kinesis/src/main/docs/aws-kinesis-component.adoc
+++ b/components/camel-aws-kinesis/src/main/docs/aws-kinesis-component.adoc
@@ -1,5 +1,5 @@
[[aws-kinesis-component]]
-== AWS Kinesis Component
+= AWS Kinesis Component
*Available as of Camel version 2.17*
@@ -12,7 +12,7 @@ You must have a valid Amazon Web Services developer account, and be
signed up to use Amazon Kinesis. More information are available
at https://aws.amazon.com/kinesis/[AWS Kinesis]
-### URI Format
+== URI Format
[source,java]
-----------------------------------
@@ -23,7 +23,7 @@ The stream needs to be created prior to it being used. +
You can append query options to the URI in the following format,
?options=value&option2=value&...
-### URI Options
+== URI Options
// component options: START
@@ -58,7 +58,7 @@ aws-kinesis:streamName
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -68,7 +68,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (32 parameters):
+=== Query Parameters (32 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -109,7 +109,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -164,7 +164,7 @@ You have to provide the amazonKinesisClient in the
Registry with proxies and relevant credentials
configured.
-### Batch Consumer
+== Batch Consumer
This component implements the Batch Consumer.
@@ -172,9 +172,9 @@ This allows you for instance to know how many messages exists in this
batch and for instance let the Aggregator
aggregate this number of messages.
-### Usage
+== Usage
-#### Message headers set by the Kinesis consumer
+=== Message headers set by the Kinesis consumer
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -188,7 +188,7 @@ size is not defined by the API. If it is to be used as a numerical type then use
|`CamelAwsKinesisPartitionKey` |`String` |Identifies which shard in the stream the data record is assigned to.
|=======================================================================
-#### AmazonKinesis configuration
+=== AmazonKinesis configuration
You will need to create an instance of AmazonKinesisClient and
bind it to the registry
@@ -214,7 +214,7 @@ from("aws-kinesis://mykinesisstream?amazonKinesisClient=#kinesisClient")
.to("log:out?showAll=true");
--------------------------------------------------------------------------------------------------------------------
-#### Providing AWS Credentials
+=== Providing AWS Credentials
It is recommended that the credentials are obtained by using the
http://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/auth/DefaultAWSCredentialsProviderChain.html[DefaultAWSCredentialsProviderChain]
@@ -223,7 +223,7 @@ however, a
different http://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/auth/AWSCredentialsProvider.html[AWSCredentialsProvider]
can be specified when calling createClient(...).
-#### Message headers used by the Kinesis producer to write to Kinesis. The producer expects that the message body is a `byte[]`.
+=== Message headers used by the Kinesis producer to write to Kinesis. The producer expects that the message body is a `byte[]`.
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -235,7 +235,7 @@ can be specified when calling createClient(...).
|=======================================================================
-#### Message headers set by the Kinesis producer on successful storage of a Record
+=== Message headers set by the Kinesis producer on successful storage of a Record
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -249,13 +249,13 @@ http://docs.aws.amazon.com/kinesis/latest/APIReference/API_PutRecord.html#API_Pu
|=======================================================================
-### Automatic detection of AmazonKinesis client in registry
+== Automatic detection of AmazonKinesis client in registry
The component is capable of detecting the presence of an AmazonKinesis bean into the registry.
If it's the only instance of that type it will be used as client and you won't have to define it as uri parameter.
This may be really useful for smarter configuration of the endpoint.
-### Dependencies
+== Dependencies
Maven users will need to add the following dependency to their pom.xml.
@@ -272,7 +272,7 @@ Maven users will need to add the following dependency to their pom.xml.
where `$\{camel-version\}` must be replaced by the actual version of Camel.
-### See Also
+== See Also
* Configuring Camel
* Component
diff --git a/components/camel-aws-kinesis/src/main/docs/aws-kinesis-firehose-component.adoc b/components/camel-aws-kinesis/src/main/docs/aws-kinesis-firehose-component.adoc
index 8423426..fc3dda6 100644
--- a/components/camel-aws-kinesis/src/main/docs/aws-kinesis-firehose-component.adoc
+++ b/components/camel-aws-kinesis/src/main/docs/aws-kinesis-firehose-component.adoc
@@ -1,5 +1,5 @@
[[aws-kinesis-firehose-component]]
-== AWS Kinesis Firehose Component
+= AWS Kinesis Firehose Component
*Available as of Camel version 2.19*
@@ -11,7 +11,7 @@ You must have a valid Amazon Web Services developer account, and be
signed up to use Amazon Kinesis Firehose. More information are available
at https://aws.amazon.com/kinesis/firehose/[AWS Kinesis Firehose]
-### URI Format
+== URI Format
[source,java]
-----------------------------------
@@ -22,7 +22,7 @@ The stream needs to be created prior to it being used. +
You can append query options to the URI in the following format,
?options=value&option2=value&...
-### URI Options
+== URI Options
// component options: START
@@ -57,7 +57,7 @@ aws-kinesis-firehose:streamName
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -67,7 +67,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (9 parameters):
+=== Query Parameters (9 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -85,7 +85,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -136,9 +136,9 @@ Registry with proxies and relevant credentials
configured.
-### Usage
+== Usage
-#### Amazon Kinesis Firehose configuration
+=== Amazon Kinesis Firehose configuration
You will need to create an instance of AmazonKinesisClient and
bind it to the registry
@@ -164,7 +164,7 @@ from("aws-kinesis-firehose://mykinesisdeliverystream?amazonKinesisFirehoseClient
.to("log:out?showAll=true");
--------------------------------------------------------------------------------------------------------------------
-#### Providing AWS Credentials
+=== Providing AWS Credentials
It is recommended that the credentials are obtained by using the
http://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/auth/DefaultAWSCredentialsProviderChain.html[DefaultAWSCredentialsProviderChain]
@@ -173,7 +173,7 @@ however, a
different http://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/auth/AWSCredentialsProvider.html[AWSCredentialsProvider]
can be specified when calling createClient(...).
-#### Message headers set by the Kinesis producer on successful storage of a Record
+=== Message headers set by the Kinesis producer on successful storage of a Record
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -185,13 +185,13 @@ http://docs.aws.amazon.com/firehose/latest/APIReference/API_PutRecord.html#API_P
|=======================================================================
-### Automatic detection of AmazonKinesisFirehose client in registry
+== Automatic detection of AmazonKinesisFirehose client in registry
The component is capable of detecting the presence of an AmazonKinesisFirehose bean into the registry.
If it's the only instance of that type it will be used as client and you won't have to define it as uri parameter.
This may be really useful for smarter configuration of the endpoint.
-### Dependencies
+== Dependencies
Maven users will need to add the following dependency to their pom.xml.
@@ -208,7 +208,7 @@ Maven users will need to add the following dependency to their pom.xml.
where `$\{camel-version\}` must be replaced by the actual version of Camel.
-### See Also
+== See Also
* Configuring Camel
* Component
diff --git a/components/camel-aws-kms/src/main/docs/aws-kms-component.adoc b/components/camel-aws-kms/src/main/docs/aws-kms-component.adoc
index 6ae5c2e..de8cf21 100644
--- a/components/camel-aws-kms/src/main/docs/aws-kms-component.adoc
+++ b/components/camel-aws-kms/src/main/docs/aws-kms-component.adoc
@@ -1,5 +1,5 @@
[[aws-kms-component]]
-== AWS KMS Component
+= AWS KMS Component
*Available as of Camel version 2.21*
@@ -12,7 +12,7 @@ You must have a valid Amazon Web Services developer account, and be
signed up to use Amazon KMS. More information is available at
https://aws.amazon.com/kms/[Amazon KMS].
-### URI Format
+== URI Format
[source,java]
-------------------------
@@ -22,7 +22,7 @@ aws-kms://label[?options]
You can append query options to the URI in the following format,
?options=value&option2=value&...
-### URI Options
+== URI Options
// component options: START
@@ -54,7 +54,7 @@ aws-kms:label
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -64,7 +64,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (10 parameters):
+=== Query Parameters (10 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -83,7 +83,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -130,9 +130,9 @@ You have to provide the amazonKmsClient in the
Registry or your accessKey and secretKey to access
the https://aws.amazon.com/kms/[Amazon KMS] service.
-### Usage
+== Usage
-#### Message headers evaluated by the KMS producer
+=== Message headers evaluated by the KMS producer
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -147,7 +147,7 @@ the https://aws.amazon.com/kms/[Amazon KMS] service.
|`CamelAwsKMSKeyId` |`String` |The key Id
|=======================================================================
-#### KMS Producer operations
+=== KMS Producer operations
Camel-AWS KMS component provides the following operation on the producer side:
@@ -158,7 +158,7 @@ Camel-AWS KMS component provides the following operation on the producer side:
- describeKey
- enableKey
-### Automatic detection of AWSKMS client in registry
+== Automatic detection of AWSKMS client in registry
The component is capable of detecting the presence of an AWSKMS bean into the registry.
If it's the only instance of that type it will be used as client and you won't have to define it as uri parameter.
@@ -181,7 +181,7 @@ Maven users will need to add the following dependency to their pom.xml.
where `$\{camel-version\}` must be replaced by the actual version of Camel.
-### See Also
+== See Also
* Configuring Camel
* Component
diff --git a/components/camel-aws-lambda/src/main/docs/aws-lambda-component.adoc b/components/camel-aws-lambda/src/main/docs/aws-lambda-component.adoc
index 35ca291..741b4b8 100644
--- a/components/camel-aws-lambda/src/main/docs/aws-lambda-component.adoc
+++ b/components/camel-aws-lambda/src/main/docs/aws-lambda-component.adoc
@@ -1,5 +1,5 @@
[[aws-lambda-component]]
-== AWS Lambda Component
+= AWS Lambda Component
*Available as of Camel version 2.20*
@@ -18,7 +18,7 @@ When creating a Lambda function, you need to specify a IAM role which has at lea
Lambda is regional service. Unlike S3 bucket, Lambda function created in a given region is not available on other regions.
-### URI Format
+== URI Format
[source,java]
-------------------------
@@ -28,7 +28,7 @@ aws-lambda://functionName[?options]
You can append query options to the URI in the following format,
?options=value&option2=value&...
-### URI Options
+== URI Options
// component options: START
@@ -60,7 +60,7 @@ aws-lambda:function
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -70,7 +70,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (10 parameters):
+=== Query Parameters (10 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -89,7 +89,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -137,9 +137,9 @@ You have to provide the awsLambdaClient in the
Registry or your accessKey and secretKey to access
the https://aws.amazon.com/lambda/[Amazon Lambda] service.
-### Usage
+== Usage
-#### Message headers evaluated by the Lambda producer
+=== Message headers evaluated by the Lambda producer
[width="100%",cols="5%,5%,10%,75%,5%",options="header",]
|=======================================================================
@@ -198,7 +198,7 @@ The default is 3 seconds.|No
|=======================================================================
-### List of Avalaible Operations
+== List of Avalaible Operations
- listFunctions
- getFunction,
@@ -215,18 +215,18 @@ The default is 3 seconds.|No
- publishVersion
- listVersions
-### Example
+== Example
To have a full understanding of how the component works, you may have a look at this https://github.com/apache/camel/blob/master/components/camel-aws/src/test/java/org/apache/camel/component/aws/lambda/integration/LambdaComponentIntegrationTest.java[integration test]
-### Automatic detection of AmazonLambda client in registry
+== Automatic detection of AmazonLambda client in registry
The component is capable of detecting the presence of an AmazonLambda bean into the registry.
If it's the only instance of that type it will be used as client and you won't have to define it as uri parameter.
This may be really useful for smarter configuration of the endpoint.
-### Dependencies
+== Dependencies
Maven users will need to add the following dependency to their pom.xml.
@@ -243,7 +243,7 @@ Maven users will need to add the following dependency to their pom.xml.
where `$\{camel-version\}` must be replaced by the actual version of Camel.
-### See Also
+== See Also
* Configuring Camel
* Component
diff --git a/components/camel-aws-mq/src/main/docs/aws-mq-component.adoc b/components/camel-aws-mq/src/main/docs/aws-mq-component.adoc
index e58c310..629e2bd 100644
--- a/components/camel-aws-mq/src/main/docs/aws-mq-component.adoc
+++ b/components/camel-aws-mq/src/main/docs/aws-mq-component.adoc
@@ -1,5 +1,5 @@
[[aws-mq-component]]
-== AWS MQ Component
+= AWS MQ Component
*Available as of Camel version 2.21*
@@ -12,7 +12,7 @@ You must have a valid Amazon Web Services developer account, and be
signed up to use Amazon MQ. More information is available at
https://aws.amazon.com/mq/[Amazon MQ].
-### URI Format
+== URI Format
[source,java]
-------------------------
@@ -22,7 +22,7 @@ aws-mq://label[?options]
You can append query options to the URI in the following format,
?options=value&option2=value&...
-### URI Options
+== URI Options
// component options: START
@@ -54,7 +54,7 @@ aws-mq:label
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -64,7 +64,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (10 parameters):
+=== Query Parameters (10 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -83,7 +83,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -130,9 +130,9 @@ You have to provide the amazonMqClient in the
Registry or your accessKey and secretKey to access
the https://aws.amazon.com/mq/[Amazon MQ] service.
-### Usage
+== Usage
-#### Message headers evaluated by the MQ producer
+=== Message headers evaluated by the MQ producer
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -159,7 +159,7 @@ the https://aws.amazon.com/mq/[Amazon MQ] service.
|`CamelAwsMQBrokerPubliclyAccessible` |`Boolean` |If the MQ instance must be publicly available or not. Default is false.
|=======================================================================
-### Automatic detection of AmazonMQ client in registry
+== Automatic detection of AmazonMQ client in registry
The component is capable of detecting the presence of an AmazonMQ bean into the registry.
If it's the only instance of that type it will be used as client and you won't have to define it as uri parameter.
@@ -182,7 +182,7 @@ Maven users will need to add the following dependency to their pom.xml.
where `$\{camel-version\}` must be replaced by the actual version of Camel.
-### See Also
+== See Also
* Configuring Camel
* Component
diff --git a/components/camel-aws-msk/src/main/docs/aws-msk-component.adoc b/components/camel-aws-msk/src/main/docs/aws-msk-component.adoc
index 4898489..229d5be 100644
--- a/components/camel-aws-msk/src/main/docs/aws-msk-component.adoc
+++ b/components/camel-aws-msk/src/main/docs/aws-msk-component.adoc
@@ -1,5 +1,5 @@
[[aws-msk-component]]
-== AWS MSK Component
+= AWS MSK Component
*Available as of Camel version 3.0*
@@ -12,7 +12,7 @@ You must have a valid Amazon Web Services developer account, and be
signed up to use Amazon MSK. More information is available at
https://aws.amazon.com/msk/[Amazon MSK].
-### URI Format
+== URI Format
[source,java]
-------------------------
@@ -22,7 +22,7 @@ aws-msk://label[?options]
You can append query options to the URI in the following format,
?options=value&option2=value&...
-### URI Options
+== URI Options
// component options: START
@@ -54,7 +54,7 @@ aws-msk:label
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -64,7 +64,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (10 parameters):
+=== Query Parameters (10 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -84,7 +84,7 @@ with the following path and query parameters:
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -131,9 +131,9 @@ You have to provide the amazonKmsClient in the
Registry or your accessKey and secretKey to access
the https://aws.amazon.com/msk/[Amazon MSK] service.
-### Usage
+== Usage
-#### Message headers evaluated by the MSK producer
+=== Message headers evaluated by the MSK producer
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -154,7 +154,7 @@ the https://aws.amazon.com/msk/[Amazon MSK] service.
|`CamelAwsMSKBrokerNodesGroupInfo` |`com.amazonaws.services.kafka.model.BrokerNodeGroupInfo`| The Broker nodes group info to provide during the create operation
|=======================================================================
-#### KMS Producer operations
+=== KMS Producer operations
Camel-AWS KMS component provides the following operation on the producer side:
@@ -162,7 +162,7 @@ Camel-AWS KMS component provides the following operation on the producer side:
- createCluster
- deleteCluster
-### Automatic detection of AWSKafka client in registry
+== Automatic detection of AWSKafka client in registry
The component is capable of detecting the presence of an AWSKafka bean into the registry.
If it's the only instance of that type it will be used as client and you won't have to define it as uri parameter.
@@ -185,7 +185,7 @@ Maven users will need to add the following dependency to their pom.xml.
where `$\{camel-version\}` must be replaced by the actual version of Camel.
-### See Also
+== See Also
* Configuring Camel
* Component
diff --git a/components/camel-aws-s3/src/main/docs/aws-s3-component.adoc b/components/camel-aws-s3/src/main/docs/aws-s3-component.adoc
index 6bdd541..2882a2e 100644
--- a/components/camel-aws-s3/src/main/docs/aws-s3-component.adoc
+++ b/components/camel-aws-s3/src/main/docs/aws-s3-component.adoc
@@ -1,5 +1,5 @@
[[aws-s3-component]]
-== AWS S3 Storage Service Component
+= AWS S3 Storage Service Component
*Available as of Camel version 2.8*
@@ -12,7 +12,7 @@ You must have a valid Amazon Web Services developer account, and be
signed up to use Amazon S3. More information is available at
https://aws.amazon.com/s3[Amazon S3].
-### URI Format
+== URI Format
[source,java]
------------------------------
@@ -32,7 +32,7 @@ from("aws-s3:helloBucket?accessKey=yourAccessKey&secretKey=yourSecretKey&prefix=
--------------------------------------------------------------------------------
-### URI Options
+== URI Options
// component options: START
@@ -71,7 +71,7 @@ aws-s3:bucketNameOrArn
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -81,7 +81,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (55 parameters):
+=== Query Parameters (55 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -145,7 +145,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -224,7 +224,7 @@ You have to provide the amazonS3Client in the
Registry or your accessKey and secretKey to access
the https://aws.amazon.com/s3[Amazon's S3].
-### Batch Consumer
+== Batch Consumer
This component implements the Batch Consumer.
@@ -232,9 +232,9 @@ This allows you for instance to know how many messages exists in this
batch and for instance let the Aggregator
aggregate this number of messages.
-### Usage
+== Usage
-#### Message headers evaluated by the S3 producer
+=== Message headers evaluated by the S3 producer
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -281,7 +281,7 @@ the object using AWS-managed keys. For example use AES256.
|`CamelAwsS3VersionId` |`String` |The version Id of the object to be stored or returned from the current operation
|=======================================================================
-#### Message headers set by the S3 producer
+=== Message headers set by the S3 producer
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -294,7 +294,7 @@ the object using AWS-managed keys. For example use AES256.
|=======================================================================
-#### Message headers set by the S3 consumer
+=== Message headers set by the S3 consumer
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -343,7 +343,7 @@ specify caching behavior along the HTTP request/reply chain.
object using AWS-managed keys.
|=======================================================================
-#### S3 Producer operations
+=== S3 Producer operations
Camel-AWS s3 component provides the following operation on the producer side:
@@ -355,7 +355,7 @@ Camel-AWS s3 component provides the following operation on the producer side:
- listObjects
- getObject (this will return an S3Object instance)
-#### Advanced AmazonS3 configuration
+=== Advanced AmazonS3 configuration
If your Camel Application is running behind a firewall or if you need to
have more control over the `AmazonS3` instance configuration, you can
@@ -382,7 +382,7 @@ from("aws-s3://MyBucket?amazonS3Client=#client&delay=5000&maxMessagesPerPoll=5")
.to("mock:result");
--------------------------------------------------------------------------------
-#### Use KMS with the S3 component
+=== Use KMS with the S3 component
To use AWS KMS to encrypt/decrypt data by using AWS infrastructure you can use the options introduced in 2.21.x like in the following example
@@ -395,7 +395,7 @@ from("file:tmp/test?fileName=test.txt")
In this way you'll ask to S3, to use the KMS key 3f0637ad-296a-3dfe-a796-e60654fb128c, to encrypt the file test.txt. When you'll ask to download this file, the decryption will be done directly before the download.
-#### Use "useIAMCredentials" with the s3 component
+=== Use "useIAMCredentials" with the s3 component
To use AWS IAM credentials, you must first verify that the EC2 in which you are launching the Camel application on has an IAM role associated with it containing the appropriate policies attached to run effectively.
Keep in mind that this feature should only be set to "true" on remote instances. To clarify even further, you must still use static credentials locally since IAM is an AWS specific component,
@@ -405,7 +405,7 @@ when the system environment variable called "isRemote" is set to true (there are
using IAM credentials on AWS environments takes away the need to refresh on remote environments and adds a major security boost (IAM credentials are refreshed automatically every 6 hours and update when their
policies are updated). This is the AWS recommended way to manage credentials and therefore should be used as often as possible.
-#### S3 Producer Operation examples
+=== S3 Producer Operation examples
- CopyObject: this operation copy an object from one bucket to a different one
@@ -510,18 +510,18 @@ This operation will list the objects in the mycamelbucket bucket
This operation will return an S3Object instance related to the camelKey object in mycamelbucket bucket.
-### Bucket Autocreation
+== Bucket Autocreation
With the option `autoCreateBucket` users are able to avoid the autocreation of an S3 Bucket in case it doesn't exist. The default for this option is `true`.
If set to false any operation on a not-existent bucket in AWS won't be successful and an error will be returned.
-### Automatic detection of AmazonS3 client in registry
+== Automatic detection of AmazonS3 client in registry
The component is capable of detecting the presence of an AmazonS3 bean into the registry.
If it's the only instance of that type it will be used as client and you won't have to define it as uri parameter, like the example above.
This may be really useful for smarter configuration of the endpoint.
-### Dependencies
+== Dependencies
Maven users will need to add the following dependency to their pom.xml.
@@ -538,7 +538,7 @@ Maven users will need to add the following dependency to their pom.xml.
where `$\{camel-version\}` must be replaced by the actual version of Camel.
-### See Also
+== See Also
* Configuring Camel
* Component
diff --git a/components/camel-aws-sdb/src/main/docs/aws-sdb-component.adoc b/components/camel-aws-sdb/src/main/docs/aws-sdb-component.adoc
index 02ad976..2d28659 100644
--- a/components/camel-aws-sdb/src/main/docs/aws-sdb-component.adoc
+++ b/components/camel-aws-sdb/src/main/docs/aws-sdb-component.adoc
@@ -1,5 +1,5 @@
[[aws-sdb-component]]
-== AWS SimpleDB Component
+= AWS SimpleDB Component
*Available as of Camel version 2.9*
@@ -12,7 +12,7 @@ You must have a valid Amazon Web Services developer account, and be
signed up to use Amazon SDB. More information is available at
https://aws.amazon.com/sdb[Amazon SDB].
-### URI Format
+== URI Format
[source,java]
------------------------------
@@ -22,7 +22,7 @@ aws-sdb://domainName[?options]
You can append query options to the URI in the following format,
?options=value&option2=value&...
-### URI Options
+== URI Options
// component options: START
@@ -50,7 +50,7 @@ aws-sdb:domainName
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -60,7 +60,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (12 parameters):
+=== Query Parameters (12 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -81,7 +81,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -118,9 +118,9 @@ You have to provide the amazonSDBClient in the
Registry or your accessKey and secretKey to access
the https://aws.amazon.com/sdb[Amazon's SDB].
-### Usage
+== Usage
-#### Message headers evaluated by the SDB producer
+=== Message headers evaluated by the SDB producer
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -156,7 +156,7 @@ to 100.
specified attributes will be updated/deleted or not.
|=======================================================================
-#### Message headers set during DomainMetadata operation
+=== Message headers set during DomainMetadata operation
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -177,7 +177,7 @@ specified attributes will be updated/deleted or not.
|`CamelAwsSdbItemNameSize` |`Long` |The total size of all item names in the domain, in bytes.
|=======================================================================
-#### Message headers set during GetAttributes operation
+=== Message headers set during GetAttributes operation
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -186,7 +186,7 @@ specified attributes will be updated/deleted or not.
|`CamelAwsSdbAttributes` |`List<Attribute>` |The list of attributes returned by the operation.
|=======================================================================
-#### Message headers set during ListDomains operation
+=== Message headers set during ListDomains operation
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -198,7 +198,7 @@ specified attributes will be updated/deleted or not.
specified MaxNumberOfDomains still available.
|=======================================================================
-#### Message headers set during Select operation
+=== Message headers set during Select operation
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -211,7 +211,7 @@ matched, the response size exceeded 1 megabyte, or the execution time
exceeded 5 seconds.
|=======================================================================
-#### Advanced AmazonSimpleDB configuration
+=== Advanced AmazonSimpleDB configuration
If you need more control over the `AmazonSimpleDB` instance
configuration you can create your own instance and refer to it from the
@@ -240,7 +240,7 @@ AmazonSimpleDB client = new AmazonSimpleDBClient(awsCredentials, clientConfigura
registry.bind("client", client);
--------------------------------------------------------------------------------------
-### Dependencies
+== Dependencies
Maven users will need to add the following dependency to their pom.xml.
@@ -257,7 +257,7 @@ Maven users will need to add the following dependency to their pom.xml.
where `$\{camel-version\}` must be replaced by the actual version of Camel.
-### See Also
+== See Also
* Configuring Camel
* Component
diff --git a/components/camel-aws-ses/src/main/docs/aws-ses-component.adoc b/components/camel-aws-ses/src/main/docs/aws-ses-component.adoc
index 22ea4ad..1e4cd5d 100644
--- a/components/camel-aws-ses/src/main/docs/aws-ses-component.adoc
+++ b/components/camel-aws-ses/src/main/docs/aws-ses-component.adoc
@@ -1,5 +1,5 @@
[[aws-ses-component]]
-== AWS Simple Email Service Component
+= AWS Simple Email Service Component
*Available as of Camel version 2.9*
@@ -12,7 +12,7 @@ You must have a valid Amazon Web Services developer account, and be
signed up to use Amazon SES. More information is available at
https://aws.amazon.com/ses[Amazon SES].
-### URI Format
+== URI Format
[source,java]
------------------------
@@ -22,7 +22,7 @@ aws-ses://from[?options]
You can append query options to the URI in the following format,
?options=value&option2=value&...
-### URI Options
+== URI Options
// component options: START
@@ -54,7 +54,7 @@ aws-ses:from
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -64,7 +64,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (13 parameters):
+=== Query Parameters (13 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -86,7 +86,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -137,9 +137,9 @@ You have to provide the amazonSESClient in the
Registry or your accessKey and secretKey to access
the https://aws.amazon.com/ses[Amazon's SES].
-### Usage
+== Usage
-#### Message headers evaluated by the SES producer
+=== Message headers evaluated by the SES producer
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -158,7 +158,7 @@ the https://aws.amazon.com/ses[Amazon's SES].
|`CamelAwsSesHtmlEmail` |`Boolean` |The flag to show if email content is HTML.
|=======================================================================
-#### Message headers set by the SES producer
+=== Message headers set by the SES producer
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -167,7 +167,7 @@ the https://aws.amazon.com/ses[Amazon's SES].
|`CamelAwsSesMessageId` |`String` |The Amazon SES message ID.
|=======================================================================
-#### Advanced AmazonSimpleEmailService configuration
+=== Advanced AmazonSimpleEmailService configuration
If you need more control over the `AmazonSimpleEmailService` instance
configuration you can create your own instance and refer to it from the
@@ -195,11 +195,11 @@ AmazonSimpleEmailService client = new AmazonSimpleEmailServiceClient(awsCredenti
registry.bind("client", client);
----------------------------------------------------------------------------------------------------------
-### Dependencies
+== Dependencies
Maven users will need to add the following dependency to their pom.xml.
-### Automatic detection of AmazonSimpleEmailService client in registry
+== Automatic detection of AmazonSimpleEmailService client in registry
The component is capable of detecting the presence of an AmazonSimpleEmailService bean into the registry.
If it's the only instance of that type it will be used as client and you won't have to define it as uri parameter.
@@ -218,7 +218,7 @@ This may be really useful for smarter configuration of the endpoint.
where `$\{camel-version\}` must be replaced by the actual version of Camel.
-### See Also
+== See Also
* Configuring Camel
* Component
diff --git a/components/camel-aws-sns/src/main/docs/aws-sns-component.adoc b/components/camel-aws-sns/src/main/docs/aws-sns-component.adoc
index 3c544af..598b72c 100644
--- a/components/camel-aws-sns/src/main/docs/aws-sns-component.adoc
+++ b/components/camel-aws-sns/src/main/docs/aws-sns-component.adoc
@@ -1,5 +1,5 @@
[[aws-sns-component]]
-== AWS Simple Notification System Component
+= AWS Simple Notification System Component
*Available as of Camel version 2.8*
@@ -14,7 +14,7 @@ You must have a valid Amazon Web Services developer account, and be
signed up to use Amazon SNS. More information is available at
https://aws.amazon.com/sns[Amazon SNS].
-### URI Format
+== URI Format
[source,java]
-----------------------------
@@ -25,7 +25,7 @@ The topic will be created if they don't already exists. +
You can append query options to the URI in the following format,
`?options=value&option2=value&...`
-### URI Options
+== URI Options
// component options: START
@@ -58,7 +58,7 @@ aws-sns:topicNameOrArn
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -68,7 +68,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (19 parameters):
+=== Query Parameters (19 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -96,7 +96,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -154,9 +154,9 @@ You have to provide the amazonSNSClient in the
Registry or your accessKey and secretKey to access
the https://aws.amazon.com/sns[Amazon's SNS].
-### Usage
+== Usage
-#### Message headers evaluated by the SNS producer
+=== Message headers evaluated by the SNS producer
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -166,7 +166,7 @@ the https://aws.amazon.com/sns[Amazon's SNS].
`SnsConfiguration` is used.
|=======================================================================
-#### Message headers set by the SNS producer
+=== Message headers set by the SNS producer
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -175,7 +175,7 @@ the https://aws.amazon.com/sns[Amazon's SNS].
|`CamelAwsSnsMessageId` |`String` |The Amazon SNS message ID.
|=======================================================================
-#### Advanced AmazonSNS configuration
+=== Advanced AmazonSNS configuration
If you need more control over the `AmazonSNS` instance configuration you
can create your own instance and refer to it from the URI:
@@ -202,7 +202,7 @@ AmazonSNS client = new AmazonSNSClient(awsCredentials, clientConfiguration);
registry.bind("client", client);
--------------------------------------------------------------------------------------
-#### Create a subscription between an AWS SNS Topic and an AWS SQS Queue
+=== Create a subscription between an AWS SNS Topic and an AWS SQS Queue
You can create a subscription of an SQS Queue to an SNS Topic in this way:
@@ -225,18 +225,18 @@ from("aws-sqs://test-camel?amazonSQSClient=#amazonSQSClient&delay=50&maxMessages
.to(...);
-------------------------------------------------
-### Topic Autocreation
+== Topic Autocreation
With the option `autoCreateTopic` users are able to avoid the autocreation of an SNS Topic in case it doesn't exist. The default for this option is `true`.
If set to false any operation on a not-existent topic in AWS won't be successful and an error will be returned.
-### Automatic detection of AmazonSNS client in registry
+== Automatic detection of AmazonSNS client in registry
The component is capable of detecting the presence of an AmazonSNS bean into the registry.
If it's the only instance of that type it will be used as client and you won't have to define it as uri parameter.
This may be really useful for smarter configuration of the endpoint.
-### Dependencies
+== Dependencies
Maven users will need to add the following dependency to their pom.xml.
@@ -253,7 +253,7 @@ Maven users will need to add the following dependency to their pom.xml.
where `$\{camel-version\}` must be replaced by the actual version of Camel.
-### See Also
+== See Also
* Configuring Camel
* Component
diff --git a/components/camel-aws-sqs/src/main/docs/aws-sqs-component.adoc b/components/camel-aws-sqs/src/main/docs/aws-sqs-component.adoc
index 6033f29..9d62f5e 100644
--- a/components/camel-aws-sqs/src/main/docs/aws-sqs-component.adoc
+++ b/components/camel-aws-sqs/src/main/docs/aws-sqs-component.adoc
@@ -1,5 +1,5 @@
[[aws-sqs-component]]
-== AWS Simple Queue Service Component
+= AWS Simple Queue Service Component
*Available as of Camel version 2.6*
@@ -12,7 +12,7 @@ You must have a valid Amazon Web Services developer account, and be
signed up to use Amazon SQS. More information is available at
https://aws.amazon.com/sqs[Amazon SQS].
-### URI Format
+== URI Format
[source,java]
------------------------------
@@ -23,7 +23,7 @@ The queue will be created if they don't already exists. +
You can append query options to the URI in the following format,
?options=value&option2=value&...
-### URI Options
+== URI Options
// component options: START
@@ -59,7 +59,7 @@ aws-sqs:queueNameOrArn
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -69,7 +69,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (55 parameters):
+=== Query Parameters (55 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -133,7 +133,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -210,7 +210,7 @@ You have to provide the amazonSQSClient in the
Registry or your accessKey and secretKey to access
the https://aws.amazon.com/sqs[Amazon's SQS].
-### Batch Consumer
+== Batch Consumer
This component implements the Batch Consumer.
@@ -218,9 +218,9 @@ This allows you for instance to know how many messages exists in this
batch and for instance let the Aggregator
aggregate this number of messages.
-### Usage
+== Usage
-#### Message headers set by the SQS producer
+=== Message headers set by the SQS producer
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -234,7 +234,7 @@ aggregate this number of messages.
see by others.
|=======================================================================
-#### Message headers set by the SQS consumer
+=== Message headers set by the SQS consumer
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -249,7 +249,7 @@ see by others.
|`CamelAwsSqsMessageAttributes` |`Map<String, String>` |The Amazon SQS message attributes.
|=======================================================================
-#### Advanced AmazonSQS configuration
+=== Advanced AmazonSQS configuration
If your Camel Application is running behind a firewall or if you need to
have more control over the AmazonSQS instance configuration, you can
@@ -276,7 +276,7 @@ from("aws-sqs://MyQueue?amazonSQSClient=#client&delay=5000&maxMessagesPerPoll=5"
.to("mock:result");
---------------------------------------------------------------------------------
-#### Creating or updating an SQS Queue
+=== Creating or updating an SQS Queue
In the SQS Component, when an endpoint is started, a check is executed to obtain information
about the existence of the queue or not. You're able to customize the creation through the QueueAttributeName
@@ -291,7 +291,7 @@ from("aws-sqs://MyQueue?amazonSQSClient=#client&delay=5000&maxMessagesPerPoll=5"
In this example if the MyQueue queue is not already created on AWS (and the autoCreateQueue option is set to true), it will be created with default parameters from the
SQS configuration. If it's already up on AWS, the SQS configuration options will be used to override the existent AWS configuration.
-#### DelayQueue VS Delay for Single message
+=== DelayQueue VS Delay for Single message
When the option delayQueue is set to true, the SQS Queue will be a DelayQueue with the
DelaySeconds option as delay. For more information about DelayQueue you can read the https://docs.aws.amazon.com/en_us/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-delay-queues.html[AWS SQS documentation].
@@ -303,12 +303,12 @@ One important information to take into account is the following:
as stated in the official documentation. If you want to specify a delay on single messages, you can ignore the delayQueue option, while you can set this option
to true, if you need to add a fixed delay to all messages enqueued.
-#### Server Side Encryption
+=== Server Side Encryption
There is a set of Server Side Encryption attributes for a queue. The related option are serverSideEncryptionEnabled, keyMasterKeyId and kmsDataKeyReusePeriod.
The SSE is disabled by default. You need to explicitly set the option to true and set the related parameters as queue attributes.
-### Dependencies
+== Dependencies
Maven users will need to add the following dependency to their pom.xml.
@@ -325,7 +325,7 @@ Maven users will need to add the following dependency to their pom.xml.
where `$\{camel-version\}` must be replaced by the actual version of Camel.
-### JMS-style Selectors
+== JMS-style Selectors
SQS does not allow selectors, but you can effectively achieve this by
using the Camel Filter EIP and setting an
@@ -349,13 +349,13 @@ will not make it through the filter AND also not be deleted from the SQS
queue. After 5000 milliseconds, the message will become visible to other
consumers.
-### Available Producer Operations
+== Available Producer Operations
- single message (default)
- sendBatchMessage
- deleteMessage
- listQueues
-### Send Batch Message
+== Send Batch Message
You can set a `SendMessageBatchRequest` or an `Iterable`
@@ -367,7 +367,7 @@ from("direct:start")
As result you'll get an exchange containing a `SendMessageBatchResult` instance, that you can examinate to check what messages were successfull and what not.
The id set on each message of the batch will be a Random UUID.
-### Delete single Message
+== Delete single Message
Use deleteMessage operation to delete a single message. You'll need to set a receipt handle header for the message you want to delete.
@@ -380,7 +380,7 @@ from("direct:start")
As result you'll get an exchange containing a `DeleteMessageResult` instance, that you can use to check if the message was deleted or not.
-### List Queues
+== List Queues
Use listQueues operation to list queues.
@@ -391,18 +391,18 @@ from("direct:start")
As result you'll get an exchange containing a `ListQueuesResult` instance, that you can examinate to check the actual queues.
-### Queue Autocreation
+== Queue Autocreation
With the option `autoCreateQueue` users are able to avoid the autocreation of an SQS Queue in case it doesn't exist. The default for this option is `true`.
If set to false any operation on a not-existent queue in AWS won't be successful and an error will be returned.
-### Automatic detection of AmazonSQS client in registry
+== Automatic detection of AmazonSQS client in registry
The component is capable of detecting the presence of an AmazonSQS bean into the registry.
If it's the only instance of that type it will be used as client and you won't have to define it as uri parameter.
This may be really useful for smarter configuration of the endpoint.
-### Send Batch Message and Message Deduplication Strategy
+== Send Batch Message and Message Deduplication Strategy
In case you're using a SendBatchMessage Operation, you can set two different kind of Message Deduplication Strategy:
- useExchangeId
@@ -413,7 +413,7 @@ The other one will use a NullMessageDeduplicationIdStrategy, that will use the b
In case of send batch message operation, you'll need to use the `useContentBasedDeduplication` and on the Queue you're pointing you'll need to enable the `content based deduplication` option.
-### See Also
+== See Also
* Configuring Camel
* Component
diff --git a/components/camel-aws-swf/src/main/docs/aws-swf-component.adoc b/components/camel-aws-swf/src/main/docs/aws-swf-component.adoc
index 5386501..31eb619 100644
--- a/components/camel-aws-swf/src/main/docs/aws-swf-component.adoc
+++ b/components/camel-aws-swf/src/main/docs/aws-swf-component.adoc
@@ -1,5 +1,5 @@
[[aws-swf-component]]
-== AWS Simple Workflow Component
+= AWS Simple Workflow Component
*Available as of Camel version 2.13*
@@ -12,7 +12,7 @@ You must have a valid Amazon Web Services developer account, and be
signed up to use Amazon Simple Workflow. More information are available
at https://aws.amazon.com/swf/[Amazon Simple Workflow].
-### URI Format
+== URI Format
[source,java]
---------------------------------------
@@ -22,7 +22,7 @@ aws-swf://<workflow|activity>[?options]
You can append query options to the URI in the following format,
?options=value&option2=value&...
-### URI Options
+== URI Options
// component options: START
@@ -54,7 +54,7 @@ aws-swf:type
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -64,7 +64,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (32 parameters):
+=== Query Parameters (32 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -105,7 +105,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -172,9 +172,9 @@ You have to provide the amazonSWClient in the
Registry or your accessKey and secretKey to access
the https://aws.amazon.com/swf[Amazon's Simple Workflow Service].
-### Usage
+== Usage
-#### Message headers evaluated by the SWF Workflow Producer
+=== Message headers evaluated by the SWF Workflow Producer
A workflow producer allows interacting with a workflow. It can start a
new workflow execution, query its state, send signals to a running
@@ -204,7 +204,7 @@ workflow, or terminate and cancel it.
|`CamelSWFChildPolicy` |`String` |The policy to use on child workflows when terminating a workflow.
|=======================================================================
-#### Message headers set by the SWF Workflow Producer
+=== Message headers set by the SWF Workflow Producer
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -215,7 +215,7 @@ workflow, or terminate and cancel it.
|`CamelAwsDdbKeyCamelSWFRunId` |`String` |The worfklow run ID used or generated.
|=======================================================================
-#### Message headers set by the SWF Workflow Consumer
+=== Message headers set by the SWF Workflow Consumer
A workflow consumer represents the workflow logic. When it is started,
it will start polling workflow decision tasks and process them. In
@@ -237,7 +237,7 @@ CamelSWFSignalReceivedAction or CamelSWFGetStateAction.
|`CamelSWFWorkflowStartTime` |`long` |The time of the start event for this decision task.
|=======================================================================
-#### Message headers set by the SWF Activity Producer
+=== Message headers set by the SWF Activity Producer
An activity producer allows scheduling activity tasks. An activity
producer can be used only from a thread started by a workflow consumer
@@ -252,7 +252,7 @@ ie, it can process synchronous exchanges started by a workflow consumer.
|`CamelSWFVersion` |`String` |The activity version to schedule.
|=======================================================================
-#### Message headers set by the SWF Activity Consumer
+=== Message headers set by the SWF Activity Consumer
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -262,7 +262,7 @@ ie, it can process synchronous exchanges started by a workflow consumer.
completed tasks.
|=======================================================================
-#### Advanced amazonSWClient configuration
+=== Advanced amazonSWClient configuration
If you need more control over the AmazonSimpleWorkflowClient instance
configuration you can create your own instance and refer to it from the
@@ -285,13 +285,13 @@ AmazonSimpleWorkflowClient client = new AmazonSimpleWorkflowClient(awsCredential
registry.bind("client", client);
--------------------------------------------------------------------------------------------------------
-### Automatic detection of AmazonSimpleWorkflow client in registry
+== Automatic detection of AmazonSimpleWorkflow client in registry
The component is capable of detecting the presence of an AmazonSimpleWorkflow bean into the registry.
If it's the only instance of that type it will be used as client and you won't have to define it as uri parameter.
This may be really useful for smarter configuration of the endpoint.
-### Dependencies
+== Dependencies
Maven users will need to add the following dependency to their pom.xml.
@@ -308,7 +308,7 @@ Maven users will need to add the following dependency to their pom.xml.
where `$\{camel-version\}` must be replaced by the actual version of Camel.
-### See Also
+== See Also
* Configuring Camel
* Component
diff --git a/components/camel-aws-xray/src/main/docs/aws-xray.adoc b/components/camel-aws-xray/src/main/docs/aws-xray.adoc
index 0ca62c7..cda67cb 100644
--- a/components/camel-aws-xray/src/main/docs/aws-xray.adoc
+++ b/components/camel-aws-xray/src/main/docs/aws-xray.adoc
@@ -1,5 +1,5 @@
[[AWSXRay-AWSXRayComponent]]
-## AWS XRay Component
+= AWS XRay Component
*Available as of Camel 2.21*
@@ -7,7 +7,7 @@ The camel-aws-xray component is used for tracing and timing incoming and outgoin
Events (subsegments) are captured for incoming and outgoing messages being sent to/from Camel.
-### Dependency
+== Dependency
In order to include AWS XRay support into Camel, the archive containing the Camel related AWS XRay related classes need to be added to the project. In addition to that, AWS XRay libraries also need to be available.
@@ -44,7 +44,7 @@ To include both, AWS XRay and Camel, dependencies use the following Maven import
<dependencies>
---------------------------------------------------------------------------------------------------------
-### Configuration
+== Configuration
The configuration properties for the AWS XRay tracer are:
@@ -61,7 +61,7 @@ uses the rules from Intercept.
There is currently only one way an AWS XRay tracer can be configured to provide distributed tracing for a Camel application:
-#### Explicit
+=== Explicit
Include the `camel-aws-xray` component in your POM, along with any specific dependencies associated with the AWS XRay Tracer.
@@ -91,7 +91,7 @@ AWS XRay tracer bean. Camel will automatically discover and use it.
In case of the default `NoopTracingStrategy` only the creation and deletion of exchanges is tracked but not the invocation of certain beans or EIP patterns.
-#### Tracking of comprehensive route execution
+=== Tracking of comprehensive route execution
In order to track the execution of an exchange among multiple routes, on exchange creation a unique trace ID is generated and stored in the headers if no corresponding value was yet available. This trace ID is copied over to new exchanges in order to keep a consistent view of the processed exchange.
@@ -110,6 +110,6 @@ The component will use the following constants found in the headers of the excha
Note that the AWS XRay `Entity` (i.e., `Segment` and `Subsegment`) are not serializable and therefore should not get passed to other JVM processes.
-### Example
+== Example
You can find an example demonstrating the way to configure AWS XRay tracing within the tests accompanying this project.
\ No newline at end of file
diff --git a/components/camel-azure/src/main/docs/azure-blob-component.adoc b/components/camel-azure/src/main/docs/azure-blob-component.adoc
index 7e8c516..cff2e2a 100644
--- a/components/camel-azure/src/main/docs/azure-blob-component.adoc
+++ b/components/camel-azure/src/main/docs/azure-blob-component.adoc
@@ -1,5 +1,5 @@
[[azure-blob-component]]
-== Azure Storage Blob Service Component
+= Azure Storage Blob Service Component
*Available as of Camel version 2.19*
@@ -11,7 +11,7 @@ Prerequisites
You must have a valid Windows Azure Storage account. More information is available at
https://docs.microsoft.com/azure/[Azure Documentation Portal].
-### URI Format
+== URI Format
[source,java]
------------------------------
@@ -31,7 +31,7 @@ from("azure-blob:/camelazure/container1/blockBlob").
to("file://blobdirectory");
--------------------------------------------------------------------------------
-### URI Options
+== URI Options
// component options: START
@@ -67,7 +67,7 @@ azure-blob:containerOrBlobUri
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -77,7 +77,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (21 parameters):
+=== Query Parameters (21 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -107,7 +107,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -160,9 +160,9 @@ Required Azure Storage Blob Service component options
You have to provide the containerOrBlob name and the credentials if the private blob needs to be accessed.
-### Usage
+== Usage
-#### Message headers set by the Azure Storage Blob Service producer
+=== Message headers set by the Azure Storage Blob Service producer
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -170,7 +170,7 @@ You have to provide the containerOrBlob name and the credentials if the private
|`CamelFileName` |`String` |The file name for the downloaded blob content.
|=======================================================================
-#### Message headers set by the Azure Storage Blob Service producer consumer
+=== Message headers set by the Azure Storage Blob Service producer consumer
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -179,7 +179,7 @@ You have to provide the containerOrBlob name and the credentials if the private
|=======================================================================
-#### Azure Blob Service operations
+=== Azure Blob Service operations
*Operations common to all block types*
@@ -235,7 +235,7 @@ You have to provide the containerOrBlob name and the credentials if the private
-#### Azure Blob Client configuration
+=== Azure Blob Client configuration
If your Camel Application is running behind a firewall or if you need to
have more control over the Azure Blob Client configuration, you can
@@ -256,7 +256,7 @@ from("azure-blob://camelazure/container1/blockBlob?azureBlobClient=#client")
.to("mock:result");
--------------------------------------------------------------------------------
-### Dependencies
+== Dependencies
Maven users will need to add the following dependency to their pom.xml.
@@ -273,7 +273,7 @@ Maven users will need to add the following dependency to their pom.xml.
where `${camel-version`} must be replaced by the actual version of Camel.
-### See Also
+== See Also
* Configuring Camel
* Component
diff --git a/components/camel-azure/src/main/docs/azure-queue-component.adoc b/components/camel-azure/src/main/docs/azure-queue-component.adoc
index 417d81b..630da10 100644
--- a/components/camel-azure/src/main/docs/azure-queue-component.adoc
+++ b/components/camel-azure/src/main/docs/azure-queue-component.adoc
@@ -1,5 +1,5 @@
[[azure-queue-component]]
-== Azure Storage Queue Service Component
+= Azure Storage Queue Service Component
*Available as of Camel version 2.19*
@@ -11,7 +11,7 @@ Prerequisites
You must have a valid Microsoft Azure account. More information is available at
https://azure.microsoft.com/en-us/free/[Azure Portal].
-### URI Format
+== URI Format
[source,java]
------------------------------
@@ -31,7 +31,7 @@ from("azure-queue:/camelazure/messageQueue").
to("file://queuedirectory");
--------------------------------------------------------------------------------
-### URI Options
+== URI Options
// component options: START
@@ -67,7 +67,7 @@ azure-queue:containerAndQueueUri
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -77,7 +77,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (12 parameters):
+=== Query Parameters (12 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -98,7 +98,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -141,9 +141,9 @@ Required Azure Storage Queue Service component options
You have to provide the containerAndQueue URI and the credentials.
-### Usage
+== Usage
-#### Azure Queue Service operations
+=== Azure Queue Service operations
[width="100%",cols="20%,80%",options="header",]
|===
@@ -162,7 +162,7 @@ You have to provide the containerAndQueue URI and the credentials.
-#### Azure Queue Client configuration
+=== Azure Queue Client configuration
If your Camel Application is running behind a firewall or if you need to
have more control over the Azure Queue Client configuration, you can
@@ -185,7 +185,7 @@ from("azure-queue:/camelazure/messageQueue?azureQueueClient=#client")
.to("mock:result");
--------------------------------------------------------------------------------
-### Dependencies
+== Dependencies
Maven users will need to add the following dependency to their pom.xml.
@@ -202,7 +202,7 @@ Maven users will need to add the following dependency to their pom.xml.
where `${camel-version`} must be replaced by the actual version of Camel.
-### See Also
+== See Also
* Configuring Camel
* Component
diff --git a/components/camel-azure/src/main/docs/azure.adoc b/components/camel-azure/src/main/docs/azure.adoc
index fdf9a8b..bf6b77a 100644
--- a/components/camel-azure/src/main/docs/azure.adoc
+++ b/components/camel-azure/src/main/docs/azure.adoc
@@ -1,5 +1,5 @@
[[Azure-CamelComponentsforWindowsAzureServices]]
-== Camel Components for Windows Azure Services
+= Camel Components for Windows Azure Services
The Camel Components for https://azure.microsoft.com/[Windows Azure Services]
provide connectivity to Azure services from Camel.
diff --git a/components/camel-barcode/src/main/docs/barcode-dataformat.adoc b/components/camel-barcode/src/main/docs/barcode-dataformat.adoc
index 0e2c284..64f8e55 100644
--- a/components/camel-barcode/src/main/docs/barcode-dataformat.adoc
+++ b/components/camel-barcode/src/main/docs/barcode-dataformat.adoc
@@ -1,5 +1,5 @@
[[barcode-dataformat]]
-== Barcode DataFormat
+= Barcode DataFormat
*Available as of Camel version 2.14*
@@ -9,7 +9,7 @@ component is to create a barcode image from a String (marshal) and a
String from a barcode image (unmarshal). You're free to use all features
that zxing offers.
-### Dependencies
+== Dependencies
To use the barcode data format in your camel routes you need to add the
a dependency on *camel-barcode* which implements this data format.
@@ -27,7 +27,7 @@ the download page for the latest versions).
</dependency>
----------------------------------------
-### Barcode Options
+== Barcode Options
// dataformat options: START
The Barcode dataformat supports 5 options, which are listed below.
@@ -45,7 +45,7 @@ The Barcode dataformat supports 5 options, which are listed below.
|===
// dataformat options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -77,7 +77,7 @@ The component supports 6 options, which are listed below.
// spring-boot-auto-configure options: END
ND
-### Using the Java DSL
+== Using the Java DSL
First you have to initialize the barcode data fomat class. You can use
the default constructor, or one of parameterized (see JavaDoc). The
@@ -113,7 +113,7 @@ code.addToHintMap(DecodeHintType.TRY_HARDER, Boolean.true);
For possible hints, please consult the xzing documentation.
-#### Marshalling
+=== Marshalling
[source,java]
----------------------------
@@ -133,7 +133,7 @@ You should find inside the 'barcode_out' folder this image:
image:qr-code.png[image]
-#### Unmarshalling
+=== Unmarshalling
The unmarshaller is generic. For unmarshalling you can use any
BarcodeDataFormat instance. If you've two instances, one for
diff --git a/components/camel-base64/src/main/docs/base64-dataformat.adoc b/components/camel-base64/src/main/docs/base64-dataformat.adoc
index 5ede77f..82867db 100644
--- a/components/camel-base64/src/main/docs/base64-dataformat.adoc
+++ b/components/camel-base64/src/main/docs/base64-dataformat.adoc
@@ -1,11 +1,11 @@
[[base64-dataformat]]
-== Base64 DataFormat
+= Base64 DataFormat
*Available as of Camel version 2.11*
The Base64 data format is used for base64 encoding and decoding.
-=== Options
+== Options
// dataformat options: START
The Base64 dataformat supports 4 options, which are listed below.
@@ -22,7 +22,7 @@ The Base64 dataformat supports 4 options, which are listed below.
|===
// dataformat options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -82,7 +82,7 @@ Most of the time, you won't need to declare the data format if you use
the default options. In that case, you can declare the data format
inline as shown below.
-=== Marshal
+== Marshal
In this example we marshal the file content to base64 object.
@@ -104,7 +104,7 @@ In Spring DSL:
<to uri="jms://myqueue"/>
----
-=== Unmarshal
+== Unmarshal
In this example we unmarshal the payload from the JMS queue to a byte[]
object, before its processed by the newOrder processor.
@@ -127,7 +127,7 @@ In Spring DSL:
<to uri="bean:newOrder"/>
----
-=== Dependencies
+== Dependencies
To use Base64 in your Camel routes you need to add a dependency on
*camel-base64* which implements this data format.
diff --git a/components/camel-bean-validator/src/main/docs/bean-validator-component.adoc b/components/camel-bean-validator/src/main/docs/bean-validator-component.adoc
index 514f43a..9b41ca3 100644
--- a/components/camel-bean-validator/src/main/docs/bean-validator-component.adoc
+++ b/components/camel-bean-validator/src/main/docs/bean-validator-component.adoc
@@ -1,5 +1,5 @@
[[bean-validator-component]]
-== Bean Validator Component
+= Bean Validator Component
*Available as of Camel version 2.3*
@@ -23,7 +23,7 @@ for this component:
</dependency>
------------------------------------------------------------
-### URI format
+== URI format
[source,java]
------------------------------
@@ -41,7 +41,7 @@ Where *label* is an arbitrary text value describing the endpoint. +
You can append query options to the URI in the following format,
?option=value&option=value&...
-### URI Options
+== URI Options
// component options: START
@@ -68,7 +68,7 @@ bean-validator:label
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -78,7 +78,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (8 parameters):
+=== Query Parameters (8 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -95,7 +95,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -125,7 +125,7 @@ The component supports 3 options, which are listed below.
-### OSGi deployment
+== OSGi deployment
To use Hibernate Validator in the OSGi environment use dedicated
`ValidationProviderResolver` implementation, just as
@@ -149,7 +149,7 @@ If no custom `ValidationProviderResolver` is defined and the validator
component has been deployed into the OSGi environment,
the `HibernateValidationProviderResolver` will be automatically used.
-### Example
+== Example
Assumed we have a java bean with the following annotations
@@ -316,7 +316,7 @@ Note that the body should include an instance of a class to validate.
-### See Also
+== See Also
* Configuring Camel
* Component
diff --git a/components/camel-bean/src/main/docs/bean-component.adoc b/components/camel-bean/src/main/docs/bean-component.adoc
index f965353..6246a4b 100644
--- a/components/camel-bean/src/main/docs/bean-component.adoc
+++ b/components/camel-bean/src/main/docs/bean-component.adoc
@@ -1,11 +1,11 @@
[[bean-component]]
-== Bean Component
+= Bean Component
*Available as of Camel version 1.0*
The Bean component binds beans to Camel message exchanges.
-=== URI format
+== URI format
[source]
----
@@ -15,7 +15,7 @@ bean:beanName[?options]
Where *beanID* can be any string which is used to look up the bean in
the Registry
-=== Options
+== Options
// component options: START
@@ -43,7 +43,7 @@ bean:beanName
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -53,7 +53,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (6 parameters):
+=== Query Parameters (6 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -72,7 +72,7 @@ with the following path and query parameters:
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-=== Using
+== Using
The object instance that is used to consume messages must be explicitly
registered with the Registry. For example, if you
@@ -103,7 +103,7 @@ And the same route using Spring DSL:
</route>
----------------------------
-=== Bean as endpoint
+== Bean as endpoint
Camel also supports invoking xref:bean-component.adoc[Bean] as an Endpoint. In the
route below:
@@ -116,7 +116,7 @@ Camel will use Bean Binding to invoke the
`sayHello` method, by converting the Exchange's In body to the `String`
type and storing the output of the method on the Exchange Out body.
-=== Java DSL bean syntax
+== Java DSL bean syntax
Java DSL comes with syntactic sugar for the xref:bean-component.adoc[Bean]
component. Instead of specifying the bean explicitly as the endpoint
@@ -148,7 +148,7 @@ from("direct:start").bean(new ExampleBean(), "methodName");
from("direct:start").bean(ExampleBean.class);
---------------------------------------------------------------
-=== Bean Binding
+== Bean Binding
How bean methods to be invoked are chosen (if they are not specified
explicitly through the *method* parameter) and how parameter values are
diff --git a/components/camel-bean/src/main/docs/bean-language.adoc b/components/camel-bean/src/main/docs/bean-language.adoc
index 08023f6..5fd1bbc 100644
--- a/components/camel-bean/src/main/docs/bean-language.adoc
+++ b/components/camel-bean/src/main/docs/bean-language.adoc
@@ -1,5 +1,5 @@
[[bean-language]]
-== Bean method Language
+= Bean method Language
== Bean Language
*Available as of Camel version 1.3*
@@ -18,7 +18,7 @@ xref:manual::message.adoc[Message] Exchange to the method parameters; so you can
annotate the bean to extract headers or other expressions such as
xref:components::xpath-language.adoc[XPath] or xref:components::xquery-language.adoc[XQuery] from the message.
-=== Bean Language options
+== Bean Language options
// language options: START
The Bean method language supports 4 options, which are listed below.
@@ -37,7 +37,7 @@ The Bean method language supports 4 options, which are listed below.
[[BeanLanguage-UsingBeanExpressionsinJava]]
-=== Using Bean Expressions in Java
+== Using Bean Expressions in Java
[source,syntaxhighlighter-pre]
----
@@ -47,7 +47,7 @@ from("activemq:topic:OrdersTopic")
----
[[BeanLanguage-UsingBeanExpressionsinSpringXML]]
-=== Using Bean Expressions in Spring XML
+== Using Bean Expressions in Spring XML
[source,syntaxhighlighter-pre]
----
@@ -70,7 +70,7 @@ deprecated. Use the *`ref`* attribute instead.
====
[[BeanLanguage-WritingtheExpressionBean]]
-=== Writing the Expression Bean
+== Writing the Expression Bean
The bean in the above examples is just any old Java Bean with a method
called *`isGoldCustomer()`* that returns some object that is easily
@@ -110,7 +110,7 @@ xref:manual::message.adoc[Message] or individual headers, properties, the body
or other expressions.
[[BeanLanguage-Non-RegistryBeans]]
-=== Non-Registry Beans
+== Non-Registry Beans
The xref:bean-language.adoc[Bean Language] also supports invoking beans
that isn't registered in the xref:manual::registry.adoc[Registry]. This is
@@ -169,7 +169,7 @@ from("activemq:topic:OrdersTopic")
----
[[BeanLanguage-OtherExamples]]
-=== Other Examples
+== Other Examples
We have some test cases you can look at if it'll help
diff --git a/components/camel-bean/src/main/docs/class-component.adoc b/components/camel-bean/src/main/docs/class-component.adoc
index 498030b..d51336f 100644
--- a/components/camel-bean/src/main/docs/class-component.adoc
+++ b/components/camel-bean/src/main/docs/class-component.adoc
@@ -1,5 +1,5 @@
[[class-component]]
-== Class Component
+= Class Component
*Available as of Camel version 2.4*
@@ -8,7 +8,7 @@ in the same way as the xref:bean-component.adoc[Bean] component but instead of
looking up beans from a Registry it creates the bean
based on the class name.
-=== URI format
+== URI format
[source]
----
@@ -18,7 +18,7 @@ class:className[?options]
Where *className* is the fully qualified class name to create and use as
bean.
-=== Options
+== Options
// component options: START
@@ -46,7 +46,7 @@ class:beanName
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -56,7 +56,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (6 parameters):
+=== Query Parameters (6 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -72,7 +72,7 @@ with the following path and query parameters:
// endpoint options: END
-=== Using
+== Using
You simply use the *class* component just as the xref:bean-component.adoc[Bean]
component but by specifying the fully qualified classname instead. +
@@ -91,7 +91,7 @@ example `hello`:
from("direct:start").to("class:org.apache.camel.component.bean.MyFooBean?method=hello").to("mock:result");
--------------------------------------------------------------------------------------------------------------
-=== Setting properties on the created instance
+== Setting properties on the created instance
In the endpoint uri you can specify properties to set on the created
instance, for example if it has a `setPrefix` method:
@@ -120,7 +120,7 @@ id `foo` and invoke the `setCool` method on the created instance of the
TIP:See more details at the xref:bean-component.adoc[Bean] component as the *class*
component works in much the same way.
-=== See Also
+== See Also
* Configuring Camel
* Component
diff --git a/components/camel-beanio/src/main/docs/beanio-dataformat.adoc b/components/camel-beanio/src/main/docs/beanio-dataformat.adoc
index 12802f6..42d6a69 100644
--- a/components/camel-beanio/src/main/docs/beanio-dataformat.adoc
+++ b/components/camel-beanio/src/main/docs/beanio-dataformat.adoc
@@ -1,5 +1,5 @@
[[beanio-dataformat]]
-== BeanIO DataFormat
+= BeanIO DataFormat
*Available as of Camel version 2.10*
@@ -12,7 +12,7 @@ http://beanio.org/2.0/docs/reference/index.html#TheMappingFile[mappings
XML] file where you define the mapping from the flat format to Objects
(POJOs). This mapping file is mandatory to use.
-### Options
+== Options
// dataformat options: START
The BeanIO dataformat supports 9 options, which are listed below.
@@ -34,7 +34,7 @@ The BeanIO dataformat supports 9 options, which are listed below.
|===
// dataformat options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -70,13 +70,13 @@ The component supports 10 options, which are listed below.
// spring-boot-auto-configure options: END
ND
-### Usage
+== Usage
An example of a
https://svn.apache.org/repos/asf/camel/trunk/components/camel-beanio/src/test/resources/org/apache/camel/dataformat/beanio/mappings.xml[mapping
file is here].
-#### Using Java DSL
+=== Using Java DSL
To use the `BeanIODataFormat` you need to configure the data format with
the mapping file, as well the name of the stream. +
@@ -93,13 +93,13 @@ List<Employee> into a stream of CSV data.
The CSV data could for example be as below:
-#### Using XML DSL
+=== Using XML DSL
To use the BeanIO data format in XML, you need to configure it using the
<beanio> XML tag as shown below. The routes is similar to the example
above.
-### Dependencies
+== Dependencies
To use BeanIO in your Camel routes you need to add a dependency on
*camel-beanio* which implements this data format.
diff --git a/components/camel-beanstalk/src/main/docs/beanstalk-component.adoc b/components/camel-beanstalk/src/main/docs/beanstalk-component.adoc
index a1ffc00..9ea222e 100644
--- a/components/camel-beanstalk/src/main/docs/beanstalk-component.adoc
+++ b/components/camel-beanstalk/src/main/docs/beanstalk-component.adoc
@@ -1,5 +1,5 @@
[[beanstalk-component]]
-== Beanstalk Component
+= Beanstalk Component
*Available as of Camel version 2.15*
@@ -10,7 +10,7 @@ You can find the detailed explanation of Beanstalk job lifecycle
at http://github.com/kr/beanstalkd/blob/v1.3/doc/protocol.txt[Beanstalk
protocol].
-### Dependencies
+== Dependencies
Maven users need to add the following dependency to their `pom.xml`
@@ -25,7 +25,7 @@ Maven users need to add the following dependency to their `pom.xml`
where `${camel-version`} must be replaced by the actual version of Camel.
-### URI format
+== URI format
[source,xml]
------------------------------------------
@@ -52,7 +52,7 @@ details here].
By the way, you cannot specify several tubes when you are writing jobs
into Beanstalk.
-### Beanstalk options
+== Beanstalk options
@@ -82,7 +82,7 @@ beanstalk:connectionSettings
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -92,7 +92,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (28 parameters):
+=== Query Parameters (28 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -129,7 +129,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -188,7 +188,7 @@ Consumer] which means there is more options you can configure, such as
how frequent the consumer should poll. For more details
see Polling Consumer.
-### Consumer Headers
+== Consumer Headers
The consumer stores a number of job headers in the Exchange message:
@@ -218,7 +218,7 @@ queue
|_beanstalk.kicks_ |int |the number of times this job has been kicked
|=======================================================================
-### Examples
+== Examples
This Camel component lets you both request the jobs for processing and
supply them to Beanstalkd daemon. Our simple demo routes may look like
@@ -258,7 +258,7 @@ out of buried and/or delayed state to the normal queue.
-### See Also
+== See Also
* Configuring Camel
* Component
diff --git a/components/camel-bindy/src/main/docs/bindy-dataformat.adoc b/components/camel-bindy/src/main/docs/bindy-dataformat.adoc
index a39a824..825bd53 100644
--- a/components/camel-bindy/src/main/docs/bindy-dataformat.adoc
+++ b/components/camel-bindy/src/main/docs/bindy-dataformat.adoc
@@ -1,5 +1,5 @@
[[bindy-dataformat]]
-== Bindy DataFormat
+= Bindy DataFormat
*Available as of Camel version 2.0*
@@ -49,7 +49,7 @@ the Class or field.
As you configure bindy using class names instead of package names
you can put multiple models in the same package.
-=== Options
+== Options
// dataformat options: START
The Bindy dataformat supports 5 options, which are listed below.
@@ -67,7 +67,7 @@ The Bindy dataformat supports 5 options, which are listed below.
|===
// dataformat options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -113,7 +113,7 @@ ND
-=== Annotations
+== Annotations
The annotations created allow to map different concept of your model to
the POJO like :
@@ -131,7 +131,7 @@ financial messages),
This section will describe them :
-=== 1. CsvRecord
+== 1. CsvRecord
The CsvRecord annotation is used to identified the root class of the
model. It represents a record = a line of a CSV file and can be linked
@@ -384,7 +384,7 @@ public Class Order {
Remark : pos is used to parse the file, stream while positions is used
to generate the CSV
-=== 2. Link
+== 2. Link
The link annotation will allow to link objects together.
@@ -436,7 +436,7 @@ public class Client {
}
----
-=== 3. DataField
+== 3. DataField
The DataField annotation defines the property of the field. Each
datafield is identified by its position in the record, a type (string,
@@ -730,7 +730,7 @@ public class Order {
This attribute is only applicable to optional fields.
-=== 4. FixedLengthRecord
+== 4. FixedLengthRecord
The FixedLengthRecord annotation is used to identified the root class of
the model. It represents a record = a line of a file/message containing
@@ -1173,7 +1173,7 @@ public static class Order {
}
----
-=== 5. Message
+== 5. Message
The Message annotation is used to identified the class of your model who
will contain key value pairs fields. This kind of format is used mainly
@@ -1209,7 +1209,7 @@ project http://www.quickfixj.org/[http://www.quickfixj.org/].
|keyValuePairSeparair |string |mandatory - can be '\u0001', '\u0009', '#' or 'anything'
|crlf |string |optional - possible values = WINDOWS,UNIX,MAC, or custom; default value
-= WINDOWS - allow to define the carriage return character to use. If you
+== WINDOWS - allow to define the carriage return character to use. If you
specify a value other than the three listed before, the value you enter
(custom) will be used as the CRLF character(s)
@@ -1254,7 +1254,7 @@ message looks like (src\test\data\fix\fix.txt) and the Order, Trailer,
Header classes
(src\test\java\org\apache\camel\dataformat\bindy\model\fix\simple\Order.java)
-=== 6. KeyValuePairField
+== 6. KeyValuePairField
The KeyValuePairField annotation defines the property of a key value
pair field. Each KeyValuePairField is identified by a tag (= key) and
@@ -1350,7 +1350,7 @@ public class Order {
}
----
-=== 7. Section
+== 7. Section
In FIX message of fixed length records, it is common to have different
sections in the representation of the information : header, body and
@@ -1432,7 +1432,7 @@ public class Trailer {
}
----
-=== 8. OneToMany
+== 8. OneToMany
The purpose of the annotation @OneToMany is to allow to work with a
`List<?>` field defined a POJO class or from a record containing
@@ -1566,7 +1566,7 @@ public class Security {
}
----
-=== 9. BindyConverter
+== 9. BindyConverter
The purpose of the annotation @BindyConverter is define a converter
to be used on field level. The provided class must implement the
@@ -1594,7 +1594,7 @@ public static class CustomConverter implements Format<String> {
}
----
-=== 10. FormatFactories
+== 10. FormatFactories
The purpose of the annotation @FormatFactories is to define a set of converters
at record-level. The provided classes must implement the FormatFactoryInterface interface.
@@ -1645,7 +1645,7 @@ public static class OrderNumberFormatFactory extends AbstractFormatFactory {
}
----
-=== Supported Datatypes
+== Supported Datatypes
The DefaultFormatFactory makes formatting of the following datatype available by
returning an instance of the interface FormatFactoryInterface based on the provided
@@ -1671,7 +1671,7 @@ FormattingOptions:
The DefaultFormatFactory can be overridden by providing an instance of
FactoryRegistry in the registry in use (e.g. spring or JNDI).
-=== Using the Java DSL
+== Using the Java DSL
The next step instantiates the DataFormat _bindy_ class
associated with this record type and providing a class as a parameter.
@@ -1686,7 +1686,7 @@ configured in this package.
DataFormat bindy = new BindyCsvDataFormat(com.acme.model.MyModel.class);
----
-==== Setting locale
+=== Setting locale
Bindy supports configuring the locale on the dataformat, such as
@@ -1707,7 +1707,7 @@ BindyCsvDataFormat bindy = new BindyCsvDataFormat(com.acme.model.MyModel.class);
bindy.setLocale("default");
----
-==== Unmarshaling
+=== Unmarshaling
[source,java]
----
@@ -1791,7 +1791,7 @@ from("file://inbox?charset=Cp922")
.to("direct:handleOrders");
----
-==== Marshaling
+=== Marshaling
To generate CSV records from a collection of model objects, you create
the following route :
@@ -1803,7 +1803,7 @@ from("direct:handleOrders")
.to("file://outbox")
----
-=== Using Spring XML
+== Using Spring XML
This is really easy to use Spring as your favorite DSL language to
declare the routes to be used for camel-bindy. The following example
@@ -1857,7 +1857,7 @@ content to generate a file containing the csv record.
NOTE: Please verify that your model classes implements serializable otherwise
the queue manager will raise an error
-=== Dependencies
+== Dependencies
To use Bindy in your camel routes you need to add the a dependency on
*camel-bindy* which implements this data format.
diff --git a/components/camel-blueprint/src/main/docs/blueprint.adoc b/components/camel-blueprint/src/main/docs/blueprint.adoc
index e372c74..dc091e3 100644
--- a/components/camel-blueprint/src/main/docs/blueprint.adoc
+++ b/components/camel-blueprint/src/main/docs/blueprint.adoc
@@ -1,10 +1,10 @@
-## Using OSGi blueprint with Camel
+= Using OSGi blueprint with Camel
A custom XML namespace for Blueprint has been created to let you leverage the nice XML dialect.
Given Blueprint custom namespaces are not standardized yet, this namespace can only be used on the Apache Aries Blueprint
implementation, which is the one used by Apache Karaf.
-### Overview
+== Overview
The XML schema is mostly the same as the one for Spring, so all the xml snippets throughout the documentation
referring to Spring XML also apply to Blueprint routes.
@@ -37,7 +37,7 @@ However, using blueprint when you deploy your applications in an OSGi enviroment
- you can use Blueprint property placeholders
-### Using camel-blueprint
+== Using camel-blueprint
To leverage camel-blueprint in OSGi, you only need the Aries Blueprint bundle and the camel-blueprint bundle,
in addition to camel-core and its dependencies.
diff --git a/components/camel-bonita/src/main/docs/bonita-component.adoc b/components/camel-bonita/src/main/docs/bonita-component.adoc
index 41f7237..6d0177f 100644
--- a/components/camel-bonita/src/main/docs/bonita-component.adoc
+++ b/components/camel-bonita/src/main/docs/bonita-component.adoc
@@ -1,11 +1,11 @@
[[bonita-component]]
-== Bonita Component
+= Bonita Component
*Available as of Camel version 2.19*
Used for communicating with a remote Bonita BPM process engine.
-### URI format
+== URI format
[source,java]
------------------------------
@@ -14,7 +14,7 @@ bonita://[operation]?[options]
Where *operation* is the specific action to perform on Bonita.
-### General Options
+== General Options
// component options: START
The Bonita component supports 2 options, which are listed below.
@@ -39,7 +39,7 @@ bonita:operation
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -49,7 +49,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (10 parameters):
+=== Query Parameters (10 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -68,7 +68,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -97,12 +97,12 @@ The component supports 3 options, which are listed below.
// spring-boot-auto-configure options: END
-### Body content
+== Body content
For the startCase operation, the input variables are retrieved from the body message. This one has to contains a Map<String,Serializable>.
-### Examples
+== Examples
The following example start a new case in Bonita:
@@ -111,7 +111,7 @@ The following example start a new case in Bonita:
from("direct:start").to("bonita:startCase?hostname=localhost&port=8080&processName=TestProcess&username=install&password=install")
----------------------------------------------------------------------
-### Dependencies
+== Dependencies
To use Bonita in your Camel routes you need to add a dependency on
*camel-bonita*, which implements the component.
diff --git a/components/camel-boon/src/main/docs/boon-dataformat.adoc b/components/camel-boon/src/main/docs/boon-dataformat.adoc
index 87ac271..40c9bd8 100644
--- a/components/camel-boon/src/main/docs/boon-dataformat.adoc
+++ b/components/camel-boon/src/main/docs/boon-dataformat.adoc
@@ -1,5 +1,5 @@
[[boon-dataformat]]
-== Boon DataFormat
+= Boon DataFormat
*Available as of Camel version 2.16*
@@ -11,7 +11,7 @@ simple
and https://github.com/RichardHightower/json-parsers-benchmark[fast
parser] than other common parsers currently used.
-### Options
+== Options
@@ -30,7 +30,7 @@ The Boon dataformat supports 3 options, which are listed below.
|===
// dataformat options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -64,7 +64,7 @@ ND
-### Using the Java DSL
+== Using the Java DSL
[source,java]
------------------------------------------------------------------------
@@ -75,7 +75,7 @@ from("activemq:My.Queue")
.to("mqseries:Another.Queue");
------------------------------------------------------------------------
-### Using Blueprint XML
+== Using Blueprint XML
[source,java]
---------------------------------------------------------------------------------
@@ -92,7 +92,7 @@ from("activemq:My.Queue")
</camelContext>
---------------------------------------------------------------------------------
-### Dependencies
+== Dependencies
[source,java]
-------------------------------------
diff --git a/components/camel-box/camel-box-component/src/main/docs/box-component.adoc b/components/camel-box/camel-box-component/src/main/docs/box-component.adoc
index d6ce566..3adc3bc 100644
--- a/components/camel-box/camel-box-component/src/main/docs/box-component.adoc
+++ b/components/camel-box/camel-box-component/src/main/docs/box-component.adoc
@@ -1,5 +1,5 @@
[[box-component]]
-== Box Component
+= Box Component
*Available as of Camel version 2.14*
@@ -29,23 +29,23 @@ for this component:
</dependency>
----
-=== Connection Authentication Types
+== Connection Authentication Types
The Box component supports three different types of authenticated connections.
-==== Standard Authentication
+=== Standard Authentication
*Standard Authentication* uses the *OAuth 2.0 three-legged authentication process* to authenticate its connections with Box.com. This type of authentication enables Box *managed users* and *external users* to access, edit, and save their Box content through the Box component.
-==== App Enterprise Authentication
+=== App Enterprise Authentication
*App Enterprise Authentication* uses the *OAuth 2.0 with JSON Web Tokens (JWT)* to authenticate its connections as a *Service Account* for a *Box Application*. This type of authentication enables a service account to access, edit, and save the Box content of its *Box Application* through the Box component.
-==== App User Authentication
+=== App User Authentication
*App User Authentication* uses the *OAuth 2.0 with JSON Web Tokens (JWT)* to authenticate its connections as an *App User* for a *Box Application*. This type of authentication enables app users to access, edit, and save their Box content in its *Box Application* through the Box component.
-=== Box Options
+== Box Options
// component options: START
The Box component supports 3 options, which are listed below.
@@ -70,7 +70,7 @@ box:apiName/methodName
with the following path and query parameters:
-==== Path Parameters (2 parameters):
+=== Path Parameters (2 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -81,7 +81,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (22 parameters):
+=== Query Parameters (22 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -112,7 +112,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -157,7 +157,7 @@ The component supports 20 options, which are listed below.
|===
// spring-boot-auto-configure options: END
-=== URI format
+== URI format
[source]
----
@@ -178,7 +178,7 @@ apiName can be one of:
* users
-=== Producer Endpoints:
+== Producer Endpoints:
Producer endpoints can use endpoint prefixes followed by endpoint names
and associated options described next. A shorthand alias can be used for
@@ -206,7 +206,7 @@ RuntimeCamelException with a
*com.box.sdk.BoxAPIException* derived exception
cause.
-==== Endpoint Prefix _collaborations_
+=== Endpoint Prefix _collaborations_
For more information on Box collaborations see
https://developer.box.com/reference#collaboration-object[https://developer.box.com/reference#collaboration-object]. The
@@ -257,7 +257,7 @@ URI Options for _collaborations_
|info |com.box.sdk.BoxCollaboration.Info
|===
-==== Endpoint Prefix _comments_
+=== Endpoint Prefix _comments_
For more information on Box comments see
https://developer.box.com/reference#comment-object[https://developer.box.com/reference#comment-object]. The
@@ -301,7 +301,7 @@ URI Options for _collaborations_
|===
-==== Endpoint Prefix _events-logs_
+=== Endpoint Prefix _events-logs_
For more information on Box event logs see
https://developer.box.com/reference#events[https://developer.box.com/reference#events].
@@ -334,7 +334,7 @@ URI Options for _event-logs_
|types |com.box.sdk.BoxEvent.Types[]
|===
-==== Endpoint Prefix _files_
+=== Endpoint Prefix _files_
For more information on Box files see
https://developer.box.com/reference#file-object[https://developer.box.com/reference#file-object].
@@ -454,7 +454,7 @@ URI Options for _files_
|typeName |String
|===
-==== Endpoint Prefix _folders_
+=== Endpoint Prefix _folders_
For more information on Box folders see
https://developer.box.com/reference#folder-object[https://developer.box.com/reference#folder-object].
@@ -530,7 +530,7 @@ URI Options for _folders_
|permissions |com.box.sdk.BoxSharedLink.Permissions
|===
-==== Endpoint Prefix _groups_
+=== Endpoint Prefix _groups_
For more information on Box groups see
https://developer.box.com/reference#group-object[https://developer.box.com/reference#group-object].
@@ -589,7 +589,7 @@ URI Options for _groups_
|===
-==== Endpoint Prefix _search_
+=== Endpoint Prefix _search_
For more information on Box search API see
https://developer.box.com/reference#searching-for-content[https://developer.box.com/reference#searching-for-content]. The
@@ -619,7 +619,7 @@ URI Options for _search_
|query |String
|===
-==== Endpoint Prefix _tasks_
+=== Endpoint Prefix _tasks_
For information on Box tasks see
https://developer.box.com/reference#task-object-1[https://developer.box.com/reference#task-object-1].
@@ -677,7 +677,7 @@ URI Options for _tasks_
|taskAssignmentId |String
|===
-==== Endpoint Prefix _users_
+=== Endpoint Prefix _users_
For information on Box users see
https://developer.box.com/reference#user-object[https://developer.box.com/reference#user-object].
@@ -747,7 +747,7 @@ URI Options for _users_
|userId |String
|===
-=== Consumer Endpoints:
+== Consumer Endpoints:
For more information on Box events see
https://developer.box.com/reference#events[https://developer.box.com/reference#events].
@@ -775,18 +775,18 @@ URI Options for _events_
|startingPosition |Long
|===
-=== Message header
+== Message header
Any of the options can be provided in a message header for producer
endpoints with *CamelBox.* prefix.
-=== Message body
+== Message body
All result message bodies utilize objects provided by the Box Java SDK.
Producer endpoints can specify the option name for incoming message body
in the *inBody* endpoint parameter.
-=== Samples
+== Samples
The following route uploads new files to the user's root folder:
diff --git a/components/camel-braintree/src/main/docs/braintree-component.adoc b/components/camel-braintree/src/main/docs/braintree-component.adoc
index 44429fa..b189513 100644
--- a/components/camel-braintree/src/main/docs/braintree-component.adoc
+++ b/components/camel-braintree/src/main/docs/braintree-component.adoc
@@ -1,5 +1,5 @@
[[braintree-component]]
-== Braintree Component
+= Braintree Component
*Available as of Camel version 2.17*
@@ -30,7 +30,7 @@ for this component:
-### Braintree Options
+== Braintree Options
@@ -62,7 +62,7 @@ braintree:apiName/methodName
with the following path and query parameters:
-==== Path Parameters (2 parameters):
+=== Path Parameters (2 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -73,7 +73,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (16 parameters):
+=== Query Parameters (16 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -98,7 +98,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -140,7 +140,7 @@ The component supports 15 options, which are listed below.
-### URI format
+== URI format
@@ -173,7 +173,7 @@ Endpoint prefix can be one of:
-### BraintreeComponent
+== BraintreeComponent
The Braintree Component can be configured with the options below. These
options can be provided using the component's bean
@@ -201,7 +201,7 @@ of the environment, merchantId, publicKey and privateKey options.
All the options above are provided by Braintree Payments
-### Producer Endpoints:
+== Producer Endpoints:
Producer endpoints can use endpoint prefixes followed by endpoint names
and associated options described next. A shorthand alias can be used for
@@ -225,7 +225,7 @@ at https://developers.braintreepayments.com/reference/overview[https://develope
-#### Endpoint prefix _addOn_
+=== Endpoint prefix _addOn_
The following endpoints can be invoked with the prefix *addOn* as
follows:
@@ -243,7 +243,7 @@ braintree://addOn/endpoint
|all | | |List<com.braintreegateway.Addon>
|====================================================
-#### Endpoint prefix _address_
+=== Endpoint prefix _address_
The following endpoints can be invoked with the prefix *address* as
follows:
@@ -281,7 +281,7 @@ URI Options for _address_
|id |String
|============================================
-#### Endpoint prefix _clientToken_
+=== Endpoint prefix _clientToken_
The following endpoints can be invoked with the prefix *clientToken* as
follows:
@@ -308,7 +308,7 @@ URI Options for _clientToken_
|request |com.braintreegateway.ClientTokenrequest
|================================================
-#### Endpoint prefix _creditCardVerification_
+=== Endpoint prefix _creditCardVerification_
The following endpoints can be invoked with the
prefix *creditCardverification* as follows:
@@ -339,7 +339,7 @@ URI Options for _creditCardVerification_
|query |com.braintreegateway.CreditCardVerificationSearchRequest
|===============================================================
-#### Endpoint prefix _customer_
+=== Endpoint prefix _customer_
The following endpoints can be invoked with the prefix *customer* as
follows:
@@ -382,7 +382,7 @@ URI Options for _customer_
|query |com.braintreegateway.CustomerSearchRequest
|=================================================
-#### Endpoint prefix _discount_
+=== Endpoint prefix _discount_
The following endpoints can be invoked with the prefix *discount* as
follows:
@@ -404,7 +404,7 @@ braintree://discount/endpoint
+
-#### Endpoint prefix _dispute_
+=== Endpoint prefix _dispute_
The following endpoints can be invoked with the prefix *dispute* as
follows:
@@ -461,7 +461,7 @@ URI Options for _dispute_
|==========================================================
-#### Endpoint prefix _documentUpload_
+=== Endpoint prefix _documentUpload_
The following endpoints can be invoked with the prefix *documentUpload* as
follows:
@@ -488,7 +488,7 @@ URI Options for _documentUpload_
|==========================================================
-#### Endpoint prefix _merchantAccount_
+=== Endpoint prefix _merchantAccount_
The following endpoints can be invoked with the
prefix *merchantAccount* as follows:
@@ -526,7 +526,7 @@ URI Options for _merchantAccount_
|currencyRequest |com.braintreegateway.MerchantAccountCreateForCurrencyRequest
|====================================================
-#### Endpoint prefix _paymentMethod_
+=== Endpoint prefix _paymentMethod_
The following endpoints can be invoked with the
prefix *paymentMethod* as follows:
@@ -564,7 +564,7 @@ URI Options for _paymentMethod_
|deleteRequest |com.braintreegateway.PaymentMethodDeleteRequest
|==================================================
-#### Endpoint prefix _paymentMethodNonce_
+=== Endpoint prefix _paymentMethodNonce_
The following endpoints can be invoked with the
prefix *paymentMethodNonce* as follows:
@@ -595,7 +595,7 @@ URI Options for _paymentMethodNonce_
|paymentMethodNonce |String
|==========================
-#### Endpoint prefix _plan_
+=== Endpoint prefix _plan_
The following endpoints can be invoked with the prefix *plan* as
follows:
@@ -614,7 +614,7 @@ braintree://plan/endpoint
|====================================================
-#### Endpoint prefix _report_
+=== Endpoint prefix _report_
The following endpoints can be invoked with the prefix *report* as
follows:
@@ -640,7 +640,7 @@ URI Options for _report_
|==============================================================
-#### Endpoint prefix _settlementBatchSummary_
+=== Endpoint prefix _settlementBatchSummary_
The following endpoints can be invoked with the
prefix *settlementBatchSummary* as follows:
@@ -669,7 +669,7 @@ URI Options for _settlementBatchSummary_
|groupByCustomField |String
|==========================
-#### Endpoint prefix _subscription_
+=== Endpoint prefix _subscription_
The following endpoints can be invoked with the prefix *subscription* as
follows:
@@ -721,7 +721,7 @@ URI Options for _subscription_
-#### Endpoint prefix _transaction_
+=== Endpoint prefix _transaction_
The following endpoints can be invoked with the prefix *transaction* as
follows:
@@ -786,7 +786,7 @@ URI Options for _transaction_
|query |com.braintreegateway.TransactionSearchRequest
|==========================================================
-#### Endpoint prefix _webhookNotification_
+=== Endpoint prefix _webhookNotification_
The following endpoints can be invoked with the
prefix *webhookNotification* as follows:
@@ -818,7 +818,7 @@ URI Options for _webhookNotification_
-### Consumer Endpoints
+== Consumer Endpoints
Any of the producer endpoints can be used as a consumer endpoint.
Consumer endpoints can
@@ -830,12 +830,12 @@ be executed once for each exchange. To change this behavior use the
property *consumer.splitResults=true* to return a single exchange for
the entire list or array.
-### Message Headers
+== Message Headers
Any URI option can be provided in a message header for producer
endpoints with a *CamelBraintree.* prefix.
-### Message body
+== Message body
All result message bodies utilize objects provided by the Braintree Java
SDK. Producer endpoints can specify the option name for incoming message
@@ -845,7 +845,7 @@ body in the *inBody* endpoint parameter.
-### Examples
+== Examples
*Blueprint*
@@ -885,7 +885,7 @@ body in the *inBody* endpoint parameter.
</blueprint>
--------------------------------------------------------------------------------------------------------------------------------------------
-### See Also
+== See Also
*
https://cwiki.apache.org/confluence/display/CAMEL/Configuring+Camel[Configuring
diff --git a/components/camel-browse/src/main/docs/browse-component.adoc b/components/camel-browse/src/main/docs/browse-component.adoc
index b0bc715..e773f0a 100644
--- a/components/camel-browse/src/main/docs/browse-component.adoc
+++ b/components/camel-browse/src/main/docs/browse-component.adoc
@@ -1,5 +1,5 @@
[[browse-component]]
-== Browse Component
+= Browse Component
*Available as of Camel version 1.3*
@@ -8,7 +8,7 @@ BrowsableEndpoint which can be useful for
testing, visualisation tools or debugging. The exchanges sent to the
endpoint are all available to be browsed.
-=== URI format
+== URI format
[source]
-------------------------
@@ -18,7 +18,7 @@ browse:someName[?options]
Where *someName* can be any string to uniquely identify the endpoint.
-=== Options
+== Options
// component options: START
@@ -45,7 +45,7 @@ browse:name
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -55,7 +55,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (6 parameters):
+=== Query Parameters (6 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -71,7 +71,7 @@ with the following path and query parameters:
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -99,7 +99,7 @@ The component supports 3 options, which are listed below.
|===
// spring-boot-auto-configure options: END
-=== Sample
+== Sample
In the route below, we insert a `browse:` component to be able to browse
the Exchanges that are passing through:
@@ -127,7 +127,7 @@ public void inspectRecievedOrders() {
}
----
-=== See Also
+== See Also
* Configuring Camel
* Component
diff --git a/components/camel-caffeine/src/main/docs/caffeine-cache-component.adoc b/components/camel-caffeine/src/main/docs/caffeine-cache-component.adoc
index dcb2cdb..adba693 100644
--- a/components/camel-caffeine/src/main/docs/caffeine-cache-component.adoc
+++ b/components/camel-caffeine/src/main/docs/caffeine-cache-component.adoc
@@ -1,5 +1,5 @@
[[caffeine-cache-component]]
-== Caffeine Cache Component
+= Caffeine Cache Component
*Available as of Camel version 2.20*
@@ -19,7 +19,7 @@ their `pom.xml` for this component:
</dependency>
------------------------------------------------------------
-### URI format
+== URI format
[source,java]
-----------------------------
@@ -29,7 +29,7 @@ caffeine-cache://cacheName[?options]
You can append query options to the URI in the following
format, `?option=value&option=#beanRef&...`
-### Options
+== Options
// component options: START
@@ -57,7 +57,7 @@ caffeine-cache:cacheName
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -67,7 +67,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (21 parameters):
+=== Query Parameters (21 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -97,7 +97,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -141,7 +141,7 @@ The component supports 18 options, which are listed below.
// spring-boot-auto-configure options: END
-### Examples
+== Examples
You can use your cache with the following code:
@@ -163,7 +163,7 @@ You can use your cache with the following code:
In this way you'll work always on the same cache in the registry.
-### Check operation result
+== Check operation result
Each time you'll use an operation on the cache you'll have two different headers to check for status:
diff --git a/components/camel-caffeine/src/main/docs/caffeine-loadcache-component.adoc b/components/camel-caffeine/src/main/docs/caffeine-loadcache-component.adoc
index d65d776..f029b77 100644
--- a/components/camel-caffeine/src/main/docs/caffeine-loadcache-component.adoc
+++ b/components/camel-caffeine/src/main/docs/caffeine-loadcache-component.adoc
@@ -1,5 +1,5 @@
[[caffeine-loadcache-component]]
-== Caffeine LoadCache Component
+= Caffeine LoadCache Component
*Available as of Camel version 2.20*
@@ -19,7 +19,7 @@ their `pom.xml` for this component:
</dependency>
------------------------------------------------------------
-### URI format
+== URI format
[source,java]
-----------------------------
@@ -29,7 +29,7 @@ caffeine-loadcache://cacheName[?options]
You can append query options to the URI in the following
format, `?option=value&option=#beanRef&...`
-### Options
+== Options
// component options: START
@@ -57,7 +57,7 @@ caffeine-loadcache:cacheName
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -67,7 +67,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (21 parameters):
+=== Query Parameters (21 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -97,7 +97,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
diff --git a/components/camel-cassandraql/src/main/docs/cql-component.adoc b/components/camel-cassandraql/src/main/docs/cql-component.adoc
index d8d6df3..7f26053 100644
--- a/components/camel-cassandraql/src/main/docs/cql-component.adoc
+++ b/components/camel-cassandraql/src/main/docs/cql-component.adoc
@@ -1,5 +1,5 @@
[[cql-component]]
-== Cassandra CQL Component
+= Cassandra CQL Component
*Available as of Camel version 2.15*
@@ -31,7 +31,7 @@ Maven users will need to add the following dependency to their
</dependency>
------------------------------------------------------------
-=== URI format
+== URI format
The endpoint can initiate the Cassandra connection or use an existing
one.
@@ -51,7 +51,7 @@ To fine tune the Cassandra connection (SSL options, pooling options,
load balancing policy, retry policy, reconnection policy...), create
your own Cluster instance and give it to the Camel endpoint.
-=== Cassandra Options
+== Cassandra Options
// component options: START
@@ -78,7 +78,7 @@ cql:beanRef:hosts:port/keyspace
with the following path and query parameters:
-==== Path Parameters (4 parameters):
+=== Path Parameters (4 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -91,7 +91,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (31 parameters):
+=== Query Parameters (31 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -131,7 +131,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -159,9 +159,9 @@ The component supports 3 options, which are listed below.
|===
// spring-boot-auto-configure options: END
-=== Messages
+== Messages
-==== Incoming Message
+=== Incoming Message
The Camel Cassandra endpoint expects a bunch of simple objects (`Object`
or `Object[]` or `Collection<Object>`) which will be bound to the CQL
@@ -173,7 +173,7 @@ Headers:
* `CamelCqlQuery` (optional, `String` or `RegularStatement`): CQL query
either as a plain String or built using the `QueryBuilder`.
-==== Outgoing Message
+=== Outgoing Message
The Camel Cassandra endpoint produces one or many a Cassandra Row
objects depending on the `resultSetConversionStrategy`:
@@ -186,7 +186,7 @@ objects depending on the `resultSetConversionStrategy`:
* Anything else, if `resultSetConversionStrategy` is a custom
implementation of the `ResultSetConversionStrategy`
-=== Repositories
+== Repositories
Cassandra can be used to store message keys or messages for the
idempotent and aggregation EIP.
@@ -197,7 +197,7 @@ anti-patterns queues and queue like datasets]. It's advised to use
LeveledCompaction and a small GC grace setting for these tables to allow
tombstoned rows to be removed quickly.
-=== Idempotent repository
+== Idempotent repository
The `NamedCassandraIdempotentRepository` stores messages keys in a
Cassandra table like this:
@@ -239,7 +239,7 @@ Alternatively, the `CassandraIdempotentRepository` does not have a
`LOCAL_QUORUM`…
|=======================================================================
-=== Aggregation repository
+== Aggregation repository
The `NamedCassandraAggregationRepository` stores exchanges by
correlation key in a Cassandra table like this:
@@ -284,7 +284,7 @@ Alternatively, the `CassandraAggregationRepository` does not have a
`LOCAL_QUORUM`…
|=======================================================================
-=== Examples
+== Examples
To insert something on a table you can use the following code:
diff --git a/components/camel-cbor/src/main/docs/cbor-dataformat.adoc b/components/camel-cbor/src/main/docs/cbor-dataformat.adoc
index 173d0f7..05e3651 100644
--- a/components/camel-cbor/src/main/docs/cbor-dataformat.adoc
+++ b/components/camel-cbor/src/main/docs/cbor-dataformat.adoc
@@ -1,5 +1,5 @@
[[cbor-dataformat]]
-== CBOR DataFormat
+= CBOR DataFormat
*Available as of Camel version 3.0*
@@ -16,7 +16,7 @@ from("activemq:My.Queue").
to("mqseries:Another.Queue");
-------------------------------
-### CBOR Options
+== CBOR Options
// dataformat options: START
The CBOR dataformat supports 11 options, which are listed below.
@@ -40,7 +40,7 @@ The CBOR dataformat supports 11 options, which are listed below.
|===
// dataformat options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -77,7 +77,7 @@ The component supports 12 options, which are listed below.
|===
// spring-boot-auto-configure options: END
-#### Using CBOR in Spring DSL
+=== Using CBOR in Spring DSL
When using Data Format in Spring DSL you need to
declare the data formats first. This is done in the *DataFormats* XML
@@ -103,7 +103,7 @@ And then you can refer to this id in the route:
</route>
-------------------------------------
-### Dependencies
+== Dependencies
[source,java]
-------------------------------------
diff --git a/components/camel-cdi/src/main/docs/cdi.adoc b/components/camel-cdi/src/main/docs/cdi.adoc
index 05cf6548..ebcac6f 100644
--- a/components/camel-cdi/src/main/docs/cdi.adoc
+++ b/components/camel-cdi/src/main/docs/cdi.adoc
@@ -1,5 +1,5 @@
[[cdi-component]]
-== Camel CDI
+= Camel CDI
The Camel CDI component provides auto-configuration for Apache Camel
using CDI as dependency injection framework based
@@ -22,7 +22,7 @@ Camel CDI testing.
camel-cdi is deprecated in OSGi and not supported. Use OSGi Blueprint if using Camel with OSGi.
====
-=== Auto-configured Camel context
+== Auto-configured Camel context
Camel CDI automatically deploys and configures a `CamelContext` bean.
That `CamelContext` bean is automatically instantiated, configured and
@@ -43,7 +43,7 @@ Note that this bean can be customized programmatically and other Camel
context beans can be deployed in the application as well.
[[CDI-Auto-detectingCamelroutes]]
-=== Auto-detecting Camel routes
+== Auto-detecting Camel routes
Camel CDI automatically collects all the `RoutesBuilder` beans in the
application, instantiates and add them to the `CamelContext` bean
@@ -84,7 +84,7 @@ static void configuration(@Observes CdiCamelConfiguration configuration) {
}
----
-=== Auto-configured Camel primitives
+== Auto-configured Camel primitives
Camel CDI provides beans for common Camel primitives that can be
injected in any CDI beans, e.g.:
@@ -110,7 +110,7 @@ Endpoint endpoint;
TypeConverter converter;
----
-=== Camel context configuration
+== Camel context configuration
If you just want to change the name of the default `CamelContext` bean,
you can used the `@ContextName` qualifier provided by Camel CDI, e.g.:
@@ -207,7 +207,7 @@ class ManualStartupCamelContext extends DefaultCamelContext {
}
----
-=== Configuration properties
+== Configuration properties
To configure the sourcing of the configuration properties used by Camel
to resolve properties placeholders, you can declare
@@ -258,7 +258,7 @@ You can see the `camel-example-cdi-properties` example for a working
example of a Camel CDI application using DeltaSpike configuration
mechanism.
-=== Auto-configured type converters
+== Auto-configured type converters
CDI beans annotated with the `@Converter` annotation are automatically
registered into the deployed Camel contexts, e.g.:
@@ -277,9 +277,9 @@ public class MyTypeConverter {
Note that CDI injection is supported within the type converters.
-=== Camel bean integration
+== Camel bean integration
-==== Camel annotations
+=== Camel annotations
As part of the Camel http://camel.apache.org/bean-integration.html[bean
integration], Camel comes with a set
@@ -397,7 +397,7 @@ void consume(@Body String body) {
|
|===
-==== Bean component
+=== Bean component
You can refer to CDI beans, either by type or name, From the Camel DSL,
e.g. with the Java Camel DSL:
@@ -423,7 +423,7 @@ class MyNamedBean {
from("direct:inbound").bean("foo");
----
-==== Referring beans from Endpoint URIs
+=== Referring beans from Endpoint URIs
When configuring endpoints using the URI syntax you can refer to beans
in the Registry using the `pass:[#]` notation. If the URI
@@ -451,7 +451,7 @@ PlatformTransactionManager createTransactionManager(TransactionManager transacti
}
----
-=== Camel events to CDI events
+== Camel events to CDI events
Camel provides a set
of http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/management/event/package-summary.html[management
@@ -516,7 +516,7 @@ Note that the support for Camel events translation into CDI events is
only activated if observer methods listening for Camel events are
detected in the deployment, and that per Camel context.
-=== CDI events endpoint
+== CDI events endpoint
The CDI event endpoint bridges
the http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#events[CDI
@@ -660,7 +660,7 @@ endpoint instances and the observer methods as the CDI container doesn't
have any ways of discovering the Camel context model during the
deployment phase.
-=== Camel XML configuration import
+== Camel XML configuration import
While CDI favors a typesafe dependency injection mechanism, it may be
useful to reuse existing Camel XML configuration files into a Camel CDI
@@ -743,7 +743,7 @@ configuration, e.g.:
----
-=== Transaction support
+== Transaction support
Camel CDI provides support for Camel transactional client using JTA.
@@ -767,7 +767,7 @@ Note that, for the time being, the transaction manager is looked up as JNDI reso
More flexible strategies will be added in the future to support a wider range of deployment scenarios.
====
-==== Transaction policies
+=== Transaction policies
Camel CDI provides implementation for the typically supported Camel `TransactedPolicy` as CDI beans. It is possible to have these policies looked up by name using the transacted EIP, e.g.:
@@ -817,7 +817,7 @@ The list of supported transaction policy names is:
- `PROPAGATION_NESTED`,
- `PROPAGATION_MANDATORY`.
-==== Transactional error handler
+=== Transactional error handler
Camel CDI provides a transactional error handler that extends the redelivery error handler, forces a rollback whenever an exception occurs and creates a new transaction for each redelivery.
@@ -840,7 +840,7 @@ class MyRouteBean extends CdiRouteBuilder {
----
-=== Lazy Injection / Programmatic Lookup
+== Lazy Injection / Programmatic Lookup
While the CDI programmatic model favors a http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#typesafe_resolution[typesafe resolution]
mechanism that occurs at application initialization time, it is possible to perform
@@ -924,7 +924,7 @@ for (CamelContext context : contexts)
----
-=== Maven Archetype
+== Maven Archetype
Among the available xref:manual::camel-maven-archetypes.adoc[Camel Maven
archetypes], you can use the provided `camel-archetype-cdi` to generate
@@ -936,7 +936,7 @@ mvn archetype:generate -DarchetypeGroupId=org.apache.camel.archetypes -Darchetyp
----
-=== See Also
+== See Also
* Camel CDI testing
* http://www.cdi-spec.org[CDI specification Web site]
diff --git a/components/camel-chatscript/src/main/docs/chatscript-component.adoc b/components/camel-chatscript/src/main/docs/chatscript-component.adoc
index 204b470..8ab3187 100644
--- a/components/camel-chatscript/src/main/docs/chatscript-component.adoc
+++ b/components/camel-chatscript/src/main/docs/chatscript-component.adoc
@@ -1,5 +1,5 @@
[[chatscript-component]]
-== ChatScript Component
+= ChatScript Component
*Available as of Camel version 3.0*
@@ -29,13 +29,13 @@ for this component:
</dependency>
------------------------------------------------------------
-### URI format
+== URI format
[source,java]
-------------------------------------------------------------------------------------------------------------------------
ChatScript:host:[port]/botName[?options]
-------------------------------------------------------------------------------------------------------------------------
-### Options
+== Options
// component options: START
The ChatScript component supports 2 options, which are listed below.
@@ -59,7 +59,7 @@ chatscript:host:port/botName
with the following path and query parameters:
-==== Path Parameters (3 parameters):
+=== Path Parameters (3 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -71,7 +71,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (5 parameters):
+=== Query Parameters (5 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -86,7 +86,7 @@ with the following path and query parameters:
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
diff --git a/components/camel-chunk/src/main/docs/chunk-component.adoc b/components/camel-chunk/src/main/docs/chunk-component.adoc
index 22307a6..4e21cc9 100644
--- a/components/camel-chunk/src/main/docs/chunk-component.adoc
+++ b/components/camel-chunk/src/main/docs/chunk-component.adoc
@@ -1,5 +1,5 @@
[[chunk-component]]
-== Chunk Component
+= Chunk Component
*Available as of Camel version 2.15*
@@ -20,7 +20,7 @@ their `pom.xml` for this component:
</dependency>
---------------------------------------------------------------------------------
-### URI format
+== URI format
[source,java]
----------------------------
@@ -33,7 +33,7 @@ invoke.
You can append query options to the URI in the following
format, `?option=value&option=value&...`
-### Options
+== Options
// component options: START
@@ -60,7 +60,7 @@ chunk:resourceUri
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -70,7 +70,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (9 parameters):
+=== Query Parameters (9 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -88,7 +88,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -123,7 +123,7 @@ with extensions _.chtml_ or _.cxml. _If you need to specify a different
folder or extensions, you will need to use the specific options listed
above.
-### Chunk Context
+== Chunk Context
Camel will provide exchange information in the Chunk context (just
a `Map`). The `Exchange` is transferred as:
@@ -148,7 +148,7 @@ a `Map`). The `Exchange` is transferred as:
|`response` |The Out message (only for InOut message exchange pattern).
|=======================================================================
-### Dynamic templates
+== Dynamic templates
Camel provides two headers by which you can define a different resource
location for a template or the template content itself. If any of these
@@ -165,7 +165,7 @@ configured. |
|ChunkConstants.CHUNK_TEMPLATE |String |The template to use instead of the endpoint configured. |
|=======================================================================
-### Samples
+== Samples
For example you could use something like:
@@ -209,7 +209,7 @@ to("chunk:file_example?themeFolder=template&themeSubfolder=subfolder&extension=c
In this example Chunk component will look for the file
_file_example.chunk_ in the folder _template/subfolder._
-### The Email Sample
+== The Email Sample
In this sample we want to use Chunk templating for an order confirmation
email. The email template is laid out in Chunk as:
@@ -225,7 +225,7 @@ Regards Camel Riders Bookstore
{$body}
----------------------------------------------
-### See Also
+== See Also
* Configuring Camel
* Component
diff --git a/components/camel-cm-sms/src/main/docs/cm-sms-component.adoc b/components/camel-cm-sms/src/main/docs/cm-sms-component.adoc
index 08af984..ee93c9f 100644
--- a/components/camel-cm-sms/src/main/docs/cm-sms-component.adoc
+++ b/components/camel-cm-sms/src/main/docs/cm-sms-component.adoc
@@ -1,5 +1,5 @@
[[cm-sms-component]]
-== CM SMS Gateway Component
+= CM SMS Gateway Component
*Available as of Camel version 2.18*
@@ -28,7 +28,7 @@ for this component:
</dependency>
---
-=== Options
+== Options
// component options: START
@@ -55,7 +55,7 @@ cm-sms:host
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -65,7 +65,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (7 parameters):
+=== Query Parameters (7 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -81,7 +81,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -111,6 +111,6 @@ The component supports 3 options, which are listed below.
-=== Sample
+== Sample
You can try https://github.com/oalles/camel-cm-sample[this project] to see how camel-cm-sms can be integrated in a camel route.
diff --git a/components/camel-cmis/src/main/docs/cmis-component.adoc b/components/camel-cmis/src/main/docs/cmis-component.adoc
index 94d2bc2..652bf21 100644
--- a/components/camel-cmis/src/main/docs/cmis-component.adoc
+++ b/components/camel-cmis/src/main/docs/cmis-component.adoc
@@ -1,5 +1,5 @@
[[cmis-component]]
-== CMIS Component
+= CMIS Component
*Available as of Camel version 2.11*
@@ -8,7 +8,7 @@ http://chemistry.apache.org/java/opencmis.html[Apache Chemistry] client
API and allows you to add/read nodes to/from a CMIS compliant content
repositories.
-### URI Format
+== URI Format
[source,java]
------------------------------
@@ -18,7 +18,7 @@ cmis://cmisServerUrl[?options]
You can append query options to the URI in the following format,
?options=value&option2=value&...
-### CMIS Options
+== CMIS Options
// component options: START
@@ -46,7 +46,7 @@ cmis:cmsUrl
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -56,7 +56,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (15 parameters):
+=== Query Parameters (15 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -80,7 +80,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -111,9 +111,9 @@ The component supports 4 options, which are listed below.
-### Usage
+== Usage
-#### Message headers evaluated by the producer
+=== Message headers evaluated by the producer
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -138,7 +138,7 @@ the node from this cmis property and it is path
|`cmis:contentStreamMimeType` |`null` |The mimetype to set for a document
|=======================================================================
-#### Message headers set during querying Producer operation
+=== Message headers set during querying Producer operation
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -152,7 +152,7 @@ map is cmis property and its value. If `CamelCMISRetrieveContent` header is set
entry in the map with key `CamelCMISContent` will contain `InputStream`
of the document type of nodes.
-### Dependencies
+== Dependencies
Maven users will need to add the following dependency to their pom.xml.
@@ -170,7 +170,7 @@ Maven users will need to add the following dependency to their pom.xml.
where `${camel-version`} must be replaced by the actual version of Camel
(2.11 or higher).
-### See Also
+== See Also
* Configuring Camel
* Component
diff --git a/components/camel-coap/src/main/docs/coap-component.adoc b/components/camel-coap/src/main/docs/coap-component.adoc
index ef0b136..78c0d37 100644
--- a/components/camel-coap/src/main/docs/coap-component.adoc
+++ b/components/camel-coap/src/main/docs/coap-component.adoc
@@ -1,5 +1,5 @@
[[coap-component]]
-== CoAP Component
+= CoAP Component
*Available as of Camel version 2.16*
@@ -38,7 +38,7 @@ for this component:
</dependency>
---------------------------------------------------------
-### Options
+== Options
// component options: START
@@ -66,7 +66,7 @@ coap:uri
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -76,7 +76,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (15 parameters):
+=== Query Parameters (15 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -100,7 +100,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -129,7 +129,7 @@ The component supports 3 options, which are listed below.
// spring-boot-auto-configure options: END
-### Message Headers
+== Message Headers
[width="100%",cols="10%,20%,70%",options="header",]
|=======================================================================
@@ -144,7 +144,7 @@ of what each code means.
|`CamelCoapUri` |`String` |The URI of a CoAP server to call. Will override any existing URI configured directly on the endpoint.
|=======================================================================
-#### Configuring the CoAP producer request method
+=== Configuring the CoAP producer request method
The following rules determine which request method the CoAP producer will use to invoke the target URI:
diff --git a/components/camel-cometd/src/main/docs/cometd-component.adoc b/components/camel-cometd/src/main/docs/cometd-component.adoc
index 2d05c59..d8d4138 100644
--- a/components/camel-cometd/src/main/docs/cometd-component.adoc
+++ b/components/camel-cometd/src/main/docs/cometd-component.adoc
@@ -1,5 +1,5 @@
[[cometd-component]]
-== CometD Component
+= CometD Component
*Available as of Camel version 2.0*
@@ -24,7 +24,7 @@ for this component:
</dependency>
------------------------------------------------------------
-### URI format
+== URI format
[source,java]
----------------------------------------
@@ -34,7 +34,7 @@ cometd://host:port/channelName[?options]
The *channelName* represents a topic that can be subscribed to by the
Camel endpoints.
-### Examples
+== Examples
------------------------------------------
cometd://localhost:8080/service/mychannel
@@ -43,7 +43,7 @@ cometds://localhost:8443/service/mychannel
where `cometds:` represents an SSL configured endpoint.
-### Options
+== Options
@@ -82,7 +82,7 @@ cometd:host:port/channelName
with the following path and query parameters:
-==== Path Parameters (3 parameters):
+=== Path Parameters (3 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -94,7 +94,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (18 parameters):
+=== Query Parameters (18 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -121,7 +121,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -170,7 +170,7 @@ For file (for webapp resources located in the Web Application directory
the webapp folder -->
cometd://localhost:8080?resourceBase=classpath:webapp
-### Authentication
+== Authentication
*Available as of Camel 2.8*
@@ -178,9 +178,9 @@ You can configure custom `SecurityPolicy` and `Extension`'s to the
`CometdComponent` which allows you to use authentication as
http://cometd.org/documentation/howtos/authentication[documented here]
-### Setting up SSL for Cometd Component
+== Setting up SSL for Cometd Component
-#### Using the JSSE Configuration Utility
+=== Using the JSSE Configuration Utility
The Cometd component supports SSL/TLS configuration
through the xref:manual::camel-configuration-utilities.adoc[Camel JSSE
@@ -242,7 +242,7 @@ Spring DSL based configuration of endpoint
<to uri="cometds://127.0.0.1:443/service/test?baseResource=file:./target/test-classes/webapp&timeout=240000&interval=0&maxInterval=30000&multiFrameInterval=1500&jsonCommented=true&logLevel=2"/>...
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-### See Also
+== See Also
* Configuring Camel
* Component
diff --git a/components/camel-consul/src/main/docs/consul-component.adoc b/components/camel-consul/src/main/docs/consul-component.adoc
index 4245cf3..a9bc52a 100644
--- a/components/camel-consul/src/main/docs/consul-component.adoc
+++ b/components/camel-consul/src/main/docs/consul-component.adoc
@@ -1,5 +1,5 @@
[[consul-component]]
-== Consul Component
+= Consul Component
*Available as of Camel version 2.18*
@@ -17,7 +17,7 @@ for this component:
</dependency>
-------------------------------------------------
-### URI format
+== URI format
[source,java]
---------------------------------------
@@ -30,7 +30,7 @@ You can append query options to the URI in the following format:
?option=value&option=value&...
---------------------------------------
-### Options
+== Options
@@ -70,7 +70,7 @@ consul:apiEndpoint
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -80,7 +80,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (6 parameters):
+=== Query Parameters (6 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -95,7 +95,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -215,7 +215,7 @@ The component supports 91 options, which are listed below.
-### Headers
+== Headers
[width="100%",options="header"]
|=======================================================================
diff --git a/components/camel-controlbus/src/main/docs/controlbus-component.adoc b/components/camel-controlbus/src/main/docs/controlbus-component.adoc
index cfd64bf..04fdab1 100644
--- a/components/camel-controlbus/src/main/docs/controlbus-component.adoc
+++ b/components/camel-controlbus/src/main/docs/controlbus-component.adoc
@@ -1,5 +1,5 @@
[[controlbus-component]]
-== Control Bus Component
+= Control Bus Component
*Available as of Camel version 2.11*
@@ -36,7 +36,7 @@ controlbus:command[?options]
Where *command* can be any string to identify which type of command to
use.
-=== Commands
+== Commands
[width="100%",cols="10%,90%",options="header",]
|===
@@ -49,7 +49,7 @@ evaluating the message body. If there is any result from the evaluation,
then the result is put in the message body.
|===
-=== Options
+== Options
// component options: START
@@ -76,7 +76,7 @@ controlbus:command:language
with the following path and query parameters:
-==== Path Parameters (2 parameters):
+=== Path Parameters (2 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -87,7 +87,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (8 parameters):
+=== Query Parameters (8 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -109,7 +109,7 @@ You can append query options to the URI in the following format,
`?option=value&option=value&...`
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -138,7 +138,7 @@ The component supports 3 options, which are listed below.
// spring-boot-auto-configure options: END
-=== Using route command
+== Using route command
The route command allows you to do common tasks on a given route very
easily, for example to start a route, you can send an empty message to
@@ -157,7 +157,7 @@ String status = template.requestBody("controlbus:route?routeId=foo&action=status
----
[[ControlBus-Gettingperformancestatistics]]
-=== Getting performance statistics
+== Getting performance statistics
*Available as of Camel 2.11.1*
@@ -183,7 +183,7 @@ just omit the routeId parameter as shown below:
String xml = template.requestBody("controlbus:route?action=stats", null, String.class);
----
-=== Using Simple language
+== Using Simple language
You can use the xref:manual::simple-language.adoc[Simple] language with the control bus,
for example to stop a specific route, you can send a message to the
diff --git a/components/camel-corda/src/main/docs/corda-component.adoc b/components/camel-corda/src/main/docs/corda-component.adoc
index 526797e..4b99b8d 100644
--- a/components/camel-corda/src/main/docs/corda-component.adoc
+++ b/components/camel-corda/src/main/docs/corda-component.adoc
@@ -1,5 +1,5 @@
[[corda-component]]
-== corda Component
+= corda Component
*Available as of Camel version 2.23*
@@ -19,14 +19,14 @@ for this component:
</dependency>
------------------------------------------------------------
-=== URI Format
+== URI Format
[source,text]
----
corda://<host:port>[?options]
----
-=== Corda Options
+== Corda Options
// component options: START
@@ -53,7 +53,7 @@ corda:configuration
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -63,7 +63,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (6 parameters):
+=== Query Parameters (6 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -78,7 +78,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -124,7 +124,7 @@ You can append query options to the URI in the following format,
?options=value&option2=value&...
-### Message Headers
+== Message Headers
[width="100%",cols="10%,90%",options="header",]
|=======================================================================
@@ -136,7 +136,7 @@ You can append query options to the URI in the following format,
-### Samples
+== Samples
Subscribe for new vault state changes:
diff --git a/components/camel-couchbase/src/main/docs/couchbase-component.adoc b/components/camel-couchbase/src/main/docs/couchbase-component.adoc
index 0764056..8fd9e28 100644
--- a/components/camel-couchbase/src/main/docs/couchbase-component.adoc
+++ b/components/camel-couchbase/src/main/docs/couchbase-component.adoc
@@ -1,5 +1,5 @@
[[couchbase-component]]
-== Couchbase Component
+= Couchbase Component
*Available as of Camel version 2.19*
@@ -20,14 +20,14 @@ for this component:
</dependency>
------------------------------------------------------------
-### URI format
+== URI format
[source,java]
-------------------------------------------------
couchbase:url
-------------------------------------------------
-### Options
+== Options
// component options: START
The Couchbase component supports 2 options, which are listed below.
@@ -51,7 +51,7 @@ couchbase:protocol:hostname:port
with the following path and query parameters:
-==== Path Parameters (3 parameters):
+=== Path Parameters (3 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -63,7 +63,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (49 parameters):
+=== Query Parameters (49 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -121,7 +121,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -149,7 +149,7 @@ The component supports 3 options, which are listed below.
|===
// spring-boot-auto-configure options: END
-=== Couchbase SDK compatibility
+== Couchbase SDK compatibility
This component is currently using a "Legacy SDK" version of couchbase-client.
In order to authenticate with newer versions of Couchbase Server 5.0 and beyond, as per instructions on the https://docs.couchbase.com/java-sdk/2.7/sdk-authentication-overview.html/[CouchBase Java SDK Authentication]:
diff --git a/components/camel-couchdb/src/main/docs/couchdb-component.adoc b/components/camel-couchdb/src/main/docs/couchdb-component.adoc
index 7154ce1..232ea48 100644
--- a/components/camel-couchdb/src/main/docs/couchdb-component.adoc
+++ b/components/camel-couchdb/src/main/docs/couchdb-component.adoc
@@ -1,5 +1,5 @@
[[couchdb-component]]
-== CouchDB Component
+= CouchDB Component
*Available as of Camel version 2.11*
@@ -32,7 +32,7 @@ for this component:
</dependency>
------------------------------------------------------------
-### URI format
+== URI format
[source,java]
-------------------------------------------------
@@ -42,7 +42,7 @@ couchdb:http://hostname[:port]/database?[options]
Where *hostname* is the hostname of the running couchdb instance. Port
is optional and if not specified then defaults to 5984.
-### Options
+== Options
// component options: START
The CouchDB component supports 2 options, which are listed below.
@@ -66,7 +66,7 @@ couchdb:protocol:hostname:port/database
with the following path and query parameters:
-==== Path Parameters (4 parameters):
+=== Path Parameters (4 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -79,7 +79,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (14 parameters):
+=== Query Parameters (14 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -102,7 +102,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -131,7 +131,7 @@ The component supports 3 options, which are listed below.
// spring-boot-auto-configure options: END
-### Headers
+== Headers
The following headers are set on exchanges during message transport.
@@ -157,7 +157,7 @@ ignored. That means for example, if you set CouchDbId as a header, it
will not be used as the id for insertion, the id of the document will
still be used.
-### Message Body
+== Message Body
The component will use the message body as the document to be inserted.
If the body is an instance of String, then it will be marshalled into a
@@ -166,7 +166,7 @@ or the insert / update will fail. If the body is an instance of a
com.google.gson.JsonElement then it will be inserted as is. Otherwise
the producer will throw an exception of unsupported body type.
-### Samples
+== Samples
For example if you wish to consume all inserts, updates and deletes from
a CouchDB instance running locally, on port 9999 then you could use the
diff --git a/components/camel-crypto-cms/src/main/docs/crypto-cms-component.adoc b/components/camel-crypto-cms/src/main/docs/crypto-cms-component.adoc
index 9ba6d6c..7803394 100644
--- a/components/camel-crypto-cms/src/main/docs/crypto-cms-component.adoc
+++ b/components/camel-crypto-cms/src/main/docs/crypto-cms-component.adoc
@@ -1,5 +1,5 @@
[[crypto-cms-component]]
-== Crypto CMS Component
+= Crypto CMS Component
*Available as of Camel version 2.20*
@@ -31,7 +31,7 @@ Security.addProvider(new BouncyCastleProvider());
If the Bouncy Castle security provider is not registered then the Crypto CMS component will register the provider.
-### Options
+== Options
// component options: START
The Crypto CMS component supports 4 options, which are listed below.
@@ -57,7 +57,7 @@ crypto-cms:cryptoOperation:name
with the following path and query parameters:
-==== Path Parameters (2 parameters):
+=== Path Parameters (2 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -68,7 +68,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (17 parameters):
+=== Query Parameters (17 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -94,7 +94,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -125,7 +125,7 @@ The component supports 5 options, which are listed below.
// spring-boot-auto-configure options: END
-### Enveloped Data
+== Enveloped Data
Note, that a `crypto-cms:encypt` endpoint is typically defined in one route and the complimentary `crypto-cms:decrypt` in another, though for simplicity in the
examples they appear one after the other.
@@ -235,7 +235,7 @@ from("direct:start")
</route>
----
-### Signed Data
+== Signed Data
Note, that a `crypto-cms:sign` endpoint is typically defined in one route and the complimentary `crypto-cms:verify` in another, though for simplicity in the
examples they appear one after the other.
diff --git a/components/camel-crypto/src/main/docs/crypto-component.adoc b/components/camel-crypto/src/main/docs/crypto-component.adoc
index 5734dbe..451b196 100644
--- a/components/camel-crypto/src/main/docs/crypto-component.adoc
+++ b/components/camel-crypto/src/main/docs/crypto-component.adoc
@@ -1,5 +1,5 @@
[[crypto-component]]
-== Crypto (JCE) Component
+= Crypto (JCE) Component
*Available as of Camel version 2.3*
@@ -22,7 +22,7 @@ for this component:
</dependency>
------------------------------------------------------------
-### Introduction
+== Introduction
Digital signatures make use of Asymmetric Cryptographic techniques to
sign messages. From a (very) high level, the algorithms use pairs of
@@ -48,7 +48,7 @@ and how to leverage them with the JCE.
* The ever insightful Wikipedia
http://en.wikipedia.org/wiki/Digital_signature[Digital_signatures]
-### URI format
+== URI format
As mentioned Camel provides a pair of crypto endpoints to create and
verify signatures
@@ -78,7 +78,7 @@ complimentary `crypto:verify` in another, though for simplicity in the
examples they appear one after the other. It goes without saying that
both signing and verifying should be configured identically.
-### Options
+== Options
// component options: START
The Crypto (JCE) component supports 3 options, which are listed below.
@@ -103,7 +103,7 @@ crypto:cryptoOperation:name
with the following path and query parameters:
-==== Path Parameters (2 parameters):
+=== Path Parameters (2 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -114,7 +114,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (21 parameters):
+=== Query Parameters (21 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -144,7 +144,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -206,9 +206,9 @@ The component supports 34 options, which are listed below.
-### Using
+== Using
-#### Raw keys
+=== Raw keys
The most basic way to way to sign and verify an exchange is with a
KeyPair as follows.
@@ -216,7 +216,7 @@ KeyPair as follows.
The same can be achieved with the xref:manual::spring-xml-extensions.adoc[Spring
XML Extensions] using references to keys
-#### KeyStores and Aliases.
+=== KeyStores and Aliases.
The JCE provides a very versatile keystore concept for housing pairs of
private keys and certificates, keeping them encrypted and password
@@ -236,7 +236,7 @@ also shows how to load and initialize the keystore.
Again in Spring a ref is used to lookup an actual keystore instance.
-#### Changing JCE Provider and Algorithm
+=== Changing JCE Provider and Algorithm
Changing the Signature algorithm or the Security provider is a simple
matter of specifying their names. You will need to also use Keys that
@@ -244,7 +244,7 @@ are compatible with the algorithm you choose.
or
-#### Changing the Signature Message Header
+=== Changing the Signature Message Header
It may be desirable to change the message header used to store the
signature. A different header name can be specified in the route
@@ -252,13 +252,13 @@ definition as follows
or
-#### Changing the buffersize
+=== Changing the buffersize
In case you need to update the size of the buffer...
or
-#### Supplying Keys dynamically.
+=== Supplying Keys dynamically.
When using a Recipient list or similar EIP the recipient of an exchange
can vary dynamically. Using the same key across all recipients may be
@@ -295,7 +295,7 @@ signed.getIn().setHeader(KEYSTORE_ALIAS, "bob");
template.send("direct:alias-verify", signed);
-------------------------------------------------------------------------------------------------
-### See Also
+== See Also
* Configuring Camel
* Component
diff --git a/components/camel-crypto/src/main/docs/crypto-dataformat.adoc b/components/camel-crypto/src/main/docs/crypto-dataformat.adoc
index b20a89c..8b3547d 100644
--- a/components/camel-crypto/src/main/docs/crypto-dataformat.adoc
+++ b/components/camel-crypto/src/main/docs/crypto-dataformat.adoc
@@ -1,5 +1,5 @@
[[crypto-dataformat]]
-== Crypto (Java Cryptographic Extension) DataFormat
+= Crypto (Java Cryptographic Extension) DataFormat
*Available as of Camel version 2.3*
@@ -11,7 +11,7 @@ encryption to cyphertext and unmarshalling to mean decryption back to
the original plaintext. This data format implements only symmetric
(shared-key) encryption and decyption.
-### CryptoDataFormat Options
+== CryptoDataFormat Options
// dataformat options: START
The Crypto (Java Cryptographic Extension) dataformat supports 10 options, which are listed below.
@@ -34,7 +34,7 @@ The Crypto (Java Cryptographic Extension) dataformat supports 10 options, which
|===
// dataformat options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -95,7 +95,7 @@ The component supports 34 options, which are listed below.
ND
-### Basic Usage
+== Basic Usage
At its most basic all that is required to encrypt/decrypt an exchange is a shared secret key.
If one or more instances of the Crypto data format are configured with this key the format can
@@ -136,7 +136,7 @@ In Spring the dataformat is configured first and then used in routes
----------------------------------------------------------
-### Specifying the Encryption Algorithm
+== Specifying the Encryption Algorithm
Changing the algorithm is a matter of supplying the JCE algorithm name. If you change the algorithm you will need to use a compatible key.
@@ -158,7 +158,7 @@ from("direct:hmac-algorithm")
A list of the available algorithms in Java 7 is available via the Java Cryptography Architecture Standard Algorithm Name Documentation.
-### Specifying an Initialization Vector
+== Specifying an Initialization Vector
Some crypto algorithms, particularly block algorithms, require configuration with an initial block of data known as an Initialization Vector.
In the JCE this is passed as an AlgorithmParameterSpec when the Cipher is initialized.
@@ -226,7 +226,7 @@ For more information of the use of Initialization Vectors, consult
* http://en.wikipedia.org/wiki/Block_cipher_modes_of_operation
-### Hashed Message Authentication Codes (HMAC)
+== Hashed Message Authentication Codes (HMAC)
To avoid attacks against the encrypted data while it is in transit the CryptoDataFormat can also calculate a Message Authentication
Code for the encrypted exchange contents based on a configurable MAC algorithm. The calculated HMAC is appended to the stream after encryption.
It is separated from the stream in the decryption phase. The MAC is recalculated and verified against the transmitted version to insure nothing
@@ -279,7 +279,7 @@ or with spring.
----------------------------------------------------------
-### Supplying Keys Dynamically
+== Supplying Keys Dynamically
When using a Recipient list or similar EIP the recipient of an exchange can vary dynamically.
Using the same key across all recipients may neither be feasible or desirable. It would be useful to be able to specify
@@ -320,7 +320,7 @@ or with spring.
----------------------------------------------------------
-### Dependencies
+== Dependencies
To use the xref:crypto-component.adoc[Crypto] dataformat in your camel routes you
need to add the following dependency to your pom.
@@ -335,7 +335,7 @@ need to add the following dependency to your pom.
</dependency>
----------------------------------------------------------
-### See Also
+== See Also
* Data Format
* Crypto (Digital Signatures)
diff --git a/components/camel-crypto/src/main/docs/pgp-dataformat.adoc b/components/camel-crypto/src/main/docs/pgp-dataformat.adoc
index 2fd348e..354d52c 100644
--- a/components/camel-crypto/src/main/docs/pgp-dataformat.adoc
+++ b/components/camel-crypto/src/main/docs/pgp-dataformat.adoc
@@ -1,5 +1,5 @@
[[pgp-dataformat]]
-== PGP DataFormat
+= PGP DataFormat
*Available as of Camel version 2.9*
@@ -11,7 +11,7 @@ encryption to cyphertext and unmarshalling to mean decryption back to
the original plaintext. This data format implements only symmetric
(shared-key) encryption and decyption.
-### PGPDataFormat Options
+== PGPDataFormat Options
// dataformat options: START
The PGP dataformat supports 15 options, which are listed below.
@@ -39,7 +39,7 @@ The PGP dataformat supports 15 options, which are listed below.
|===
// dataformat options: END
-### PGPDataFormat Message Headers
+== PGPDataFormat Message Headers
You can override the PGPDataFormat options by applying below headers
into message dynamically.
@@ -94,7 +94,7 @@ symmectric key, set by PGPDataFormat during encryptiion process
signatures, set by PGPDataFormat during signing process
|=======================================================================
-### Encrypting with PGPDataFormat
+== Encrypting with PGPDataFormat
The following sample uses the popular PGP format for
encrypting/decrypting files using the
@@ -106,7 +106,7 @@ encryption, but you can obviously use different keys:
Or using Spring:
-#### To work with the previous example you need the following
+=== To work with the previous example you need the following
* A public keyring file which contains the public keys used to encrypt
the data
@@ -114,7 +114,7 @@ the data
data
* The keyring password
-#### Managing your keyring
+=== Managing your keyring
To manage the keyring, I use the command line tools, I find this to be
the simplest approach in managing the keys. There are also Java
@@ -149,7 +149,7 @@ ls -l ~/.gnupg/pubring.gpg ~/.gnupg/secring.gpg
[[Crypto-PGPDecrypting/VerifyingofMessagesEncrypted/SignedbyDifferentPrivate/PublicKeys]]
PGP Decrypting/Verifying of Messages Encrypted/Signed by Different
-### Private/Public Keys
+== Private/Public Keys
A PGP Data Formater can decrypt/verify messages which have been
encrypted by different public keys or signed by different private keys.
@@ -192,7 +192,7 @@ same mechanism is also used to locate the public key for verifying a
signature. Therefore you no longer must specify User IDs for the
unmarshaling.
-### Restricting the Signer Identities during PGP Signature Verification
+== Restricting the Signer Identities during PGP Signature Verification
If you verify a signature you not only want to verify the correctness of
the signature but you also want check that the signature comes from a
@@ -227,7 +227,7 @@ successful as soon as one signature can be verified.
then do not specify the signature key User IDs. In this case all public
keys in the public keyring are taken into account.
-### Several Signatures in One PGP Data Format
+== Several Signatures in One PGP Data Format
The PGP specification allows that one PGP data format can contain
several signatures from different keys. Since Camel 2.13.3 it is
@@ -255,7 +255,7 @@ from("direct:start")
...
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-### Support of Sub-Keys and Key Flags in PGP Data Format Marshaler
+== Support of Sub-Keys and Key Flags in PGP Data Format Marshaler
*An https://tools.ietf.org/html/rfc4880#section-12.1[OpenPGP V4 key] can
have a primary key and sub-keys. The usage of the keys is indicated by
@@ -269,7 +269,7 @@ these Key Flags of the primary key and sub-keys in order to determine
the right key for signing and encryption. This is necessary because the
primary key and its sub-keys have the same User IDs.
-### Support of Custom Key Accessors
+== Support of Custom Key Accessors
*You can implement custom key accessors for encryption/signing. The
above PGPDataFormat class selects in a certain predefined way the keys
@@ -292,7 +292,7 @@ PGPKeyAccessDataFormat has the same options as PGPDataFormat except
password, keyFileName, encryptionKeyRing, signaturePassword,
signatureKeyFileName, and signatureKeyRing.
-### Dependencies
+== Dependencies
To use the PGP dataformat in your camel routes you
need to add the following dependency to your pom.
@@ -307,7 +307,7 @@ need to add the following dependency to your pom.
</dependency>
----------------------------------------------------------
-### See Also
+== See Also
* Data Format
* Crypto (Digital Signatures)
diff --git a/components/camel-csv/src/main/docs/csv-dataformat.adoc b/components/camel-csv/src/main/docs/csv-dataformat.adoc
index b1e2547..78b219f 100644
--- a/components/camel-csv/src/main/docs/csv-dataformat.adoc
+++ b/components/camel-csv/src/main/docs/csv-dataformat.adoc
@@ -1,5 +1,5 @@
[[csv-dataformat]]
-== CSV DataFormat
+= CSV DataFormat
*Available as of Camel version 1.3*
@@ -9,7 +9,7 @@ handle CSV payloads (Comma Separated Values) such as those
exported/imported by Excel.
-### Options
+== Options
// dataformat options: START
The CSV dataformat supports 29 options, which are listed below.
@@ -51,7 +51,7 @@ The CSV dataformat supports 29 options, which are listed below.
|===
// dataformat options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -109,7 +109,7 @@ ND
-### Marshalling a Map to CSV
+== Marshalling a Map to CSV
The component allows you to marshal a Java Map (or any other message
type that can be converted in a Map) into a
@@ -153,7 +153,7 @@ then it will produce
abc,123
----
-### Unmarshalling a CSV message into a Java List
+== Unmarshalling a CSV message into a Java List
Unmarshalling will transform a CSV messsage into a Java List with CSV
file lines (containing another List with all the field values).
@@ -189,7 +189,7 @@ for (List<String> line : data) {
}
--------------------------------------------------------------------------------------------------------------
-### Marshalling a List<Map> to CSV
+== Marshalling a List<Map> to CSV
*Available as of Camel 2.1*
@@ -198,7 +198,7 @@ format you can now store the message payload as a
`List<Map<String, Object>>` object where the list contains a Map for
each row.
-### File Poller of CSV, then unmarshaling
+== File Poller of CSV, then unmarshaling
Given a bean which can handle the incoming data...
@@ -225,7 +225,7 @@ public void doHandleCsvData(List<List<String>> csvData)
</route>
------------------------------------------------------------------------------------------------
-### Marshaling with a pipe as delimiter
+== Marshaling with a pipe as delimiter
Considering the following body
[source,java]
@@ -266,7 +266,7 @@ abc|123
[[CSV-UsingautogenColumns,configRefandstrategyRefattributesinsideXMLDSL]]
Using autogenColumns, configRef and strategyRef attributes inside XML
-### DSL
+== DSL
*Available as of Camel 2.9.2 / 2.10 and deleted for Camel 2.15*
@@ -305,7 +305,7 @@ should illustrate this customization.
</bean>
-----------------------------------------------------------------------------------------------------------------------------
-### Using skipFirstLine option while unmarshaling
+== Using skipFirstLine option while unmarshaling
*Available as of Camel 2.10 and deleted for Camel 2.15*
@@ -335,7 +335,7 @@ from("direct:start")
.to("bean:myCsvHandler?method=doHandleCsv");
--------------------------------------------
-### Unmarshaling with a pipe as delimiter
+== Unmarshaling with a pipe as delimiter
Using the Spring/XML DSL:
@@ -398,7 +398,7 @@ csvConfig.setDelimiter(';');
doesn't work. You have to set the delimiter as a String!
-### Dependencies
+== Dependencies
To use CSV in your Camel routes you need to add a dependency on
*camel-csv*, which implements this data format.
diff --git a/components/camel-cxf-transport/src/main/docs/cxf-transport.adoc b/components/camel-cxf-transport/src/main/docs/cxf-transport.adoc
index ca41a57..fa23b53 100644
--- a/components/camel-cxf-transport/src/main/docs/cxf-transport.adoc
+++ b/components/camel-cxf-transport/src/main/docs/cxf-transport.adoc
@@ -1,5 +1,5 @@
[[CamelTransportforCXF-WhatstheCamelTransportforCXF]]
-== What's the Camel Transport for CXF
+= What's the Camel Transport for CXF
In CXF you offer or consume a webservice by defining its address. The
first part of the address specifies the protocol to use. For example
@@ -18,13 +18,13 @@ use Camel's routing engine and integration patterns support together
with your CXF services.
[[CamelTransportforCXF-IntegrateCamelintoCXFtransportlayer]]
-=== Integrate Camel into CXF transport layer
+== Integrate Camel into CXF transport layer
To include the Camel Transport into your CXF bus you use the
CamelTransportFactory. You can do this in Java as well as in Spring.
[[CamelTransportforCXF-SettinguptheCamelTransportinSpring]]
-==== Setting up the Camel Transport in Spring
+=== Setting up the Camel Transport in Spring
You can use the following snippet in your applicationcontext if you want
to configure anything special. If you only want to activate the camel
@@ -53,7 +53,7 @@ jar and load a CamelTransportFactory for you.
--------------------------------------------------------------------------------------------------------
[[CamelTransportforCXF-IntegratingtheCamelTransportinaprogrammaticway]]
-==== Integrating the Camel Transport in a programmatic way
+=== Integrating the Camel Transport in a programmatic way
Camel transport provides a setContext method that you could use to set
the Camel context into the transport factory. If you want this factory
@@ -88,10 +88,10 @@ BusFactory.setDefaultBus(bus);
------------------------------------------------------------------------------------------------------------------
[[CamelTransportforCXF-ConfigurethedestinationandconduitwithSpring]]
-=== Configure the destination and conduit with Spring
+== Configure the destination and conduit with Spring
[[CamelTransportforCXF-Namespace]]
-==== Namespace
+=== Namespace
The elements used to configure a Camel transport endpoint are defined
in the namespace `\http://cxf.apache.org/transports/camel`. It is
@@ -115,7 +115,7 @@ the `xsi:schemaLocation` attribute.
---------------------------------------------------------------------
[[CamelTransportforCXF-Thedestinationelement]]
-==== The `destination` element
+=== The `destination` element
You configure a Camel transport server endpoint using the
`camel:destination` element and its children. The `camel:destination`
@@ -163,7 +163,7 @@ You can specify the camel context in the camel destination
The camel context id which you want inject into the camel destination
[[CamelTransportforCXF-Theconduitelement]]
-==== The `conduit` element
+=== The `conduit` element
You configure a Camel transport client using the `camel:conduit` element
and its children. The `camel:conduit` element takes a single attribute,
@@ -213,7 +213,7 @@ You can specify the camel context in the camel conduit
The camel context id which you want inject into the camel conduit
[[CamelTransportforCXF-ConfigurethedestinationandconduitwithBlueprint]]
-=== Configure the destination and conduit with Blueprint
+== Configure the destination and conduit with Blueprint
Camel Transport for CXF supports configuration with Blueprint.
@@ -245,7 +245,7 @@ context in the camel destination.
------------------------------------------------------------------------
[[CamelTransportforCXF-ExampleUsingCamelasaloadbalancerforCXF]]
-=== Example Using Camel as a load balancer for CXF
+== Example Using Camel as a load balancer for CXF
This example shows how to use the camel load balancing feature in CXF.
You need to load the configuration file in CXF and publish the endpoints
diff --git a/components/camel-cxf/src/main/docs/cxf-component.adoc b/components/camel-cxf/src/main/docs/cxf-component.adoc
index 8421f8e..eed3390 100644
--- a/components/camel-cxf/src/main/docs/cxf-component.adoc
+++ b/components/camel-cxf/src/main/docs/cxf-component.adoc
@@ -1,5 +1,5 @@
[[cxf-component]]
-== CXF Component
+= CXF Component
*Available as of Camel version 1.0*
@@ -50,7 +50,7 @@ for this component:
------------------------------------------------------------
-=== URI format
+== URI format
There are two URI formats for this endpoint: *cxfEndpoint* and *someAddress*.
[source,java]
@@ -78,7 +78,7 @@ For either style above, you can append options to the URI as follows:
cxf:bean:cxfEndpoint?wsdlURL=wsdl/hello_world.wsdl&dataFormat=PAYLOAD
---------------------------------------------------------------------
-=== Options
+== Options
@@ -111,7 +111,7 @@ cxf:beanId:address
with the following path and query parameters:
-==== Path Parameters (2 parameters):
+=== Path Parameters (2 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -122,7 +122,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (36 parameters):
+=== Query Parameters (36 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -167,7 +167,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -205,7 +205,7 @@ http://en.wikipedia.org/wiki/QName[QNames], so if you provide them be
sure to prefix them with their \{namespace} as shown in the examples
above.
-==== Descriptions of the dataformats
+=== Descriptions of the dataformats
In Apache Camel, the Camel CXF component is the key to integrating routes with Web services. You can use the Camel CXF component to create a CXF endpoint, which can be used in either of the following ways:
* *Consumer* — (at the start of a route) represents a Web service instance, which integrates with the route. The type of payload injected into the route depends on the value of the endpoint's dataFormat option.
@@ -240,7 +240,7 @@ defined in
`org.apache.camel.component.cxf.common.message.CxfConstants.DATA_FORMAT_PROPERTY`.
[#cxf-loggingout-interceptor-in-message-mode]
-==== How to enable CXF's LoggingOutInterceptor in MESSAGE mode
+=== How to enable CXF's LoggingOutInterceptor in MESSAGE mode
CXF's `LoggingOutInterceptor` outputs outbound message that goes on the
wire to logging system (Java Util Logging). Since the
@@ -267,7 +267,7 @@ following is an example.
</cxf:cxfEndpoint>
-------------------------------------------------------------------------------------------------------
-==== Description of relayHeaders option
+=== Description of relayHeaders option
There are _in-band_ and _out-of-band_ on-the-wire headers from the
perspective of a JAXWS WSDL-first developer.
@@ -286,7 +286,7 @@ be consumed say by another JAXWS endpoint, then `relayHeaders` should be
set to `true`, which is the default value.
-==== Available only in POJO mode
+=== Available only in POJO mode
The `relayHeaders=true` express an intent to relay the headers. The
actual decision on whether a given header is relayed is delegated to a
@@ -407,7 +407,7 @@ value is `false`, it will throw an exception
_Default_: `false`
|=======================================================================
-=== Configure the CXF endpoints with Spring
+== Configure the CXF endpoints with Spring
You can configure the CXF endpoint with the Spring configuration file
shown below, and you can also embed the endpoint into the `camelContext`
@@ -537,7 +537,7 @@ and setDefaultBus properties from spring configuration file.
</cxf:cxfEndpoint>
-------------------------------------------------------------------------
-=== Configuring the CXF Endpoints with Apache Aries Blueprint
+== Configuring the CXF Endpoints with Apache Aries Blueprint
The component is capable of utilizing aries blueprint
dependency injection for your CXF endpoints.
@@ -613,7 +613,7 @@ You can also use the bean references just as in spring
</blueprint>
----------------------------------------------------------------------------------------------------------------
-=== How to make the camel-cxf component use log4j instead of java.util.logging
+== How to make the camel-cxf component use log4j instead of java.util.logging
CXF's default logger is `java.util.logging`. If you want to change it to
log4j, proceed as follows. Create a file, in the classpath, named
@@ -622,7 +622,7 @@ fully-qualified name of the class,
`org.apache.cxf.common.logging.Log4jLogger`, with no comments, on a
single line.
-=== How to let camel-cxf response message with xml start document
+== How to let camel-cxf response message with xml start document
If you are using some SOAP client such as PHP, you will get this kind of
error, because CXF doesn't add the XML start document "<?xml
@@ -647,7 +647,7 @@ camel-cxf endpont or add a message header for it like
exchange.getOut().setHeader(Client.RESPONSE_CONTEXT, map);
-------------------------------------------------------------------
-=== How to override the CXF producer address from message header
+== How to override the CXF producer address from message header
The `camel-cxf` producer supports to override the services address by
setting the message with the key of "CamelDestinationOverrideUrl".
@@ -658,7 +658,7 @@ setting the message with the key of "CamelDestinationOverrideUrl".
exchange.getIn().setHeader(Exchange.DESTINATION_OVERRIDE_URL, constant(getServiceAddress()));
----------------------------------------------------------------------------------------------
-=== How to consume a message from a camel-cxf endpoint in POJO data format
+== How to consume a message from a camel-cxf endpoint in POJO data format
The `camel-cxf` endpoint consumer POJO data format is based on the
http://cxf.apache.org/docs/invokers.html[CXF invoker], so the
@@ -666,7 +666,7 @@ message header has a property with the name of
`CxfConstants.OPERATION_NAME` and the message body is a list of the SEI
method parameters.
-=== How to prepare the message for the camel-cxf endpoint in POJO data format
+== How to prepare the message for the camel-cxf endpoint in POJO data format
The `camel-cxf` endpoint producer is based on the
https://github.com/apache/cxf/blob/master/core/src/main/java/org/apache/cxf/endpoint/Client.java[CXF
@@ -684,7 +684,7 @@ list.
If you want to get the object array from the message body, you can get
the body using `message.getbody(Object[].class)`, as follows:
-=== How to deal with the message for a camel-cxf endpoint in PAYLOAD data format
+== How to deal with the message for a camel-cxf endpoint in PAYLOAD data format
`PAYLOAD` means that you process the payload message from the SOAP
envelope. You can use the `Header.HEADER_LIST` as the key to set or get
@@ -695,7 +695,7 @@ elements.
for SOAP message headers and Body elements. This change enables
decoupling the native CXF message from the Camel message.
-=== How to get and set SOAP headers in POJO mode
+== How to get and set SOAP headers in POJO mode
`POJO` means that the data format is a "list of Java objects" when the
Camel-cxf endpoint produces or consumes Camel exchanges. Even though
@@ -724,7 +724,7 @@ InsertResponseOutHeaderProcessor and InsertRequestOutHeaderProcessor are
actually the same. The only difference between the two processors is
setting the direction of the inserted SOAP header.
-=== How to get and set SOAP headers in PAYLOAD mode
+== How to get and set SOAP headers in PAYLOAD mode
We've already shown how to access SOAP message (CxfPayload object) in
PAYLOAD mode (See "How to deal with the message for a camel-cxf endpoint
@@ -745,12 +745,12 @@ forwarded to the CXF service. If you do not want that these headers are
forwarded you have to remove them in the Camel header
"org.apache.cxf.headers.Header.list".
-=== SOAP headers are not available in MESSAGE mode
+== SOAP headers are not available in MESSAGE mode
SOAP headers are not available in MESSAGE mode as SOAP processing is
skipped.
-=== How to throw a SOAP Fault from Camel
+== How to throw a SOAP Fault from Camel
If you are using a `camel-cxf` endpoint to consume the SOAP request, you
may need to throw the SOAP Fault from the camel context. +
@@ -768,7 +768,7 @@ Same for using POJO data format. You can set the SOAPFault on the out
body.
[#propagate-request-response-context]
-=== How to propagate a camel-cxf endpoint's request and response context
+== How to propagate a camel-cxf endpoint's request and response context
https://github.com/apache/cxf/blob/master/core/src/main/java/org/apache/cxf/endpoint/Client.java[CXF
client API] provides a way to invoke the operation with request and
@@ -801,7 +801,7 @@ response context with the following code:
responseContext.get("javax.xml.ws.wsdl.operation").toString());
-------------------------------------------------------------------------------------------------------------
-=== Attachment Support
+== Attachment Support
*POJO Mode:* Both SOAP with Attachment and MTOM are supported (see
example in Payload Mode for enabling MTOM). However, SOAP with
@@ -842,7 +842,7 @@ you require just the SOAP XML as a String, you can set the message body
with message.getSOAPPart(), and Camel convert can do the rest of work
for you.
-=== Streaming Support in PAYLOAD mode
+== Streaming Support in PAYLOAD mode
The camel-cxf component now supports streaming of incoming
messages when using PAYLOAD mode. Previously, the incoming messages
@@ -873,7 +873,7 @@ Global system property: you can add a system property of
That sets the global default, but setting the endpoint property above
will override this value for that endpoint.
-=== Using the generic CXF Dispatch mode
+== Using the generic CXF Dispatch mode
The camel-cxf component supports the generic
https://cxf.apache.org/docs/jax-ws-dispatch-api.html[CXF dispatch
@@ -897,7 +897,7 @@ the key SOAPAction (case-insensitive).
-=== See Also
+== See Also
* Configuring Camel
* Component
diff --git a/components/camel-cxf/src/main/docs/cxfrs-component.adoc b/components/camel-cxf/src/main/docs/cxfrs-component.adoc
index 92d2bb4..d001422 100644
--- a/components/camel-cxf/src/main/docs/cxfrs-component.adoc
+++ b/components/camel-cxf/src/main/docs/cxfrs-component.adoc
@@ -1,5 +1,5 @@
[[cxfrs-component]]
-== CXF-RS Component
+= CXF-RS Component
*Available as of Camel version 2.0*
@@ -19,7 +19,7 @@ for this component:
</dependency>
-------------------------------------------------------------------------------------
-### URI format
+== URI format
[source,java]
-----------------------
@@ -43,7 +43,7 @@ For either style above, you can append options to the URI as follows:
cxfrs:bean:cxfEndpoint?resourceClasses=org.apache.camel.rs.Example
------------------------------------------------------------------
-### Options
+== Options
@@ -74,7 +74,7 @@ cxfrs:beanId:address
with the following path and query parameters:
-==== Path Parameters (2 parameters):
+=== Path Parameters (2 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -85,7 +85,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (32 parameters):
+=== Query Parameters (32 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -126,7 +126,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -166,7 +166,7 @@ https://github.com/apache/camel/blob/master/components/camel-cxf/src/main/resour
file] and http://cxf.apache.org/docs/jax-rs.html[CXF JAX-RS
documentation] for more information.
-### How to configure the REST endpoint in Camel
+== How to configure the REST endpoint in Camel
In
https://github.com/apache/camel/blob/master/components/camel-cxf/src/main/resources/schema/cxfEndpoint.xsd[camel-cxf
@@ -174,7 +174,7 @@ schema file], there are two elements for the REST endpoint definition.
*cxf:rsServer* for REST consumer, *cxf:rsClient* for REST producer. +
You can find a Camel REST service route configuration example here.
-### How to override the CXF producer address from message header
+== How to override the CXF producer address from message header
The `camel-cxfrs` producer supports to override the services address by
setting the message with the key of "CamelDestinationOverrideUrl".
@@ -185,7 +185,7 @@ setting the message with the key of "CamelDestinationOverrideUrl".
exchange.getIn().setHeader(Exchange.DESTINATION_OVERRIDE_URL, constant(getServiceAddress()));
----------------------------------------------------------------------------------------------
-### Consuming a REST Request - Simple Binding Style
+== Consuming a REST Request - Simple Binding Style
*Available as of Camel 2.11*
@@ -223,7 +223,7 @@ respected and it becomes the final response.
* In all cases, Camel headers permitted by custom or default
`HeaderFilterStrategy` are added to the HTTP response.
-#### Enabling the Simple Binding Style
+=== Enabling the Simple Binding Style
This binding style can be activated by setting the `bindingStyle`
parameter in the consumer endpoint to value `SimpleConsumer`:
@@ -234,7 +234,7 @@ parameter in the consumer endpoint to value `SimpleConsumer`:
.to("log:TEST?showAll=true");
---------------------------------------------------------
-#### Examples of request binding with different method signatures
+=== Examples of request binding with different method signatures
Below is a list of method signatures along with the expected result from
the Simple binding.
@@ -266,7 +266,7 @@ as the IN message body.
The DataHandler is unwrapped from the MessageContentsList and preserved
as the IN message body.
-#### More examples of the Simple Binding Style
+=== More examples of the Simple Binding Style
Given a JAX-RS resource class with this method:
@@ -315,7 +315,7 @@ For more examples on how to process requests and write responses can be
found
https://svn.apache.org/repos/asf/camel/trunk/components/camel-cxf/src/test/java/org/apache/camel/component/cxf/jaxrs/simplebinding/[here].
-### Consuming a REST Request - Default Binding Style
+== Consuming a REST Request - Default Binding Style
The http://cxf.apache.org/docs/jax-rs.html[CXF JAXRS front end]
implements the https://javaee.github.io/jsr311/[JAX-RS (JSR-311) API], so we can
@@ -410,7 +410,7 @@ public interface CustomerServiceResource {
}
----
-### How to invoke the REST service through camel-cxfrs producer
+== How to invoke the REST service through camel-cxfrs producer
The http://cxf.apache.org/docs/jax-rs.html[CXF JAXRS front end]
implements
diff --git a/components/camel-dataformat/src/main/docs/dataformat-component.adoc b/components/camel-dataformat/src/main/docs/dataformat-component.adoc
index 09bce42..8764039 100644
--- a/components/camel-dataformat/src/main/docs/dataformat-component.adoc
+++ b/components/camel-dataformat/src/main/docs/dataformat-component.adoc
@@ -1,12 +1,12 @@
[[dataformat-component]]
-== Data Format Component
+= Data Format Component
*Available as of Camel version 2.12*
The Dataformat component allows to use xref:manual::data-format.adoc[Data
Format] as a Camel Component.
-=== URI format
+== URI format
[source]
----
@@ -19,7 +19,7 @@ then followed by the operation which must either be `marshal` or
Format] in use. See the Data Format documentation
for which options it support.
-=== DataFormat Options
+== DataFormat Options
// component options: START
@@ -46,7 +46,7 @@ dataformat:name:operation
with the following path and query parameters:
-==== Path Parameters (2 parameters):
+=== Path Parameters (2 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -57,7 +57,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (3 parameters):
+=== Query Parameters (3 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -70,7 +70,7 @@ with the following path and query parameters:
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -98,7 +98,7 @@ The component supports 3 options, which are listed below.
|===
// spring-boot-auto-configure options: END
-=== Samples
+== Samples
For example to use the xref:jaxb-dataformat.adoc[JAXB] xref:manual::data-format.adoc[Data
Format] we can do as follows:
diff --git a/components/camel-dataset/src/main/docs/dataset-component.adoc b/components/camel-dataset/src/main/docs/dataset-component.adoc
index 290a296..0abd769 100644
--- a/components/camel-dataset/src/main/docs/dataset-component.adoc
+++ b/components/camel-dataset/src/main/docs/dataset-component.adoc
@@ -1,5 +1,5 @@
[[dataset-component]]
-== Dataset Component
+= Dataset Component
*Available as of Camel version 1.3*
@@ -21,7 +21,7 @@ data set is received.
Camel will use the xref:log-component.adoc[throughput logger] when sending
dataset's.
-=== URI format
+== URI format
[source]
----
@@ -41,7 +41,7 @@ some implementations that can be used for testing:
and `org.apache.camel.component.dataset.FileDataSet`, all of which
extend `DataSetSupport`.
-=== Options
+== Options
// component options: START
@@ -68,7 +68,7 @@ dataset:name
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -78,7 +78,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (18 parameters):
+=== Query Parameters (18 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -105,7 +105,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -136,7 +136,7 @@ The component supports 3 options, which are listed below.
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-=== Configuring DataSet
+== Configuring DataSet
Camel will lookup in the Registry for a bean
implementing the DataSet interface. So you can register your own DataSet
@@ -149,7 +149,7 @@ as:
</bean>
----
-=== Example
+== Example
For example, to test that a set of messages are sent to a queue and then
consumed from the queue without losing any messages:
@@ -171,12 +171,12 @@ Then you create a DataSet implementation, such as using the
data set is and what the messages look like etc.
-=== DataSetSupport (abstract class)
+== DataSetSupport (abstract class)
The DataSetSupport abstract class is a nice starting point for new
DataSets, and provides some useful features to derived classes.
-==== Properties on DataSetSupport
+=== Properties on DataSetSupport
[width="100%",cols="10%,10%,10%,70%",options="header",]
|===
@@ -195,11 +195,11 @@ progress. Useful for showing progress of a large load test. If < 0, then
`size` / 5, if is 0 then `size`, else set to `reportCount` value.
|===
-=== SimpleDataSet
+== SimpleDataSet
The `SimpleDataSet` extends `DataSetSupport`, and adds a default body.
-==== Additional Properties on SimpleDataSet
+=== Additional Properties on SimpleDataSet
[width="100%",cols="10%,10%,10%,70%",options="header",]
|===
@@ -212,14 +212,14 @@ configure the `SimpleDataSet` to use it by setting the
`outputTransformer` property.
|===
-=== ListDataSet
+== ListDataSet
*Available since Camel 2.17*
The List`DataSet` extends `DataSetSupport`, and adds a list of default
bodies.
-==== Additional Properties on ListDataSet
+=== Additional Properties on ListDataSet
[width="100%",cols="10%,10%,10%,70%",options="header",]
|===
@@ -240,14 +240,14 @@ the payload for the exchange will be selected using the modulus of the
`CamelDataSetIndex % defaultBodies.size()` )
|===
-=== FileDataSet
+== FileDataSet
*Available since Camel 2.17*
The `FileDataSet` extends `ListDataSet`, and adds support for loading
the bodies from a file.
-==== Additional Properties on FileDataSet
+=== Additional Properties on FileDataSet
[width="100%",cols="10%,10%,10%,70%",options="header",]
|===
diff --git a/components/camel-dataset/src/main/docs/dataset-test-component.adoc b/components/camel-dataset/src/main/docs/dataset-test-component.adoc
index dfffd0a..78f9597 100644
--- a/components/camel-dataset/src/main/docs/dataset-test-component.adoc
+++ b/components/camel-dataset/src/main/docs/dataset-test-component.adoc
@@ -1,5 +1,5 @@
[[dataset-test-component]]
-== DataSet Test Component
+= DataSet Test Component
*Available as of Camel version 1.3*
@@ -27,7 +27,7 @@ of expected messages and their message payloads are equal.
The xref:test.adoc[Test] component is provided
directly in the camel-core.
-=== URI format
+== URI format
[source]
----
@@ -38,7 +38,7 @@ Where *expectedMessagesEndpointUri* refers to some other
Component URI that the expected message bodies are
pulled from before starting the test.
-=== URI Options
+== URI Options
// component options: START
The DataSet Test component supports 2 options, which are listed below.
@@ -63,7 +63,7 @@ dataset-test:name
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -73,7 +73,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (16 parameters):
+=== Query Parameters (16 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -98,7 +98,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -127,7 +127,7 @@ The component supports 3 options, which are listed below.
// spring-boot-auto-configure options: END
-=== Example
+== Example
For example, you could write a test case as follows:
@@ -144,6 +144,6 @@ method], your test case will perform the necessary assertions.
To see how you can set other expectations on the test endpoint, see the
xref:mock-component.adoc[Mock] component.
-=== See Also
+== See Also
* Spring Testing
diff --git a/components/camel-digitalocean/src/main/docs/digitalocean-component.adoc b/components/camel-digitalocean/src/main/docs/digitalocean-component.adoc
index 74e3476..8e473e4 100644
--- a/components/camel-digitalocean/src/main/docs/digitalocean-component.adoc
+++ b/components/camel-digitalocean/src/main/docs/digitalocean-component.adoc
@@ -1,15 +1,15 @@
[[digitalocean-component]]
-== DigitalOcean Component
+= DigitalOcean Component
*Available as of Camel version 2.19*
The DigitalOcean component allows you to manage Droplets and resources within the DigitalOcean cloud with **Camel** by encapsulating https://www.digitalocean.com/community/projects/api-client-in-java[digitalocean-api-java]. All of the functionality that you are familiar with in the DigitalOcean control panel is also available through this Camel component.
-=== Prerequisites
+== Prerequisites
You must have a valid DigitalOcean account and a valid OAuth token. You can generate an OAuth token by visiting the [Apps & API] section of the DigitalOcean control panel for your account.
-=== URI format
+== URI format
The **DigitalOcean Component** uses the following URI format:
@@ -27,7 +27,7 @@ digitalocean://droplets?operation=list&oAuthToken=XXXXXX&page=1&perPage=10
The DigitalOcean component only supports producer endpoints so you cannot use this component at the beginning of a route to listen to messages in a channel.
-=== Options
+== Options
// component options: START
@@ -52,7 +52,7 @@ digitalocean:operation
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -62,7 +62,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (12 parameters):
+=== Query Parameters (12 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -83,7 +83,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -120,17 +120,17 @@ All **operation** values are defined in `DigitalOceanOperations` enumeration.
All **header** names used by the component are defined in `DigitalOceanHeaders` enumeration.
-=== Message body result
+== Message body result
All message bodies returned are using objects provided by the **digitalocean-api-java** library.
-=== API Rate Limits
+== API Rate Limits
DigitalOcean REST API encapsulated by camel-digitalocean component is subjected to API Rate Limiting. You can find the per method limits in the https://developers.digitalocean.com/documentation/v2/#rate-limit[API Rate Limits documentation].
-=== Account endpoint
+== Account endpoint
[width="100%",cols="2,5,^1,2",options="header"]
|===
@@ -138,7 +138,7 @@ DigitalOcean REST API encapsulated by camel-digitalocean component is subjected
| `get` | get account info | | `com.myjeeva.digitalocean.pojo.Account`
|===
-=== BlockStorages endpoint
+== BlockStorages endpoint
[width="100%",cols="2,5,^5a,1",options="header"]
|===
@@ -223,7 +223,7 @@ DigitalOcean REST API encapsulated by camel-digitalocean component is subjected
| `List<com.myjeeva.digitalocean.pojo.Action>`
|===
-=== Droplets endpoint
+== Droplets endpoint
[width="100%",cols="2,5,^1,2",options="header"]
|===
@@ -330,7 +330,7 @@ DigitalOcean REST API encapsulated by camel-digitalocean component is subjected
| `listAllNeighbors` | retrieve a list of any droplets that are running on the same physical hardware | | `List<com.myjeeva.digitalocean.pojo.Droplet>`
|===
-=== Images endpoint
+== Images endpoint
[width="100%",cols="2,5,^1,2",options="header"]
|===
@@ -358,7 +358,7 @@ DigitalOcean REST API encapsulated by camel-digitalocean component is subjected
| `convert` | convert an image, for example, a backup to a snapshot| `CamelDigitalOceanId` _Integer_ | `com.myjeeva.digitalocean.pojo.Action`
|===
-=== Snapshots endpoint
+== Snapshots endpoint
[width="100%",cols="2,5,^1,2",options="header"]
|===
@@ -368,7 +368,7 @@ DigitalOcean REST API encapsulated by camel-digitalocean component is subjected
| `delete` | delete an snapshot| `CamelDigitalOceanId` _Integer_ | `com.myjeeva.digitalocean.pojo.Delete`
|===
-=== Keys endpoint
+== Keys endpoint
[width="100%",cols="2,5,^1,2",options="header"]
|===
@@ -393,7 +393,7 @@ DigitalOcean REST API encapsulated by camel-digitalocean component is subjected
| `delete` | delete a key by fingerprint| `CamelDigitalOceanKeyFingerprint` _String_ | `com.myjeeva.digitalocean.pojo.Delete`
|===
-=== Regions endpoint
+== Regions endpoint
[width="100%",cols="2,5,^1,2",options="header"]
|===
@@ -401,7 +401,7 @@ DigitalOcean REST API encapsulated by camel-digitalocean component is subjected
| `list` | list all of the regions that are available | | `List<com.myjeeva.digitalocean.pojo.Region>`
|===
-=== Sizes endpoint
+== Sizes endpoint
[width="100%",cols="2,5,^1,2",options="header"]
|===
@@ -409,7 +409,7 @@ DigitalOcean REST API encapsulated by camel-digitalocean component is subjected
| `list` | list all of the sizes that are available | | `List<com.myjeeva.digitalocean.pojo.Size>`
|===
-=== Floating IPs endpoint
+== Floating IPs endpoint
[width="100%",cols="2,5,^1,2",options="header"]
|===
@@ -430,7 +430,7 @@ DigitalOcean REST API encapsulated by camel-digitalocean component is subjected
| `listActions` | retrieve all actions that have been executed on a Floating IP | `CamelDigitalOceanFloatingIPAddress` _String_ | `List<com.myjeeva.digitalocean.pojo.Action>`
|===
-=== Tags endpoint
+== Tags endpoint
[width="100%",cols="2,5,^4,2",options="header"]
|===
@@ -447,7 +447,7 @@ DigitalOcean REST API encapsulated by camel-digitalocean component is subjected
| `com.myjeeva.digitalocean.pojo.Tag`
|===
-=== Examples
+== Examples
Get your account info
diff --git a/components/camel-direct/src/main/docs/direct-component.adoc b/components/camel-direct/src/main/docs/direct-component.adoc
index 4e0af95..230275f 100644
--- a/components/camel-direct/src/main/docs/direct-component.adoc
+++ b/components/camel-direct/src/main/docs/direct-component.adoc
@@ -1,5 +1,5 @@
[[direct-component]]
-== Direct Component
+= Direct Component
*Available as of Camel version 1.0*
@@ -16,7 +16,7 @@ TIP: *Connection to other camel contexts*
The xref:vm-component.adoc[VM] component provides connections between Camel
contexts as long they run in the same *JVM*.
-=== URI format
+== URI format
[source]
----
@@ -25,7 +25,7 @@ direct:someName[?options]
Where *someName* can be any string to uniquely identify the endpoint
-=== Options
+== Options
@@ -56,7 +56,7 @@ direct:name
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -66,7 +66,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (9 parameters):
+=== Query Parameters (9 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -85,7 +85,7 @@ with the following path and query parameters:
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -115,7 +115,7 @@ The component supports 5 options, which are listed below.
|===
// spring-boot-auto-configure options: END
-=== Samples
+== Samples
In the route below we use the direct component to link the two routes
together:
@@ -151,7 +151,7 @@ And the sample using spring DSL:
See also samples from the xref:seda-component.adoc[SEDA] component, how they can
be used together.
-=== See Also
+== See Also
* xref:seda-component.adoc[SEDA]
* xref:vm-component.adoc[VM]
diff --git a/components/camel-directvm/src/main/docs/direct-vm-component.adoc b/components/camel-directvm/src/main/docs/direct-vm-component.adoc
index 2465ca9..842f434 100644
--- a/components/camel-directvm/src/main/docs/direct-vm-component.adoc
+++ b/components/camel-directvm/src/main/docs/direct-vm-component.adoc
@@ -1,5 +1,5 @@
[[direct-vm-component]]
-== Direct VM Component
+= Direct VM Component
*Available as of Camel version 2.10*
@@ -27,7 +27,7 @@ Transactions - Tx.
image:camel-direct-vm.png[image]
-=== URI format
+== URI format
[source]
----
@@ -36,7 +36,7 @@ direct-vm:someName
Where *someName* can be any string to uniquely identify the endpoint
-=== Options
+== Options
@@ -69,7 +69,7 @@ direct-vm:name
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -79,7 +79,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (11 parameters):
+=== Query Parameters (11 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -100,7 +100,7 @@ with the following path and query parameters:
// endpoint options: END
-=== Samples
+== Samples
In the route below we use the direct component to link the two routes
together:
@@ -138,7 +138,7 @@ And the sample using spring DSL:
</route>
----
-=== See Also
+== See Also
* xref:direct-component.adoc[Direct]
* xref:seda-component.adoc[SEDA]
diff --git a/components/camel-disruptor/src/main/docs/disruptor-component.adoc b/components/camel-disruptor/src/main/docs/disruptor-component.adoc
index c937383..fd1d98a 100644
--- a/components/camel-disruptor/src/main/docs/disruptor-component.adoc
+++ b/components/camel-disruptor/src/main/docs/disruptor-component.adoc
@@ -1,5 +1,5 @@
[[disruptor-component]]
-== Disruptor Component
+= Disruptor Component
*Available as of Camel version 2.12*
@@ -62,7 +62,7 @@ for this component:
</dependency>
------------------------------------------------------------
-### URI format
+== URI format
[source,java]
-----------------------------
@@ -87,7 +87,7 @@ across contexts in case of +
?option=value&option=value&…
------------------------------
-### Options
+== Options
All the following options are valid for both the **disruptor:** and
**disruptor-vm:** components.
@@ -126,7 +126,7 @@ disruptor:name
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -136,7 +136,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (14 parameters):
+=== Query Parameters (14 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -159,7 +159,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -206,7 +206,7 @@ The component supports 20 options, which are listed below.
-### Wait strategies
+== Wait strategies
The wait strategy effects the type of waiting performed by the consumer
threads that are currently waiting for the next exchange to be
@@ -235,7 +235,7 @@ barrier after an initially spinning. |This strategy is a good compromise between
without incurring significant latency spikes.
|=======================================================================
-### Use of Request Reply
+== Use of Request Reply
The Disruptor component supports using xref:manual::requestReply-eip.adoc[Request
Reply], where the caller will wait for the Async route to complete. For
@@ -253,7 +253,7 @@ buffer. As it is a Request Reply message, we
wait for the response. When the consumer on the _disruptor:input_ buffer
is complete, it copies the response to the original message response.
-### Concurrent consumers
+== Concurrent consumers
By default, the Disruptor endpoint uses a single consumer thread, but
you can configure it to use concurrent consumer threads. So instead of
@@ -269,7 +269,7 @@ increase/shrink dynamically at runtime depending on load, whereas the
number of concurrent consumers is always fixed and supported by the
Disruptor internally so performance will be higher.
-### Thread pools
+== Thread pools
Be aware that adding a thread pool to a Disruptor endpoint by doing
something like:
@@ -286,7 +286,7 @@ of the performance gains achieved by using the Disruptor. Instead, it is
advices to directly configure number of threads that process messages on
a Disruptor endpoint using the concurrentConsumers option.
-### Sample
+== Sample
In the route below we use the Disruptor to send the request to this
async queue to be able to send a fire-and-forget message for further
@@ -319,7 +319,7 @@ another thread for further processing. Since this is from a unit test,
it will be sent to a mock endpoint where we can do assertions in the
unit test.
-### Using multipleConsumers
+== Using multipleConsumers
In this example we have defined two consumers and registered them as
spring beans.
@@ -358,7 +358,7 @@ public class FooEventConsumer {
}
-------------------------------------------
-### Extracting disruptor information
+== Extracting disruptor information
If needed, information such as buffer size, etc. can be obtained without
using JMX in this fashion:
diff --git a/components/camel-dns/src/main/docs/dns-component.adoc b/components/camel-dns/src/main/docs/dns-component.adoc
index 7416915..617c251 100644
--- a/components/camel-dns/src/main/docs/dns-component.adoc
+++ b/components/camel-dns/src/main/docs/dns-component.adoc
@@ -1,5 +1,5 @@
[[dns-component]]
-== DNS Component
+= DNS Component
*Available as of Camel version 2.7*
@@ -36,7 +36,7 @@ for this component:
</dependency>
----
-=== URI format
+== URI format
The URI scheme for a DNS component is as follows
@@ -47,7 +47,7 @@ dns://operation[?options]
This component only supports producers.
-=== Options
+== Options
// component options: START
@@ -74,7 +74,7 @@ dns:dnsType
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -84,7 +84,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (3 parameters):
+=== Query Parameters (3 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -96,7 +96,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -126,7 +126,7 @@ The component supports 3 options, which are listed below.
-=== Headers
+== Headers
[width="100%",cols="10%,10%,10%,70%",options="header",]
|===
@@ -148,9 +148,9 @@ Optional.
one specified by the OS will be used. Optional.
|===
-=== Examples
+== Examples
-==== IP lookup
+=== IP lookup
[source,xml]
----
@@ -165,7 +165,7 @@ This looks up a domain's IP. For example, www.example.com resolves to
The IP address to lookup must be provided in the header with key
`"dns.domain"`.
-==== DNS lookup
+=== DNS lookup
[source,xml]
----
@@ -179,7 +179,7 @@ This returns a set of DNS records associated with a domain. +
The name to lookup must be provided in the header with key
`"dns.name"`.
-==== DNS Dig
+=== DNS Dig
Dig is a Unix command-line utility to run DNS queries.
@@ -194,7 +194,7 @@ Dig is a Unix command-line utility to run DNS queries.
The query must be provided in the header with key `"dns.query"`.
-=== Dns Activation Policy
+== Dns Activation Policy
DnsActivationPolicy can be used to dynamically start and stop routes based on dns state.
diff --git a/components/camel-docker/src/main/docs/docker-component.adoc b/components/camel-docker/src/main/docs/docker-component.adoc
index 50db6b0..cf3fa15 100644
--- a/components/camel-docker/src/main/docs/docker-component.adoc
+++ b/components/camel-docker/src/main/docs/docker-component.adoc
@@ -1,5 +1,5 @@
[[docker-component]]
-== Docker Component
+= Docker Component
*Available as of Camel version 2.15*
@@ -11,7 +11,7 @@ https://docs.docker.com/reference/api/docker_remote_api[Docker Remote
API].
-### URI format
+== URI format
[source,java]
------------------------------
@@ -20,7 +20,7 @@ docker://[operation]?[options]
Where *operation* is the specific action to perform on Docker.
-### General Options
+== General Options
// component options: START
The Docker component supports 3 options, which are listed below.
@@ -46,7 +46,7 @@ docker:operation
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -56,7 +56,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (22 parameters):
+=== Query Parameters (22 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -87,7 +87,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -134,7 +134,7 @@ The component supports 21 options, which are listed below.
// spring-boot-auto-configure options: END
-### Header Strategy
+== Header Strategy
All URI option can be passed as Header properties. Values found in a
message header take precedence over URI parameters. A header property
@@ -149,7 +149,7 @@ below
|=======================================================================
-### Examples
+== Examples
The following example consumes events from Docker:
@@ -166,7 +166,7 @@ from("docker://info?host=192.168.59.103&port=2375").to("log:info");
-------------------------------------------------------------------
-### Dependencies
+== Dependencies
To use Docker in your Camel routes you need to add a dependency on
*camel-docker*, which implements the component.
diff --git a/components/camel-dozer/src/main/docs/dozer-component.adoc b/components/camel-dozer/src/main/docs/dozer-component.adoc
index b94f5cb..dedcdae 100644
--- a/components/camel-dozer/src/main/docs/dozer-component.adoc
+++ b/components/camel-dozer/src/main/docs/dozer-component.adoc
@@ -1,5 +1,5 @@
[[dozer-component]]
-== Dozer Component
+= Dozer Component
*Available as of Camel version 2.15*
@@ -33,7 +33,7 @@ following dependency to their `pom.xml`:
</dependency>
------------------------------------------------------------
-### URI format
+== URI format
The Dozer component only supports producer endpoints.
@@ -54,7 +54,7 @@ from("direct:orderInput").
to("direct:orderOutput");
---------------------------------------------------------------------------------------
-### Options
+== Options
// component options: START
The Dozer component supports 2 options, which are listed below.
@@ -78,7 +78,7 @@ dozer:name
with the following path and query parameters:
-==== Path Parameters (1 parameters):
+=== Path Parameters (1 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -88,7 +88,7 @@ with the following path and query parameters:
|===
-==== Query Parameters (9 parameters):
+=== Query Parameters (9 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -106,7 +106,7 @@ with the following path and query parameters:
|===
// endpoint options: END
// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
+== Spring Boot Auto-Configuration
When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
@@ -135,7 +135,7 @@ The component supports 3 options, which are listed below.
// spring-boot-auto-configure options: END
-### Using Data Formats with Dozer
+== Using Data Formats with Dozer
Dozer does not support non-Java sources and targets for mappings, so it
cannot, for example, map an XML document to a Java object on its own.
@@ -169,7 +169,7 @@ using a JAXB data format and marshal the mapping output using Jackson.
<endpoint uri="dozer:xml2json?marshalId=myjson&unmarshalId=myjaxb&targetModel=org.example.Order"/>
----------------------------------------------------------------------------------------------------------
-### Configuring Dozer
+== Configuring Dozer
All Dozer endpoints require a Dozer mapping configuration file which
defines mappings between source and target objects. The component will
@@ -192,13 +192,13 @@ of `org.apache.camel.converter.dozer.DozerBeanMapperConfiguration`.
</bean>
------------------------------------------------------------------------------------------
-### Mapping Extensions
+== Mapping Extensions
The Dozer component implements a number of extensions to the Dozer
mapping framework as custom converters. These converters implement
... 81804 lines suppressed ...