You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by dj...@apache.org on 2021/10/14 03:16:57 UTC
[camel-spring-boot] 04/05: remove no-longer-needed adoc partials
This is an automated email from the ASF dual-hosted git repository.
djencks pushed a commit to branch camel-spring-boot-3.7.x
in repository https://gitbox.apache.org/repos/asf/camel-spring-boot.git
commit 59958e5fee93a1e0d50476464641d4f5710ba58e
Author: David Jencks <dj...@apache.org>
AuthorDate: Wed Oct 6 23:24:38 2021 -0700
remove no-longer-needed adoc partials
---
.../src/main/docs/activemq-starter.adoc | 129 ---------------
.../src/main/docs/ahc-starter.adoc | 38 -----
.../src/main/docs/ahc-ws-starter.adoc | 39 -----
.../src/main/docs/amqp-starter.adoc | 126 ---------------
.../src/main/docs/any23-starter.adoc | 33 ----
.../src/main/docs/apns-starter.adoc | 33 ----
.../src/main/docs/arangodb-starter.adoc | 41 -----
.../src/main/docs/as2-starter.adoc | 33 ----
.../src/main/docs/asn1-starter.adoc | 31 ----
.../src/main/docs/asterisk-starter.adoc | 32 ----
.../src/main/docs/atlasmap-starter.adoc | 32 ----
.../src/main/docs/atmos-starter.adoc | 36 -----
.../main/docs/atmosphere-websocket-starter.adoc | 40 -----
.../src/main/docs/atom-starter.adoc | 31 ----
.../src/main/docs/atomix-starter.adoc | 149 ------------------
.../src/main/docs/avro-rpc-starter.adoc | 39 -----
.../src/main/docs/avro-starter.adoc | 30 ----
.../src/main/docs/aws-cw-starter.adoc | 44 ------
.../src/main/docs/aws-ddb-starter.adoc | 61 -------
.../src/main/docs/aws-ec2-starter.adoc | 41 -----
.../src/main/docs/aws-ecs-starter.adoc | 41 -----
.../src/main/docs/aws-eks-starter.adoc | 41 -----
.../src/main/docs/aws-iam-starter.adoc | 41 -----
.../src/main/docs/aws-kinesis-starter.adoc | 58 -------
.../src/main/docs/aws-kms-starter.adoc | 41 -----
.../src/main/docs/aws-lambda-starter.adoc | 41 -----
.../src/main/docs/aws-mq-starter.adoc | 41 -----
.../src/main/docs/aws-msk-starter.adoc | 41 -----
.../src/main/docs/aws-s3-starter.adoc | 68 --------
.../src/main/docs/aws-sdb-starter.adoc | 31 ----
.../src/main/docs/aws-ses-starter.adoc | 44 ------
.../src/main/docs/aws-sns-starter.adoc | 49 ------
.../src/main/docs/aws-sqs-starter.adoc | 68 --------
.../src/main/docs/aws-swf-starter.adoc | 59 -------
.../src/main/docs/aws-translate-starter.adoc | 44 ------
.../src/main/docs/aws2-athena-starter.adoc | 58 -------
.../src/main/docs/aws2-cw-starter.adoc | 44 ------
.../src/main/docs/aws2-ddb-starter.adoc | 61 -------
.../src/main/docs/aws2-ec2-starter.adoc | 42 -----
.../src/main/docs/aws2-ecs-starter.adoc | 42 -----
.../src/main/docs/aws2-eks-starter.adoc | 42 -----
.../src/main/docs/aws2-eventbridge-starter.adoc | 43 -----
.../src/main/docs/aws2-iam-starter.adoc | 42 -----
.../src/main/docs/aws2-kinesis-starter.adoc | 61 -------
.../src/main/docs/aws2-kms-starter.adoc | 42 -----
.../src/main/docs/aws2-lambda-starter.adoc | 42 -----
.../src/main/docs/aws2-mq-starter.adoc | 42 -----
.../src/main/docs/aws2-msk-starter.adoc | 42 -----
.../src/main/docs/aws2-s3-starter.adoc | 71 ---------
.../src/main/docs/aws2-ses-starter.adoc | 44 ------
.../src/main/docs/aws2-sns-starter.adoc | 51 ------
.../src/main/docs/aws2-sqs-starter.adoc | 69 --------
.../src/main/docs/aws2-sts-starter.adoc | 42 -----
.../src/main/docs/aws2-translate-starter.adoc | 45 ------
.../src/main/docs/azure-eventhubs-starter.adoc | 50 ------
.../src/main/docs/azure-starter.adoc | 65 --------
.../src/main/docs/azure-storage-blob-starter.adoc | 57 -------
.../src/main/docs/azure-storage-queue-starter.adoc | 45 ------
.../src/main/docs/barcode-starter.adoc | 33 ----
.../src/main/docs/base64-starter.adoc | 32 ----
.../src/main/docs/bean-starter.adoc | 41 -----
.../src/main/docs/bean-validator-starter.adoc | 37 -----
.../src/main/docs/beanio-starter.adoc | 37 -----
.../src/main/docs/beanstalk-starter.adoc | 33 ----
.../src/main/docs/bindy-starter.adoc | 46 ------
.../src/main/docs/bonita-starter.adoc | 31 ----
.../src/main/docs/box-starter.adoc | 48 ------
.../src/main/docs/braintree-starter.adoc | 32 ----
.../src/main/docs/browse-starter.adoc | 32 ----
.../src/main/docs/caffeine-starter.adoc | 64 --------
.../src/main/docs/cassandraql-starter.adoc | 32 ----
.../src/main/docs/cbor-starter.adoc | 39 -----
.../src/main/docs/chatscript-starter.adoc | 31 ----
.../src/main/docs/chunk-starter.adoc | 33 ----
.../src/main/docs/cm-sms-starter.adoc | 31 ----
.../src/main/docs/cmis-starter.adoc | 33 ----
.../src/main/docs/coap-starter.adoc | 32 ----
.../src/main/docs/cometd-starter.adoc | 39 -----
.../src/main/docs/consul-starter.adoc | 118 --------------
.../src/main/docs/controlbus-starter.adoc | 31 ----
.../src/main/docs/corda-starter.adoc | 43 -----
.../src/main/docs/core-starter.adoc | 175 ---------------------
.../src/main/docs/couchbase-starter.adoc | 32 ----
.../src/main/docs/couchdb-starter.adoc | 32 ----
.../src/main/docs/cron-starter.adoc | 32 ----
.../src/main/docs/crypto-cms-starter.adoc | 33 ----
.../src/main/docs/crypto-starter.adoc | 75 ---------
.../src/main/docs/csv-starter.adoc | 57 -------
.../src/main/docs/cxf-starter.adoc | 41 -----
.../src/main/docs/dataformat-starter.adoc | 31 ----
.../src/main/docs/dataset-starter.adoc | 35 -----
.../src/main/docs/datasonnet-starter.adoc | 34 ----
.../src/main/docs/debezium-mongodb-starter.adoc | 83 ----------
.../src/main/docs/debezium-mysql-starter.adoc | 108 -------------
.../src/main/docs/debezium-postgres-starter.adoc | 113 -------------
.../src/main/docs/debezium-sqlserver-starter.adoc | 93 -----------
.../src/main/docs/digitalocean-starter.adoc | 31 ----
.../src/main/docs/direct-starter.adoc | 34 ----
.../src/main/docs/directvm-starter.adoc | 36 -----
.../src/main/docs/disruptor-starter.adoc | 48 ------
.../src/main/docs/djl-starter.adoc | 31 ----
.../src/main/docs/dns-starter.adoc | 31 ----
.../src/main/docs/docker-starter.adoc | 50 ------
.../src/main/docs/dozer-starter.adoc | 31 ----
.../src/main/docs/drill-starter.adoc | 31 ----
.../src/main/docs/dropbox-starter.adoc | 32 ----
.../src/main/docs/ehcache-starter.adoc | 49 ------
.../src/main/docs/elasticsearch-rest-starter.adoc | 42 -----
.../src/main/docs/elsql-starter.adoc | 35 -----
.../src/main/docs/etcd-starter.adoc | 71 ---------
.../src/main/docs/exec-starter.adoc | 31 ----
.../src/main/docs/facebook-starter.adoc | 60 -------
.../src/main/docs/fastjson-starter.adoc | 31 ----
.../src/main/docs/fhir-starter.adoc | 84 ----------
.../src/main/docs/file-starter.adoc | 39 -----
.../src/main/docs/file-watch-starter.adoc | 36 -----
.../src/main/docs/flatpack-starter.adoc | 41 -----
.../src/main/docs/flink-starter.adoc | 34 ----
.../src/main/docs/fop-starter.adoc | 31 ----
.../src/main/docs/freemarker-starter.adoc | 34 ----
.../src/main/docs/ftp-starter.adoc | 41 -----
.../src/main/docs/ganglia-starter.adoc | 44 ------
.../src/main/docs/geocoder-starter.adoc | 32 ----
.../src/main/docs/git-starter.adoc | 32 ----
.../src/main/docs/github-starter.adoc | 33 ----
.../src/main/docs/google-bigquery-starter.adoc | 39 -----
.../src/main/docs/google-calendar-starter.adoc | 59 -------
.../src/main/docs/google-drive-starter.adoc | 40 -----
.../src/main/docs/google-mail-starter.adoc | 53 -------
.../src/main/docs/google-pubsub-starter.adoc | 36 -----
.../src/main/docs/google-sheets-starter.adoc | 58 -------
.../src/main/docs/gora-starter.adoc | 32 ----
.../src/main/docs/grape-starter.adoc | 32 ----
.../src/main/docs/graphql-starter.adoc | 31 ----
.../src/main/docs/grok-starter.adoc | 33 ----
.../src/main/docs/groovy-starter.adoc | 31 ----
.../src/main/docs/grpc-starter.adoc | 32 ----
.../src/main/docs/gson-starter.adoc | 32 ----
.../src/main/docs/guava-eventbus-starter.adoc | 34 ----
.../src/main/docs/hazelcast-starter.adoc | 113 -------------
.../src/main/docs/hbase-starter.adoc | 34 ----
.../src/main/docs/hdfs-starter.adoc | 34 ----
.../src/main/docs/hl7-starter.adoc | 32 ----
.../src/main/docs/http-starter.adoc | 55 -------
.../src/main/docs/hystrix-starter.adoc | 32 ----
.../src/main/docs/ical-starter.adoc | 30 ----
.../src/main/docs/iec60870-starter.adoc | 38 -----
.../src/main/docs/ignite-starter.adoc | 72 ---------
.../src/main/docs/infinispan-starter.adoc | 62 --------
.../src/main/docs/influxdb-starter.adoc | 32 ----
.../src/main/docs/iota-starter.adoc | 31 ----
.../src/main/docs/ipfs-starter.adoc | 33 ----
.../src/main/docs/irc-starter.adoc | 33 ----
.../src/main/docs/ironmq-starter.adoc | 32 ----
.../src/main/docs/jackson-starter.adoc | 46 ------
.../src/main/docs/jacksonxml-starter.adoc | 44 ------
.../src/main/docs/jasypt-starter.adoc | 34 ----
.../src/main/docs/jaxb-starter.adoc | 48 ------
.../src/main/docs/jbpm-starter.adoc | 32 ----
.../src/main/docs/jcache-starter.adoc | 37 -----
.../src/main/docs/jclouds-starter.adoc | 34 ----
.../src/main/docs/jcr-starter.adoc | 32 ----
.../src/main/docs/jdbc-starter.adoc | 31 ----
.../src/main/docs/jetty-starter.adoc | 61 -------
.../src/main/docs/jgroups-raft-starter.adoc | 41 -----
.../src/main/docs/jgroups-starter.adoc | 39 -----
.../src/main/docs/jing-starter.adoc | 31 ----
.../src/main/docs/jira-starter.adoc | 41 -----
.../src/main/docs/jms-starter.adoc | 125 ---------------
.../src/main/docs/jmx-starter.adoc | 31 ----
.../src/main/docs/johnzon-starter.adoc | 32 ----
.../src/main/docs/jolt-starter.adoc | 33 ----
.../src/main/docs/jooq-starter.adoc | 37 -----
.../src/main/docs/joor-starter.adoc | 34 ----
.../src/main/docs/jpa-starter.adoc | 36 -----
.../src/main/docs/jsch-starter.adoc | 32 ----
.../src/main/docs/jslt-starter.adoc | 34 ----
.../src/main/docs/json-validator-starter.adoc | 31 ----
.../src/main/docs/jsonapi-starter.adoc | 31 ----
.../src/main/docs/jsonata-starter.adoc | 31 ----
.../src/main/docs/jsonb-starter.adoc | 34 ----
.../src/main/docs/jsonpath-starter.adoc | 36 -----
.../src/main/docs/jt400-starter.adoc | 33 ----
.../src/main/docs/kafka-starter.adoc | 126 ---------------
.../src/main/docs/kubernetes-starter.adoc | 102 ------------
.../src/main/docs/kudu-starter.adoc | 31 ----
.../src/main/docs/language-starter.adoc | 31 ----
.../src/main/docs/ldap-starter.adoc | 31 ----
.../src/main/docs/ldif-starter.adoc | 31 ----
.../src/main/docs/log-starter.adoc | 32 ----
.../src/main/docs/lra-starter.adoc | 34 ----
.../src/main/docs/lucene-starter.adoc | 36 -----
.../src/main/docs/lumberjack-starter.adoc | 33 ----
.../src/main/docs/lzf-starter.adoc | 30 ----
.../src/main/docs/mail-starter.adoc | 77 ---------
.../src/main/docs/master-starter.adoc | 33 ----
.../src/main/docs/metrics-starter.adoc | 32 ----
.../src/main/docs/micrometer-starter.adoc | 32 ----
.../src/main/docs/milo-starter.adoc | 74 ---------
.../src/main/docs/mina-starter.adoc | 57 -------
.../src/main/docs/minio-starter.adoc | 76 ---------
.../src/main/docs/mllp-starter.adoc | 35 -----
.../src/main/docs/mock-starter.adoc | 31 ----
.../src/main/docs/mongodb-gridfs-starter.adoc | 32 ----
.../src/main/docs/mongodb-starter.adoc | 33 ----
.../src/main/docs/msv-starter.adoc | 33 ----
.../src/main/docs/mustache-starter.adoc | 34 ----
.../src/main/docs/mvel-starter.adoc | 35 -----
.../src/main/docs/mybatis-starter.adoc | 39 -----
.../src/main/docs/nagios-starter.adoc | 36 -----
.../src/main/docs/nats-starter.adoc | 35 -----
.../src/main/docs/netty-http-starter.adoc | 91 -----------
.../src/main/docs/netty-starter.adoc | 102 ------------
.../src/main/docs/nitrite-starter.adoc | 32 ----
.../src/main/docs/nsq-starter.adoc | 34 ----
.../src/main/docs/oaipmh-starter.adoc | 32 ----
.../src/main/docs/ognl-starter.adoc | 31 ----
.../src/main/docs/olingo2-starter.adoc | 47 ------
.../src/main/docs/olingo4-starter.adoc | 45 ------
.../src/main/docs/openstack-starter.adoc | 46 ------
.../src/main/docs/opentelemetry-starter.adoc | 32 ----
.../src/main/docs/opentracing-starter.adoc | 31 ----
.../src/main/docs/optaplanner-starter.adoc | 32 ----
.../src/main/docs/paho-starter.adoc | 60 -------
.../src/main/docs/pdf-starter.adoc | 31 ----
.../src/main/docs/pg-replication-slot-starter.adoc | 31 ----
.../src/main/docs/pgevent-starter.adoc | 32 ----
.../src/main/docs/platform-http-starter.adoc | 32 ----
.../src/main/docs/printer-starter.adoc | 31 ----
.../src/main/docs/protobuf-starter.adoc | 32 ----
.../src/main/docs/pubnub-starter.adoc | 32 ----
.../src/main/docs/pulsar-starter.adoc | 65 --------
.../src/main/docs/quartz-starter.adoc | 42 -----
.../src/main/docs/quickfix-starter.adoc | 36 -----
.../src/main/docs/rabbitmq-starter.adoc | 85 ----------
.../src/main/docs/reactive-streams-starter.adoc | 38 -----
.../src/main/docs/ref-starter.adoc | 32 ----
.../src/main/docs/rest-openapi-starter.adoc | 39 -----
.../src/main/docs/rest-starter.adoc | 40 -----
.../src/main/docs/rest-swagger-starter.adoc | 39 -----
.../src/main/docs/resteasy-starter.adoc | 35 -----
.../src/main/docs/robotframework-starter.adoc | 80 ----------
.../src/main/docs/rss-starter.adoc | 32 ----
.../src/main/docs/saga-starter.adoc | 31 ----
.../src/main/docs/salesforce-starter.adoc | 105 -------------
.../src/main/docs/sap-netweaver-starter.adoc | 31 ----
.../src/main/docs/saxon-starter.adoc | 39 -----
.../src/main/docs/scheduler-starter.adoc | 32 ----
.../src/main/docs/schematron-starter.adoc | 31 ----
.../src/main/docs/seda-starter.adoc | 38 -----
.../src/main/docs/service-starter.adoc | 33 ----
.../src/main/docs/servicenow-starter.adoc | 77 ---------
.../src/main/docs/servlet-starter.adoc | 42 -----
.../src/main/docs/sip-starter.adoc | 32 ----
.../src/main/docs/sjms-starter.adoc | 55 -------
.../src/main/docs/sjms2-starter.adoc | 48 ------
.../src/main/docs/slack-starter.adoc | 33 ----
.../src/main/docs/smpp-starter.adoc | 67 --------
.../src/main/docs/snakeyaml-starter.adoc | 39 -----
.../src/main/docs/snmp-starter.adoc | 32 ----
.../src/main/docs/soap-starter.adoc | 35 -----
.../src/main/docs/solr-starter.adoc | 31 ----
.../src/main/docs/soroush-starter.adoc | 33 ----
.../src/main/docs/spark-starter.adoc | 33 ----
.../src/main/docs/splunk-starter.adoc | 33 ----
.../src/main/docs/spring-batch-starter.adoc | 33 ----
.../src/main/docs/spring-integration-starter.adoc | 32 ----
.../src/main/docs/spring-ldap-starter.adoc | 31 ----
.../src/main/docs/spring-redis-starter.adoc | 32 ----
.../src/main/docs/spring-starter.adoc | 34 ----
.../src/main/docs/spring-ws-starter.adoc | 33 ----
.../src/main/docs/sql-starter.adoc | 36 -----
.../src/main/docs/ssh-starter.adoc | 46 ------
.../src/main/docs/stax-starter.adoc | 31 ----
.../src/main/docs/stomp-starter.adoc | 42 -----
.../src/main/docs/stream-starter.adoc | 32 ----
.../src/main/docs/stringtemplate-starter.adoc | 33 ----
.../src/main/docs/stub-starter.adoc | 38 -----
.../src/main/docs/syslog-starter.adoc | 29 ----
.../src/main/docs/tagsoup-starter.adoc | 31 ----
.../src/main/docs/tarfile-starter.adoc | 33 ----
.../src/main/docs/telegram-starter.adoc | 36 -----
.../src/main/docs/thrift-starter.adoc | 37 -----
.../src/main/docs/tika-starter.adoc | 31 ----
.../src/main/docs/timer-starter.adoc | 31 ----
.../src/main/docs/twilio-starter.adoc | 37 -----
.../src/main/docs/twitter-starter.adoc | 64 --------
.../docs/undertow-spring-security-starter.adoc | 33 ----
.../src/main/docs/undertow-starter.adoc | 40 -----
.../src/main/docs/univocity-parsers-starter.adoc | 78 ---------
.../src/main/docs/validator-starter.adoc | 32 ----
.../src/main/docs/velocity-starter.adoc | 34 ----
.../src/main/docs/vertx-http-starter.adoc | 46 ------
.../src/main/docs/vertx-kafka-starter.adoc | 127 ---------------
.../src/main/docs/vertx-starter.adoc | 38 -----
.../src/main/docs/vertx-websocket-starter.adoc | 36 -----
.../camel-vm-starter/src/main/docs/vm-starter.adoc | 38 -----
.../src/main/docs/weather-starter.adoc | 32 ----
.../src/main/docs/web3j-starter.adoc | 67 --------
.../src/main/docs/webhook-starter.adoc | 37 -----
.../src/main/docs/websocket-jsr356-starter.adoc | 33 ----
.../src/main/docs/websocket-starter.adoc | 44 ------
.../src/main/docs/weka-starter.adoc | 31 ----
.../src/main/docs/wordpress-starter.adoc | 41 -----
.../src/main/docs/workday-starter.adoc | 31 ----
.../src/main/docs/xchange-starter.adoc | 31 ----
.../camel-xj-starter/src/main/docs/xj-starter.adoc | 39 -----
.../src/main/docs/xml-jaxp-starter.adoc | 33 ----
.../src/main/docs/xmlsecurity-starter.adoc | 91 -----------
.../src/main/docs/xmpp-starter.adoc | 32 ----
.../src/main/docs/xpath-starter.adoc | 37 -----
.../src/main/docs/xslt-saxon-starter.adoc | 39 -----
.../src/main/docs/xslt-starter.adoc | 36 -----
.../src/main/docs/xstream-starter.adoc | 41 -----
.../src/main/docs/yammer-starter.adoc | 44 ------
.../src/main/docs/zendesk-starter.adoc | 39 -----
.../src/main/docs/zip-deflater-starter.adoc | 31 ----
.../src/main/docs/zipfile-starter.adoc | 33 ----
.../src/main/docs/zipkin-starter.adoc | 39 -----
.../src/main/docs/zookeeper-master-starter.adoc | 37 -----
.../src/main/docs/zookeeper-starter.adoc | 85 ----------
.../spring-boot/partials/activemq-starter.adoc | 129 ---------------
.../modules/spring-boot/partials/ahc-starter.adoc | 38 -----
.../spring-boot/partials/ahc-ws-starter.adoc | 39 -----
.../modules/spring-boot/partials/amqp-starter.adoc | 126 ---------------
.../spring-boot/partials/any23-starter.adoc | 33 ----
.../modules/spring-boot/partials/apns-starter.adoc | 33 ----
.../spring-boot/partials/arangodb-starter.adoc | 41 -----
.../modules/spring-boot/partials/as2-starter.adoc | 33 ----
.../modules/spring-boot/partials/asn1-starter.adoc | 31 ----
.../spring-boot/partials/asterisk-starter.adoc | 32 ----
.../spring-boot/partials/atlasmap-starter.adoc | 32 ----
.../spring-boot/partials/atmos-starter.adoc | 36 -----
.../partials/atmosphere-websocket-starter.adoc | 40 -----
.../modules/spring-boot/partials/atom-starter.adoc | 31 ----
.../spring-boot/partials/atomix-starter.adoc | 149 ------------------
.../spring-boot/partials/avro-rpc-starter.adoc | 39 -----
.../modules/spring-boot/partials/avro-starter.adoc | 30 ----
.../spring-boot/partials/aws-cw-starter.adoc | 44 ------
.../spring-boot/partials/aws-ddb-starter.adoc | 61 -------
.../spring-boot/partials/aws-ec2-starter.adoc | 41 -----
.../spring-boot/partials/aws-ecs-starter.adoc | 41 -----
.../spring-boot/partials/aws-eks-starter.adoc | 41 -----
.../spring-boot/partials/aws-iam-starter.adoc | 41 -----
.../spring-boot/partials/aws-kinesis-starter.adoc | 58 -------
.../spring-boot/partials/aws-kms-starter.adoc | 41 -----
.../spring-boot/partials/aws-lambda-starter.adoc | 41 -----
.../spring-boot/partials/aws-mq-starter.adoc | 41 -----
.../spring-boot/partials/aws-msk-starter.adoc | 41 -----
.../spring-boot/partials/aws-s3-starter.adoc | 68 --------
.../spring-boot/partials/aws-sdb-starter.adoc | 31 ----
.../spring-boot/partials/aws-ses-starter.adoc | 44 ------
.../spring-boot/partials/aws-sns-starter.adoc | 49 ------
.../spring-boot/partials/aws-sqs-starter.adoc | 68 --------
.../spring-boot/partials/aws-swf-starter.adoc | 59 -------
.../partials/aws-translate-starter.adoc | 44 ------
.../spring-boot/partials/aws2-athena-starter.adoc | 58 -------
.../spring-boot/partials/aws2-cw-starter.adoc | 44 ------
.../spring-boot/partials/aws2-ddb-starter.adoc | 61 -------
.../spring-boot/partials/aws2-ec2-starter.adoc | 42 -----
.../spring-boot/partials/aws2-ecs-starter.adoc | 42 -----
.../spring-boot/partials/aws2-eks-starter.adoc | 42 -----
.../partials/aws2-eventbridge-starter.adoc | 43 -----
.../spring-boot/partials/aws2-iam-starter.adoc | 42 -----
.../spring-boot/partials/aws2-kinesis-starter.adoc | 61 -------
.../spring-boot/partials/aws2-kms-starter.adoc | 42 -----
.../spring-boot/partials/aws2-lambda-starter.adoc | 42 -----
.../spring-boot/partials/aws2-mq-starter.adoc | 42 -----
.../spring-boot/partials/aws2-msk-starter.adoc | 42 -----
.../spring-boot/partials/aws2-s3-starter.adoc | 71 ---------
.../spring-boot/partials/aws2-ses-starter.adoc | 44 ------
.../spring-boot/partials/aws2-sns-starter.adoc | 51 ------
.../spring-boot/partials/aws2-sqs-starter.adoc | 69 --------
.../spring-boot/partials/aws2-sts-starter.adoc | 42 -----
.../partials/aws2-translate-starter.adoc | 45 ------
.../partials/azure-eventhubs-starter.adoc | 50 ------
.../spring-boot/partials/azure-starter.adoc | 65 --------
.../partials/azure-storage-blob-starter.adoc | 57 -------
.../partials/azure-storage-queue-starter.adoc | 45 ------
.../spring-boot/partials/barcode-starter.adoc | 33 ----
.../spring-boot/partials/base64-starter.adoc | 32 ----
.../modules/spring-boot/partials/bean-starter.adoc | 41 -----
.../partials/bean-validator-starter.adoc | 37 -----
.../spring-boot/partials/beanio-starter.adoc | 37 -----
.../spring-boot/partials/beanstalk-starter.adoc | 33 ----
.../spring-boot/partials/bindy-starter.adoc | 46 ------
.../spring-boot/partials/bonita-starter.adoc | 31 ----
.../modules/spring-boot/partials/box-starter.adoc | 48 ------
.../spring-boot/partials/braintree-starter.adoc | 32 ----
.../spring-boot/partials/browse-starter.adoc | 32 ----
.../spring-boot/partials/caffeine-starter.adoc | 64 --------
.../spring-boot/partials/cassandraql-starter.adoc | 32 ----
.../modules/spring-boot/partials/cbor-starter.adoc | 39 -----
.../spring-boot/partials/chatscript-starter.adoc | 31 ----
.../spring-boot/partials/chunk-starter.adoc | 33 ----
.../spring-boot/partials/cm-sms-starter.adoc | 31 ----
.../modules/spring-boot/partials/cmis-starter.adoc | 33 ----
.../modules/spring-boot/partials/coap-starter.adoc | 32 ----
.../spring-boot/partials/cometd-starter.adoc | 39 -----
.../spring-boot/partials/consul-starter.adoc | 118 --------------
.../spring-boot/partials/controlbus-starter.adoc | 31 ----
.../spring-boot/partials/corda-starter.adoc | 43 -----
.../modules/spring-boot/partials/core-starter.adoc | 175 ---------------------
.../spring-boot/partials/couchbase-starter.adoc | 32 ----
.../spring-boot/partials/couchdb-starter.adoc | 32 ----
.../modules/spring-boot/partials/cron-starter.adoc | 32 ----
.../spring-boot/partials/crypto-cms-starter.adoc | 33 ----
.../spring-boot/partials/crypto-starter.adoc | 75 ---------
.../modules/spring-boot/partials/csv-starter.adoc | 57 -------
.../modules/spring-boot/partials/cxf-starter.adoc | 41 -----
.../spring-boot/partials/dataformat-starter.adoc | 31 ----
.../spring-boot/partials/dataset-starter.adoc | 35 -----
.../spring-boot/partials/datasonnet-starter.adoc | 34 ----
.../partials/debezium-mongodb-starter.adoc | 83 ----------
.../partials/debezium-mysql-starter.adoc | 108 -------------
.../partials/debezium-postgres-starter.adoc | 113 -------------
.../partials/debezium-sqlserver-starter.adoc | 93 -----------
.../spring-boot/partials/digitalocean-starter.adoc | 31 ----
.../spring-boot/partials/direct-starter.adoc | 34 ----
.../spring-boot/partials/directvm-starter.adoc | 36 -----
.../spring-boot/partials/disruptor-starter.adoc | 48 ------
.../modules/spring-boot/partials/djl-starter.adoc | 31 ----
.../modules/spring-boot/partials/dns-starter.adoc | 31 ----
.../spring-boot/partials/docker-starter.adoc | 50 ------
.../spring-boot/partials/dozer-starter.adoc | 31 ----
.../spring-boot/partials/drill-starter.adoc | 31 ----
.../spring-boot/partials/dropbox-starter.adoc | 32 ----
.../spring-boot/partials/ehcache-starter.adoc | 49 ------
.../partials/elasticsearch-rest-starter.adoc | 42 -----
.../spring-boot/partials/elsql-starter.adoc | 35 -----
.../modules/spring-boot/partials/etcd-starter.adoc | 71 ---------
.../modules/spring-boot/partials/exec-starter.adoc | 31 ----
.../spring-boot/partials/facebook-starter.adoc | 60 -------
.../spring-boot/partials/fastjson-starter.adoc | 31 ----
.../modules/spring-boot/partials/fhir-starter.adoc | 84 ----------
.../modules/spring-boot/partials/file-starter.adoc | 39 -----
.../spring-boot/partials/file-watch-starter.adoc | 36 -----
.../spring-boot/partials/flatpack-starter.adoc | 41 -----
.../spring-boot/partials/flink-starter.adoc | 34 ----
.../modules/spring-boot/partials/fop-starter.adoc | 31 ----
.../spring-boot/partials/freemarker-starter.adoc | 34 ----
.../modules/spring-boot/partials/ftp-starter.adoc | 41 -----
.../spring-boot/partials/ganglia-starter.adoc | 44 ------
.../spring-boot/partials/geocoder-starter.adoc | 32 ----
.../modules/spring-boot/partials/git-starter.adoc | 32 ----
.../spring-boot/partials/github-starter.adoc | 33 ----
.../partials/google-bigquery-starter.adoc | 39 -----
.../partials/google-calendar-starter.adoc | 59 -------
.../spring-boot/partials/google-drive-starter.adoc | 40 -----
.../spring-boot/partials/google-mail-starter.adoc | 53 -------
.../partials/google-pubsub-starter.adoc | 36 -----
.../partials/google-sheets-starter.adoc | 58 -------
.../modules/spring-boot/partials/gora-starter.adoc | 32 ----
.../spring-boot/partials/grape-starter.adoc | 32 ----
.../spring-boot/partials/graphql-starter.adoc | 31 ----
.../modules/spring-boot/partials/grok-starter.adoc | 33 ----
.../spring-boot/partials/groovy-starter.adoc | 31 ----
.../modules/spring-boot/partials/grpc-starter.adoc | 32 ----
.../modules/spring-boot/partials/gson-starter.adoc | 32 ----
.../partials/guava-eventbus-starter.adoc | 34 ----
.../spring-boot/partials/hazelcast-starter.adoc | 113 -------------
.../spring-boot/partials/hbase-starter.adoc | 34 ----
.../modules/spring-boot/partials/hdfs-starter.adoc | 34 ----
.../modules/spring-boot/partials/hl7-starter.adoc | 32 ----
.../modules/spring-boot/partials/http-starter.adoc | 55 -------
.../spring-boot/partials/hystrix-starter.adoc | 32 ----
.../modules/spring-boot/partials/ical-starter.adoc | 30 ----
.../spring-boot/partials/iec60870-starter.adoc | 38 -----
.../spring-boot/partials/ignite-starter.adoc | 72 ---------
.../spring-boot/partials/infinispan-starter.adoc | 62 --------
.../spring-boot/partials/influxdb-starter.adoc | 32 ----
.../modules/spring-boot/partials/iota-starter.adoc | 31 ----
.../modules/spring-boot/partials/ipfs-starter.adoc | 33 ----
.../modules/spring-boot/partials/irc-starter.adoc | 33 ----
.../spring-boot/partials/ironmq-starter.adoc | 32 ----
.../spring-boot/partials/jackson-starter.adoc | 46 ------
.../spring-boot/partials/jacksonxml-starter.adoc | 44 ------
.../spring-boot/partials/jasypt-starter.adoc | 34 ----
.../modules/spring-boot/partials/jaxb-starter.adoc | 48 ------
.../modules/spring-boot/partials/jbpm-starter.adoc | 32 ----
.../spring-boot/partials/jcache-starter.adoc | 37 -----
.../spring-boot/partials/jclouds-starter.adoc | 34 ----
.../modules/spring-boot/partials/jcr-starter.adoc | 32 ----
.../modules/spring-boot/partials/jdbc-starter.adoc | 31 ----
.../spring-boot/partials/jetty-starter.adoc | 61 -------
.../spring-boot/partials/jgroups-raft-starter.adoc | 41 -----
.../spring-boot/partials/jgroups-starter.adoc | 39 -----
.../modules/spring-boot/partials/jing-starter.adoc | 31 ----
.../modules/spring-boot/partials/jira-starter.adoc | 41 -----
.../modules/spring-boot/partials/jms-starter.adoc | 125 ---------------
.../modules/spring-boot/partials/jmx-starter.adoc | 31 ----
.../spring-boot/partials/johnzon-starter.adoc | 32 ----
.../modules/spring-boot/partials/jolt-starter.adoc | 33 ----
.../modules/spring-boot/partials/jooq-starter.adoc | 37 -----
.../modules/spring-boot/partials/joor-starter.adoc | 34 ----
.../modules/spring-boot/partials/jpa-starter.adoc | 36 -----
.../modules/spring-boot/partials/jsch-starter.adoc | 32 ----
.../modules/spring-boot/partials/jslt-starter.adoc | 34 ----
.../partials/json-validator-starter.adoc | 31 ----
.../spring-boot/partials/jsonapi-starter.adoc | 31 ----
.../spring-boot/partials/jsonata-starter.adoc | 31 ----
.../spring-boot/partials/jsonb-starter.adoc | 34 ----
.../spring-boot/partials/jsonpath-starter.adoc | 36 -----
.../spring-boot/partials/jt400-starter.adoc | 33 ----
.../spring-boot/partials/kafka-starter.adoc | 126 ---------------
.../spring-boot/partials/kubernetes-starter.adoc | 102 ------------
.../modules/spring-boot/partials/kudu-starter.adoc | 31 ----
.../spring-boot/partials/language-starter.adoc | 31 ----
.../modules/spring-boot/partials/ldap-starter.adoc | 31 ----
.../modules/spring-boot/partials/ldif-starter.adoc | 31 ----
.../modules/spring-boot/partials/log-starter.adoc | 32 ----
.../modules/spring-boot/partials/lra-starter.adoc | 34 ----
.../spring-boot/partials/lucene-starter.adoc | 36 -----
.../spring-boot/partials/lumberjack-starter.adoc | 33 ----
.../modules/spring-boot/partials/lzf-starter.adoc | 30 ----
.../modules/spring-boot/partials/mail-starter.adoc | 77 ---------
.../spring-boot/partials/master-starter.adoc | 33 ----
.../spring-boot/partials/metrics-starter.adoc | 32 ----
.../spring-boot/partials/micrometer-starter.adoc | 32 ----
.../modules/spring-boot/partials/milo-starter.adoc | 74 ---------
.../modules/spring-boot/partials/mina-starter.adoc | 57 -------
.../spring-boot/partials/minio-starter.adoc | 76 ---------
.../modules/spring-boot/partials/mllp-starter.adoc | 35 -----
.../modules/spring-boot/partials/mock-starter.adoc | 31 ----
.../partials/mongodb-gridfs-starter.adoc | 32 ----
.../spring-boot/partials/mongodb-starter.adoc | 33 ----
.../modules/spring-boot/partials/msv-starter.adoc | 33 ----
.../spring-boot/partials/mustache-starter.adoc | 34 ----
.../modules/spring-boot/partials/mvel-starter.adoc | 35 -----
.../spring-boot/partials/mybatis-starter.adoc | 39 -----
.../spring-boot/partials/nagios-starter.adoc | 36 -----
.../modules/spring-boot/partials/nats-starter.adoc | 35 -----
.../spring-boot/partials/netty-http-starter.adoc | 91 -----------
.../spring-boot/partials/netty-starter.adoc | 102 ------------
.../spring-boot/partials/nitrite-starter.adoc | 32 ----
.../modules/spring-boot/partials/nsq-starter.adoc | 34 ----
.../spring-boot/partials/oaipmh-starter.adoc | 32 ----
.../modules/spring-boot/partials/ognl-starter.adoc | 31 ----
.../spring-boot/partials/olingo2-starter.adoc | 47 ------
.../spring-boot/partials/olingo4-starter.adoc | 45 ------
.../spring-boot/partials/openstack-starter.adoc | 46 ------
.../partials/opentelemetry-starter.adoc | 32 ----
.../spring-boot/partials/opentracing-starter.adoc | 31 ----
.../spring-boot/partials/optaplanner-starter.adoc | 32 ----
.../modules/spring-boot/partials/paho-starter.adoc | 60 -------
.../modules/spring-boot/partials/pdf-starter.adoc | 31 ----
.../partials/pg-replication-slot-starter.adoc | 31 ----
.../spring-boot/partials/pgevent-starter.adoc | 32 ----
.../partials/platform-http-starter.adoc | 32 ----
.../spring-boot/partials/printer-starter.adoc | 31 ----
.../spring-boot/partials/protobuf-starter.adoc | 32 ----
.../spring-boot/partials/pubnub-starter.adoc | 32 ----
.../spring-boot/partials/pulsar-starter.adoc | 65 --------
.../spring-boot/partials/quartz-starter.adoc | 42 -----
.../spring-boot/partials/quickfix-starter.adoc | 36 -----
.../spring-boot/partials/rabbitmq-starter.adoc | 85 ----------
.../partials/reactive-streams-starter.adoc | 38 -----
.../modules/spring-boot/partials/ref-starter.adoc | 32 ----
.../spring-boot/partials/rest-openapi-starter.adoc | 39 -----
.../modules/spring-boot/partials/rest-starter.adoc | 40 -----
.../spring-boot/partials/rest-swagger-starter.adoc | 39 -----
.../spring-boot/partials/resteasy-starter.adoc | 35 -----
.../partials/robotframework-starter.adoc | 80 ----------
.../modules/spring-boot/partials/rss-starter.adoc | 32 ----
.../modules/spring-boot/partials/saga-starter.adoc | 31 ----
.../spring-boot/partials/salesforce-starter.adoc | 105 -------------
.../partials/sap-netweaver-starter.adoc | 31 ----
.../spring-boot/partials/saxon-starter.adoc | 39 -----
.../spring-boot/partials/scheduler-starter.adoc | 32 ----
.../spring-boot/partials/schematron-starter.adoc | 31 ----
.../modules/spring-boot/partials/seda-starter.adoc | 38 -----
.../spring-boot/partials/service-starter.adoc | 33 ----
.../spring-boot/partials/servicenow-starter.adoc | 77 ---------
.../spring-boot/partials/servlet-starter.adoc | 42 -----
.../modules/spring-boot/partials/sip-starter.adoc | 32 ----
.../modules/spring-boot/partials/sjms-starter.adoc | 55 -------
.../spring-boot/partials/sjms2-starter.adoc | 48 ------
.../spring-boot/partials/slack-starter.adoc | 33 ----
.../modules/spring-boot/partials/smpp-starter.adoc | 67 --------
.../spring-boot/partials/snakeyaml-starter.adoc | 39 -----
.../modules/spring-boot/partials/snmp-starter.adoc | 32 ----
.../modules/spring-boot/partials/soap-starter.adoc | 35 -----
.../modules/spring-boot/partials/solr-starter.adoc | 31 ----
.../spring-boot/partials/soroush-starter.adoc | 33 ----
.../spring-boot/partials/spark-starter.adoc | 33 ----
.../spring-boot/partials/splunk-starter.adoc | 33 ----
.../spring-boot/partials/spring-batch-starter.adoc | 33 ----
.../partials/spring-integration-starter.adoc | 32 ----
.../spring-boot/partials/spring-ldap-starter.adoc | 31 ----
.../spring-boot/partials/spring-redis-starter.adoc | 32 ----
.../spring-boot/partials/spring-starter.adoc | 34 ----
.../spring-boot/partials/spring-ws-starter.adoc | 33 ----
.../modules/spring-boot/partials/sql-starter.adoc | 36 -----
.../modules/spring-boot/partials/ssh-starter.adoc | 46 ------
.../modules/spring-boot/partials/stax-starter.adoc | 31 ----
.../spring-boot/partials/stomp-starter.adoc | 42 -----
.../spring-boot/partials/stream-starter.adoc | 32 ----
.../partials/stringtemplate-starter.adoc | 33 ----
.../modules/spring-boot/partials/stub-starter.adoc | 38 -----
.../spring-boot/partials/syslog-starter.adoc | 29 ----
.../spring-boot/partials/tagsoup-starter.adoc | 31 ----
.../spring-boot/partials/tarfile-starter.adoc | 33 ----
.../spring-boot/partials/telegram-starter.adoc | 36 -----
.../spring-boot/partials/thrift-starter.adoc | 37 -----
.../modules/spring-boot/partials/tika-starter.adoc | 31 ----
.../spring-boot/partials/timer-starter.adoc | 31 ----
.../spring-boot/partials/twilio-starter.adoc | 37 -----
.../spring-boot/partials/twitter-starter.adoc | 64 --------
.../partials/undertow-spring-security-starter.adoc | 33 ----
.../spring-boot/partials/undertow-starter.adoc | 40 -----
.../partials/univocity-parsers-starter.adoc | 78 ---------
.../spring-boot/partials/validator-starter.adoc | 32 ----
.../spring-boot/partials/velocity-starter.adoc | 34 ----
.../spring-boot/partials/vertx-http-starter.adoc | 46 ------
.../spring-boot/partials/vertx-kafka-starter.adoc | 127 ---------------
.../spring-boot/partials/vertx-starter.adoc | 38 -----
.../partials/vertx-websocket-starter.adoc | 36 -----
.../modules/spring-boot/partials/vm-starter.adoc | 38 -----
.../spring-boot/partials/weather-starter.adoc | 32 ----
.../spring-boot/partials/web3j-starter.adoc | 67 --------
.../spring-boot/partials/webhook-starter.adoc | 37 -----
.../partials/websocket-jsr356-starter.adoc | 33 ----
.../spring-boot/partials/websocket-starter.adoc | 44 ------
.../modules/spring-boot/partials/weka-starter.adoc | 31 ----
.../spring-boot/partials/wordpress-starter.adoc | 41 -----
.../spring-boot/partials/workday-starter.adoc | 31 ----
.../spring-boot/partials/xchange-starter.adoc | 31 ----
.../modules/spring-boot/partials/xj-starter.adoc | 39 -----
.../spring-boot/partials/xml-jaxp-starter.adoc | 33 ----
.../spring-boot/partials/xmlsecurity-starter.adoc | 91 -----------
.../modules/spring-boot/partials/xmpp-starter.adoc | 32 ----
.../spring-boot/partials/xpath-starter.adoc | 37 -----
.../spring-boot/partials/xslt-saxon-starter.adoc | 39 -----
.../modules/spring-boot/partials/xslt-starter.adoc | 36 -----
.../spring-boot/partials/xstream-starter.adoc | 41 -----
.../spring-boot/partials/yammer-starter.adoc | 44 ------
.../spring-boot/partials/zendesk-starter.adoc | 39 -----
.../spring-boot/partials/zip-deflater-starter.adoc | 31 ----
.../spring-boot/partials/zipfile-starter.adoc | 33 ----
.../spring-boot/partials/zipkin-starter.adoc | 39 -----
.../partials/zookeeper-master-starter.adoc | 37 -----
.../spring-boot/partials/zookeeper-starter.adoc | 85 ----------
642 files changed, 28296 deletions(-)
diff --git a/components-starter/camel-activemq-starter/src/main/docs/activemq-starter.adoc b/components-starter/camel-activemq-starter/src/main/docs/activemq-starter.adoc
deleted file mode 100644
index dc59fb1..0000000
--- a/components-starter/camel-activemq-starter/src/main/docs/activemq-starter.adoc
+++ /dev/null
@@ -1,129 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for activemq
-
-== Spring Boot Auto-Configuration
-
-When using activemq with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-activemq-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 101 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.activemq.accept-messages-while-stopping* | Specifies whether the consumer accept messages while it is stopping. You may consider enabling this option, if you start and stop JMS routes at runtime, while there are still messages enqueued on the queue. If this option is false, and you stop the JMS route, then messages may be rejected, and the JMS broker would have to attempt redeliveries, which yet again may be rejected, and eventually the message may be moved at a dead l [...]
-| *camel.component.activemq.acknowledgement-mode-name* | The JMS acknowledgement name, which is one of: SESSION_TRANSACTED, CLIENT_ACKNOWLEDGE, AUTO_ACKNOWLEDGE, DUPS_OK_ACKNOWLEDGE | AUTO_ACKNOWLEDGE | String
-| *camel.component.activemq.allow-additional-headers* | This option is used to allow additional headers which may have values that are invalid according to JMS specification. For example some message systems such as WMQ do this with header names using prefix JMS_IBM_MQMD_ containing values with byte array or other invalid types. You can specify multiple header names separated by comma, and use as suffix for wildcard matching. | | String
-| *camel.component.activemq.allow-auto-wired-connection-factory* | Whether to auto-discover ConnectionFactory from the registry, if no connection factory has been configured. If only one instance of ConnectionFactory is found then it will be used. This is enabled by default. | true | Boolean
-| *camel.component.activemq.allow-auto-wired-destination-resolver* | Whether to auto-discover DestinationResolver from the registry, if no destination resolver has been configured. If only one instance of DestinationResolver is found then it will be used. This is enabled by default. | true | Boolean
-| *camel.component.activemq.allow-null-body* | Whether to allow sending messages with no body. If this option is false and the message body is null, then an JMSException is thrown. | true | Boolean
-| *camel.component.activemq.allow-reply-manager-quick-stop* | Whether the DefaultMessageListenerContainer used in the reply managers for request-reply messaging allow the DefaultMessageListenerContainer.runningAllowed flag to quick stop in case JmsConfiguration#isAcceptMessagesWhileStopping is enabled, and org.apache.camel.CamelContext is currently being stopped. This quick stop ability is enabled by default in the regular JMS consumers but to enable for reply managers you must enable th [...]
-| *camel.component.activemq.allow-serialized-headers* | Controls whether or not to include serialized headers. Applies only when transferExchange is true. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level. | false | Boolean
-| *camel.component.activemq.always-copy-message* | If true, Camel will always make a JMS message copy of the message when it is passed to the producer for sending. Copying the message is needed in some situations, such as when a replyToDestinationSelectorName is set (incidentally, Camel will set the alwaysCopyMessage option to true, if a replyToDestinationSelectorName is set) | false | Boolean
-| *camel.component.activemq.artemis-streaming-enabled* | Whether optimizing for Apache Artemis streaming mode. | true | Boolean
-| *camel.component.activemq.async-consumer* | Whether the JmsConsumer processes the Exchange asynchronously. If enabled then the JmsConsumer may pickup the next message from the JMS queue, while the previous message is being processed asynchronously (by the Asynchronous Routing Engine). This means that messages may be processed not 100% strictly in order. If disabled (as default) then the Exchange is fully processed before the JmsConsumer will pickup the next message from the JMS queue. [...]
-| *camel.component.activemq.async-start-listener* | Whether to startup the JmsConsumer message listener asynchronously, when starting a route. For example if a JmsConsumer cannot get a connection to a remote JMS broker, then it may block while retrying and/or failover. This will cause Camel to block while starting routes. By setting this option to true, you will let routes startup, while the JmsConsumer connects to the JMS broker using a dedicated thread in asynchronous mode. If this opt [...]
-| *camel.component.activemq.async-stop-listener* | Whether to stop the JmsConsumer message listener asynchronously, when stopping a route. | false | Boolean
-| *camel.component.activemq.auto-startup* | Specifies whether the consumer container should auto-startup. | true | Boolean
-| *camel.component.activemq.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.activemq.broker-url* | Sets the broker URL to use to connect to ActiveMQ. If none configured then localhost:61616 is used by default (however can be overridden by configuration from environment variables) | | String
-| *camel.component.activemq.cache-level* | Sets the cache level by ID for the underlying JMS resources. See cacheLevelName option for more details. | | Integer
-| *camel.component.activemq.cache-level-name* | Sets the cache level by name for the underlying JMS resources. Possible values are: CACHE_AUTO, CACHE_CONNECTION, CACHE_CONSUMER, CACHE_NONE, and CACHE_SESSION. The default setting is CACHE_AUTO. See the Spring documentation and Transactions Cache Levels for more information. | CACHE_AUTO | String
-| *camel.component.activemq.client-id* | Sets the JMS client ID to use. Note that this value, if specified, must be unique and can only be used by a single JMS connection instance. It is typically only required for durable topic subscriptions. If using Apache ActiveMQ you may prefer to use Virtual Topics instead. | | String
-| *camel.component.activemq.concurrent-consumers* | Specifies the default number of concurrent consumers when consuming from JMS (not for request/reply over JMS). See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. When doing request/reply over JMS then the option replyToConcurrentConsumers is used to control number of concurrent consumers on the reply message listener. | 1 | Integer
-| *camel.component.activemq.configuration* | To use a shared JMS configuration. The option is a org.apache.camel.component.jms.JmsConfiguration type. | | JmsConfiguration
-| *camel.component.activemq.connection-factory* | The connection factory to be use. A connection factory must be configured either on the component or endpoint. The option is a javax.jms.ConnectionFactory type. | | ConnectionFactory
-| *camel.component.activemq.consumer-type* | The consumer type to use, which can be one of: Simple, Default, or Custom. The consumer type determines which Spring JMS listener to use. Default will use org.springframework.jms.listener.DefaultMessageListenerContainer, Simple will use org.springframework.jms.listener.SimpleMessageListenerContainer. When Custom is specified, the MessageListenerContainerFactory defined by the messageListenerContainerFactory option will determine what org.sprin [...]
-| *camel.component.activemq.correlation-property* | When using InOut exchange pattern use this JMS property instead of JMSCorrelationID JMS property to correlate messages. If set messages will be correlated solely on the value of this property JMSCorrelationID property will be ignored and not set by Camel. | | String
-| *camel.component.activemq.default-task-executor-type* | Specifies what default TaskExecutor type to use in the DefaultMessageListenerContainer, for both consumer endpoints and the ReplyTo consumer of producer endpoints. Possible values: SimpleAsync (uses Spring's SimpleAsyncTaskExecutor) or ThreadPool (uses Spring's ThreadPoolTaskExecutor with optimal values - cached threadpool-like). If not set, it defaults to the previous behaviour, which uses a cached thread pool for consumer endpoi [...]
-| *camel.component.activemq.delivery-delay* | Sets delivery delay to use for send calls for JMS. This option requires JMS 2.0 compliant broker. | -1 | Long
-| *camel.component.activemq.delivery-mode* | Specifies the delivery mode to be used. Possible values are those defined by javax.jms.DeliveryMode. NON_PERSISTENT = 1 and PERSISTENT = 2. | | Integer
-| *camel.component.activemq.delivery-persistent* | Specifies whether persistent delivery is used by default. | true | Boolean
-| *camel.component.activemq.destination-resolver* | A pluggable org.springframework.jms.support.destination.DestinationResolver that allows you to use your own resolver (for example, to lookup the real destination in a JNDI registry). The option is a org.springframework.jms.support.destination.DestinationResolver type. | | DestinationResolver
-| *camel.component.activemq.disable-reply-to* | Specifies whether Camel ignores the JMSReplyTo header in messages. If true, Camel does not send a reply back to the destination specified in the JMSReplyTo header. You can use this option if you want Camel to consume from a route and you do not want Camel to automatically send back a reply message because another component in your code handles the reply message. You can also use this option if you want to use Camel as a proxy between differ [...]
-| *camel.component.activemq.disable-time-to-live* | Use this option to force disabling time to live. For example when you do request/reply over JMS, then Camel will by default use the requestTimeout value as time to live on the message being sent. The problem is that the sender and receiver systems have to have their clocks synchronized, so they are in sync. This is not always so easy to archive. So you can use disableTimeToLive=true to not set a time to live value on the sent message. T [...]
-| *camel.component.activemq.durable-subscription-name* | The durable subscriber name for specifying durable topic subscriptions. The clientId option must be configured as well. | | String
-| *camel.component.activemq.eager-loading-of-properties* | Enables eager loading of JMS properties and payload as soon as a message is loaded which generally is inefficient as the JMS properties may not be required but sometimes can catch early any issues with the underlying JMS provider and the use of JMS properties. See also the option eagerPoisonBody. | false | Boolean
-| *camel.component.activemq.eager-poison-body* | If eagerLoadingOfProperties is enabled and the JMS message payload (JMS body or JMS properties) is poison (cannot be read/mapped), then set this text as the message body instead so the message can be processed (the cause of the poison are already stored as exception on the Exchange). This can be turned off by setting eagerPoisonBody=false. See also the option eagerLoadingOfProperties. | Poison JMS message due to ${exception.message} | String
-| *camel.component.activemq.enabled* | Whether to enable auto configuration of the activemq component. This is enabled by default. | | Boolean
-| *camel.component.activemq.error-handler* | Specifies a org.springframework.util.ErrorHandler to be invoked in case of any uncaught exceptions thrown while processing a Message. By default these exceptions will be logged at the WARN level, if no errorHandler has been configured. You can configure logging level and whether stack traces should be logged using errorHandlerLoggingLevel and errorHandlerLogStackTrace options. This makes it much easier to configure, than having to code a custo [...]
-| *camel.component.activemq.error-handler-log-stack-trace* | Allows to control whether stacktraces should be logged or not, by the default errorHandler. | true | Boolean
-| *camel.component.activemq.error-handler-logging-level* | Allows to configure the default errorHandler logging level for logging uncaught exceptions. | | LoggingLevel
-| *camel.component.activemq.exception-listener* | Specifies the JMS Exception Listener that is to be notified of any underlying JMS exceptions. The option is a javax.jms.ExceptionListener type. | | ExceptionListener
-| *camel.component.activemq.explicit-qos-enabled* | Set if the deliveryMode, priority or timeToLive qualities of service should be used when sending messages. This option is based on Spring's JmsTemplate. The deliveryMode, priority and timeToLive options are applied to the current endpoint. This contrasts with the preserveMessageQos option, which operates at message granularity, reading QoS properties exclusively from the Camel In message headers. | false | Boolean
-| *camel.component.activemq.expose-listener-session* | Specifies whether the listener session should be exposed when consuming messages. | false | Boolean
-| *camel.component.activemq.force-send-original-message* | When using mapJmsMessage=false Camel will create a new JMS message to send to a new JMS destination if you touch the headers (get or set) during the route. Set this option to true to force Camel to send the original JMS message that was received. | false | Boolean
-| *camel.component.activemq.format-date-headers-to-iso8601* | Sets whether JMS date properties should be formatted according to the ISO 8601 standard. | false | Boolean
-| *camel.component.activemq.header-filter-strategy* | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. The option is a org.apache.camel.spi.HeaderFilterStrategy type. | | HeaderFilterStrategy
-| *camel.component.activemq.idle-consumer-limit* | Specify the limit for the number of consumers that are allowed to be idle at any given time. | 1 | Integer
-| *camel.component.activemq.idle-task-execution-limit* | Specifies the limit for idle executions of a receive task, not having received any message within its execution. If this limit is reached, the task will shut down and leave receiving to other executing tasks (in the case of dynamic scheduling; see the maxConcurrentConsumers setting). There is additional doc available from Spring. | 1 | Integer
-| *camel.component.activemq.include-all-jmsx-properties* | Whether to include all JMSXxxx properties when mapping from JMS to Camel Message. Setting this to true will include properties such as JMSXAppID, and JMSXUserID etc. Note: If you are using a custom headerFilterStrategy then this option does not apply. | false | Boolean
-| *camel.component.activemq.include-sent-jms-message-id* | Only applicable when sending to JMS destination using InOnly (eg fire and forget). Enabling this option will enrich the Camel Exchange with the actual JMSMessageID that was used by the JMS client when the message was sent to the JMS destination. | false | Boolean
-| *camel.component.activemq.jms-key-format-strategy* | Pluggable strategy for encoding and decoding JMS keys so they can be compliant with the JMS specification. Camel provides two implementations out of the box: default and passthrough. The default strategy will safely marshal dots and hyphens (. and -). The passthrough strategy leaves the key as is. Can be used for JMS brokers which do not care whether JMS header keys contain illegal characters. You can provide your own implementation [...]
-| *camel.component.activemq.jms-message-type* | Allows you to force the use of a specific javax.jms.Message implementation for sending JMS messages. Possible values are: Bytes, Map, Object, Stream, Text. By default, Camel would determine which JMS message type to use from the In body type. This option allows you to specify it. | | JmsMessageType
-| *camel.component.activemq.lazy-create-transaction-manager* | If true, Camel will create a JmsTransactionManager, if there is no transactionManager injected when option transacted=true. | true | Boolean
-| *camel.component.activemq.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed t [...]
-| *camel.component.activemq.map-jms-message* | Specifies whether Camel should auto map the received JMS message to a suited payload type, such as javax.jms.TextMessage to a String etc. | true | Boolean
-| *camel.component.activemq.max-concurrent-consumers* | Specifies the maximum number of concurrent consumers when consuming from JMS (not for request/reply over JMS). See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. When doing request/reply over JMS then the option replyToMaxConcurrentConsumers is used to control number of concurrent consumers on the reply message listener. | | Integer
-| *camel.component.activemq.max-messages-per-task* | The number of messages per task. -1 is unlimited. If you use a range for concurrent consumers (eg min max), then this option can be used to set a value to eg 100 to control how fast the consumers will shrink when less work is required. | -1 | Integer
-| *camel.component.activemq.message-converter* | To use a custom Spring org.springframework.jms.support.converter.MessageConverter so you can be in control how to map to/from a javax.jms.Message. The option is a org.springframework.jms.support.converter.MessageConverter type. | | MessageConverter
-| *camel.component.activemq.message-created-strategy* | To use the given MessageCreatedStrategy which are invoked when Camel creates new instances of javax.jms.Message objects when Camel is sending a JMS message. The option is a org.apache.camel.component.jms.MessageCreatedStrategy type. | | MessageCreatedStrategy
-| *camel.component.activemq.message-id-enabled* | When sending, specifies whether message IDs should be added. This is just an hint to the JMS broker. If the JMS provider accepts this hint, these messages must have the message ID set to null; if the provider ignores the hint, the message ID must be set to its normal unique value. | true | Boolean
-| *camel.component.activemq.message-listener-container-factory* | Registry ID of the MessageListenerContainerFactory used to determine what org.springframework.jms.listener.AbstractMessageListenerContainer to use to consume messages. Setting this will automatically set consumerType to Custom. The option is a org.apache.camel.component.jms.MessageListenerContainerFactory type. | | MessageListenerContainerFactory
-| *camel.component.activemq.message-timestamp-enabled* | Specifies whether timestamps should be enabled by default on sending messages. This is just an hint to the JMS broker. If the JMS provider accepts this hint, these messages must have the timestamp set to zero; if the provider ignores the hint the timestamp must be set to its normal value. | true | Boolean
-| *camel.component.activemq.password* | Password to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory. | | String
-| *camel.component.activemq.preserve-message-qos* | Set to true, if you want to send message using the QoS settings specified on the message, instead of the QoS settings on the JMS endpoint. The following three headers are considered JMSPriority, JMSDeliveryMode, and JMSExpiration. You can provide all or only some of them. If not provided, Camel will fall back to use the values from the endpoint instead. So, when using this option, the headers override the values from the endpoint. The e [...]
-| *camel.component.activemq.priority* | Values greater than 1 specify the message priority when sending (where 0 is the lowest priority and 9 is the highest). The explicitQosEnabled option must also be enabled in order for this option to have any effect. | 4 | Integer
-| *camel.component.activemq.pub-sub-no-local* | Specifies whether to inhibit the delivery of messages published by its own connection. | false | Boolean
-| *camel.component.activemq.queue-browse-strategy* | To use a custom QueueBrowseStrategy when browsing queues. The option is a org.apache.camel.component.jms.QueueBrowseStrategy type. | | QueueBrowseStrategy
-| *camel.component.activemq.receive-timeout* | The timeout for receiving messages (in milliseconds). The option is a long type. | 1000 | Long
-| *camel.component.activemq.recovery-interval* | Specifies the interval between recovery attempts, i.e. when a connection is being refreshed, in milliseconds. The default is 5000 ms, that is, 5 seconds. The option is a long type. | 5000 | Long
-| *camel.component.activemq.reply-to* | Provides an explicit ReplyTo destination (overrides any incoming value of Message.getJMSReplyTo() in consumer). | | String
-| *camel.component.activemq.reply-to-cache-level-name* | Sets the cache level by name for the reply consumer when doing request/reply over JMS. This option only applies when using fixed reply queues (not temporary). Camel will by default use: CACHE_CONSUMER for exclusive or shared w/ replyToSelectorName. And CACHE_SESSION for shared without replyToSelectorName. Some JMS brokers such as IBM WebSphere may require to set the replyToCacheLevelName=CACHE_NONE to work. Note: If using temporary [...]
-| *camel.component.activemq.reply-to-concurrent-consumers* | Specifies the default number of concurrent consumers when doing request/reply over JMS. See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. | 1 | Integer
-| *camel.component.activemq.reply-to-delivery-persistent* | Specifies whether to use persistent delivery by default for replies. | true | Boolean
-| *camel.component.activemq.reply-to-destination-selector-name* | Sets the JMS Selector using the fixed name to be used so you can filter out your own replies from the others when using a shared queue (that is, if you are not using a temporary reply queue). | | String
-| *camel.component.activemq.reply-to-max-concurrent-consumers* | Specifies the maximum number of concurrent consumers when using request/reply over JMS. See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. | | Integer
-| *camel.component.activemq.reply-to-on-timeout-max-concurrent-consumers* | Specifies the maximum number of concurrent consumers for continue routing when timeout occurred when using request/reply over JMS. | 1 | Integer
-| *camel.component.activemq.reply-to-override* | Provides an explicit ReplyTo destination in the JMS message, which overrides the setting of replyTo. It is useful if you want to forward the message to a remote Queue and receive the reply message from the ReplyTo destination. | | String
-| *camel.component.activemq.reply-to-same-destination-allowed* | Whether a JMS consumer is allowed to send a reply message to the same destination that the consumer is using to consume from. This prevents an endless loop by consuming and sending back the same message to itself. | false | Boolean
-| *camel.component.activemq.reply-to-type* | Allows for explicitly specifying which kind of strategy to use for replyTo queues when doing request/reply over JMS. Possible values are: Temporary, Shared, or Exclusive. By default Camel will use temporary queues. However if replyTo has been configured, then Shared is used by default. This option allows you to use exclusive queues instead of shared ones. See Camel JMS documentation for more details, and especially the notes about the implicat [...]
-| *camel.component.activemq.request-timeout* | The timeout for waiting for a reply when using the InOut Exchange Pattern (in milliseconds). The default is 20 seconds. You can include the header CamelJmsRequestTimeout to override this endpoint configured timeout value, and thus have per message individual timeout values. See also the requestTimeoutCheckerInterval option. The option is a long type. | 20000 | Long
-| *camel.component.activemq.request-timeout-checker-interval* | Configures how often Camel should check for timed out Exchanges when doing request/reply over JMS. By default Camel checks once per second. But if you must react faster when a timeout occurs, then you can lower this interval, to check more frequently. The timeout is determined by the option requestTimeout. The option is a long type. | 1000 | Long
-| *camel.component.activemq.selector* | Sets the JMS selector to use | | String
-| *camel.component.activemq.stream-message-type-enabled* | Sets whether StreamMessage type is enabled or not. Message payloads of streaming kind such as files, InputStream, etc will either by sent as BytesMessage or StreamMessage. This option controls which kind will be used. By default BytesMessage is used which enforces the entire message payload to be read into memory. By enabling this option the message payload is read into memory in chunks and each chunk is then written to the Strea [...]
-| *camel.component.activemq.subscription-durable* | Set whether to make the subscription durable. The durable subscription name to be used can be specified through the subscriptionName property. Default is false. Set this to true to register a durable subscription, typically in combination with a subscriptionName value (unless your message listener class name is good enough as subscription name). Only makes sense when listening to a topic (pub-sub domain), therefore this method switches [...]
-| *camel.component.activemq.subscription-name* | Set the name of a subscription to create. To be applied in case of a topic (pub-sub domain) with a shared or durable subscription. The subscription name needs to be unique within this client's JMS client id. Default is the class name of the specified message listener. Note: Only 1 concurrent consumer (which is the default of this message listener container) is allowed for each subscription, except for a shared subscription (which requires [...]
-| *camel.component.activemq.subscription-shared* | Set whether to make the subscription shared. The shared subscription name to be used can be specified through the subscriptionName property. Default is false. Set this to true to register a shared subscription, typically in combination with a subscriptionName value (unless your message listener class name is good enough as subscription name). Note that shared subscriptions may also be durable, so this flag can (and often will) be combine [...]
-| *camel.component.activemq.task-executor* | Allows you to specify a custom task executor for consuming messages. The option is a org.springframework.core.task.TaskExecutor type. | | TaskExecutor
-| *camel.component.activemq.test-connection-on-startup* | Specifies whether to test the connection on startup. This ensures that when Camel starts that all the JMS consumers have a valid connection to the JMS broker. If a connection cannot be granted then Camel throws an exception on startup. This ensures that Camel is not started with failed connections. The JMS producers is tested as well. | false | Boolean
-| *camel.component.activemq.time-to-live* | When sending messages, specifies the time-to-live of the message (in milliseconds). | -1 | Long
-| *camel.component.activemq.transacted* | Specifies whether to use transacted mode | false | Boolean
-| *camel.component.activemq.transacted-in-out* | Specifies whether InOut operations (request reply) default to using transacted mode If this flag is set to true, then Spring JmsTemplate will have sessionTransacted set to true, and the acknowledgeMode as transacted on the JmsTemplate used for InOut operations. Note from Spring JMS: that within a JTA transaction, the parameters passed to createQueue, createTopic methods are not taken into account. Depending on the Java EE transaction conte [...]
-| *camel.component.activemq.transaction-manager* | The Spring transaction manager to use. The option is a org.springframework.transaction.PlatformTransactionManager type. | | PlatformTransactionManager
-| *camel.component.activemq.transaction-name* | The name of the transaction to use. | | String
-| *camel.component.activemq.transaction-timeout* | The timeout value of the transaction (in seconds), if using transacted mode. | -1 | Integer
-| *camel.component.activemq.transfer-exception* | If enabled and you are using Request Reply messaging (InOut) and an Exchange failed on the consumer side, then the caused Exception will be send back in response as a javax.jms.ObjectMessage. If the client is Camel, the returned Exception is rethrown. This allows you to use Camel JMS as a bridge in your routing - for example, using persistent queues to enable robust routing. Notice that if you also have transferExchange enabled, this opti [...]
-| *camel.component.activemq.transfer-exchange* | You can transfer the exchange over the wire instead of just the body and headers. The following fields are transferred: In body, Out body, Fault body, In headers, Out headers, Fault headers, exchange properties, exchange exception. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level. You must enable this option on both the producer and consumer side, so Camel knows the p [...]
-| *camel.component.activemq.trust-all-packages* | Define if all Java packages are trusted or not (for Java object JMS message types). Notice its not recommended practice to send Java serialized objects over network. Setting this to true can expose security risks, so use this with care. | false | Boolean
-| *camel.component.activemq.use-message-id-as-correlation-id* | Specifies whether JMSMessageID should always be used as JMSCorrelationID for InOut messages. | false | Boolean
-| *camel.component.activemq.use-pooled-connection* | Enables or disables whether a PooledConnectionFactory will be used so that when messages are sent to ActiveMQ from outside of a message consuming thread, pooling will be used rather than the default with the Spring JmsTemplate which will create a new connection, session, producer for each message then close them all down again. The default value is true. | true | Boolean
-| *camel.component.activemq.use-single-connection* | Enables or disables whether a Spring SingleConnectionFactory will be used so that when messages are sent to ActiveMQ from outside of a message consuming thread, pooling will be used rather than the default with the Spring JmsTemplate which will create a new connection, session, producer for each message then close them all down again. The default value is false and a pooled connection is used by default. | false | Boolean
-| *camel.component.activemq.username* | Username to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory. | | String
-| *camel.component.activemq.wait-for-provision-correlation-to-be-updated-counter* | Number of times to wait for provisional correlation id to be updated to the actual correlation id when doing request/reply over JMS and when the option useMessageIDAsCorrelationID is enabled. | 50 | Integer
-| *camel.component.activemq.wait-for-provision-correlation-to-be-updated-thread-sleeping-time* | Interval in millis to sleep each time while waiting for provisional correlation id to be updated. The option is a long type. | 100 | Long
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-ahc-starter/src/main/docs/ahc-starter.adoc b/components-starter/camel-ahc-starter/src/main/docs/ahc-starter.adoc
deleted file mode 100644
index b56cdd7..0000000
--- a/components-starter/camel-ahc-starter/src/main/docs/ahc-starter.adoc
+++ /dev/null
@@ -1,38 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for ahc
-
-== Spring Boot Auto-Configuration
-
-When using ahc with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-ahc-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 10 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.ahc.allow-java-serialized-object* | Whether to allow java serialization when a request uses context-type=application/x-java-serialized-object This is by default turned off. If you enable this then be aware that Java will deserialize the incoming data from the request to Java and that can be a potential security risk. | false | Boolean
-| *camel.component.ahc.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.ahc.binding* | To use a custom AhcBinding which allows to control how to bind between AHC and Camel. The option is a org.apache.camel.component.ahc.AhcBinding type. | | AhcBinding
-| *camel.component.ahc.client* | To use a custom AsyncHttpClient. The option is a org.asynchttpclient.AsyncHttpClient type. | | AsyncHttpClient
-| *camel.component.ahc.client-config* | To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance. The option is a org.asynchttpclient.AsyncHttpClientConfig type. | | AsyncHttpClientConfig
-| *camel.component.ahc.enabled* | Whether to enable auto configuration of the ahc component. This is enabled by default. | | Boolean
-| *camel.component.ahc.header-filter-strategy* | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. The option is a org.apache.camel.spi.HeaderFilterStrategy type. | | HeaderFilterStrategy
-| *camel.component.ahc.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then c [...]
-| *camel.component.ahc.ssl-context-parameters* | Reference to a org.apache.camel.support.jsse.SSLContextParameters in the Registry. Note that configuring this option will override any SSL/TLS configuration options provided through the clientConfig option at the endpoint or component level. The option is a org.apache.camel.support.jsse.SSLContextParameters type. | | SSLContextParameters
-| *camel.component.ahc.use-global-ssl-context-parameters* | Enable usage of global SSL context parameters. | false | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-ahc-ws-starter/src/main/docs/ahc-ws-starter.adoc b/components-starter/camel-ahc-ws-starter/src/main/docs/ahc-ws-starter.adoc
deleted file mode 100644
index 70bd266..0000000
--- a/components-starter/camel-ahc-ws-starter/src/main/docs/ahc-ws-starter.adoc
+++ /dev/null
@@ -1,39 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for ahc-ws
-
-== Spring Boot Auto-Configuration
-
-When using ahc-ws with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-ahc-ws-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 11 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.ahc-ws.allow-java-serialized-object* | Whether to allow java serialization when a request uses context-type=application/x-java-serialized-object This is by default turned off. If you enable this then be aware that Java will deserialize the incoming data from the request to Java and that can be a potential security risk. | false | Boolean
-| *camel.component.ahc-ws.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.ahc-ws.binding* | To use a custom AhcBinding which allows to control how to bind between AHC and Camel. The option is a org.apache.camel.component.ahc.AhcBinding type. | | AhcBinding
-| *camel.component.ahc-ws.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.ahc-ws.client* | To use a custom AsyncHttpClient. The option is a org.asynchttpclient.AsyncHttpClient type. | | AsyncHttpClient
-| *camel.component.ahc-ws.client-config* | To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance. The option is a org.asynchttpclient.AsyncHttpClientConfig type. | | AsyncHttpClientConfig
-| *camel.component.ahc-ws.enabled* | Whether to enable auto configuration of the ahc-ws component. This is enabled by default. | | Boolean
-| *camel.component.ahc-ws.header-filter-strategy* | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. The option is a org.apache.camel.spi.HeaderFilterStrategy type. | | HeaderFilterStrategy
-| *camel.component.ahc-ws.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed the [...]
-| *camel.component.ahc-ws.ssl-context-parameters* | Reference to a org.apache.camel.support.jsse.SSLContextParameters in the Registry. Note that configuring this option will override any SSL/TLS configuration options provided through the clientConfig option at the endpoint or component level. The option is a org.apache.camel.support.jsse.SSLContextParameters type. | | SSLContextParameters
-| *camel.component.ahc-ws.use-global-ssl-context-parameters* | Enable usage of global SSL context parameters. | false | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-amqp-starter/src/main/docs/amqp-starter.adoc b/components-starter/camel-amqp-starter/src/main/docs/amqp-starter.adoc
deleted file mode 100644
index ed49784..0000000
--- a/components-starter/camel-amqp-starter/src/main/docs/amqp-starter.adoc
+++ /dev/null
@@ -1,126 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for amqp
-
-== Spring Boot Auto-Configuration
-
-When using amqp with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-amqp-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 98 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.amqp.accept-messages-while-stopping* | Specifies whether the consumer accept messages while it is stopping. You may consider enabling this option, if you start and stop JMS routes at runtime, while there are still messages enqueued on the queue. If this option is false, and you stop the JMS route, then messages may be rejected, and the JMS broker would have to attempt redeliveries, which yet again may be rejected, and eventually the message may be moved at a dead lette [...]
-| *camel.component.amqp.acknowledgement-mode-name* | The JMS acknowledgement name, which is one of: SESSION_TRANSACTED, CLIENT_ACKNOWLEDGE, AUTO_ACKNOWLEDGE, DUPS_OK_ACKNOWLEDGE | AUTO_ACKNOWLEDGE | String
-| *camel.component.amqp.allow-additional-headers* | This option is used to allow additional headers which may have values that are invalid according to JMS specification. For example some message systems such as WMQ do this with header names using prefix JMS_IBM_MQMD_ containing values with byte array or other invalid types. You can specify multiple header names separated by comma, and use as suffix for wildcard matching. | | String
-| *camel.component.amqp.allow-auto-wired-connection-factory* | Whether to auto-discover ConnectionFactory from the registry, if no connection factory has been configured. If only one instance of ConnectionFactory is found then it will be used. This is enabled by default. | true | Boolean
-| *camel.component.amqp.allow-auto-wired-destination-resolver* | Whether to auto-discover DestinationResolver from the registry, if no destination resolver has been configured. If only one instance of DestinationResolver is found then it will be used. This is enabled by default. | true | Boolean
-| *camel.component.amqp.allow-null-body* | Whether to allow sending messages with no body. If this option is false and the message body is null, then an JMSException is thrown. | true | Boolean
-| *camel.component.amqp.allow-reply-manager-quick-stop* | Whether the DefaultMessageListenerContainer used in the reply managers for request-reply messaging allow the DefaultMessageListenerContainer.runningAllowed flag to quick stop in case JmsConfiguration#isAcceptMessagesWhileStopping is enabled, and org.apache.camel.CamelContext is currently being stopped. This quick stop ability is enabled by default in the regular JMS consumers but to enable for reply managers you must enable this f [...]
-| *camel.component.amqp.allow-serialized-headers* | Controls whether or not to include serialized headers. Applies only when transferExchange is true. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level. | false | Boolean
-| *camel.component.amqp.always-copy-message* | If true, Camel will always make a JMS message copy of the message when it is passed to the producer for sending. Copying the message is needed in some situations, such as when a replyToDestinationSelectorName is set (incidentally, Camel will set the alwaysCopyMessage option to true, if a replyToDestinationSelectorName is set) | false | Boolean
-| *camel.component.amqp.artemis-streaming-enabled* | Whether optimizing for Apache Artemis streaming mode. | true | Boolean
-| *camel.component.amqp.async-consumer* | Whether the JmsConsumer processes the Exchange asynchronously. If enabled then the JmsConsumer may pickup the next message from the JMS queue, while the previous message is being processed asynchronously (by the Asynchronous Routing Engine). This means that messages may be processed not 100% strictly in order. If disabled (as default) then the Exchange is fully processed before the JmsConsumer will pickup the next message from the JMS queue. Note [...]
-| *camel.component.amqp.async-start-listener* | Whether to startup the JmsConsumer message listener asynchronously, when starting a route. For example if a JmsConsumer cannot get a connection to a remote JMS broker, then it may block while retrying and/or failover. This will cause Camel to block while starting routes. By setting this option to true, you will let routes startup, while the JmsConsumer connects to the JMS broker using a dedicated thread in asynchronous mode. If this option [...]
-| *camel.component.amqp.async-stop-listener* | Whether to stop the JmsConsumer message listener asynchronously, when stopping a route. | false | Boolean
-| *camel.component.amqp.auto-startup* | Specifies whether the consumer container should auto-startup. | true | Boolean
-| *camel.component.amqp.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.amqp.cache-level* | Sets the cache level by ID for the underlying JMS resources. See cacheLevelName option for more details. | | Integer
-| *camel.component.amqp.cache-level-name* | Sets the cache level by name for the underlying JMS resources. Possible values are: CACHE_AUTO, CACHE_CONNECTION, CACHE_CONSUMER, CACHE_NONE, and CACHE_SESSION. The default setting is CACHE_AUTO. See the Spring documentation and Transactions Cache Levels for more information. | CACHE_AUTO | String
-| *camel.component.amqp.client-id* | Sets the JMS client ID to use. Note that this value, if specified, must be unique and can only be used by a single JMS connection instance. It is typically only required for durable topic subscriptions. If using Apache ActiveMQ you may prefer to use Virtual Topics instead. | | String
-| *camel.component.amqp.concurrent-consumers* | Specifies the default number of concurrent consumers when consuming from JMS (not for request/reply over JMS). See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. When doing request/reply over JMS then the option replyToConcurrentConsumers is used to control number of concurrent consumers on the reply message listener. | 1 | Integer
-| *camel.component.amqp.configuration* | To use a shared JMS configuration. The option is a org.apache.camel.component.jms.JmsConfiguration type. | | JmsConfiguration
-| *camel.component.amqp.connection-factory* | The connection factory to be use. A connection factory must be configured either on the component or endpoint. The option is a javax.jms.ConnectionFactory type. | | ConnectionFactory
-| *camel.component.amqp.consumer-type* | The consumer type to use, which can be one of: Simple, Default, or Custom. The consumer type determines which Spring JMS listener to use. Default will use org.springframework.jms.listener.DefaultMessageListenerContainer, Simple will use org.springframework.jms.listener.SimpleMessageListenerContainer. When Custom is specified, the MessageListenerContainerFactory defined by the messageListenerContainerFactory option will determine what org.springfra [...]
-| *camel.component.amqp.correlation-property* | When using InOut exchange pattern use this JMS property instead of JMSCorrelationID JMS property to correlate messages. If set messages will be correlated solely on the value of this property JMSCorrelationID property will be ignored and not set by Camel. | | String
-| *camel.component.amqp.default-task-executor-type* | Specifies what default TaskExecutor type to use in the DefaultMessageListenerContainer, for both consumer endpoints and the ReplyTo consumer of producer endpoints. Possible values: SimpleAsync (uses Spring's SimpleAsyncTaskExecutor) or ThreadPool (uses Spring's ThreadPoolTaskExecutor with optimal values - cached threadpool-like). If not set, it defaults to the previous behaviour, which uses a cached thread pool for consumer endpoints [...]
-| *camel.component.amqp.delivery-delay* | Sets delivery delay to use for send calls for JMS. This option requires JMS 2.0 compliant broker. | -1 | Long
-| *camel.component.amqp.delivery-mode* | Specifies the delivery mode to be used. Possible values are those defined by javax.jms.DeliveryMode. NON_PERSISTENT = 1 and PERSISTENT = 2. | | Integer
-| *camel.component.amqp.delivery-persistent* | Specifies whether persistent delivery is used by default. | true | Boolean
-| *camel.component.amqp.destination-resolver* | A pluggable org.springframework.jms.support.destination.DestinationResolver that allows you to use your own resolver (for example, to lookup the real destination in a JNDI registry). The option is a org.springframework.jms.support.destination.DestinationResolver type. | | DestinationResolver
-| *camel.component.amqp.disable-reply-to* | Specifies whether Camel ignores the JMSReplyTo header in messages. If true, Camel does not send a reply back to the destination specified in the JMSReplyTo header. You can use this option if you want Camel to consume from a route and you do not want Camel to automatically send back a reply message because another component in your code handles the reply message. You can also use this option if you want to use Camel as a proxy between different [...]
-| *camel.component.amqp.disable-time-to-live* | Use this option to force disabling time to live. For example when you do request/reply over JMS, then Camel will by default use the requestTimeout value as time to live on the message being sent. The problem is that the sender and receiver systems have to have their clocks synchronized, so they are in sync. This is not always so easy to archive. So you can use disableTimeToLive=true to not set a time to live value on the sent message. Then [...]
-| *camel.component.amqp.durable-subscription-name* | The durable subscriber name for specifying durable topic subscriptions. The clientId option must be configured as well. | | String
-| *camel.component.amqp.eager-loading-of-properties* | Enables eager loading of JMS properties and payload as soon as a message is loaded which generally is inefficient as the JMS properties may not be required but sometimes can catch early any issues with the underlying JMS provider and the use of JMS properties. See also the option eagerPoisonBody. | false | Boolean
-| *camel.component.amqp.eager-poison-body* | If eagerLoadingOfProperties is enabled and the JMS message payload (JMS body or JMS properties) is poison (cannot be read/mapped), then set this text as the message body instead so the message can be processed (the cause of the poison are already stored as exception on the Exchange). This can be turned off by setting eagerPoisonBody=false. See also the option eagerLoadingOfProperties. | Poison JMS message due to ${exception.message} | String
-| *camel.component.amqp.enabled* | Whether to enable auto configuration of the amqp component. This is enabled by default. | | Boolean
-| *camel.component.amqp.error-handler* | Specifies a org.springframework.util.ErrorHandler to be invoked in case of any uncaught exceptions thrown while processing a Message. By default these exceptions will be logged at the WARN level, if no errorHandler has been configured. You can configure logging level and whether stack traces should be logged using errorHandlerLoggingLevel and errorHandlerLogStackTrace options. This makes it much easier to configure, than having to code a custom er [...]
-| *camel.component.amqp.error-handler-log-stack-trace* | Allows to control whether stacktraces should be logged or not, by the default errorHandler. | true | Boolean
-| *camel.component.amqp.error-handler-logging-level* | Allows to configure the default errorHandler logging level for logging uncaught exceptions. | | LoggingLevel
-| *camel.component.amqp.exception-listener* | Specifies the JMS Exception Listener that is to be notified of any underlying JMS exceptions. The option is a javax.jms.ExceptionListener type. | | ExceptionListener
-| *camel.component.amqp.explicit-qos-enabled* | Set if the deliveryMode, priority or timeToLive qualities of service should be used when sending messages. This option is based on Spring's JmsTemplate. The deliveryMode, priority and timeToLive options are applied to the current endpoint. This contrasts with the preserveMessageQos option, which operates at message granularity, reading QoS properties exclusively from the Camel In message headers. | false | Boolean
-| *camel.component.amqp.expose-listener-session* | Specifies whether the listener session should be exposed when consuming messages. | false | Boolean
-| *camel.component.amqp.force-send-original-message* | When using mapJmsMessage=false Camel will create a new JMS message to send to a new JMS destination if you touch the headers (get or set) during the route. Set this option to true to force Camel to send the original JMS message that was received. | false | Boolean
-| *camel.component.amqp.format-date-headers-to-iso8601* | Sets whether JMS date properties should be formatted according to the ISO 8601 standard. | false | Boolean
-| *camel.component.amqp.header-filter-strategy* | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. The option is a org.apache.camel.spi.HeaderFilterStrategy type. | | HeaderFilterStrategy
-| *camel.component.amqp.idle-consumer-limit* | Specify the limit for the number of consumers that are allowed to be idle at any given time. | 1 | Integer
-| *camel.component.amqp.idle-task-execution-limit* | Specifies the limit for idle executions of a receive task, not having received any message within its execution. If this limit is reached, the task will shut down and leave receiving to other executing tasks (in the case of dynamic scheduling; see the maxConcurrentConsumers setting). There is additional doc available from Spring. | 1 | Integer
-| *camel.component.amqp.include-all-jmsx-properties* | Whether to include all JMSXxxx properties when mapping from JMS to Camel Message. Setting this to true will include properties such as JMSXAppID, and JMSXUserID etc. Note: If you are using a custom headerFilterStrategy then this option does not apply. | false | Boolean
-| *camel.component.amqp.include-amqp-annotations* | Whether to include AMQP annotations when mapping from AMQP to Camel Message. Setting this to true maps AMQP message annotations that contain a JMS_AMQP_MA_ prefix to message headers. Due to limitations in Apache Qpid JMS API, currently delivery annotations are ignored. | false | Boolean
-| *camel.component.amqp.include-sent-jms-message-id* | Only applicable when sending to JMS destination using InOnly (eg fire and forget). Enabling this option will enrich the Camel Exchange with the actual JMSMessageID that was used by the JMS client when the message was sent to the JMS destination. | false | Boolean
-| *camel.component.amqp.jms-key-format-strategy* | Pluggable strategy for encoding and decoding JMS keys so they can be compliant with the JMS specification. Camel provides two implementations out of the box: default and passthrough. The default strategy will safely marshal dots and hyphens (. and -). The passthrough strategy leaves the key as is. Can be used for JMS brokers which do not care whether JMS header keys contain illegal characters. You can provide your own implementation of t [...]
-| *camel.component.amqp.jms-message-type* | Allows you to force the use of a specific javax.jms.Message implementation for sending JMS messages. Possible values are: Bytes, Map, Object, Stream, Text. By default, Camel would determine which JMS message type to use from the In body type. This option allows you to specify it. | | JmsMessageType
-| *camel.component.amqp.lazy-create-transaction-manager* | If true, Camel will create a JmsTransactionManager, if there is no transactionManager injected when option transacted=true. | true | Boolean
-| *camel.component.amqp.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
-| *camel.component.amqp.map-jms-message* | Specifies whether Camel should auto map the received JMS message to a suited payload type, such as javax.jms.TextMessage to a String etc. | true | Boolean
-| *camel.component.amqp.max-concurrent-consumers* | Specifies the maximum number of concurrent consumers when consuming from JMS (not for request/reply over JMS). See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. When doing request/reply over JMS then the option replyToMaxConcurrentConsumers is used to control number of concurrent consumers on the reply message listener. | | Integer
-| *camel.component.amqp.max-messages-per-task* | The number of messages per task. -1 is unlimited. If you use a range for concurrent consumers (eg min max), then this option can be used to set a value to eg 100 to control how fast the consumers will shrink when less work is required. | -1 | Integer
-| *camel.component.amqp.message-converter* | To use a custom Spring org.springframework.jms.support.converter.MessageConverter so you can be in control how to map to/from a javax.jms.Message. The option is a org.springframework.jms.support.converter.MessageConverter type. | | MessageConverter
-| *camel.component.amqp.message-created-strategy* | To use the given MessageCreatedStrategy which are invoked when Camel creates new instances of javax.jms.Message objects when Camel is sending a JMS message. The option is a org.apache.camel.component.jms.MessageCreatedStrategy type. | | MessageCreatedStrategy
-| *camel.component.amqp.message-id-enabled* | When sending, specifies whether message IDs should be added. This is just an hint to the JMS broker. If the JMS provider accepts this hint, these messages must have the message ID set to null; if the provider ignores the hint, the message ID must be set to its normal unique value. | true | Boolean
-| *camel.component.amqp.message-listener-container-factory* | Registry ID of the MessageListenerContainerFactory used to determine what org.springframework.jms.listener.AbstractMessageListenerContainer to use to consume messages. Setting this will automatically set consumerType to Custom. The option is a org.apache.camel.component.jms.MessageListenerContainerFactory type. | | MessageListenerContainerFactory
-| *camel.component.amqp.message-timestamp-enabled* | Specifies whether timestamps should be enabled by default on sending messages. This is just an hint to the JMS broker. If the JMS provider accepts this hint, these messages must have the timestamp set to zero; if the provider ignores the hint the timestamp must be set to its normal value. | true | Boolean
-| *camel.component.amqp.password* | Password to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory. | | String
-| *camel.component.amqp.preserve-message-qos* | Set to true, if you want to send message using the QoS settings specified on the message, instead of the QoS settings on the JMS endpoint. The following three headers are considered JMSPriority, JMSDeliveryMode, and JMSExpiration. You can provide all or only some of them. If not provided, Camel will fall back to use the values from the endpoint instead. So, when using this option, the headers override the values from the endpoint. The expli [...]
-| *camel.component.amqp.priority* | Values greater than 1 specify the message priority when sending (where 0 is the lowest priority and 9 is the highest). The explicitQosEnabled option must also be enabled in order for this option to have any effect. | 4 | Integer
-| *camel.component.amqp.pub-sub-no-local* | Specifies whether to inhibit the delivery of messages published by its own connection. | false | Boolean
-| *camel.component.amqp.queue-browse-strategy* | To use a custom QueueBrowseStrategy when browsing queues. The option is a org.apache.camel.component.jms.QueueBrowseStrategy type. | | QueueBrowseStrategy
-| *camel.component.amqp.receive-timeout* | The timeout for receiving messages (in milliseconds). The option is a long type. | 1000 | Long
-| *camel.component.amqp.recovery-interval* | Specifies the interval between recovery attempts, i.e. when a connection is being refreshed, in milliseconds. The default is 5000 ms, that is, 5 seconds. The option is a long type. | 5000 | Long
-| *camel.component.amqp.reply-to* | Provides an explicit ReplyTo destination (overrides any incoming value of Message.getJMSReplyTo() in consumer). | | String
-| *camel.component.amqp.reply-to-cache-level-name* | Sets the cache level by name for the reply consumer when doing request/reply over JMS. This option only applies when using fixed reply queues (not temporary). Camel will by default use: CACHE_CONSUMER for exclusive or shared w/ replyToSelectorName. And CACHE_SESSION for shared without replyToSelectorName. Some JMS brokers such as IBM WebSphere may require to set the replyToCacheLevelName=CACHE_NONE to work. Note: If using temporary que [...]
-| *camel.component.amqp.reply-to-concurrent-consumers* | Specifies the default number of concurrent consumers when doing request/reply over JMS. See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. | 1 | Integer
-| *camel.component.amqp.reply-to-delivery-persistent* | Specifies whether to use persistent delivery by default for replies. | true | Boolean
-| *camel.component.amqp.reply-to-destination-selector-name* | Sets the JMS Selector using the fixed name to be used so you can filter out your own replies from the others when using a shared queue (that is, if you are not using a temporary reply queue). | | String
-| *camel.component.amqp.reply-to-max-concurrent-consumers* | Specifies the maximum number of concurrent consumers when using request/reply over JMS. See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. | | Integer
-| *camel.component.amqp.reply-to-on-timeout-max-concurrent-consumers* | Specifies the maximum number of concurrent consumers for continue routing when timeout occurred when using request/reply over JMS. | 1 | Integer
-| *camel.component.amqp.reply-to-override* | Provides an explicit ReplyTo destination in the JMS message, which overrides the setting of replyTo. It is useful if you want to forward the message to a remote Queue and receive the reply message from the ReplyTo destination. | | String
-| *camel.component.amqp.reply-to-same-destination-allowed* | Whether a JMS consumer is allowed to send a reply message to the same destination that the consumer is using to consume from. This prevents an endless loop by consuming and sending back the same message to itself. | false | Boolean
-| *camel.component.amqp.reply-to-type* | Allows for explicitly specifying which kind of strategy to use for replyTo queues when doing request/reply over JMS. Possible values are: Temporary, Shared, or Exclusive. By default Camel will use temporary queues. However if replyTo has been configured, then Shared is used by default. This option allows you to use exclusive queues instead of shared ones. See Camel JMS documentation for more details, and especially the notes about the implications [...]
-| *camel.component.amqp.request-timeout* | The timeout for waiting for a reply when using the InOut Exchange Pattern (in milliseconds). The default is 20 seconds. You can include the header CamelJmsRequestTimeout to override this endpoint configured timeout value, and thus have per message individual timeout values. See also the requestTimeoutCheckerInterval option. The option is a long type. | 20000 | Long
-| *camel.component.amqp.request-timeout-checker-interval* | Configures how often Camel should check for timed out Exchanges when doing request/reply over JMS. By default Camel checks once per second. But if you must react faster when a timeout occurs, then you can lower this interval, to check more frequently. The timeout is determined by the option requestTimeout. The option is a long type. | 1000 | Long
-| *camel.component.amqp.selector* | Sets the JMS selector to use | | String
-| *camel.component.amqp.stream-message-type-enabled* | Sets whether StreamMessage type is enabled or not. Message payloads of streaming kind such as files, InputStream, etc will either by sent as BytesMessage or StreamMessage. This option controls which kind will be used. By default BytesMessage is used which enforces the entire message payload to be read into memory. By enabling this option the message payload is read into memory in chunks and each chunk is then written to the StreamMes [...]
-| *camel.component.amqp.subscription-durable* | Set whether to make the subscription durable. The durable subscription name to be used can be specified through the subscriptionName property. Default is false. Set this to true to register a durable subscription, typically in combination with a subscriptionName value (unless your message listener class name is good enough as subscription name). Only makes sense when listening to a topic (pub-sub domain), therefore this method switches the [...]
-| *camel.component.amqp.subscription-name* | Set the name of a subscription to create. To be applied in case of a topic (pub-sub domain) with a shared or durable subscription. The subscription name needs to be unique within this client's JMS client id. Default is the class name of the specified message listener. Note: Only 1 concurrent consumer (which is the default of this message listener container) is allowed for each subscription, except for a shared subscription (which requires JMS [...]
-| *camel.component.amqp.subscription-shared* | Set whether to make the subscription shared. The shared subscription name to be used can be specified through the subscriptionName property. Default is false. Set this to true to register a shared subscription, typically in combination with a subscriptionName value (unless your message listener class name is good enough as subscription name). Note that shared subscriptions may also be durable, so this flag can (and often will) be combined wi [...]
-| *camel.component.amqp.task-executor* | Allows you to specify a custom task executor for consuming messages. The option is a org.springframework.core.task.TaskExecutor type. | | TaskExecutor
-| *camel.component.amqp.test-connection-on-startup* | Specifies whether to test the connection on startup. This ensures that when Camel starts that all the JMS consumers have a valid connection to the JMS broker. If a connection cannot be granted then Camel throws an exception on startup. This ensures that Camel is not started with failed connections. The JMS producers is tested as well. | false | Boolean
-| *camel.component.amqp.time-to-live* | When sending messages, specifies the time-to-live of the message (in milliseconds). | -1 | Long
-| *camel.component.amqp.transacted* | Specifies whether to use transacted mode | false | Boolean
-| *camel.component.amqp.transacted-in-out* | Specifies whether InOut operations (request reply) default to using transacted mode If this flag is set to true, then Spring JmsTemplate will have sessionTransacted set to true, and the acknowledgeMode as transacted on the JmsTemplate used for InOut operations. Note from Spring JMS: that within a JTA transaction, the parameters passed to createQueue, createTopic methods are not taken into account. Depending on the Java EE transaction context, [...]
-| *camel.component.amqp.transaction-manager* | The Spring transaction manager to use. The option is a org.springframework.transaction.PlatformTransactionManager type. | | PlatformTransactionManager
-| *camel.component.amqp.transaction-name* | The name of the transaction to use. | | String
-| *camel.component.amqp.transaction-timeout* | The timeout value of the transaction (in seconds), if using transacted mode. | -1 | Integer
-| *camel.component.amqp.transfer-exception* | If enabled and you are using Request Reply messaging (InOut) and an Exchange failed on the consumer side, then the caused Exception will be send back in response as a javax.jms.ObjectMessage. If the client is Camel, the returned Exception is rethrown. This allows you to use Camel JMS as a bridge in your routing - for example, using persistent queues to enable robust routing. Notice that if you also have transferExchange enabled, this option t [...]
-| *camel.component.amqp.transfer-exchange* | You can transfer the exchange over the wire instead of just the body and headers. The following fields are transferred: In body, Out body, Fault body, In headers, Out headers, Fault headers, exchange properties, exchange exception. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level. You must enable this option on both the producer and consumer side, so Camel knows the paylo [...]
-| *camel.component.amqp.use-message-id-as-correlation-id* | Specifies whether JMSMessageID should always be used as JMSCorrelationID for InOut messages. | false | Boolean
-| *camel.component.amqp.username* | Username to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory. | | String
-| *camel.component.amqp.wait-for-provision-correlation-to-be-updated-counter* | Number of times to wait for provisional correlation id to be updated to the actual correlation id when doing request/reply over JMS and when the option useMessageIDAsCorrelationID is enabled. | 50 | Integer
-| *camel.component.amqp.wait-for-provision-correlation-to-be-updated-thread-sleeping-time* | Interval in millis to sleep each time while waiting for provisional correlation id to be updated. The option is a long type. | 100 | Long
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-any23-starter/src/main/docs/any23-starter.adoc b/components-starter/camel-any23-starter/src/main/docs/any23-starter.adoc
deleted file mode 100644
index 7b2563a..0000000
--- a/components-starter/camel-any23-starter/src/main/docs/any23-starter.adoc
+++ /dev/null
@@ -1,33 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for any23
-
-== Spring Boot Auto-Configuration
-
-When using any23 with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-any23-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 5 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.dataformat.any23.base-u-r-i* | The URI to use as base for building RDF entities if only relative paths are provided. | | String
-| *camel.dataformat.any23.configuration* | Configurations for Apache Any23 as key-value pairs in order to customize the extraction process. The list of supported parameters can be found here. If not provided, a default configuration is used. | | List
-| *camel.dataformat.any23.enabled* | Whether to enable auto configuration of the any23 data format. This is enabled by default. | | Boolean
-| *camel.dataformat.any23.extractors* | List of Any23 extractors to be used in the unmarshal operation. A list of the available extractors can be found here here. If not provided, all the available extractors are used. | | List
-| *camel.dataformat.any23.output-format* | What RDF syntax to unmarshal as, can be: NTRIPLES, TURTLE, NQUADS, RDFXML, JSONLD, RDFJSON, RDF4JMODEL. It is by default: RDF4JMODEL. | | Any23OutputFormat
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-apns-starter/src/main/docs/apns-starter.adoc b/components-starter/camel-apns-starter/src/main/docs/apns-starter.adoc
deleted file mode 100644
index 8321444..0000000
--- a/components-starter/camel-apns-starter/src/main/docs/apns-starter.adoc
+++ /dev/null
@@ -1,33 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for apns
-
-== Spring Boot Auto-Configuration
-
-When using apns with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-apns-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 5 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.apns.apns-service* | The ApnsService to use. The org.apache.camel.component.apns.factory.ApnsServiceFactory can be used to build a ApnsService. The option is a com.notnoop.apns.ApnsService type. | | ApnsService
-| *camel.component.apns.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.apns.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.apns.enabled* | Whether to enable auto configuration of the apns component. This is enabled by default. | | Boolean
-| *camel.component.apns.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-arangodb-starter/src/main/docs/arangodb-starter.adoc b/components-starter/camel-arangodb-starter/src/main/docs/arangodb-starter.adoc
deleted file mode 100644
index 61edb45..0000000
--- a/components-starter/camel-arangodb-starter/src/main/docs/arangodb-starter.adoc
+++ /dev/null
@@ -1,41 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for arangodb
-
-== Spring Boot Auto-Configuration
-
-When using arangodb with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-arangodb-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 13 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.arangodb.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.arangodb.configuration* | Component configuration. The option is a org.apache.camel.component.arangodb.ArangoDbConfiguration type. | | ArangoDbConfiguration
-| *camel.component.arangodb.document-collection* | Collection name, when using ArangoDb as a Document Database. Set the documentCollection name when using the CRUD operation on the document database collections (SAVE_DOCUMENT , FIND_DOCUMENT_BY_KEY, UPDATE_DOCUMENT, DELETE_DOCUMENT). | | String
-| *camel.component.arangodb.edge-collection* | Collection name of vertices, when using ArangoDb as a Graph Database. Set the edgeCollection name to perform CRUD operation on edges using these operations : SAVE_VERTEX, FIND_VERTEX_BY_KEY, UPDATE_VERTEX, DELETE_VERTEX. The graph attribute is mandatory. | | String
-| *camel.component.arangodb.enabled* | Whether to enable auto configuration of the arangodb component. This is enabled by default. | | Boolean
-| *camel.component.arangodb.graph* | Graph name, when using ArangoDb as a Graph Database. Combine this attribute with one of the two attributes vertexCollection and edgeCollection. | | String
-| *camel.component.arangodb.host* | ArangoDB host. If host and port are default, this field is Optional. | | String
-| *camel.component.arangodb.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed t [...]
-| *camel.component.arangodb.operation* | Operations to perform on ArangoDb. For the operation AQL_QUERY, no need to specify a collection or graph. | | ArangoDbOperation
-| *camel.component.arangodb.password* | ArangoDB password. If user and password are default, this field is Optional. | | String
-| *camel.component.arangodb.port* | ArangoDB exposed port. If host and port are default, this field is Optional. | | Integer
-| *camel.component.arangodb.user* | ArangoDB user. If user and password are default, this field is Optional. | | String
-| *camel.component.arangodb.vertex-collection* | Collection name of vertices, when using ArangoDb as a Graph Database. Set the vertexCollection name to perform CRUD operation on vertices using these operations : SAVE_EDGE, FIND_EDGE_BY_KEY, UPDATE_EDGE, DELETE_EDGE. The graph attribute is mandatory. | | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-as2-starter/src/main/docs/as2-starter.adoc b/components-starter/camel-as2-starter/src/main/docs/as2-starter.adoc
deleted file mode 100644
index 91a0c4f..0000000
--- a/components-starter/camel-as2-starter/src/main/docs/as2-starter.adoc
+++ /dev/null
@@ -1,33 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for as2
-
-== Spring Boot Auto-Configuration
-
-When using as2 with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-as2-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 5 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.as2.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.as2.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.as2.configuration* | Component configuration. The option is a org.apache.camel.component.as2.AS2Configuration type. | | AS2Configuration
-| *camel.component.as2.enabled* | Whether to enable auto configuration of the as2 component. This is enabled by default. | | Boolean
-| *camel.component.as2.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then c [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-asn1-starter/src/main/docs/asn1-starter.adoc b/components-starter/camel-asn1-starter/src/main/docs/asn1-starter.adoc
deleted file mode 100644
index f3427d9..0000000
--- a/components-starter/camel-asn1-starter/src/main/docs/asn1-starter.adoc
+++ /dev/null
@@ -1,31 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for asn1
-
-== Spring Boot Auto-Configuration
-
-When using asn1 with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-asn1-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 3 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.dataformat.asn1.clazz-name* | Name of class to use when unmarshalling | | String
-| *camel.dataformat.asn1.enabled* | Whether to enable auto configuration of the asn1 data format. This is enabled by default. | | Boolean
-| *camel.dataformat.asn1.using-iterator* | If the asn1 file has more then one entry, the setting this option to true, allows to work with the splitter EIP, to split the data using an iterator in a streaming mode. | false | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-asterisk-starter/src/main/docs/asterisk-starter.adoc b/components-starter/camel-asterisk-starter/src/main/docs/asterisk-starter.adoc
deleted file mode 100644
index 6738762..0000000
--- a/components-starter/camel-asterisk-starter/src/main/docs/asterisk-starter.adoc
+++ /dev/null
@@ -1,32 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for asterisk
-
-== Spring Boot Auto-Configuration
-
-When using asterisk with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-asterisk-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 4 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.asterisk.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.asterisk.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.asterisk.enabled* | Whether to enable auto configuration of the asterisk component. This is enabled by default. | | Boolean
-| *camel.component.asterisk.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed t [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-atlasmap-starter/src/main/docs/atlasmap-starter.adoc b/components-starter/camel-atlasmap-starter/src/main/docs/atlasmap-starter.adoc
deleted file mode 100644
index f565d35..0000000
--- a/components-starter/camel-atlasmap-starter/src/main/docs/atlasmap-starter.adoc
+++ /dev/null
@@ -1,32 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for atlasmap
-
-== Spring Boot Auto-Configuration
-
-When using atlasmap with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-atlasmap-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 4 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.atlasmap.atlas-context-factory* | To use the AtlasContextFactory otherwise a new engine is created. The option is a io.atlasmap.api.AtlasContextFactory type. | | AtlasContextFactory
-| *camel.component.atlasmap.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.atlasmap.enabled* | Whether to enable auto configuration of the atlasmap component. This is enabled by default. | | Boolean
-| *camel.component.atlasmap.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed t [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-atmos-starter/src/main/docs/atmos-starter.adoc b/components-starter/camel-atmos-starter/src/main/docs/atmos-starter.adoc
deleted file mode 100644
index a8e1024..0000000
--- a/components-starter/camel-atmos-starter/src/main/docs/atmos-starter.adoc
+++ /dev/null
@@ -1,36 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for atmos
-
-== Spring Boot Auto-Configuration
-
-When using atmos with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-atmos-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 8 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.atmos.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.atmos.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.atmos.enabled* | Whether to enable auto configuration of the atmos component. This is enabled by default. | | Boolean
-| *camel.component.atmos.full-token-id* | The token id to pass to the Atmos client | | String
-| *camel.component.atmos.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
-| *camel.component.atmos.secret-key* | The secret key to pass to the Atmos client (should be base64 encoded) | | String
-| *camel.component.atmos.ssl-validation* | Whether the Atmos client should perform SSL validation | false | Boolean
-| *camel.component.atmos.uri* | The URI of the server for the Atmos client to connect to | | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-atmosphere-websocket-starter/src/main/docs/atmosphere-websocket-starter.adoc b/components-starter/camel-atmosphere-websocket-starter/src/main/docs/atmosphere-websocket-starter.adoc
deleted file mode 100644
index 883d89e..0000000
--- a/components-starter/camel-atmosphere-websocket-starter/src/main/docs/atmosphere-websocket-starter.adoc
+++ /dev/null
@@ -1,40 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for atmosphere-websocket
-
-== Spring Boot Auto-Configuration
-
-When using atmosphere-websocket with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-atmosphere-websocket-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 12 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.atmosphere-websocket.allow-java-serialized-object* | Whether to allow java serialization when a request uses context-type=application/x-java-serialized-object. This is by default turned off. If you enable this then be aware that Java will deserialize the incoming data from the request to Java and that can be a potential security risk. | false | Boolean
-| *camel.component.atmosphere-websocket.attachment-multipart-binding* | Whether to automatic bind multipart/form-data as attachments on the Camel Exchange. The options attachmentMultipartBinding=true and disableStreamCache=false cannot work together. Remove disableStreamCache to use AttachmentMultipartBinding. This is turn off by default as this may require servlet specific configuration to enable this when using Servlet's. | false | Boolean
-| *camel.component.atmosphere-websocket.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.atmosphere-websocket.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.atmosphere-websocket.enabled* | Whether to enable auto configuration of the atmosphere-websocket component. This is enabled by default. | | Boolean
-| *camel.component.atmosphere-websocket.file-name-ext-whitelist* | Whitelist of accepted filename extensions for accepting uploaded files. Multiple extensions can be separated by comma, such as txt,xml. | | String
-| *camel.component.atmosphere-websocket.header-filter-strategy* | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. The option is a org.apache.camel.spi.HeaderFilterStrategy type. | | HeaderFilterStrategy
-| *camel.component.atmosphere-websocket.http-binding* | To use a custom HttpBinding to control the mapping between Camel message and HttpClient. The option is a org.apache.camel.http.common.HttpBinding type. | | HttpBinding
-| *camel.component.atmosphere-websocket.http-configuration* | To use the shared HttpConfiguration as base configuration. The option is a org.apache.camel.http.common.HttpConfiguration type. | | HttpConfiguration
-| *camel.component.atmosphere-websocket.http-registry* | To use a custom org.apache.camel.component.servlet.HttpRegistry. The option is a org.apache.camel.http.common.HttpRegistry type. | | HttpRegistry
-| *camel.component.atmosphere-websocket.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is [...]
-| *camel.component.atmosphere-websocket.servlet-name* | Default name of servlet to use. The default name is CamelServlet. | CamelServlet | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-atom-starter/src/main/docs/atom-starter.adoc b/components-starter/camel-atom-starter/src/main/docs/atom-starter.adoc
deleted file mode 100644
index 0dfb33f..0000000
--- a/components-starter/camel-atom-starter/src/main/docs/atom-starter.adoc
+++ /dev/null
@@ -1,31 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for atom
-
-== Spring Boot Auto-Configuration
-
-When using atom with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-atom-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 3 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.atom.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.atom.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.atom.enabled* | Whether to enable auto configuration of the atom component. This is enabled by default. | | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-atomix-starter/src/main/docs/atomix-starter.adoc b/components-starter/camel-atomix-starter/src/main/docs/atomix-starter.adoc
deleted file mode 100644
index 80453e4..0000000
--- a/components-starter/camel-atomix-starter/src/main/docs/atomix-starter.adoc
+++ /dev/null
@@ -1,149 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for atomix
-
-== Spring Boot Auto-Configuration
-
-When using atomix with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-atomix-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 121 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.atomix-map.atomix* | The Atomix instance to use. The option is a io.atomix.Atomix type. | | Atomix
-| *camel.component.atomix-map.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.atomix-map.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.atomix-map.configuration* | The shared component configuration. The option is a org.apache.camel.component.atomix.client.map.AtomixMapConfiguration type. | | AtomixMapConfiguration
-| *camel.component.atomix-map.configuration-uri* | The path to the AtomixClient configuration | | String
-| *camel.component.atomix-map.default-action* | The default action. | | AtomixMap$Action
-| *camel.component.atomix-map.default-resource-config* | The cluster wide default resource configuration. The option is a java.util.Properties type. | | Properties
-| *camel.component.atomix-map.default-resource-options* | The local default resource options. The option is a java.util.Properties type. | | Properties
-| *camel.component.atomix-map.enabled* | Whether to enable auto configuration of the atomix-map component. This is enabled by default. | | Boolean
-| *camel.component.atomix-map.ephemeral* | Sets if the local member should join groups as PersistentMember or not. If set to ephemeral the local member will receive an auto generated ID thus the local one is ignored. | false | Boolean
-| *camel.component.atomix-map.key* | The key to use if none is set in the header or to listen for events for a specific key. The option is a java.lang.Object type. | | Object
-| *camel.component.atomix-map.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed [...]
-| *camel.component.atomix-map.nodes* | The nodes the AtomixClient should connect to | | List
-| *camel.component.atomix-map.read-consistency* | The read consistency level. | | ReadConsistency
-| *camel.component.atomix-map.resource-configs* | Cluster wide resources configuration. | | Map
-| *camel.component.atomix-map.resource-options* | Local resources configurations | | Map
-| *camel.component.atomix-map.result-header* | The header that wil carry the result. | | String
-| *camel.component.atomix-map.transport-class-name* | The class name (fqn) of the Atomix transport | io.atomix.catalyst.transport.netty.NettyTransport | String
-| *camel.component.atomix-map.ttl* | The resource ttl. The option is a long type. | | Long
-| *camel.component.atomix-messaging.atomix* | The Atomix instance to use. The option is a io.atomix.Atomix type. | | Atomix
-| *camel.component.atomix-messaging.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.atomix-messaging.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.atomix-messaging.broadcast-type* | The broadcast type. | | AtomixMessaging$BroadcastType
-| *camel.component.atomix-messaging.channel-name* | The messaging channel name | | String
-| *camel.component.atomix-messaging.configuration* | The shared component configuration. The option is a org.apache.camel.component.atomix.client.messaging.AtomixMessagingConfiguration type. | | AtomixMessagingConfiguration
-| *camel.component.atomix-messaging.configuration-uri* | The path to the AtomixClient configuration | | String
-| *camel.component.atomix-messaging.default-action* | The default action. | | AtomixMessaging$Action
-| *camel.component.atomix-messaging.default-resource-config* | The cluster wide default resource configuration. The option is a java.util.Properties type. | | Properties
-| *camel.component.atomix-messaging.default-resource-options* | The local default resource options. The option is a java.util.Properties type. | | Properties
-| *camel.component.atomix-messaging.enabled* | Whether to enable auto configuration of the atomix-messaging component. This is enabled by default. | | Boolean
-| *camel.component.atomix-messaging.ephemeral* | Sets if the local member should join groups as PersistentMember or not. If set to ephemeral the local member will receive an auto generated ID thus the local one is ignored. | false | Boolean
-| *camel.component.atomix-messaging.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is pro [...]
-| *camel.component.atomix-messaging.member-name* | The Atomix Group member name | | String
-| *camel.component.atomix-messaging.nodes* | The nodes the AtomixClient should connect to | | List
-| *camel.component.atomix-messaging.read-consistency* | The read consistency level. | | ReadConsistency
-| *camel.component.atomix-messaging.resource-configs* | Cluster wide resources configuration. | | Map
-| *camel.component.atomix-messaging.resource-options* | Local resources configurations | | Map
-| *camel.component.atomix-messaging.result-header* | The header that wil carry the result. | | String
-| *camel.component.atomix-messaging.transport-class-name* | The class name (fqn) of the Atomix transport | io.atomix.catalyst.transport.netty.NettyTransport | String
-| *camel.component.atomix-multimap.atomix* | The Atomix instance to use. The option is a io.atomix.Atomix type. | | Atomix
-| *camel.component.atomix-multimap.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.atomix-multimap.configuration* | The shared component configuration. The option is a org.apache.camel.component.atomix.client.multimap.AtomixMultiMapConfiguration type. | | AtomixMultiMapConfiguration
-| *camel.component.atomix-multimap.configuration-uri* | The path to the AtomixClient configuration | | String
-| *camel.component.atomix-multimap.default-action* | The default action. | | AtomixMultiMap$Action
-| *camel.component.atomix-multimap.default-resource-config* | The cluster wide default resource configuration. The option is a java.util.Properties type. | | Properties
-| *camel.component.atomix-multimap.default-resource-options* | The local default resource options. The option is a java.util.Properties type. | | Properties
-| *camel.component.atomix-multimap.enabled* | Whether to enable auto configuration of the atomix-multimap component. This is enabled by default. | | Boolean
-| *camel.component.atomix-multimap.ephemeral* | Sets if the local member should join groups as PersistentMember or not. If set to ephemeral the local member will receive an auto generated ID thus the local one is ignored. | false | Boolean
-| *camel.component.atomix-multimap.key* | The key to use if none is set in the header or to listen for events for a specific key. The option is a java.lang.Object type. | | Object
-| *camel.component.atomix-multimap.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proc [...]
-| *camel.component.atomix-multimap.nodes* | The nodes the AtomixClient should connect to | | List
-| *camel.component.atomix-multimap.read-consistency* | The read consistency level. | | ReadConsistency
-| *camel.component.atomix-multimap.resource-configs* | Cluster wide resources configuration. | | Map
-| *camel.component.atomix-multimap.resource-options* | Local resources configurations | | Map
-| *camel.component.atomix-multimap.result-header* | The header that wil carry the result. | | String
-| *camel.component.atomix-multimap.transport-class-name* | The class name (fqn) of the Atomix transport | io.atomix.catalyst.transport.netty.NettyTransport | String
-| *camel.component.atomix-multimap.ttl* | The resource ttl. The option is a long type. | | Long
-| *camel.component.atomix-queue.atomix* | The Atomix instance to use. The option is a io.atomix.Atomix type. | | Atomix
-| *camel.component.atomix-queue.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.atomix-queue.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.atomix-queue.configuration* | The shared component configuration. The option is a org.apache.camel.component.atomix.client.queue.AtomixQueueConfiguration type. | | AtomixQueueConfiguration
-| *camel.component.atomix-queue.configuration-uri* | The path to the AtomixClient configuration | | String
-| *camel.component.atomix-queue.default-action* | The default action. | | AtomixQueue$Action
-| *camel.component.atomix-queue.default-resource-config* | The cluster wide default resource configuration. The option is a java.util.Properties type. | | Properties
-| *camel.component.atomix-queue.default-resource-options* | The local default resource options. The option is a java.util.Properties type. | | Properties
-| *camel.component.atomix-queue.enabled* | Whether to enable auto configuration of the atomix-queue component. This is enabled by default. | | Boolean
-| *camel.component.atomix-queue.ephemeral* | Sets if the local member should join groups as PersistentMember or not. If set to ephemeral the local member will receive an auto generated ID thus the local one is ignored. | false | Boolean
-| *camel.component.atomix-queue.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is process [...]
-| *camel.component.atomix-queue.nodes* | The nodes the AtomixClient should connect to | | List
-| *camel.component.atomix-queue.read-consistency* | The read consistency level. | | ReadConsistency
-| *camel.component.atomix-queue.resource-configs* | Cluster wide resources configuration. | | Map
-| *camel.component.atomix-queue.resource-options* | Local resources configurations | | Map
-| *camel.component.atomix-queue.result-header* | The header that wil carry the result. | | String
-| *camel.component.atomix-queue.transport-class-name* | The class name (fqn) of the Atomix transport | io.atomix.catalyst.transport.netty.NettyTransport | String
-| *camel.component.atomix-set.atomix* | The Atomix instance to use. The option is a io.atomix.Atomix type. | | Atomix
-| *camel.component.atomix-set.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.atomix-set.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.atomix-set.configuration* | The shared component configuration. The option is a org.apache.camel.component.atomix.client.set.AtomixSetConfiguration type. | | AtomixSetConfiguration
-| *camel.component.atomix-set.configuration-uri* | The path to the AtomixClient configuration | | String
-| *camel.component.atomix-set.default-action* | The default action. | | AtomixSet$Action
-| *camel.component.atomix-set.default-resource-config* | The cluster wide default resource configuration. The option is a java.util.Properties type. | | Properties
-| *camel.component.atomix-set.default-resource-options* | The local default resource options. The option is a java.util.Properties type. | | Properties
-| *camel.component.atomix-set.enabled* | Whether to enable auto configuration of the atomix-set component. This is enabled by default. | | Boolean
-| *camel.component.atomix-set.ephemeral* | Sets if the local member should join groups as PersistentMember or not. If set to ephemeral the local member will receive an auto generated ID thus the local one is ignored. | false | Boolean
-| *camel.component.atomix-set.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed [...]
-| *camel.component.atomix-set.nodes* | The nodes the AtomixClient should connect to | | List
-| *camel.component.atomix-set.read-consistency* | The read consistency level. | | ReadConsistency
-| *camel.component.atomix-set.resource-configs* | Cluster wide resources configuration. | | Map
-| *camel.component.atomix-set.resource-options* | Local resources configurations | | Map
-| *camel.component.atomix-set.result-header* | The header that wil carry the result. | | String
-| *camel.component.atomix-set.transport-class-name* | The class name (fqn) of the Atomix transport | io.atomix.catalyst.transport.netty.NettyTransport | String
-| *camel.component.atomix-set.ttl* | The resource ttl. The option is a long type. | | Long
-| *camel.component.atomix-value.atomix* | The Atomix instance to use. The option is a io.atomix.Atomix type. | | Atomix
-| *camel.component.atomix-value.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.atomix-value.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.atomix-value.configuration* | The shared component configuration. The option is a org.apache.camel.component.atomix.client.value.AtomixValueConfiguration type. | | AtomixValueConfiguration
-| *camel.component.atomix-value.configuration-uri* | The path to the AtomixClient configuration | | String
-| *camel.component.atomix-value.default-action* | The default action. | | AtomixValue$Action
-| *camel.component.atomix-value.default-resource-config* | The cluster wide default resource configuration. The option is a java.util.Properties type. | | Properties
-| *camel.component.atomix-value.default-resource-options* | The local default resource options. The option is a java.util.Properties type. | | Properties
-| *camel.component.atomix-value.enabled* | Whether to enable auto configuration of the atomix-value component. This is enabled by default. | | Boolean
-| *camel.component.atomix-value.ephemeral* | Sets if the local member should join groups as PersistentMember or not. If set to ephemeral the local member will receive an auto generated ID thus the local one is ignored. | false | Boolean
-| *camel.component.atomix-value.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is process [...]
-| *camel.component.atomix-value.nodes* | The nodes the AtomixClient should connect to | | List
-| *camel.component.atomix-value.read-consistency* | The read consistency level. | | ReadConsistency
-| *camel.component.atomix-value.resource-configs* | Cluster wide resources configuration. | | Map
-| *camel.component.atomix-value.resource-options* | Local resources configurations | | Map
-| *camel.component.atomix-value.result-header* | The header that wil carry the result. | | String
-| *camel.component.atomix-value.transport-class-name* | The class name (fqn) of the Atomix transport | io.atomix.catalyst.transport.netty.NettyTransport | String
-| *camel.component.atomix-value.ttl* | The resource ttl. The option is a long type. | | Long
-| *camel.component.atomix.cluster.service.address* | The address of the node - node only. | | String
-| *camel.component.atomix.cluster.service.attributes* | Custom service attributes. | | Map
-| *camel.component.atomix.cluster.service.configuration-uri* | The Atomix configuration uri. | | String
-| *camel.component.atomix.cluster.service.enabled* | Sets if the atomix cluster service should be enabled or not, default is false. | false | Boolean
-| *camel.component.atomix.cluster.service.ephemeral* | Sets if the local member should join groups as PersistentMember or not (node only). | | Boolean
-| *camel.component.atomix.cluster.service.id* | The cluster id. | | String
-| *camel.component.atomix.cluster.service.mode* | Sets the cluster mode. | | AtomixClusterServiceConfiguration$Mode
-| *camel.component.atomix.cluster.service.nodes* | The address of the nodes composing the cluster. | | Set
-| *camel.component.atomix.cluster.service.order* | Service lookup order/priority. | | Integer
-| *camel.component.atomix.cluster.service.storage-level* | The storage mode - node only. | | StorageLevel
-| *camel.component.atomix.cluster.service.storage-path* | The storage directory - node only. | | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-avro-rpc-starter/src/main/docs/avro-rpc-starter.adoc b/components-starter/camel-avro-rpc-starter/src/main/docs/avro-rpc-starter.adoc
deleted file mode 100644
index a2c533c..0000000
--- a/components-starter/camel-avro-rpc-starter/src/main/docs/avro-rpc-starter.adoc
+++ /dev/null
@@ -1,39 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for avro-rpc
-
-== Spring Boot Auto-Configuration
-
-When using avro-rpc with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-avro-rpc-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 11 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.avro.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.avro.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.avro.configuration* | To use a shared AvroConfiguration to configure options once. The option is a org.apache.camel.component.avro.AvroConfiguration type. | | AvroConfiguration
-| *camel.component.avro.enabled* | Whether to enable auto configuration of the avro component. This is enabled by default. | | Boolean
-| *camel.component.avro.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
-| *camel.component.avro.protocol* | Avro protocol to use. The option is a org.apache.avro.Protocol type. | | Protocol
-| *camel.component.avro.protocol-class-name* | Avro protocol to use defined by the FQN class name | | String
-| *camel.component.avro.protocol-location* | Avro protocol location | | String
-| *camel.component.avro.reflection-protocol* | If protocol object provided is reflection protocol. Should be used only with protocol parameter because for protocolClassName protocol type will be auto detected | false | Boolean
-| *camel.component.avro.single-parameter* | If true, consumer parameter won't be wrapped into array. Will fail if protocol specifies more then 1 parameter for the message | false | Boolean
-| *camel.component.avro.uri-authority* | Authority to use (username and password) | | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-avro-starter/src/main/docs/avro-starter.adoc b/components-starter/camel-avro-starter/src/main/docs/avro-starter.adoc
deleted file mode 100644
index bde1c2e..0000000
--- a/components-starter/camel-avro-starter/src/main/docs/avro-starter.adoc
+++ /dev/null
@@ -1,30 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for avro
-
-== Spring Boot Auto-Configuration
-
-When using avro with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-avro-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 2 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.dataformat.avro.enabled* | Whether to enable auto configuration of the avro data format. This is enabled by default. | | Boolean
-| *camel.dataformat.avro.instance-class-name* | Class name to use for marshal and unmarshalling | | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-aws-cw-starter/src/main/docs/aws-cw-starter.adoc b/components-starter/camel-aws-cw-starter/src/main/docs/aws-cw-starter.adoc
deleted file mode 100644
index 846267f..0000000
--- a/components-starter/camel-aws-cw-starter/src/main/docs/aws-cw-starter.adoc
+++ /dev/null
@@ -1,44 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for aws-cw
-
-== Spring Boot Auto-Configuration
-
-When using aws-cw with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-aws-cw-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 16 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.aws-cw.access-key* | Amazon AWS Access Key | | String
-| *camel.component.aws-cw.amazon-cw-client* | To use the AmazonCloudWatch as the client. The option is a com.amazonaws.services.cloudwatch.AmazonCloudWatch type. | | AmazonCloudWatch
-| *camel.component.aws-cw.auto-discover-client* | Setting the autoDiscoverClient mechanism, if true, the component will look for a client instance in the registry automatically otherwise it will skip that checking. | true | Boolean
-| *camel.component.aws-cw.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.aws-cw.configuration* | The component configuration. The option is a org.apache.camel.component.aws.cw.CwConfiguration type. | | CwConfiguration
-| *camel.component.aws-cw.enabled* | Whether to enable auto configuration of the aws-cw component. This is enabled by default. | | Boolean
-| *camel.component.aws-cw.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed the [...]
-| *camel.component.aws-cw.name* | The metric name | | String
-| *camel.component.aws-cw.proxy-host* | To define a proxy host when instantiating the CW client | | String
-| *camel.component.aws-cw.proxy-port* | To define a proxy port when instantiating the CW client | | Integer
-| *camel.component.aws-cw.proxy-protocol* | To define a proxy protocol when instantiating the CW client | | Protocol
-| *camel.component.aws-cw.region* | The region in which CW client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | | String
-| *camel.component.aws-cw.secret-key* | Amazon AWS Secret Key | | String
-| *camel.component.aws-cw.timestamp* | The metric timestamp | | Date
-| *camel.component.aws-cw.unit* | The metric unit | | String
-| *camel.component.aws-cw.value* | The metric value | | Double
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-aws-ddb-starter/src/main/docs/aws-ddb-starter.adoc b/components-starter/camel-aws-ddb-starter/src/main/docs/aws-ddb-starter.adoc
deleted file mode 100644
index 5298edd..0000000
--- a/components-starter/camel-aws-ddb-starter/src/main/docs/aws-ddb-starter.adoc
+++ /dev/null
@@ -1,61 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for aws-ddb
-
-== Spring Boot Auto-Configuration
-
-When using aws-ddb with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-aws-ddb-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 33 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.aws-ddb.access-key* | Amazon AWS Access Key | | String
-| *camel.component.aws-ddb.amazon-d-d-b-client* | To use the AmazonDynamoDB as the client. The option is a com.amazonaws.services.dynamodbv2.AmazonDynamoDB type. | | AmazonDynamoDB
-| *camel.component.aws-ddb.auto-discover-client* | Setting the autoDiscoverClient mechanism, if true, the component will look for a client instance in the registry automatically otherwise it will skip that checking. | true | Boolean
-| *camel.component.aws-ddb.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.aws-ddb.configuration* | The component configuration. The option is a org.apache.camel.component.aws.ddb.DdbConfiguration type. | | DdbConfiguration
-| *camel.component.aws-ddb.consistent-read* | Determines whether or not strong consistency should be enforced when data is read. | false | Boolean
-| *camel.component.aws-ddb.enabled* | Whether to enable auto configuration of the aws-ddb component. This is enabled by default. | | Boolean
-| *camel.component.aws-ddb.key-attribute-name* | Attribute name when creating table | | String
-| *camel.component.aws-ddb.key-attribute-type* | Attribute type when creating table | | String
-| *camel.component.aws-ddb.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
-| *camel.component.aws-ddb.operation* | What operation to perform | | DdbOperations
-| *camel.component.aws-ddb.proxy-host* | To define a proxy host when instantiating the DDB client | | String
-| *camel.component.aws-ddb.proxy-port* | To define a proxy port when instantiating the DDB client. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | | Integer
-| *camel.component.aws-ddb.proxy-protocol* | To define a proxy protocol when instantiating the DDB client | | Protocol
-| *camel.component.aws-ddb.read-capacity* | The provisioned throughput to reserve for reading resources from your table | | Long
-| *camel.component.aws-ddb.region* | The region in which DDB client needs to work | | String
-| *camel.component.aws-ddb.secret-key* | Amazon AWS Secret Key | | String
-| *camel.component.aws-ddb.write-capacity* | The provisioned throughput to reserved for writing resources to your table | | Long
-| *camel.component.aws-ddbstream.access-key* | Amazon AWS Access Key | | String
-| *camel.component.aws-ddbstream.amazon-dynamo-db-streams-client* | Amazon DynamoDB client to use for all requests for this endpoint. The option is a com.amazonaws.services.dynamodbv2.AmazonDynamoDBStreams type. | | AmazonDynamoDBStreams
-| *camel.component.aws-ddbstream.auto-discover-client* | Setting the autoDiscoverClient mechanism, if true, the component will look for a client instance in the registry automatically otherwise it will skip that checking | true | Boolean
-| *camel.component.aws-ddbstream.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.aws-ddbstream.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.aws-ddbstream.configuration* | The component configuration. The option is a org.apache.camel.component.aws.ddbstream.DdbStreamConfiguration type. | | DdbStreamConfiguration
-| *camel.component.aws-ddbstream.enabled* | Whether to enable auto configuration of the aws-ddbstream component. This is enabled by default. | | Boolean
-| *camel.component.aws-ddbstream.iterator-type* | Defines where in the DynaboDB stream to start getting records. Note that using TRIM_HORIZON can cause a significant delay before the stream has caught up to real-time. if {AT,AFTER}_SEQUENCE_NUMBER are used, then a sequenceNumberProvider MUST be supplied. | | ShardIteratorType
-| *camel.component.aws-ddbstream.max-results-per-request* | Maximum number of records that will be fetched in each poll | | Integer
-| *camel.component.aws-ddbstream.proxy-host* | To define a proxy host when instantiating the DDBStreams client | | String
-| *camel.component.aws-ddbstream.proxy-port* | To define a proxy port when instantiating the DDBStreams client | | Integer
-| *camel.component.aws-ddbstream.proxy-protocol* | To define a proxy protocol when instantiating the DDBStreams client | | Protocol
-| *camel.component.aws-ddbstream.region* | The region in which DDBStreams client needs to work | | String
-| *camel.component.aws-ddbstream.secret-key* | Amazon AWS Secret Key | | String
-| *camel.component.aws-ddbstream.sequence-number-provider* | Provider for the sequence number when using one of the two ShardIteratorType.{AT,AFTER}_SEQUENCE_NUMBER iterator types. Can be a registry reference or a literal sequence number. The option is a org.apache.camel.component.aws.ddbstream.SequenceNumberProvider type. | | SequenceNumberProvider
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-aws-ec2-starter/src/main/docs/aws-ec2-starter.adoc b/components-starter/camel-aws-ec2-starter/src/main/docs/aws-ec2-starter.adoc
deleted file mode 100644
index 6093a49..0000000
--- a/components-starter/camel-aws-ec2-starter/src/main/docs/aws-ec2-starter.adoc
+++ /dev/null
@@ -1,41 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for aws-ec2
-
-== Spring Boot Auto-Configuration
-
-When using aws-ec2 with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-aws-ec2-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 13 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.aws-ec2.access-key* | Amazon AWS Access Key | | String
-| *camel.component.aws-ec2.amazon-ec2-client* | To use a existing configured AmazonEC2Client as client. The option is a com.amazonaws.services.ec2.AmazonEC2 type. | | AmazonEC2
-| *camel.component.aws-ec2.auto-discover-client* | Setting the autoDiscoverClient mechanism, if true, the component will look for a client instance in the registry automatically otherwise it will skip that checking. | true | Boolean
-| *camel.component.aws-ec2.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.aws-ec2.configuration* | The component configuration. The option is a org.apache.camel.component.aws.ec2.EC2Configuration type. | | EC2Configuration
-| *camel.component.aws-ec2.enabled* | Whether to enable auto configuration of the aws-ec2 component. This is enabled by default. | | Boolean
-| *camel.component.aws-ec2.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
-| *camel.component.aws-ec2.operation* | The operation to perform. It can be createAndRunInstances, startInstances, stopInstances, terminateInstances, describeInstances, describeInstancesStatus, rebootInstances, monitorInstances, unmonitorInstances, createTags or deleteTags | | EC2Operations
-| *camel.component.aws-ec2.proxy-host* | To define a proxy host when instantiating the EC2 client | | String
-| *camel.component.aws-ec2.proxy-port* | To define a proxy port when instantiating the EC2 client | | Integer
-| *camel.component.aws-ec2.proxy-protocol* | To define a proxy protocol when instantiating the EC2 client | | Protocol
-| *camel.component.aws-ec2.region* | The region in which ECS client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | | String
-| *camel.component.aws-ec2.secret-key* | Amazon AWS Secret Key | | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-aws-ecs-starter/src/main/docs/aws-ecs-starter.adoc b/components-starter/camel-aws-ecs-starter/src/main/docs/aws-ecs-starter.adoc
deleted file mode 100644
index 0a26de8..0000000
--- a/components-starter/camel-aws-ecs-starter/src/main/docs/aws-ecs-starter.adoc
+++ /dev/null
@@ -1,41 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for aws-ecs
-
-== Spring Boot Auto-Configuration
-
-When using aws-ecs with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-aws-ecs-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 13 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.aws-ecs.access-key* | Amazon AWS Access Key | | String
-| *camel.component.aws-ecs.auto-discover-client* | Setting the autoDiscoverClient mechanism, if true, the component will look for a client instance in the registry automatically otherwise it will skip that checking. | true | Boolean
-| *camel.component.aws-ecs.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.aws-ecs.configuration* | The component configuration. The option is a org.apache.camel.component.aws.ecs.ECSConfiguration type. | | ECSConfiguration
-| *camel.component.aws-ecs.ecs-client* | To use a existing configured AWS ECS as client. The option is a com.amazonaws.services.ecs.AmazonECS type. | | AmazonECS
-| *camel.component.aws-ecs.enabled* | Whether to enable auto configuration of the aws-ecs component. This is enabled by default. | | Boolean
-| *camel.component.aws-ecs.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
-| *camel.component.aws-ecs.operation* | The operation to perform | | ECSOperations
-| *camel.component.aws-ecs.proxy-host* | To define a proxy host when instantiating the ECS client | | String
-| *camel.component.aws-ecs.proxy-port* | To define a proxy port when instantiating the ECS client | | Integer
-| *camel.component.aws-ecs.proxy-protocol* | To define a proxy protocol when instantiating the ECS client | | Protocol
-| *camel.component.aws-ecs.region* | The region in which ECS client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | | String
-| *camel.component.aws-ecs.secret-key* | Amazon AWS Secret Key | | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-aws-eks-starter/src/main/docs/aws-eks-starter.adoc b/components-starter/camel-aws-eks-starter/src/main/docs/aws-eks-starter.adoc
deleted file mode 100644
index df7b229..0000000
--- a/components-starter/camel-aws-eks-starter/src/main/docs/aws-eks-starter.adoc
+++ /dev/null
@@ -1,41 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for aws-eks
-
-== Spring Boot Auto-Configuration
-
-When using aws-eks with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-aws-eks-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 13 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.aws-eks.access-key* | Amazon AWS Access Key | | String
-| *camel.component.aws-eks.auto-discover-client* | Setting the autoDiscoverClient mechanism, if true, the component will look for a client instance in the registry automatically otherwise it will skip that checking. | true | Boolean
-| *camel.component.aws-eks.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.aws-eks.configuration* | The component configuration. The option is a org.apache.camel.component.aws.eks.EKSConfiguration type. | | EKSConfiguration
-| *camel.component.aws-eks.eks-client* | To use a existing configured AWS EKS as client. The option is a com.amazonaws.services.eks.AmazonEKS type. | | AmazonEKS
-| *camel.component.aws-eks.enabled* | Whether to enable auto configuration of the aws-eks component. This is enabled by default. | | Boolean
-| *camel.component.aws-eks.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
-| *camel.component.aws-eks.operation* | The operation to perform | | EKSOperations
-| *camel.component.aws-eks.proxy-host* | To define a proxy host when instantiating the EKS client | | String
-| *camel.component.aws-eks.proxy-port* | To define a proxy port when instantiating the EKS client | | Integer
-| *camel.component.aws-eks.proxy-protocol* | To define a proxy protocol when instantiating the EKS client | | Protocol
-| *camel.component.aws-eks.region* | The region in which EKS client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | | String
-| *camel.component.aws-eks.secret-key* | Amazon AWS Secret Key | | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-aws-iam-starter/src/main/docs/aws-iam-starter.adoc b/components-starter/camel-aws-iam-starter/src/main/docs/aws-iam-starter.adoc
deleted file mode 100644
index 49adf18..0000000
--- a/components-starter/camel-aws-iam-starter/src/main/docs/aws-iam-starter.adoc
+++ /dev/null
@@ -1,41 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for aws-iam
-
-== Spring Boot Auto-Configuration
-
-When using aws-iam with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-aws-iam-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 13 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.aws-iam.access-key* | Amazon AWS Access Key | | String
-| *camel.component.aws-iam.auto-discover-client* | Setting the autoDiscoverClient mechanism, if true, the component will look for a client instance in the registry automatically otherwise it will skip that checking. | true | Boolean
-| *camel.component.aws-iam.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.aws-iam.configuration* | The component configuration. The option is a org.apache.camel.component.aws.iam.IAMConfiguration type. | | IAMConfiguration
-| *camel.component.aws-iam.enabled* | Whether to enable auto configuration of the aws-iam component. This is enabled by default. | | Boolean
-| *camel.component.aws-iam.iam-client* | To use a existing configured AWS IAM as client. The option is a com.amazonaws.services.identitymanagement.AmazonIdentityManagement type. | | AmazonIdentityManagement
-| *camel.component.aws-iam.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
-| *camel.component.aws-iam.operation* | The operation to perform | | IAMOperations
-| *camel.component.aws-iam.proxy-host* | To define a proxy host when instantiating the IAM client | | String
-| *camel.component.aws-iam.proxy-port* | To define a proxy port when instantiating the IAM client | | Integer
-| *camel.component.aws-iam.proxy-protocol* | To define a proxy protocol when instantiating the IAM client | | Protocol
-| *camel.component.aws-iam.region* | The region in which IAM client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | | String
-| *camel.component.aws-iam.secret-key* | Amazon AWS Secret Key | | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-aws-kinesis-starter/src/main/docs/aws-kinesis-starter.adoc b/components-starter/camel-aws-kinesis-starter/src/main/docs/aws-kinesis-starter.adoc
deleted file mode 100644
index f9554f8..0000000
--- a/components-starter/camel-aws-kinesis-starter/src/main/docs/aws-kinesis-starter.adoc
+++ /dev/null
@@ -1,58 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for aws-kinesis
-
-== Spring Boot Auto-Configuration
-
-When using aws-kinesis with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-aws-kinesis-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 30 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.aws-kinesis-firehose.access-key* | Amazon AWS Access Key | | String
-| *camel.component.aws-kinesis-firehose.amazon-kinesis-firehose-client* | Amazon Kinesis Firehose client to use for all requests for this endpoint. The option is a com.amazonaws.services.kinesisfirehose.AmazonKinesisFirehose type. | | AmazonKinesisFirehose
-| *camel.component.aws-kinesis-firehose.auto-discover-client* | Setting the autoDiscoverClient mechanism, if true, the component will look for a client instance in the registry automatically otherwise it will skip that checking | true | Boolean
-| *camel.component.aws-kinesis-firehose.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.aws-kinesis-firehose.configuration* | The component configuration. The option is a org.apache.camel.component.aws.firehose.KinesisFirehoseConfiguration type. | | KinesisFirehoseConfiguration
-| *camel.component.aws-kinesis-firehose.enabled* | Whether to enable auto configuration of the aws-kinesis-firehose component. This is enabled by default. | | Boolean
-| *camel.component.aws-kinesis-firehose.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is [...]
-| *camel.component.aws-kinesis-firehose.proxy-host* | To define a proxy host when instantiating the Kinesis Firehose client | | String
-| *camel.component.aws-kinesis-firehose.proxy-port* | To define a proxy port when instantiating the Kinesis Firehose client | | Integer
-| *camel.component.aws-kinesis-firehose.proxy-protocol* | To define a proxy protocol when instantiating the Kinesis Firehose client | | Protocol
-| *camel.component.aws-kinesis-firehose.region* | The region in which Kinesis client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1)You'll need to use the name Regions.EU_WEST_1.name() | | String
-| *camel.component.aws-kinesis-firehose.secret-key* | Amazon AWS Secret Key | | String
-| *camel.component.aws-kinesis.access-key* | Amazon AWS Access Key | | String
-| *camel.component.aws-kinesis.amazon-kinesis-client* | Amazon Kinesis client to use for all requests for this endpoint. The option is a com.amazonaws.services.kinesis.AmazonKinesis type. | | AmazonKinesis
-| *camel.component.aws-kinesis.auto-discover-client* | Setting the autoDiscoverClient mechanism, if true, the component will look for a client instance in the registry automatically otherwise it will skip that checking | true | Boolean
-| *camel.component.aws-kinesis.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.aws-kinesis.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.aws-kinesis.configuration* | The component configuration. The option is a org.apache.camel.component.aws.kinesis.KinesisConfiguration type. | | KinesisConfiguration
-| *camel.component.aws-kinesis.enabled* | Whether to enable auto configuration of the aws-kinesis component. This is enabled by default. | | Boolean
-| *camel.component.aws-kinesis.iterator-type* | Defines where in the Kinesis stream to start getting records | | ShardIteratorType
-| *camel.component.aws-kinesis.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processe [...]
-| *camel.component.aws-kinesis.max-results-per-request* | Maximum number of records that will be fetched in each poll | 1 | Integer
-| *camel.component.aws-kinesis.proxy-host* | To define a proxy host when instantiating the Kinesis client | | String
-| *camel.component.aws-kinesis.proxy-port* | To define a proxy port when instantiating the Kinesis client | | Integer
-| *camel.component.aws-kinesis.proxy-protocol* | To define a proxy protocol when instantiating the Kinesis client | | Protocol
-| *camel.component.aws-kinesis.region* | The region in which Kinesis client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1)You'll need to use the name Regions.EU_WEST_1.name() | | String
-| *camel.component.aws-kinesis.secret-key* | Amazon AWS Secret Key | | String
-| *camel.component.aws-kinesis.sequence-number* | The sequence number to start polling from. Required if iteratorType is set to AFTER_SEQUENCE_NUMBER or AT_SEQUENCE_NUMBER | | String
-| *camel.component.aws-kinesis.shard-closed* | Define what will be the behavior in case of shard closed. Possible value are ignore, silent and fail. In case of ignore a message will be logged and the consumer will restart from the beginning,in case of silent there will be no logging and the consumer will start from the beginning,in case of fail a ReachedClosedStateException will be raised | | KinesisShardClosedStrategyEnum
-| *camel.component.aws-kinesis.shard-id* | Defines which shardId in the Kinesis stream to get records from | | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-aws-kms-starter/src/main/docs/aws-kms-starter.adoc b/components-starter/camel-aws-kms-starter/src/main/docs/aws-kms-starter.adoc
deleted file mode 100644
index c291bc9..0000000
--- a/components-starter/camel-aws-kms-starter/src/main/docs/aws-kms-starter.adoc
+++ /dev/null
@@ -1,41 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for aws-kms
-
-== Spring Boot Auto-Configuration
-
-When using aws-kms with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-aws-kms-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 13 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.aws-kms.access-key* | Amazon AWS Access Key | | String
-| *camel.component.aws-kms.auto-discover-client* | Setting the autoDiscoverClient mechanism, if true, the component will look for a client instance in the registry automatically otherwise it will skip that checking. | true | Boolean
-| *camel.component.aws-kms.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.aws-kms.configuration* | The Component configuration. The option is a org.apache.camel.component.aws.kms.KMSConfiguration type. | | KMSConfiguration
-| *camel.component.aws-kms.enabled* | Whether to enable auto configuration of the aws-kms component. This is enabled by default. | | Boolean
-| *camel.component.aws-kms.kms-client* | To use a existing configured AWS KMS as client. The option is a com.amazonaws.services.kms.AWSKMS type. | | AWSKMS
-| *camel.component.aws-kms.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
-| *camel.component.aws-kms.operation* | The operation to perform | | KMSOperations
-| *camel.component.aws-kms.proxy-host* | To define a proxy host when instantiating the KMS client | | String
-| *camel.component.aws-kms.proxy-port* | To define a proxy port when instantiating the KMS client | | Integer
-| *camel.component.aws-kms.proxy-protocol* | To define a proxy protocol when instantiating the KMS client | | Protocol
-| *camel.component.aws-kms.region* | The region in which KMS client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | | String
-| *camel.component.aws-kms.secret-key* | Amazon AWS Secret Key | | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-aws-lambda-starter/src/main/docs/aws-lambda-starter.adoc b/components-starter/camel-aws-lambda-starter/src/main/docs/aws-lambda-starter.adoc
deleted file mode 100644
index cba4aec..0000000
--- a/components-starter/camel-aws-lambda-starter/src/main/docs/aws-lambda-starter.adoc
+++ /dev/null
@@ -1,41 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for aws-lambda
-
-== Spring Boot Auto-Configuration
-
-When using aws-lambda with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-aws-lambda-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 13 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.aws-lambda.access-key* | Amazon AWS Access Key | | String
-| *camel.component.aws-lambda.auto-discover-client* | Setting the autoDiscoverClient mechanism, if true, the component will look for a client instance in the registry automatically otherwise it will skip that checking. | true | Boolean
-| *camel.component.aws-lambda.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.aws-lambda.aws-lambda-client* | To use a existing configured AwsLambdaClient as client. The option is a com.amazonaws.services.lambda.AWSLambda type. | | AWSLambda
-| *camel.component.aws-lambda.configuration* | The AWS Lambda default configuration. The option is a org.apache.camel.component.aws.lambda.LambdaConfiguration type. | | LambdaConfiguration
-| *camel.component.aws-lambda.enabled* | Whether to enable auto configuration of the aws-lambda component. This is enabled by default. | | Boolean
-| *camel.component.aws-lambda.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed [...]
-| *camel.component.aws-lambda.operation* | The operation to perform. It can be listFunctions, getFunction, createFunction, deleteFunction or invokeFunction | | LambdaOperations
-| *camel.component.aws-lambda.proxy-host* | To define a proxy host when instantiating the Lambda client | | String
-| *camel.component.aws-lambda.proxy-port* | To define a proxy port when instantiating the Lambda client | | Integer
-| *camel.component.aws-lambda.proxy-protocol* | To define a proxy protocol when instantiating the Lambda client | | Protocol
-| *camel.component.aws-lambda.region* | Amazon AWS Region. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | | String
-| *camel.component.aws-lambda.secret-key* | Amazon AWS Secret Key | | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-aws-mq-starter/src/main/docs/aws-mq-starter.adoc b/components-starter/camel-aws-mq-starter/src/main/docs/aws-mq-starter.adoc
deleted file mode 100644
index be4d917..0000000
--- a/components-starter/camel-aws-mq-starter/src/main/docs/aws-mq-starter.adoc
+++ /dev/null
@@ -1,41 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for aws-mq
-
-== Spring Boot Auto-Configuration
-
-When using aws-mq with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-aws-mq-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 13 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.aws-mq.access-key* | Amazon AWS Access Key | | String
-| *camel.component.aws-mq.amazon-mq-client* | To use a existing configured AmazonMQClient as client. The option is a com.amazonaws.services.mq.AmazonMQ type. | | AmazonMQ
-| *camel.component.aws-mq.auto-discover-client* | Setting the autoDiscoverClient mechanism, if true, the component will look for a client instance in the registry automatically otherwise it will skip that checking. | true | Boolean
-| *camel.component.aws-mq.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.aws-mq.configuration* | The Component configuration. The option is a org.apache.camel.component.aws.mq.MQConfiguration type. | | MQConfiguration
-| *camel.component.aws-mq.enabled* | Whether to enable auto configuration of the aws-mq component. This is enabled by default. | | Boolean
-| *camel.component.aws-mq.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed the [...]
-| *camel.component.aws-mq.operation* | The operation to perform. It can be listBrokers,createBroker,deleteBroker | | MQOperations
-| *camel.component.aws-mq.proxy-host* | To define a proxy host when instantiating the MQ client | | String
-| *camel.component.aws-mq.proxy-port* | To define a proxy port when instantiating the MQ client | | Integer
-| *camel.component.aws-mq.proxy-protocol* | To define a proxy protocol when instantiating the MQ client | | Protocol
-| *camel.component.aws-mq.region* | The region in which MQ client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | | String
-| *camel.component.aws-mq.secret-key* | Amazon AWS Secret Key | | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-aws-msk-starter/src/main/docs/aws-msk-starter.adoc b/components-starter/camel-aws-msk-starter/src/main/docs/aws-msk-starter.adoc
deleted file mode 100644
index 59b0648..0000000
--- a/components-starter/camel-aws-msk-starter/src/main/docs/aws-msk-starter.adoc
+++ /dev/null
@@ -1,41 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for aws-msk
-
-== Spring Boot Auto-Configuration
-
-When using aws-msk with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-aws-msk-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 13 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.aws-msk.access-key* | Amazon AWS Access Key | | String
-| *camel.component.aws-msk.auto-discover-client* | Setting the autoDiscoverClient mechanism, if true, the component will look for a client instance in the registry automatically otherwise it will skip that checking. | true | Boolean
-| *camel.component.aws-msk.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.aws-msk.configuration* | The component configuration. The option is a org.apache.camel.component.aws.msk.MSKConfiguration type. | | MSKConfiguration
-| *camel.component.aws-msk.enabled* | Whether to enable auto configuration of the aws-msk component. This is enabled by default. | | Boolean
-| *camel.component.aws-msk.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
-| *camel.component.aws-msk.msk-client* | To use a existing configured AWS MSK as client. The option is a com.amazonaws.services.kafka.AWSKafka type. | | AWSKafka
-| *camel.component.aws-msk.operation* | The operation to perform | | MSKOperations
-| *camel.component.aws-msk.proxy-host* | To define a proxy host when instantiating the MSK client | | String
-| *camel.component.aws-msk.proxy-port* | To define a proxy port when instantiating the MSK client | | Integer
-| *camel.component.aws-msk.proxy-protocol* | To define a proxy protocol when instantiating the MSK client | | Protocol
-| *camel.component.aws-msk.region* | The region in which MSK client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | | String
-| *camel.component.aws-msk.secret-key* | Amazon AWS Secret Key | | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-aws-s3-starter/src/main/docs/aws-s3-starter.adoc b/components-starter/camel-aws-s3-starter/src/main/docs/aws-s3-starter.adoc
deleted file mode 100644
index 0ad0ca3..0000000
--- a/components-starter/camel-aws-s3-starter/src/main/docs/aws-s3-starter.adoc
+++ /dev/null
@@ -1,68 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for aws-s3
-
-== Spring Boot Auto-Configuration
-
-When using aws-s3 with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-aws-s3-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 40 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.aws-s3.accelerate-mode-enabled* | Define if Accelerate Mode enabled is true or false | false | Boolean
-| *camel.component.aws-s3.access-key* | Amazon AWS Access Key | | String
-| *camel.component.aws-s3.amazon-s3-client* | Reference to a com.amazonaws.services.s3.AmazonS3 in the registry. The option is a com.amazonaws.services.s3.AmazonS3 type. | | AmazonS3
-| *camel.component.aws-s3.auto-create-bucket* | Setting the autocreation of the bucket | true | Boolean
-| *camel.component.aws-s3.auto-discover-client* | Setting the autoDiscoverClient mechanism, if true, the component will look for a client instance in the registry automatically otherwise it will skip that checking. | true | Boolean
-| *camel.component.aws-s3.autoclose-body* | If this option is true and includeBody is true, then the S3Object.close() method will be called on exchange completion. This option is strongly related to includeBody option. In case of setting includeBody to true and autocloseBody to false, it will be up to the caller to close the S3Object stream. Setting autocloseBody to true, will close the S3Object stream automatically. | true | Boolean
-| *camel.component.aws-s3.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.aws-s3.aws-k-m-s-key-id* | Define the id of KMS key to use in case KMS is enabled | | String
-| *camel.component.aws-s3.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.aws-s3.chunked-encoding-disabled* | Define if disabled Chunked Encoding is true or false | false | Boolean
-| *camel.component.aws-s3.configuration* | The component configuration. The option is a org.apache.camel.component.aws.s3.S3Configuration type. | | S3Configuration
-| *camel.component.aws-s3.delete-after-read* | Delete objects from S3 after they have been retrieved. The delete is only performed if the Exchange is committed. If a rollback occurs, the object is not deleted. If this option is false, then the same objects will be retrieve over and over again on the polls. Therefore you need to use the Idempotent Consumer EIP in the route to filter out duplicates. You can filter using the S3Constants#BUCKET_NAME and S3Constants#KEY headers, or only the S [...]
-| *camel.component.aws-s3.delete-after-write* | Delete file object after the S3 file has been uploaded | false | Boolean
-| *camel.component.aws-s3.delimiter* | The delimiter which is used in the com.amazonaws.services.s3.model.ListObjectsRequest to only consume objects we are interested in. | | String
-| *camel.component.aws-s3.dualstack-enabled* | Define if Dualstack enabled is true or false | false | Boolean
-| *camel.component.aws-s3.enabled* | Whether to enable auto configuration of the aws-s3 component. This is enabled by default. | | Boolean
-| *camel.component.aws-s3.encryption-materials* | The encryption materials to use in case of Symmetric/Asymmetric client usage. The option is a com.amazonaws.services.s3.model.EncryptionMaterials type. | | EncryptionMaterials
-| *camel.component.aws-s3.endpoint-configuration* | Amazon AWS Endpoint Configuration. The option is a com.amazonaws.client.builder.AwsClientBuilder.EndpointConfiguration type. | | AwsClientBuilder$EndpointConfiguration
-| *camel.component.aws-s3.file-name* | To get the object from the bucket with the given file name | | String
-| *camel.component.aws-s3.force-global-bucket-access-enabled* | Define if Force Global Bucket Access enabled is true or false | false | Boolean
-| *camel.component.aws-s3.include-body* | If it is true, the exchange body will be set to a stream to the contents of the file. If false, the headers will be set with the S3 object metadata, but the body will be null. This option is strongly related to autocloseBody option. In case of setting includeBody to true and autocloseBody to false, it will be up to the caller to close the S3Object stream. Setting autocloseBody to true, will close the S3Object stream automatically. | true | Boolean
-| *camel.component.aws-s3.key-name* | Setting the key name for an element in the bucket through endpoint parameter | | String
-| *camel.component.aws-s3.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed the [...]
-| *camel.component.aws-s3.multi-part-upload* | If it is true, camel will upload the file with multi part format, the part size is decided by the option of partSize | false | Boolean
-| *camel.component.aws-s3.operation* | The operation to do in case the user don't want to do only an upload | | S3Operations
-| *camel.component.aws-s3.part-size* | Setup the partSize which is used in multi part upload, the default size is 25M. | 26214400 | Long
-| *camel.component.aws-s3.path-style-access* | Whether or not the S3 client should use path style access | false | Boolean
-| *camel.component.aws-s3.payload-signing-enabled* | Define if Payload Signing enabled is true or false | false | Boolean
-| *camel.component.aws-s3.policy* | The policy for this queue to set in the com.amazonaws.services.s3.AmazonS3#setBucketPolicy() method. | | String
-| *camel.component.aws-s3.prefix* | The prefix which is used in the com.amazonaws.services.s3.model.ListObjectsRequest to only consume objects we are interested in. | | String
-| *camel.component.aws-s3.proxy-host* | To define a proxy host when instantiating the S3 client | | String
-| *camel.component.aws-s3.proxy-port* | Specify a proxy port to be used inside the client definition. | | Integer
-| *camel.component.aws-s3.proxy-protocol* | To define a proxy protocol when instantiating the S3 client | | Protocol
-| *camel.component.aws-s3.region* | The region in which S3 client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | | String
-| *camel.component.aws-s3.secret-key* | Amazon AWS Secret Key | | String
-| *camel.component.aws-s3.server-side-encryption* | Sets the server-side encryption algorithm when encrypting the object using AWS-managed keys. For example use AES256. | | String
-| *camel.component.aws-s3.storage-class* | The storage class to set in the com.amazonaws.services.s3.model.PutObjectRequest request. | | String
-| *camel.component.aws-s3.use-aws-k-m-s* | Define if KMS must be used or not | false | Boolean
-| *camel.component.aws-s3.use-encryption* | Define if encryption must be used or not | false | Boolean
-| *camel.component.aws-s3.use-i-a-m-credentials* | Set whether the S3 client should expect to load credentials on an EC2 instance or to expect static credentials to be passed in. | false | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-aws-sdb-starter/src/main/docs/aws-sdb-starter.adoc b/components-starter/camel-aws-sdb-starter/src/main/docs/aws-sdb-starter.adoc
deleted file mode 100644
index f669f04..0000000
--- a/components-starter/camel-aws-sdb-starter/src/main/docs/aws-sdb-starter.adoc
+++ /dev/null
@@ -1,31 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for aws-sdb
-
-== Spring Boot Auto-Configuration
-
-When using aws-sdb with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-aws-sdb-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 3 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.aws-sdb.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.aws-sdb.enabled* | Whether to enable auto configuration of the aws-sdb component. This is enabled by default. | | Boolean
-| *camel.component.aws-sdb.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-aws-ses-starter/src/main/docs/aws-ses-starter.adoc b/components-starter/camel-aws-ses-starter/src/main/docs/aws-ses-starter.adoc
deleted file mode 100644
index 41d4fa1..0000000
--- a/components-starter/camel-aws-ses-starter/src/main/docs/aws-ses-starter.adoc
+++ /dev/null
@@ -1,44 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for aws-ses
-
-== Spring Boot Auto-Configuration
-
-When using aws-ses with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-aws-ses-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 16 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.aws-ses.access-key* | Amazon AWS Access Key | | String
-| *camel.component.aws-ses.amazon-s-e-s-client* | To use the AmazonSimpleEmailService as the client. The option is a com.amazonaws.services.simpleemail.AmazonSimpleEmailService type. | | AmazonSimpleEmailService
-| *camel.component.aws-ses.auto-discover-client* | Setting the autoDiscoverClient mechanism, if true, the component will look for a client instance in the registry automatically otherwise it will skip that checking. | true | Boolean
-| *camel.component.aws-ses.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.aws-ses.configuration* | The component configuration. The option is a org.apache.camel.component.aws.ses.SesConfiguration type. | | SesConfiguration
-| *camel.component.aws-ses.enabled* | Whether to enable auto configuration of the aws-ses component. This is enabled by default. | | Boolean
-| *camel.component.aws-ses.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
-| *camel.component.aws-ses.proxy-host* | To define a proxy host when instantiating the SES client | | String
-| *camel.component.aws-ses.proxy-port* | To define a proxy port when instantiating the SES client | | Integer
-| *camel.component.aws-ses.proxy-protocol* | To define a proxy protocol when instantiating the SES client | | Protocol
-| *camel.component.aws-ses.region* | The region in which SES client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | | String
-| *camel.component.aws-ses.reply-to-addresses* | List of reply-to email address(es) for the message, override it using 'CamelAwsSesReplyToAddresses' header. | | List
-| *camel.component.aws-ses.return-path* | The email address to which bounce notifications are to be forwarded, override it using 'CamelAwsSesReturnPath' header. | | String
-| *camel.component.aws-ses.secret-key* | Amazon AWS Secret Key | | String
-| *camel.component.aws-ses.subject* | The subject which is used if the message header 'CamelAwsSesSubject' is not present. | | String
-| *camel.component.aws-ses.to* | List of destination email address. Can be overriden with 'CamelAwsSesTo' header. | | List
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-aws-sns-starter/src/main/docs/aws-sns-starter.adoc b/components-starter/camel-aws-sns-starter/src/main/docs/aws-sns-starter.adoc
deleted file mode 100644
index 6bdac46..0000000
--- a/components-starter/camel-aws-sns-starter/src/main/docs/aws-sns-starter.adoc
+++ /dev/null
@@ -1,49 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for aws-sns
-
-== Spring Boot Auto-Configuration
-
-When using aws-sns with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-aws-sns-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 21 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.aws-sns.access-key* | Amazon AWS Access Key | | String
-| *camel.component.aws-sns.amazon-s-n-s-client* | To use the AmazonSNS as the client. The option is a com.amazonaws.services.sns.AmazonSNS type. | | AmazonSNS
-| *camel.component.aws-sns.amazon-s-q-s-client* | An SQS Client to use as bridge between SNS and SQS. The option is a com.amazonaws.services.sqs.AmazonSQS type. | | AmazonSQS
-| *camel.component.aws-sns.auto-create-topic* | Setting the autocreation of the topic | true | Boolean
-| *camel.component.aws-sns.auto-discover-client* | Setting the autoDiscoverClient mechanism, if true, the component will look for a client instance in the registry automatically otherwise it will skip that checking. | true | Boolean
-| *camel.component.aws-sns.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.aws-sns.configuration* | The component configuration. The option is a org.apache.camel.component.aws.sns.SnsConfiguration type. | | SnsConfiguration
-| *camel.component.aws-sns.enabled* | Whether to enable auto configuration of the aws-sns component. This is enabled by default. | | Boolean
-| *camel.component.aws-sns.kms-master-key-id* | The ID of an AWS-managed customer master key (CMK) for Amazon SNS or a custom CMK. | | String
-| *camel.component.aws-sns.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
-| *camel.component.aws-sns.message-structure* | The message structure to use such as json | | String
-| *camel.component.aws-sns.policy* | The policy for this queue | | String
-| *camel.component.aws-sns.proxy-host* | To define a proxy host when instantiating the SNS client | | String
-| *camel.component.aws-sns.proxy-port* | To define a proxy port when instantiating the SNS client | | Integer
-| *camel.component.aws-sns.proxy-protocol* | To define a proxy protocol when instantiating the SNS client | | Protocol
-| *camel.component.aws-sns.queue-url* | The queueUrl to subscribe to | | String
-| *camel.component.aws-sns.region* | The region in which SNS client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | | String
-| *camel.component.aws-sns.secret-key* | Amazon AWS Secret Key | | String
-| *camel.component.aws-sns.server-side-encryption-enabled* | Define if Server Side Encryption is enabled or not on the topic | false | Boolean
-| *camel.component.aws-sns.subject* | The subject which is used if the message header 'CamelAwsSnsSubject' is not present. | | String
-| *camel.component.aws-sns.subscribe-s-n-sto-s-q-s* | Define if the subscription between SNS Topic and SQS must be done or not | false | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-aws-sqs-starter/src/main/docs/aws-sqs-starter.adoc b/components-starter/camel-aws-sqs-starter/src/main/docs/aws-sqs-starter.adoc
deleted file mode 100644
index f332ba4..0000000
--- a/components-starter/camel-aws-sqs-starter/src/main/docs/aws-sqs-starter.adoc
+++ /dev/null
@@ -1,68 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for aws-sqs
-
-== Spring Boot Auto-Configuration
-
-When using aws-sqs with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-aws-sqs-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 40 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.aws-sqs.access-key* | Amazon AWS Access Key | | String
-| *camel.component.aws-sqs.amazon-a-w-s-host* | The hostname of the Amazon AWS cloud. | amazonaws.com | String
-| *camel.component.aws-sqs.amazon-s-q-s-client* | To use the AmazonSQS as client. The option is a com.amazonaws.services.sqs.AmazonSQS type. | | AmazonSQS
-| *camel.component.aws-sqs.attribute-names* | A list of attribute names to receive when consuming. Multiple names can be separated by comma. | | String
-| *camel.component.aws-sqs.auto-create-queue* | Setting the autocreation of the queue | true | Boolean
-| *camel.component.aws-sqs.auto-discover-client* | Setting the autoDiscoverClient mechanism, if true, the component will look for a client instance in the registry automatically otherwise it will skip that checking. | true | Boolean
-| *camel.component.aws-sqs.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.aws-sqs.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.aws-sqs.concurrent-consumers* | Allows you to use multiple threads to poll the sqs queue to increase throughput | 1 | Integer
-| *camel.component.aws-sqs.configuration* | The component configuration. The option is a org.apache.camel.component.aws.sqs.SqsConfiguration type. | | SqsConfiguration
-| *camel.component.aws-sqs.default-visibility-timeout* | The default visibility timeout (in seconds) | | Integer
-| *camel.component.aws-sqs.delay-queue* | Define if you want to apply delaySeconds option to the queue or on single messages | false | Boolean
-| *camel.component.aws-sqs.delay-seconds* | Delay sending messages for a number of seconds. | | Integer
-| *camel.component.aws-sqs.delete-after-read* | Delete message from SQS after it has been read | true | Boolean
-| *camel.component.aws-sqs.delete-if-filtered* | Whether or not to send the DeleteMessage to the SQS queue if an exchange fails to get through a filter. If 'false' and exchange does not make it through a Camel filter upstream in the route, then don't send DeleteMessage. | true | Boolean
-| *camel.component.aws-sqs.enabled* | Whether to enable auto configuration of the aws-sqs component. This is enabled by default. | | Boolean
-| *camel.component.aws-sqs.extend-message-visibility* | If enabled then a scheduled background task will keep extending the message visibility on SQS. This is needed if it takes a long time to process the message. If set to true defaultVisibilityTimeout must be set. See details at Amazon docs. | false | Boolean
-| *camel.component.aws-sqs.kms-data-key-reuse-period-seconds* | The length of time, in seconds, for which Amazon SQS can reuse a data key to encrypt or decrypt messages before calling AWS KMS again. An integer representing seconds, between 60 seconds (1 minute) and 86,400 seconds (24 hours). Default: 300 (5 minutes). | | Integer
-| *camel.component.aws-sqs.kms-master-key-id* | The ID of an AWS-managed customer master key (CMK) for Amazon SQS or a custom CMK. | | String
-| *camel.component.aws-sqs.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
-| *camel.component.aws-sqs.maximum-message-size* | The maximumMessageSize (in bytes) an SQS message can contain for this queue. | | Integer
-| *camel.component.aws-sqs.message-attribute-names* | A list of message attribute names to receive when consuming. Multiple names can be separated by comma. | | String
-| *camel.component.aws-sqs.message-deduplication-id-strategy* | Only for FIFO queues. Strategy for setting the messageDeduplicationId on the message. Can be one of the following options: useExchangeId, useContentBasedDeduplication. For the useContentBasedDeduplication option, no messageDeduplicationId will be set on the message. | useExchangeId | String
-| *camel.component.aws-sqs.message-group-id-strategy* | Only for FIFO queues. Strategy for setting the messageGroupId on the message. Can be one of the following options: useConstant, useExchangeId, usePropertyValue. For the usePropertyValue option, the value of property CamelAwsMessageGroupId will be used. | | String
-| *camel.component.aws-sqs.message-retention-period* | The messageRetentionPeriod (in seconds) a message will be retained by SQS for this queue. | | Integer
-| *camel.component.aws-sqs.operation* | The operation to do in case the user don't want to send only a message | | SqsOperations
-| *camel.component.aws-sqs.policy* | The policy for this queue | | String
-| *camel.component.aws-sqs.protocol* | The underlying protocol used to communicate with SQS | https | String
-| *camel.component.aws-sqs.proxy-host* | To define a proxy host when instantiating the SQS client | | String
-| *camel.component.aws-sqs.proxy-port* | To define a proxy port when instantiating the SQS client | | Integer
-| *camel.component.aws-sqs.proxy-protocol* | To define a proxy protocol when instantiating the SQS client | | Protocol
-| *camel.component.aws-sqs.queue-owner-a-w-s-account-id* | Specify the queue owner aws account id when you need to connect the queue with different account owner. | | String
-| *camel.component.aws-sqs.queue-url* | To define the queueUrl explicitly. All other parameters, which would influence the queueUrl, are ignored. This parameter is intended to be used, to connect to a mock implementation of SQS, for testing purposes. | | String
-| *camel.component.aws-sqs.receive-message-wait-time-seconds* | If you do not specify WaitTimeSeconds in the request, the queue attribute ReceiveMessageWaitTimeSeconds is used to determine how long to wait. | | Integer
-| *camel.component.aws-sqs.redrive-policy* | Specify the policy that send message to DeadLetter queue. See detail at Amazon docs. | | String
-| *camel.component.aws-sqs.region* | Specify the queue region which could be used with queueOwnerAWSAccountId to build the service URL. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | | String
-| *camel.component.aws-sqs.secret-key* | Amazon AWS Secret Key | | String
-| *camel.component.aws-sqs.server-side-encryption-enabled* | Define if Server Side Encryption is enabled or not on the queue | false | Boolean
-| *camel.component.aws-sqs.visibility-timeout* | The duration (in seconds) that the received messages are hidden from subsequent retrieve requests after being retrieved by a ReceiveMessage request to set in the com.amazonaws.services.sqs.model.SetQueueAttributesRequest. This only make sense if its different from defaultVisibilityTimeout. It changes the queue visibility timeout attribute permanently. | | Integer
-| *camel.component.aws-sqs.wait-time-seconds* | Duration in seconds (0 to 20) that the ReceiveMessage action call will wait until a message is in the queue to include in the response. | | Integer
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-aws-swf-starter/src/main/docs/aws-swf-starter.adoc b/components-starter/camel-aws-swf-starter/src/main/docs/aws-swf-starter.adoc
deleted file mode 100644
index 5117a1b..0000000
--- a/components-starter/camel-aws-swf-starter/src/main/docs/aws-swf-starter.adoc
+++ /dev/null
@@ -1,59 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for aws-swf
-
-== Spring Boot Auto-Configuration
-
-When using aws-swf with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-aws-swf-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 31 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.aws-swf.access-key* | Amazon AWS Access Key. | | String
-| *camel.component.aws-swf.activity-list* | The list name to consume activities from. | | String
-| *camel.component.aws-swf.activity-scheduling-options* | Activity scheduling options. The option is a com.amazonaws.services.simpleworkflow.flow.ActivitySchedulingOptions type. | | ActivitySchedulingOptions
-| *camel.component.aws-swf.activity-thread-pool-size* | Maximum number of threads in work pool for activity. | 100 | Integer
-| *camel.component.aws-swf.activity-type-execution-options* | Activity execution options. The option is a com.amazonaws.services.simpleworkflow.flow.worker.ActivityTypeExecutionOptions type. | | ActivityTypeExecutionOptions
-| *camel.component.aws-swf.activity-type-registration-options* | Activity registration options. The option is a com.amazonaws.services.simpleworkflow.flow.worker.ActivityTypeRegistrationOptions type. | | ActivityTypeRegistrationOptions
-| *camel.component.aws-swf.amazon-s-w-client* | To use the given AmazonSimpleWorkflowClient as client. The option is a com.amazonaws.services.simpleworkflow.AmazonSimpleWorkflow type. | | AmazonSimpleWorkflow
-| *camel.component.aws-swf.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.aws-swf.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.aws-swf.child-policy* | The policy to use on child workflows when terminating a workflow. | | String
-| *camel.component.aws-swf.client-configuration-parameters* | To configure the ClientConfiguration using the key/values from the Map. | | Map
-| *camel.component.aws-swf.configuration* | The component configuration. The option is a org.apache.camel.component.aws.swf.SWFConfiguration type. | | SWFConfiguration
-| *camel.component.aws-swf.data-converter* | An instance of com.amazonaws.services.simpleworkflow.flow.DataConverter to use for serializing/deserializing the data. The option is a com.amazonaws.services.simpleworkflow.flow.DataConverter type. | | DataConverter
-| *camel.component.aws-swf.domain-name* | The workflow domain to use. | | String
-| *camel.component.aws-swf.enabled* | Whether to enable auto configuration of the aws-swf component. This is enabled by default. | | Boolean
-| *camel.component.aws-swf.event-name* | The workflow or activity event name to use. | | String
-| *camel.component.aws-swf.execution-start-to-close-timeout* | Set the execution start to close timeout. | 3600 | String
-| *camel.component.aws-swf.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
-| *camel.component.aws-swf.operation* | Workflow operation | START | String
-| *camel.component.aws-swf.region* | Amazon AWS Region. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | | String
-| *camel.component.aws-swf.s-w-client-parameters* | To configure the AmazonSimpleWorkflowClient using the key/values from the Map. | | Map
-| *camel.component.aws-swf.secret-key* | Amazon AWS Secret Key. | | String
-| *camel.component.aws-swf.signal-name* | The name of the signal to send to the workflow. | | String
-| *camel.component.aws-swf.start-workflow-options-parameters* | To configure the StartWorkflowOptions using the key/values from the Map. | | Map
-| *camel.component.aws-swf.state-result-type* | The type of the result when a workflow state is queried. | | String
-| *camel.component.aws-swf.task-start-to-close-timeout* | Set the task start to close timeout. | 600 | String
-| *camel.component.aws-swf.termination-details* | Details for terminating a workflow. | | String
-| *camel.component.aws-swf.termination-reason* | The reason for terminating a workflow. | | String
-| *camel.component.aws-swf.version* | The workflow or activity event version to use. | | String
-| *camel.component.aws-swf.workflow-list* | The list name to consume workflows from. | | String
-| *camel.component.aws-swf.workflow-type-registration-options* | Workflow registration options. The option is a com.amazonaws.services.simpleworkflow.flow.WorkflowTypeRegistrationOptions type. | | WorkflowTypeRegistrationOptions
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-aws-translate-starter/src/main/docs/aws-translate-starter.adoc b/components-starter/camel-aws-translate-starter/src/main/docs/aws-translate-starter.adoc
deleted file mode 100644
index 8effc77..0000000
--- a/components-starter/camel-aws-translate-starter/src/main/docs/aws-translate-starter.adoc
+++ /dev/null
@@ -1,44 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for aws-translate
-
-== Spring Boot Auto-Configuration
-
-When using aws-translate with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-aws-translate-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 16 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.aws-translate.access-key* | Amazon AWS Access Key | | String
-| *camel.component.aws-translate.auto-discover-client* | Setting the autoDiscoverClient mechanism, if true, the component will look for a client instance in the registry automatically otherwise it will skip that checking. | true | Boolean
-| *camel.component.aws-translate.autodetect-source-language* | Being able to autodetect the source language | false | Boolean
-| *camel.component.aws-translate.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.aws-translate.configuration* | The component configuration. The option is a org.apache.camel.component.aws.translate.TranslateConfiguration type. | | TranslateConfiguration
-| *camel.component.aws-translate.enabled* | Whether to enable auto configuration of the aws-translate component. This is enabled by default. | | Boolean
-| *camel.component.aws-translate.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proces [...]
-| *camel.component.aws-translate.operation* | The operation to perform | | TranslateOperations
-| *camel.component.aws-translate.proxy-host* | To define a proxy host when instantiating the Translate client | | String
-| *camel.component.aws-translate.proxy-port* | To define a proxy port when instantiating the Translate client | | Integer
-| *camel.component.aws-translate.proxy-protocol* | To define a proxy protocol when instantiating the Translate client | | Protocol
-| *camel.component.aws-translate.region* | The region in which Translate client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | | String
-| *camel.component.aws-translate.secret-key* | Amazon AWS Secret Key | | String
-| *camel.component.aws-translate.source-language* | Source language to use | | String
-| *camel.component.aws-translate.target-language* | Target language to use | | String
-| *camel.component.aws-translate.translate-client* | To use a existing configured AWS Translate as client. The option is a com.amazonaws.services.translate.AmazonTranslate type. | | AmazonTranslate
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-aws2-athena-starter/src/main/docs/aws2-athena-starter.adoc b/components-starter/camel-aws2-athena-starter/src/main/docs/aws2-athena-starter.adoc
deleted file mode 100644
index edfa977..0000000
--- a/components-starter/camel-aws2-athena-starter/src/main/docs/aws2-athena-starter.adoc
+++ /dev/null
@@ -1,58 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for aws2-athena
-
-== Spring Boot Auto-Configuration
-
-When using aws2-athena with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-aws2-athena-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 30 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.aws2-athena.access-key* | Amazon AWS Access Key. | | String
-| *camel.component.aws2-athena.amazon-athena-client* | The AmazonAthena instance to use as the client. The option is a software.amazon.awssdk.services.athena.AthenaClient type. | | AthenaClient
-| *camel.component.aws2-athena.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.aws2-athena.client-request-token* | A unique string to ensure issues queries are idempotent. It is unlikely you will need to set this. | | String
-| *camel.component.aws2-athena.configuration* | The component configuration. The option is a org.apache.camel.component.aws2.athena.Athena2Configuration type. | | Athena2Configuration
-| *camel.component.aws2-athena.database* | The Athena database to use. | | String
-| *camel.component.aws2-athena.delay* | Milliseconds before the next poll for query execution status. See the section 'Waiting for Query Completion and Retrying Failed Queries' to learn more. | 2000 | Long
-| *camel.component.aws2-athena.enabled* | Whether to enable auto configuration of the aws2-athena component. This is enabled by default. | | Boolean
-| *camel.component.aws2-athena.encryption-option* | The encryption type to use when storing query results in S3. One of SSE_S3, SSE_KMS, or CSE_KMS. | | EncryptionOption
-| *camel.component.aws2-athena.include-trace* | Include useful trace information at the beginning of queries as an SQL comment (prefixed with --). | false | Boolean
-| *camel.component.aws2-athena.initial-delay* | Milliseconds before the first poll for query execution status. See the section 'Waiting for Query Completion and Retrying Failed Queries' to learn more. | 1000 | Long
-| *camel.component.aws2-athena.kms-key* | For SSE-KMS and CSE-KMS, this is the KMS key ARN or ID. | | String
-| *camel.component.aws2-athena.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processe [...]
-| *camel.component.aws2-athena.max-attempts* | Maximum number of times to attempt a query. Set to 1 to disable retries. See the section 'Waiting for Query Completion and Retrying Failed Queries' to learn more. | 1 | Integer
-| *camel.component.aws2-athena.max-results* | Max number of results to return for the given operation (if supported by the Athena API endpoint). If not set, will use the Athena API default for the given operation. | | Integer
-| *camel.component.aws2-athena.next-token* | Pagination token to use in the case where the response from the previous request was truncated. | | String
-| *camel.component.aws2-athena.operation* | The Athena API function to call. | | Athena2Operations
-| *camel.component.aws2-athena.output-location* | The location in Amazon S3 where query results are stored, such as s3://path/to/query/bucket/. Ensure this value ends with a forward slash ('/'). | | String
-| *camel.component.aws2-athena.output-type* | How query results should be returned. One of StreamList (default - return a GetQueryResultsIterable that can page through all results), SelectList (returns at most 1,000 rows at a time, plus a NextToken value as a header than can be used for manual pagination of results), S3Pointer (return an S3 path pointing to the results). | | Athena2OutputType
-| *camel.component.aws2-athena.proxy-host* | To define a proxy host when instantiating the Athena client. | | String
-| *camel.component.aws2-athena.proxy-port* | To define a proxy port when instantiating the Athena client. | | Integer
-| *camel.component.aws2-athena.proxy-protocol* | To define a proxy protocol when instantiating the Athena client. | | Protocol
-| *camel.component.aws2-athena.query-execution-id* | The unique ID identifying the query execution. | | String
-| *camel.component.aws2-athena.query-string* | The SQL query to run. Except for simple queries, prefer setting this as the body of the Exchange or as a header using Athena2Constants.QUERY_STRING to avoid having to deal with URL encoding issues. | | String
-| *camel.component.aws2-athena.region* | The region in which Athena client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1). You'll need to use the name Region.EU_WEST_1.id(). | | String
-| *camel.component.aws2-athena.reset-wait-timeout-on-retry* | Reset the waitTimeout countdown in the event of a query retry. If set to true, potential max time spent waiting for queries is equal to waitTimeout x maxAttempts. See the section 'Waiting for Query Completion and Retrying Failed Queries' to learn more. | true | Boolean
-| *camel.component.aws2-athena.retry* | Optional comma separated list of error types to retry the query for. Use 'retryable' to retry all retryable failure conditions (e.g. generic errors and resources exhausted), 'generic' to retry 'GENERIC_INTERNAL_ERROR' failures, 'exhausted' to retry queries that have exhausted resource limits, 'always' to always retry regardless of failure condition, or 'never' or null to never retry (default). See the section 'Waiting for Query Completion and Retry [...]
-| *camel.component.aws2-athena.secret-key* | Amazon AWS Secret Key. | | String
-| *camel.component.aws2-athena.wait-timeout* | Optional max wait time in millis to wait for a successful query completion. See the section 'Waiting for Query Completion and Retrying Failed Queries' to learn more. | 0 | Long
-| *camel.component.aws2-athena.work-group* | The workgroup to use for running the query. | | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-aws2-cw-starter/src/main/docs/aws2-cw-starter.adoc b/components-starter/camel-aws2-cw-starter/src/main/docs/aws2-cw-starter.adoc
deleted file mode 100644
index 3499f09..0000000
--- a/components-starter/camel-aws2-cw-starter/src/main/docs/aws2-cw-starter.adoc
+++ /dev/null
@@ -1,44 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for aws2-cw
-
-== Spring Boot Auto-Configuration
-
-When using aws2-cw with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-aws2-cw-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 16 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.aws2-cw.access-key* | Amazon AWS Access Key | | String
-| *camel.component.aws2-cw.amazon-cw-client* | To use the AmazonCloudWatch as the client. The option is a software.amazon.awssdk.services.cloudwatch.CloudWatchClient type. | | CloudWatchClient
-| *camel.component.aws2-cw.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.aws2-cw.configuration* | The component configuration. The option is a org.apache.camel.component.aws2.cw.Cw2Configuration type. | | Cw2Configuration
-| *camel.component.aws2-cw.enabled* | Whether to enable auto configuration of the aws2-cw component. This is enabled by default. | | Boolean
-| *camel.component.aws2-cw.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
-| *camel.component.aws2-cw.name* | The metric name | | String
-| *camel.component.aws2-cw.proxy-host* | To define a proxy host when instantiating the CW client | | String
-| *camel.component.aws2-cw.proxy-port* | To define a proxy port when instantiating the CW client | | Integer
-| *camel.component.aws2-cw.proxy-protocol* | To define a proxy protocol when instantiating the CW client | | Protocol
-| *camel.component.aws2-cw.region* | The region in which EKS client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | | String
-| *camel.component.aws2-cw.secret-key* | Amazon AWS Secret Key | | String
-| *camel.component.aws2-cw.timestamp* | The metric timestamp. The option is a java.time.Instant type. | | Instant
-| *camel.component.aws2-cw.trust-all-certificates* | If we want to trust all certificates in case of overriding the endpoint | false | Boolean
-| *camel.component.aws2-cw.unit* | The metric unit | | String
-| *camel.component.aws2-cw.value* | The metric value | | Double
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-aws2-ddb-starter/src/main/docs/aws2-ddb-starter.adoc b/components-starter/camel-aws2-ddb-starter/src/main/docs/aws2-ddb-starter.adoc
deleted file mode 100644
index 1ba1782..0000000
--- a/components-starter/camel-aws2-ddb-starter/src/main/docs/aws2-ddb-starter.adoc
+++ /dev/null
@@ -1,61 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for aws2-ddb
-
-== Spring Boot Auto-Configuration
-
-When using aws2-ddb with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-aws2-ddb-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 33 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.aws2-ddb.access-key* | Amazon AWS Access Key | | String
-| *camel.component.aws2-ddb.amazon-d-d-b-client* | To use the AmazonDynamoDB as the client. The option is a software.amazon.awssdk.services.dynamodb.DynamoDbClient type. | | DynamoDbClient
-| *camel.component.aws2-ddb.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.aws2-ddb.configuration* | The component configuration. The option is a org.apache.camel.component.aws2.ddb.Ddb2Configuration type. | | Ddb2Configuration
-| *camel.component.aws2-ddb.consistent-read* | Determines whether or not strong consistency should be enforced when data is read. | false | Boolean
-| *camel.component.aws2-ddb.enabled* | Whether to enable auto configuration of the aws2-ddb component. This is enabled by default. | | Boolean
-| *camel.component.aws2-ddb.key-attribute-name* | Attribute name when creating table | | String
-| *camel.component.aws2-ddb.key-attribute-type* | Attribute type when creating table | | String
-| *camel.component.aws2-ddb.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed t [...]
-| *camel.component.aws2-ddb.operation* | What operation to perform | | Ddb2Operations
-| *camel.component.aws2-ddb.proxy-host* | To define a proxy host when instantiating the DDB client | | String
-| *camel.component.aws2-ddb.proxy-port* | The region in which DynamoDB client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | | Integer
-| *camel.component.aws2-ddb.proxy-protocol* | To define a proxy protocol when instantiating the DDB client | | Protocol
-| *camel.component.aws2-ddb.read-capacity* | The provisioned throughput to reserve for reading resources from your table | | Long
-| *camel.component.aws2-ddb.region* | The region in which DDB client needs to work | | String
-| *camel.component.aws2-ddb.secret-key* | Amazon AWS Secret Key | | String
-| *camel.component.aws2-ddb.trust-all-certificates* | If we want to trust all certificates in case of overriding the endpoint | false | Boolean
-| *camel.component.aws2-ddb.write-capacity* | The provisioned throughput to reserved for writing resources to your table | | Long
-| *camel.component.aws2-ddbstream.access-key* | Amazon AWS Access Key | | String
-| *camel.component.aws2-ddbstream.amazon-dynamo-db-streams-client* | Amazon DynamoDB client to use for all requests for this endpoint. The option is a software.amazon.awssdk.services.dynamodb.streams.DynamoDbStreamsClient type. | | DynamoDbStreamsClient
-| *camel.component.aws2-ddbstream.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.aws2-ddbstream.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.aws2-ddbstream.configuration* | The component configuration. The option is a org.apache.camel.component.aws2.ddbstream.Ddb2StreamConfiguration type. | | Ddb2StreamConfiguration
-| *camel.component.aws2-ddbstream.enabled* | Whether to enable auto configuration of the aws2-ddbstream component. This is enabled by default. | | Boolean
-| *camel.component.aws2-ddbstream.iterator-type* | Defines where in the DynaboDB stream to start getting records. Note that using TRIM_HORIZON can cause a significant delay before the stream has caught up to real-time. if {AT,AFTER}_SEQUENCE_NUMBER are used, then a sequenceNumberProvider MUST be supplied. | | ShardIteratorType
-| *camel.component.aws2-ddbstream.max-results-per-request* | Maximum number of records that will be fetched in each poll | | Integer
-| *camel.component.aws2-ddbstream.proxy-host* | To define a proxy host when instantiating the DDBStreams client | | String
-| *camel.component.aws2-ddbstream.proxy-port* | To define a proxy port when instantiating the DDBStreams client | | Integer
-| *camel.component.aws2-ddbstream.proxy-protocol* | To define a proxy protocol when instantiating the DDBStreams client | | Protocol
-| *camel.component.aws2-ddbstream.region* | The region in which DDBStreams client needs to work | | String
-| *camel.component.aws2-ddbstream.secret-key* | Amazon AWS Secret Key | | String
-| *camel.component.aws2-ddbstream.sequence-number-provider* | Provider for the sequence number when using one of the two ShardIteratorType.{AT,AFTER}_SEQUENCE_NUMBER iterator types. Can be a registry reference or a literal sequence number. The option is a org.apache.camel.component.aws2.ddbstream.SequenceNumberProvider type. | | SequenceNumberProvider
-| *camel.component.aws2-ddbstream.trust-all-certificates* | If we want to trust all certificates in case of overriding the endpoint | false | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-aws2-ec2-starter/src/main/docs/aws2-ec2-starter.adoc b/components-starter/camel-aws2-ec2-starter/src/main/docs/aws2-ec2-starter.adoc
deleted file mode 100644
index 91ed2ce..0000000
--- a/components-starter/camel-aws2-ec2-starter/src/main/docs/aws2-ec2-starter.adoc
+++ /dev/null
@@ -1,42 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for aws2-ec2
-
-== Spring Boot Auto-Configuration
-
-When using aws2-ec2 with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-aws2-ec2-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 14 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.aws2-ec2.access-key* | Amazon AWS Access Key | | String
-| *camel.component.aws2-ec2.amazon-ec2-client* | To use a existing configured AmazonEC2Client as client. The option is a software.amazon.awssdk.services.ec2.Ec2Client type. | | Ec2Client
-| *camel.component.aws2-ec2.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.aws2-ec2.configuration* | The component configuration. The option is a org.apache.camel.component.aws2.ec2.AWS2EC2Configuration type. | | AWS2EC2Configuration
-| *camel.component.aws2-ec2.enabled* | Whether to enable auto configuration of the aws2-ec2 component. This is enabled by default. | | Boolean
-| *camel.component.aws2-ec2.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed t [...]
-| *camel.component.aws2-ec2.operation* | The operation to perform. It can be createAndRunInstances, startInstances, stopInstances, terminateInstances, describeInstances, describeInstancesStatus, rebootInstances, monitorInstances, unmonitorInstances, createTags or deleteTags | | AWS2EC2Operations
-| *camel.component.aws2-ec2.pojo-request* | If we want to use a POJO request as body or not | false | Boolean
-| *camel.component.aws2-ec2.proxy-host* | To define a proxy host when instantiating the EC2 client | | String
-| *camel.component.aws2-ec2.proxy-port* | To define a proxy port when instantiating the EC2 client | | Integer
-| *camel.component.aws2-ec2.proxy-protocol* | To define a proxy protocol when instantiating the EC2 client | | Protocol
-| *camel.component.aws2-ec2.region* | The region in which EC2 client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | | String
-| *camel.component.aws2-ec2.secret-key* | Amazon AWS Secret Key | | String
-| *camel.component.aws2-ec2.trust-all-certificates* | If we want to trust all certificates in case of overriding the endpoint | false | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-aws2-ecs-starter/src/main/docs/aws2-ecs-starter.adoc b/components-starter/camel-aws2-ecs-starter/src/main/docs/aws2-ecs-starter.adoc
deleted file mode 100644
index f24c071..0000000
--- a/components-starter/camel-aws2-ecs-starter/src/main/docs/aws2-ecs-starter.adoc
+++ /dev/null
@@ -1,42 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for aws2-ecs
-
-== Spring Boot Auto-Configuration
-
-When using aws2-ecs with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-aws2-ecs-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 14 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.aws2-ecs.access-key* | Amazon AWS Access Key | | String
-| *camel.component.aws2-ecs.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.aws2-ecs.configuration* | Component configuration. The option is a org.apache.camel.component.aws2.ecs.ECS2Configuration type. | | ECS2Configuration
-| *camel.component.aws2-ecs.ecs-client* | To use a existing configured AWS ECS as client. The option is a software.amazon.awssdk.services.ecs.EcsClient type. | | EcsClient
-| *camel.component.aws2-ecs.enabled* | Whether to enable auto configuration of the aws2-ecs component. This is enabled by default. | | Boolean
-| *camel.component.aws2-ecs.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed t [...]
-| *camel.component.aws2-ecs.operation* | The operation to perform | | ECS2Operations
-| *camel.component.aws2-ecs.pojo-request* | If we want to use a POJO request as body or not | false | Boolean
-| *camel.component.aws2-ecs.proxy-host* | To define a proxy host when instantiating the ECS client | | String
-| *camel.component.aws2-ecs.proxy-port* | To define a proxy port when instantiating the ECS client | | Integer
-| *camel.component.aws2-ecs.proxy-protocol* | To define a proxy protocol when instantiating the ECS client | | Protocol
-| *camel.component.aws2-ecs.region* | The region in which ECS client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | | String
-| *camel.component.aws2-ecs.secret-key* | Amazon AWS Secret Key | | String
-| *camel.component.aws2-ecs.trust-all-certificates* | If we want to trust all certificates in case of overriding the endpoint | false | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-aws2-eks-starter/src/main/docs/aws2-eks-starter.adoc b/components-starter/camel-aws2-eks-starter/src/main/docs/aws2-eks-starter.adoc
deleted file mode 100644
index 70e8be4..0000000
--- a/components-starter/camel-aws2-eks-starter/src/main/docs/aws2-eks-starter.adoc
+++ /dev/null
@@ -1,42 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for aws2-eks
-
-== Spring Boot Auto-Configuration
-
-When using aws2-eks with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-aws2-eks-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 14 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.aws2-eks.access-key* | Amazon AWS Access Key | | String
-| *camel.component.aws2-eks.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.aws2-eks.configuration* | Component configuration. The option is a org.apache.camel.component.aws2.eks.EKS2Configuration type. | | EKS2Configuration
-| *camel.component.aws2-eks.eks-client* | To use a existing configured AWS EKS as client. The option is a software.amazon.awssdk.services.eks.EksClient type. | | EksClient
-| *camel.component.aws2-eks.enabled* | Whether to enable auto configuration of the aws2-eks component. This is enabled by default. | | Boolean
-| *camel.component.aws2-eks.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed t [...]
-| *camel.component.aws2-eks.operation* | The operation to perform | | EKS2Operations
-| *camel.component.aws2-eks.pojo-request* | If we want to use a POJO request as body or not | false | Boolean
-| *camel.component.aws2-eks.proxy-host* | To define a proxy host when instantiating the EKS client | | String
-| *camel.component.aws2-eks.proxy-port* | To define a proxy port when instantiating the EKS client | | Integer
-| *camel.component.aws2-eks.proxy-protocol* | To define a proxy protocol when instantiating the EKS client | | Protocol
-| *camel.component.aws2-eks.region* | The region in which EKS client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | | String
-| *camel.component.aws2-eks.secret-key* | Amazon AWS Secret Key | | String
-| *camel.component.aws2-eks.trust-all-certificates* | If we want to trust all certificates in case of overriding the endpoint | false | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-aws2-eventbridge-starter/src/main/docs/aws2-eventbridge-starter.adoc b/components-starter/camel-aws2-eventbridge-starter/src/main/docs/aws2-eventbridge-starter.adoc
deleted file mode 100644
index d0c909b..0000000
--- a/components-starter/camel-aws2-eventbridge-starter/src/main/docs/aws2-eventbridge-starter.adoc
+++ /dev/null
@@ -1,43 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for aws2-eventbridge
-
-== Spring Boot Auto-Configuration
-
-When using aws2-eventbridge with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-aws2-eventbridge-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 15 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.aws2-eventbridge.access-key* | Amazon AWS Access Key | | String
-| *camel.component.aws2-eventbridge.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.aws2-eventbridge.configuration* | Component configuration. The option is a org.apache.camel.component.aws2.eventbridge.EventbridgeConfiguration type. | | EventbridgeConfiguration
-| *camel.component.aws2-eventbridge.enabled* | Whether to enable auto configuration of the aws2-eventbridge component. This is enabled by default. | | Boolean
-| *camel.component.aws2-eventbridge.event-pattern-file* | EventPattern File | | String
-| *camel.component.aws2-eventbridge.eventbridge-client* | To use a existing configured AWS Eventbridge as client. The option is a software.amazon.awssdk.services.eventbridge.EventBridgeClient type. | | EventBridgeClient
-| *camel.component.aws2-eventbridge.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is pro [...]
-| *camel.component.aws2-eventbridge.operation* | The operation to perform | | EventbridgeOperations
-| *camel.component.aws2-eventbridge.pojo-request* | If we want to use a POJO request as body or not | false | Boolean
-| *camel.component.aws2-eventbridge.proxy-host* | To define a proxy host when instantiating the Eventbridge client | | String
-| *camel.component.aws2-eventbridge.proxy-port* | To define a proxy port when instantiating the Eventbridge client | | Integer
-| *camel.component.aws2-eventbridge.proxy-protocol* | To define a proxy protocol when instantiating the Eventbridge client | | Protocol
-| *camel.component.aws2-eventbridge.region* | The region in which Eventbridge client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | | String
-| *camel.component.aws2-eventbridge.secret-key* | Amazon AWS Secret Key | | String
-| *camel.component.aws2-eventbridge.trust-all-certificates* | If we want to trust all certificates in case of overriding the endpoint | false | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-aws2-iam-starter/src/main/docs/aws2-iam-starter.adoc b/components-starter/camel-aws2-iam-starter/src/main/docs/aws2-iam-starter.adoc
deleted file mode 100644
index 5d7d02e..0000000
--- a/components-starter/camel-aws2-iam-starter/src/main/docs/aws2-iam-starter.adoc
+++ /dev/null
@@ -1,42 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for aws2-iam
-
-== Spring Boot Auto-Configuration
-
-When using aws2-iam with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-aws2-iam-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 14 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.aws2-iam.access-key* | Amazon AWS Access Key | | String
-| *camel.component.aws2-iam.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.aws2-iam.configuration* | Component configuration. The option is a org.apache.camel.component.aws2.iam.IAM2Configuration type. | | IAM2Configuration
-| *camel.component.aws2-iam.enabled* | Whether to enable auto configuration of the aws2-iam component. This is enabled by default. | | Boolean
-| *camel.component.aws2-iam.iam-client* | To use a existing configured AWS IAM as client. The option is a software.amazon.awssdk.services.iam.IamClient type. | | IamClient
-| *camel.component.aws2-iam.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed t [...]
-| *camel.component.aws2-iam.operation* | The operation to perform. You can configure a default operation on the component level, or the operation as part of the endpoint, or via a message header with the key CamelAwsIAMOperation. | | IAM2Operations
-| *camel.component.aws2-iam.pojo-request* | If we want to use a POJO request as body or not | false | Boolean
-| *camel.component.aws2-iam.proxy-host* | To define a proxy host when instantiating the IAM client | | String
-| *camel.component.aws2-iam.proxy-port* | To define a proxy port when instantiating the IAM client | | Integer
-| *camel.component.aws2-iam.proxy-protocol* | To define a proxy protocol when instantiating the IAM client | | Protocol
-| *camel.component.aws2-iam.region* | The region in which IAM client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | aws-global | String
-| *camel.component.aws2-iam.secret-key* | Amazon AWS Secret Key | | String
-| *camel.component.aws2-iam.trust-all-certificates* | If we want to trust all certificates in case of overriding the endpoint | false | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-aws2-kinesis-starter/src/main/docs/aws2-kinesis-starter.adoc b/components-starter/camel-aws2-kinesis-starter/src/main/docs/aws2-kinesis-starter.adoc
deleted file mode 100644
index a8720fe..0000000
--- a/components-starter/camel-aws2-kinesis-starter/src/main/docs/aws2-kinesis-starter.adoc
+++ /dev/null
@@ -1,61 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for aws2-kinesis
-
-== Spring Boot Auto-Configuration
-
-When using aws2-kinesis with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-aws2-kinesis-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 33 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.aws2-kinesis-firehose.access-key* | Amazon AWS Access Key | | String
-| *camel.component.aws2-kinesis-firehose.amazon-kinesis-firehose-client* | Amazon Kinesis Firehose client to use for all requests for this endpoint. The option is a software.amazon.awssdk.services.firehose.FirehoseClient type. | | FirehoseClient
-| *camel.component.aws2-kinesis-firehose.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.aws2-kinesis-firehose.cbor-enabled* | This option will set the CBOR_ENABLED property during the execution | true | Boolean
-| *camel.component.aws2-kinesis-firehose.configuration* | Component configuration. The option is a org.apache.camel.component.aws2.firehose.KinesisFirehose2Configuration type. | | KinesisFirehose2Configuration
-| *camel.component.aws2-kinesis-firehose.enabled* | Whether to enable auto configuration of the aws2-kinesis-firehose component. This is enabled by default. | | Boolean
-| *camel.component.aws2-kinesis-firehose.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message i [...]
-| *camel.component.aws2-kinesis-firehose.operation* | The operation to do in case the user don't want to send only a record | | KinesisFirehose2Operations
-| *camel.component.aws2-kinesis-firehose.proxy-host* | To define a proxy host when instantiating the Kinesis Firehose client | | String
-| *camel.component.aws2-kinesis-firehose.proxy-port* | To define a proxy port when instantiating the Kinesis Firehose client | | Integer
-| *camel.component.aws2-kinesis-firehose.proxy-protocol* | To define a proxy protocol when instantiating the Kinesis Firehose client | | Protocol
-| *camel.component.aws2-kinesis-firehose.region* | The region in which Kinesis Firehose client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | | String
-| *camel.component.aws2-kinesis-firehose.secret-key* | Amazon AWS Secret Key | | String
-| *camel.component.aws2-kinesis-firehose.trust-all-certificates* | If we want to trust all certificates in case of overriding the endpoint | false | Boolean
-| *camel.component.aws2-kinesis.access-key* | Amazon AWS Access Key | | String
-| *camel.component.aws2-kinesis.amazon-kinesis-client* | Amazon Kinesis client to use for all requests for this endpoint. The option is a software.amazon.awssdk.services.kinesis.KinesisClient type. | | KinesisClient
-| *camel.component.aws2-kinesis.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.aws2-kinesis.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.aws2-kinesis.cbor-enabled* | This option will set the CBOR_ENABLED property during the execution | true | Boolean
-| *camel.component.aws2-kinesis.configuration* | Component configuration. The option is a org.apache.camel.component.aws2.kinesis.Kinesis2Configuration type. | | Kinesis2Configuration
-| *camel.component.aws2-kinesis.enabled* | Whether to enable auto configuration of the aws2-kinesis component. This is enabled by default. | | Boolean
-| *camel.component.aws2-kinesis.iterator-type* | Defines where in the Kinesis stream to start getting records | | ShardIteratorType
-| *camel.component.aws2-kinesis.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is process [...]
-| *camel.component.aws2-kinesis.max-results-per-request* | Maximum number of records that will be fetched in each poll | 1 | Integer
-| *camel.component.aws2-kinesis.proxy-host* | To define a proxy host when instantiating the Kinesis client | | String
-| *camel.component.aws2-kinesis.proxy-port* | To define a proxy port when instantiating the Kinesis client | | Integer
-| *camel.component.aws2-kinesis.proxy-protocol* | To define a proxy protocol when instantiating the Kinesis client | | Protocol
-| *camel.component.aws2-kinesis.region* | The region in which Kinesis Firehose client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | | String
-| *camel.component.aws2-kinesis.secret-key* | Amazon AWS Secret Key | | String
-| *camel.component.aws2-kinesis.sequence-number* | The sequence number to start polling from. Required if iteratorType is set to AFTER_SEQUENCE_NUMBER or AT_SEQUENCE_NUMBER | | String
-| *camel.component.aws2-kinesis.shard-closed* | Define what will be the behavior in case of shard closed. Possible value are ignore, silent and fail. In case of ignore a message will be logged and the consumer will restart from the beginning,in case of silent there will be no logging and the consumer will start from the beginning,in case of fail a ReachedClosedStateException will be raised | | Kinesis2ShardClosedStrategyEnum
-| *camel.component.aws2-kinesis.shard-id* | Defines which shardId in the Kinesis stream to get records from | | String
-| *camel.component.aws2-kinesis.trust-all-certificates* | If we want to trust all certificates in case of overriding the endpoint | false | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-aws2-kms-starter/src/main/docs/aws2-kms-starter.adoc b/components-starter/camel-aws2-kms-starter/src/main/docs/aws2-kms-starter.adoc
deleted file mode 100644
index 959109d..0000000
--- a/components-starter/camel-aws2-kms-starter/src/main/docs/aws2-kms-starter.adoc
+++ /dev/null
@@ -1,42 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for aws2-kms
-
-== Spring Boot Auto-Configuration
-
-When using aws2-kms with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-aws2-kms-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 14 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.aws2-kms.access-key* | Amazon AWS Access Key | | String
-| *camel.component.aws2-kms.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.aws2-kms.configuration* | Component configuration. The option is a org.apache.camel.component.aws2.kms.KMS2Configuration type. | | KMS2Configuration
-| *camel.component.aws2-kms.enabled* | Whether to enable auto configuration of the aws2-kms component. This is enabled by default. | | Boolean
-| *camel.component.aws2-kms.kms-client* | To use a existing configured AWS KMS as client. The option is a software.amazon.awssdk.services.kms.KmsClient type. | | KmsClient
-| *camel.component.aws2-kms.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed t [...]
-| *camel.component.aws2-kms.operation* | The operation to perform | | KMS2Operations
-| *camel.component.aws2-kms.pojo-request* | If we want to use a POJO request as body or not | false | Boolean
-| *camel.component.aws2-kms.proxy-host* | To define a proxy host when instantiating the KMS client | | String
-| *camel.component.aws2-kms.proxy-port* | To define a proxy port when instantiating the KMS client | | Integer
-| *camel.component.aws2-kms.proxy-protocol* | To define a proxy protocol when instantiating the KMS client | | Protocol
-| *camel.component.aws2-kms.region* | The region in which EKS client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | | String
-| *camel.component.aws2-kms.secret-key* | Amazon AWS Secret Key | | String
-| *camel.component.aws2-kms.trust-all-certificates* | If we want to trust all certificates in case of overriding the endpoint | false | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-aws2-lambda-starter/src/main/docs/aws2-lambda-starter.adoc b/components-starter/camel-aws2-lambda-starter/src/main/docs/aws2-lambda-starter.adoc
deleted file mode 100644
index 600ac7b..0000000
--- a/components-starter/camel-aws2-lambda-starter/src/main/docs/aws2-lambda-starter.adoc
+++ /dev/null
@@ -1,42 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for aws2-lambda
-
-== Spring Boot Auto-Configuration
-
-When using aws2-lambda with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-aws2-lambda-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 14 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.aws2-lambda.access-key* | Amazon AWS Access Key | | String
-| *camel.component.aws2-lambda.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.aws2-lambda.aws-lambda-client* | To use a existing configured AwsLambdaClient as client. The option is a software.amazon.awssdk.services.lambda.LambdaClient type. | | LambdaClient
-| *camel.component.aws2-lambda.configuration* | Component configuration. The option is a org.apache.camel.component.aws2.lambda.Lambda2Configuration type. | | Lambda2Configuration
-| *camel.component.aws2-lambda.enabled* | Whether to enable auto configuration of the aws2-lambda component. This is enabled by default. | | Boolean
-| *camel.component.aws2-lambda.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processe [...]
-| *camel.component.aws2-lambda.operation* | The operation to perform. It can be listFunctions, getFunction, createFunction, deleteFunction or invokeFunction | | Lambda2Operations
-| *camel.component.aws2-lambda.pojo-request* | If we want to use a POJO request as body or not | false | Boolean
-| *camel.component.aws2-lambda.proxy-host* | To define a proxy host when instantiating the Lambda client | | String
-| *camel.component.aws2-lambda.proxy-port* | To define a proxy port when instantiating the Lambda client | | Integer
-| *camel.component.aws2-lambda.proxy-protocol* | To define a proxy protocol when instantiating the Lambda client | | Protocol
-| *camel.component.aws2-lambda.region* | The region in which ECS client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | | String
-| *camel.component.aws2-lambda.secret-key* | Amazon AWS Secret Key | | String
-| *camel.component.aws2-lambda.trust-all-certificates* | If we want to trust all certificates in case of overriding the endpoint | false | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-aws2-mq-starter/src/main/docs/aws2-mq-starter.adoc b/components-starter/camel-aws2-mq-starter/src/main/docs/aws2-mq-starter.adoc
deleted file mode 100644
index 493f734..0000000
--- a/components-starter/camel-aws2-mq-starter/src/main/docs/aws2-mq-starter.adoc
+++ /dev/null
@@ -1,42 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for aws2-mq
-
-== Spring Boot Auto-Configuration
-
-When using aws2-mq with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-aws2-mq-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 14 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.aws2-mq.access-key* | Amazon AWS Access Key | | String
-| *camel.component.aws2-mq.amazon-mq-client* | To use a existing configured AmazonMQClient as client. The option is a software.amazon.awssdk.services.mq.MqClient type. | | MqClient
-| *camel.component.aws2-mq.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.aws2-mq.configuration* | Component configuration. The option is a org.apache.camel.component.aws2.mq.MQ2Configuration type. | | MQ2Configuration
-| *camel.component.aws2-mq.enabled* | Whether to enable auto configuration of the aws2-mq component. This is enabled by default. | | Boolean
-| *camel.component.aws2-mq.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
-| *camel.component.aws2-mq.operation* | The operation to perform. It can be listBrokers,createBroker,deleteBroker | | MQ2Operations
-| *camel.component.aws2-mq.pojo-request* | If we want to use a POJO request as body or not | false | Boolean
-| *camel.component.aws2-mq.proxy-host* | To define a proxy host when instantiating the MQ client | | String
-| *camel.component.aws2-mq.proxy-port* | To define a proxy port when instantiating the MQ client | | Integer
-| *camel.component.aws2-mq.proxy-protocol* | To define a proxy protocol when instantiating the MQ client | | Protocol
-| *camel.component.aws2-mq.region* | The region in which MQ client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | | String
-| *camel.component.aws2-mq.secret-key* | Amazon AWS Secret Key | | String
-| *camel.component.aws2-mq.trust-all-certificates* | If we want to trust all certificates in case of overriding the endpoint | false | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-aws2-msk-starter/src/main/docs/aws2-msk-starter.adoc b/components-starter/camel-aws2-msk-starter/src/main/docs/aws2-msk-starter.adoc
deleted file mode 100644
index 0c77189..0000000
--- a/components-starter/camel-aws2-msk-starter/src/main/docs/aws2-msk-starter.adoc
+++ /dev/null
@@ -1,42 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for aws2-msk
-
-== Spring Boot Auto-Configuration
-
-When using aws2-msk with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-aws2-msk-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 14 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.aws2-msk.access-key* | Amazon AWS Access Key | | String
-| *camel.component.aws2-msk.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.aws2-msk.configuration* | Component configuration. The option is a org.apache.camel.component.aws2.msk.MSK2Configuration type. | | MSK2Configuration
-| *camel.component.aws2-msk.enabled* | Whether to enable auto configuration of the aws2-msk component. This is enabled by default. | | Boolean
-| *camel.component.aws2-msk.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed t [...]
-| *camel.component.aws2-msk.msk-client* | To use a existing configured AWS MSK as client. The option is a software.amazon.awssdk.services.kafka.KafkaClient type. | | KafkaClient
-| *camel.component.aws2-msk.operation* | The operation to perform | | MSK2Operations
-| *camel.component.aws2-msk.pojo-request* | If we want to use a POJO request as body or not | false | Boolean
-| *camel.component.aws2-msk.proxy-host* | To define a proxy host when instantiating the MSK client | | String
-| *camel.component.aws2-msk.proxy-port* | To define a proxy port when instantiating the MSK client | | Integer
-| *camel.component.aws2-msk.proxy-protocol* | To define a proxy protocol when instantiating the MSK client | | Protocol
-| *camel.component.aws2-msk.region* | The region in which MSK client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | | String
-| *camel.component.aws2-msk.secret-key* | Amazon AWS Secret Key | | String
-| *camel.component.aws2-msk.trust-all-certificates* | If we want to trust all certificates in case of overriding the endpoint | false | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-aws2-s3-starter/src/main/docs/aws2-s3-starter.adoc b/components-starter/camel-aws2-s3-starter/src/main/docs/aws2-s3-starter.adoc
deleted file mode 100644
index 653ed35..0000000
--- a/components-starter/camel-aws2-s3-starter/src/main/docs/aws2-s3-starter.adoc
+++ /dev/null
@@ -1,71 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for aws2-s3
-
-== Spring Boot Auto-Configuration
-
-When using aws2-s3 with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-aws2-s3-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 43 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.aws2-s3.access-key* | Amazon AWS Access Key | | String
-| *camel.component.aws2-s3.amazon-s3-client* | Reference to a com.amazonaws.services.s3.AmazonS3 in the registry. The option is a software.amazon.awssdk.services.s3.S3Client type. | | S3Client
-| *camel.component.aws2-s3.amazon-s3-presigner* | An S3 Presigner for Request, used mainly in createDownloadLink operation. The option is a software.amazon.awssdk.services.s3.presigner.S3Presigner type. | | S3Presigner
-| *camel.component.aws2-s3.auto-create-bucket* | Setting the autocreation of the S3 bucket bucketName. This will apply also in case of moveAfterRead option enabled and it will create the destinationBucket if it doesn't exist already. | true | Boolean
-| *camel.component.aws2-s3.autoclose-body* | If this option is true and includeBody is false, then the S3Object.close() method will be called on exchange completion. This option is strongly related to includeBody option. In case of setting includeBody to false and autocloseBody to false, it will be up to the caller to close the S3Object stream. Setting autocloseBody to true, will close the S3Object stream automatically. | true | Boolean
-| *camel.component.aws2-s3.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.aws2-s3.aws-k-m-s-key-id* | Define the id of KMS key to use in case KMS is enabled | | String
-| *camel.component.aws2-s3.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.aws2-s3.configuration* | The component configuration. The option is a org.apache.camel.component.aws2.s3.AWS2S3Configuration type. | | AWS2S3Configuration
-| *camel.component.aws2-s3.customer-algorithm* | Define the customer algorithm to use in case CustomerKey is enabled | | String
-| *camel.component.aws2-s3.customer-key-id* | Define the id of Customer key to use in case CustomerKey is enabled | | String
-| *camel.component.aws2-s3.customer-key-m-d5* | Define the MD5 of Customer key to use in case CustomerKey is enabled | | String
-| *camel.component.aws2-s3.delete-after-read* | Delete objects from S3 after they have been retrieved. The delete is only performed if the Exchange is committed. If a rollback occurs, the object is not deleted. If this option is false, then the same objects will be retrieve over and over again on the polls. Therefore you need to use the Idempotent Consumer EIP in the route to filter out duplicates. You can filter using the AWS2S3Constants#BUCKET_NAME and AWS2S3Constants#KEY headers, or o [...]
-| *camel.component.aws2-s3.delete-after-write* | Delete file object after the S3 file has been uploaded | false | Boolean
-| *camel.component.aws2-s3.delimiter* | The delimiter which is used in the com.amazonaws.services.s3.model.ListObjectsRequest to only consume objects we are interested in. | | String
-| *camel.component.aws2-s3.destination-bucket* | Define the destination bucket where an object must be moved when moveAfterRead is set to true. | | String
-| *camel.component.aws2-s3.destination-bucket-prefix* | Define the destination bucket prefix to use when an object must be moved and moveAfterRead is set to true. | | String
-| *camel.component.aws2-s3.destination-bucket-suffix* | Define the destination bucket suffix to use when an object must be moved and moveAfterRead is set to true. | | String
-| *camel.component.aws2-s3.enabled* | Whether to enable auto configuration of the aws2-s3 component. This is enabled by default. | | Boolean
-| *camel.component.aws2-s3.file-name* | To get the object from the bucket with the given file name | | String
-| *camel.component.aws2-s3.include-body* | If it is true, the S3Object exchange will be consumed and put into the body and closed. If false the S3Object stream will be put raw into the body and the headers will be set with the S3 object metadata. This option is strongly related to autocloseBody option. In case of setting includeBody to true because the S3Object stream will be consumed then it will also be closed in case of includeBody false then it will be up to the caller to close the S [...]
-| *camel.component.aws2-s3.include-folders* | If it is true, the folders/directories will be consumed. If it is false, they will be ignored, and Exchanges will not be created for those | true | Boolean
-| *camel.component.aws2-s3.key-name* | Setting the key name for an element in the bucket through endpoint parameter | | String
-| *camel.component.aws2-s3.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
-| *camel.component.aws2-s3.move-after-read* | Move objects from S3 bucket to a different bucket after they have been retrieved. To accomplish the operation the destinationBucket option must be set. The copy bucket operation is only performed if the Exchange is committed. If a rollback occurs, the object is not moved. | false | Boolean
-| *camel.component.aws2-s3.multi-part-upload* | If it is true, camel will upload the file with multi part format, the part size is decided by the option of partSize | false | Boolean
-| *camel.component.aws2-s3.operation* | The operation to do in case the user don't want to do only an upload | | AWS2S3Operations
-| *camel.component.aws2-s3.override-endpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | Boolean
-| *camel.component.aws2-s3.part-size* | Setup the partSize which is used in multi part upload, the default size is 25M. | 26214400 | Long
-| *camel.component.aws2-s3.pojo-request* | If we want to use a POJO request as body or not | false | Boolean
-| *camel.component.aws2-s3.policy* | The policy for this queue to set in the com.amazonaws.services.s3.AmazonS3#setBucketPolicy() method. | | String
-| *camel.component.aws2-s3.prefix* | The prefix which is used in the com.amazonaws.services.s3.model.ListObjectsRequest to only consume objects we are interested in. | | String
-| *camel.component.aws2-s3.proxy-host* | To define a proxy host when instantiating the SQS client | | String
-| *camel.component.aws2-s3.proxy-port* | Specify a proxy port to be used inside the client definition. | | Integer
-| *camel.component.aws2-s3.proxy-protocol* | To define a proxy protocol when instantiating the S3 client | | Protocol
-| *camel.component.aws2-s3.region* | The region in which S3 client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | | String
-| *camel.component.aws2-s3.secret-key* | Amazon AWS Secret Key | | String
-| *camel.component.aws2-s3.storage-class* | The storage class to set in the com.amazonaws.services.s3.model.PutObjectRequest request. | | String
-| *camel.component.aws2-s3.trust-all-certificates* | If we want to trust all certificates in case of overriding the endpoint | false | Boolean
-| *camel.component.aws2-s3.uri-endpoint-override* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | | String
-| *camel.component.aws2-s3.use-aws-k-m-s* | Define if KMS must be used or not | false | Boolean
-| *camel.component.aws2-s3.use-customer-key* | Define if Customer Key must be used or not | false | Boolean
-| *camel.component.aws2-s3.use-default-credentials-provider* | Set whether the S3 client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | false | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-aws2-ses-starter/src/main/docs/aws2-ses-starter.adoc b/components-starter/camel-aws2-ses-starter/src/main/docs/aws2-ses-starter.adoc
deleted file mode 100644
index 72e8c0a..0000000
--- a/components-starter/camel-aws2-ses-starter/src/main/docs/aws2-ses-starter.adoc
+++ /dev/null
@@ -1,44 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for aws2-ses
-
-== Spring Boot Auto-Configuration
-
-When using aws2-ses with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-aws2-ses-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 16 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.aws2-ses.access-key* | Amazon AWS Access Key | | String
-| *camel.component.aws2-ses.amazon-s-e-s-client* | To use the AmazonSimpleEmailService as the client. The option is a software.amazon.awssdk.services.ses.SesClient type. | | SesClient
-| *camel.component.aws2-ses.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.aws2-ses.configuration* | component configuration. The option is a org.apache.camel.component.aws2.ses.Ses2Configuration type. | | Ses2Configuration
-| *camel.component.aws2-ses.enabled* | Whether to enable auto configuration of the aws2-ses component. This is enabled by default. | | Boolean
-| *camel.component.aws2-ses.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed t [...]
-| *camel.component.aws2-ses.proxy-host* | To define a proxy host when instantiating the SES client | | String
-| *camel.component.aws2-ses.proxy-port* | To define a proxy port when instantiating the SES client | | Integer
-| *camel.component.aws2-ses.proxy-protocol* | To define a proxy protocol when instantiating the SES client | | Protocol
-| *camel.component.aws2-ses.region* | The region in which SES client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | | String
-| *camel.component.aws2-ses.reply-to-addresses* | List of reply-to email address(es) for the message, override it using 'CamelAwsSesReplyToAddresses' header. | | List
-| *camel.component.aws2-ses.return-path* | The email address to which bounce notifications are to be forwarded, override it using 'CamelAwsSesReturnPath' header. | | String
-| *camel.component.aws2-ses.secret-key* | Amazon AWS Secret Key | | String
-| *camel.component.aws2-ses.subject* | The subject which is used if the message header 'CamelAwsSesSubject' is not present. | | String
-| *camel.component.aws2-ses.to* | List of destination email address. Can be overriden with 'CamelAwsSesTo' header. | | List
-| *camel.component.aws2-ses.trust-all-certificates* | If we want to trust all certificates in case of overriding the endpoint | false | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-aws2-sns-starter/src/main/docs/aws2-sns-starter.adoc b/components-starter/camel-aws2-sns-starter/src/main/docs/aws2-sns-starter.adoc
deleted file mode 100644
index c2ed634..0000000
--- a/components-starter/camel-aws2-sns-starter/src/main/docs/aws2-sns-starter.adoc
+++ /dev/null
@@ -1,51 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for aws2-sns
-
-== Spring Boot Auto-Configuration
-
-When using aws2-sns with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-aws2-sns-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 23 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.aws2-sns.access-key* | Amazon AWS Access Key | | String
-| *camel.component.aws2-sns.amazon-s-n-s-client* | To use the AmazonSNS as the client. The option is a software.amazon.awssdk.services.sns.SnsClient type. | | SnsClient
-| *camel.component.aws2-sns.auto-create-topic* | Setting the autocreation of the topic | true | Boolean
-| *camel.component.aws2-sns.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.aws2-sns.configuration* | Component configuration. The option is a org.apache.camel.component.aws2.sns.Sns2Configuration type. | | Sns2Configuration
-| *camel.component.aws2-sns.enabled* | Whether to enable auto configuration of the aws2-sns component. This is enabled by default. | | Boolean
-| *camel.component.aws2-sns.kms-master-key-id* | The ID of an AWS-managed customer master key (CMK) for Amazon SNS or a custom CMK. | | String
-| *camel.component.aws2-sns.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed t [...]
-| *camel.component.aws2-sns.message-deduplication-id-strategy* | Only for FIFO Topic. Strategy for setting the messageDeduplicationId on the message. Can be one of the following options: useExchangeId, useContentBasedDeduplication. For the useContentBasedDeduplication option, no messageDeduplicationId will be set on the message. | useExchangeId | String
-| *camel.component.aws2-sns.message-group-id-strategy* | Only for FIFO Topic. Strategy for setting the messageGroupId on the message. Can be one of the following options: useConstant, useExchangeId, usePropertyValue. For the usePropertyValue option, the value of property CamelAwsMessageGroupId will be used. | | String
-| *camel.component.aws2-sns.message-structure* | The message structure to use such as json | | String
-| *camel.component.aws2-sns.policy* | The policy for this queue | | String
-| *camel.component.aws2-sns.proxy-host* | To define a proxy host when instantiating the SNS client | | String
-| *camel.component.aws2-sns.proxy-port* | To define a proxy port when instantiating the SNS client | | Integer
-| *camel.component.aws2-sns.proxy-protocol* | To define a proxy protocol when instantiating the SNS client | | Protocol
-| *camel.component.aws2-sns.queue-url* | The queueUrl to subscribe to | | String
-| *camel.component.aws2-sns.region* | The region in which SNS client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | | String
-| *camel.component.aws2-sns.secret-key* | Amazon AWS Secret Key | | String
-| *camel.component.aws2-sns.server-side-encryption-enabled* | Define if Server Side Encryption is enabled or not on the topic | false | Boolean
-| *camel.component.aws2-sns.subject* | The subject which is used if the message header 'CamelAwsSnsSubject' is not present. | | String
-| *camel.component.aws2-sns.subscribe-s-n-sto-s-q-s* | Define if the subscription between SNS Topic and SQS must be done or not | false | Boolean
-| *camel.component.aws2-sns.trust-all-certificates* | If we want to trust all certificates in case of overriding the endpoint | false | Boolean
-| *camel.component.aws2-sns.use-default-credentials-provider* | Set whether the SNS client should expect to load credentials on an AWS infra instance or to expect static credentials to be passed in. | false | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-aws2-sqs-starter/src/main/docs/aws2-sqs-starter.adoc b/components-starter/camel-aws2-sqs-starter/src/main/docs/aws2-sqs-starter.adoc
deleted file mode 100644
index e54a950..0000000
--- a/components-starter/camel-aws2-sqs-starter/src/main/docs/aws2-sqs-starter.adoc
+++ /dev/null
@@ -1,69 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for aws2-sqs
-
-== Spring Boot Auto-Configuration
-
-When using aws2-sqs with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-aws2-sqs-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 41 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.aws2-sqs.access-key* | Amazon AWS Access Key | | String
-| *camel.component.aws2-sqs.amazon-a-w-s-host* | The hostname of the Amazon AWS cloud. | amazonaws.com | String
-| *camel.component.aws2-sqs.amazon-s-q-s-client* | To use the AmazonSQS as client. The option is a software.amazon.awssdk.services.sqs.SqsClient type. | | SqsClient
-| *camel.component.aws2-sqs.attribute-names* | A list of attribute names to receive when consuming. Multiple names can be separated by comma. | | String
-| *camel.component.aws2-sqs.auto-create-queue* | Setting the autocreation of the queue | true | Boolean
-| *camel.component.aws2-sqs.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.aws2-sqs.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.aws2-sqs.concurrent-consumers* | Allows you to use multiple threads to poll the sqs queue to increase throughput | 1 | Integer
-| *camel.component.aws2-sqs.configuration* | The AWS SQS default configuration. The option is a org.apache.camel.component.aws2.sqs.Sqs2Configuration type. | | Sqs2Configuration
-| *camel.component.aws2-sqs.default-visibility-timeout* | The default visibility timeout (in seconds) | | Integer
-| *camel.component.aws2-sqs.delay-queue* | Define if you want to apply delaySeconds option to the queue or on single messages | false | Boolean
-| *camel.component.aws2-sqs.delay-seconds* | Delay sending messages for a number of seconds. | | Integer
-| *camel.component.aws2-sqs.delete-after-read* | Delete message from SQS after it has been read | true | Boolean
-| *camel.component.aws2-sqs.delete-if-filtered* | Whether or not to send the DeleteMessage to the SQS queue if an exchange fails to get through a filter. If 'false' and exchange does not make it through a Camel filter upstream in the route, then don't send DeleteMessage. | true | Boolean
-| *camel.component.aws2-sqs.enabled* | Whether to enable auto configuration of the aws2-sqs component. This is enabled by default. | | Boolean
-| *camel.component.aws2-sqs.extend-message-visibility* | If enabled then a scheduled background task will keep extending the message visibility on SQS. This is needed if it takes a long time to process the message. If set to true defaultVisibilityTimeout must be set. See details at Amazon docs. | false | Boolean
-| *camel.component.aws2-sqs.kms-data-key-reuse-period-seconds* | The length of time, in seconds, for which Amazon SQS can reuse a data key to encrypt or decrypt messages before calling AWS KMS again. An integer representing seconds, between 60 seconds (1 minute) and 86,400 seconds (24 hours). Default: 300 (5 minutes). | | Integer
-| *camel.component.aws2-sqs.kms-master-key-id* | The ID of an AWS-managed customer master key (CMK) for Amazon SQS or a custom CMK. | | String
-| *camel.component.aws2-sqs.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed t [...]
-| *camel.component.aws2-sqs.maximum-message-size* | The maximumMessageSize (in bytes) an SQS message can contain for this queue. | | Integer
-| *camel.component.aws2-sqs.message-attribute-names* | A list of message attribute names to receive when consuming. Multiple names can be separated by comma. | | String
-| *camel.component.aws2-sqs.message-deduplication-id-strategy* | Only for FIFO queues. Strategy for setting the messageDeduplicationId on the message. Can be one of the following options: useExchangeId, useContentBasedDeduplication. For the useContentBasedDeduplication option, no messageDeduplicationId will be set on the message. | useExchangeId | String
-| *camel.component.aws2-sqs.message-group-id-strategy* | Only for FIFO queues. Strategy for setting the messageGroupId on the message. Can be one of the following options: useConstant, useExchangeId, usePropertyValue. For the usePropertyValue option, the value of property CamelAwsMessageGroupId will be used. | | String
-| *camel.component.aws2-sqs.message-retention-period* | The messageRetentionPeriod (in seconds) a message will be retained by SQS for this queue. | | Integer
-| *camel.component.aws2-sqs.operation* | The operation to do in case the user don't want to send only a message | | Sqs2Operations
-| *camel.component.aws2-sqs.policy* | The policy for this queue | | String
-| *camel.component.aws2-sqs.protocol* | The underlying protocol used to communicate with SQS | https | String
-| *camel.component.aws2-sqs.proxy-host* | To define a proxy host when instantiating the SQS client | | String
-| *camel.component.aws2-sqs.proxy-port* | To define a proxy port when instantiating the SQS client | | Integer
-| *camel.component.aws2-sqs.proxy-protocol* | To define a proxy protocol when instantiating the SQS client | | Protocol
-| *camel.component.aws2-sqs.queue-owner-a-w-s-account-id* | Specify the queue owner aws account id when you need to connect the queue with different account owner. | | String
-| *camel.component.aws2-sqs.queue-url* | To define the queueUrl explicitly. All other parameters, which would influence the queueUrl, are ignored. This parameter is intended to be used, to connect to a mock implementation of SQS, for testing purposes. | | String
-| *camel.component.aws2-sqs.receive-message-wait-time-seconds* | If you do not specify WaitTimeSeconds in the request, the queue attribute ReceiveMessageWaitTimeSeconds is used to determine how long to wait. | | Integer
-| *camel.component.aws2-sqs.redrive-policy* | Specify the policy that send message to DeadLetter queue. See detail at Amazon docs. | | String
-| *camel.component.aws2-sqs.region* | The region in which SQS client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | | String
-| *camel.component.aws2-sqs.secret-key* | Amazon AWS Secret Key | | String
-| *camel.component.aws2-sqs.server-side-encryption-enabled* | Define if Server Side Encryption is enabled or not on the queue | false | Boolean
-| *camel.component.aws2-sqs.trust-all-certificates* | If we want to trust all certificates in case of overriding the endpoint | false | Boolean
-| *camel.component.aws2-sqs.use-default-credentials-provider* | Set whether the SQS client should expect to load credentials on an AWS infra instance or to expect static credentials to be passed in. | false | Boolean
-| *camel.component.aws2-sqs.visibility-timeout* | The duration (in seconds) that the received messages are hidden from subsequent retrieve requests after being retrieved by a ReceiveMessage request to set in the com.amazonaws.services.sqs.model.SetQueueAttributesRequest. This only make sense if its different from defaultVisibilityTimeout. It changes the queue visibility timeout attribute permanently. | | Integer
-| *camel.component.aws2-sqs.wait-time-seconds* | Duration in seconds (0 to 20) that the ReceiveMessage action call will wait until a message is in the queue to include in the response. | | Integer
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-aws2-sts-starter/src/main/docs/aws2-sts-starter.adoc b/components-starter/camel-aws2-sts-starter/src/main/docs/aws2-sts-starter.adoc
deleted file mode 100644
index 0f5fda3..0000000
--- a/components-starter/camel-aws2-sts-starter/src/main/docs/aws2-sts-starter.adoc
+++ /dev/null
@@ -1,42 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for aws2-sts
-
-== Spring Boot Auto-Configuration
-
-When using aws2-sts with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-aws2-sts-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 14 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.aws2-sts.access-key* | Amazon AWS Access Key | | String
-| *camel.component.aws2-sts.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.aws2-sts.configuration* | Component configuration. The option is a org.apache.camel.component.aws2.sts.STS2Configuration type. | | STS2Configuration
-| *camel.component.aws2-sts.enabled* | Whether to enable auto configuration of the aws2-sts component. This is enabled by default. | | Boolean
-| *camel.component.aws2-sts.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed t [...]
-| *camel.component.aws2-sts.operation* | The operation to perform | | STS2Operations
-| *camel.component.aws2-sts.pojo-request* | If we want to use a POJO request as body or not | false | Boolean
-| *camel.component.aws2-sts.proxy-host* | To define a proxy host when instantiating the STS client | | String
-| *camel.component.aws2-sts.proxy-port* | To define a proxy port when instantiating the STS client | | Integer
-| *camel.component.aws2-sts.proxy-protocol* | To define a proxy protocol when instantiating the STS client | | Protocol
-| *camel.component.aws2-sts.region* | The region in which STS client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | aws-global | String
-| *camel.component.aws2-sts.secret-key* | Amazon AWS Secret Key | | String
-| *camel.component.aws2-sts.sts-client* | To use a existing configured AWS STS as client. The option is a software.amazon.awssdk.services.sts.StsClient type. | | StsClient
-| *camel.component.aws2-sts.trust-all-certificates* | If we want to trust all certificates in case of overriding the endpoint | false | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-aws2-translate-starter/src/main/docs/aws2-translate-starter.adoc b/components-starter/camel-aws2-translate-starter/src/main/docs/aws2-translate-starter.adoc
deleted file mode 100644
index 9561e4f..0000000
--- a/components-starter/camel-aws2-translate-starter/src/main/docs/aws2-translate-starter.adoc
+++ /dev/null
@@ -1,45 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for aws2-translate
-
-== Spring Boot Auto-Configuration
-
-When using aws2-translate with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-aws2-translate-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 17 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.aws2-translate.access-key* | Amazon AWS Access Key | | String
-| *camel.component.aws2-translate.autodetect-source-language* | Being able to autodetect the source language | false | Boolean
-| *camel.component.aws2-translate.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.aws2-translate.configuration* | Component configuration. The option is a org.apache.camel.component.aws2.translate.Translate2Configuration type. | | Translate2Configuration
-| *camel.component.aws2-translate.enabled* | Whether to enable auto configuration of the aws2-translate component. This is enabled by default. | | Boolean
-| *camel.component.aws2-translate.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proce [...]
-| *camel.component.aws2-translate.operation* | The operation to perform | | Translate2Operations
-| *camel.component.aws2-translate.pojo-request* | If we want to use a POJO request as body or not | false | Boolean
-| *camel.component.aws2-translate.proxy-host* | To define a proxy host when instantiating the Translate client | | String
-| *camel.component.aws2-translate.proxy-port* | To define a proxy port when instantiating the Translate client | | Integer
-| *camel.component.aws2-translate.proxy-protocol* | To define a proxy protocol when instantiating the Translate client | | Protocol
-| *camel.component.aws2-translate.region* | The region in which Translate client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | | String
-| *camel.component.aws2-translate.secret-key* | Amazon AWS Secret Key | | String
-| *camel.component.aws2-translate.source-language* | Source language to use | | String
-| *camel.component.aws2-translate.target-language* | Target language to use | | String
-| *camel.component.aws2-translate.translate-client* | To use a existing configured AWS Translate as client. The option is a software.amazon.awssdk.services.translate.TranslateClient type. | | TranslateClient
-| *camel.component.aws2-translate.trust-all-certificates* | If we want to trust all certificates in case of overriding the endpoint | false | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-azure-eventhubs-starter/src/main/docs/azure-eventhubs-starter.adoc b/components-starter/camel-azure-eventhubs-starter/src/main/docs/azure-eventhubs-starter.adoc
deleted file mode 100644
index c628847efc..0000000
--- a/components-starter/camel-azure-eventhubs-starter/src/main/docs/azure-eventhubs-starter.adoc
+++ /dev/null
@@ -1,50 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for azure-eventhubs
-
-== Spring Boot Auto-Configuration
-
-When using azure-eventhubs with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-azure-eventhubs-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 22 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.azure-eventhubs.amqp-retry-options* | Sets the retry policy for EventHubAsyncClient. If not specified, the default retry options are used. The option is a com.azure.core.amqp.AmqpRetryOptions type. | | AmqpRetryOptions
-| *camel.component.azure-eventhubs.amqp-transport-type* | Sets the transport type by which all the communication with Azure Event Hubs occurs. Default value is AmqpTransportType#AMQP. | | AmqpTransportType
-| *camel.component.azure-eventhubs.auto-discover-client* | Setting the autoDiscoverClient mechanism, if true, the component will look for a client instance in the registry automatically otherwise it will skip that checking. | true | Boolean
-| *camel.component.azure-eventhubs.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.azure-eventhubs.blob-access-key* | In case you chose the default BlobCheckpointStore, this sets access key for the associated azure account name to be used for authentication with azure blob services | | String
-| *camel.component.azure-eventhubs.blob-account-name* | In case you chose the default BlobCheckpointStore, this sets Azure account name to be used for authentication with azure blob services. | | String
-| *camel.component.azure-eventhubs.blob-container-name* | In case you chose the default BlobCheckpointStore, this sets the blob container that shall be used by the BlobCheckpointStore to store the checkpoint offsets | | String
-| *camel.component.azure-eventhubs.blob-storage-shared-key-credential* | In case you chose the default BlobCheckpointStore, StorageSharedKeyCredential can be injected to create the azure client, this holds the important authentication information. The option is a com.azure.storage.common.StorageSharedKeyCredential type. | | StorageSharedKeyCredential
-| *camel.component.azure-eventhubs.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.azure-eventhubs.checkpoint-store* | Sets the CheckpointStore the EventProcessorClient will use for storing partition ownership and checkpoint information. Users can, optionally, provide their own implementation of CheckpointStore which will store ownership and checkpoint information. By default it set to use com.azure.messaging.eventhubs.checkpointstore.blob.BlobCheckpointStore which stores all checkpoint offsets into Azure Blob Storage. The option is a com.azure.messa [...]
-| *camel.component.azure-eventhubs.configuration* | The component configurations. The option is a org.apache.camel.component.azure.eventhubs.EventHubsConfiguration type. | | EventHubsConfiguration
-| *camel.component.azure-eventhubs.connection-string* | Instead of supplying namespace, sharedAccessKey, sharedAccessName ... etc, you can just supply the connection string for your eventHub. The connection string for EventHubs already include all the necessary information to connection to your EventHub. To learn on how to generate the connection string, take a look at this documentation: \https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-get-connection-string | | String
-| *camel.component.azure-eventhubs.consumer-group-name* | Sets the name of the consumer group this consumer is associated with. Events are read in the context of this group. The name of the consumer group that is created by default is {link #DEFAULT_CONSUMER_GROUP_NAME $Default}. | $Default | String
-| *camel.component.azure-eventhubs.enabled* | Whether to enable auto configuration of the azure-eventhubs component. This is enabled by default. | | Boolean
-| *camel.component.azure-eventhubs.event-position* | Sets the map containing the event position to use for each partition if a checkpoint for the partition does not exist in CheckpointStore. This map is keyed off of the partition id. If there is no checkpoint in CheckpointStore and there is no entry in this map, the processing of the partition will start from {link EventPosition#latest() latest} position. | | Map
-| *camel.component.azure-eventhubs.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proc [...]
-| *camel.component.azure-eventhubs.partition-id* | Sets the identifier of the Event Hub partition that the events will be sent to. If the identifier is not specified, the Event Hubs service will be responsible for routing events that are sent to an available partition. | | String
-| *camel.component.azure-eventhubs.partition-key* | Sets a hashing key to be provided for the batch of events, which instructs the Event Hubs service to map this key to a specific partition. The selection of a partition is stable for a given partition hashing key. Should any other batches of events be sent using the same exact partition hashing key, the Event Hubs service will route them all to the same partition. This should be specified only when there is a need to group events by part [...]
-| *camel.component.azure-eventhubs.prefetch-count* | Sets the count used by the receiver to control the number of events the Event Hub consumer will actively receive and queue locally without regard to whether a receive operation is currently active. | 500 | Integer
-| *camel.component.azure-eventhubs.producer-async-client* | Sets the EventHubProducerAsyncClient.An asynchronous producer responsible for transmitting EventData to a specific Event Hub, grouped together in batches. Depending on the options specified when creating an \{linkEventDataBatch}, the events may be automatically routed to an available partition or specific to a partition. Use by this component to produce the data in camel producer. The option is a com.azure.messaging.eventhubs.Ev [...]
-| *camel.component.azure-eventhubs.shared-access-key* | The generated value for the SharedAccessName | | String
-| *camel.component.azure-eventhubs.shared-access-name* | The name you chose for your EventHubs SAS keys | | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-azure-starter/src/main/docs/azure-starter.adoc b/components-starter/camel-azure-starter/src/main/docs/azure-starter.adoc
deleted file mode 100644
index 3771331..0000000
--- a/components-starter/camel-azure-starter/src/main/docs/azure-starter.adoc
+++ /dev/null
@@ -1,65 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for azure
-
-== Spring Boot Auto-Configuration
-
-When using azure with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-azure-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 37 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.azure-blob.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.azure-blob.azure-blob-client* | The blob service client. The option is a com.microsoft.azure.storage.blob.CloudBlob type. | | CloudBlob
-| *camel.component.azure-blob.blob-metadata* | Set the blob meta-data | | Map
-| *camel.component.azure-blob.blob-offset* | Set the blob offset for the upload or download operations, default is 0 | 0 | Long
-| *camel.component.azure-blob.blob-prefix* | Set a prefix which can be used for listing the blobs | | String
-| *camel.component.azure-blob.blob-type* | Set a blob type, 'blockblob' is default | | BlobType
-| *camel.component.azure-blob.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.azure-blob.close-stream-after-read* | Close the stream after read or keep it open, default is true | true | Boolean
-| *camel.component.azure-blob.close-stream-after-write* | Close the stream after write or keep it open, default is true | true | Boolean
-| *camel.component.azure-blob.configuration* | The Blob Service configuration. The option is a org.apache.camel.component.azure.blob.BlobServiceConfiguration type. | | BlobServiceConfiguration
-| *camel.component.azure-blob.credentials* | Set the storage credentials, required in most cases. The option is a com.microsoft.azure.storage.StorageCredentials type. | | StorageCredentials
-| *camel.component.azure-blob.credentials-account-key* | Set the storage account key used during authentication phase | | String
-| *camel.component.azure-blob.credentials-account-name* | Set the storage account name used during authentication phase | | String
-| *camel.component.azure-blob.data-length* | Set the data length for the download or page blob upload operations | | Long
-| *camel.component.azure-blob.enabled* | Whether to enable auto configuration of the azure-blob component. This is enabled by default. | | Boolean
-| *camel.component.azure-blob.file-dir* | Set the file directory where the downloaded blobs will be saved to | | String
-| *camel.component.azure-blob.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed [...]
-| *camel.component.azure-blob.operation* | Blob service operation hint to the producer | | BlobServiceOperations
-| *camel.component.azure-blob.public-for-read* | Storage resources can be public for reading their content, if this property is enabled then the credentials do not have to be set | false | Boolean
-| *camel.component.azure-blob.stream-read-size* | Set the minimum read size in bytes when reading the blob content | | Integer
-| *camel.component.azure-blob.stream-write-size* | Set the size of the buffer for writing block and page blocks | | Integer
-| *camel.component.azure-blob.use-flat-listing* | Specify if the flat or hierarchical blob listing should be used | true | Boolean
-| *camel.component.azure-blob.validate-client-u-r-i* | Whether to validate the Azure client URI | true | Boolean
-| *camel.component.azure-queue.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.azure-queue.azure-queue-client* | The queue service client. The option is a com.microsoft.azure.storage.queue.CloudQueue type. | | CloudQueue
-| *camel.component.azure-queue.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.azure-queue.configuration* | The Queue Service configuration. The option is a org.apache.camel.component.azure.queue.QueueServiceConfiguration type. | | QueueServiceConfiguration
-| *camel.component.azure-queue.credentials* | Set the storage credentials, required in most cases. The option is a com.microsoft.azure.storage.StorageCredentials type. | | StorageCredentials
-| *camel.component.azure-queue.credentials-account-key* | Set the storage account key used during authentication phase | | String
-| *camel.component.azure-queue.credentials-account-name* | Set the storage account name used during authentication phase | | String
-| *camel.component.azure-queue.enabled* | Whether to enable auto configuration of the azure-queue component. This is enabled by default. | | Boolean
-| *camel.component.azure-queue.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processe [...]
-| *camel.component.azure-queue.message-time-to-live* | Message Time To Live in seconds | | Integer
-| *camel.component.azure-queue.message-visibility-delay* | Message Visibility Delay in seconds | | Integer
-| *camel.component.azure-queue.operation* | Queue service operation hint to the producer | | QueueServiceOperations
-| *camel.component.azure-queue.queue-prefix* | Set a prefix which can be used for listing the queues | | String
-| *camel.component.azure-queue.validate-client-u-r-i* | Whether to validate the Azure client URI | true | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-azure-storage-blob-starter/src/main/docs/azure-storage-blob-starter.adoc b/components-starter/camel-azure-storage-blob-starter/src/main/docs/azure-storage-blob-starter.adoc
deleted file mode 100644
index 9a5cf84..0000000
--- a/components-starter/camel-azure-storage-blob-starter/src/main/docs/azure-storage-blob-starter.adoc
+++ /dev/null
@@ -1,57 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for azure-storage-blob
-
-== Spring Boot Auto-Configuration
-
-When using azure-storage-blob with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-azure-storage-blob-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 29 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.azure-storage-blob.access-key* | Access key for the associated azure account name to be used for authentication with azure blob services | | String
-| *camel.component.azure-storage-blob.auto-discover-client* | Setting the autoDiscoverClient mechanism, if true, the component will look for a client instance in the registry automatically otherwise it will skip that checking. | true | Boolean
-| *camel.component.azure-storage-blob.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.azure-storage-blob.blob-name* | The blob name, to consume specific blob from a container. However on producer, is only required for the operations on the blob level | | String
-| *camel.component.azure-storage-blob.blob-offset* | Set the blob offset for the upload or download operations, default is 0 | 0 | Long
-| *camel.component.azure-storage-blob.blob-sequence-number* | A user-controlled value that you can use to track requests. The value of the sequence number must be between 0 and 263 - 1.The default value is 0. | 0 | Long
-| *camel.component.azure-storage-blob.blob-type* | The blob type in order to initiate the appropriate settings for each blob type | | BlobType
-| *camel.component.azure-storage-blob.block-list-type* | Specifies which type of blocks to return. | | BlockListType
-| *camel.component.azure-storage-blob.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.azure-storage-blob.close-stream-after-read* | Close the stream after read or keep it open, default is true | true | Boolean
-| *camel.component.azure-storage-blob.close-stream-after-write* | Close the stream after write or keep it open, default is true | true | Boolean
-| *camel.component.azure-storage-blob.commit-block-list-later* | When is set to true, the staged blocks will not be committed directly. | true | Boolean
-| *camel.component.azure-storage-blob.configuration* | The component configurations. The option is a org.apache.camel.component.azure.storage.blob.BlobConfiguration type. | | BlobConfiguration
-| *camel.component.azure-storage-blob.create-append-blob* | When is set to true, the append blocks will be created when committing append blocks. | true | Boolean
-| *camel.component.azure-storage-blob.create-page-blob* | When is set to true, the page blob will be created when uploading page blob. | true | Boolean
-| *camel.component.azure-storage-blob.credentials* | StorageSharedKeyCredential can be injected to create the azure client, this holds the important authentication information. The option is a com.azure.storage.common.StorageSharedKeyCredential type. | | StorageSharedKeyCredential
-| *camel.component.azure-storage-blob.data-count* | How many bytes to include in the range. Must be greater than or equal to 0 if specified. | | Long
-| *camel.component.azure-storage-blob.download-link-expiration* | Override the default expiration (millis) of URL download link. | | Long
-| *camel.component.azure-storage-blob.enabled* | Whether to enable auto configuration of the azure-storage-blob component. This is enabled by default. | | Boolean
-| *camel.component.azure-storage-blob.file-dir* | The file directory where the downloaded blobs will be saved to, this can be used in both, producer and consumer | | String
-| *camel.component.azure-storage-blob.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is p [...]
-| *camel.component.azure-storage-blob.max-results-per-page* | Specifies the maximum number of blobs to return, including all BlobPrefix elements. If the request does not specify maxResultsPerPage or specifies a value greater than 5,000, the server will return up to 5,000 items. | | Integer
-| *camel.component.azure-storage-blob.max-retry-requests* | Specifies the maximum number of additional HTTP Get requests that will be made while reading the data from a response body. | 0 | Integer
-| *camel.component.azure-storage-blob.operation* | The blob operation that can be used with this component on the producer | | BlobOperationsDefinition
-| *camel.component.azure-storage-blob.page-blob-size* | Specifies the maximum size for the page blob, up to 8 TB. The page blob size must be aligned to a 512-byte boundary. | 512 | Long
-| *camel.component.azure-storage-blob.prefix* | Filters the results to return only blobs whose names begin with the specified prefix. May be null to return all blobs. | | String
-| *camel.component.azure-storage-blob.regex* | Filters the results to return only blobs whose names match the specified regular expression. May be null to return all if both prefix and regex are set, regex takes the priority and prefix is ignored. | | String
-| *camel.component.azure-storage-blob.service-client* | Client to a storage account. This client does not hold any state about a particular storage account but is instead a convenient way of sending off appropriate requests to the resource on the service. It may also be used to construct URLs to blobs and containers. This client contains operations on a service account. Operations on a container are available on BlobContainerClient through BlobServiceClient#getBlobContainerClient(String) [...]
-| *camel.component.azure-storage-blob.timeout* | An optional timeout value beyond which a RuntimeException will be raised. The option is a java.time.Duration type. | | Duration
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-azure-storage-queue-starter/src/main/docs/azure-storage-queue-starter.adoc b/components-starter/camel-azure-storage-queue-starter/src/main/docs/azure-storage-queue-starter.adoc
deleted file mode 100644
index 4f5a1a3..0000000
--- a/components-starter/camel-azure-storage-queue-starter/src/main/docs/azure-storage-queue-starter.adoc
+++ /dev/null
@@ -1,45 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for azure-storage-queue
-
-== Spring Boot Auto-Configuration
-
-When using azure-storage-queue with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-azure-storage-queue-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 17 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.azure-storage-queue.access-key* | Access key for the associated azure account name to be used for authentication with azure queue services | | String
-| *camel.component.azure-storage-queue.auto-discover-client* | Setting the autoDiscoverClient mechanism, if true, the component will look for a client instance in the registry automatically otherwise it will skip that checking. | true | Boolean
-| *camel.component.azure-storage-queue.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.azure-storage-queue.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.azure-storage-queue.configuration* | The component configurations. The option is a org.apache.camel.component.azure.storage.queue.QueueConfiguration type. | | QueueConfiguration
-| *camel.component.azure-storage-queue.create-queue* | When is set to true, the queue will be automatically created when sending messages to the queue. | true | Boolean
-| *camel.component.azure-storage-queue.credentials* | StorageSharedKeyCredential can be injected to create the azure client, this holds the important authentication information. The option is a com.azure.storage.common.StorageSharedKeyCredential type. | | StorageSharedKeyCredential
-| *camel.component.azure-storage-queue.enabled* | Whether to enable auto configuration of the azure-storage-queue component. This is enabled by default. | | Boolean
-| *camel.component.azure-storage-queue.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is [...]
-| *camel.component.azure-storage-queue.max-messages* | Maximum number of messages to get, if there are less messages exist in the queue than requested all the messages will be returned. If left empty only 1 message will be retrieved, the allowed range is 1 to 32 messages. | 1 | Integer
-| *camel.component.azure-storage-queue.message-id* | The ID of the message to be deleted or updated. | | String
-| *camel.component.azure-storage-queue.operation* | Queue service operation hint to the producer | | QueueOperationDefinition
-| *camel.component.azure-storage-queue.pop-receipt* | Unique identifier that must match for the message to be deleted or updated. | | String
-| *camel.component.azure-storage-queue.service-client* | Service client to a storage account to interact with the queue service. This client does not hold any state about a particular storage account but is instead a convenient way of sending off appropriate requests to the resource on the service. This client contains all the operations for interacting with a queue account in Azure Storage. Operations allowed by the client are creating, listing, and deleting queues, retrieving and updat [...]
-| *camel.component.azure-storage-queue.time-to-live* | How long the message will stay alive in the queue. If unset the value will default to 7 days, if -1 is passed the message will not expire. The time to live must be -1 or any positive number. The format should be in this form: PnDTnHnMn.nS., e.g: PT20.345S -- parses as 20.345 seconds, P2D -- parses as 2 days However, in case you are using EndpointDsl/ComponentDsl, you can do something like Duration.ofSeconds() since these Java APIs ar [...]
-| *camel.component.azure-storage-queue.timeout* | An optional timeout applied to the operation. If a response is not returned before the timeout concludes a RuntimeException will be thrown. The option is a java.time.Duration type. | | Duration
-| *camel.component.azure-storage-queue.visibility-timeout* | The timeout period for how long the message is invisible in the queue. The timeout must be between 1 seconds and 7 days. The format should be in this form: PnDTnHnMn.nS., e.g: PT20.345S -- parses as 20.345 seconds, P2D -- parses as 2 days However, in case you are using EndpointDsl/ComponentDsl, you can do something like Duration.ofSeconds() since these Java APIs are typesafe. The option is a java.time.Duration type. | | Duration
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-barcode-starter/src/main/docs/barcode-starter.adoc b/components-starter/camel-barcode-starter/src/main/docs/barcode-starter.adoc
deleted file mode 100644
index ea393eb..0000000
--- a/components-starter/camel-barcode-starter/src/main/docs/barcode-starter.adoc
+++ /dev/null
@@ -1,33 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for barcode
-
-== Spring Boot Auto-Configuration
-
-When using barcode with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-barcode-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 5 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.dataformat.barcode.barcode-format* | Barcode format such as QR-Code | | String
-| *camel.dataformat.barcode.enabled* | Whether to enable auto configuration of the barcode data format. This is enabled by default. | | Boolean
-| *camel.dataformat.barcode.height* | Height of the barcode | | Integer
-| *camel.dataformat.barcode.image-type* | Image type of the barcode such as png | | String
-| *camel.dataformat.barcode.width* | Width of the barcode | | Integer
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-base64-starter/src/main/docs/base64-starter.adoc b/components-starter/camel-base64-starter/src/main/docs/base64-starter.adoc
deleted file mode 100644
index e12f804..0000000
--- a/components-starter/camel-base64-starter/src/main/docs/base64-starter.adoc
+++ /dev/null
@@ -1,32 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for base64
-
-== Spring Boot Auto-Configuration
-
-When using base64 with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-base64-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 4 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.dataformat.base64.enabled* | Whether to enable auto configuration of the base64 data format. This is enabled by default. | | Boolean
-| *camel.dataformat.base64.line-length* | To specific a maximum line length for the encoded data. By default 76 is used. | 76 | Integer
-| *camel.dataformat.base64.line-separator* | The line separators to use. Uses new line characters (CRLF) by default. | | String
-| *camel.dataformat.base64.url-safe* | Instead of emitting '' and '/' we emit '-' and '_' respectively. urlSafe is only applied to encode operations. Decoding seamlessly handles both modes. Is by default false. | false | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-bean-starter/src/main/docs/bean-starter.adoc b/components-starter/camel-bean-starter/src/main/docs/bean-starter.adoc
deleted file mode 100644
index 4fbaee9..0000000
--- a/components-starter/camel-bean-starter/src/main/docs/bean-starter.adoc
+++ /dev/null
@@ -1,41 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for bean
-
-== Spring Boot Auto-Configuration
-
-When using bean with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-bean-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 13 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.bean.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.bean.enabled* | Whether to enable auto configuration of the bean component. This is enabled by default. | | Boolean
-| *camel.component.bean.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
-| *camel.component.bean.scope* | Scope of bean. When using singleton scope (default) the bean is created or looked up only once and reused for the lifetime of the endpoint. The bean should be thread-safe in case concurrent threads is calling the bean at the same time. When using request scope the bean is created or looked up once per request (exchange). This can be used if you want to store state on a bean while processing a request and you want to call the same bean instance multiple ti [...]
-| *camel.component.class.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.class.enabled* | Whether to enable auto configuration of the class component. This is enabled by default. | | Boolean
-| *camel.component.class.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
-| *camel.component.class.scope* | Scope of bean. When using singleton scope (default) the bean is created or looked up only once and reused for the lifetime of the endpoint. The bean should be thread-safe in case concurrent threads is calling the bean at the same time. When using request scope the bean is created or looked up once per request (exchange). This can be used if you want to store state on a bean while processing a request and you want to call the same bean instance multiple t [...]
-| *camel.language.bean.enabled* | Whether to enable auto configuration of the bean language. This is enabled by default. | | Boolean
-| *camel.language.bean.scope* | Scope of bean. When using singleton scope (default) the bean is created or looked up only once and reused for the lifetime of the endpoint. The bean should be thread-safe in case concurrent threads is calling the bean at the same time. When using request scope the bean is created or looked up once per request (exchange). This can be used if you want to store state on a bean while processing a request and you want to call the same bean instance multiple tim [...]
-| *camel.language.bean.trim* | Whether to trim the value to remove leading and trailing whitespaces and line breaks | true | Boolean
-| *camel.component.bean.cache* | *Deprecated* Use singleton option instead. | true | Boolean
-| *camel.component.class.cache* | *Deprecated* Use singleton option instead. | true | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-bean-validator-starter/src/main/docs/bean-validator-starter.adoc b/components-starter/camel-bean-validator-starter/src/main/docs/bean-validator-starter.adoc
deleted file mode 100644
index 1660fbf..0000000
--- a/components-starter/camel-bean-validator-starter/src/main/docs/bean-validator-starter.adoc
+++ /dev/null
@@ -1,37 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for bean-validator
-
-== Spring Boot Auto-Configuration
-
-When using bean-validator with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-bean-validator-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 9 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.bean-validator.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.bean-validator.constraint-validator-factory* | To use a custom ConstraintValidatorFactory. The option is a javax.validation.ConstraintValidatorFactory type. | | ConstraintValidatorFactory
-| *camel.component.bean-validator.enabled* | Whether to enable auto configuration of the bean-validator component. This is enabled by default. | | Boolean
-| *camel.component.bean-validator.ignore-xml-configuration* | Whether to ignore data from the META-INF/validation.xml file. | false | Boolean
-| *camel.component.bean-validator.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proce [...]
-| *camel.component.bean-validator.message-interpolator* | To use a custom MessageInterpolator. The option is a javax.validation.MessageInterpolator type. | | MessageInterpolator
-| *camel.component.bean-validator.traversable-resolver* | To use a custom TraversableResolver. The option is a javax.validation.TraversableResolver type. | | TraversableResolver
-| *camel.component.bean-validator.validation-provider-resolver* | To use a a custom ValidationProviderResolver. The option is a javax.validation.ValidationProviderResolver type. | | ValidationProviderResolver
-| *camel.component.bean-validator.validator-factory* | To use a custom ValidatorFactory. The option is a javax.validation.ValidatorFactory type. | | ValidatorFactory
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-beanio-starter/src/main/docs/beanio-starter.adoc b/components-starter/camel-beanio-starter/src/main/docs/beanio-starter.adoc
deleted file mode 100644
index 079a56e..0000000
--- a/components-starter/camel-beanio-starter/src/main/docs/beanio-starter.adoc
+++ /dev/null
@@ -1,37 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for beanio
-
-== Spring Boot Auto-Configuration
-
-When using beanio with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-beanio-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 9 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.dataformat.beanio.bean-reader-error-handler-type* | To use a custom org.apache.camel.dataformat.beanio.BeanIOErrorHandler as error handler while parsing. Configure the fully qualified class name of the error handler. Notice the options ignoreUnidentifiedRecords, ignoreUnexpectedRecords, and ignoreInvalidRecords may not be in use when you use a custom error handler. | | String
-| *camel.dataformat.beanio.enabled* | Whether to enable auto configuration of the beanio data format. This is enabled by default. | | Boolean
-| *camel.dataformat.beanio.encoding* | The charset to use. Is by default the JVM platform default charset. | | String
-| *camel.dataformat.beanio.ignore-invalid-records* | Whether to ignore invalid records. | false | Boolean
-| *camel.dataformat.beanio.ignore-unexpected-records* | Whether to ignore unexpected records. | false | Boolean
-| *camel.dataformat.beanio.ignore-unidentified-records* | Whether to ignore unidentified records. | false | Boolean
-| *camel.dataformat.beanio.mapping* | The BeanIO mapping file. Is by default loaded from the classpath. You can prefix with file:, http:, or classpath: to denote from where to load the mapping file. | | String
-| *camel.dataformat.beanio.stream-name* | The name of the stream to use. | | String
-| *camel.dataformat.beanio.unmarshal-single-object* | This options controls whether to unmarshal as a list of objects or as a single object only. The former is the default mode, and the latter is only intended in special use-cases where beanio maps the Camel message to a single POJO bean. | false | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-beanstalk-starter/src/main/docs/beanstalk-starter.adoc b/components-starter/camel-beanstalk-starter/src/main/docs/beanstalk-starter.adoc
deleted file mode 100644
index 34eeca6..0000000
--- a/components-starter/camel-beanstalk-starter/src/main/docs/beanstalk-starter.adoc
+++ /dev/null
@@ -1,33 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for beanstalk
-
-== Spring Boot Auto-Configuration
-
-When using beanstalk with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-beanstalk-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 5 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.beanstalk.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.beanstalk.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.beanstalk.connection-settings-factory* | Custom ConnectionSettingsFactory. Specify which ConnectionSettingsFactory to use to make connections to Beanstalkd. Especially useful for unit testing without beanstalkd daemon (you can mock ConnectionSettings). The option is a org.apache.camel.component.beanstalk.ConnectionSettingsFactory type. | | ConnectionSettingsFactory
-| *camel.component.beanstalk.enabled* | Whether to enable auto configuration of the beanstalk component. This is enabled by default. | | Boolean
-| *camel.component.beanstalk.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-bindy-starter/src/main/docs/bindy-starter.adoc b/components-starter/camel-bindy-starter/src/main/docs/bindy-starter.adoc
deleted file mode 100644
index 15194ce..0000000
--- a/components-starter/camel-bindy-starter/src/main/docs/bindy-starter.adoc
+++ /dev/null
@@ -1,46 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for bindy
-
-== Spring Boot Auto-Configuration
-
-When using bindy with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-bindy-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 18 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.dataformat.bindy-csv.allow-empty-stream* | Whether to allow empty streams in the unmarshal process. If true, no exception will be thrown when a body without records is provided. | false | Boolean
-| *camel.dataformat.bindy-csv.class-type* | Name of model class to use. | | String
-| *camel.dataformat.bindy-csv.enabled* | Whether to enable auto configuration of the bindy-csv data format. This is enabled by default. | | Boolean
-| *camel.dataformat.bindy-csv.locale* | To configure a default locale to use, such as us for united states. To use the JVM platform default locale then use the name default | | String
-| *camel.dataformat.bindy-csv.type* | Whether to use Csv, Fixed, or KeyValue. | | String
-| *camel.dataformat.bindy-csv.unwrap-single-instance* | When unmarshalling should a single instance be unwrapped and returned instead of wrapped in a java.util.List. | true | Boolean
-| *camel.dataformat.bindy-fixed.allow-empty-stream* | Whether to allow empty streams in the unmarshal process. If true, no exception will be thrown when a body without records is provided. | false | Boolean
-| *camel.dataformat.bindy-fixed.class-type* | Name of model class to use. | | String
-| *camel.dataformat.bindy-fixed.enabled* | Whether to enable auto configuration of the bindy-fixed data format. This is enabled by default. | | Boolean
-| *camel.dataformat.bindy-fixed.locale* | To configure a default locale to use, such as us for united states. To use the JVM platform default locale then use the name default | | String
-| *camel.dataformat.bindy-fixed.type* | Whether to use Csv, Fixed, or KeyValue. | | String
-| *camel.dataformat.bindy-fixed.unwrap-single-instance* | When unmarshalling should a single instance be unwrapped and returned instead of wrapped in a java.util.List. | true | Boolean
-| *camel.dataformat.bindy-kvp.allow-empty-stream* | Whether to allow empty streams in the unmarshal process. If true, no exception will be thrown when a body without records is provided. | false | Boolean
-| *camel.dataformat.bindy-kvp.class-type* | Name of model class to use. | | String
-| *camel.dataformat.bindy-kvp.enabled* | Whether to enable auto configuration of the bindy-kvp data format. This is enabled by default. | | Boolean
-| *camel.dataformat.bindy-kvp.locale* | To configure a default locale to use, such as us for united states. To use the JVM platform default locale then use the name default | | String
-| *camel.dataformat.bindy-kvp.type* | Whether to use Csv, Fixed, or KeyValue. | | String
-| *camel.dataformat.bindy-kvp.unwrap-single-instance* | When unmarshalling should a single instance be unwrapped and returned instead of wrapped in a java.util.List. | true | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-bonita-starter/src/main/docs/bonita-starter.adoc b/components-starter/camel-bonita-starter/src/main/docs/bonita-starter.adoc
deleted file mode 100644
index a67de3b..0000000
--- a/components-starter/camel-bonita-starter/src/main/docs/bonita-starter.adoc
+++ /dev/null
@@ -1,31 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for bonita
-
-== Spring Boot Auto-Configuration
-
-When using bonita with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-bonita-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 3 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.bonita.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.bonita.enabled* | Whether to enable auto configuration of the bonita component. This is enabled by default. | | Boolean
-| *camel.component.bonita.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed the [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-box-starter/src/main/docs/box-starter.adoc b/components-starter/camel-box-starter/src/main/docs/box-starter.adoc
deleted file mode 100644
index f6c6e37..0000000
--- a/components-starter/camel-box-starter/src/main/docs/box-starter.adoc
+++ /dev/null
@@ -1,48 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for box
-
-== Spring Boot Auto-Configuration
-
-When using box with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-box-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 20 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.box.access-token-cache* | Custom Access Token Cache for storing and retrieving access tokens. The option is a com.box.sdk.IAccessTokenCache type. | | IAccessTokenCache
-| *camel.component.box.authentication-type* | The type of authentication for connection. Types of Authentication: STANDARD_AUTHENTICATION - OAuth 2.0 (3-legged) SERVER_AUTHENTICATION - OAuth 2.0 with JSON Web Tokens | APP_USER_AUTHENTICATION | String
-| *camel.component.box.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.box.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.box.client-id* | Box application client ID | | String
-| *camel.component.box.client-secret* | Box application client secret | | String
-| *camel.component.box.configuration* | To use the shared configuration. The option is a org.apache.camel.component.box.BoxConfiguration type. | | BoxConfiguration
-| *camel.component.box.enabled* | Whether to enable auto configuration of the box component. This is enabled by default. | | Boolean
-| *camel.component.box.encryption-algorithm* | The type of encryption algorithm for JWT. Supported Algorithms: RSA_SHA_256 RSA_SHA_384 RSA_SHA_512 | | EncryptionAlgorithm
-| *camel.component.box.enterprise-id* | The enterprise ID to use for an App Enterprise. | | String
-| *camel.component.box.http-params* | Custom HTTP params for settings like proxy host | | Map
-| *camel.component.box.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then c [...]
-| *camel.component.box.max-cache-entries* | The maximum number of access tokens in cache. | 100 | Integer
-| *camel.component.box.private-key-file* | The private key for generating the JWT signature. | | String
-| *camel.component.box.private-key-password* | The password for the private key. | | String
-| *camel.component.box.public-key-id* | The ID for public key for validating the JWT signature. | | String
-| *camel.component.box.ssl-context-parameters* | To configure security using SSLContextParameters. The option is a org.apache.camel.support.jsse.SSLContextParameters type. | | SSLContextParameters
-| *camel.component.box.user-id* | The user ID to use for an App User. | | String
-| *camel.component.box.user-name* | Box user name, MUST be provided | | String
-| *camel.component.box.user-password* | Box user password, MUST be provided if authSecureStorage is not set, or returns null on first call | | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-braintree-starter/src/main/docs/braintree-starter.adoc b/components-starter/camel-braintree-starter/src/main/docs/braintree-starter.adoc
deleted file mode 100644
index a146fc2..0000000
--- a/components-starter/camel-braintree-starter/src/main/docs/braintree-starter.adoc
+++ /dev/null
@@ -1,32 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for braintree
-
-== Spring Boot Auto-Configuration
-
-When using braintree with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-braintree-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 4 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.braintree.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.braintree.configuration* | Component configuration. The option is a org.apache.camel.component.braintree.BraintreeConfiguration type. | | BraintreeConfiguration
-| *camel.component.braintree.enabled* | Whether to enable auto configuration of the braintree component. This is enabled by default. | | Boolean
-| *camel.component.braintree.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-browse-starter/src/main/docs/browse-starter.adoc b/components-starter/camel-browse-starter/src/main/docs/browse-starter.adoc
deleted file mode 100644
index 5e824f4..0000000
--- a/components-starter/camel-browse-starter/src/main/docs/browse-starter.adoc
+++ /dev/null
@@ -1,32 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for browse
-
-== Spring Boot Auto-Configuration
-
-When using browse with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-browse-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 4 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.browse.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.browse.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.browse.enabled* | Whether to enable auto configuration of the browse component. This is enabled by default. | | Boolean
-| *camel.component.browse.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed the [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-caffeine-starter/src/main/docs/caffeine-starter.adoc b/components-starter/camel-caffeine-starter/src/main/docs/caffeine-starter.adoc
deleted file mode 100644
index 647d1ec..0000000
--- a/components-starter/camel-caffeine-starter/src/main/docs/caffeine-starter.adoc
+++ /dev/null
@@ -1,64 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for caffeine
-
-== Spring Boot Auto-Configuration
-
-When using caffeine with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-caffeine-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 36 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.caffeine-cache.action* | To configure the default cache action. If an action is set in the message header, then the operation from the header takes precedence. | | String
-| *camel.component.caffeine-cache.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.caffeine-cache.cache-loader* | To configure a CacheLoader in case of a LoadCache use. The option is a com.github.benmanes.caffeine.cache.CacheLoader type. | | CacheLoader
-| *camel.component.caffeine-cache.configuration* | Sets the global component configuration. The option is a org.apache.camel.component.caffeine.CaffeineConfiguration type. | | CaffeineConfiguration
-| *camel.component.caffeine-cache.create-cache-if-not-exist* | Configure if a cache need to be created if it does exist or can't be pre-configured. | true | Boolean
-| *camel.component.caffeine-cache.enabled* | Whether to enable auto configuration of the caffeine-cache component. This is enabled by default. | | Boolean
-| *camel.component.caffeine-cache.eviction-type* | Set the eviction Type for this cache | | EvictionType
-| *camel.component.caffeine-cache.expire-after-access-time* | Set the expire After Access Time in case of time based Eviction (in seconds) | 300 | Integer
-| *camel.component.caffeine-cache.expire-after-write-time* | Set the expire After Access Write in case of time based Eviction (in seconds) | 300 | Integer
-| *camel.component.caffeine-cache.initial-capacity* | Set the initial Capacity for the cache | 10000 | Integer
-| *camel.component.caffeine-cache.key* | To configure the default action key. If a key is set in the message header, then the key from the header takes precedence. The option is a java.lang.Object type. | | Object
-| *camel.component.caffeine-cache.key-type* | The cache key type, default java.lang.Object | | String
-| *camel.component.caffeine-cache.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proce [...]
-| *camel.component.caffeine-cache.maximum-size* | Set the maximum size for the cache | 10000 | Integer
-| *camel.component.caffeine-cache.removal-listener* | Set a specific removal Listener for the cache. The option is a com.github.benmanes.caffeine.cache.RemovalListener type. | | RemovalListener
-| *camel.component.caffeine-cache.stats-counter* | Set a specific Stats Counter for the cache stats. The option is a com.github.benmanes.caffeine.cache.stats.StatsCounter type. | | StatsCounter
-| *camel.component.caffeine-cache.stats-enabled* | To enable stats on the cache | false | Boolean
-| *camel.component.caffeine-cache.value-type* | The cache value type, default java.lang.Object | | String
-| *camel.component.caffeine-loadcache.action* | To configure the default cache action. If an action is set in the message header, then the operation from the header takes precedence. | | String
-| *camel.component.caffeine-loadcache.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.caffeine-loadcache.cache-loader* | To configure a CacheLoader in case of a LoadCache use. The option is a com.github.benmanes.caffeine.cache.CacheLoader type. | | CacheLoader
-| *camel.component.caffeine-loadcache.configuration* | Sets the global component configuration. The option is a org.apache.camel.component.caffeine.CaffeineConfiguration type. | | CaffeineConfiguration
-| *camel.component.caffeine-loadcache.create-cache-if-not-exist* | Configure if a cache need to be created if it does exist or can't be pre-configured. | true | Boolean
-| *camel.component.caffeine-loadcache.enabled* | Whether to enable auto configuration of the caffeine-loadcache component. This is enabled by default. | | Boolean
-| *camel.component.caffeine-loadcache.eviction-type* | Set the eviction Type for this cache | | EvictionType
-| *camel.component.caffeine-loadcache.expire-after-access-time* | Set the expire After Access Time in case of time based Eviction (in seconds) | 300 | Integer
-| *camel.component.caffeine-loadcache.expire-after-write-time* | Set the expire After Access Write in case of time based Eviction (in seconds) | 300 | Integer
-| *camel.component.caffeine-loadcache.initial-capacity* | Set the initial Capacity for the cache | 10000 | Integer
-| *camel.component.caffeine-loadcache.key* | To configure the default action key. If a key is set in the message header, then the key from the header takes precedence. The option is a java.lang.Object type. | | Object
-| *camel.component.caffeine-loadcache.key-type* | The cache key type, default java.lang.Object | | String
-| *camel.component.caffeine-loadcache.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is p [...]
-| *camel.component.caffeine-loadcache.maximum-size* | Set the maximum size for the cache | 10000 | Integer
-| *camel.component.caffeine-loadcache.removal-listener* | Set a specific removal Listener for the cache. The option is a com.github.benmanes.caffeine.cache.RemovalListener type. | | RemovalListener
-| *camel.component.caffeine-loadcache.stats-counter* | Set a specific Stats Counter for the cache stats. The option is a com.github.benmanes.caffeine.cache.stats.StatsCounter type. | | StatsCounter
-| *camel.component.caffeine-loadcache.stats-enabled* | To enable stats on the cache | false | Boolean
-| *camel.component.caffeine-loadcache.value-type* | The cache value type, default java.lang.Object | | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-cassandraql-starter/src/main/docs/cassandraql-starter.adoc b/components-starter/camel-cassandraql-starter/src/main/docs/cassandraql-starter.adoc
deleted file mode 100644
index 8515223..0000000
--- a/components-starter/camel-cassandraql-starter/src/main/docs/cassandraql-starter.adoc
+++ /dev/null
@@ -1,32 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for cassandraql
-
-== Spring Boot Auto-Configuration
-
-When using cassandraql with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-cassandraql-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 4 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.cql.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.cql.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.cql.enabled* | Whether to enable auto configuration of the cql component. This is enabled by default. | | Boolean
-| *camel.component.cql.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then c [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-cbor-starter/src/main/docs/cbor-starter.adoc b/components-starter/camel-cbor-starter/src/main/docs/cbor-starter.adoc
deleted file mode 100644
index d7163e6..0000000
--- a/components-starter/camel-cbor-starter/src/main/docs/cbor-starter.adoc
+++ /dev/null
@@ -1,39 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for cbor
-
-== Spring Boot Auto-Configuration
-
-When using cbor with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-cbor-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 11 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.dataformat.cbor.allow-jms-type* | Used for JMS users to allow the JMSType header from the JMS spec to specify a FQN classname to use to unmarshal to. | false | Boolean
-| *camel.dataformat.cbor.allow-unmarshall-type* | If enabled then Jackson CBOR is allowed to attempt to use the CamelCBORUnmarshalType header during the unmarshalling. This should only be enabled when desired to be used. | false | Boolean
-| *camel.dataformat.cbor.collection-type-name* | Refers to a custom collection type to lookup in the registry to use. This option should rarely be used, but allows to use different collection types than java.util.Collection based as default. | | String
-| *camel.dataformat.cbor.disable-features* | Set of features to disable on the Jackson com.fasterxml.jackson.databind.ObjectMapper. The features should be a name that matches a enum from com.fasterxml.jackson.databind.SerializationFeature, com.fasterxml.jackson.databind.DeserializationFeature, or com.fasterxml.jackson.databind.MapperFeature Multiple features can be separated by comma | | String
-| *camel.dataformat.cbor.enable-features* | Set of features to enable on the Jackson com.fasterxml.jackson.databind.ObjectMapper. The features should be a name that matches a enum from com.fasterxml.jackson.databind.SerializationFeature, com.fasterxml.jackson.databind.DeserializationFeature, or com.fasterxml.jackson.databind.MapperFeature Multiple features can be separated by comma | | String
-| *camel.dataformat.cbor.enabled* | Whether to enable auto configuration of the cbor data format. This is enabled by default. | | Boolean
-| *camel.dataformat.cbor.object-mapper* | Lookup and use the existing CBOR ObjectMapper with the given id when using Jackson. | | String
-| *camel.dataformat.cbor.pretty-print* | To enable pretty printing output nicely formatted. Is by default false. | false | Boolean
-| *camel.dataformat.cbor.unmarshal-type-name* | Class name of the java type to use when unmarshalling | | String
-| *camel.dataformat.cbor.use-default-object-mapper* | Whether to lookup and use default Jackson CBOR ObjectMapper from the registry. | true | Boolean
-| *camel.dataformat.cbor.use-list* | To unmarshal to a List of Map or a List of Pojo. | false | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-chatscript-starter/src/main/docs/chatscript-starter.adoc b/components-starter/camel-chatscript-starter/src/main/docs/chatscript-starter.adoc
deleted file mode 100644
index d82d5fb..0000000
--- a/components-starter/camel-chatscript-starter/src/main/docs/chatscript-starter.adoc
+++ /dev/null
@@ -1,31 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for chatscript
-
-== Spring Boot Auto-Configuration
-
-When using chatscript with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-chatscript-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 3 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.chatscript.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.chatscript.enabled* | Whether to enable auto configuration of the chatscript component. This is enabled by default. | | Boolean
-| *camel.component.chatscript.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-chunk-starter/src/main/docs/chunk-starter.adoc b/components-starter/camel-chunk-starter/src/main/docs/chunk-starter.adoc
deleted file mode 100644
index 3ec57a9..0000000
--- a/components-starter/camel-chunk-starter/src/main/docs/chunk-starter.adoc
+++ /dev/null
@@ -1,33 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for chunk
-
-== Spring Boot Auto-Configuration
-
-When using chunk with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-chunk-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 5 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.chunk.allow-context-map-all* | Sets whether the context map should allow access to all details. By default only the message body and headers can be accessed. This option can be enabled for full access to the current Exchange and CamelContext. Doing so impose a potential security risk as this opens access to the full power of CamelContext API. | false | Boolean
-| *camel.component.chunk.allow-template-from-header* | Whether to allow to use resource template from header or not (default false). Enabling this allows to specify dynamic templates via message header. However this can be seen as a potential security vulnerability if the header is coming from a malicious user, so use this with care. | false | Boolean
-| *camel.component.chunk.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.chunk.enabled* | Whether to enable auto configuration of the chunk component. This is enabled by default. | | Boolean
-| *camel.component.chunk.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-cm-sms-starter/src/main/docs/cm-sms-starter.adoc b/components-starter/camel-cm-sms-starter/src/main/docs/cm-sms-starter.adoc
deleted file mode 100644
index 27770d2..0000000
--- a/components-starter/camel-cm-sms-starter/src/main/docs/cm-sms-starter.adoc
+++ /dev/null
@@ -1,31 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for cm-sms
-
-== Spring Boot Auto-Configuration
-
-When using cm-sms with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-cm-sms-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 3 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.cm-sms.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.cm-sms.enabled* | Whether to enable auto configuration of the cm-sms component. This is enabled by default. | | Boolean
-| *camel.component.cm-sms.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed the [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-cmis-starter/src/main/docs/cmis-starter.adoc b/components-starter/camel-cmis-starter/src/main/docs/cmis-starter.adoc
deleted file mode 100644
index 9abb48c..0000000
--- a/components-starter/camel-cmis-starter/src/main/docs/cmis-starter.adoc
+++ /dev/null
@@ -1,33 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for cmis
-
-== Spring Boot Auto-Configuration
-
-When using cmis with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-cmis-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 5 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.cmis.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.cmis.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.cmis.enabled* | Whether to enable auto configuration of the cmis component. This is enabled by default. | | Boolean
-| *camel.component.cmis.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
-| *camel.component.cmis.session-facade-factory* | To use a custom CMISSessionFacadeFactory to create the CMISSessionFacade instances. The option is a org.apache.camel.component.cmis.CMISSessionFacadeFactory type. | | CMISSessionFacadeFactory
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-coap-starter/src/main/docs/coap-starter.adoc b/components-starter/camel-coap-starter/src/main/docs/coap-starter.adoc
deleted file mode 100644
index 79d3a89..0000000
--- a/components-starter/camel-coap-starter/src/main/docs/coap-starter.adoc
+++ /dev/null
@@ -1,32 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for coap
-
-== Spring Boot Auto-Configuration
-
-When using coap with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-coap-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 4 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.coap.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.coap.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.coap.enabled* | Whether to enable auto configuration of the coap component. This is enabled by default. | | Boolean
-| *camel.component.coap.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-cometd-starter/src/main/docs/cometd-starter.adoc b/components-starter/camel-cometd-starter/src/main/docs/cometd-starter.adoc
deleted file mode 100644
index 52985cd..0000000
--- a/components-starter/camel-cometd-starter/src/main/docs/cometd-starter.adoc
+++ /dev/null
@@ -1,39 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for cometd
-
-== Spring Boot Auto-Configuration
-
-When using cometd with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-cometd-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 11 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.cometd.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.cometd.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.cometd.enabled* | Whether to enable auto configuration of the cometd component. This is enabled by default. | | Boolean
-| *camel.component.cometd.extensions* | To use a list of custom BayeuxServer.Extension that allows modifying incoming and outgoing requests. | | List
-| *camel.component.cometd.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed the [...]
-| *camel.component.cometd.security-policy* | To use a custom configured SecurityPolicy to control authorization. The option is a org.cometd.bayeux.server.SecurityPolicy type. | | SecurityPolicy
-| *camel.component.cometd.ssl-context-parameters* | To configure security using SSLContextParameters. The option is a org.apache.camel.support.jsse.SSLContextParameters type. | | SSLContextParameters
-| *camel.component.cometd.ssl-key-password* | The password for the keystore when using SSL. | | String
-| *camel.component.cometd.ssl-keystore* | The path to the keystore. | | String
-| *camel.component.cometd.ssl-password* | The password when using SSL. | | String
-| *camel.component.cometd.use-global-ssl-context-parameters* | Enable usage of global SSL context parameters. | false | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-consul-starter/src/main/docs/consul-starter.adoc b/components-starter/camel-consul-starter/src/main/docs/consul-starter.adoc
deleted file mode 100644
index e92cdcc..0000000
--- a/components-starter/camel-consul-starter/src/main/docs/consul-starter.adoc
+++ /dev/null
@@ -1,118 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for consul
-
-== Spring Boot Auto-Configuration
-
-When using consul with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-consul-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 90 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.consul.acl-token* | Sets the ACL token to be used with Consul | | String
-| *camel.component.consul.action* | The default action. Can be overridden by CamelConsulAction | | String
-| *camel.component.consul.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.consul.block-seconds* | The second to wait for a watch event, default 10 seconds | 10 | Integer
-| *camel.component.consul.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.consul.cluster.service.acl-token* | Sets the ACL token to be used with Consul | | String
-| *camel.component.consul.cluster.service.attributes* | Custom service attributes. | | Map
-| *camel.component.consul.cluster.service.block-seconds* | The time (in seconds) to wait for a watch event, default 10 seconds | 10 | Integer
-| *camel.component.consul.cluster.service.connect-timeout* | Connect timeout for OkHttpClient | | Duration
-| *camel.component.consul.cluster.service.connect-timeout-millis* | Use connectTimeout instead | | Long
-| *camel.component.consul.cluster.service.consistency-mode* | The consistencyMode used for queries, default ConsistencyMode.DEFAULT | | ConsistencyMode
-| *camel.component.consul.cluster.service.datacenter* | The data center | | String
-| *camel.component.consul.cluster.service.enabled* | Sets if the consul cluster service should be enabled or not, default is false. | false | Boolean
-| *camel.component.consul.cluster.service.first-index* | The first index for watch for, default 0 | 0 | BigInteger
-| *camel.component.consul.cluster.service.id* | Cluster Service ID | | String
-| *camel.component.consul.cluster.service.near-node* | The near node to use for queries. | | String
-| *camel.component.consul.cluster.service.node-meta* | The note meta-data to use for queries. | | List
-| *camel.component.consul.cluster.service.order* | Service lookup order/priority. | | Integer
-| *camel.component.consul.cluster.service.password* | Sets the password to be used for basic authentication | | String
-| *camel.component.consul.cluster.service.ping-instance* | Configure if the AgentClient should attempt a ping before returning the Consul instance | true | Boolean
-| *camel.component.consul.cluster.service.read-timeout* | Read timeout for OkHttpClient | | Duration
-| *camel.component.consul.cluster.service.read-timeout-millis* | Use readTimeout instead. | | Long
-| *camel.component.consul.cluster.service.recursive* | Recursively watch, default false | false | Boolean
-| *camel.component.consul.cluster.service.root-path* | Consul root path | /camel | String
-| *camel.component.consul.cluster.service.session-lock-delay* | The value for lockDelay | 5 | Integer
-| *camel.component.consul.cluster.service.session-refresh-interval* | The value of wait attribute | 5 | Integer
-| *camel.component.consul.cluster.service.session-ttl* | The value of TTL | 60 | Integer
-| *camel.component.consul.cluster.service.ssl-context-parameters* | SSL configuration using an org.apache.camel.support.jsse.SSLContextParameters instance. | | SSLContextParameters
-| *camel.component.consul.cluster.service.tags* | Set tags. You can separate multiple tags by comma. | | Set
-| *camel.component.consul.cluster.service.url* | The Consul agent URL | | String
-| *camel.component.consul.cluster.service.user-name* | Sets the username to be used for basic authentication | | String
-| *camel.component.consul.cluster.service.write-timeout* | Write timeout for OkHttpClient | | Duration
-| *camel.component.consul.cluster.service.write-timeout-millis* | Use writeTimeout instead. | | Long
-| *camel.component.consul.configuration* | Consul configuration. The option is a org.apache.camel.component.consul.ConsulConfiguration type. | | ConsulConfiguration
-| *camel.component.consul.connect-timeout* | Connect timeout for OkHttpClient. The option is a java.time.Duration type. | | Duration
-| *camel.component.consul.consistency-mode* | The consistencyMode used for queries, default ConsistencyMode.DEFAULT | | ConsistencyMode
-| *camel.component.consul.consul-client* | Reference to a com.orbitz.consul.Consul in the registry. The option is a com.orbitz.consul.Consul type. | | Consul
-| *camel.component.consul.datacenter* | The data center | | String
-| *camel.component.consul.enabled* | Whether to enable auto configuration of the consul component. This is enabled by default. | | Boolean
-| *camel.component.consul.first-index* | The first index for watch for, default 0. The option is a java.math.BigInteger type. | | BigInteger
-| *camel.component.consul.key* | The default key. Can be overridden by CamelConsulKey | | String
-| *camel.component.consul.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed the [...]
-| *camel.component.consul.near-node* | The near node to use for queries. | | String
-| *camel.component.consul.node-meta* | The note meta-data to use for queries. | | List
-| *camel.component.consul.password* | Sets the password to be used for basic authentication | | String
-| *camel.component.consul.ping-instance* | Configure if the AgentClient should attempt a ping before returning the Consul instance | true | Boolean
-| *camel.component.consul.read-timeout* | Read timeout for OkHttpClient. The option is a java.time.Duration type. | | Duration
-| *camel.component.consul.recursive* | Recursively watch, default false | false | Boolean
-| *camel.component.consul.service-registry.acl-token* | Sets the ACL token to be used with Consul | | String
-| *camel.component.consul.service-registry.attributes* | Custom service attributes. | | Map
-| *camel.component.consul.service-registry.block-seconds* | The time (in seconds) to wait for a watch event, default 10 seconds | 10 | Integer
-| *camel.component.consul.service-registry.check-interval* | How often (in seconds) a service has to be marked as healthy if its check is TTL or how often the check should run. Default is 5 seconds. | 5 | Integer
-| *camel.component.consul.service-registry.check-ttl* | The time (in seconds) to live for TTL checks. Default is 1 minute. | 60 | Integer
-| *camel.component.consul.service-registry.connect-timeout* | Connect timeout for OkHttpClient | | Duration
-| *camel.component.consul.service-registry.connect-timeout-millis* | Use connectTimeout instead | | Long
-| *camel.component.consul.service-registry.consistency-mode* | The consistencyMode used for queries, default ConsistencyMode.DEFAULT | | ConsistencyMode
-| *camel.component.consul.service-registry.datacenter* | The data center | | String
-| *camel.component.consul.service-registry.deregister-after* | How long (in seconds) to wait to deregister a service in case of unclean shutdown. Default is 1 hour. | 3600 | Integer
-| *camel.component.consul.service-registry.deregister-services-on-stop* | Should we remove all the registered services know by this registry on stop? | true | Boolean
-| *camel.component.consul.service-registry.enabled* | Sets if the consul service registry should be enabled or not, default is false. | false | Boolean
-| *camel.component.consul.service-registry.first-index* | The first index for watch for, default 0 | 0 | BigInteger
-| *camel.component.consul.service-registry.id* | Service Registry ID | | String
-| *camel.component.consul.service-registry.near-node* | The near node to use for queries. | | String
-| *camel.component.consul.service-registry.node-meta* | The note meta-data to use for queries. | | List
-| *camel.component.consul.service-registry.order* | Service lookup order/priority. | | Integer
-| *camel.component.consul.service-registry.override-service-host* | Should we override the service host if given ? | true | Boolean
-| *camel.component.consul.service-registry.password* | Sets the password to be used for basic authentication | | String
-| *camel.component.consul.service-registry.ping-instance* | Configure if the AgentClient should attempt a ping before returning the Consul instance | true | Boolean
-| *camel.component.consul.service-registry.read-timeout* | Read timeout for OkHttpClient | | Duration
-| *camel.component.consul.service-registry.read-timeout-millis* | Use readTimeout instead. | | Long
-| *camel.component.consul.service-registry.recursive* | Recursively watch, default false | false | Boolean
-| *camel.component.consul.service-registry.service-host* | Service host. | | String
-| *camel.component.consul.service-registry.ssl-context-parameters* | SSL configuration using an org.apache.camel.support.jsse.SSLContextParameters instance. | | SSLContextParameters
-| *camel.component.consul.service-registry.tags* | Set tags. You can separate multiple tags by comma. | | Set
-| *camel.component.consul.service-registry.url* | The Consul agent URL | | String
-| *camel.component.consul.service-registry.user-name* | Sets the username to be used for basic authentication | | String
-| *camel.component.consul.service-registry.write-timeout* | Write timeout for OkHttpClient | | Duration
-| *camel.component.consul.service-registry.write-timeout-millis* | Use writeTimeout instead. | | Long
-| *camel.component.consul.ssl-context-parameters* | SSL configuration using an org.apache.camel.support.jsse.SSLContextParameters instance. The option is a org.apache.camel.support.jsse.SSLContextParameters type. | | SSLContextParameters
-| *camel.component.consul.tags* | Set tags. You can separate multiple tags by comma. | | String
-| *camel.component.consul.url* | The Consul agent URL | | String
-| *camel.component.consul.use-global-ssl-context-parameters* | Enable usage of global SSL context parameters. | false | Boolean
-| *camel.component.consul.user-name* | Sets the username to be used for basic authentication | | String
-| *camel.component.consul.value-as-string* | Default to transform values retrieved from Consul i.e. on KV endpoint to string. | false | Boolean
-| *camel.component.consul.write-timeout* | Write timeout for OkHttpClient. The option is a java.time.Duration type. | | Duration
-| *camel.component.consul.cluster.service.dc* | *Deprecated* Use datacenter instead | | String
-| *camel.component.consul.connect-timeout-millis* | *Deprecated* Connect timeout for OkHttpClient. Deprecation note: Use connectTimeout instead | | Long
-| *camel.component.consul.read-timeout-millis* | *Deprecated* Read timeout for OkHttpClient. Deprecation note: Use readTimeout instead | | Long
-| *camel.component.consul.service-registry.dc* | *Deprecated* Use datacenter instead | | String
-| *camel.component.consul.write-timeout-millis* | *Deprecated* Write timeout for OkHttpClient. Deprecation note: Use writeTimeout instead. The option is a java.lang.Long type. | | Long
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-controlbus-starter/src/main/docs/controlbus-starter.adoc b/components-starter/camel-controlbus-starter/src/main/docs/controlbus-starter.adoc
deleted file mode 100644
index 7b2770c..0000000
--- a/components-starter/camel-controlbus-starter/src/main/docs/controlbus-starter.adoc
+++ /dev/null
@@ -1,31 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for controlbus
-
-== Spring Boot Auto-Configuration
-
-When using controlbus with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-controlbus-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 3 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.controlbus.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.controlbus.enabled* | Whether to enable auto configuration of the controlbus component. This is enabled by default. | | Boolean
-| *camel.component.controlbus.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-corda-starter/src/main/docs/corda-starter.adoc b/components-starter/camel-corda-starter/src/main/docs/corda-starter.adoc
deleted file mode 100644
index 2d241eb..0000000
--- a/components-starter/camel-corda-starter/src/main/docs/corda-starter.adoc
+++ /dev/null
@@ -1,43 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for corda
-
-== Spring Boot Auto-Configuration
-
-When using corda with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-corda-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 15 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.corda.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.corda.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.corda.configuration* | To use a shared configuration. The option is a org.apache.camel.component.corda.CordaConfiguration type. | | CordaConfiguration
-| *camel.component.corda.contract-state-class* | A contract state (or just state) contains opaque data used by a contract program. It can be thought of as a disk file that the program can use to persist data across transactions. States are immutable: once created they are never updated, instead, any changes must generate a new successor state. States can be updated (consumed) only once: the notary is responsible for ensuring there is no double spending by only signing a transaction if th [...]
-| *camel.component.corda.enabled* | Whether to enable auto configuration of the corda component. This is enabled by default. | | Boolean
-| *camel.component.corda.flow-logic-arguments* | Start the given flow with the given arguments, returning an Observable with a single observation of the result of running the flow. The flowLogicClass must be annotated with net.corda.core.flows.StartableByRPC. | | Object[]
-| *camel.component.corda.flow-logic-class* | Start the given flow with the given arguments, returning an Observable with a single observation of the result of running the flow. The flowLogicClass must be annotated with net.corda.core.flows.StartableByRPC. | | Class
-| *camel.component.corda.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
-| *camel.component.corda.operation* | Operation to use | | String
-| *camel.component.corda.page-specification* | PageSpecification allows specification of a page number (starting from 1) and page size (defaulting to 200 with a maximum page size of (Integer.MAX_INT) Note: we default the page number to 200 to enable queries without requiring a page specification but enabling detection of large results sets that fall out of the 200 requirement. Max page size should be used with extreme caution as results may exceed your JVM memory footprint. The option is [...]
-| *camel.component.corda.password* | Password for login | | String
-| *camel.component.corda.process-snapshot* | Whether to process snapshots or not | true | Boolean
-| *camel.component.corda.query-criteria* | QueryCriteria assumes underlying schema tables are correctly indexed for performance. The option is a net.corda.core.node.services.vault.QueryCriteria type. | | QueryCriteria
-| *camel.component.corda.sort* | Sort allows specification of a set of entity attribute names and their associated directionality and null handling, to be applied upon processing a query specification. | | Sort
-| *camel.component.corda.username* | Username for login | | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-core-starter/src/main/docs/core-starter.adoc b/components-starter/camel-core-starter/src/main/docs/core-starter.adoc
deleted file mode 100644
index afa6a40..0000000
--- a/components-starter/camel-core-starter/src/main/docs/core-starter.adoc
+++ /dev/null
@@ -1,175 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for core
-
-== Spring Boot Auto-Configuration
-
-When using core with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-core-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 147 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.cloud.consul.service-discovery.acl-token* | Sets the ACL token to be used with Consul | | String
-| *camel.cloud.consul.service-discovery.block-seconds* | The seconds to wait for a watch event, default 10 seconds | 10 | Integer
-| *camel.cloud.consul.service-discovery.configurations* | Define additional configuration definitions | | Map
-| *camel.cloud.consul.service-discovery.connect-timeout-millis* | Connect timeout for OkHttpClient | | Long
-| *camel.cloud.consul.service-discovery.datacenter* | The data center | | String
-| *camel.cloud.consul.service-discovery.enabled* | Enable the component | true | Boolean
-| *camel.cloud.consul.service-discovery.password* | Sets the password to be used for basic authentication | | String
-| *camel.cloud.consul.service-discovery.properties* | Set client properties to use. These properties are specific to what service call implementation are in use. For example if using ribbon, then the client properties are define in com.netflix.client.config.CommonClientConfigKey. | | Map
-| *camel.cloud.consul.service-discovery.read-timeout-millis* | Read timeout for OkHttpClient | | Long
-| *camel.cloud.consul.service-discovery.url* | The Consul agent URL | | String
-| *camel.cloud.consul.service-discovery.user-name* | Sets the username to be used for basic authentication | | String
-| *camel.cloud.consul.service-discovery.write-timeout-millis* | Write timeout for OkHttpClient | | Long
-| *camel.cloud.dns.service-discovery.configurations* | Define additional configuration definitions | | Map
-| *camel.cloud.dns.service-discovery.domain* | The domain name; | | String
-| *camel.cloud.dns.service-discovery.enabled* | Enable the component | true | Boolean
-| *camel.cloud.dns.service-discovery.properties* | Set client properties to use. These properties are specific to what service call implementation are in use. For example if using ribbon, then the client properties are define in com.netflix.client.config.CommonClientConfigKey. | | Map
-| *camel.cloud.dns.service-discovery.proto* | The transport protocol of the desired service. | _tcp | String
-| *camel.cloud.etcd.service-discovery.configurations* | Define additional configuration definitions | | Map
-| *camel.cloud.etcd.service-discovery.enabled* | Enable the component | true | Boolean
-| *camel.cloud.etcd.service-discovery.password* | The password to use for basic authentication. | | String
-| *camel.cloud.etcd.service-discovery.properties* | Set client properties to use. These properties are specific to what service call implementation are in use. For example if using ribbon, then the client properties are define in com.netflix.client.config.CommonClientConfigKey. | | Map
-| *camel.cloud.etcd.service-discovery.service-path* | The path to look for for service discovery | /services/ | String
-| *camel.cloud.etcd.service-discovery.timeout* | To set the maximum time an action could take to complete. | | Long
-| *camel.cloud.etcd.service-discovery.type* | To set the discovery type, valid values are on-demand and watch. | on-demand | String
-| *camel.cloud.etcd.service-discovery.uris* | The URIs the client can connect to. | | String
-| *camel.cloud.etcd.service-discovery.user-name* | The user name to use for basic authentication. | | String
-| *camel.cloud.kubernetes.service-discovery.api-version* | Sets the API version when using client lookup | | String
-| *camel.cloud.kubernetes.service-discovery.ca-cert-data* | Sets the Certificate Authority data when using client lookup | | String
-| *camel.cloud.kubernetes.service-discovery.ca-cert-file* | Sets the Certificate Authority data that are loaded from the file when using client lookup | | String
-| *camel.cloud.kubernetes.service-discovery.client-cert-data* | Sets the Client Certificate data when using client lookup | | String
-| *camel.cloud.kubernetes.service-discovery.client-cert-file* | Sets the Client Certificate data that are loaded from the file when using client lookup | | String
-| *camel.cloud.kubernetes.service-discovery.client-key-algo* | Sets the Client Keystore algorithm, such as RSA when using client lookup | | String
-| *camel.cloud.kubernetes.service-discovery.client-key-data* | Sets the Client Keystore data when using client lookup | | String
-| *camel.cloud.kubernetes.service-discovery.client-key-file* | Sets the Client Keystore data that are loaded from the file when using client lookup | | String
-| *camel.cloud.kubernetes.service-discovery.client-key-passphrase* | Sets the Client Keystore passphrase when using client lookup | | String
-| *camel.cloud.kubernetes.service-discovery.configurations* | Define additional configuration definitions | | Map
-| *camel.cloud.kubernetes.service-discovery.dns-domain* | Sets the DNS domain to use for DNS lookup. | | String
-| *camel.cloud.kubernetes.service-discovery.enabled* | Enable the component | true | Boolean
-| *camel.cloud.kubernetes.service-discovery.lookup* | How to perform service lookup. Possible values: client, dns, environment. When using client, then the client queries the kubernetes master to obtain a list of active pods that provides the service, and then random (or round robin) select a pod. When using dns the service name is resolved as name.namespace.svc.dnsDomain. When using dnssrv the service name is resolved with SRV query for _._...svc... When using environment then environme [...]
-| *camel.cloud.kubernetes.service-discovery.master-url* | Sets the URL to the master when using client lookup | | String
-| *camel.cloud.kubernetes.service-discovery.namespace* | Sets the namespace to use. Will by default use namespace from the ENV variable KUBERNETES_MASTER. | | String
-| *camel.cloud.kubernetes.service-discovery.oauth-token* | Sets the OAUTH token for authentication (instead of username/password) when using client lookup | | String
-| *camel.cloud.kubernetes.service-discovery.password* | Sets the password for authentication when using client lookup | | String
-| *camel.cloud.kubernetes.service-discovery.port-name* | Sets the Port Name to use for DNS/DNSSRV lookup. | | String
-| *camel.cloud.kubernetes.service-discovery.port-protocol* | Sets the Port Protocol to use for DNS/DNSSRV lookup. | | String
-| *camel.cloud.kubernetes.service-discovery.properties* | Set client properties to use. These properties are specific to what service call implementation are in use. For example if using ribbon, then the client properties are define in com.netflix.client.config.CommonClientConfigKey. | | Map
-| *camel.cloud.kubernetes.service-discovery.trust-certs* | Sets whether to turn on trust certificate check when using client lookup | false | Boolean
-| *camel.cloud.kubernetes.service-discovery.username* | Sets the username for authentication when using client lookup | | String
-| *camel.cloud.ribbon.load-balancer.client-name* | Sets the Ribbon client name | | String
-| *camel.cloud.ribbon.load-balancer.configurations* | Define additional configuration definitions | | Map
-| *camel.cloud.ribbon.load-balancer.enabled* | Enable the component | true | Boolean
-| *camel.cloud.ribbon.load-balancer.namespace* | The namespace | | String
-| *camel.cloud.ribbon.load-balancer.password* | The password | | String
-| *camel.cloud.ribbon.load-balancer.properties* | Set client properties to use. These properties are specific to what service call implementation are in use. For example if using ribbon, then the client properties are define in com.netflix.client.config.CommonClientConfigKey. | | Map
-| *camel.cloud.ribbon.load-balancer.username* | The username | | String
-| *camel.hystrix.allow-maximum-size-to-diverge-from-core-size* | Allows the configuration for maximumSize to take effect. That value can then be equal to, or higher, than coreSize | false | Boolean
-| *camel.hystrix.circuit-breaker-enabled* | Whether to use a HystrixCircuitBreaker or not. If false no circuit-breaker logic will be used and all requests permitted. This is similar in effect to circuitBreakerForceClosed() except that continues tracking metrics and knowing whether it should be open/closed, this property results in not even instantiating a circuit-breaker. | true | Boolean
-| *camel.hystrix.circuit-breaker-error-threshold-percentage* | Error percentage threshold (as whole number such as 50) at which point the circuit breaker will trip open and reject requests. It will stay tripped for the duration defined in circuitBreakerSleepWindowInMilliseconds; The error percentage this is compared against comes from HystrixCommandMetrics.getHealthCounts(). | 50 | Integer
-| *camel.hystrix.circuit-breaker-force-closed* | If true the HystrixCircuitBreaker#allowRequest() will always return true to allow requests regardless of the error percentage from HystrixCommandMetrics.getHealthCounts(). The circuitBreakerForceOpen() property takes precedence so if it set to true this property does nothing. | false | Boolean
-| *camel.hystrix.circuit-breaker-force-open* | If true the HystrixCircuitBreaker.allowRequest() will always return false, causing the circuit to be open (tripped) and reject all requests. This property takes precedence over circuitBreakerForceClosed(); | false | Boolean
-| *camel.hystrix.circuit-breaker-request-volume-threshold* | Minimum number of requests in the metricsRollingStatisticalWindowInMilliseconds() that must exist before the HystrixCircuitBreaker will trip. If below this number the circuit will not trip regardless of error percentage. | 20 | Integer
-| *camel.hystrix.circuit-breaker-sleep-window-in-milliseconds* | The time in milliseconds after a HystrixCircuitBreaker trips open that it should wait before trying requests again. | 5000 | Integer
-| *camel.hystrix.configurations* | Define additional configuration definitions | | Map
-| *camel.hystrix.core-pool-size* | Core thread-pool size that gets passed to java.util.concurrent.ThreadPoolExecutor#setCorePoolSize(int) | 10 | Integer
-| *camel.hystrix.enabled* | Enable the component | true | Boolean
-| *camel.hystrix.execution-isolation-semaphore-max-concurrent-requests* | Number of concurrent requests permitted to HystrixCommand.run(). Requests beyond the concurrent limit will be rejected. Applicable only when executionIsolationStrategy == SEMAPHORE. | 20 | Integer
-| *camel.hystrix.execution-isolation-strategy* | What isolation strategy HystrixCommand.run() will be executed with. If THREAD then it will be executed on a separate thread and concurrent requests limited by the number of threads in the thread-pool. If SEMAPHORE then it will be executed on the calling thread and concurrent requests limited by the semaphore count. | THREAD | String
-| *camel.hystrix.execution-isolation-thread-interrupt-on-timeout* | Whether the execution thread should attempt an interrupt (using Future#cancel ) when a thread times out. Applicable only when executionIsolationStrategy() == THREAD. | true | Boolean
-| *camel.hystrix.execution-timeout-enabled* | Whether the timeout mechanism is enabled for this command | true | Boolean
-| *camel.hystrix.execution-timeout-in-milliseconds* | Time in milliseconds at which point the command will timeout and halt execution. If executionIsolationThreadInterruptOnTimeout == true and the command is thread-isolated, the executing thread will be interrupted. If the command is semaphore-isolated and a HystrixObservableCommand, that command will get unsubscribed. | 1000 | Integer
-| *camel.hystrix.fallback-enabled* | Whether HystrixCommand.getFallback() should be attempted when failure occurs. | true | Boolean
-| *camel.hystrix.fallback-isolation-semaphore-max-concurrent-requests* | Number of concurrent requests permitted to HystrixCommand.getFallback(). Requests beyond the concurrent limit will fail-fast and not attempt retrieving a fallback. | 10 | Integer
-| *camel.hystrix.group-key* | Sets the group key to use. The default value is CamelHystrix. | CamelHystrix | String
-| *camel.hystrix.keep-alive-time* | Keep-alive time in minutes that gets passed to ThreadPoolExecutor#setKeepAliveTime(long,TimeUnit) | 1 | Integer
-| *camel.hystrix.max-queue-size* | Max queue size that gets passed to BlockingQueue in HystrixConcurrencyStrategy.getBlockingQueue(int) This should only affect the instantiation of a threadpool - it is not eliglible to change a queue size on the fly. For that, use queueSizeRejectionThreshold(). | -1 | Integer
-| *camel.hystrix.maximum-size* | Maximum thread-pool size that gets passed to ThreadPoolExecutor#setMaximumPoolSize(int) . This is the maximum amount of concurrency that can be supported without starting to reject HystrixCommands. Please note that this setting only takes effect if you also set allowMaximumSizeToDivergeFromCoreSize | 10 | Integer
-| *camel.hystrix.metrics-health-snapshot-interval-in-milliseconds* | Time in milliseconds to wait between allowing health snapshots to be taken that calculate success and error percentages and affect HystrixCircuitBreaker.isOpen() status. On high-volume circuits the continual calculation of error percentage can become CPU intensive thus this controls how often it is calculated. | 500 | Integer
-| *camel.hystrix.metrics-rolling-percentile-bucket-size* | Maximum number of values stored in each bucket of the rolling percentile. This is passed into HystrixRollingPercentile inside HystrixCommandMetrics. | 10 | Integer
-| *camel.hystrix.metrics-rolling-percentile-enabled* | Whether percentile metrics should be captured using HystrixRollingPercentile inside HystrixCommandMetrics. | true | Boolean
-| *camel.hystrix.metrics-rolling-percentile-window-buckets* | Number of buckets the rolling percentile window is broken into. This is passed into HystrixRollingPercentile inside HystrixCommandMetrics. | 6 | Integer
-| *camel.hystrix.metrics-rolling-percentile-window-in-milliseconds* | Duration of percentile rolling window in milliseconds. This is passed into HystrixRollingPercentile inside HystrixCommandMetrics. | 10000 | Integer
-| *camel.hystrix.metrics-rolling-statistical-window-buckets* | Number of buckets the rolling statistical window is broken into. This is passed into HystrixRollingNumber inside HystrixCommandMetrics. | 10 | Integer
-| *camel.hystrix.metrics-rolling-statistical-window-in-milliseconds* | This property sets the duration of the statistical rolling window, in milliseconds. This is how long metrics are kept for the thread pool. The window is divided into buckets and rolls by those increments. | 10000 | Integer
-| *camel.hystrix.queue-size-rejection-threshold* | Queue size rejection threshold is an artificial max size at which rejections will occur even if maxQueueSize has not been reached. This is done because the maxQueueSize of a BlockingQueue can not be dynamically changed and we want to support dynamically changing the queue size that affects rejections. This is used by HystrixCommand when queuing a thread for execution. | 5 | Integer
-| *camel.hystrix.request-log-enabled* | Whether HystrixCommand execution and events should be logged to HystrixRequestLog. | true | Boolean
-| *camel.hystrix.thread-pool-key* | Sets the thread pool key to use. Will by default use the same value as groupKey has been configured to use. | CamelHystrix | String
-| *camel.hystrix.thread-pool-rolling-number-statistical-window-buckets* | Number of buckets the rolling statistical window is broken into. This is passed into HystrixRollingNumber inside each HystrixThreadPoolMetrics instance. | 10 | Integer
-| *camel.hystrix.thread-pool-rolling-number-statistical-window-in-milliseconds* | Duration of statistical rolling window in milliseconds. This is passed into HystrixRollingNumber inside each HystrixThreadPoolMetrics instance. | 10000 | Integer
-| *camel.language.constant.enabled* | Whether to enable auto configuration of the constant language. This is enabled by default. | | Boolean
-| *camel.language.constant.trim* | Whether to trim the value to remove leading and trailing whitespaces and line breaks | true | Boolean
-| *camel.language.csimple.enabled* | Whether to enable auto configuration of the csimple language. This is enabled by default. | | Boolean
-| *camel.language.csimple.trim* | Whether to trim the value to remove leading and trailing whitespaces and line breaks | true | Boolean
-| *camel.language.exchangeproperty.enabled* | Whether to enable auto configuration of the exchangeProperty language. This is enabled by default. | | Boolean
-| *camel.language.exchangeproperty.trim* | Whether to trim the value to remove leading and trailing whitespaces and line breaks | true | Boolean
-| *camel.language.file.enabled* | Whether to enable auto configuration of the file language. This is enabled by default. | | Boolean
-| *camel.language.file.trim* | Whether to trim the value to remove leading and trailing whitespaces and line breaks | true | Boolean
-| *camel.language.header.enabled* | Whether to enable auto configuration of the header language. This is enabled by default. | | Boolean
-| *camel.language.header.trim* | Whether to trim the value to remove leading and trailing whitespaces and line breaks | true | Boolean
-| *camel.language.ref.enabled* | Whether to enable auto configuration of the ref language. This is enabled by default. | | Boolean
-| *camel.language.ref.trim* | Whether to trim the value to remove leading and trailing whitespaces and line breaks | true | Boolean
-| *camel.language.simple.enabled* | Whether to enable auto configuration of the simple language. This is enabled by default. | | Boolean
-| *camel.language.simple.trim* | Whether to trim the value to remove leading and trailing whitespaces and line breaks | true | Boolean
-| *camel.language.tokenize.enabled* | Whether to enable auto configuration of the tokenize language. This is enabled by default. | | Boolean
-| *camel.language.tokenize.group-delimiter* | Sets the delimiter to use when grouping. If this has not been set then token will be used as the delimiter. | | String
-| *camel.language.tokenize.trim* | Whether to trim the value to remove leading and trailing whitespaces and line breaks | true | Boolean
-| *camel.resilience4j.automatic-transition-from-open-to-half-open-enabled* | Enables automatic transition from OPEN to HALF_OPEN state once the waitDurationInOpenState has passed. | false | Boolean
-| *camel.resilience4j.circuit-breaker-ref* | Refers to an existing io.github.resilience4j.circuitbreaker.CircuitBreaker instance to lookup and use from the registry. When using this, then any other circuit breaker options are not in use. | | String
-| *camel.resilience4j.config-ref* | Refers to an existing io.github.resilience4j.circuitbreaker.CircuitBreakerConfig instance to lookup and use from the registry. | | String
-| *camel.resilience4j.configurations* | Define additional configuration definitions | | Map
-| *camel.resilience4j.enabled* | Enable the component | true | Boolean
-| *camel.resilience4j.failure-rate-threshold* | Configures the failure rate threshold in percentage. If the failure rate is equal or greater than the threshold the CircuitBreaker transitions to open and starts short-circuiting calls. The threshold must be greater than 0 and not greater than 100. Default value is 50 percentage. | | Float
-| *camel.resilience4j.minimum-number-of-calls* | Configures the minimum number of calls which are required (per sliding window period) before the CircuitBreaker can calculate the error rate. For example, if minimumNumberOfCalls is 10, then at least 10 calls must be recorded, before the failure rate can be calculated. If only 9 calls have been recorded the CircuitBreaker will not transition to open even if all 9 calls have failed. Default minimumNumberOfCalls is 100 | 100 | Integer
-| *camel.resilience4j.permitted-number-of-calls-in-half-open-state* | Configures the number of permitted calls when the CircuitBreaker is half open. The size must be greater than 0. Default size is 10. | 10 | Integer
-| *camel.resilience4j.sliding-window-size* | Configures the size of the sliding window which is used to record the outcome of calls when the CircuitBreaker is closed. slidingWindowSize configures the size of the sliding window. Sliding window can either be count-based or time-based. If slidingWindowType is COUNT_BASED, the last slidingWindowSize calls are recorded and aggregated. If slidingWindowType is TIME_BASED, the calls of the last slidingWindowSize seconds are recorded and aggregat [...]
-| *camel.resilience4j.sliding-window-type* | Configures the type of the sliding window which is used to record the outcome of calls when the CircuitBreaker is closed. Sliding window can either be count-based or time-based. If slidingWindowType is COUNT_BASED, the last slidingWindowSize calls are recorded and aggregated. If slidingWindowType is TIME_BASED, the calls of the last slidingWindowSize seconds are recorded and aggregated. Default slidingWindowType is COUNT_BASED. | COUNT_BASED | String
-| *camel.resilience4j.slow-call-duration-threshold* | Configures the duration threshold (seconds) above which calls are considered as slow and increase the slow calls percentage. Default value is 60 seconds. | 60 | Integer
-| *camel.resilience4j.slow-call-rate-threshold* | Configures a threshold in percentage. The CircuitBreaker considers a call as slow when the call duration is greater than slowCallDurationThreshold Duration. When the percentage of slow calls is equal or greater the threshold, the CircuitBreaker transitions to open and starts short-circuiting calls. The threshold must be greater than 0 and not greater than 100. Default value is 100 percentage which means that all recorded calls must be slo [...]
-| *camel.resilience4j.wait-duration-in-open-state* | Configures the wait duration (in seconds) which specifies how long the CircuitBreaker should stay open, before it switches to half open. Default value is 60 seconds. | 60 | Integer
-| *camel.resilience4j.writable-stack-trace-enabled* | Enables writable stack traces. When set to false, Exception.getStackTrace returns a zero length array. This may be used to reduce log spam when the circuit breaker is open as the cause of the exceptions is already known (the circuit breaker is short-circuiting calls). | true | Boolean
-| *camel.rest.api-component* | The name of the Camel component to use as the REST API (such as swagger) If no API Component has been explicit configured, then Camel will lookup if there is a Camel component responsible for servicing and generating the REST API documentation, or if a org.apache.camel.spi.RestApiProcessorFactory is registered in the registry. If either one is found, then that is being used. | | String
-| *camel.rest.api-context-id-pattern* | Sets an CamelContext id pattern to only allow Rest APIs from rest services within CamelContext's which name matches the pattern. The pattern #name# refers to the CamelContext name, to match on the current CamelContext only. For any other value, the pattern uses the rules from PatternHelper#matchPattern(String,String) | | String
-| *camel.rest.api-context-listing* | Sets whether listing of all available CamelContext's with REST services in the JVM is enabled. If enabled it allows to discover these contexts, if false then only the current CamelContext is in use. | false | Boolean
-| *camel.rest.api-context-path* | Sets a leading API context-path the REST API services will be using. This can be used when using components such as camel-servlet where the deployed web application is deployed using a context-path. | | String
-| *camel.rest.api-context-route-id* | Sets the route id to use for the route that services the REST API. The route will by default use an auto assigned route id. | | String
-| *camel.rest.api-host* | To use an specific hostname for the API documentation (eg swagger) This can be used to override the generated host with this configured hostname | | String
-| *camel.rest.api-property* | Allows to configure as many additional properties for the api documentation (swagger). For example set property api.title to my cool stuff | | Map
-| *camel.rest.api-vendor-extension* | Whether vendor extension is enabled in the Rest APIs. If enabled then Camel will include additional information as vendor extension (eg keys starting with x-) such as route ids, class names etc. Not all 3rd party API gateways and tools supports vendor-extensions when importing your API docs. | false | Boolean
-| *camel.rest.binding-mode* | Sets the binding mode to use. The default value is off | | RestBindingMode
-| *camel.rest.client-request-validation* | Whether to enable validation of the client request to check whether the Content-Type and Accept headers from the client is supported by the Rest-DSL configuration of its consumes/produces settings. This can be turned on, to enable this check. In case of validation error, then HTTP Status codes 415 or 406 is returned. The default value is false. | false | Boolean
-| *camel.rest.component* | The Camel Rest component to use for the REST transport (consumer), such as netty-http, jetty, servlet, undertow. If no component has been explicit configured, then Camel will lookup if there is a Camel component that integrates with the Rest DSL, or if a org.apache.camel.spi.RestConsumerFactory is registered in the registry. If either one is found, then that is being used. | | String
-| *camel.rest.component-property* | Allows to configure as many additional properties for the rest component in use. | | Map
-| *camel.rest.consumer-property* | Allows to configure as many additional properties for the rest consumer in use. | | Map
-| *camel.rest.context-path* | Sets a leading context-path the REST services will be using. This can be used when using components such as camel-servlet where the deployed web application is deployed using a context-path. Or for components such as camel-jetty or camel-netty-http that includes a HTTP server. | | String
-| *camel.rest.cors-headers* | Allows to configure custom CORS headers. | | Map
-| *camel.rest.data-format-property* | Allows to configure as many additional properties for the data formats in use. For example set property prettyPrint to true to have json outputted in pretty mode. The properties can be prefixed to denote the option is only for either JSON or XML and for either the IN or the OUT. The prefixes are: json.in. json.out. xml.in. xml.out. For example a key with value xml.out.mustBeJAXBElement is only for the XML data format for the outgoing. A key without a [...]
-| *camel.rest.enable-cors* | Whether to enable CORS headers in the HTTP response. The default value is false. | false | Boolean
-| *camel.rest.endpoint-property* | Allows to configure as many additional properties for the rest endpoint in use. | | Map
-| *camel.rest.host* | The hostname to use for exposing the REST service. | | String
-| *camel.rest.host-name-resolver* | If no hostname has been explicit configured, then this resolver is used to compute the hostname the REST service will be using. | | RestHostNameResolver
-| *camel.rest.json-data-format* | Name of specific json data format to use. By default json-jackson will be used. Important: This option is only for setting a custom name of the data format, not to refer to an existing data format instance. | | String
-| *camel.rest.port* | The port number to use for exposing the REST service. Notice if you use servlet component then the port number configured here does not apply, as the port number in use is the actual port number the servlet component is using. eg if using Apache Tomcat its the tomcat http port, if using Apache Karaf its the HTTP service in Karaf that uses port 8181 by default etc. Though in those situations setting the port number here, allows tooling and JMX to know the port number [...]
-| *camel.rest.producer-api-doc* | Sets the location of the api document (swagger api) the REST producer will use to validate the REST uri and query parameters are valid accordingly to the api document. This requires adding camel-swagger-java to the classpath, and any miss configuration will let Camel fail on startup and report the error(s). The location of the api document is loaded from classpath by default, but you can use file: or http: to refer to resources to load from file or http [...]
-| *camel.rest.producer-component* | Sets the name of the Camel component to use as the REST producer | | String
-| *camel.rest.scheme* | The scheme to use for exposing the REST service. Usually http or https is supported. The default value is http | | String
-| *camel.rest.skip-binding-on-error-code* | Whether to skip binding on output if there is a custom HTTP error code header. This allows to build custom error messages that do not bind to json / xml etc, as success messages otherwise will do. | false | Boolean
-| *camel.rest.use-x-forward-headers* | Whether to use X-Forward headers for Host and related setting. The default value is true. | true | Boolean
-| *camel.rest.xml-data-format* | Name of specific XML data format to use. By default jaxb will be used. Important: This option is only for setting a custom name of the data format, not to refer to an existing data format instance. | | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-couchbase-starter/src/main/docs/couchbase-starter.adoc b/components-starter/camel-couchbase-starter/src/main/docs/couchbase-starter.adoc
deleted file mode 100644
index 98a66ed..0000000
--- a/components-starter/camel-couchbase-starter/src/main/docs/couchbase-starter.adoc
+++ /dev/null
@@ -1,32 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for couchbase
-
-== Spring Boot Auto-Configuration
-
-When using couchbase with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-couchbase-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 4 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.couchbase.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.couchbase.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.couchbase.enabled* | Whether to enable auto configuration of the couchbase component. This is enabled by default. | | Boolean
-| *camel.component.couchbase.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-couchdb-starter/src/main/docs/couchdb-starter.adoc b/components-starter/camel-couchdb-starter/src/main/docs/couchdb-starter.adoc
deleted file mode 100644
index a1e342c..0000000
--- a/components-starter/camel-couchdb-starter/src/main/docs/couchdb-starter.adoc
+++ /dev/null
@@ -1,32 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for couchdb
-
-== Spring Boot Auto-Configuration
-
-When using couchdb with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-couchdb-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 4 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.couchdb.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.couchdb.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.couchdb.enabled* | Whether to enable auto configuration of the couchdb component. This is enabled by default. | | Boolean
-| *camel.component.couchdb.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-cron-starter/src/main/docs/cron-starter.adoc b/components-starter/camel-cron-starter/src/main/docs/cron-starter.adoc
deleted file mode 100644
index 9194bc5..0000000
--- a/components-starter/camel-cron-starter/src/main/docs/cron-starter.adoc
+++ /dev/null
@@ -1,32 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for cron
-
-== Spring Boot Auto-Configuration
-
-When using cron with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-cron-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 4 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.cron.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.cron.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.cron.cron-service* | The id of the CamelCronService to use when multiple implementations are provided | | String
-| *camel.component.cron.enabled* | Whether to enable auto configuration of the cron component. This is enabled by default. | | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-crypto-cms-starter/src/main/docs/crypto-cms-starter.adoc b/components-starter/camel-crypto-cms-starter/src/main/docs/crypto-cms-starter.adoc
deleted file mode 100644
index 7a1b82c..0000000
--- a/components-starter/camel-crypto-cms-starter/src/main/docs/crypto-cms-starter.adoc
+++ /dev/null
@@ -1,33 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for crypto-cms
-
-== Spring Boot Auto-Configuration
-
-When using crypto-cms with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-crypto-cms-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 5 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.crypto-cms.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.crypto-cms.enabled* | Whether to enable auto configuration of the crypto-cms component. This is enabled by default. | | Boolean
-| *camel.component.crypto-cms.enveloped-data-decryptor-configuration* | To configure the shared EnvelopedDataDecryptorConfiguration, which determines the uri parameters for the decrypt operation. The option is a org.apache.camel.component.crypto.cms.crypt.EnvelopedDataDecryptorConfiguration type. | | EnvelopedDataDecryptorConfiguration
-| *camel.component.crypto-cms.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed [...]
-| *camel.component.crypto-cms.signed-data-verifier-configuration* | To configure the shared SignedDataVerifierConfiguration, which determines the uri parameters for the verify operation. The option is a org.apache.camel.component.crypto.cms.sig.SignedDataVerifierConfiguration type. | | SignedDataVerifierConfiguration
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-crypto-starter/src/main/docs/crypto-starter.adoc b/components-starter/camel-crypto-starter/src/main/docs/crypto-starter.adoc
deleted file mode 100644
index d2e77a1..0000000
--- a/components-starter/camel-crypto-starter/src/main/docs/crypto-starter.adoc
+++ /dev/null
@@ -1,75 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for crypto
-
-== Spring Boot Auto-Configuration
-
-When using crypto with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-crypto-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 47 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.crypto.algorithm* | Sets the JCE name of the Algorithm that should be used for the signer. | SHA256withRSA | String
-| *camel.component.crypto.alias* | Sets the alias used to query the KeyStore for keys and {link java.security.cert.Certificate Certificates} to be used in signing and verifying exchanges. This value can be provided at runtime via the message header org.apache.camel.component.crypto.DigitalSignatureConstants#KEYSTORE_ALIAS | | String
-| *camel.component.crypto.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.crypto.buffer-size* | Set the size of the buffer used to read in the Exchange payload data. | 2048 | Integer
-| *camel.component.crypto.certificate* | Set the Certificate that should be used to verify the signature in the exchange based on its payload. The option is a java.security.cert.Certificate type. | | Certificate
-| *camel.component.crypto.certificate-name* | Sets the reference name for a PrivateKey that can be found in the registry. | | String
-| *camel.component.crypto.clear-headers* | Determines if the Signature specific headers be cleared after signing and verification. Defaults to true, and should only be made otherwise at your extreme peril as vital private information such as Keys and passwords may escape if unset. | true | Boolean
-| *camel.component.crypto.configuration* | To use the shared DigitalSignatureConfiguration as configuration. The option is a org.apache.camel.component.crypto.DigitalSignatureConfiguration type. | | DigitalSignatureConfiguration
-| *camel.component.crypto.enabled* | Whether to enable auto configuration of the crypto component. This is enabled by default. | | Boolean
-| *camel.component.crypto.key-store-parameters* | Sets the KeyStore that can contain keys and Certficates for use in signing and verifying exchanges based on the given KeyStoreParameters. A KeyStore is typically used with an alias, either one supplied in the Route definition or dynamically via the message header CamelSignatureKeyStoreAlias. If no alias is supplied and there is only a single entry in the Keystore, then this single entry will be used. The option is a org.apache.camel.suppo [...]
-| *camel.component.crypto.keystore* | Sets the KeyStore that can contain keys and Certficates for use in signing and verifying exchanges. A KeyStore is typically used with an alias, either one supplied in the Route definition or dynamically via the message header CamelSignatureKeyStoreAlias. If no alias is supplied and there is only a single entry in the Keystore, then this single entry will be used. The option is a java.security.KeyStore type. | | KeyStore
-| *camel.component.crypto.keystore-name* | Sets the reference name for a Keystore that can be found in the registry. | | String
-| *camel.component.crypto.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed the [...]
-| *camel.component.crypto.password* | Sets the password used to access an aliased PrivateKey in the KeyStore. | | String
-| *camel.component.crypto.private-key* | Set the PrivateKey that should be used to sign the exchange. The option is a java.security.PrivateKey type. | | PrivateKey
-| *camel.component.crypto.private-key-name* | Sets the reference name for a PrivateKey that can be found in the registry. | | String
-| *camel.component.crypto.provider* | Set the id of the security provider that provides the configured Signature algorithm. | | String
-| *camel.component.crypto.public-key* | Set the PublicKey that should be used to verify the signature in the exchange. The option is a java.security.PublicKey type. | | PublicKey
-| *camel.component.crypto.public-key-name* | references that should be resolved when the context changes | | String
-| *camel.component.crypto.secure-random* | Set the SecureRandom used to initialize the Signature service. The option is a java.security.SecureRandom type. | | SecureRandom
-| *camel.component.crypto.secure-random-name* | Sets the reference name for a SecureRandom that can be found in the registry. | | String
-| *camel.component.crypto.signature-header-name* | Set the name of the message header that should be used to store the base64 encoded signature. This defaults to 'CamelDigitalSignature' | | String
-| *camel.dataformat.crypto.algorithm* | The JCE algorithm name indicating the cryptographic algorithm that will be used. | | String
-| *camel.dataformat.crypto.algorithm-parameter-ref* | A JCE AlgorithmParameterSpec used to initialize the Cipher. Will lookup the type using the given name as a java.security.spec.AlgorithmParameterSpec type. | | String
-| *camel.dataformat.crypto.buffersize* | The size of the buffer used in the signature process. | | Integer
-| *camel.dataformat.crypto.crypto-provider* | The name of the JCE Security Provider that should be used. | | String
-| *camel.dataformat.crypto.enabled* | Whether to enable auto configuration of the crypto data format. This is enabled by default. | | Boolean
-| *camel.dataformat.crypto.init-vector-ref* | Refers to a byte array containing the Initialization Vector that will be used to initialize the Cipher. | | String
-| *camel.dataformat.crypto.inline* | Flag indicating that the configured IV should be inlined into the encrypted data stream. Is by default false. | false | Boolean
-| *camel.dataformat.crypto.key-ref* | Refers to the secret key to lookup from the register to use. | | String
-| *camel.dataformat.crypto.mac-algorithm* | The JCE algorithm name indicating the Message Authentication algorithm. | HmacSHA1 | String
-| *camel.dataformat.crypto.should-append-h-m-a-c* | Flag indicating that a Message Authentication Code should be calculated and appended to the encrypted data. | true | Boolean
-| *camel.dataformat.pgp.algorithm* | Symmetric key encryption algorithm; possible values are defined in org.bouncycastle.bcpg.SymmetricKeyAlgorithmTags; for example 2 (= TRIPLE DES), 3 (= CAST5), 4 (= BLOWFISH), 6 (= DES), 7 (= AES_128). Only relevant for encrypting. | | Integer
-| *camel.dataformat.pgp.armored* | This option will cause PGP to base64 encode the encrypted text, making it available for copy/paste, etc. | false | Boolean
-| *camel.dataformat.pgp.compression-algorithm* | Compression algorithm; possible values are defined in org.bouncycastle.bcpg.CompressionAlgorithmTags; for example 0 (= UNCOMPRESSED), 1 (= ZIP), 2 (= ZLIB), 3 (= BZIP2). Only relevant for encrypting. | | Integer
-| *camel.dataformat.pgp.enabled* | Whether to enable auto configuration of the pgp data format. This is enabled by default. | | Boolean
-| *camel.dataformat.pgp.hash-algorithm* | Signature hash algorithm; possible values are defined in org.bouncycastle.bcpg.HashAlgorithmTags; for example 2 (= SHA1), 8 (= SHA256), 9 (= SHA384), 10 (= SHA512), 11 (=SHA224). Only relevant for signing. | | Integer
-| *camel.dataformat.pgp.integrity* | Adds an integrity check/sign into the encryption file. The default value is true. | true | Boolean
-| *camel.dataformat.pgp.key-file-name* | Filename of the keyring; must be accessible as a classpath resource (but you can specify a location in the file system by using the file: prefix). | | String
-| *camel.dataformat.pgp.key-userid* | The user ID of the key in the PGP keyring used during encryption. Can also be only a part of a user ID. For example, if the user ID is Test User then you can use the part Test User or to address the user ID. | | String
-| *camel.dataformat.pgp.password* | Password used when opening the private key (not used for encryption). | | String
-| *camel.dataformat.pgp.provider* | Java Cryptography Extension (JCE) provider, default is Bouncy Castle (BC). Alternatively you can use, for example, the IAIK JCE provider; in this case the provider must be registered beforehand and the Bouncy Castle provider must not be registered beforehand. The Sun JCE provider does not work. | | String
-| *camel.dataformat.pgp.signature-key-file-name* | Filename of the keyring to use for signing (during encryption) or for signature verification (during decryption); must be accessible as a classpath resource (but you can specify a location in the file system by using the file: prefix). | | String
-| *camel.dataformat.pgp.signature-key-ring* | Keyring used for signing/verifying as byte array. You can not set the signatureKeyFileName and signatureKeyRing at the same time. | | String
-| *camel.dataformat.pgp.signature-key-userid* | User ID of the key in the PGP keyring used for signing (during encryption) or signature verification (during decryption). During the signature verification process the specified User ID restricts the public keys from the public keyring which can be used for the verification. If no User ID is specified for the signature verficiation then any public key in the public keyring can be used for the verification. Can also be only a part of a user [...]
-| *camel.dataformat.pgp.signature-password* | Password used when opening the private key used for signing (during encryption). | | String
-| *camel.dataformat.pgp.signature-verification-option* | Controls the behavior for verifying the signature during unmarshaling. There are 4 values possible: optional: The PGP message may or may not contain signatures; if it does contain signatures, then a signature verification is executed. required: The PGP message must contain at least one signature; if this is not the case an exception (PGPException) is thrown. A signature verification is executed. ignore: Contained signatures in the [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-csv-starter/src/main/docs/csv-starter.adoc b/components-starter/camel-csv-starter/src/main/docs/csv-starter.adoc
deleted file mode 100644
index a26b2f9..0000000
--- a/components-starter/camel-csv-starter/src/main/docs/csv-starter.adoc
+++ /dev/null
@@ -1,57 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for csv
-
-== Spring Boot Auto-Configuration
-
-When using csv with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-csv-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 29 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.dataformat.csv.allow-missing-column-names* | Whether to allow missing column names. | false | Boolean
-| *camel.dataformat.csv.comment-marker* | Sets the comment marker of the reference format. | | String
-| *camel.dataformat.csv.comment-marker-disabled* | Disables the comment marker of the reference format. | false | Boolean
-| *camel.dataformat.csv.delimiter* | Sets the delimiter to use. The default value is , (comma) | | String
-| *camel.dataformat.csv.enabled* | Whether to enable auto configuration of the csv data format. This is enabled by default. | | Boolean
-| *camel.dataformat.csv.escape* | Sets the escape character to use | | String
-| *camel.dataformat.csv.escape-disabled* | Use for disabling using escape character | false | Boolean
-| *camel.dataformat.csv.format-name* | The name of the format to use, the default value is CSVFormat.DEFAULT | | String
-| *camel.dataformat.csv.format-ref* | The reference format to use, it will be updated with the other format options, the default value is CSVFormat.DEFAULT | | String
-| *camel.dataformat.csv.header* | To configure the CSV headers | | List
-| *camel.dataformat.csv.header-disabled* | Use for disabling headers | false | Boolean
-| *camel.dataformat.csv.ignore-empty-lines* | Whether to ignore empty lines. | false | Boolean
-| *camel.dataformat.csv.ignore-header-case* | Sets whether or not to ignore case when accessing header names. | false | Boolean
-| *camel.dataformat.csv.ignore-surrounding-spaces* | Whether to ignore surrounding spaces | false | Boolean
-| *camel.dataformat.csv.lazy-load* | Whether the unmarshalling should produce an iterator that reads the lines on the fly or if all the lines must be read at one. | false | Boolean
-| *camel.dataformat.csv.marshaller-factory-ref* | Sets the implementation of the CsvMarshallerFactory interface which is able to customize marshalling/unmarshalling behavior by extending CsvMarshaller or creating it from scratch. | | String
-| *camel.dataformat.csv.null-string* | Sets the null string | | String
-| *camel.dataformat.csv.null-string-disabled* | Used to disable null strings | false | Boolean
-| *camel.dataformat.csv.quote* | Sets the quote which by default is | | String
-| *camel.dataformat.csv.quote-disabled* | Used to disable quotes | false | Boolean
-| *camel.dataformat.csv.quote-mode* | Sets the quote mode | | String
-| *camel.dataformat.csv.record-converter-ref* | Refers to a custom CsvRecordConverter to lookup from the registry to use. | | String
-| *camel.dataformat.csv.record-separator* | Sets the record separator (aka new line) which by default is new line characters (CRLF) | | String
-| *camel.dataformat.csv.record-separator-disabled* | Used for disabling record separator | | String
-| *camel.dataformat.csv.skip-header-record* | Whether to skip the header record in the output | false | Boolean
-| *camel.dataformat.csv.trailing-delimiter* | Sets whether or not to add a trailing delimiter. | false | Boolean
-| *camel.dataformat.csv.trim* | Sets whether or not to trim leading and trailing blanks. | false | Boolean
-| *camel.dataformat.csv.use-maps* | Whether the unmarshalling should produce maps (HashMap)for the lines values instead of lists. It requires to have header (either defined or collected). | false | Boolean
-| *camel.dataformat.csv.use-ordered-maps* | Whether the unmarshalling should produce ordered maps (LinkedHashMap) for the lines values instead of lists. It requires to have header (either defined or collected). | false | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-cxf-starter/src/main/docs/cxf-starter.adoc b/components-starter/camel-cxf-starter/src/main/docs/cxf-starter.adoc
deleted file mode 100644
index a93cfa4..0000000
--- a/components-starter/camel-cxf-starter/src/main/docs/cxf-starter.adoc
+++ /dev/null
@@ -1,41 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for cxf
-
-== Spring Boot Auto-Configuration
-
-When using cxf with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-cxf-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 13 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.cxf.allow-streaming* | This option controls whether the CXF component, when running in PAYLOAD mode, will DOM parse the incoming messages into DOM Elements or keep the payload as a javax.xml.transform.Source object that would allow streaming in some cases. | | Boolean
-| *camel.component.cxf.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.cxf.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.cxf.enabled* | Whether to enable auto configuration of the cxf component. This is enabled by default. | | Boolean
-| *camel.component.cxf.header-filter-strategy* | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. The option is a org.apache.camel.spi.HeaderFilterStrategy type. | | HeaderFilterStrategy
-| *camel.component.cxf.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then c [...]
-| *camel.component.cxf.use-global-ssl-context-parameters* | Enable usage of global SSL context parameters. | false | Boolean
-| *camel.component.cxfrs.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.cxfrs.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.cxfrs.enabled* | Whether to enable auto configuration of the cxfrs component. This is enabled by default. | | Boolean
-| *camel.component.cxfrs.header-filter-strategy* | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. The option is a org.apache.camel.spi.HeaderFilterStrategy type. | | HeaderFilterStrategy
-| *camel.component.cxfrs.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
-| *camel.component.cxfrs.use-global-ssl-context-parameters* | Enable usage of global SSL context parameters. | false | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-dataformat-starter/src/main/docs/dataformat-starter.adoc b/components-starter/camel-dataformat-starter/src/main/docs/dataformat-starter.adoc
deleted file mode 100644
index 776b238..0000000
--- a/components-starter/camel-dataformat-starter/src/main/docs/dataformat-starter.adoc
+++ /dev/null
@@ -1,31 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for dataformat
-
-== Spring Boot Auto-Configuration
-
-When using dataformat with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-dataformat-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 3 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.dataformat.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.dataformat.enabled* | Whether to enable auto configuration of the dataformat component. This is enabled by default. | | Boolean
-| *camel.component.dataformat.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-dataset-starter/src/main/docs/dataset-starter.adoc b/components-starter/camel-dataset-starter/src/main/docs/dataset-starter.adoc
deleted file mode 100644
index a708902..0000000
--- a/components-starter/camel-dataset-starter/src/main/docs/dataset-starter.adoc
+++ /dev/null
@@ -1,35 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for dataset
-
-== Spring Boot Auto-Configuration
-
-When using dataset with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-dataset-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 7 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.dataset-test.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.dataset-test.enabled* | Whether to enable auto configuration of the dataset-test component. This is enabled by default. | | Boolean
-| *camel.component.dataset-test.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is process [...]
-| *camel.component.dataset.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.dataset.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.dataset.enabled* | Whether to enable auto configuration of the dataset component. This is enabled by default. | | Boolean
-| *camel.component.dataset.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-datasonnet-starter/src/main/docs/datasonnet-starter.adoc b/components-starter/camel-datasonnet-starter/src/main/docs/datasonnet-starter.adoc
deleted file mode 100644
index 024e6c3..0000000
--- a/components-starter/camel-datasonnet-starter/src/main/docs/datasonnet-starter.adoc
+++ /dev/null
@@ -1,34 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for datasonnet
-
-== Spring Boot Auto-Configuration
-
-When using datasonnet with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-datasonnet-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 4 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.language.datasonnet.body-media-type* | The String representation of the message's body MediaType | | String
-| *camel.language.datasonnet.enabled* | Whether to enable auto configuration of the datasonnet language. This is enabled by default. | | Boolean
-| *camel.language.datasonnet.output-media-type* | The String representation of the MediaType to output | | String
-| *camel.language.datasonnet.trim* | Whether to trim the value to remove leading and trailing whitespaces and line breaks | true | Boolean
-|===
-
-
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-debezium-mongodb-starter/src/main/docs/debezium-mongodb-starter.adoc b/components-starter/camel-debezium-mongodb-starter/src/main/docs/debezium-mongodb-starter.adoc
deleted file mode 100644
index 8f202d5..0000000
--- a/components-starter/camel-debezium-mongodb-starter/src/main/docs/debezium-mongodb-starter.adoc
+++ /dev/null
@@ -1,83 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for debezium-mongodb
-
-== Spring Boot Auto-Configuration
-
-When using debezium-mongodb with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-debezium-mongodb-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 55 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.debezium-mongodb.additional-properties* | Additional properties for debezium components in case they can't be set directly on the camel configurations (e.g: setting Kafka Connect properties needed by Debezium engine, for example setting KafkaOffsetBackingStore), the properties have to be prefixed with additionalProperties.. E.g: additionalProperties.transactional.id=12345&additionalProperties.schema.registry.url=\http://localhost:8811/avro | | Map
-| *camel.component.debezium-mongodb.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.debezium-mongodb.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.debezium-mongodb.collection-exclude-list* | A comma-separated list of regular expressions that match the collection names for which changes are to be excluded | | String
-| *camel.component.debezium-mongodb.collection-include-list* | A comma-separated list of regular expressions that match the collection names for which changes are to be captured | | String
-| *camel.component.debezium-mongodb.configuration* | Allow pre-configured Configurations to be set. The option is a org.apache.camel.component.debezium.configuration.MongoDbConnectorEmbeddedDebeziumConfiguration type. | | MongoDbConnectorEmbeddedDebeziumConfiguration
-| *camel.component.debezium-mongodb.connect-backoff-initial-delay-ms* | The initial delay when trying to reconnect to a primary after a connection cannot be made or when no primary is available. Defaults to 1 second (1000 ms). The option is a long type. | 1000 | Long
-| *camel.component.debezium-mongodb.connect-backoff-max-delay-ms* | The maximum delay when trying to reconnect to a primary after a connection cannot be made or when no primary is available. Defaults to 120 second (120,000 ms). The option is a long type. | 120000 | Long
-| *camel.component.debezium-mongodb.connect-max-attempts* | Maximum number of failed connection attempts to a replica set primary before an exception occurs and task is aborted. Defaults to 16, which with the defaults for 'connect.backoff.initial.delay.ms' and 'connect.backoff.max.delay.ms' results in just over 20 minutes of attempts before failing. | 16 | Integer
-| *camel.component.debezium-mongodb.converters* | Optional list of custom converters that would be used instead of default ones. The converters are defined using '.type' config option and configured using options '.' | | String
-| *camel.component.debezium-mongodb.database-exclude-list* | A comma-separated list of regular expressions that match the database names for which changes are to be excluded | | String
-| *camel.component.debezium-mongodb.database-history-file-filename* | The path to the file that will be used to record the database history | | String
-| *camel.component.debezium-mongodb.database-include-list* | A comma-separated list of regular expressions that match the database names for which changes are to be captured | | String
-| *camel.component.debezium-mongodb.enabled* | Whether to enable auto configuration of the debezium-mongodb component. This is enabled by default. | | Boolean
-| *camel.component.debezium-mongodb.event-processing-failure-handling-mode* | Specify how failures during processing of events (i.e. when encountering a corrupted event) should be handled, including:'fail' (the default) an exception indicating the problematic event and its position is raised, causing the connector to be stopped; 'warn' the problematic event and its position will be logged and the event will be skipped;'ignore' the problematic event will be skipped. | fail | String
-| *camel.component.debezium-mongodb.field-exclude-list* | A comma-separated list of the fully-qualified names of fields that should be excluded from change event message values | | String
-| *camel.component.debezium-mongodb.field-renames* | Description is not available here, please check Debezium website for corresponding key 'field.renames' description. | | String
-| *camel.component.debezium-mongodb.heartbeat-interval-ms* | Length of an interval in milli-seconds in in which the connector periodically sends heartbeat messages to a heartbeat topic. Use 0 to disable heartbeat messages. Disabled by default. The option is a int type. | 0 | Integer
-| *camel.component.debezium-mongodb.heartbeat-topics-prefix* | The prefix that is used to name heartbeat topics.Defaults to __debezium-heartbeat. | __debezium-heartbeat | String
-| *camel.component.debezium-mongodb.initial-sync-max-threads* | Maximum number of threads used to perform an initial sync of the collections in a replica set. Defaults to 1. | 1 | Integer
-| *camel.component.debezium-mongodb.internal-key-converter* | The Converter class that should be used to serialize and deserialize key data for offsets. The default is JSON converter. | org.apache.kafka.connect.json.JsonConverter | String
-| *camel.component.debezium-mongodb.internal-value-converter* | The Converter class that should be used to serialize and deserialize value data for offsets. The default is JSON converter. | org.apache.kafka.connect.json.JsonConverter | String
-| *camel.component.debezium-mongodb.max-batch-size* | Maximum size of each batch of source records. Defaults to 2048. | 2048 | Integer
-| *camel.component.debezium-mongodb.max-queue-size* | Maximum size of the queue for change events read from the database log but not yet recorded or forwarded. Defaults to 8192, and should always be larger than the maximum batch size. | 8192 | Integer
-| *camel.component.debezium-mongodb.mongodb-authsource* | Database containing user credentials. | admin | String
-| *camel.component.debezium-mongodb.mongodb-connect-timeout-ms* | The connection timeout in milliseconds. The option is a int type. | 10000 | Integer
-| *camel.component.debezium-mongodb.mongodb-hosts* | The hostname and port pairs (in the form 'host' or 'host:port') of the MongoDB server(s) in the replica set. | | String
-| *camel.component.debezium-mongodb.mongodb-members-auto-discover* | Specifies whether the addresses in 'hosts' are seeds that should be used to discover all members of the cluster or replica set ('true'), or whether the address(es) in 'hosts' should be used as is ('false'). The default is 'true'. | true | Boolean
-| *camel.component.debezium-mongodb.mongodb-name* | Unique name that identifies the MongoDB replica set or cluster and all recorded offsets, andthat is used as a prefix for all schemas and topics. Each distinct MongoDB installation should have a separate namespace and monitored by at most one Debezium connector. | | String
-| *camel.component.debezium-mongodb.mongodb-password* | Password to be used when connecting to MongoDB, if necessary. | | String
-| *camel.component.debezium-mongodb.mongodb-poll-interval-ms* | Frequency in milliseconds to look for new, removed, or changed replica sets. Defaults to 30000 milliseconds. The option is a long type. | 30000 | Long
-| *camel.component.debezium-mongodb.mongodb-server-selection-timeout-ms* | The server selection timeout in milliseconds. The option is a int type. | 30000 | Integer
-| *camel.component.debezium-mongodb.mongodb-socket-timeout-ms* | The socket timeout in milliseconds. The option is a int type. | 0 | Integer
-| *camel.component.debezium-mongodb.mongodb-ssl-enabled* | Should connector use SSL to connect to MongoDB instances | false | Boolean
-| *camel.component.debezium-mongodb.mongodb-ssl-invalid-hostname-allowed* | Whether invalid host names are allowed when using SSL. If true the connection will not prevent man-in-the-middle attacks | false | Boolean
-| *camel.component.debezium-mongodb.mongodb-user* | Database user for connecting to MongoDB, if necessary. | | String
-| *camel.component.debezium-mongodb.offset-commit-policy* | The name of the Java class of the commit policy. It defines when offsets commit has to be triggered based on the number of events processed and the time elapsed since the last commit. This class must implement the interface 'OffsetCommitPolicy'. The default is a periodic commit policy based upon time intervals. | io.debezium.embedded.spi.OffsetCommitPolicy.PeriodicCommitOffsetPolicy | String
-| *camel.component.debezium-mongodb.offset-commit-timeout-ms* | Maximum number of milliseconds to wait for records to flush and partition offset data to be committed to offset storage before cancelling the process and restoring the offset data to be committed in a future attempt. The default is 5 seconds. The option is a long type. | 5000 | Long
-| *camel.component.debezium-mongodb.offset-flush-interval-ms* | Interval at which to try committing offsets. The default is 1 minute. The option is a long type. | 60000 | Long
-| *camel.component.debezium-mongodb.offset-storage* | The name of the Java class that is responsible for persistence of connector offsets. | org.apache.kafka.connect.storage.FileOffsetBackingStore | String
-| *camel.component.debezium-mongodb.offset-storage-file-name* | Path to file where offsets are to be stored. Required when offset.storage is set to the FileOffsetBackingStore. | | String
-| *camel.component.debezium-mongodb.offset-storage-partitions* | The number of partitions used when creating the offset storage topic. Required when offset.storage is set to the 'KafkaOffsetBackingStore'. | | Integer
-| *camel.component.debezium-mongodb.offset-storage-replication-factor* | Replication factor used when creating the offset storage topic. Required when offset.storage is set to the KafkaOffsetBackingStore | | Integer
-| *camel.component.debezium-mongodb.offset-storage-topic* | The name of the Kafka topic where offsets are to be stored. Required when offset.storage is set to the KafkaOffsetBackingStore. | | String
-| *camel.component.debezium-mongodb.poll-interval-ms* | Frequency in milliseconds to wait for new change events to appear after receiving no events. Defaults to 500ms. The option is a long type. | 500 | Long
-| *camel.component.debezium-mongodb.provide-transaction-metadata* | Enables transaction metadata extraction together with event counting | false | Boolean
-| *camel.component.debezium-mongodb.query-fetch-size* | The maximum number of records that should be loaded into memory while streaming. A value of 0 uses the default JDBC fetch size. | 0 | Integer
-| *camel.component.debezium-mongodb.retriable-restart-connector-wait-ms* | Time to wait before restarting connector after retriable exception occurs. Defaults to 10000ms. The option is a long type. | 10000 | Long
-| *camel.component.debezium-mongodb.sanitize-field-names* | Whether field names will be sanitized to Avro naming conventions | false | Boolean
-| *camel.component.debezium-mongodb.skipped-operations* | The comma-separated list of operations to skip during streaming, defined as: 'i' for inserts; 'u' for updates; 'd' for deletes. By default, no operations will be skipped. | | String
-| *camel.component.debezium-mongodb.snapshot-delay-ms* | The number of milliseconds to delay before a snapshot will begin. The option is a long type. | 0 | Long
-| *camel.component.debezium-mongodb.snapshot-fetch-size* | The maximum number of records that should be loaded into memory while performing a snapshot | | Integer
-| *camel.component.debezium-mongodb.snapshot-mode* | The criteria for running a snapshot upon startup of the connector. Options include: 'initial' (the default) to specify the connector should always perform an initial sync when required; 'never' to specify the connector should never perform an initial sync | initial | String
-| *camel.component.debezium-mongodb.source-struct-version* | A version of the format of the publicly visible source part in the message | v2 | String
-| *camel.component.debezium-mongodb.tombstones-on-delete* | Whether delete operations should be represented by a delete event and a subsquenttombstone event (true) or only by a delete event (false). Emitting the tombstone event (the default behavior) allows Kafka to completely delete all events pertaining to the given key once the source record got deleted. | false | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-debezium-mysql-starter/src/main/docs/debezium-mysql-starter.adoc b/components-starter/camel-debezium-mysql-starter/src/main/docs/debezium-mysql-starter.adoc
deleted file mode 100644
index 577a688..0000000
--- a/components-starter/camel-debezium-mysql-starter/src/main/docs/debezium-mysql-starter.adoc
+++ /dev/null
@@ -1,108 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for debezium-mysql
-
-== Spring Boot Auto-Configuration
-
-When using debezium-mysql with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-debezium-mysql-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 80 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.debezium-mysql.additional-properties* | Additional properties for debezium components in case they can't be set directly on the camel configurations (e.g: setting Kafka Connect properties needed by Debezium engine, for example setting KafkaOffsetBackingStore), the properties have to be prefixed with additionalProperties.. E.g: additionalProperties.transactional.id=12345&additionalProperties.schema.registry.url=\http://localhost:8811/avro | | Map
-| *camel.component.debezium-mysql.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.debezium-mysql.bigint-unsigned-handling-mode* | Specify how BIGINT UNSIGNED columns should be represented in change events, including:'precise' uses java.math.BigDecimal to represent values, which are encoded in the change events using a binary representation and Kafka Connect's 'org.apache.kafka.connect.data.Decimal' type; 'long' (the default) represents values using Java's 'long', which may not offer the precision but will be far easier to use in consumers. | long | String
-| *camel.component.debezium-mysql.binary-handling-mode* | Specify how binary (blob, binary, etc.) columns should be represented in change events, including:'bytes' represents binary data as byte array (default)'base64' represents binary data as base64-encoded string'hex' represents binary data as hex-encoded (base16) string | bytes | String
-| *camel.component.debezium-mysql.binlog-buffer-size* | The size of a look-ahead buffer used by the binlog reader to decide whether the transaction in progress is going to be committed or rolled back. Use 0 to disable look-ahead buffering. Defaults to 0 (i.e. buffering is disabled). | 0 | Integer
-| *camel.component.debezium-mysql.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.debezium-mysql.column-blacklist* | Regular expressions matching columns to exclude from change events (deprecated, use column.exclude.list instead) | | String
-| *camel.component.debezium-mysql.column-exclude-list* | Regular expressions matching columns to exclude from change events | | String
-| *camel.component.debezium-mysql.column-include-list* | Regular expressions matching columns to include in change events | | String
-| *camel.component.debezium-mysql.configuration* | Allow pre-configured Configurations to be set. The option is a org.apache.camel.component.debezium.configuration.MySqlConnectorEmbeddedDebeziumConfiguration type. | | MySqlConnectorEmbeddedDebeziumConfiguration
-| *camel.component.debezium-mysql.connect-keep-alive* | Whether a separate thread should be used to ensure the connection is kept alive. | true | Boolean
-| *camel.component.debezium-mysql.connect-keep-alive-interval-ms* | Interval in milliseconds to wait for connection checking if keep alive thread is used. The option is a long type. | 60000 | Long
-| *camel.component.debezium-mysql.connect-timeout-ms* | Maximum time in milliseconds to wait after trying to connect to the database before timing out. The option is a int type. | 30000 | Integer
-| *camel.component.debezium-mysql.database-exclude-list* | A comma-separated list of regular expressions that match database names to be excluded from monitoring | | String
-| *camel.component.debezium-mysql.database-history* | The name of the DatabaseHistory class that should be used to store and recover database schema changes. The configuration properties for the history are prefixed with the 'database.history.' string. | io.debezium.relational.history.FileDatabaseHistory | String
-| *camel.component.debezium-mysql.database-history-file-filename* | The path to the file that will be used to record the database history | | String
-| *camel.component.debezium-mysql.database-history-kafka-bootstrap-servers* | A list of host/port pairs that the connector will use for establishing the initial connection to the Kafka cluster for retrieving database schema history previously stored by the connector. This should point to the same Kafka cluster used by the Kafka Connect process. | | String
-| *camel.component.debezium-mysql.database-history-kafka-recovery-attempts* | The number of attempts in a row that no data are returned from Kafka before recover completes. The maximum amount of time to wait after receiving no data is (recovery.attempts) x (recovery.poll.interval.ms). | 100 | Integer
-| *camel.component.debezium-mysql.database-history-kafka-recovery-poll-interval-ms* | The number of milliseconds to wait while polling for persisted data during recovery. The option is a int type. | 100 | Integer
-| *camel.component.debezium-mysql.database-history-kafka-topic* | The name of the topic for the database schema history | | String
-| *camel.component.debezium-mysql.database-history-skip-unparseable-ddl* | Controls the action Debezium will take when it meets a DDL statement in binlog, that it cannot parse.By default the connector will stop operating but by changing the setting it can ignore the statements which it cannot parse. If skipping is enabled then Debezium can miss metadata changes. | false | Boolean
-| *camel.component.debezium-mysql.database-history-store-only-monitored-tables-ddl* | Controls what DDL will Debezium store in database history.By default (false) Debezium will store all incoming DDL statements. If set to truethen only DDL that manipulates a monitored table will be stored. | false | Boolean
-| *camel.component.debezium-mysql.database-hostname* | Resolvable hostname or IP address of the MySQL database server. | | String
-| *camel.component.debezium-mysql.database-include-list* | The databases for which changes are to be captured | | String
-| *camel.component.debezium-mysql.database-initial-statements* | A semicolon separated list of SQL statements to be executed when a JDBC connection (not binlog reading connection) to the database is established. Note that the connector may establish JDBC connections at its own discretion, so this should typically be used for configuration of session parameters only,but not for executing DML statements. Use doubled semicolon (';;') to use a semicolon as a character and not as a delimiter. [...]
-| *camel.component.debezium-mysql.database-jdbc-driver* | JDBC Driver class name used to connect to the MySQL database server. | class com.mysql.cj.jdbc.Driver | String
-| *camel.component.debezium-mysql.database-password* | Password of the MySQL database user to be used when connecting to the database. | | String
-| *camel.component.debezium-mysql.database-port* | Port of the MySQL database server. | 3306 | Integer
-| *camel.component.debezium-mysql.database-server-id* | A numeric ID of this database client, which must be unique across all currently-running database processes in the cluster. This connector joins the MySQL database cluster as another server (with this unique ID) so it can read the binlog. By default, a random number is generated between 5400 and 6400. | | Long
-| *camel.component.debezium-mysql.database-server-id-offset* | Only relevant if parallel snapshotting is configured. During parallel snapshotting, multiple (4) connections open to the database client, and they each need their own unique connection ID. This offset is used to generate those IDs from the base configured cluster ID. | 10000 | Long
-| *camel.component.debezium-mysql.database-server-name* | Unique name that identifies the database server and all recorded offsets, and that is used as a prefix for all schemas and topics. Each distinct installation should have a separate namespace and be monitored by at most one Debezium connector. | | String
-| *camel.component.debezium-mysql.database-ssl-keystore* | Location of the Java keystore file containing an application process's own certificate and private key. | | String
-| *camel.component.debezium-mysql.database-ssl-keystore-password* | Password to access the private key from the keystore file specified by 'ssl.keystore' configuration property or the 'javax.net.ssl.keyStore' system or JVM property. This password is used to unlock the keystore file (store password), and to decrypt the private key stored in the keystore (key password). | | String
-| *camel.component.debezium-mysql.database-ssl-mode* | Whether to use an encrypted connection to MySQL. Options include'disabled' (the default) to use an unencrypted connection; 'preferred' to establish a secure (encrypted) connection if the server supports secure connections, but fall back to an unencrypted connection otherwise; 'required' to use a secure (encrypted) connection, and fail if one cannot be established; 'verify_ca' like 'required' but additionally verify the server TLS cer [...]
-| *camel.component.debezium-mysql.database-ssl-truststore* | Location of the Java truststore file containing the collection of CA certificates trusted by this application process (trust store). | | String
-| *camel.component.debezium-mysql.database-ssl-truststore-password* | Password to unlock the keystore file (store password) specified by 'ssl.trustore' configuration property or the 'javax.net.ssl.trustStore' system or JVM property. | | String
-| *camel.component.debezium-mysql.database-user* | Name of the MySQL database user to be used when connecting to the database. | | String
-| *camel.component.debezium-mysql.decimal-handling-mode* | Specify how DECIMAL and NUMERIC columns should be represented in change events, including:'precise' (the default) uses java.math.BigDecimal to represent values, which are encoded in the change events using a binary representation and Kafka Connect's 'org.apache.kafka.connect.data.Decimal' type; 'string' uses string to represent values; 'double' represents values using Java's 'double', which may not offer the precision but will be [...]
-| *camel.component.debezium-mysql.enable-time-adjuster* | MySQL allows user to insert year value as either 2-digit or 4-digit. In case of two digit the value is automatically mapped into 1970 - 2069.false - delegates the implicit conversion to the databasetrue - (the default) Debezium makes the conversion | true | Boolean
-| *camel.component.debezium-mysql.enabled* | Whether to enable auto configuration of the debezium-mysql component. This is enabled by default. | | Boolean
-| *camel.component.debezium-mysql.event-deserialization-failure-handling-mode* | Specify how failures during deserialization of binlog events (i.e. when encountering a corrupted event) should be handled, including:'fail' (the default) an exception indicating the problematic event and its binlog position is raised, causing the connector to be stopped; 'warn' the problematic event and its binlog position will be logged and the event will be skipped;'ignore' the problematic event will be sk [...]
-| *camel.component.debezium-mysql.event-processing-failure-handling-mode* | Specify how failures during processing of events (i.e. when encountering a corrupted event) should be handled, including:'fail' (the default) an exception indicating the problematic event and its position is raised, causing the connector to be stopped; 'warn' the problematic event and its position will be logged and the event will be skipped;'ignore' the problematic event will be skipped. | fail | String
-| *camel.component.debezium-mysql.gtid-new-channel-position* | If set to 'latest', when connector sees new GTID, it will start consuming gtid channel from the server latest executed gtid position. If 'earliest' (the default) connector starts reading channel from first available (not purged) gtid position on the server. | earliest | String
-| *camel.component.debezium-mysql.gtid-source-excludes* | The source UUIDs used to exclude GTID ranges when determine the starting position in the MySQL server's binlog. | | String
-| *camel.component.debezium-mysql.gtid-source-filter-dml-events* | If set to true, we will only produce DML events into Kafka for transactions that were written on mysql servers with UUIDs matching the filters defined by the gtid.source.includes or gtid.source.excludes configuration options, if they are specified. | true | Boolean
-| *camel.component.debezium-mysql.gtid-source-includes* | The source UUIDs used to include GTID ranges when determine the starting position in the MySQL server's binlog. | | String
-| *camel.component.debezium-mysql.heartbeat-interval-ms* | Length of an interval in milli-seconds in in which the connector periodically sends heartbeat messages to a heartbeat topic. Use 0 to disable heartbeat messages. Disabled by default. The option is a int type. | 0 | Integer
-| *camel.component.debezium-mysql.heartbeat-topics-prefix* | The prefix that is used to name heartbeat topics.Defaults to __debezium-heartbeat. | __debezium-heartbeat | String
-| *camel.component.debezium-mysql.include-query* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For this reason the default val [...]
-| *camel.component.debezium-mysql.include-schema-changes* | Whether the connector should publish changes in the database schema to a Kafka topic with the same name as the database server ID. Each schema change will be recorded using a key that contains the database name and whose value include logical description of the new schema and optionally the DDL statement(s).The default is 'true'. This is independent of how the connector internally records database history. | true | Boolean
-| *camel.component.debezium-mysql.inconsistent-schema-handling-mode* | Specify how binlog events that belong to a table missing from internal schema representation (i.e. internal representation is not consistent with database) should be handled, including:'fail' (the default) an exception indicating the problematic event and its binlog position is raised, causing the connector to be stopped; 'warn' the problematic event and its binlog position will be logged and the event will be skipped [...]
-| *camel.component.debezium-mysql.internal-key-converter* | The Converter class that should be used to serialize and deserialize key data for offsets. The default is JSON converter. | org.apache.kafka.connect.json.JsonConverter | String
-| *camel.component.debezium-mysql.internal-value-converter* | The Converter class that should be used to serialize and deserialize value data for offsets. The default is JSON converter. | org.apache.kafka.connect.json.JsonConverter | String
-| *camel.component.debezium-mysql.max-batch-size* | Maximum size of each batch of source records. Defaults to 2048. | 2048 | Integer
-| *camel.component.debezium-mysql.max-queue-size* | Maximum size of the queue for change events read from the database log but not yet recorded or forwarded. Defaults to 8192, and should always be larger than the maximum batch size. | 8192 | Integer
-| *camel.component.debezium-mysql.message-key-columns* | A semicolon-separated list of expressions that match fully-qualified tables and column(s) to be used as message key. Each expression must match the pattern ':',where the table names could be defined as (DB_NAME.TABLE_NAME) or (SCHEMA_NAME.TABLE_NAME), depending on the specific connector,and the key columns are a comma-separated list of columns representing the custom key. For any table without an explicit key configuration the tabl [...]
-| *camel.component.debezium-mysql.offset-commit-policy* | The name of the Java class of the commit policy. It defines when offsets commit has to be triggered based on the number of events processed and the time elapsed since the last commit. This class must implement the interface 'OffsetCommitPolicy'. The default is a periodic commit policy based upon time intervals. | io.debezium.embedded.spi.OffsetCommitPolicy.PeriodicCommitOffsetPolicy | String
-| *camel.component.debezium-mysql.offset-commit-timeout-ms* | Maximum number of milliseconds to wait for records to flush and partition offset data to be committed to offset storage before cancelling the process and restoring the offset data to be committed in a future attempt. The default is 5 seconds. The option is a long type. | 5000 | Long
-| *camel.component.debezium-mysql.offset-flush-interval-ms* | Interval at which to try committing offsets. The default is 1 minute. The option is a long type. | 60000 | Long
-| *camel.component.debezium-mysql.offset-storage* | The name of the Java class that is responsible for persistence of connector offsets. | org.apache.kafka.connect.storage.FileOffsetBackingStore | String
-| *camel.component.debezium-mysql.offset-storage-file-name* | Path to file where offsets are to be stored. Required when offset.storage is set to the FileOffsetBackingStore. | | String
-| *camel.component.debezium-mysql.offset-storage-partitions* | The number of partitions used when creating the offset storage topic. Required when offset.storage is set to the 'KafkaOffsetBackingStore'. | | Integer
-| *camel.component.debezium-mysql.offset-storage-replication-factor* | Replication factor used when creating the offset storage topic. Required when offset.storage is set to the KafkaOffsetBackingStore | | Integer
-| *camel.component.debezium-mysql.offset-storage-topic* | The name of the Kafka topic where offsets are to be stored. Required when offset.storage is set to the KafkaOffsetBackingStore. | | String
-| *camel.component.debezium-mysql.poll-interval-ms* | Frequency in milliseconds to wait for new change events to appear after receiving no events. Defaults to 500ms. The option is a long type. | 500 | Long
-| *camel.component.debezium-mysql.skipped-operations* | The comma-separated list of operations to skip during streaming, defined as: 'i' for inserts; 'u' for updates; 'd' for deletes. By default, no operations will be skipped. | | String
-| *camel.component.debezium-mysql.snapshot-delay-ms* | The number of milliseconds to delay before a snapshot will begin. The option is a long type. | 0 | Long
-| *camel.component.debezium-mysql.snapshot-fetch-size* | The maximum number of records that should be loaded into memory while performing a snapshot | | Integer
-| *camel.component.debezium-mysql.snapshot-locking-mode* | Controls how long the connector holds onto the global read lock while it is performing a snapshot. The default is 'minimal', which means the connector holds the global read lock (and thus prevents any updates) for just the initial portion of the snapshot while the database schemas and other metadata are being read. The remaining work in a snapshot involves selecting all rows from each table, and this can be done using the snapsho [...]
-| *camel.component.debezium-mysql.snapshot-mode* | The criteria for running a snapshot upon startup of the connector. Options include: 'when_needed' to specify that the connector run a snapshot upon startup whenever it deems it necessary; 'schema_only' to only take a snapshot of the schema (table structures) but no actual data; 'initial' (the default) to specify the connector can run a snapshot only when no offsets are available for the logical server name; 'initial_only' same as 'initia [...]
-| *camel.component.debezium-mysql.snapshot-new-tables* | BETA FEATURE: On connector restart, the connector will check if there have been any new tables added to the configuration, and snapshot them. There is presently only two options:'off': Default behavior. Do not snapshot new tables.'parallel': The snapshot of the new tables will occur in parallel to the continued binlog reading of the old tables. When the snapshot completes, an independent binlog reader will begin reading the events [...]
-| *camel.component.debezium-mysql.snapshot-select-statement-overrides* | This property contains a comma-separated list of fully-qualified tables (DB_NAME.TABLE_NAME) or (SCHEMA_NAME.TABLE_NAME), depending on thespecific connectors . Select statements for the individual tables are specified in further configuration properties, one for each table, identified by the id 'snapshot.select.statement.overrides.DB_NAME.TABLE_NAME' or 'snapshot.select.statement.overrides.SCHEMA_NAME.TABLE_NAME', r [...]
-| *camel.component.debezium-mysql.source-struct-version* | A version of the format of the publicly visible source part in the message | v2 | String
-| *camel.component.debezium-mysql.table-blacklist* | A comma-separated list of regular expressions that match the fully-qualified names of tables to be excluded from monitoring (deprecated, use table.exclude.list instead) | | String
-| *camel.component.debezium-mysql.table-exclude-list* | A comma-separated list of regular expressions that match the fully-qualified names of tables to be excluded from monitoring | | String
-| *camel.component.debezium-mysql.table-ignore-builtin* | Flag specifying whether built-in tables should be ignored. | true | Boolean
-| *camel.component.debezium-mysql.table-include-list* | The tables for which changes are to be captured | | String
-| *camel.component.debezium-mysql.table-whitelist* | The tables for which changes are to be captured (deprecated, use table.include.list instead) | | String
-| *camel.component.debezium-mysql.time-precision-mode* | Time, date and timestamps can be represented with different kinds of precisions, including:'adaptive_time_microseconds': the precision of date and timestamp values is based the database column's precision; but time fields always use microseconds precision;'connect': always represents time, date and timestamp values using Kafka Connect's built-in representations for Time, Date, and Timestamp, which uses millisecond precision regardl [...]
-| *camel.component.debezium-mysql.tombstones-on-delete* | Whether delete operations should be represented by a delete event and a subsquenttombstone event (true) or only by a delete event (false). Emitting the tombstone event (the default behavior) allows Kafka to completely delete all events pertaining to the given key once the source record got deleted. | false | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-debezium-postgres-starter/src/main/docs/debezium-postgres-starter.adoc b/components-starter/camel-debezium-postgres-starter/src/main/docs/debezium-postgres-starter.adoc
deleted file mode 100644
index 210857b..0000000
--- a/components-starter/camel-debezium-postgres-starter/src/main/docs/debezium-postgres-starter.adoc
+++ /dev/null
@@ -1,113 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for debezium-postgres
-
-== Spring Boot Auto-Configuration
-
-When using debezium-postgres with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-debezium-postgres-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 85 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.debezium-postgres.additional-properties* | Additional properties for debezium components in case they can't be set directly on the camel configurations (e.g: setting Kafka Connect properties needed by Debezium engine, for example setting KafkaOffsetBackingStore), the properties have to be prefixed with additionalProperties.. E.g: additionalProperties.transactional.id=12345&additionalProperties.schema.registry.url=\http://localhost:8811/avro | | Map
-| *camel.component.debezium-postgres.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.debezium-postgres.binary-handling-mode* | Specify how binary (blob, binary, etc.) columns should be represented in change events, including:'bytes' represents binary data as byte array (default)'base64' represents binary data as base64-encoded string'hex' represents binary data as hex-encoded (base16) string | bytes | String
-| *camel.component.debezium-postgres.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.debezium-postgres.column-blacklist* | Regular expressions matching columns to exclude from change events (deprecated, use column.exclude.list instead) | | String
-| *camel.component.debezium-postgres.column-exclude-list* | Regular expressions matching columns to exclude from change events | | String
-| *camel.component.debezium-postgres.column-include-list* | Regular expressions matching columns to include in change events | | String
-| *camel.component.debezium-postgres.column-propagate-source-type* | A comma-separated list of regular expressions matching fully-qualified names of columns that adds the columns original type and original length as parameters to the corresponding field schemas in the emitted change records. | | String
-| *camel.component.debezium-postgres.column-whitelist* | Regular expressions matching columns to include in change events (deprecated, use column.include.list instead) | | String
-| *camel.component.debezium-postgres.configuration* | Allow pre-configured Configurations to be set. The option is a org.apache.camel.component.debezium.configuration.PostgresConnectorEmbeddedDebeziumConfiguration type. | | PostgresConnectorEmbeddedDebeziumConfiguration
-| *camel.component.debezium-postgres.converters* | Optional list of custom converters that would be used instead of default ones. The converters are defined using '.type' config option and configured using options '.' | | String
-| *camel.component.debezium-postgres.database-dbname* | The name of the database the connector should be monitoring | | String
-| *camel.component.debezium-postgres.database-history-file-filename* | The path to the file that will be used to record the database history | | String
-| *camel.component.debezium-postgres.database-hostname* | Resolvable hostname or IP address of the Postgres database server. | | String
-| *camel.component.debezium-postgres.database-initial-statements* | A semicolon separated list of SQL statements to be executed when a JDBC connection to the database is established. Note that the connector may establish JDBC connections at its own discretion, so this should typically be used for configurationof session parameters only, but not for executing DML statements. Use doubled semicolon (';;') to use a semicolon as a character and not as a delimiter. | | String
-| *camel.component.debezium-postgres.database-password* | Password of the Postgres database user to be used when connecting to the database. | | String
-| *camel.component.debezium-postgres.database-port* | Port of the Postgres database server. | 5432 | Integer
-| *camel.component.debezium-postgres.database-server-name* | Unique name that identifies the database server and all recorded offsets, and that is used as a prefix for all schemas and topics. Each distinct installation should have a separate namespace and be monitored by at most one Debezium connector. | | String
-| *camel.component.debezium-postgres.database-sslcert* | File containing the SSL Certificate for the client. See the Postgres SSL docs for further information | | String
-| *camel.component.debezium-postgres.database-sslfactory* | A name of class to that creates SSL Sockets. Use org.postgresql.ssl.NonValidatingFactory to disable SSL validation in development environments | | String
-| *camel.component.debezium-postgres.database-sslkey* | File containing the SSL private key for the client. See the Postgres SSL docs for further information | | String
-| *camel.component.debezium-postgres.database-sslmode* | Whether to use an encrypted connection to Postgres. Options include'disable' (the default) to use an unencrypted connection; 'require' to use a secure (encrypted) connection, and fail if one cannot be established; 'verify-ca' like 'required' but additionally verify the server TLS certificate against the configured Certificate Authority (CA) certificates, or fail if no valid matching CA certificates are found; or'verify-full' like ' [...]
-| *camel.component.debezium-postgres.database-sslpassword* | Password to access the client private key from the file specified by 'database.sslkey'. See the Postgres SSL docs for further information | | String
-| *camel.component.debezium-postgres.database-sslrootcert* | File containing the root certificate(s) against which the server is validated. See the Postgres JDBC SSL docs for further information | | String
-| *camel.component.debezium-postgres.database-tcpkeepalive* | Enable or disable TCP keep-alive probe to avoid dropping TCP connection | true | Boolean
-| *camel.component.debezium-postgres.database-user* | Name of the Postgres database user to be used when connecting to the database. | | String
-| *camel.component.debezium-postgres.datatype-propagate-source-type* | A comma-separated list of regular expressions matching the database-specific data type names that adds the data type's original type and original length as parameters to the corresponding field schemas in the emitted change records. | | String
-| *camel.component.debezium-postgres.decimal-handling-mode* | Specify how DECIMAL and NUMERIC columns should be represented in change events, including:'precise' (the default) uses java.math.BigDecimal to represent values, which are encoded in the change events using a binary representation and Kafka Connect's 'org.apache.kafka.connect.data.Decimal' type; 'string' uses string to represent values; 'double' represents values using Java's 'double', which may not offer the precision but will [...]
-| *camel.component.debezium-postgres.enabled* | Whether to enable auto configuration of the debezium-postgres component. This is enabled by default. | | Boolean
-| *camel.component.debezium-postgres.event-processing-failure-handling-mode* | Specify how failures during processing of events (i.e. when encountering a corrupted event) should be handled, including:'fail' (the default) an exception indicating the problematic event and its position is raised, causing the connector to be stopped; 'warn' the problematic event and its position will be logged and the event will be skipped;'ignore' the problematic event will be skipped. | fail | String
-| *camel.component.debezium-postgres.heartbeat-action-query* | The query executed with every heartbeat. | | String
-| *camel.component.debezium-postgres.heartbeat-interval-ms* | Length of an interval in milli-seconds in in which the connector periodically sends heartbeat messages to a heartbeat topic. Use 0 to disable heartbeat messages. Disabled by default. The option is a int type. | 0 | Integer
-| *camel.component.debezium-postgres.heartbeat-topics-prefix* | The prefix that is used to name heartbeat topics.Defaults to __debezium-heartbeat. | __debezium-heartbeat | String
-| *camel.component.debezium-postgres.hstore-handling-mode* | Specify how HSTORE columns should be represented in change events, including:'json' represents values as string-ified JSON (default)'map' represents values as a key/value map | json | String
-| *camel.component.debezium-postgres.include-unknown-datatypes* | Specify whether the fields of data type not supported by Debezium should be processed:'false' (the default) omits the fields; 'true' converts the field into an implementation dependent binary representation. | false | Boolean
-| *camel.component.debezium-postgres.internal-key-converter* | The Converter class that should be used to serialize and deserialize key data for offsets. The default is JSON converter. | org.apache.kafka.connect.json.JsonConverter | String
-| *camel.component.debezium-postgres.internal-value-converter* | The Converter class that should be used to serialize and deserialize value data for offsets. The default is JSON converter. | org.apache.kafka.connect.json.JsonConverter | String
-| *camel.component.debezium-postgres.interval-handling-mode* | Specify how INTERVAL columns should be represented in change events, including:'string' represents values as an exact ISO formatted string'numeric' (default) represents values using the inexact conversion into microseconds | numeric | String
-| *camel.component.debezium-postgres.max-batch-size* | Maximum size of each batch of source records. Defaults to 2048. | 2048 | Integer
-| *camel.component.debezium-postgres.max-queue-size* | Maximum size of the queue for change events read from the database log but not yet recorded or forwarded. Defaults to 8192, and should always be larger than the maximum batch size. | 8192 | Integer
-| *camel.component.debezium-postgres.message-key-columns* | A semicolon-separated list of expressions that match fully-qualified tables and column(s) to be used as message key. Each expression must match the pattern ':',where the table names could be defined as (DB_NAME.TABLE_NAME) or (SCHEMA_NAME.TABLE_NAME), depending on the specific connector,and the key columns are a comma-separated list of columns representing the custom key. For any table without an explicit key configuration the t [...]
-| *camel.component.debezium-postgres.offset-commit-policy* | The name of the Java class of the commit policy. It defines when offsets commit has to be triggered based on the number of events processed and the time elapsed since the last commit. This class must implement the interface 'OffsetCommitPolicy'. The default is a periodic commit policy based upon time intervals. | io.debezium.embedded.spi.OffsetCommitPolicy.PeriodicCommitOffsetPolicy | String
-| *camel.component.debezium-postgres.offset-commit-timeout-ms* | Maximum number of milliseconds to wait for records to flush and partition offset data to be committed to offset storage before cancelling the process and restoring the offset data to be committed in a future attempt. The default is 5 seconds. The option is a long type. | 5000 | Long
-| *camel.component.debezium-postgres.offset-flush-interval-ms* | Interval at which to try committing offsets. The default is 1 minute. The option is a long type. | 60000 | Long
-| *camel.component.debezium-postgres.offset-storage* | The name of the Java class that is responsible for persistence of connector offsets. | org.apache.kafka.connect.storage.FileOffsetBackingStore | String
-| *camel.component.debezium-postgres.offset-storage-file-name* | Path to file where offsets are to be stored. Required when offset.storage is set to the FileOffsetBackingStore. | | String
-| *camel.component.debezium-postgres.offset-storage-partitions* | The number of partitions used when creating the offset storage topic. Required when offset.storage is set to the 'KafkaOffsetBackingStore'. | | Integer
-| *camel.component.debezium-postgres.offset-storage-replication-factor* | Replication factor used when creating the offset storage topic. Required when offset.storage is set to the KafkaOffsetBackingStore | | Integer
-| *camel.component.debezium-postgres.offset-storage-topic* | The name of the Kafka topic where offsets are to be stored. Required when offset.storage is set to the KafkaOffsetBackingStore. | | String
-| *camel.component.debezium-postgres.plugin-name* | The name of the Postgres logical decoding plugin installed on the server. Supported values are 'decoderbufs' and 'wal2json'. Defaults to 'decoderbufs'. | decoderbufs | String
-| *camel.component.debezium-postgres.poll-interval-ms* | Frequency in milliseconds to wait for new change events to appear after receiving no events. Defaults to 500ms. The option is a long type. | 500 | Long
-| *camel.component.debezium-postgres.provide-transaction-metadata* | Enables transaction metadata extraction together with event counting | false | Boolean
-| *camel.component.debezium-postgres.publication-autocreate-mode* | Applies only when streaming changes using pgoutput.Determine how creation of a publication should work, the default is all_tables.DISABLED - The connector will not attempt to create a publication at all. The expectation is that the user has created the publication up-front. If the publication isn't found to exist upon startup, the connector will throw an exception and stop.ALL_TABLES - If no publication exists, the conne [...]
-| *camel.component.debezium-postgres.publication-name* | The name of the Postgres 10 publication used for streaming changes from a plugin.Defaults to 'dbz_publication' | dbz_publication | String
-| *camel.component.debezium-postgres.query-fetch-size* | The maximum number of records that should be loaded into memory while streaming. A value of 0 uses the default JDBC fetch size. | 0 | Integer
-| *camel.component.debezium-postgres.retriable-restart-connector-wait-ms* | Time to wait before restarting connector after retriable exception occurs. Defaults to 10000ms. The option is a long type. | 10000 | Long
-| *camel.component.debezium-postgres.sanitize-field-names* | Whether field names will be sanitized to Avro naming conventions | false | Boolean
-| *camel.component.debezium-postgres.schema-blacklist* | The schemas for which events must not be captured (deprecated, use schema.exclude.list instead) | | String
-| *camel.component.debezium-postgres.schema-exclude-list* | The schemas for which events must not be captured | | String
-| *camel.component.debezium-postgres.schema-include-list* | The schemas for which events should be captured | | String
-| *camel.component.debezium-postgres.schema-refresh-mode* | Specify the conditions that trigger a refresh of the in-memory schema for a table. 'columns_diff' (the default) is the safest mode, ensuring the in-memory schema stays in-sync with the database table's schema at all times. 'columns_diff_exclude_unchanged_toast' instructs the connector to refresh the in-memory schema cache if there is a discrepancy between it and the schema derived from the incoming message, unless unchanged TOAS [...]
-| *camel.component.debezium-postgres.schema-whitelist* | The schemas for which events should be captured (deprecated, use schema.include.list instead) | | String
-| *camel.component.debezium-postgres.skipped-operations* | The comma-separated list of operations to skip during streaming, defined as: 'i' for inserts; 'u' for updates; 'd' for deletes. By default, no operations will be skipped. | | String
-| *camel.component.debezium-postgres.slot-drop-on-stop* | Whether or not to drop the logical replication slot when the connector finishes orderlyBy default the replication is kept so that on restart progress can resume from the last recorded location | false | Boolean
-| *camel.component.debezium-postgres.slot-max-retries* | How many times to retry connecting to a replication slot when an attempt fails. | 6 | Integer
-| *camel.component.debezium-postgres.slot-name* | The name of the Postgres logical decoding slot created for streaming changes from a plugin.Defaults to 'debezium | debezium | String
-| *camel.component.debezium-postgres.slot-retry-delay-ms* | The number of milli-seconds to wait between retry attempts when the connector fails to connect to a replication slot. The option is a long type. | 10000 | Long
-| *camel.component.debezium-postgres.slot-stream-params* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | | String
-| *camel.component.debezium-postgres.snapshot-custom-class* | When 'snapshot.mode' is set as custom, this setting must be set to specify a fully qualified class name to load (via the default class loader).This class must implement the 'Snapshotter' interface and is called on each app boot to determine whether to do a snapshot and how to build queries. | | String
-| *camel.component.debezium-postgres.snapshot-delay-ms* | The number of milliseconds to delay before a snapshot will begin. The option is a long type. | 0 | Long
-| *camel.component.debezium-postgres.snapshot-fetch-size* | The maximum number of records that should be loaded into memory while performing a snapshot | | Integer
-| *camel.component.debezium-postgres.snapshot-lock-timeout-ms* | The maximum number of millis to wait for table locks at the beginning of a snapshot. If locks cannot be acquired in this time frame, the snapshot will be aborted. Defaults to 10 seconds. The option is a long type. | 10000 | Long
-| *camel.component.debezium-postgres.snapshot-mode* | The criteria for running a snapshot upon startup of the connector. Options include: 'always' to specify that the connector run a snapshot each time it starts up; 'initial' (the default) to specify the connector can run a snapshot only when no offsets are available for the logical server name; 'initial_only' same as 'initial' except the connector should stop after completing the snapshot and before it would normally start emitting chan [...]
-| *camel.component.debezium-postgres.snapshot-select-statement-overrides* | This property contains a comma-separated list of fully-qualified tables (DB_NAME.TABLE_NAME) or (SCHEMA_NAME.TABLE_NAME), depending on thespecific connectors . Select statements for the individual tables are specified in further configuration properties, one for each table, identified by the id 'snapshot.select.statement.overrides.DB_NAME.TABLE_NAME' or 'snapshot.select.statement.overrides.SCHEMA_NAME.TABLE_NAME' [...]
-| *camel.component.debezium-postgres.source-struct-version* | A version of the format of the publicly visible source part in the message | v2 | String
-| *camel.component.debezium-postgres.status-update-interval-ms* | Frequency in milliseconds for sending replication connection status updates to the server. Defaults to 10 seconds (10000 ms). The option is a int type. | 10000 | Integer
-| *camel.component.debezium-postgres.table-blacklist* | A comma-separated list of regular expressions that match the fully-qualified names of tables to be excluded from monitoring (deprecated, use table.exclude.list instead) | | String
-| *camel.component.debezium-postgres.table-exclude-list* | A comma-separated list of regular expressions that match the fully-qualified names of tables to be excluded from monitoring | | String
-| *camel.component.debezium-postgres.table-ignore-builtin* | Flag specifying whether built-in tables should be ignored. | true | Boolean
-| *camel.component.debezium-postgres.table-include-list* | The tables for which changes are to be captured | | String
-| *camel.component.debezium-postgres.table-whitelist* | The tables for which changes are to be captured (deprecated, use table.include.list instead) | | String
-| *camel.component.debezium-postgres.time-precision-mode* | Time, date, and timestamps can be represented with different kinds of precisions, including:'adaptive' (the default) bases the precision of time, date, and timestamp values on the database column's precision; 'adaptive_time_microseconds' like 'adaptive' mode, but TIME fields always use microseconds precision;'connect' always represents time, date, and timestamp values using Kafka Connect's built-in representations for Time, Date [...]
-| *camel.component.debezium-postgres.toasted-value-placeholder* | Specify the constant that will be provided by Debezium to indicate that the original value is a toasted value not provided by the database. If starts with 'hex:' prefix it is expected that the rest of the string repesents hexadecimally encoded octets. | __debezium_unavailable_value | String
-| *camel.component.debezium-postgres.tombstones-on-delete* | Whether delete operations should be represented by a delete event and a subsquenttombstone event (true) or only by a delete event (false). Emitting the tombstone event (the default behavior) allows Kafka to completely delete all events pertaining to the given key once the source record got deleted. | false | Boolean
-| *camel.component.debezium-postgres.xmin-fetch-interval-ms* | Specify how often (in ms) the xmin will be fetched from the replication slot. This xmin value is exposed by the slot which gives a lower bound of where a new replication slot could start from. The lower the value, the more likely this value is to be the current 'true' value, but the bigger the performance cost. The bigger the value, the less likely this value is to be the current 'true' value, but the lower the performance pe [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-debezium-sqlserver-starter/src/main/docs/debezium-sqlserver-starter.adoc b/components-starter/camel-debezium-sqlserver-starter/src/main/docs/debezium-sqlserver-starter.adoc
deleted file mode 100644
index db40b4c..0000000
--- a/components-starter/camel-debezium-sqlserver-starter/src/main/docs/debezium-sqlserver-starter.adoc
+++ /dev/null
@@ -1,93 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for debezium-sqlserver
-
-== Spring Boot Auto-Configuration
-
-When using debezium-sqlserver with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-debezium-sqlserver-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 65 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.debezium-sqlserver.additional-properties* | Additional properties for debezium components in case they can't be set directly on the camel configurations (e.g: setting Kafka Connect properties needed by Debezium engine, for example setting KafkaOffsetBackingStore), the properties have to be prefixed with additionalProperties.. E.g: additionalProperties.transactional.id=12345&additionalProperties.schema.registry.url=\http://localhost:8811/avro | | Map
-| *camel.component.debezium-sqlserver.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.debezium-sqlserver.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.debezium-sqlserver.column-blacklist* | Regular expressions matching columns to exclude from change events (deprecated, use column.exclude.list instead) | | String
-| *camel.component.debezium-sqlserver.column-exclude-list* | Regular expressions matching columns to exclude from change events | | String
-| *camel.component.debezium-sqlserver.column-include-list* | Regular expressions matching columns to include in change events | | String
-| *camel.component.debezium-sqlserver.column-propagate-source-type* | A comma-separated list of regular expressions matching fully-qualified names of columns that adds the columns original type and original length as parameters to the corresponding field schemas in the emitted change records. | | String
-| *camel.component.debezium-sqlserver.column-whitelist* | Regular expressions matching columns to include in change events (deprecated, use column.include.list instead) | | String
-| *camel.component.debezium-sqlserver.configuration* | Allow pre-configured Configurations to be set. The option is a org.apache.camel.component.debezium.configuration.SqlServerConnectorEmbeddedDebeziumConfiguration type. | | SqlServerConnectorEmbeddedDebeziumConfiguration
-| *camel.component.debezium-sqlserver.converters* | Optional list of custom converters that would be used instead of default ones. The converters are defined using '.type' config option and configured using options '.' | | String
-| *camel.component.debezium-sqlserver.database-dbname* | The name of the database the connector should be monitoring. When working with a multi-tenant set-up, must be set to the CDB name. | | String
-| *camel.component.debezium-sqlserver.database-history* | The name of the DatabaseHistory class that should be used to store and recover database schema changes. The configuration properties for the history are prefixed with the 'database.history.' string. | io.debezium.relational.history.FileDatabaseHistory | String
-| *camel.component.debezium-sqlserver.database-history-file-filename* | The path to the file that will be used to record the database history | | String
-| *camel.component.debezium-sqlserver.database-history-kafka-bootstrap-servers* | A list of host/port pairs that the connector will use for establishing the initial connection to the Kafka cluster for retrieving database schema history previously stored by the connector. This should point to the same Kafka cluster used by the Kafka Connect process. | | String
-| *camel.component.debezium-sqlserver.database-history-kafka-recovery-attempts* | The number of attempts in a row that no data are returned from Kafka before recover completes. The maximum amount of time to wait after receiving no data is (recovery.attempts) x (recovery.poll.interval.ms). | 100 | Integer
-| *camel.component.debezium-sqlserver.database-history-kafka-recovery-poll-interval-ms* | The number of milliseconds to wait while polling for persisted data during recovery. The option is a int type. | 100 | Integer
-| *camel.component.debezium-sqlserver.database-history-kafka-topic* | The name of the topic for the database schema history | | String
-| *camel.component.debezium-sqlserver.database-hostname* | Resolvable hostname or IP address of the SQL Server database server. | | String
-| *camel.component.debezium-sqlserver.database-instance* | The SQL Server instance name | | String
-| *camel.component.debezium-sqlserver.database-password* | Password of the SQL Server database user to be used when connecting to the database. | | String
-| *camel.component.debezium-sqlserver.database-port* | Port of the SQL Server database server. | 1433 | Integer
-| *camel.component.debezium-sqlserver.database-server-name* | Unique name that identifies the database server and all recorded offsets, and that is used as a prefix for all schemas and topics. Each distinct installation should have a separate namespace and be monitored by at most one Debezium connector. | | String
-| *camel.component.debezium-sqlserver.database-server-timezone* | The timezone of the server used to correctly shift the commit transaction timestamp on the client sideOptions include: Any valid Java ZoneId | | String
-| *camel.component.debezium-sqlserver.database-user* | Name of the SQL Server database user to be used when connecting to the database. | | String
-| *camel.component.debezium-sqlserver.datatype-propagate-source-type* | A comma-separated list of regular expressions matching the database-specific data type names that adds the data type's original type and original length as parameters to the corresponding field schemas in the emitted change records. | | String
-| *camel.component.debezium-sqlserver.decimal-handling-mode* | Specify how DECIMAL and NUMERIC columns should be represented in change events, including:'precise' (the default) uses java.math.BigDecimal to represent values, which are encoded in the change events using a binary representation and Kafka Connect's 'org.apache.kafka.connect.data.Decimal' type; 'string' uses string to represent values; 'double' represents values using Java's 'double', which may not offer the precision but wil [...]
-| *camel.component.debezium-sqlserver.enabled* | Whether to enable auto configuration of the debezium-sqlserver component. This is enabled by default. | | Boolean
-| *camel.component.debezium-sqlserver.event-processing-failure-handling-mode* | Specify how failures during processing of events (i.e. when encountering a corrupted event) should be handled, including:'fail' (the default) an exception indicating the problematic event and its position is raised, causing the connector to be stopped; 'warn' the problematic event and its position will be logged and the event will be skipped;'ignore' the problematic event will be skipped. | fail | String
-| *camel.component.debezium-sqlserver.heartbeat-interval-ms* | Length of an interval in milli-seconds in in which the connector periodically sends heartbeat messages to a heartbeat topic. Use 0 to disable heartbeat messages. Disabled by default. The option is a int type. | 0 | Integer
-| *camel.component.debezium-sqlserver.heartbeat-topics-prefix* | The prefix that is used to name heartbeat topics.Defaults to __debezium-heartbeat. | __debezium-heartbeat | String
-| *camel.component.debezium-sqlserver.include-schema-changes* | Whether the connector should publish changes in the database schema to a Kafka topic with the same name as the database server ID. Each schema change will be recorded using a key that contains the database name and whose value include logical description of the new schema and optionally the DDL statement(s).The default is 'true'. This is independent of how the connector internally records database history. | true | Boolean
-| *camel.component.debezium-sqlserver.internal-key-converter* | The Converter class that should be used to serialize and deserialize key data for offsets. The default is JSON converter. | org.apache.kafka.connect.json.JsonConverter | String
-| *camel.component.debezium-sqlserver.internal-value-converter* | The Converter class that should be used to serialize and deserialize value data for offsets. The default is JSON converter. | org.apache.kafka.connect.json.JsonConverter | String
-| *camel.component.debezium-sqlserver.max-batch-size* | Maximum size of each batch of source records. Defaults to 2048. | 2048 | Integer
-| *camel.component.debezium-sqlserver.max-queue-size* | Maximum size of the queue for change events read from the database log but not yet recorded or forwarded. Defaults to 8192, and should always be larger than the maximum batch size. | 8192 | Integer
-| *camel.component.debezium-sqlserver.message-key-columns* | A semicolon-separated list of expressions that match fully-qualified tables and column(s) to be used as message key. Each expression must match the pattern ':',where the table names could be defined as (DB_NAME.TABLE_NAME) or (SCHEMA_NAME.TABLE_NAME), depending on the specific connector,and the key columns are a comma-separated list of columns representing the custom key. For any table without an explicit key configuration the [...]
-| *camel.component.debezium-sqlserver.offset-commit-policy* | The name of the Java class of the commit policy. It defines when offsets commit has to be triggered based on the number of events processed and the time elapsed since the last commit. This class must implement the interface 'OffsetCommitPolicy'. The default is a periodic commit policy based upon time intervals. | io.debezium.embedded.spi.OffsetCommitPolicy.PeriodicCommitOffsetPolicy | String
-| *camel.component.debezium-sqlserver.offset-commit-timeout-ms* | Maximum number of milliseconds to wait for records to flush and partition offset data to be committed to offset storage before cancelling the process and restoring the offset data to be committed in a future attempt. The default is 5 seconds. The option is a long type. | 5000 | Long
-| *camel.component.debezium-sqlserver.offset-flush-interval-ms* | Interval at which to try committing offsets. The default is 1 minute. The option is a long type. | 60000 | Long
-| *camel.component.debezium-sqlserver.offset-storage* | The name of the Java class that is responsible for persistence of connector offsets. | org.apache.kafka.connect.storage.FileOffsetBackingStore | String
-| *camel.component.debezium-sqlserver.offset-storage-file-name* | Path to file where offsets are to be stored. Required when offset.storage is set to the FileOffsetBackingStore. | | String
-| *camel.component.debezium-sqlserver.offset-storage-partitions* | The number of partitions used when creating the offset storage topic. Required when offset.storage is set to the 'KafkaOffsetBackingStore'. | | Integer
-| *camel.component.debezium-sqlserver.offset-storage-replication-factor* | Replication factor used when creating the offset storage topic. Required when offset.storage is set to the KafkaOffsetBackingStore | | Integer
-| *camel.component.debezium-sqlserver.offset-storage-topic* | The name of the Kafka topic where offsets are to be stored. Required when offset.storage is set to the KafkaOffsetBackingStore. | | String
-| *camel.component.debezium-sqlserver.poll-interval-ms* | Frequency in milliseconds to wait for new change events to appear after receiving no events. Defaults to 500ms. The option is a long type. | 500 | Long
-| *camel.component.debezium-sqlserver.provide-transaction-metadata* | Enables transaction metadata extraction together with event counting | false | Boolean
-| *camel.component.debezium-sqlserver.query-fetch-size* | The maximum number of records that should be loaded into memory while streaming. A value of 0 uses the default JDBC fetch size. | 0 | Integer
-| *camel.component.debezium-sqlserver.retriable-restart-connector-wait-ms* | Time to wait before restarting connector after retriable exception occurs. Defaults to 10000ms. The option is a long type. | 10000 | Long
-| *camel.component.debezium-sqlserver.sanitize-field-names* | Whether field names will be sanitized to Avro naming conventions | false | Boolean
-| *camel.component.debezium-sqlserver.skipped-operations* | The comma-separated list of operations to skip during streaming, defined as: 'i' for inserts; 'u' for updates; 'd' for deletes. By default, no operations will be skipped. | | String
-| *camel.component.debezium-sqlserver.snapshot-delay-ms* | The number of milliseconds to delay before a snapshot will begin. The option is a long type. | 0 | Long
-| *camel.component.debezium-sqlserver.snapshot-fetch-size* | The maximum number of records that should be loaded into memory while performing a snapshot | | Integer
-| *camel.component.debezium-sqlserver.snapshot-isolation-mode* | Controls which transaction isolation level is used and how long the connector locks the monitored tables. The default is 'repeatable_read', which means that repeatable read isolation level is used. In addition, exclusive locks are taken only during schema snapshot. Using a value of 'exclusive' ensures that the connector holds the exclusive lock (and thus prevents any reads and updates) for all monitored tables during the en [...]
-| *camel.component.debezium-sqlserver.snapshot-lock-timeout-ms* | The maximum number of millis to wait for table locks at the beginning of a snapshot. If locks cannot be acquired in this time frame, the snapshot will be aborted. Defaults to 10 seconds. The option is a long type. | 10000 | Long
-| *camel.component.debezium-sqlserver.snapshot-mode* | The criteria for running a snapshot upon startup of the connector. Options include: 'initial' (the default) to specify the connector should run a snapshot only when no offsets are available for the logical server name; 'schema_only' to specify the connector should run a snapshot of the schema when no offsets are available for the logical server name. | initial | String
-| *camel.component.debezium-sqlserver.snapshot-select-statement-overrides* | This property contains a comma-separated list of fully-qualified tables (DB_NAME.TABLE_NAME) or (SCHEMA_NAME.TABLE_NAME), depending on thespecific connectors . Select statements for the individual tables are specified in further configuration properties, one for each table, identified by the id 'snapshot.select.statement.overrides.DB_NAME.TABLE_NAME' or 'snapshot.select.statement.overrides.SCHEMA_NAME.TABLE_NAME [...]
-| *camel.component.debezium-sqlserver.source-struct-version* | A version of the format of the publicly visible source part in the message | v2 | String
-| *camel.component.debezium-sqlserver.source-timestamp-mode* | Configures the criteria of the attached timestamp within the source record (ts_ms).Options include:'commit', (default) the source timestamp is set to the instant where the record was committed in the database'processing', the source timestamp is set to the instant where the record was processed by Debezium. | commit | String
-| *camel.component.debezium-sqlserver.table-blacklist* | A comma-separated list of regular expressions that match the fully-qualified names of tables to be excluded from monitoring (deprecated, use table.exclude.list instead) | | String
-| *camel.component.debezium-sqlserver.table-exclude-list* | A comma-separated list of regular expressions that match the fully-qualified names of tables to be excluded from monitoring | | String
-| *camel.component.debezium-sqlserver.table-ignore-builtin* | Flag specifying whether built-in tables should be ignored. | true | Boolean
-| *camel.component.debezium-sqlserver.table-include-list* | The tables for which changes are to be captured | | String
-| *camel.component.debezium-sqlserver.table-whitelist* | The tables for which changes are to be captured (deprecated, use table.include.list instead) | | String
-| *camel.component.debezium-sqlserver.time-precision-mode* | Time, date, and timestamps can be represented with different kinds of precisions, including:'adaptive' (the default) bases the precision of time, date, and timestamp values on the database column's precision; 'adaptive_time_microseconds' like 'adaptive' mode, but TIME fields always use microseconds precision;'connect' always represents time, date, and timestamp values using Kafka Connect's built-in representations for Time, Dat [...]
-| *camel.component.debezium-sqlserver.tombstones-on-delete* | Whether delete operations should be represented by a delete event and a subsquenttombstone event (true) or only by a delete event (false). Emitting the tombstone event (the default behavior) allows Kafka to completely delete all events pertaining to the given key once the source record got deleted. | false | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-digitalocean-starter/src/main/docs/digitalocean-starter.adoc b/components-starter/camel-digitalocean-starter/src/main/docs/digitalocean-starter.adoc
deleted file mode 100644
index c57dc59..0000000
--- a/components-starter/camel-digitalocean-starter/src/main/docs/digitalocean-starter.adoc
+++ /dev/null
@@ -1,31 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for digitalocean
-
-== Spring Boot Auto-Configuration
-
-When using digitalocean with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-digitalocean-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 3 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.digitalocean.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.digitalocean.enabled* | Whether to enable auto configuration of the digitalocean component. This is enabled by default. | | Boolean
-| *camel.component.digitalocean.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is process [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-direct-starter/src/main/docs/direct-starter.adoc b/components-starter/camel-direct-starter/src/main/docs/direct-starter.adoc
deleted file mode 100644
index 3d7126a..0000000
--- a/components-starter/camel-direct-starter/src/main/docs/direct-starter.adoc
+++ /dev/null
@@ -1,34 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for direct
-
-== Spring Boot Auto-Configuration
-
-When using direct with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-direct-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 6 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.direct.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.direct.block* | If sending a message to a direct endpoint which has no active consumer, then we can tell the producer to block and wait for the consumer to become active. | true | Boolean
-| *camel.component.direct.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.direct.enabled* | Whether to enable auto configuration of the direct component. This is enabled by default. | | Boolean
-| *camel.component.direct.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed the [...]
-| *camel.component.direct.timeout* | The timeout value to use if block is enabled. | 30000 | Long
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-directvm-starter/src/main/docs/directvm-starter.adoc b/components-starter/camel-directvm-starter/src/main/docs/directvm-starter.adoc
deleted file mode 100644
index cfcfacd..0000000
--- a/components-starter/camel-directvm-starter/src/main/docs/directvm-starter.adoc
+++ /dev/null
@@ -1,36 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for directvm
-
-== Spring Boot Auto-Configuration
-
-When using directvm with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-directvm-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 8 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.direct-vm.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.direct-vm.block* | If sending a message to a direct endpoint which has no active consumer, then we can tell the producer to block and wait for the consumer to become active. | true | Boolean
-| *camel.component.direct-vm.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.direct-vm.enabled* | Whether to enable auto configuration of the direct-vm component. This is enabled by default. | | Boolean
-| *camel.component.direct-vm.header-filter-strategy* | Sets a HeaderFilterStrategy that will only be applied on producer endpoints (on both directions: request and response). Default value: none. The option is a org.apache.camel.spi.HeaderFilterStrategy type. | | HeaderFilterStrategy
-| *camel.component.direct-vm.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed [...]
-| *camel.component.direct-vm.propagate-properties* | Whether to propagate or not properties from the producer side to the consumer side, and vice versa. Default value: true. | true | Boolean
-| *camel.component.direct-vm.timeout* | The timeout value to use if block is enabled. | 30000 | Long
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-disruptor-starter/src/main/docs/disruptor-starter.adoc b/components-starter/camel-disruptor-starter/src/main/docs/disruptor-starter.adoc
deleted file mode 100644
index df2cf00..0000000
--- a/components-starter/camel-disruptor-starter/src/main/docs/disruptor-starter.adoc
+++ /dev/null
@@ -1,48 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for disruptor
-
-== Spring Boot Auto-Configuration
-
-When using disruptor with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-disruptor-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 20 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.disruptor-vm.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.disruptor-vm.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.disruptor-vm.buffer-size* | To configure the ring buffer size | 1024 | Integer
-| *camel.component.disruptor-vm.default-block-when-full* | To configure the default value for block when full The default value is true. | true | Boolean
-| *camel.component.disruptor-vm.default-concurrent-consumers* | To configure the default number of concurrent consumers | 1 | Integer
-| *camel.component.disruptor-vm.default-multiple-consumers* | To configure the default value for multiple consumers | false | Boolean
-| *camel.component.disruptor-vm.default-producer-type* | To configure the default value for DisruptorProducerType The default value is Multi. | | DisruptorProducerType
-| *camel.component.disruptor-vm.default-wait-strategy* | To configure the default value for DisruptorWaitStrategy The default value is Blocking. | | DisruptorWaitStrategy
-| *camel.component.disruptor-vm.enabled* | Whether to enable auto configuration of the disruptor-vm component. This is enabled by default. | | Boolean
-| *camel.component.disruptor-vm.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is process [...]
-| *camel.component.disruptor.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.disruptor.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.disruptor.buffer-size* | To configure the ring buffer size | 1024 | Integer
-| *camel.component.disruptor.default-block-when-full* | To configure the default value for block when full The default value is true. | true | Boolean
-| *camel.component.disruptor.default-concurrent-consumers* | To configure the default number of concurrent consumers | 1 | Integer
-| *camel.component.disruptor.default-multiple-consumers* | To configure the default value for multiple consumers | false | Boolean
-| *camel.component.disruptor.default-producer-type* | To configure the default value for DisruptorProducerType The default value is Multi. | | DisruptorProducerType
-| *camel.component.disruptor.default-wait-strategy* | To configure the default value for DisruptorWaitStrategy The default value is Blocking. | | DisruptorWaitStrategy
-| *camel.component.disruptor.enabled* | Whether to enable auto configuration of the disruptor component. This is enabled by default. | | Boolean
-| *camel.component.disruptor.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-djl-starter/src/main/docs/djl-starter.adoc b/components-starter/camel-djl-starter/src/main/docs/djl-starter.adoc
deleted file mode 100644
index 33f13c0..0000000
--- a/components-starter/camel-djl-starter/src/main/docs/djl-starter.adoc
+++ /dev/null
@@ -1,31 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for djl
-
-== Spring Boot Auto-Configuration
-
-When using djl with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-djl-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 3 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.djl.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.djl.enabled* | Whether to enable auto configuration of the djl component. This is enabled by default. | | Boolean
-| *camel.component.djl.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then c [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-dns-starter/src/main/docs/dns-starter.adoc b/components-starter/camel-dns-starter/src/main/docs/dns-starter.adoc
deleted file mode 100644
index 1e10599..0000000
--- a/components-starter/camel-dns-starter/src/main/docs/dns-starter.adoc
+++ /dev/null
@@ -1,31 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for dns
-
-== Spring Boot Auto-Configuration
-
-When using dns with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-dns-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 3 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.dns.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.dns.enabled* | Whether to enable auto configuration of the dns component. This is enabled by default. | | Boolean
-| *camel.component.dns.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then c [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-docker-starter/src/main/docs/docker-starter.adoc b/components-starter/camel-docker-starter/src/main/docs/docker-starter.adoc
deleted file mode 100644
index e725fd4..0000000
--- a/components-starter/camel-docker-starter/src/main/docs/docker-starter.adoc
+++ /dev/null
@@ -1,50 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for docker
-
-== Spring Boot Auto-Configuration
-
-When using docker with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-docker-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 22 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.docker.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.docker.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.docker.cert-path* | Location containing the SSL certificate chain | | String
-| *camel.component.docker.cmd-exec-factory* | The fully qualified class name of the DockerCmdExecFactory implementation to use | com.github.dockerjava.netty.NettyDockerCmdExecFactory | String
-| *camel.component.docker.configuration* | To use the shared docker configuration. The option is a org.apache.camel.component.docker.DockerConfiguration type. | | DockerConfiguration
-| *camel.component.docker.email* | Email address associated with the user | | String
-| *camel.component.docker.enabled* | Whether to enable auto configuration of the docker component. This is enabled by default. | | Boolean
-| *camel.component.docker.follow-redirect-filter* | Whether to follow redirect filter | false | Boolean
-| *camel.component.docker.host* | Docker host | localhost | String
-| *camel.component.docker.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed the [...]
-| *camel.component.docker.logging-filter* | Whether to use logging filter | false | Boolean
-| *camel.component.docker.max-per-route-connections* | Maximum route connections | 100 | Integer
-| *camel.component.docker.max-total-connections* | Maximum total connections | 100 | Integer
-| *camel.component.docker.parameters* | Additional configuration parameters as key/value pairs | | Map
-| *camel.component.docker.password* | Password to authenticate with | | String
-| *camel.component.docker.port* | Docker port | 2375 | Integer
-| *camel.component.docker.request-timeout* | Request timeout for response (in seconds) | | Integer
-| *camel.component.docker.secure* | Use HTTPS communication | false | Boolean
-| *camel.component.docker.server-address* | Server address for docker registry. | https://index.docker.io/v1/ | String
-| *camel.component.docker.socket* | Socket connection mode | true | Boolean
-| *camel.component.docker.tls-verify* | Check TLS | false | Boolean
-| *camel.component.docker.username* | User name to authenticate with | | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-dozer-starter/src/main/docs/dozer-starter.adoc b/components-starter/camel-dozer-starter/src/main/docs/dozer-starter.adoc
deleted file mode 100644
index 5eb5b1a..0000000
--- a/components-starter/camel-dozer-starter/src/main/docs/dozer-starter.adoc
+++ /dev/null
@@ -1,31 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for dozer
-
-== Spring Boot Auto-Configuration
-
-When using dozer with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-dozer-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 3 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.dozer.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.dozer.enabled* | Whether to enable auto configuration of the dozer component. This is enabled by default. | | Boolean
-| *camel.component.dozer.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-drill-starter/src/main/docs/drill-starter.adoc b/components-starter/camel-drill-starter/src/main/docs/drill-starter.adoc
deleted file mode 100644
index c61abf6..0000000
--- a/components-starter/camel-drill-starter/src/main/docs/drill-starter.adoc
+++ /dev/null
@@ -1,31 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for drill
-
-== Spring Boot Auto-Configuration
-
-When using drill with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-drill-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 3 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.drill.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.drill.enabled* | Whether to enable auto configuration of the drill component. This is enabled by default. | | Boolean
-| *camel.component.drill.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-dropbox-starter/src/main/docs/dropbox-starter.adoc b/components-starter/camel-dropbox-starter/src/main/docs/dropbox-starter.adoc
deleted file mode 100644
index e26a1c9..0000000
--- a/components-starter/camel-dropbox-starter/src/main/docs/dropbox-starter.adoc
+++ /dev/null
@@ -1,32 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for dropbox
-
-== Spring Boot Auto-Configuration
-
-When using dropbox with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-dropbox-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 4 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.dropbox.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.dropbox.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.dropbox.enabled* | Whether to enable auto configuration of the dropbox component. This is enabled by default. | | Boolean
-| *camel.component.dropbox.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-ehcache-starter/src/main/docs/ehcache-starter.adoc b/components-starter/camel-ehcache-starter/src/main/docs/ehcache-starter.adoc
deleted file mode 100644
index 5b86b0f..0000000
--- a/components-starter/camel-ehcache-starter/src/main/docs/ehcache-starter.adoc
+++ /dev/null
@@ -1,49 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for ehcache
-
-== Spring Boot Auto-Configuration
-
-When using ehcache with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-ehcache-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 21 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.ehcache.action* | To configure the default cache action. If an action is set in the message header, then the operation from the header takes precedence. | | String
-| *camel.component.ehcache.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.ehcache.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.ehcache.cache-manager* | The cache manager. The option is a org.ehcache.CacheManager type. | | CacheManager
-| *camel.component.ehcache.cache-manager-configuration* | The cache manager configuration. The option is a org.ehcache.config.Configuration type. | | Configuration
-| *camel.component.ehcache.configuration* | The default cache configuration to be used to create caches. The option is a org.ehcache.config.CacheConfiguration type. | | CacheConfiguration
-| *camel.component.ehcache.configuration-uri* | URI pointing to the Ehcache XML configuration file's location | | String
-| *camel.component.ehcache.configurations* | A map of cache configuration to be used to create caches. | | Map
-| *camel.component.ehcache.create-cache-if-not-exist* | Configure if a cache need to be created if it does exist or can't be pre-configured. | true | Boolean
-| *camel.component.ehcache.customizer.cache-configuration.enabled* | Enable or disable the cache-configuration customizer. | true | Boolean
-| *camel.component.ehcache.customizer.cache-configuration.mode* | Configure if the cache configurations have be added or they have to replace those already configured on the component. | | CacheConfigurationCustomizerConfiguration$Mode
-| *camel.component.ehcache.customizer.cache-manager.enabled* | Enable or disable the cache-manager customizer. | true | Boolean
-| *camel.component.ehcache.customizer.cache-manager.override* | Configure if the cache manager eventually set on the component should be overridden by the customizer. | false | Boolean
-| *camel.component.ehcache.enabled* | Whether to enable auto configuration of the ehcache component. This is enabled by default. | | Boolean
-| *camel.component.ehcache.event-firing* | Set the delivery mode (synchronous, asynchronous) | | EventFiring
-| *camel.component.ehcache.event-ordering* | Set the delivery mode (ordered, unordered) | | EventOrdering
-| *camel.component.ehcache.event-types* | Set the type of events to listen for (EVICTED,EXPIRED,REMOVED,CREATED,UPDATED). You can specify multiple entries separated by comma. | | String
-| *camel.component.ehcache.key* | To configure the default action key. If a key is set in the message header, then the key from the header takes precedence. The option is a java.lang.Object type. | | Object
-| *camel.component.ehcache.key-type* | The cache key type, default java.lang.Object | | String
-| *camel.component.ehcache.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
-| *camel.component.ehcache.value-type* | The cache value type, default java.lang.Object | | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-elasticsearch-rest-starter/src/main/docs/elasticsearch-rest-starter.adoc b/components-starter/camel-elasticsearch-rest-starter/src/main/docs/elasticsearch-rest-starter.adoc
deleted file mode 100644
index a285b72..0000000
--- a/components-starter/camel-elasticsearch-rest-starter/src/main/docs/elasticsearch-rest-starter.adoc
+++ /dev/null
@@ -1,42 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for elasticsearch-rest
-
-== Spring Boot Auto-Configuration
-
-When using elasticsearch-rest with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-elasticsearch-rest-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 14 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.elasticsearch-rest.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.elasticsearch-rest.client* | To use an existing configured Elasticsearch client, instead of creating a client per endpoint. This allow to customize the client with specific settings. The option is a org.elasticsearch.client.RestClient type. | | RestClient
-| *camel.component.elasticsearch-rest.connection-timeout* | The time in ms to wait before connection will timeout. | 30000 | Integer
-| *camel.component.elasticsearch-rest.enable-s-s-l* | Enable SSL | false | Boolean
-| *camel.component.elasticsearch-rest.enable-sniffer* | Enable automatically discover nodes from a running Elasticsearch cluster | false | Boolean
-| *camel.component.elasticsearch-rest.enabled* | Whether to enable auto configuration of the elasticsearch-rest component. This is enabled by default. | | Boolean
-| *camel.component.elasticsearch-rest.host-addresses* | Comma separated list with ip:port formatted remote transport addresses to use. The ip and port options must be left blank for hostAddresses to be considered instead. | | String
-| *camel.component.elasticsearch-rest.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is p [...]
-| *camel.component.elasticsearch-rest.max-retry-timeout* | The time in ms before retry | 30000 | Integer
-| *camel.component.elasticsearch-rest.password* | Password for authenticate | | String
-| *camel.component.elasticsearch-rest.sniff-after-failure-delay* | The delay of a sniff execution scheduled after a failure (in milliseconds) | 60000 | Integer
-| *camel.component.elasticsearch-rest.sniffer-interval* | The interval between consecutive ordinary sniff executions in milliseconds. Will be honoured when sniffOnFailure is disabled or when there are no failures between consecutive sniff executions | 300000 | Integer
-| *camel.component.elasticsearch-rest.socket-timeout* | The timeout in ms to wait before the socket will timeout. | 30000 | Integer
-| *camel.component.elasticsearch-rest.user* | Basic authenticate user | | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-elsql-starter/src/main/docs/elsql-starter.adoc b/components-starter/camel-elsql-starter/src/main/docs/elsql-starter.adoc
deleted file mode 100644
index 3dd1f56..0000000
--- a/components-starter/camel-elsql-starter/src/main/docs/elsql-starter.adoc
+++ /dev/null
@@ -1,35 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for elsql
-
-== Spring Boot Auto-Configuration
-
-When using elsql with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-elsql-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 7 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.elsql.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.elsql.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.elsql.database-vendor* | To use a vendor specific com.opengamma.elsql.ElSqlConfig | | ElSqlDatabaseVendor
-| *camel.component.elsql.el-sql-config* | To use a specific configured ElSqlConfig. It may be better to use the databaseVendor option instead. The option is a com.opengamma.elsql.ElSqlConfig type. | | ElSqlConfig
-| *camel.component.elsql.enabled* | Whether to enable auto configuration of the elsql component. This is enabled by default. | | Boolean
-| *camel.component.elsql.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
-| *camel.component.elsql.resource-uri* | The resource file which contains the elsql SQL statements to use. You can specify multiple resources separated by comma. The resources are loaded on the classpath by default, you can prefix with file: to load from file system. Notice you can set this option on the component and then you do not have to configure this on the endpoint. | | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-etcd-starter/src/main/docs/etcd-starter.adoc b/components-starter/camel-etcd-starter/src/main/docs/etcd-starter.adoc
deleted file mode 100644
index ef4e183..0000000
--- a/components-starter/camel-etcd-starter/src/main/docs/etcd-starter.adoc
+++ /dev/null
@@ -1,71 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for etcd
-
-== Spring Boot Auto-Configuration
-
-When using etcd with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-etcd-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 43 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.etcd-keys.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.etcd-keys.configuration* | Component configuration. The option is a org.apache.camel.component.etcd.EtcdConfiguration type. | | EtcdConfiguration
-| *camel.component.etcd-keys.enabled* | Whether to enable auto configuration of the etcd-keys component. This is enabled by default. | | Boolean
-| *camel.component.etcd-keys.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed [...]
-| *camel.component.etcd-keys.password* | The password to use for basic authentication. | | String
-| *camel.component.etcd-keys.recursive* | To apply an action recursively. | false | Boolean
-| *camel.component.etcd-keys.service-path* | The path to look for for service discovery | /services/ | String
-| *camel.component.etcd-keys.ssl-context-parameters* | To configure security using SSLContextParameters. The option is a org.apache.camel.support.jsse.SSLContextParameters type. | | SSLContextParameters
-| *camel.component.etcd-keys.time-to-live* | To set the lifespan of a key in milliseconds. | | Integer
-| *camel.component.etcd-keys.timeout* | To set the maximum time an action could take to complete. The option is a java.lang.Long type. | | Long
-| *camel.component.etcd-keys.uris* | To set the URIs the client connects. | http://localhost:2379,http://localhost:4001 | String
-| *camel.component.etcd-keys.use-global-ssl-context-parameters* | Enable usage of global SSL context parameters. | false | Boolean
-| *camel.component.etcd-keys.user-name* | The user name to use for basic authentication. | | String
-| *camel.component.etcd-stats.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.etcd-stats.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.etcd-stats.configuration* | Component configuration. The option is a org.apache.camel.component.etcd.EtcdConfiguration type. | | EtcdConfiguration
-| *camel.component.etcd-stats.enabled* | Whether to enable auto configuration of the etcd-stats component. This is enabled by default. | | Boolean
-| *camel.component.etcd-stats.from-index* | The index to watch from | 0 | Long
-| *camel.component.etcd-stats.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed [...]
-| *camel.component.etcd-stats.password* | The password to use for basic authentication. | | String
-| *camel.component.etcd-stats.recursive* | To apply an action recursively. | false | Boolean
-| *camel.component.etcd-stats.send-empty-exchange-on-timeout* | To send an empty message in case of timeout watching for a key. | false | Boolean
-| *camel.component.etcd-stats.service-path* | The path to look for for service discovery | /services/ | String
-| *camel.component.etcd-stats.ssl-context-parameters* | To configure security using SSLContextParameters. The option is a org.apache.camel.support.jsse.SSLContextParameters type. | | SSLContextParameters
-| *camel.component.etcd-stats.time-to-live* | To set the lifespan of a key in milliseconds. | | Integer
-| *camel.component.etcd-stats.timeout* | To set the maximum time an action could take to complete. The option is a java.lang.Long type. | | Long
-| *camel.component.etcd-stats.uris* | To set the URIs the client connects. | http://localhost:2379,http://localhost:4001 | String
-| *camel.component.etcd-stats.use-global-ssl-context-parameters* | Enable usage of global SSL context parameters. | false | Boolean
-| *camel.component.etcd-stats.user-name* | The user name to use for basic authentication. | | String
-| *camel.component.etcd-watch.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.etcd-watch.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.etcd-watch.configuration* | Component configuration. The option is a org.apache.camel.component.etcd.EtcdConfiguration type. | | EtcdConfiguration
-| *camel.component.etcd-watch.enabled* | Whether to enable auto configuration of the etcd-watch component. This is enabled by default. | | Boolean
-| *camel.component.etcd-watch.from-index* | The index to watch from | 0 | Long
-| *camel.component.etcd-watch.password* | The password to use for basic authentication. | | String
-| *camel.component.etcd-watch.recursive* | To apply an action recursively. | false | Boolean
-| *camel.component.etcd-watch.send-empty-exchange-on-timeout* | To send an empty message in case of timeout watching for a key. | false | Boolean
-| *camel.component.etcd-watch.service-path* | The path to look for for service discovery | /services/ | String
-| *camel.component.etcd-watch.ssl-context-parameters* | To configure security using SSLContextParameters. The option is a org.apache.camel.support.jsse.SSLContextParameters type. | | SSLContextParameters
-| *camel.component.etcd-watch.timeout* | To set the maximum time an action could take to complete. The option is a java.lang.Long type. | | Long
-| *camel.component.etcd-watch.uris* | To set the URIs the client connects. | http://localhost:2379,http://localhost:4001 | String
-| *camel.component.etcd-watch.use-global-ssl-context-parameters* | Enable usage of global SSL context parameters. | false | Boolean
-| *camel.component.etcd-watch.user-name* | The user name to use for basic authentication. | | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-exec-starter/src/main/docs/exec-starter.adoc b/components-starter/camel-exec-starter/src/main/docs/exec-starter.adoc
deleted file mode 100644
index 8cf3ccb..0000000
--- a/components-starter/camel-exec-starter/src/main/docs/exec-starter.adoc
+++ /dev/null
@@ -1,31 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for exec
-
-== Spring Boot Auto-Configuration
-
-When using exec with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-exec-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 3 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.exec.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.exec.enabled* | Whether to enable auto configuration of the exec component. This is enabled by default. | | Boolean
-| *camel.component.exec.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-facebook-starter/src/main/docs/facebook-starter.adoc b/components-starter/camel-facebook-starter/src/main/docs/facebook-starter.adoc
deleted file mode 100644
index 4c975ce..0000000
--- a/components-starter/camel-facebook-starter/src/main/docs/facebook-starter.adoc
+++ /dev/null
@@ -1,60 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for facebook
-
-== Spring Boot Auto-Configuration
-
-When using facebook with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-facebook-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 32 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.facebook.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.facebook.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.facebook.client-u-r-l* | Facebook4J API client URL | | String
-| *camel.component.facebook.client-version* | Facebook4J client API version | | String
-| *camel.component.facebook.configuration* | To use the shared configuration. The option is a org.apache.camel.component.facebook.config.FacebookConfiguration type. | | FacebookConfiguration
-| *camel.component.facebook.debug-enabled* | Enables deubg output. Effective only with the embedded logger | false | Boolean
-| *camel.component.facebook.enabled* | Whether to enable auto configuration of the facebook component. This is enabled by default. | | Boolean
-| *camel.component.facebook.gzip-enabled* | Use Facebook GZIP encoding | true | Boolean
-| *camel.component.facebook.http-connection-timeout* | Http connection timeout in milliseconds | 20000 | Integer
-| *camel.component.facebook.http-default-max-per-route* | HTTP maximum connections per route | 2 | Integer
-| *camel.component.facebook.http-max-total-connections* | HTTP maximum total connections | 20 | Integer
-| *camel.component.facebook.http-proxy-host* | HTTP proxy server host name | | String
-| *camel.component.facebook.http-proxy-password* | HTTP proxy server password | | String
-| *camel.component.facebook.http-proxy-port* | HTTP proxy server port | | Integer
-| *camel.component.facebook.http-proxy-user* | HTTP proxy server user name | | String
-| *camel.component.facebook.http-read-timeout* | Http read timeout in milliseconds | 120000 | Integer
-| *camel.component.facebook.http-retry-count* | Number of HTTP retries | 0 | Integer
-| *camel.component.facebook.http-retry-interval-seconds* | HTTP retry interval in seconds | 5 | Integer
-| *camel.component.facebook.http-streaming-read-timeout* | HTTP streaming read timeout in milliseconds | 40000 | Integer
-| *camel.component.facebook.json-store-enabled* | If set to true, raw JSON forms will be stored in DataObjectFactory | false | Boolean
-| *camel.component.facebook.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed t [...]
-| *camel.component.facebook.mbean-enabled* | If set to true, Facebook4J mbean will be registerd | false | Boolean
-| *camel.component.facebook.o-auth-access-token* | The user access token | | String
-| *camel.component.facebook.o-auth-access-token-u-r-l* | OAuth access token URL | https://graph.facebook.com/oauth/access_token | String
-| *camel.component.facebook.o-auth-app-id* | The application Id | | String
-| *camel.component.facebook.o-auth-app-secret* | The application Secret | | String
-| *camel.component.facebook.o-auth-authorization-u-r-l* | OAuth authorization URL | https://www.facebook.com/dialog/oauth | String
-| *camel.component.facebook.o-auth-permissions* | Default OAuth permissions. Comma separated permission names. See \https://developers.facebook.com/docs/reference/login/#permissions for the detail | | String
-| *camel.component.facebook.pretty-debug-enabled* | Prettify JSON debug output if set to true | false | Boolean
-| *camel.component.facebook.rest-base-u-r-l* | API base URL | https://graph.facebook.com/ | String
-| *camel.component.facebook.use-s-s-l* | Use SSL | true | Boolean
-| *camel.component.facebook.video-base-u-r-l* | Video API base URL | https://graph-video.facebook.com/ | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-fastjson-starter/src/main/docs/fastjson-starter.adoc b/components-starter/camel-fastjson-starter/src/main/docs/fastjson-starter.adoc
deleted file mode 100644
index a8a186b..0000000
--- a/components-starter/camel-fastjson-starter/src/main/docs/fastjson-starter.adoc
+++ /dev/null
@@ -1,31 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for fastjson
-
-== Spring Boot Auto-Configuration
-
-When using fastjson with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-fastjson-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 3 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.dataformat.json-fastjson.content-type-header* | Whether the data format should set the Content-Type header with the type from the data format. For example application/xml for data formats marshalling to XML, or application/json for data formats marshalling to JSON | true | Boolean
-| *camel.dataformat.json-fastjson.enabled* | Whether to enable auto configuration of the json-fastjson data format. This is enabled by default. | | Boolean
-| *camel.dataformat.json-fastjson.unmarshal-type-name* | Class name of the java type to use when unmarshalling | | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-fhir-starter/src/main/docs/fhir-starter.adoc b/components-starter/camel-fhir-starter/src/main/docs/fhir-starter.adoc
deleted file mode 100644
index acff30c..0000000
--- a/components-starter/camel-fhir-starter/src/main/docs/fhir-starter.adoc
+++ /dev/null
@@ -1,84 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for fhir
-
-== Spring Boot Auto-Configuration
-
-When using fhir with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-fhir-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 56 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.fhir.access-token* | OAuth access token | | String
-| *camel.component.fhir.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.fhir.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.fhir.client* | To use the custom client. The option is a ca.uhn.fhir.rest.client.api.IGenericClient type. | | IGenericClient
-| *camel.component.fhir.client-factory* | To use the custom client factory. The option is a ca.uhn.fhir.rest.client.api.IRestfulClientFactory type. | | IRestfulClientFactory
-| *camel.component.fhir.compress* | Compresses outgoing (POST/PUT) contents to the GZIP format | false | Boolean
-| *camel.component.fhir.configuration* | To use the shared configuration. The option is a org.apache.camel.component.fhir.FhirConfiguration type. | | FhirConfiguration
-| *camel.component.fhir.connection-timeout* | How long to try and establish the initial TCP connection (in ms) | 10000 | Integer
-| *camel.component.fhir.defer-model-scanning* | When this option is set, model classes will not be scanned for children until the child list for the given type is actually accessed. | false | Boolean
-| *camel.component.fhir.enabled* | Whether to enable auto configuration of the fhir component. This is enabled by default. | | Boolean
-| *camel.component.fhir.encoding* | Encoding to use for all request | | String
-| *camel.component.fhir.fhir-context* | FhirContext is an expensive object to create. To avoid creating multiple instances, it can be set directly. The option is a ca.uhn.fhir.context.FhirContext type. | | FhirContext
-| *camel.component.fhir.fhir-version* | The FHIR Version to use | R4 | String
-| *camel.component.fhir.force-conformance-check* | Force conformance check | false | Boolean
-| *camel.component.fhir.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
-| *camel.component.fhir.log* | Will log every requests and responses | false | Boolean
-| *camel.component.fhir.password* | Username to use for basic authentication | | String
-| *camel.component.fhir.pretty-print* | Pretty print all request | false | Boolean
-| *camel.component.fhir.proxy-host* | The proxy host | | String
-| *camel.component.fhir.proxy-password* | The proxy password | | String
-| *camel.component.fhir.proxy-port* | The proxy port | | Integer
-| *camel.component.fhir.proxy-user* | The proxy username | | String
-| *camel.component.fhir.server-url* | The FHIR server base URL | | String
-| *camel.component.fhir.session-cookie* | HTTP session cookie to add to every request | | String
-| *camel.component.fhir.socket-timeout* | How long to block for individual read/write operations (in ms) | 10000 | Integer
-| *camel.component.fhir.summary* | Request that the server modify the response using the _summary param | | String
-| *camel.component.fhir.username* | Username to use for basic authentication | | String
-| *camel.component.fhir.validation-mode* | When should Camel validate the FHIR Server's conformance statement | ONCE | String
-| *camel.dataformat.fhirjson.content-type-header* | Whether the data format should set the Content-Type header with the type from the data format. For example application/xml for data formats marshalling to XML, or application/json for data formats marshalling to JSON | true | Boolean
-| *camel.dataformat.fhirjson.dont-encode-elements* | If provided, specifies the elements which should NOT be encoded. Valid values for this field would include: Patient - Don't encode patient and all its children Patient.name - Don't encode the patient's name Patient.name.family - Don't encode the patient's family name .text - Don't encode the text element on any resource (only the very first position may contain a wildcard) DSTU2 note: Note that values including meta, such as Patient.me [...]
-| *camel.dataformat.fhirjson.dont-strip-versions-from-references-at-paths* | If supplied value(s), any resource references at the specified paths will have their resource versions encoded instead of being automatically stripped during the encoding process. This setting has no effect on the parsing process. This method provides a finer-grained level of control than setStripVersionsFromReferences(String) and any paths specified by this method will be encoded even if setStripVersionsFromRef [...]
-| *camel.dataformat.fhirjson.enabled* | Whether to enable auto configuration of the fhirJson data format. This is enabled by default. | | Boolean
-| *camel.dataformat.fhirjson.encode-elements* | If provided, specifies the elements which should be encoded, to the exclusion of all others. Valid values for this field would include: Patient - Encode patient and all its children Patient.name - Encode only the patient's name Patient.name.family - Encode only the patient's family name .text - Encode the text element on any resource (only the very first position may contain a wildcard) .(mandatory) - This is a special case which causes any [...]
-| *camel.dataformat.fhirjson.encode-elements-applies-to-child-resources-only* | If set to true (default is false), the values supplied to setEncodeElements(Set) will not be applied to the root resource (typically a Bundle), but will be applied to any sub-resources contained within it (i.e. search result resources in that bundle) | false | Boolean
-| *camel.dataformat.fhirjson.fhir-version* | The version of FHIR to use. Possible values are: DSTU2,DSTU2_HL7ORG,DSTU2_1,DSTU3,R4 | DSTU3 | String
-| *camel.dataformat.fhirjson.omit-resource-id* | If set to true (default is false) the ID of any resources being encoded will not be included in the output. Note that this does not apply to contained resources, only to root resources. In other words, if this is set to true, contained resources will still have local IDs but the outer/containing ID will not have an ID. | false | Boolean
-| *camel.dataformat.fhirjson.override-resource-id-with-bundle-entry-full-url* | If set to true (which is the default), the Bundle.entry.fullUrl will override the Bundle.entry.resource's resource id if the fullUrl is defined. This behavior happens when parsing the source data into a Bundle object. Set this to false if this is not the desired behavior (e.g. the client code wishes to perform additional validation checks between the fullUrl and the resource id). | false | Boolean
-| *camel.dataformat.fhirjson.pretty-print* | Sets the pretty print flag, meaning that the parser will encode resources with human-readable spacing and newlines between elements instead of condensing output as much as possible. | false | Boolean
-| *camel.dataformat.fhirjson.server-base-url* | Sets the server's base URL used by this parser. If a value is set, resource references will be turned into relative references if they are provided as absolute URLs but have a base matching the given base. | | String
-| *camel.dataformat.fhirjson.strip-versions-from-references* | If set to true (which is the default), resource references containing a version will have the version removed when the resource is encoded. This is generally good behaviour because in most situations, references from one resource to another should be to the resource by ID, not by ID and version. In some cases though, it may be desirable to preserve the version in resource links. In that case, this value should be set to false [...]
-| *camel.dataformat.fhirjson.summary-mode* | If set to true (default is false) only elements marked by the FHIR specification as being summary elements will be included. | false | Boolean
-| *camel.dataformat.fhirjson.suppress-narratives* | If set to true (default is false), narratives will not be included in the encoded values. | false | Boolean
-| *camel.dataformat.fhirxml.content-type-header* | Whether the data format should set the Content-Type header with the type from the data format. For example application/xml for data formats marshalling to XML, or application/json for data formats marshalling to JSON | true | Boolean
-| *camel.dataformat.fhirxml.dont-encode-elements* | If provided, specifies the elements which should NOT be encoded. Valid values for this field would include: Patient - Don't encode patient and all its children Patient.name - Don't encode the patient's name Patient.name.family - Don't encode the patient's family name .text - Don't encode the text element on any resource (only the very first position may contain a wildcard) DSTU2 note: Note that values including meta, such as Patient.met [...]
-| *camel.dataformat.fhirxml.dont-strip-versions-from-references-at-paths* | If supplied value(s), any resource references at the specified paths will have their resource versions encoded instead of being automatically stripped during the encoding process. This setting has no effect on the parsing process. This method provides a finer-grained level of control than setStripVersionsFromReferences(String) and any paths specified by this method will be encoded even if setStripVersionsFromRefe [...]
-| *camel.dataformat.fhirxml.enabled* | Whether to enable auto configuration of the fhirXml data format. This is enabled by default. | | Boolean
-| *camel.dataformat.fhirxml.encode-elements* | If provided, specifies the elements which should be encoded, to the exclusion of all others. Valid values for this field would include: Patient - Encode patient and all its children Patient.name - Encode only the patient's name Patient.name.family - Encode only the patient's family name .text - Encode the text element on any resource (only the very first position may contain a wildcard) .(mandatory) - This is a special case which causes any [...]
-| *camel.dataformat.fhirxml.encode-elements-applies-to-child-resources-only* | If set to true (default is false), the values supplied to setEncodeElements(Set) will not be applied to the root resource (typically a Bundle), but will be applied to any sub-resources contained within it (i.e. search result resources in that bundle) | false | Boolean
-| *camel.dataformat.fhirxml.fhir-version* | The version of FHIR to use. Possible values are: DSTU2,DSTU2_HL7ORG,DSTU2_1,DSTU3,R4 | DSTU3 | String
-| *camel.dataformat.fhirxml.omit-resource-id* | If set to true (default is false) the ID of any resources being encoded will not be included in the output. Note that this does not apply to contained resources, only to root resources. In other words, if this is set to true, contained resources will still have local IDs but the outer/containing ID will not have an ID. | false | Boolean
-| *camel.dataformat.fhirxml.override-resource-id-with-bundle-entry-full-url* | If set to true (which is the default), the Bundle.entry.fullUrl will override the Bundle.entry.resource's resource id if the fullUrl is defined. This behavior happens when parsing the source data into a Bundle object. Set this to false if this is not the desired behavior (e.g. the client code wishes to perform additional validation checks between the fullUrl and the resource id). | false | Boolean
-| *camel.dataformat.fhirxml.pretty-print* | Sets the pretty print flag, meaning that the parser will encode resources with human-readable spacing and newlines between elements instead of condensing output as much as possible. | false | Boolean
-| *camel.dataformat.fhirxml.server-base-url* | Sets the server's base URL used by this parser. If a value is set, resource references will be turned into relative references if they are provided as absolute URLs but have a base matching the given base. | | String
-| *camel.dataformat.fhirxml.strip-versions-from-references* | If set to true (which is the default), resource references containing a version will have the version removed when the resource is encoded. This is generally good behaviour because in most situations, references from one resource to another should be to the resource by ID, not by ID and version. In some cases though, it may be desirable to preserve the version in resource links. In that case, this value should be set to false. [...]
-| *camel.dataformat.fhirxml.summary-mode* | If set to true (default is false) only elements marked by the FHIR specification as being summary elements will be included. | false | Boolean
-| *camel.dataformat.fhirxml.suppress-narratives* | If set to true (default is false), narratives will not be included in the encoded values. | false | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-file-starter/src/main/docs/file-starter.adoc b/components-starter/camel-file-starter/src/main/docs/file-starter.adoc
deleted file mode 100644
index 6e99ac0..0000000
--- a/components-starter/camel-file-starter/src/main/docs/file-starter.adoc
+++ /dev/null
@@ -1,39 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for file
-
-== Spring Boot Auto-Configuration
-
-When using file with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-file-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 11 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.file.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.file.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.file.cluster.service.acquire-lock-delay* | The time to wait before starting to try to acquire lock. | | String
-| *camel.component.file.cluster.service.acquire-lock-interval* | The time to wait between attempts to try to acquire lock. | | String
-| *camel.component.file.cluster.service.attributes* | Custom service attributes. | | Map
-| *camel.component.file.cluster.service.enabled* | Sets if the file cluster service should be enabled or not, default is false. | false | Boolean
-| *camel.component.file.cluster.service.id* | Cluster Service ID | | String
-| *camel.component.file.cluster.service.order* | Service lookup order/priority. | | Integer
-| *camel.component.file.cluster.service.root* | The root path. | | String
-| *camel.component.file.enabled* | Whether to enable auto configuration of the file component. This is enabled by default. | | Boolean
-| *camel.component.file.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-file-watch-starter/src/main/docs/file-watch-starter.adoc b/components-starter/camel-file-watch-starter/src/main/docs/file-watch-starter.adoc
deleted file mode 100644
index 69163ba..0000000
--- a/components-starter/camel-file-watch-starter/src/main/docs/file-watch-starter.adoc
+++ /dev/null
@@ -1,36 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for file-watch
-
-== Spring Boot Auto-Configuration
-
-When using file-watch with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-file-watch-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 8 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.file-watch.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.file-watch.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.file-watch.concurrent-consumers* | The number of concurrent consumers. Increase this value, if your route is slow to prevent buffering in queue. | 1 | Integer
-| *camel.component.file-watch.enabled* | Whether to enable auto configuration of the file-watch component. This is enabled by default. | | Boolean
-| *camel.component.file-watch.file-hasher* | Reference to io.methvin.watcher.hashing.FileHasher. This prevents emitting duplicate events on some platforms. For working with large files and if you dont need detect multiple modifications per second per file, use #lastModifiedTimeFileHasher. You can also provide custom implementation in registry. The option is a io.methvin.watcher.hashing.FileHasher type. | | FileHasher
-| *camel.component.file-watch.poll-threads* | The number of threads polling WatchService. Increase this value, if you see OVERFLOW messages in log. | 1 | Integer
-| *camel.component.file-watch.queue-size* | Maximum size of queue between WatchService and consumer. Unbounded by default. | 2147483647 | Integer
-| *camel.component.file-watch.use-file-hashing* | Enables or disables file hashing to detect duplicate events. If you disable this, you can get some events multiple times on some platforms and JDKs. Check java.nio.file.WatchService limitations for your target platform. | true | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-flatpack-starter/src/main/docs/flatpack-starter.adoc b/components-starter/camel-flatpack-starter/src/main/docs/flatpack-starter.adoc
deleted file mode 100644
index ad554e3..0000000
--- a/components-starter/camel-flatpack-starter/src/main/docs/flatpack-starter.adoc
+++ /dev/null
@@ -1,41 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for flatpack
-
-== Spring Boot Auto-Configuration
-
-When using flatpack with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-flatpack-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 13 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.flatpack.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.flatpack.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.flatpack.enabled* | Whether to enable auto configuration of the flatpack component. This is enabled by default. | | Boolean
-| *camel.component.flatpack.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed t [...]
-| *camel.dataformat.flatpack.allow-short-lines* | Allows for lines to be shorter than expected and ignores the extra characters | false | Boolean
-| *camel.dataformat.flatpack.definition* | The flatpack pzmap configuration file. Can be omitted in simpler situations, but its preferred to use the pzmap. | | String
-| *camel.dataformat.flatpack.delimiter* | The delimiter char (could be ; , or similar) | , | String
-| *camel.dataformat.flatpack.enabled* | Whether to enable auto configuration of the flatpack data format. This is enabled by default. | | Boolean
-| *camel.dataformat.flatpack.fixed* | Delimited or fixed. Is by default false = delimited | false | Boolean
-| *camel.dataformat.flatpack.ignore-extra-columns* | Allows for lines to be longer than expected and ignores the extra characters. | false | Boolean
-| *camel.dataformat.flatpack.ignore-first-record* | Whether the first line is ignored for delimited files (for the column headers). Is by default true. | true | Boolean
-| *camel.dataformat.flatpack.parser-factory-ref* | References to a custom parser factory to lookup in the registry | | String
-| *camel.dataformat.flatpack.text-qualifier* | If the text is qualified with a character. Uses quote character by default. | | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-flink-starter/src/main/docs/flink-starter.adoc b/components-starter/camel-flink-starter/src/main/docs/flink-starter.adoc
deleted file mode 100644
index 5b609b5..0000000
--- a/components-starter/camel-flink-starter/src/main/docs/flink-starter.adoc
+++ /dev/null
@@ -1,34 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for flink
-
-== Spring Boot Auto-Configuration
-
-When using flink with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-flink-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 6 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.flink.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.flink.data-set-callback* | Function performing action against a DataSet. The option is a org.apache.camel.component.flink.DataSetCallback type. | | DataSetCallback
-| *camel.component.flink.data-stream* | DataStream to compute against. The option is a org.apache.flink.streaming.api.datastream.DataStream type. | | DataStream
-| *camel.component.flink.data-stream-callback* | Function performing action against a DataStream. The option is a org.apache.camel.component.flink.DataStreamCallback type. | | DataStreamCallback
-| *camel.component.flink.enabled* | Whether to enable auto configuration of the flink component. This is enabled by default. | | Boolean
-| *camel.component.flink.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-fop-starter/src/main/docs/fop-starter.adoc b/components-starter/camel-fop-starter/src/main/docs/fop-starter.adoc
deleted file mode 100644
index 25996f0..0000000
--- a/components-starter/camel-fop-starter/src/main/docs/fop-starter.adoc
+++ /dev/null
@@ -1,31 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for fop
-
-== Spring Boot Auto-Configuration
-
-When using fop with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-fop-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 3 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.fop.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.fop.enabled* | Whether to enable auto configuration of the fop component. This is enabled by default. | | Boolean
-| *camel.component.fop.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then c [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-freemarker-starter/src/main/docs/freemarker-starter.adoc b/components-starter/camel-freemarker-starter/src/main/docs/freemarker-starter.adoc
deleted file mode 100644
index 66ff0b7..0000000
--- a/components-starter/camel-freemarker-starter/src/main/docs/freemarker-starter.adoc
+++ /dev/null
@@ -1,34 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for freemarker
-
-== Spring Boot Auto-Configuration
-
-When using freemarker with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-freemarker-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 6 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.freemarker.allow-context-map-all* | Sets whether the context map should allow access to all details. By default only the message body and headers can be accessed. This option can be enabled for full access to the current Exchange and CamelContext. Doing so impose a potential security risk as this opens access to the full power of CamelContext API. | false | Boolean
-| *camel.component.freemarker.allow-template-from-header* | Whether to allow to use resource template from header or not (default false). Enabling this allows to specify dynamic templates via message header. However this can be seen as a potential security vulnerability if the header is coming from a malicious user, so use this with care. | false | Boolean
-| *camel.component.freemarker.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.freemarker.configuration* | To use an existing freemarker.template.Configuration instance as the configuration. The option is a freemarker.template.Configuration type. | | Configuration
-| *camel.component.freemarker.enabled* | Whether to enable auto configuration of the freemarker component. This is enabled by default. | | Boolean
-| *camel.component.freemarker.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-ftp-starter/src/main/docs/ftp-starter.adoc b/components-starter/camel-ftp-starter/src/main/docs/ftp-starter.adoc
deleted file mode 100644
index 51849b7..0000000
--- a/components-starter/camel-ftp-starter/src/main/docs/ftp-starter.adoc
+++ /dev/null
@@ -1,41 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for ftp
-
-== Spring Boot Auto-Configuration
-
-When using ftp with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-ftp-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 13 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.ftp.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.ftp.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.ftp.enabled* | Whether to enable auto configuration of the ftp component. This is enabled by default. | | Boolean
-| *camel.component.ftp.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then c [...]
-| *camel.component.ftps.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.ftps.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.ftps.enabled* | Whether to enable auto configuration of the ftps component. This is enabled by default. | | Boolean
-| *camel.component.ftps.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
-| *camel.component.ftps.use-global-ssl-context-parameters* | Enable usage of global SSL context parameters. | false | Boolean
-| *camel.component.sftp.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.sftp.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.sftp.enabled* | Whether to enable auto configuration of the sftp component. This is enabled by default. | | Boolean
-| *camel.component.sftp.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-ganglia-starter/src/main/docs/ganglia-starter.adoc b/components-starter/camel-ganglia-starter/src/main/docs/ganglia-starter.adoc
deleted file mode 100644
index 6708310..0000000
--- a/components-starter/camel-ganglia-starter/src/main/docs/ganglia-starter.adoc
+++ /dev/null
@@ -1,44 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for ganglia
-
-== Spring Boot Auto-Configuration
-
-When using ganglia with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-ganglia-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 16 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.ganglia.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.ganglia.configuration* | To use the shared configuration. The option is a org.apache.camel.component.ganglia.GangliaConfiguration type. | | GangliaConfiguration
-| *camel.component.ganglia.dmax* | Minumum time in seconds before Ganglia will purge the metric value if it expires. Set to 0 and the value will remain in Ganglia indefinitely until a gmond agent restart. | 0 | Integer
-| *camel.component.ganglia.enabled* | Whether to enable auto configuration of the ganglia component. This is enabled by default. | | Boolean
-| *camel.component.ganglia.group-name* | The group that the metric belongs to. | java | String
-| *camel.component.ganglia.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
-| *camel.component.ganglia.metric-name* | The name to use for the metric. | metric | String
-| *camel.component.ganglia.mode* | Send the UDP metric packets using MULTICAST or UNICAST | | GMetric$UDPAddressingMode
-| *camel.component.ganglia.prefix* | Prefix the metric name with this string and an underscore. | | String
-| *camel.component.ganglia.slope* | The slope | | GMetricSlope
-| *camel.component.ganglia.spoof-hostname* | Spoofing information IP:hostname | | String
-| *camel.component.ganglia.tmax* | Maximum time in seconds that the value can be considered current. After this, Ganglia considers the value to have expired. | 60 | Integer
-| *camel.component.ganglia.ttl* | If using multicast, set the TTL of the packets | 5 | Integer
-| *camel.component.ganglia.type* | The type of value | | GMetricType
-| *camel.component.ganglia.units* | Any unit of measurement that qualifies the metric, e.g. widgets, litres, bytes. Do not include a prefix such as k (kilo) or m (milli), other tools may scale the units later. The value should be unscaled. | | String
-| *camel.component.ganglia.wire-format31x* | Use the wire format of Ganglia 3.1.0 and later versions. Set this to false to use Ganglia 3.0.x or earlier. | true | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-geocoder-starter/src/main/docs/geocoder-starter.adoc b/components-starter/camel-geocoder-starter/src/main/docs/geocoder-starter.adoc
deleted file mode 100644
index f9a2c2b..0000000
--- a/components-starter/camel-geocoder-starter/src/main/docs/geocoder-starter.adoc
+++ /dev/null
@@ -1,32 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for geocoder
-
-== Spring Boot Auto-Configuration
-
-When using geocoder with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-geocoder-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 4 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.geocoder.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.geocoder.enabled* | Whether to enable auto configuration of the geocoder component. This is enabled by default. | | Boolean
-| *camel.component.geocoder.geo-api-context* | Configuration for Google maps API. The option is a com.google.maps.GeoApiContext type. | | GeoApiContext
-| *camel.component.geocoder.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed t [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-git-starter/src/main/docs/git-starter.adoc b/components-starter/camel-git-starter/src/main/docs/git-starter.adoc
deleted file mode 100644
index 2020082..0000000
--- a/components-starter/camel-git-starter/src/main/docs/git-starter.adoc
+++ /dev/null
@@ -1,32 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for git
-
-== Spring Boot Auto-Configuration
-
-When using git with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-git-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 4 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.git.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.git.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.git.enabled* | Whether to enable auto configuration of the git component. This is enabled by default. | | Boolean
-| *camel.component.git.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then c [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-github-starter/src/main/docs/github-starter.adoc b/components-starter/camel-github-starter/src/main/docs/github-starter.adoc
deleted file mode 100644
index ac3aea7..0000000
--- a/components-starter/camel-github-starter/src/main/docs/github-starter.adoc
+++ /dev/null
@@ -1,33 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for github
-
-== Spring Boot Auto-Configuration
-
-When using github with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-github-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 5 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.github.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.github.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.github.enabled* | Whether to enable auto configuration of the github component. This is enabled by default. | | Boolean
-| *camel.component.github.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed the [...]
-| *camel.component.github.oauth-token* | GitHub OAuth token. Must be configured on either component or endpoint. | | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-google-bigquery-starter/src/main/docs/google-bigquery-starter.adoc b/components-starter/camel-google-bigquery-starter/src/main/docs/google-bigquery-starter.adoc
deleted file mode 100644
index 2208adc..0000000
--- a/components-starter/camel-google-bigquery-starter/src/main/docs/google-bigquery-starter.adoc
+++ /dev/null
@@ -1,39 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for google-bigquery
-
-== Spring Boot Auto-Configuration
-
-When using google-bigquery with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-google-bigquery-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 11 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.google-bigquery-sql.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.google-bigquery-sql.connection-factory* | ConnectionFactory to obtain connection to Bigquery Service. If not provided the default one will be used. The option is a org.apache.camel.component.google.bigquery.GoogleBigQueryConnectionFactory type. | | GoogleBigQueryConnectionFactory
-| *camel.component.google-bigquery-sql.enabled* | Whether to enable auto configuration of the google-bigquery-sql component. This is enabled by default. | | Boolean
-| *camel.component.google-bigquery-sql.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is [...]
-| *camel.component.google-bigquery-sql.project-id* | Google Cloud Project Id | | String
-| *camel.component.google-bigquery.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.google-bigquery.connection-factory* | ConnectionFactory to obtain connection to Bigquery Service. If not provided the default one will be used. The option is a org.apache.camel.component.google.bigquery.GoogleBigQueryConnectionFactory type. | | GoogleBigQueryConnectionFactory
-| *camel.component.google-bigquery.dataset-id* | BigQuery Dataset Id | | String
-| *camel.component.google-bigquery.enabled* | Whether to enable auto configuration of the google-bigquery component. This is enabled by default. | | Boolean
-| *camel.component.google-bigquery.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proc [...]
-| *camel.component.google-bigquery.project-id* | Google Cloud Project Id | | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-google-calendar-starter/src/main/docs/google-calendar-starter.adoc b/components-starter/camel-google-calendar-starter/src/main/docs/google-calendar-starter.adoc
deleted file mode 100644
index ecaa937..0000000
--- a/components-starter/camel-google-calendar-starter/src/main/docs/google-calendar-starter.adoc
+++ /dev/null
@@ -1,59 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for google-calendar
-
-== Spring Boot Auto-Configuration
-
-When using google-calendar with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-google-calendar-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 31 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.google-calendar-stream.access-token* | OAuth 2 access token. This typically expires after an hour so refreshToken is recommended for long term usage. | | String
-| *camel.component.google-calendar-stream.application-name* | Google Calendar application name. Example would be camel-google-calendar/1.0 | | String
-| *camel.component.google-calendar-stream.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.google-calendar-stream.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.google-calendar-stream.calendar-id* | The calendarId to be used | primary | String
-| *camel.component.google-calendar-stream.client-factory* | The client Factory. The option is a org.apache.camel.component.google.calendar.GoogleCalendarClientFactory type. | | GoogleCalendarClientFactory
-| *camel.component.google-calendar-stream.client-id* | Client ID of the calendar application | | String
-| *camel.component.google-calendar-stream.client-secret* | Client secret of the calendar application | | String
-| *camel.component.google-calendar-stream.configuration* | The configuration. The option is a org.apache.camel.component.google.calendar.stream.GoogleCalendarStreamConfiguration type. | | GoogleCalendarStreamConfiguration
-| *camel.component.google-calendar-stream.consider-last-update* | Take into account the lastUpdate of the last event polled as start date for the next poll | false | Boolean
-| *camel.component.google-calendar-stream.consume-from-now* | Consume events in the selected calendar from now on | true | Boolean
-| *camel.component.google-calendar-stream.enabled* | Whether to enable auto configuration of the google-calendar-stream component. This is enabled by default. | | Boolean
-| *camel.component.google-calendar-stream.max-results* | Max results to be returned | 10 | Integer
-| *camel.component.google-calendar-stream.query* | The query to execute on calendar | | String
-| *camel.component.google-calendar-stream.refresh-token* | OAuth 2 refresh token. Using this, the Google Calendar component can obtain a new accessToken whenever the current one expires - a necessity if the application is long-lived. | | String
-| *camel.component.google-calendar-stream.scopes* | Specifies the level of permissions you want a calendar application to have to a user account. See \https://developers.google.com/calendar/auth for more info. | | List
-| *camel.component.google-calendar.access-token* | OAuth 2 access token. This typically expires after an hour so refreshToken is recommended for long term usage. | | String
-| *camel.component.google-calendar.application-name* | Google calendar application name. Example would be camel-google-calendar/1.0 | | String
-| *camel.component.google-calendar.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.google-calendar.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.google-calendar.client-factory* | To use the GoogleCalendarClientFactory as factory for creating the client. Will by default use BatchGoogleCalendarClientFactory. The option is a org.apache.camel.component.google.calendar.GoogleCalendarClientFactory type. | | GoogleCalendarClientFactory
-| *camel.component.google-calendar.client-id* | Client ID of the calendar application | | String
-| *camel.component.google-calendar.client-secret* | Client secret of the calendar application | | String
-| *camel.component.google-calendar.configuration* | To use the shared configuration. The option is a org.apache.camel.component.google.calendar.GoogleCalendarConfiguration type. | | GoogleCalendarConfiguration
-| *camel.component.google-calendar.email-address* | The emailAddress of the Google Service Account. | | String
-| *camel.component.google-calendar.enabled* | Whether to enable auto configuration of the google-calendar component. This is enabled by default. | | Boolean
-| *camel.component.google-calendar.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proc [...]
-| *camel.component.google-calendar.p12-file-name* | The name of the p12 file which has the private key to use with the Google Service Account. | | String
-| *camel.component.google-calendar.refresh-token* | OAuth 2 refresh token. Using this, the Google Calendar component can obtain a new accessToken whenever the current one expires - a necessity if the application is long-lived. | | String
-| *camel.component.google-calendar.scopes* | Specifies the level of permissions you want a calendar application to have to a user account. You can separate multiple scopes by comma. See \https://developers.google.com/google-apps/calendar/auth for more info. | https://www.googleapis.com/auth/calendar | String
-| *camel.component.google-calendar.user* | The email address of the user the application is trying to impersonate in the service account flow | | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-google-drive-starter/src/main/docs/google-drive-starter.adoc b/components-starter/camel-google-drive-starter/src/main/docs/google-drive-starter.adoc
deleted file mode 100644
index d20fcbe..0000000
--- a/components-starter/camel-google-drive-starter/src/main/docs/google-drive-starter.adoc
+++ /dev/null
@@ -1,40 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for google-drive
-
-== Spring Boot Auto-Configuration
-
-When using google-drive with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-google-drive-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 12 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.google-drive.access-token* | OAuth 2 access token. This typically expires after an hour so refreshToken is recommended for long term usage. | | String
-| *camel.component.google-drive.application-name* | Google drive application name. Example would be camel-google-drive/1.0 | | String
-| *camel.component.google-drive.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.google-drive.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.google-drive.client-factory* | To use the GoogleCalendarClientFactory as factory for creating the client. Will by default use BatchGoogleDriveClientFactory. The option is a org.apache.camel.component.google.drive.GoogleDriveClientFactory type. | | GoogleDriveClientFactory
-| *camel.component.google-drive.client-id* | Client ID of the drive application | | String
-| *camel.component.google-drive.client-secret* | Client secret of the drive application | | String
-| *camel.component.google-drive.configuration* | To use the shared configuration. The option is a org.apache.camel.component.google.drive.GoogleDriveConfiguration type. | | GoogleDriveConfiguration
-| *camel.component.google-drive.enabled* | Whether to enable auto configuration of the google-drive component. This is enabled by default. | | Boolean
-| *camel.component.google-drive.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is process [...]
-| *camel.component.google-drive.refresh-token* | OAuth 2 refresh token. Using this, the Google Calendar component can obtain a new accessToken whenever the current one expires - a necessity if the application is long-lived. | | String
-| *camel.component.google-drive.scopes* | Specifies the level of permissions you want a drive application to have to a user account. See \https://developers.google.com/drive/web/scopes for more info. | | List
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-google-mail-starter/src/main/docs/google-mail-starter.adoc b/components-starter/camel-google-mail-starter/src/main/docs/google-mail-starter.adoc
deleted file mode 100644
index 85bce02..0000000
--- a/components-starter/camel-google-mail-starter/src/main/docs/google-mail-starter.adoc
+++ /dev/null
@@ -1,53 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for google-mail
-
-== Spring Boot Auto-Configuration
-
-When using google-mail with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-google-mail-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 25 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.google-mail-stream.access-token* | OAuth 2 access token. This typically expires after an hour so refreshToken is recommended for long term usage. | | String
-| *camel.component.google-mail-stream.application-name* | Google mail application name. Example would be camel-google-mail/1.0 | | String
-| *camel.component.google-mail-stream.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.google-mail-stream.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.google-mail-stream.client-factory* | The client Factory. The option is a org.apache.camel.component.google.mail.GoogleMailClientFactory type. | | GoogleMailClientFactory
-| *camel.component.google-mail-stream.client-id* | Client ID of the mail application | | String
-| *camel.component.google-mail-stream.client-secret* | Client secret of the mail application | | String
-| *camel.component.google-mail-stream.configuration* | The configuration. The option is a org.apache.camel.component.google.mail.stream.GoogleMailStreamConfiguration type. | | GoogleMailStreamConfiguration
-| *camel.component.google-mail-stream.enabled* | Whether to enable auto configuration of the google-mail-stream component. This is enabled by default. | | Boolean
-| *camel.component.google-mail-stream.labels* | Comma separated list of labels to take into account | | String
-| *camel.component.google-mail-stream.mark-as-read* | Mark the message as read once it has been consumed | false | Boolean
-| *camel.component.google-mail-stream.max-results* | Max results to be returned | 10 | Long
-| *camel.component.google-mail-stream.query* | The query to execute on gmail box | is:unread | String
-| *camel.component.google-mail-stream.refresh-token* | OAuth 2 refresh token. Using this, the Google Calendar component can obtain a new accessToken whenever the current one expires - a necessity if the application is long-lived. | | String
-| *camel.component.google-mail.access-token* | OAuth 2 access token. This typically expires after an hour so refreshToken is recommended for long term usage. | | String
-| *camel.component.google-mail.application-name* | Google mail application name. Example would be camel-google-mail/1.0 | | String
-| *camel.component.google-mail.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.google-mail.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.google-mail.client-factory* | To use the GoogleCalendarClientFactory as factory for creating the client. Will by default use BatchGoogleMailClientFactory. The option is a org.apache.camel.component.google.mail.GoogleMailClientFactory type. | | GoogleMailClientFactory
-| *camel.component.google-mail.client-id* | Client ID of the mail application | | String
-| *camel.component.google-mail.client-secret* | Client secret of the mail application | | String
-| *camel.component.google-mail.configuration* | To use the shared configuration. The option is a org.apache.camel.component.google.mail.GoogleMailConfiguration type. | | GoogleMailConfiguration
-| *camel.component.google-mail.enabled* | Whether to enable auto configuration of the google-mail component. This is enabled by default. | | Boolean
-| *camel.component.google-mail.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processe [...]
-| *camel.component.google-mail.refresh-token* | OAuth 2 refresh token. Using this, the Google Calendar component can obtain a new accessToken whenever the current one expires - a necessity if the application is long-lived. | | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-google-pubsub-starter/src/main/docs/google-pubsub-starter.adoc b/components-starter/camel-google-pubsub-starter/src/main/docs/google-pubsub-starter.adoc
deleted file mode 100644
index 1cb4775..0000000
--- a/components-starter/camel-google-pubsub-starter/src/main/docs/google-pubsub-starter.adoc
+++ /dev/null
@@ -1,36 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for google-pubsub
-
-== Spring Boot Auto-Configuration
-
-When using google-pubsub with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-google-pubsub-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 8 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.google-pubsub.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.google-pubsub.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.google-pubsub.enabled* | Whether to enable auto configuration of the google-pubsub component. This is enabled by default. | | Boolean
-| *camel.component.google-pubsub.endpoint* | Endpoint to use with local Pub/Sub emulator. | | String
-| *camel.component.google-pubsub.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proces [...]
-| *camel.component.google-pubsub.publisher-cache-size* | Maximum number of producers to cache. This could be increased if you have producers for lots of different topics. | | Integer
-| *camel.component.google-pubsub.publisher-cache-timeout* | How many milliseconds should each producer stay alive in the cache. | | Integer
-| *camel.component.google-pubsub.publisher-termination-timeout* | How many milliseconds should a producer be allowed to terminate. | | Integer
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-google-sheets-starter/src/main/docs/google-sheets-starter.adoc b/components-starter/camel-google-sheets-starter/src/main/docs/google-sheets-starter.adoc
deleted file mode 100644
index dcdb595..0000000
--- a/components-starter/camel-google-sheets-starter/src/main/docs/google-sheets-starter.adoc
+++ /dev/null
@@ -1,58 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for google-sheets
-
-== Spring Boot Auto-Configuration
-
-When using google-sheets with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-google-sheets-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 30 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.google-sheets-stream.access-token* | OAuth 2 access token. This typically expires after an hour so refreshToken is recommended for long term usage. | | String
-| *camel.component.google-sheets-stream.application-name* | Google sheets application name. Example would be camel-google-sheets/1.0 | | String
-| *camel.component.google-sheets-stream.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.google-sheets-stream.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.google-sheets-stream.client-factory* | To use the GoogleSheetsClientFactory as factory for creating the client. Will by default use BatchGoogleSheetsClientFactory. The option is a org.apache.camel.component.google.sheets.GoogleSheetsClientFactory type. | | GoogleSheetsClientFactory
-| *camel.component.google-sheets-stream.client-id* | Client ID of the sheets application | | String
-| *camel.component.google-sheets-stream.client-secret* | Client secret of the sheets application | | String
-| *camel.component.google-sheets-stream.configuration* | To use the shared configuration. The option is a org.apache.camel.component.google.sheets.stream.GoogleSheetsStreamConfiguration type. | | GoogleSheetsStreamConfiguration
-| *camel.component.google-sheets-stream.enabled* | Whether to enable auto configuration of the google-sheets-stream component. This is enabled by default. | | Boolean
-| *camel.component.google-sheets-stream.include-grid-data* | True if grid data should be returned. | false | Boolean
-| *camel.component.google-sheets-stream.major-dimension* | Specifies the major dimension that results should use.. | ROWS | String
-| *camel.component.google-sheets-stream.max-results* | Specify the maximum number of returned results. This will limit the number of rows in a returned value range data set or the number of returned value ranges in a batch request. | | Integer
-| *camel.component.google-sheets-stream.range* | Specifies the range of rows and columns in a sheet to get data from. | | String
-| *camel.component.google-sheets-stream.refresh-token* | OAuth 2 refresh token. Using this, the Google Calendar component can obtain a new accessToken whenever the current one expires - a necessity if the application is long-lived. | | String
-| *camel.component.google-sheets-stream.scopes* | Specifies the level of permissions you want a sheets application to have to a user account. See \https://developers.google.com/identity/protocols/googlescopes for more info. | | List
-| *camel.component.google-sheets-stream.split-results* | True if value range result should be split into rows or columns to process each of them individually. When true each row or column is represented with a separate exchange in batch processing. Otherwise value range object is used as exchange junk size. | false | Boolean
-| *camel.component.google-sheets-stream.spreadsheet-id* | Specifies the spreadsheet identifier that is used to identify the target to obtain. | | String
-| *camel.component.google-sheets-stream.value-render-option* | Determines how values should be rendered in the output. | FORMATTED_VALUE | String
-| *camel.component.google-sheets.access-token* | OAuth 2 access token. This typically expires after an hour so refreshToken is recommended for long term usage. | | String
-| *camel.component.google-sheets.application-name* | Google Sheets application name. Example would be camel-google-sheets/1.0 | | String
-| *camel.component.google-sheets.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.google-sheets.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.google-sheets.client-factory* | To use the GoogleSheetsClientFactory as factory for creating the client. Will by default use BatchGoogleSheetsClientFactory. The option is a org.apache.camel.component.google.sheets.GoogleSheetsClientFactory type. | | GoogleSheetsClientFactory
-| *camel.component.google-sheets.client-id* | Client ID of the sheets application | | String
-| *camel.component.google-sheets.client-secret* | Client secret of the sheets application | | String
-| *camel.component.google-sheets.configuration* | To use the shared configuration. The option is a org.apache.camel.component.google.sheets.GoogleSheetsConfiguration type. | | GoogleSheetsConfiguration
-| *camel.component.google-sheets.enabled* | Whether to enable auto configuration of the google-sheets component. This is enabled by default. | | Boolean
-| *camel.component.google-sheets.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proces [...]
-| *camel.component.google-sheets.refresh-token* | OAuth 2 refresh token. Using this, the Google Sheets component can obtain a new accessToken whenever the current one expires - a necessity if the application is long-lived. | | String
-| *camel.component.google-sheets.split-result* | When consumer return an array or collection this will generate one exchange per element, and their routes will be executed once for each exchange. Set this value to false to use a single exchange for the entire list or array. | true | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-gora-starter/src/main/docs/gora-starter.adoc b/components-starter/camel-gora-starter/src/main/docs/gora-starter.adoc
deleted file mode 100644
index 87c9474..0000000
--- a/components-starter/camel-gora-starter/src/main/docs/gora-starter.adoc
+++ /dev/null
@@ -1,32 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for gora
-
-== Spring Boot Auto-Configuration
-
-When using gora with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-gora-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 4 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.gora.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.gora.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.gora.enabled* | Whether to enable auto configuration of the gora component. This is enabled by default. | | Boolean
-| *camel.component.gora.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-grape-starter/src/main/docs/grape-starter.adoc b/components-starter/camel-grape-starter/src/main/docs/grape-starter.adoc
deleted file mode 100644
index 10f37b1..0000000
--- a/components-starter/camel-grape-starter/src/main/docs/grape-starter.adoc
+++ /dev/null
@@ -1,32 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for grape
-
-== Spring Boot Auto-Configuration
-
-When using grape with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-grape-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 4 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.grape.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.grape.enabled* | Whether to enable auto configuration of the grape component. This is enabled by default. | | Boolean
-| *camel.component.grape.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
-| *camel.component.grape.patches-repository* | Implementation of org.apache.camel.component.grape.PatchesRepository, by default: FilePatchesRepository. The option is a org.apache.camel.component.grape.PatchesRepository type. | | PatchesRepository
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-graphql-starter/src/main/docs/graphql-starter.adoc b/components-starter/camel-graphql-starter/src/main/docs/graphql-starter.adoc
deleted file mode 100644
index 57dc7bb..0000000
--- a/components-starter/camel-graphql-starter/src/main/docs/graphql-starter.adoc
+++ /dev/null
@@ -1,31 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for graphql
-
-== Spring Boot Auto-Configuration
-
-When using graphql with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-graphql-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 3 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.graphql.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.graphql.enabled* | Whether to enable auto configuration of the graphql component. This is enabled by default. | | Boolean
-| *camel.component.graphql.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-grok-starter/src/main/docs/grok-starter.adoc b/components-starter/camel-grok-starter/src/main/docs/grok-starter.adoc
deleted file mode 100644
index 19f2322..0000000
--- a/components-starter/camel-grok-starter/src/main/docs/grok-starter.adoc
+++ /dev/null
@@ -1,33 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for grok
-
-== Spring Boot Auto-Configuration
-
-When using grok with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-grok-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 5 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.dataformat.grok.allow-multiple-matches-per-line* | If false, every line of input is matched for pattern only once. Otherwise the line can be scanned multiple times when non-terminal pattern is used. | true | Boolean
-| *camel.dataformat.grok.enabled* | Whether to enable auto configuration of the grok data format. This is enabled by default. | | Boolean
-| *camel.dataformat.grok.flattened* | Turns on flattened mode. In flattened mode the exception is thrown when there are multiple pattern matches with same key. | false | Boolean
-| *camel.dataformat.grok.named-only* | Whether to capture named expressions only or not (i.e. %{IP:ip} but not $\{IP}) | false | Boolean
-| *camel.dataformat.grok.pattern* | The grok pattern to match lines of input | | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-groovy-starter/src/main/docs/groovy-starter.adoc b/components-starter/camel-groovy-starter/src/main/docs/groovy-starter.adoc
deleted file mode 100644
index 1d0c33f..0000000
--- a/components-starter/camel-groovy-starter/src/main/docs/groovy-starter.adoc
+++ /dev/null
@@ -1,31 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for groovy
-
-== Spring Boot Auto-Configuration
-
-When using groovy with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-groovy-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 2 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.language.groovy.enabled* | Whether to enable auto configuration of the groovy language. This is enabled by default. | | Boolean
-| *camel.language.groovy.trim* | Whether to trim the value to remove leading and trailing whitespaces and line breaks | true | Boolean
-|===
-
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-grpc-starter/src/main/docs/grpc-starter.adoc b/components-starter/camel-grpc-starter/src/main/docs/grpc-starter.adoc
deleted file mode 100644
index 5ab074f..0000000
--- a/components-starter/camel-grpc-starter/src/main/docs/grpc-starter.adoc
+++ /dev/null
@@ -1,32 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for grpc
-
-== Spring Boot Auto-Configuration
-
-When using grpc with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-grpc-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 4 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.grpc.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.grpc.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.grpc.enabled* | Whether to enable auto configuration of the grpc component. This is enabled by default. | | Boolean
-| *camel.component.grpc.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-gson-starter/src/main/docs/gson-starter.adoc b/components-starter/camel-gson-starter/src/main/docs/gson-starter.adoc
deleted file mode 100644
index f855844..0000000
--- a/components-starter/camel-gson-starter/src/main/docs/gson-starter.adoc
+++ /dev/null
@@ -1,32 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for gson
-
-== Spring Boot Auto-Configuration
-
-When using gson with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-gson-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 4 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.dataformat.json-gson.content-type-header* | Whether the data format should set the Content-Type header with the type from the data format. For example application/xml for data formats marshalling to XML, or application/json for data formats marshalling to JSON | true | Boolean
-| *camel.dataformat.json-gson.enabled* | Whether to enable auto configuration of the json-gson data format. This is enabled by default. | | Boolean
-| *camel.dataformat.json-gson.pretty-print* | To enable pretty printing output nicely formatted. Is by default false. | false | Boolean
-| *camel.dataformat.json-gson.unmarshal-type-name* | Class name of the java type to use when unmarshalling | | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-guava-eventbus-starter/src/main/docs/guava-eventbus-starter.adoc b/components-starter/camel-guava-eventbus-starter/src/main/docs/guava-eventbus-starter.adoc
deleted file mode 100644
index 98a9696..0000000
--- a/components-starter/camel-guava-eventbus-starter/src/main/docs/guava-eventbus-starter.adoc
+++ /dev/null
@@ -1,34 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for guava-eventbus
-
-== Spring Boot Auto-Configuration
-
-When using guava-eventbus with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-guava-eventbus-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 6 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.guava-eventbus.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.guava-eventbus.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.guava-eventbus.enabled* | Whether to enable auto configuration of the guava-eventbus component. This is enabled by default. | | Boolean
-| *camel.component.guava-eventbus.event-bus* | To use the given Guava EventBus instance. The option is a com.google.common.eventbus.EventBus type. | | EventBus
-| *camel.component.guava-eventbus.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proce [...]
-| *camel.component.guava-eventbus.listener-interface* | The interface with method(s) marked with the Subscribe annotation. Dynamic proxy will be created over the interface so it could be registered as the EventBus listener. Particularly useful when creating multi-event listeners and for handling DeadEvent properly. This option cannot be used together with eventClass option. | | Class
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-hazelcast-starter/src/main/docs/hazelcast-starter.adoc b/components-starter/camel-hazelcast-starter/src/main/docs/hazelcast-starter.adoc
deleted file mode 100644
index 46c801c..0000000
--- a/components-starter/camel-hazelcast-starter/src/main/docs/hazelcast-starter.adoc
+++ /dev/null
@@ -1,113 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for hazelcast
-
-== Spring Boot Auto-Configuration
-
-When using hazelcast with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-hazelcast-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 85 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.hazelcast-atomicvalue.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.hazelcast-atomicvalue.customizer.hazelcast-instance.enabled* | Enable or disable the cache-manager customizer. | true | Boolean
-| *camel.component.hazelcast-atomicvalue.customizer.hazelcast-instance.override* | Configure if the cache manager eventually set on the component should be overridden by the customizer. | false | Boolean
-| *camel.component.hazelcast-atomicvalue.enabled* | Whether to enable auto configuration of the hazelcast-atomicvalue component. This is enabled by default. | | Boolean
-| *camel.component.hazelcast-atomicvalue.hazelcast-instance* | The hazelcast instance reference which can be used for hazelcast endpoint. If you don't specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. The option is a com.hazelcast.core.HazelcastInstance type. | | HazelcastInstance
-| *camel.component.hazelcast-atomicvalue.hazelcast-mode* | The hazelcast mode reference which kind of instance should be used. If you don't specify the mode, then the node mode will be the default. | node | String
-| *camel.component.hazelcast-atomicvalue.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message i [...]
-| *camel.component.hazelcast-instance.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.hazelcast-instance.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.hazelcast-instance.enabled* | Whether to enable auto configuration of the hazelcast-instance component. This is enabled by default. | | Boolean
-| *camel.component.hazelcast-instance.hazelcast-instance* | The hazelcast instance reference which can be used for hazelcast endpoint. If you don't specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. The option is a com.hazelcast.core.HazelcastInstance type. | | HazelcastInstance
-| *camel.component.hazelcast-instance.hazelcast-mode* | The hazelcast mode reference which kind of instance should be used. If you don't specify the mode, then the node mode will be the default. | node | String
-| *camel.component.hazelcast-list.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.hazelcast-list.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.hazelcast-list.customizer.hazelcast-instance.enabled* | Enable or disable the cache-manager customizer. | true | Boolean
-| *camel.component.hazelcast-list.customizer.hazelcast-instance.override* | Configure if the cache manager eventually set on the component should be overridden by the customizer. | false | Boolean
-| *camel.component.hazelcast-list.enabled* | Whether to enable auto configuration of the hazelcast-list component. This is enabled by default. | | Boolean
-| *camel.component.hazelcast-list.hazelcast-instance* | The hazelcast instance reference which can be used for hazelcast endpoint. If you don't specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. The option is a com.hazelcast.core.HazelcastInstance type. | | HazelcastInstance
-| *camel.component.hazelcast-list.hazelcast-mode* | The hazelcast mode reference which kind of instance should be used. If you don't specify the mode, then the node mode will be the default. | node | String
-| *camel.component.hazelcast-list.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proce [...]
-| *camel.component.hazelcast-map.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.hazelcast-map.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.hazelcast-map.customizer.hazelcast-instance.enabled* | Enable or disable the cache-manager customizer. | true | Boolean
-| *camel.component.hazelcast-map.customizer.hazelcast-instance.override* | Configure if the cache manager eventually set on the component should be overridden by the customizer. | false | Boolean
-| *camel.component.hazelcast-map.enabled* | Whether to enable auto configuration of the hazelcast-map component. This is enabled by default. | | Boolean
-| *camel.component.hazelcast-map.hazelcast-instance* | The hazelcast instance reference which can be used for hazelcast endpoint. If you don't specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. The option is a com.hazelcast.core.HazelcastInstance type. | | HazelcastInstance
-| *camel.component.hazelcast-map.hazelcast-mode* | The hazelcast mode reference which kind of instance should be used. If you don't specify the mode, then the node mode will be the default. | node | String
-| *camel.component.hazelcast-map.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proces [...]
-| *camel.component.hazelcast-multimap.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.hazelcast-multimap.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.hazelcast-multimap.customizer.hazelcast-instance.enabled* | Enable or disable the cache-manager customizer. | true | Boolean
-| *camel.component.hazelcast-multimap.customizer.hazelcast-instance.override* | Configure if the cache manager eventually set on the component should be overridden by the customizer. | false | Boolean
-| *camel.component.hazelcast-multimap.enabled* | Whether to enable auto configuration of the hazelcast-multimap component. This is enabled by default. | | Boolean
-| *camel.component.hazelcast-multimap.hazelcast-instance* | The hazelcast instance reference which can be used for hazelcast endpoint. If you don't specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. The option is a com.hazelcast.core.HazelcastInstance type. | | HazelcastInstance
-| *camel.component.hazelcast-multimap.hazelcast-mode* | The hazelcast mode reference which kind of instance should be used. If you don't specify the mode, then the node mode will be the default. | node | String
-| *camel.component.hazelcast-multimap.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is p [...]
-| *camel.component.hazelcast-queue.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.hazelcast-queue.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.hazelcast-queue.customizer.hazelcast-instance.enabled* | Enable or disable the cache-manager customizer. | true | Boolean
-| *camel.component.hazelcast-queue.customizer.hazelcast-instance.override* | Configure if the cache manager eventually set on the component should be overridden by the customizer. | false | Boolean
-| *camel.component.hazelcast-queue.enabled* | Whether to enable auto configuration of the hazelcast-queue component. This is enabled by default. | | Boolean
-| *camel.component.hazelcast-queue.hazelcast-instance* | The hazelcast instance reference which can be used for hazelcast endpoint. If you don't specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. The option is a com.hazelcast.core.HazelcastInstance type. | | HazelcastInstance
-| *camel.component.hazelcast-queue.hazelcast-mode* | The hazelcast mode reference which kind of instance should be used. If you don't specify the mode, then the node mode will be the default. | node | String
-| *camel.component.hazelcast-queue.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proc [...]
-| *camel.component.hazelcast-replicatedmap.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.hazelcast-replicatedmap.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.hazelcast-replicatedmap.customizer.hazelcast-instance.enabled* | Enable or disable the cache-manager customizer. | true | Boolean
-| *camel.component.hazelcast-replicatedmap.customizer.hazelcast-instance.override* | Configure if the cache manager eventually set on the component should be overridden by the customizer. | false | Boolean
-| *camel.component.hazelcast-replicatedmap.enabled* | Whether to enable auto configuration of the hazelcast-replicatedmap component. This is enabled by default. | | Boolean
-| *camel.component.hazelcast-replicatedmap.hazelcast-instance* | The hazelcast instance reference which can be used for hazelcast endpoint. If you don't specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. The option is a com.hazelcast.core.HazelcastInstance type. | | HazelcastInstance
-| *camel.component.hazelcast-replicatedmap.hazelcast-mode* | The hazelcast mode reference which kind of instance should be used. If you don't specify the mode, then the node mode will be the default. | node | String
-| *camel.component.hazelcast-replicatedmap.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message [...]
-| *camel.component.hazelcast-ringbuffer.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.hazelcast-ringbuffer.customizer.hazelcast-instance.enabled* | Enable or disable the cache-manager customizer. | true | Boolean
-| *camel.component.hazelcast-ringbuffer.customizer.hazelcast-instance.override* | Configure if the cache manager eventually set on the component should be overridden by the customizer. | false | Boolean
-| *camel.component.hazelcast-ringbuffer.enabled* | Whether to enable auto configuration of the hazelcast-ringbuffer component. This is enabled by default. | | Boolean
-| *camel.component.hazelcast-ringbuffer.hazelcast-instance* | The hazelcast instance reference which can be used for hazelcast endpoint. If you don't specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. The option is a com.hazelcast.core.HazelcastInstance type. | | HazelcastInstance
-| *camel.component.hazelcast-ringbuffer.hazelcast-mode* | The hazelcast mode reference which kind of instance should be used. If you don't specify the mode, then the node mode will be the default. | node | String
-| *camel.component.hazelcast-ringbuffer.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is [...]
-| *camel.component.hazelcast-seda.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.hazelcast-seda.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.hazelcast-seda.customizer.hazelcast-instance.enabled* | Enable or disable the cache-manager customizer. | true | Boolean
-| *camel.component.hazelcast-seda.customizer.hazelcast-instance.override* | Configure if the cache manager eventually set on the component should be overridden by the customizer. | false | Boolean
-| *camel.component.hazelcast-seda.enabled* | Whether to enable auto configuration of the hazelcast-seda component. This is enabled by default. | | Boolean
-| *camel.component.hazelcast-seda.hazelcast-instance* | The hazelcast instance reference which can be used for hazelcast endpoint. If you don't specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. The option is a com.hazelcast.core.HazelcastInstance type. | | HazelcastInstance
-| *camel.component.hazelcast-seda.hazelcast-mode* | The hazelcast mode reference which kind of instance should be used. If you don't specify the mode, then the node mode will be the default. | node | String
-| *camel.component.hazelcast-seda.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proce [...]
-| *camel.component.hazelcast-set.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.hazelcast-set.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.hazelcast-set.customizer.hazelcast-instance.enabled* | Enable or disable the cache-manager customizer. | true | Boolean
-| *camel.component.hazelcast-set.customizer.hazelcast-instance.override* | Configure if the cache manager eventually set on the component should be overridden by the customizer. | false | Boolean
-| *camel.component.hazelcast-set.enabled* | Whether to enable auto configuration of the hazelcast-set component. This is enabled by default. | | Boolean
-| *camel.component.hazelcast-set.hazelcast-instance* | The hazelcast instance reference which can be used for hazelcast endpoint. If you don't specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. The option is a com.hazelcast.core.HazelcastInstance type. | | HazelcastInstance
-| *camel.component.hazelcast-set.hazelcast-mode* | The hazelcast mode reference which kind of instance should be used. If you don't specify the mode, then the node mode will be the default. | node | String
-| *camel.component.hazelcast-set.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proces [...]
-| *camel.component.hazelcast-topic.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.hazelcast-topic.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.hazelcast-topic.customizer.hazelcast-instance.enabled* | Enable or disable the cache-manager customizer. | true | Boolean
-| *camel.component.hazelcast-topic.customizer.hazelcast-instance.enabled* | Enable or disable the cache-manager customizer. | true | Boolean
-| *camel.component.hazelcast-topic.customizer.hazelcast-instance.override* | Configure if the cache manager eventually set on the component should be overridden by the customizer. | false | Boolean
-| *camel.component.hazelcast-topic.customizer.hazelcast-instance.override* | Configure if the cache manager eventually set on the component should be overridden by the customizer. | false | Boolean
-| *camel.component.hazelcast-topic.enabled* | Whether to enable auto configuration of the hazelcast-topic component. This is enabled by default. | | Boolean
-| *camel.component.hazelcast-topic.hazelcast-instance* | The hazelcast instance reference which can be used for hazelcast endpoint. If you don't specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. The option is a com.hazelcast.core.HazelcastInstance type. | | HazelcastInstance
-| *camel.component.hazelcast-topic.hazelcast-mode* | The hazelcast mode reference which kind of instance should be used. If you don't specify the mode, then the node mode will be the default. | node | String
-| *camel.component.hazelcast-topic.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proc [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-hbase-starter/src/main/docs/hbase-starter.adoc b/components-starter/camel-hbase-starter/src/main/docs/hbase-starter.adoc
deleted file mode 100644
index 453f042..0000000
--- a/components-starter/camel-hbase-starter/src/main/docs/hbase-starter.adoc
+++ /dev/null
@@ -1,34 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for hbase
-
-== Spring Boot Auto-Configuration
-
-When using hbase with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-hbase-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 6 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.hbase.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.hbase.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.hbase.configuration* | To use the shared configuration. The option is a org.apache.hadoop.conf.Configuration type. | | Configuration
-| *camel.component.hbase.enabled* | Whether to enable auto configuration of the hbase component. This is enabled by default. | | Boolean
-| *camel.component.hbase.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
-| *camel.component.hbase.pool-max-size* | Maximum number of references to keep for each table in the HTable pool. The default value is 10. | 10 | Integer
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-hdfs-starter/src/main/docs/hdfs-starter.adoc b/components-starter/camel-hdfs-starter/src/main/docs/hdfs-starter.adoc
deleted file mode 100644
index d7b1dcc..0000000
--- a/components-starter/camel-hdfs-starter/src/main/docs/hdfs-starter.adoc
+++ /dev/null
@@ -1,34 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for hdfs
-
-== Spring Boot Auto-Configuration
-
-When using hdfs with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-hdfs-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 6 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.hdfs.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.hdfs.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.hdfs.enabled* | Whether to enable auto configuration of the hdfs component. This is enabled by default. | | Boolean
-| *camel.component.hdfs.j-a-a-s-configuration* | To use the given configuration for security with JAAS. The option is a javax.security.auth.login.Configuration type. | | Configuration
-| *camel.component.hdfs.kerberos-config-file* | To use kerberos authentication, set the value of the 'java.security.krb5.conf' environment variable to an existing file. If the environment variable is already set, warn if different than the specified parameter | | String
-| *camel.component.hdfs.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-hl7-starter/src/main/docs/hl7-starter.adoc b/components-starter/camel-hl7-starter/src/main/docs/hl7-starter.adoc
deleted file mode 100644
index e84265c..0000000
--- a/components-starter/camel-hl7-starter/src/main/docs/hl7-starter.adoc
+++ /dev/null
@@ -1,32 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for hl7
-
-== Spring Boot Auto-Configuration
-
-When using hl7 with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-hl7-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 4 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.dataformat.hl7.enabled* | Whether to enable auto configuration of the hl7 data format. This is enabled by default. | | Boolean
-| *camel.dataformat.hl7.validate* | Whether to validate the HL7 message Is by default true. | true | Boolean
-| *camel.language.hl7terser.enabled* | Whether to enable auto configuration of the hl7terser language. This is enabled by default. | | Boolean
-| *camel.language.hl7terser.trim* | Whether to trim the value to remove leading and trailing whitespaces and line breaks | true | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-http-starter/src/main/docs/http-starter.adoc b/components-starter/camel-http-starter/src/main/docs/http-starter.adoc
deleted file mode 100644
index c6e341d..0000000
--- a/components-starter/camel-http-starter/src/main/docs/http-starter.adoc
+++ /dev/null
@@ -1,55 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for http
-
-== Spring Boot Auto-Configuration
-
-When using http with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-http-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 27 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.http.allow-java-serialized-object* | Whether to allow java serialization when a request uses context-type=application/x-java-serialized-object. This is by default turned off. If you enable this then be aware that Java will deserialize the incoming data from the request to Java and that can be a potential security risk. | false | Boolean
-| *camel.component.http.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.http.client-connection-manager* | To use a custom and shared HttpClientConnectionManager to manage connections. If this has been configured then this is always used for all endpoints created by this component. The option is a org.apache.http.conn.HttpClientConnectionManager type. | | HttpClientConnectionManager
-| *camel.component.http.connect-timeout* | Determines the timeout in milliseconds until a connection is established. A timeout value of zero is interpreted as an infinite timeout. A timeout value of zero is interpreted as an infinite timeout. A negative value is interpreted as undefined (system default). | -1 | Integer
-| *camel.component.http.connection-request-timeout* | The timeout in milliseconds used when requesting a connection from the connection manager. A timeout value of zero is interpreted as an infinite timeout. A timeout value of zero is interpreted as an infinite timeout. A negative value is interpreted as undefined (system default). | -1 | Integer
-| *camel.component.http.connection-time-to-live* | The time for connection to live, the time unit is millisecond, the default value is always keep alive. | | Long
-| *camel.component.http.connections-per-route* | The maximum number of connections per route. | 20 | Integer
-| *camel.component.http.cookie-store* | To use a custom org.apache.http.client.CookieStore. By default the org.apache.http.impl.client.BasicCookieStore is used which is an in-memory only cookie store. Notice if bridgeEndpoint=true then the cookie store is forced to be a noop cookie store as cookie shouldn't be stored as we are just bridging (eg acting as a proxy). The option is a org.apache.http.client.CookieStore type. | | CookieStore
-| *camel.component.http.enabled* | Whether to enable auto configuration of the http component. This is enabled by default. | | Boolean
-| *camel.component.http.header-filter-strategy* | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. The option is a org.apache.camel.spi.HeaderFilterStrategy type. | | HeaderFilterStrategy
-| *camel.component.http.http-binding* | To use a custom HttpBinding to control the mapping between Camel message and HttpClient. The option is a org.apache.camel.http.common.HttpBinding type. | | HttpBinding
-| *camel.component.http.http-client-configurer* | To use the custom HttpClientConfigurer to perform configuration of the HttpClient that will be used. The option is a org.apache.camel.component.http.HttpClientConfigurer type. | | HttpClientConfigurer
-| *camel.component.http.http-configuration* | To use the shared HttpConfiguration as base configuration. The option is a org.apache.camel.http.common.HttpConfiguration type. | | HttpConfiguration
-| *camel.component.http.http-context* | To use a custom org.apache.http.protocol.HttpContext when executing requests. The option is a org.apache.http.protocol.HttpContext type. | | HttpContext
-| *camel.component.http.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
-| *camel.component.http.max-total-connections* | The maximum number of connections. | 200 | Integer
-| *camel.component.http.proxy-auth-domain* | Proxy authentication domain to use | | String
-| *camel.component.http.proxy-auth-host* | Proxy authentication host | | String
-| *camel.component.http.proxy-auth-method* | Proxy authentication method to use | | String
-| *camel.component.http.proxy-auth-nt-host* | Proxy authentication domain (workstation name) to use with NTML | | String
-| *camel.component.http.proxy-auth-password* | Proxy authentication password | | String
-| *camel.component.http.proxy-auth-port* | Proxy authentication port | | Integer
-| *camel.component.http.proxy-auth-username* | Proxy authentication username | | String
-| *camel.component.http.socket-timeout* | Defines the socket timeout in milliseconds, which is the timeout for waiting for data or, put differently, a maximum period inactivity between two consecutive data packets). A timeout value of zero is interpreted as an infinite timeout. A negative value is interpreted as undefined (system default). | -1 | Integer
-| *camel.component.http.ssl-context-parameters* | To configure security using SSLContextParameters. Important: Only one instance of org.apache.camel.support.jsse.SSLContextParameters is supported per HttpComponent. If you need to use 2 or more different instances, you need to define a new HttpComponent per instance you need. The option is a org.apache.camel.support.jsse.SSLContextParameters type. | | SSLContextParameters
-| *camel.component.http.use-global-ssl-context-parameters* | Enable usage of global SSL context parameters. | false | Boolean
-| *camel.component.http.x509-hostname-verifier* | To use a custom X509HostnameVerifier such as DefaultHostnameVerifier or NoopHostnameVerifier. The option is a javax.net.ssl.HostnameVerifier type. | | HostnameVerifier
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-hystrix-starter/src/main/docs/hystrix-starter.adoc b/components-starter/camel-hystrix-starter/src/main/docs/hystrix-starter.adoc
deleted file mode 100644
index 8c15bc1..0000000
--- a/components-starter/camel-hystrix-starter/src/main/docs/hystrix-starter.adoc
+++ /dev/null
@@ -1,32 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for hystrix
-
-== Spring Boot Auto-Configuration
-
-When using hystrix with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-hystrix-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 3 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.hystrix.mapping.enabled* | Enables the automatic mapping of the hystrics metric servlet into the Spring web context. | true | Boolean
-| *camel.component.hystrix.mapping.path* | Endpoint for hystrix metrics servlet. | /hystrix.stream | String
-| *camel.component.hystrix.mapping.servlet-name* | Name of the Hystrix metrics servlet. | HystrixEventStreamServlet | String
-|===
-
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-ical-starter/src/main/docs/ical-starter.adoc b/components-starter/camel-ical-starter/src/main/docs/ical-starter.adoc
deleted file mode 100644
index f4a8336..0000000
--- a/components-starter/camel-ical-starter/src/main/docs/ical-starter.adoc
+++ /dev/null
@@ -1,30 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for ical
-
-== Spring Boot Auto-Configuration
-
-When using ical with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-ical-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 2 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.dataformat.ical.enabled* | Whether to enable auto configuration of the ical data format. This is enabled by default. | | Boolean
-| *camel.dataformat.ical.validating* | Whether to validate. | false | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-iec60870-starter/src/main/docs/iec60870-starter.adoc b/components-starter/camel-iec60870-starter/src/main/docs/iec60870-starter.adoc
deleted file mode 100644
index 7722909..0000000
--- a/components-starter/camel-iec60870-starter/src/main/docs/iec60870-starter.adoc
+++ /dev/null
@@ -1,38 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for iec60870
-
-== Spring Boot Auto-Configuration
-
-When using iec60870 with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-iec60870-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 10 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.iec60870-client.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.iec60870-client.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.iec60870-client.default-connection-options* | Default connection options. The option is a org.apache.camel.component.iec60870.client.ClientOptions type. | | ClientOptions
-| *camel.component.iec60870-client.enabled* | Whether to enable auto configuration of the iec60870-client component. This is enabled by default. | | Boolean
-| *camel.component.iec60870-client.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proc [...]
-| *camel.component.iec60870-server.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.iec60870-server.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.iec60870-server.default-connection-options* | Default connection options. The option is a org.apache.camel.component.iec60870.server.ServerOptions type. | | ServerOptions
-| *camel.component.iec60870-server.enabled* | Whether to enable auto configuration of the iec60870-server component. This is enabled by default. | | Boolean
-| *camel.component.iec60870-server.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proc [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-ignite-starter/src/main/docs/ignite-starter.adoc b/components-starter/camel-ignite-starter/src/main/docs/ignite-starter.adoc
deleted file mode 100644
index 08e82fd..0000000
--- a/components-starter/camel-ignite-starter/src/main/docs/ignite-starter.adoc
+++ /dev/null
@@ -1,72 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for ignite
-
-== Spring Boot Auto-Configuration
-
-When using ignite with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-ignite-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 44 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.ignite-cache.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.ignite-cache.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.ignite-cache.configuration-resource* | The resource from where to load the configuration. It can be a: URL, String or InputStream type. The option is a java.lang.Object type. | | Object
-| *camel.component.ignite-cache.enabled* | Whether to enable auto configuration of the ignite-cache component. This is enabled by default. | | Boolean
-| *camel.component.ignite-cache.ignite* | To use an existing Ignite instance. The option is a org.apache.ignite.Ignite type. | | Ignite
-| *camel.component.ignite-cache.ignite-configuration* | Allows the user to set a programmatic ignite configuration. The option is a org.apache.ignite.configuration.IgniteConfiguration type. | | IgniteConfiguration
-| *camel.component.ignite-cache.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is process [...]
-| *camel.component.ignite-compute.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.ignite-compute.configuration-resource* | The resource from where to load the configuration. It can be a: URL, String or InputStream type. The option is a java.lang.Object type. | | Object
-| *camel.component.ignite-compute.enabled* | Whether to enable auto configuration of the ignite-compute component. This is enabled by default. | | Boolean
-| *camel.component.ignite-compute.ignite* | To use an existing Ignite instance. The option is a org.apache.ignite.Ignite type. | | Ignite
-| *camel.component.ignite-compute.ignite-configuration* | Allows the user to set a programmatic ignite configuration. The option is a org.apache.ignite.configuration.IgniteConfiguration type. | | IgniteConfiguration
-| *camel.component.ignite-compute.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proce [...]
-| *camel.component.ignite-events.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.ignite-events.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.ignite-events.configuration-resource* | The resource from where to load the configuration. It can be a: URL, String or InputStream type. The option is a java.lang.Object type. | | Object
-| *camel.component.ignite-events.enabled* | Whether to enable auto configuration of the ignite-events component. This is enabled by default. | | Boolean
-| *camel.component.ignite-events.ignite* | To use an existing Ignite instance. The option is a org.apache.ignite.Ignite type. | | Ignite
-| *camel.component.ignite-events.ignite-configuration* | Allows the user to set a programmatic ignite configuration. The option is a org.apache.ignite.configuration.IgniteConfiguration type. | | IgniteConfiguration
-| *camel.component.ignite-idgen.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.ignite-idgen.configuration-resource* | The resource from where to load the configuration. It can be a: URL, String or InputStream type. The option is a java.lang.Object type. | | Object
-| *camel.component.ignite-idgen.enabled* | Whether to enable auto configuration of the ignite-idgen component. This is enabled by default. | | Boolean
-| *camel.component.ignite-idgen.ignite* | To use an existing Ignite instance. The option is a org.apache.ignite.Ignite type. | | Ignite
-| *camel.component.ignite-idgen.ignite-configuration* | Allows the user to set a programmatic ignite configuration. The option is a org.apache.ignite.configuration.IgniteConfiguration type. | | IgniteConfiguration
-| *camel.component.ignite-idgen.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is process [...]
-| *camel.component.ignite-messaging.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.ignite-messaging.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.ignite-messaging.configuration-resource* | The resource from where to load the configuration. It can be a: URL, String or InputStream type. The option is a java.lang.Object type. | | Object
-| *camel.component.ignite-messaging.enabled* | Whether to enable auto configuration of the ignite-messaging component. This is enabled by default. | | Boolean
-| *camel.component.ignite-messaging.ignite* | To use an existing Ignite instance. The option is a org.apache.ignite.Ignite type. | | Ignite
-| *camel.component.ignite-messaging.ignite-configuration* | Allows the user to set a programmatic ignite configuration. The option is a org.apache.ignite.configuration.IgniteConfiguration type. | | IgniteConfiguration
-| *camel.component.ignite-messaging.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is pro [...]
-| *camel.component.ignite-queue.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.ignite-queue.configuration-resource* | The resource from where to load the configuration. It can be a: URL, String or InputStream type. The option is a java.lang.Object type. | | Object
-| *camel.component.ignite-queue.enabled* | Whether to enable auto configuration of the ignite-queue component. This is enabled by default. | | Boolean
-| *camel.component.ignite-queue.ignite* | To use an existing Ignite instance. The option is a org.apache.ignite.Ignite type. | | Ignite
-| *camel.component.ignite-queue.ignite-configuration* | Allows the user to set a programmatic ignite configuration. The option is a org.apache.ignite.configuration.IgniteConfiguration type. | | IgniteConfiguration
-| *camel.component.ignite-queue.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is process [...]
-| *camel.component.ignite-set.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.ignite-set.configuration-resource* | The resource from where to load the configuration. It can be a: URL, String or InputStream type. The option is a java.lang.Object type. | | Object
-| *camel.component.ignite-set.enabled* | Whether to enable auto configuration of the ignite-set component. This is enabled by default. | | Boolean
-| *camel.component.ignite-set.ignite* | To use an existing Ignite instance. The option is a org.apache.ignite.Ignite type. | | Ignite
-| *camel.component.ignite-set.ignite-configuration* | Allows the user to set a programmatic ignite configuration. The option is a org.apache.ignite.configuration.IgniteConfiguration type. | | IgniteConfiguration
-| *camel.component.ignite-set.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-infinispan-starter/src/main/docs/infinispan-starter.adoc b/components-starter/camel-infinispan-starter/src/main/docs/infinispan-starter.adoc
deleted file mode 100644
index a7a049a..0000000
--- a/components-starter/camel-infinispan-starter/src/main/docs/infinispan-starter.adoc
+++ /dev/null
@@ -1,62 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for infinispan
-
-== Spring Boot Auto-Configuration
-
-When using infinispan with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-infinispan-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 34 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.infinispan.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.infinispan.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.infinispan.cache-container* | Specifies the cache Container to connect. The option is a org.infinispan.commons.api.BasicCacheContainer type. | | BasicCacheContainer
-| *camel.component.infinispan.cache-container-configuration* | The CacheContainer configuration. Uses if the cacheContainer is not defined. Must be the following types: org.infinispan.client.hotrod.configuration.Configuration - for remote cache interaction configuration; org.infinispan.configuration.cache.Configuration - for embedded cache interaction configuration;. The option is a java.lang.Object type. | | Object
-| *camel.component.infinispan.clustered-listener* | If true, the listener will be installed for the entire cluster | false | Boolean
-| *camel.component.infinispan.configuration* | Component configuration. The option is a org.apache.camel.component.infinispan.InfinispanConfiguration type. | | InfinispanConfiguration
-| *camel.component.infinispan.configuration-properties* | Implementation specific properties for the CacheManager | | Map
-| *camel.component.infinispan.configuration-uri* | An implementation specific URI for the CacheManager | | String
-| *camel.component.infinispan.custom-listener* | Returns the custom listener in use, if provided. The option is a org.apache.camel.component.infinispan.InfinispanCustomListener type. | | InfinispanCustomListener
-| *camel.component.infinispan.customizer.embedded-cache-manager.enabled* | Enable or disable the cache-manager customizer. | true | Boolean
-| *camel.component.infinispan.customizer.embedded-cache-manager.override* | Configure if the cache manager eventually set on the component should be overridden by the customizer. | false | Boolean
-| *camel.component.infinispan.customizer.remote-cache-manager.enabled* | Enable or disable the cache-manager customizer. | true | Boolean
-| *camel.component.infinispan.customizer.remote-cache-manager.override* | Configure if the cache manager eventually set on the component should be overridden by the customizer. | false | Boolean
-| *camel.component.infinispan.default-value* | Set a specific default value for some producer operations. The option is a java.lang.Object type. | | Object
-| *camel.component.infinispan.enabled* | Whether to enable auto configuration of the infinispan component. This is enabled by default. | | Boolean
-| *camel.component.infinispan.event-types* | Specifies the set of event types to register by the consumer. Multiple event can be separated by comma. The possible event types are: CACHE_ENTRY_ACTIVATED, CACHE_ENTRY_PASSIVATED, CACHE_ENTRY_VISITED, CACHE_ENTRY_LOADED, CACHE_ENTRY_EVICTED, CACHE_ENTRY_CREATED, CACHE_ENTRY_REMOVED, CACHE_ENTRY_MODIFIED, TRANSACTION_COMPLETED, TRANSACTION_REGISTERED, CACHE_ENTRY_INVALIDATED, DATA_REHASHED, TOPOLOGY_CHANGED, PARTITION_STATUS_CHANGED | | String
-| *camel.component.infinispan.flags* | A comma separated list of Flag to be applied by default on each cache invocation, not applicable to remote caches. | | String
-| *camel.component.infinispan.hosts* | Specifies the host of the cache on Infinispan instance | | String
-| *camel.component.infinispan.key* | Set a specific key for producer operations. The option is a java.lang.Object type. | | Object
-| *camel.component.infinispan.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed [...]
-| *camel.component.infinispan.old-value* | Set a specific old value for some producer operations. The option is a java.lang.Object type. | | Object
-| *camel.component.infinispan.operation* | The operation to perform. | | InfinispanOperation
-| *camel.component.infinispan.password* | Define the password to access the infinispan instance | | String
-| *camel.component.infinispan.query-builder* | Specifies the query builder. The option is a org.apache.camel.component.infinispan.InfinispanQueryBuilder type. | | InfinispanQueryBuilder
-| *camel.component.infinispan.remapping-function* | Set a specific remappingFunction to use in a compute operation. The option is a java.util.function.BiFunction type. | | BiFunction
-| *camel.component.infinispan.result-header* | Store the operation result in a header instead of the message body. By default, resultHeader == null and the query result is stored in the message body, any existing content in the message body is discarded. If resultHeader is set, the value is used as the name of the header to store the query result and the original message body is preserved. This value can be overridden by an in message header named: CamelInfinispanOperationResultHeader. T [...]
-| *camel.component.infinispan.sasl-mechanism* | Define the SASL Mechanism to access the infinispan instance | | String
-| *camel.component.infinispan.secure* | Define if we are connecting to a secured Infinispan instance | false | Boolean
-| *camel.component.infinispan.security-realm* | Define the security realm to access the infinispan instance | | String
-| *camel.component.infinispan.security-server-name* | Define the security server name to access the infinispan instance | | String
-| *camel.component.infinispan.sync* | If true, the consumer will receive notifications synchronously | true | Boolean
-| *camel.component.infinispan.username* | Define the username to access the infinispan instance | | String
-| *camel.component.infinispan.value* | Set a specific value for producer operations. The option is a java.lang.Object type. | | Object
-| *camel.component.infinispan.command* | *Deprecated* The operation to perform. | PUT | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-influxdb-starter/src/main/docs/influxdb-starter.adoc b/components-starter/camel-influxdb-starter/src/main/docs/influxdb-starter.adoc
deleted file mode 100644
index c4dce33..0000000
--- a/components-starter/camel-influxdb-starter/src/main/docs/influxdb-starter.adoc
+++ /dev/null
@@ -1,32 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for influxdb
-
-== Spring Boot Auto-Configuration
-
-When using influxdb with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-influxdb-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 4 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.influxdb.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.influxdb.enabled* | Whether to enable auto configuration of the influxdb component. This is enabled by default. | | Boolean
-| *camel.component.influxdb.influx-d-b* | The shared Influx DB to use for all endpoints. The option is a org.influxdb.InfluxDB type. | | InfluxDB
-| *camel.component.influxdb.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed t [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-iota-starter/src/main/docs/iota-starter.adoc b/components-starter/camel-iota-starter/src/main/docs/iota-starter.adoc
deleted file mode 100644
index fbff1f3..0000000
--- a/components-starter/camel-iota-starter/src/main/docs/iota-starter.adoc
+++ /dev/null
@@ -1,31 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for iota
-
-== Spring Boot Auto-Configuration
-
-When using iota with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-iota-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 3 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.iota.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.iota.enabled* | Whether to enable auto configuration of the iota component. This is enabled by default. | | Boolean
-| *camel.component.iota.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-ipfs-starter/src/main/docs/ipfs-starter.adoc b/components-starter/camel-ipfs-starter/src/main/docs/ipfs-starter.adoc
deleted file mode 100644
index b0aeadc..0000000
--- a/components-starter/camel-ipfs-starter/src/main/docs/ipfs-starter.adoc
+++ /dev/null
@@ -1,33 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for ipfs
-
-== Spring Boot Auto-Configuration
-
-When using ipfs with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-ipfs-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 5 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.ipfs.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.ipfs.enabled* | Whether to enable auto configuration of the ipfs component. This is enabled by default. | | Boolean
-| *camel.component.ipfs.ipfs-host* | The ipfs host | 127.0.0.1 | String
-| *camel.component.ipfs.ipfs-port* | The ipfs port | 5001 | Integer
-| *camel.component.ipfs.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-irc-starter/src/main/docs/irc-starter.adoc b/components-starter/camel-irc-starter/src/main/docs/irc-starter.adoc
deleted file mode 100644
index 6bcc598..0000000
--- a/components-starter/camel-irc-starter/src/main/docs/irc-starter.adoc
+++ /dev/null
@@ -1,33 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for irc
-
-== Spring Boot Auto-Configuration
-
-When using irc with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-irc-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 5 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.irc.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.irc.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.irc.enabled* | Whether to enable auto configuration of the irc component. This is enabled by default. | | Boolean
-| *camel.component.irc.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then c [...]
-| *camel.component.irc.use-global-ssl-context-parameters* | Enable usage of global SSL context parameters. | false | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-ironmq-starter/src/main/docs/ironmq-starter.adoc b/components-starter/camel-ironmq-starter/src/main/docs/ironmq-starter.adoc
deleted file mode 100644
index c58f713..0000000
--- a/components-starter/camel-ironmq-starter/src/main/docs/ironmq-starter.adoc
+++ /dev/null
@@ -1,32 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for ironmq
-
-== Spring Boot Auto-Configuration
-
-When using ironmq with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-ironmq-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 4 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.ironmq.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.ironmq.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.ironmq.enabled* | Whether to enable auto configuration of the ironmq component. This is enabled by default. | | Boolean
-| *camel.component.ironmq.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed the [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-jackson-starter/src/main/docs/jackson-starter.adoc b/components-starter/camel-jackson-starter/src/main/docs/jackson-starter.adoc
deleted file mode 100644
index 666c7f7..0000000
--- a/components-starter/camel-jackson-starter/src/main/docs/jackson-starter.adoc
+++ /dev/null
@@ -1,46 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for jackson
-
-== Spring Boot Auto-Configuration
-
-When using jackson with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-jackson-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 18 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.dataformat.json-jackson.allow-jms-type* | Used for JMS users to allow the JMSType header from the JMS spec to specify a FQN classname to use to unmarshal to. | false | Boolean
-| *camel.dataformat.json-jackson.allow-unmarshall-type* | If enabled then Jackson is allowed to attempt to use the CamelJacksonUnmarshalType header during the unmarshalling. This should only be enabled when desired to be used. | false | Boolean
-| *camel.dataformat.json-jackson.auto-discover-object-mapper* | If set to true then Jackson will lookup for an objectMapper into the registry | false | Boolean
-| *camel.dataformat.json-jackson.collection-type-name* | Refers to a custom collection type to lookup in the registry to use. This option should rarely be used, but allows to use different collection types than java.util.Collection based as default. | | String
-| *camel.dataformat.json-jackson.content-type-header* | Whether the data format should set the Content-Type header with the type from the data format. For example application/xml for data formats marshalling to XML, or application/json for data formats marshalling to JSON | true | Boolean
-| *camel.dataformat.json-jackson.disable-features* | Set of features to disable on the Jackson com.fasterxml.jackson.databind.ObjectMapper. The features should be a name that matches a enum from com.fasterxml.jackson.databind.SerializationFeature, com.fasterxml.jackson.databind.DeserializationFeature, or com.fasterxml.jackson.databind.MapperFeature Multiple features can be separated by comma | | String
-| *camel.dataformat.json-jackson.enable-features* | Set of features to enable on the Jackson com.fasterxml.jackson.databind.ObjectMapper. The features should be a name that matches a enum from com.fasterxml.jackson.databind.SerializationFeature, com.fasterxml.jackson.databind.DeserializationFeature, or com.fasterxml.jackson.databind.MapperFeature Multiple features can be separated by comma | | String
-| *camel.dataformat.json-jackson.enabled* | Whether to enable auto configuration of the json-jackson data format. This is enabled by default. | | Boolean
-| *camel.dataformat.json-jackson.include* | If you want to marshal a pojo to JSON, and the pojo has some fields with null values. And you want to skip these null values, you can set this option to NON_NULL | | String
-| *camel.dataformat.json-jackson.json-view* | When marshalling a POJO to JSON you might want to exclude certain fields from the JSON output. With Jackson you can use JSON views to accomplish this. This option is to refer to the class which has JsonView annotations | | Class
-| *camel.dataformat.json-jackson.module-class-names* | To use custom Jackson modules com.fasterxml.jackson.databind.Module specified as a String with FQN class names. Multiple classes can be separated by comma. | | String
-| *camel.dataformat.json-jackson.module-refs* | To use custom Jackson modules referred from the Camel registry. Multiple modules can be separated by comma. | | String
-| *camel.dataformat.json-jackson.object-mapper* | Lookup and use the existing ObjectMapper with the given id when using Jackson. | | String
-| *camel.dataformat.json-jackson.pretty-print* | To enable pretty printing output nicely formatted. Is by default false. | false | Boolean
-| *camel.dataformat.json-jackson.timezone* | If set then Jackson will use the Timezone when marshalling/unmarshalling. This option will have no effect on the others Json DataFormat, like gson, fastjson and xstream. | | String
-| *camel.dataformat.json-jackson.unmarshal-type-name* | Class name of the java type to use when unmarshalling | | String
-| *camel.dataformat.json-jackson.use-default-object-mapper* | Whether to lookup and use default Jackson ObjectMapper from the registry. | true | Boolean
-| *camel.dataformat.json-jackson.use-list* | To unmarshal to a List of Map or a List of Pojo. | false | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-jacksonxml-starter/src/main/docs/jacksonxml-starter.adoc b/components-starter/camel-jacksonxml-starter/src/main/docs/jacksonxml-starter.adoc
deleted file mode 100644
index a6c8c59..0000000
--- a/components-starter/camel-jacksonxml-starter/src/main/docs/jacksonxml-starter.adoc
+++ /dev/null
@@ -1,44 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for jacksonxml
-
-== Spring Boot Auto-Configuration
-
-When using jacksonxml with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-jacksonxml-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 16 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.dataformat.jacksonxml.allow-jms-type* | Used for JMS users to allow the JMSType header from the JMS spec to specify a FQN classname to use to unmarshal to. | false | Boolean
-| *camel.dataformat.jacksonxml.allow-unmarshall-type* | If enabled then Jackson is allowed to attempt to use the CamelJacksonUnmarshalType header during the unmarshalling. This should only be enabled when desired to be used. | false | Boolean
-| *camel.dataformat.jacksonxml.collection-type-name* | Refers to a custom collection type to lookup in the registry to use. This option should rarely be used, but allows to use different collection types than java.util.Collection based as default. | | String
-| *camel.dataformat.jacksonxml.content-type-header* | Whether the data format should set the Content-Type header with the type from the data format. For example application/xml for data formats marshalling to XML, or application/json for data formats marshalling to JSON | true | Boolean
-| *camel.dataformat.jacksonxml.disable-features* | Set of features to disable on the Jackson com.fasterxml.jackson.databind.ObjectMapper. The features should be a name that matches a enum from com.fasterxml.jackson.databind.SerializationFeature, com.fasterxml.jackson.databind.DeserializationFeature, or com.fasterxml.jackson.databind.MapperFeature Multiple features can be separated by comma | | String
-| *camel.dataformat.jacksonxml.enable-features* | Set of features to enable on the Jackson com.fasterxml.jackson.databind.ObjectMapper. The features should be a name that matches a enum from com.fasterxml.jackson.databind.SerializationFeature, com.fasterxml.jackson.databind.DeserializationFeature, or com.fasterxml.jackson.databind.MapperFeature Multiple features can be separated by comma | | String
-| *camel.dataformat.jacksonxml.enable-jaxb-annotation-module* | Whether to enable the JAXB annotations module when using jackson. When enabled then JAXB annotations can be used by Jackson. | false | Boolean
-| *camel.dataformat.jacksonxml.enabled* | Whether to enable auto configuration of the jacksonxml data format. This is enabled by default. | | Boolean
-| *camel.dataformat.jacksonxml.include* | If you want to marshal a pojo to JSON, and the pojo has some fields with null values. And you want to skip these null values, you can set this option to NON_NULL | | String
-| *camel.dataformat.jacksonxml.json-view* | When marshalling a POJO to JSON you might want to exclude certain fields from the JSON output. With Jackson you can use JSON views to accomplish this. This option is to refer to the class which has JsonView annotations | | Class
-| *camel.dataformat.jacksonxml.module-class-names* | To use custom Jackson modules com.fasterxml.jackson.databind.Module specified as a String with FQN class names. Multiple classes can be separated by comma. | | String
-| *camel.dataformat.jacksonxml.module-refs* | To use custom Jackson modules referred from the Camel registry. Multiple modules can be separated by comma. | | String
-| *camel.dataformat.jacksonxml.pretty-print* | To enable pretty printing output nicely formatted. Is by default false. | false | Boolean
-| *camel.dataformat.jacksonxml.unmarshal-type-name* | Class name of the java type to use when unmarshalling | | String
-| *camel.dataformat.jacksonxml.use-list* | To unmarshal to a List of Map or a List of Pojo. | false | Boolean
-| *camel.dataformat.jacksonxml.xml-mapper* | Lookup and use the existing XmlMapper with the given id. | | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-jasypt-starter/src/main/docs/jasypt-starter.adoc b/components-starter/camel-jasypt-starter/src/main/docs/jasypt-starter.adoc
deleted file mode 100644
index 1c33d6a..0000000
--- a/components-starter/camel-jasypt-starter/src/main/docs/jasypt-starter.adoc
+++ /dev/null
@@ -1,34 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for jasypt
-
-== Spring Boot Auto-Configuration
-
-When using jasypt with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-jasypt-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 6 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.jasypt.enabled* | Enable the component | true | Boolean
-| *camel.component.jasypt.algorithm* | The algorithm to be used for decryption. | PBEWithMD5AndDES | String
-| *camel.component.jasypt.iv-generator-class-name* | The initialization vector (IV) generator applied in decryption operations. | org.jasypt.iv.NoIvGenerator if the algorithm does not require an initialization vector, org.jasypt.iv.RandomIvGenerator otherwise | String
-| *camel.component.jasypt.salt-generator-class-name* | The salt generator applied in decryption operations. | org.jasypt.salt.RandomSaltGenerator | String
-| *camel.component.jasypt.password* | The master password used by Jasypt for decrypting the values. This option supports prefixes which influence the master password lookup behaviour: sysenv: means to lookup the OS system environment with the given key. sys: means to lookup a JVM system property. | | String
-| *camel.component.jasypt.provider-name* | The name of the security provider to be used for obtaining the encryption algorithm. | | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-jaxb-starter/src/main/docs/jaxb-starter.adoc b/components-starter/camel-jaxb-starter/src/main/docs/jaxb-starter.adoc
deleted file mode 100644
index d5e3dfa..0000000
--- a/components-starter/camel-jaxb-starter/src/main/docs/jaxb-starter.adoc
+++ /dev/null
@@ -1,48 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for jaxb
-
-== Spring Boot Auto-Configuration
-
-When using jaxb with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-jaxb-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 20 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.dataformat.jaxb.content-type-header* | Whether the data format should set the Content-Type header with the type from the data format. For example application/xml for data formats marshalling to XML, or application/json for data formats marshalling to JSON | true | Boolean
-| *camel.dataformat.jaxb.context-path* | Package name where your JAXB classes are located. | | String
-| *camel.dataformat.jaxb.context-path-is-class-name* | This can be set to true to mark that the contextPath is referring to a classname and not a package name. | false | Boolean
-| *camel.dataformat.jaxb.enabled* | Whether to enable auto configuration of the jaxb data format. This is enabled by default. | | Boolean
-| *camel.dataformat.jaxb.encoding* | To overrule and use a specific encoding | | String
-| *camel.dataformat.jaxb.filter-non-xml-chars* | To ignore non xml characheters and replace them with an empty space. | false | Boolean
-| *camel.dataformat.jaxb.fragment* | To turn on marshalling XML fragment trees. By default JAXB looks for XmlRootElement annotation on given class to operate on whole XML tree. This is useful but not always - sometimes generated code does not have XmlRootElement annotation, sometimes you need unmarshall only part of tree. In that case you can use partial unmarshalling. To enable this behaviours you need set property partClass. Camel will pass this class to JAXB's unmarshaler. | false | Boolean
-| *camel.dataformat.jaxb.ignore-j-a-x-b-element* | Whether to ignore JAXBElement elements - only needed to be set to false in very special use-cases. | false | Boolean
-| *camel.dataformat.jaxb.jaxb-provider-properties* | Refers to a custom java.util.Map to lookup in the registry containing custom JAXB provider properties to be used with the JAXB marshaller. | | String
-| *camel.dataformat.jaxb.must-be-j-a-x-b-element* | Whether marhsalling must be java objects with JAXB annotations. And if not then it fails. This option can be set to false to relax that, such as when the data is already in XML format. | false | Boolean
-| *camel.dataformat.jaxb.namespace-prefix-ref* | When marshalling using JAXB or SOAP then the JAXB implementation will automatic assign namespace prefixes, such as ns2, ns3, ns4 etc. To control this mapping, Camel allows you to refer to a map which contains the desired mapping. | | String
-| *camel.dataformat.jaxb.no-namespace-schema-location* | To define the location of the namespaceless schema | | String
-| *camel.dataformat.jaxb.object-factory* | Whether to allow using ObjectFactory classes to create the POJO classes during marshalling. This only applies to POJO classes that has not been annotated with JAXB and providing jaxb.index descriptor files. | false | Boolean
-| *camel.dataformat.jaxb.part-class* | Name of class used for fragment parsing. See more details at the fragment option. | | String
-| *camel.dataformat.jaxb.part-namespace* | XML namespace to use for fragment parsing. See more details at the fragment option. | | String
-| *camel.dataformat.jaxb.pretty-print* | To enable pretty printing output nicely formatted. Is by default false. | false | Boolean
-| *camel.dataformat.jaxb.schema* | To validate against an existing schema. Your can use the prefix classpath:, file: or http: to specify how the resource should by resolved. You can separate multiple schema files by using the ',' character. | | String
-| *camel.dataformat.jaxb.schema-location* | To define the location of the schema | | String
-| *camel.dataformat.jaxb.schema-severity-level* | Sets the schema severity level to use when validating against a schema. This level determines the minimum severity error that triggers JAXB to stop continue parsing. The default value of 0 (warning) means that any error (warning, error or fatal error) will trigger JAXB to stop. There are the following three levels: 0=warning, 1=error, 2=fatal error. | 0 | Integer
-| *camel.dataformat.jaxb.xml-stream-writer-wrapper* | To use a custom xml stream writer. | | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-jbpm-starter/src/main/docs/jbpm-starter.adoc b/components-starter/camel-jbpm-starter/src/main/docs/jbpm-starter.adoc
deleted file mode 100644
index 01a4d68..0000000
--- a/components-starter/camel-jbpm-starter/src/main/docs/jbpm-starter.adoc
+++ /dev/null
@@ -1,32 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for jbpm
-
-== Spring Boot Auto-Configuration
-
-When using jbpm with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-jbpm-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 4 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.jbpm.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.jbpm.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.jbpm.enabled* | Whether to enable auto configuration of the jbpm component. This is enabled by default. | | Boolean
-| *camel.component.jbpm.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-jcache-starter/src/main/docs/jcache-starter.adoc b/components-starter/camel-jcache-starter/src/main/docs/jcache-starter.adoc
deleted file mode 100644
index 6f57055..0000000
--- a/components-starter/camel-jcache-starter/src/main/docs/jcache-starter.adoc
+++ /dev/null
@@ -1,37 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for jcache
-
-== Spring Boot Auto-Configuration
-
-When using jcache with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-jcache-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 9 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.jcache.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.jcache.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.jcache.cache-configuration* | A Configuration for the Cache. The option is a javax.cache.configuration.Configuration type. | | Configuration
-| *camel.component.jcache.cache-configuration-properties* | Properties to configure jcache | | Map
-| *camel.component.jcache.cache-configuration-properties-ref* | References to an existing Properties or Map to lookup in the registry to use for configuring jcache. | | String
-| *camel.component.jcache.caching-provider* | The fully qualified class name of the javax.cache.spi.CachingProvider | | String
-| *camel.component.jcache.configuration-uri* | An implementation specific URI for the CacheManager | | String
-| *camel.component.jcache.enabled* | Whether to enable auto configuration of the jcache component. This is enabled by default. | | Boolean
-| *camel.component.jcache.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed the [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-jclouds-starter/src/main/docs/jclouds-starter.adoc b/components-starter/camel-jclouds-starter/src/main/docs/jclouds-starter.adoc
deleted file mode 100644
index e3da02f..0000000
--- a/components-starter/camel-jclouds-starter/src/main/docs/jclouds-starter.adoc
+++ /dev/null
@@ -1,34 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for jclouds
-
-== Spring Boot Auto-Configuration
-
-When using jclouds with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-jclouds-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 6 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.jclouds.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.jclouds.blob-stores* | To use the given BlobStore which must be configured when using blobstore. | | List
-| *camel.component.jclouds.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.jclouds.compute-services* | To use the given ComputeService which must be configured when use compute. | | List
-| *camel.component.jclouds.enabled* | Whether to enable auto configuration of the jclouds component. This is enabled by default. | | Boolean
-| *camel.component.jclouds.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-jcr-starter/src/main/docs/jcr-starter.adoc b/components-starter/camel-jcr-starter/src/main/docs/jcr-starter.adoc
deleted file mode 100644
index 0d460da..0000000
--- a/components-starter/camel-jcr-starter/src/main/docs/jcr-starter.adoc
+++ /dev/null
@@ -1,32 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for jcr
-
-== Spring Boot Auto-Configuration
-
-When using jcr with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-jcr-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 4 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.jcr.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.jcr.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.jcr.enabled* | Whether to enable auto configuration of the jcr component. This is enabled by default. | | Boolean
-| *camel.component.jcr.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then c [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-jdbc-starter/src/main/docs/jdbc-starter.adoc b/components-starter/camel-jdbc-starter/src/main/docs/jdbc-starter.adoc
deleted file mode 100644
index 3d7938f..0000000
--- a/components-starter/camel-jdbc-starter/src/main/docs/jdbc-starter.adoc
+++ /dev/null
@@ -1,31 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for jdbc
-
-== Spring Boot Auto-Configuration
-
-When using jdbc with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-jdbc-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 3 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.jdbc.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.jdbc.enabled* | Whether to enable auto configuration of the jdbc component. This is enabled by default. | | Boolean
-| *camel.component.jdbc.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-jetty-starter/src/main/docs/jetty-starter.adoc b/components-starter/camel-jetty-starter/src/main/docs/jetty-starter.adoc
deleted file mode 100644
index a007a67..0000000
--- a/components-starter/camel-jetty-starter/src/main/docs/jetty-starter.adoc
+++ /dev/null
@@ -1,61 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for jetty
-
-== Spring Boot Auto-Configuration
-
-When using jetty with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-jetty-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 33 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.jetty.allow-java-serialized-object* | Whether to allow java serialization when a request uses context-type=application/x-java-serialized-object. This is by default turned off. If you enable this then be aware that Java will deserialize the incoming data from the request to Java and that can be a potential security risk. | false | Boolean
-| *camel.component.jetty.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.jetty.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.jetty.continuation-timeout* | Allows to set a timeout in millis when using Jetty as consumer (server). By default Jetty uses 30000. You can use a value of = 0 to never expire. If a timeout occurs then the request will be expired and Jetty will return back a http error 503 to the client. This option is only in use when using Jetty with the Asynchronous Routing Engine. | 30000 | Long
-| *camel.component.jetty.enable-jmx* | If this option is true, Jetty JMX support will be enabled for this endpoint. | false | Boolean
-| *camel.component.jetty.enabled* | Whether to enable auto configuration of the jetty component. This is enabled by default. | | Boolean
-| *camel.component.jetty.error-handler* | This option is used to set the ErrorHandler that Jetty server uses. The option is a org.eclipse.jetty.server.handler.ErrorHandler type. | | ErrorHandler
-| *camel.component.jetty.header-filter-strategy* | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. The option is a org.apache.camel.spi.HeaderFilterStrategy type. | | HeaderFilterStrategy
-| *camel.component.jetty.http-binding* | Not to be used - use JettyHttpBinding instead. The option is a org.apache.camel.http.common.HttpBinding type. | | HttpBinding
-| *camel.component.jetty.http-configuration* | Jetty component does not use HttpConfiguration. The option is a org.apache.camel.http.common.HttpConfiguration type. | | HttpConfiguration
-| *camel.component.jetty.jetty-http-binding* | To use a custom org.apache.camel.component.jetty.JettyHttpBinding, which are used to customize how a response should be written for the producer. The option is a org.apache.camel.component.jetty.JettyHttpBinding type. | | JettyHttpBinding
-| *camel.component.jetty.keystore* | Specifies the location of the Java keystore file, which contains the Jetty server's own X.509 certificate in a key entry. | | String
-| *camel.component.jetty.max-threads* | To set a value for maximum number of threads in server thread pool. Notice that both a min and max size must be configured. | | Integer
-| *camel.component.jetty.mb-container* | To use a existing configured org.eclipse.jetty.jmx.MBeanContainer if JMX is enabled that Jetty uses for registering mbeans. The option is a org.eclipse.jetty.jmx.MBeanContainer type. | | MBeanContainer
-| *camel.component.jetty.min-threads* | To set a value for minimum number of threads in server thread pool. Notice that both a min and max size must be configured. | | Integer
-| *camel.component.jetty.proxy-host* | To use a http proxy to configure the hostname. | | String
-| *camel.component.jetty.proxy-port* | To use a http proxy to configure the port number. | | Integer
-| *camel.component.jetty.request-buffer-size* | Allows to configure a custom value of the request buffer size on the Jetty connectors. | | Integer
-| *camel.component.jetty.request-header-size* | Allows to configure a custom value of the request header size on the Jetty connectors. | | Integer
-| *camel.component.jetty.response-buffer-size* | Allows to configure a custom value of the response buffer size on the Jetty connectors. | | Integer
-| *camel.component.jetty.response-header-size* | Allows to configure a custom value of the response header size on the Jetty connectors. | | Integer
-| *camel.component.jetty.send-server-version* | If the option is true, jetty will send the server header with the jetty version information to the client which sends the request. NOTE please make sure there is no any other camel-jetty endpoint is share the same port, otherwise this option may not work as expected. | true | Boolean
-| *camel.component.jetty.socket-connector-properties* | A map which contains general HTTP connector properties. Uses the same principle as sslSocketConnectorProperties. | | Map
-| *camel.component.jetty.socket-connectors* | A map which contains per port number specific HTTP connectors. Uses the same principle as sslSocketConnectors. | | Map
-| *camel.component.jetty.ssl-context-parameters* | To configure security using SSLContextParameters. The option is a org.apache.camel.support.jsse.SSLContextParameters type. | | SSLContextParameters
-| *camel.component.jetty.ssl-key-password* | The key password, which is used to access the certificate's key entry in the keystore (this is the same password that is supplied to the keystore command's -keypass option). | | String
-| *camel.component.jetty.ssl-password* | The ssl password, which is required to access the keystore file (this is the same password that is supplied to the keystore command's -storepass option). | | String
-| *camel.component.jetty.ssl-socket-connector-properties* | A map which contains general SSL connector properties. | | Map
-| *camel.component.jetty.ssl-socket-connectors* | A map which contains per port number specific SSL connectors. | | Map
-| *camel.component.jetty.thread-pool* | To use a custom thread pool for the server. This option should only be used in special circumstances. The option is a org.eclipse.jetty.util.thread.ThreadPool type. | | ThreadPool
-| *camel.component.jetty.use-continuation* | Whether or not to use Jetty continuations for the Jetty Server. | true | Boolean
-| *camel.component.jetty.use-global-ssl-context-parameters* | Enable usage of global SSL context parameters | false | Boolean
-| *camel.component.jetty.use-x-forwarded-for-header* | To use the X-Forwarded-For header in HttpServletRequest.getRemoteAddr. | false | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-jgroups-raft-starter/src/main/docs/jgroups-raft-starter.adoc b/components-starter/camel-jgroups-raft-starter/src/main/docs/jgroups-raft-starter.adoc
deleted file mode 100644
index c9a19e7..0000000
--- a/components-starter/camel-jgroups-raft-starter/src/main/docs/jgroups-raft-starter.adoc
+++ /dev/null
@@ -1,41 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for jgroups-raft
-
-== Spring Boot Auto-Configuration
-
-When using jgroups-raft with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-jgroups-raft-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 13 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.jgroups-raft.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.jgroups-raft.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.jgroups-raft.channel-properties* | Specifies configuration properties of the RaftHandle JChannel used by the endpoint (ignored if raftHandle ref is provided). | raft.xml | String
-| *camel.component.jgroups-raft.enabled* | Whether to enable auto configuration of the jgroups-raft component. This is enabled by default. | | Boolean
-| *camel.component.jgroups-raft.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is process [...]
-| *camel.component.jgroups-raft.raft-handle* | RaftHandle to use. The option is a org.jgroups.raft.RaftHandle type. | | RaftHandle
-| *camel.component.jgroups-raft.raft-id* | Unique raftId to use. | | String
-| *camel.component.jgroups-raft.state-machine* | StateMachine to use. The option is a org.jgroups.protocols.raft.StateMachine type. | | StateMachine
-| *camel.component.jgroups.raft.cluster.service.enabled* | Sets if the jgroups raft cluster service should be enabled or not, default is false. | false | Boolean
-| *camel.component.jgroups.raft.cluster.service.id* | Cluster Service ID | | String
-| *camel.component.jgroups.raft.cluster.service.jgroups-raft-cluster-name* | JGroups Cluster name | | String
-| *camel.component.jgroups.raft.cluster.service.jgroups-raft-config* | JGrups-raft configuration File name | | String
-| *camel.component.jgroups.raft.cluster.service.raft-id* | JGroups-raft ID | | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-jgroups-starter/src/main/docs/jgroups-starter.adoc b/components-starter/camel-jgroups-starter/src/main/docs/jgroups-starter.adoc
deleted file mode 100644
index 8b9a8e7..0000000
--- a/components-starter/camel-jgroups-starter/src/main/docs/jgroups-starter.adoc
+++ /dev/null
@@ -1,39 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for jgroups
-
-== Spring Boot Auto-Configuration
-
-When using jgroups with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-jgroups-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 11 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.jgroups.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.jgroups.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.jgroups.channel* | Channel to use. The option is a org.jgroups.JChannel type. | | JChannel
-| *camel.component.jgroups.channel-properties* | Specifies configuration properties of the JChannel used by the endpoint. | | String
-| *camel.component.jgroups.enable-view-messages* | If set to true, the consumer endpoint will receive org.jgroups.View messages as well (not only org.jgroups.Message instances). By default only regular messages are consumed by the endpoint. | false | Boolean
-| *camel.component.jgroups.enabled* | Whether to enable auto configuration of the jgroups component. This is enabled by default. | | Boolean
-| *camel.component.jgroups.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
-| *camel.component.jgroups.lock.cluster.service.enabled* | Sets if the jgroups lock cluster service should be enabled or not, default is false. | false | Boolean
-| *camel.component.jgroups.lock.cluster.service.id* | Cluster Service ID | | String
-| *camel.component.jgroups.lock.cluster.service.jgroups-cluster-name* | JGroups Cluster name | | String
-| *camel.component.jgroups.lock.cluster.service.jgroups-config* | JGrups configuration File name | | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-jing-starter/src/main/docs/jing-starter.adoc b/components-starter/camel-jing-starter/src/main/docs/jing-starter.adoc
deleted file mode 100644
index ca419c3..0000000
--- a/components-starter/camel-jing-starter/src/main/docs/jing-starter.adoc
+++ /dev/null
@@ -1,31 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for jing
-
-== Spring Boot Auto-Configuration
-
-When using jing with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-jing-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 3 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.jing.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.jing.enabled* | Whether to enable auto configuration of the jing component. This is enabled by default. | | Boolean
-| *camel.component.jing.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-jira-starter/src/main/docs/jira-starter.adoc b/components-starter/camel-jira-starter/src/main/docs/jira-starter.adoc
deleted file mode 100644
index 222443b..0000000
--- a/components-starter/camel-jira-starter/src/main/docs/jira-starter.adoc
+++ /dev/null
@@ -1,41 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for jira
-
-== Spring Boot Auto-Configuration
-
-When using jira with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-jira-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 13 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.jira.access-token* | (OAuth only) The access token generated by the Jira server. | | String
-| *camel.component.jira.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.jira.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.jira.configuration* | To use a shared base jira configuration. The option is a org.apache.camel.component.jira.JiraConfiguration type. | | JiraConfiguration
-| *camel.component.jira.consumer-key* | (OAuth only) The consumer key from Jira settings. | | String
-| *camel.component.jira.delay* | Time in milliseconds to elapse for the next poll. | 6000 | Integer
-| *camel.component.jira.enabled* | Whether to enable auto configuration of the jira component. This is enabled by default. | | Boolean
-| *camel.component.jira.jira-url* | The Jira server url, example: \http://my_jira.com:8081 | | String
-| *camel.component.jira.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
-| *camel.component.jira.password* | (Basic authentication only) The password to authenticate to the Jira server. Use only if username basic authentication is used. | | String
-| *camel.component.jira.private-key* | (OAuth only) The private key generated by the client to encrypt the conversation to the server. | | String
-| *camel.component.jira.username* | (Basic authentication only) The username to authenticate to the Jira server. Use only if OAuth is not enabled on the Jira server. Do not set the username and OAuth token parameter, if they are both set, the username basic authentication takes precedence. | | String
-| *camel.component.jira.verification-code* | (OAuth only) The verification code from Jira generated in the first step of the authorization proccess. | | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-jms-starter/src/main/docs/jms-starter.adoc b/components-starter/camel-jms-starter/src/main/docs/jms-starter.adoc
deleted file mode 100644
index d83a58c..0000000
--- a/components-starter/camel-jms-starter/src/main/docs/jms-starter.adoc
+++ /dev/null
@@ -1,125 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for jms
-
-== Spring Boot Auto-Configuration
-
-When using jms with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-jms-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 97 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.jms.accept-messages-while-stopping* | Specifies whether the consumer accept messages while it is stopping. You may consider enabling this option, if you start and stop JMS routes at runtime, while there are still messages enqueued on the queue. If this option is false, and you stop the JMS route, then messages may be rejected, and the JMS broker would have to attempt redeliveries, which yet again may be rejected, and eventually the message may be moved at a dead letter [...]
-| *camel.component.jms.acknowledgement-mode-name* | The JMS acknowledgement name, which is one of: SESSION_TRANSACTED, CLIENT_ACKNOWLEDGE, AUTO_ACKNOWLEDGE, DUPS_OK_ACKNOWLEDGE | AUTO_ACKNOWLEDGE | String
-| *camel.component.jms.allow-additional-headers* | This option is used to allow additional headers which may have values that are invalid according to JMS specification. For example some message systems such as WMQ do this with header names using prefix JMS_IBM_MQMD_ containing values with byte array or other invalid types. You can specify multiple header names separated by comma, and use as suffix for wildcard matching. | | String
-| *camel.component.jms.allow-auto-wired-connection-factory* | Whether to auto-discover ConnectionFactory from the registry, if no connection factory has been configured. If only one instance of ConnectionFactory is found then it will be used. This is enabled by default. | true | Boolean
-| *camel.component.jms.allow-auto-wired-destination-resolver* | Whether to auto-discover DestinationResolver from the registry, if no destination resolver has been configured. If only one instance of DestinationResolver is found then it will be used. This is enabled by default. | true | Boolean
-| *camel.component.jms.allow-null-body* | Whether to allow sending messages with no body. If this option is false and the message body is null, then an JMSException is thrown. | true | Boolean
-| *camel.component.jms.allow-reply-manager-quick-stop* | Whether the DefaultMessageListenerContainer used in the reply managers for request-reply messaging allow the DefaultMessageListenerContainer.runningAllowed flag to quick stop in case JmsConfiguration#isAcceptMessagesWhileStopping is enabled, and org.apache.camel.CamelContext is currently being stopped. This quick stop ability is enabled by default in the regular JMS consumers but to enable for reply managers you must enable this fl [...]
-| *camel.component.jms.allow-serialized-headers* | Controls whether or not to include serialized headers. Applies only when transferExchange is true. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level. | false | Boolean
-| *camel.component.jms.always-copy-message* | If true, Camel will always make a JMS message copy of the message when it is passed to the producer for sending. Copying the message is needed in some situations, such as when a replyToDestinationSelectorName is set (incidentally, Camel will set the alwaysCopyMessage option to true, if a replyToDestinationSelectorName is set) | false | Boolean
-| *camel.component.jms.artemis-streaming-enabled* | Whether optimizing for Apache Artemis streaming mode. | true | Boolean
-| *camel.component.jms.async-consumer* | Whether the JmsConsumer processes the Exchange asynchronously. If enabled then the JmsConsumer may pickup the next message from the JMS queue, while the previous message is being processed asynchronously (by the Asynchronous Routing Engine). This means that messages may be processed not 100% strictly in order. If disabled (as default) then the Exchange is fully processed before the JmsConsumer will pickup the next message from the JMS queue. Note [...]
-| *camel.component.jms.async-start-listener* | Whether to startup the JmsConsumer message listener asynchronously, when starting a route. For example if a JmsConsumer cannot get a connection to a remote JMS broker, then it may block while retrying and/or failover. This will cause Camel to block while starting routes. By setting this option to true, you will let routes startup, while the JmsConsumer connects to the JMS broker using a dedicated thread in asynchronous mode. If this option i [...]
-| *camel.component.jms.async-stop-listener* | Whether to stop the JmsConsumer message listener asynchronously, when stopping a route. | false | Boolean
-| *camel.component.jms.auto-startup* | Specifies whether the consumer container should auto-startup. | true | Boolean
-| *camel.component.jms.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.jms.cache-level* | Sets the cache level by ID for the underlying JMS resources. See cacheLevelName option for more details. | | Integer
-| *camel.component.jms.cache-level-name* | Sets the cache level by name for the underlying JMS resources. Possible values are: CACHE_AUTO, CACHE_CONNECTION, CACHE_CONSUMER, CACHE_NONE, and CACHE_SESSION. The default setting is CACHE_AUTO. See the Spring documentation and Transactions Cache Levels for more information. | CACHE_AUTO | String
-| *camel.component.jms.client-id* | Sets the JMS client ID to use. Note that this value, if specified, must be unique and can only be used by a single JMS connection instance. It is typically only required for durable topic subscriptions. If using Apache ActiveMQ you may prefer to use Virtual Topics instead. | | String
-| *camel.component.jms.concurrent-consumers* | Specifies the default number of concurrent consumers when consuming from JMS (not for request/reply over JMS). See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. When doing request/reply over JMS then the option replyToConcurrentConsumers is used to control number of concurrent consumers on the reply message listener. | 1 | Integer
-| *camel.component.jms.configuration* | To use a shared JMS configuration. The option is a org.apache.camel.component.jms.JmsConfiguration type. | | JmsConfiguration
-| *camel.component.jms.connection-factory* | The connection factory to be use. A connection factory must be configured either on the component or endpoint. The option is a javax.jms.ConnectionFactory type. | | ConnectionFactory
-| *camel.component.jms.consumer-type* | The consumer type to use, which can be one of: Simple, Default, or Custom. The consumer type determines which Spring JMS listener to use. Default will use org.springframework.jms.listener.DefaultMessageListenerContainer, Simple will use org.springframework.jms.listener.SimpleMessageListenerContainer. When Custom is specified, the MessageListenerContainerFactory defined by the messageListenerContainerFactory option will determine what org.springfram [...]
-| *camel.component.jms.correlation-property* | When using InOut exchange pattern use this JMS property instead of JMSCorrelationID JMS property to correlate messages. If set messages will be correlated solely on the value of this property JMSCorrelationID property will be ignored and not set by Camel. | | String
-| *camel.component.jms.default-task-executor-type* | Specifies what default TaskExecutor type to use in the DefaultMessageListenerContainer, for both consumer endpoints and the ReplyTo consumer of producer endpoints. Possible values: SimpleAsync (uses Spring's SimpleAsyncTaskExecutor) or ThreadPool (uses Spring's ThreadPoolTaskExecutor with optimal values - cached threadpool-like). If not set, it defaults to the previous behaviour, which uses a cached thread pool for consumer endpoints a [...]
-| *camel.component.jms.delivery-delay* | Sets delivery delay to use for send calls for JMS. This option requires JMS 2.0 compliant broker. | -1 | Long
-| *camel.component.jms.delivery-mode* | Specifies the delivery mode to be used. Possible values are those defined by javax.jms.DeliveryMode. NON_PERSISTENT = 1 and PERSISTENT = 2. | | Integer
-| *camel.component.jms.delivery-persistent* | Specifies whether persistent delivery is used by default. | true | Boolean
-| *camel.component.jms.destination-resolver* | A pluggable org.springframework.jms.support.destination.DestinationResolver that allows you to use your own resolver (for example, to lookup the real destination in a JNDI registry). The option is a org.springframework.jms.support.destination.DestinationResolver type. | | DestinationResolver
-| *camel.component.jms.disable-reply-to* | Specifies whether Camel ignores the JMSReplyTo header in messages. If true, Camel does not send a reply back to the destination specified in the JMSReplyTo header. You can use this option if you want Camel to consume from a route and you do not want Camel to automatically send back a reply message because another component in your code handles the reply message. You can also use this option if you want to use Camel as a proxy between different m [...]
-| *camel.component.jms.disable-time-to-live* | Use this option to force disabling time to live. For example when you do request/reply over JMS, then Camel will by default use the requestTimeout value as time to live on the message being sent. The problem is that the sender and receiver systems have to have their clocks synchronized, so they are in sync. This is not always so easy to archive. So you can use disableTimeToLive=true to not set a time to live value on the sent message. Then t [...]
-| *camel.component.jms.durable-subscription-name* | The durable subscriber name for specifying durable topic subscriptions. The clientId option must be configured as well. | | String
-| *camel.component.jms.eager-loading-of-properties* | Enables eager loading of JMS properties and payload as soon as a message is loaded which generally is inefficient as the JMS properties may not be required but sometimes can catch early any issues with the underlying JMS provider and the use of JMS properties. See also the option eagerPoisonBody. | false | Boolean
-| *camel.component.jms.eager-poison-body* | If eagerLoadingOfProperties is enabled and the JMS message payload (JMS body or JMS properties) is poison (cannot be read/mapped), then set this text as the message body instead so the message can be processed (the cause of the poison are already stored as exception on the Exchange). This can be turned off by setting eagerPoisonBody=false. See also the option eagerLoadingOfProperties. | Poison JMS message due to ${exception.message} | String
-| *camel.component.jms.enabled* | Whether to enable auto configuration of the jms component. This is enabled by default. | | Boolean
-| *camel.component.jms.error-handler* | Specifies a org.springframework.util.ErrorHandler to be invoked in case of any uncaught exceptions thrown while processing a Message. By default these exceptions will be logged at the WARN level, if no errorHandler has been configured. You can configure logging level and whether stack traces should be logged using errorHandlerLoggingLevel and errorHandlerLogStackTrace options. This makes it much easier to configure, than having to code a custom err [...]
-| *camel.component.jms.error-handler-log-stack-trace* | Allows to control whether stacktraces should be logged or not, by the default errorHandler. | true | Boolean
-| *camel.component.jms.error-handler-logging-level* | Allows to configure the default errorHandler logging level for logging uncaught exceptions. | | LoggingLevel
-| *camel.component.jms.exception-listener* | Specifies the JMS Exception Listener that is to be notified of any underlying JMS exceptions. The option is a javax.jms.ExceptionListener type. | | ExceptionListener
-| *camel.component.jms.explicit-qos-enabled* | Set if the deliveryMode, priority or timeToLive qualities of service should be used when sending messages. This option is based on Spring's JmsTemplate. The deliveryMode, priority and timeToLive options are applied to the current endpoint. This contrasts with the preserveMessageQos option, which operates at message granularity, reading QoS properties exclusively from the Camel In message headers. | false | Boolean
-| *camel.component.jms.expose-listener-session* | Specifies whether the listener session should be exposed when consuming messages. | false | Boolean
-| *camel.component.jms.force-send-original-message* | When using mapJmsMessage=false Camel will create a new JMS message to send to a new JMS destination if you touch the headers (get or set) during the route. Set this option to true to force Camel to send the original JMS message that was received. | false | Boolean
-| *camel.component.jms.format-date-headers-to-iso8601* | Sets whether JMS date properties should be formatted according to the ISO 8601 standard. | false | Boolean
-| *camel.component.jms.header-filter-strategy* | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. The option is a org.apache.camel.spi.HeaderFilterStrategy type. | | HeaderFilterStrategy
-| *camel.component.jms.idle-consumer-limit* | Specify the limit for the number of consumers that are allowed to be idle at any given time. | 1 | Integer
-| *camel.component.jms.idle-task-execution-limit* | Specifies the limit for idle executions of a receive task, not having received any message within its execution. If this limit is reached, the task will shut down and leave receiving to other executing tasks (in the case of dynamic scheduling; see the maxConcurrentConsumers setting). There is additional doc available from Spring. | 1 | Integer
-| *camel.component.jms.include-all-j-m-s-x-properties* | Whether to include all JMSXxxx properties when mapping from JMS to Camel Message. Setting this to true will include properties such as JMSXAppID, and JMSXUserID etc. Note: If you are using a custom headerFilterStrategy then this option does not apply. | false | Boolean
-| *camel.component.jms.include-sent-j-m-s-message-i-d* | Only applicable when sending to JMS destination using InOnly (eg fire and forget). Enabling this option will enrich the Camel Exchange with the actual JMSMessageID that was used by the JMS client when the message was sent to the JMS destination. | false | Boolean
-| *camel.component.jms.jms-key-format-strategy* | Pluggable strategy for encoding and decoding JMS keys so they can be compliant with the JMS specification. Camel provides two implementations out of the box: default and passthrough. The default strategy will safely marshal dots and hyphens (. and -). The passthrough strategy leaves the key as is. Can be used for JMS brokers which do not care whether JMS header keys contain illegal characters. You can provide your own implementation of th [...]
-| *camel.component.jms.jms-message-type* | Allows you to force the use of a specific javax.jms.Message implementation for sending JMS messages. Possible values are: Bytes, Map, Object, Stream, Text. By default, Camel would determine which JMS message type to use from the In body type. This option allows you to specify it. | | JmsMessageType
-| *camel.component.jms.lazy-create-transaction-manager* | If true, Camel will create a JmsTransactionManager, if there is no transactionManager injected when option transacted=true. | true | Boolean
-| *camel.component.jms.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then c [...]
-| *camel.component.jms.map-jms-message* | Specifies whether Camel should auto map the received JMS message to a suited payload type, such as javax.jms.TextMessage to a String etc. | true | Boolean
-| *camel.component.jms.max-concurrent-consumers* | Specifies the maximum number of concurrent consumers when consuming from JMS (not for request/reply over JMS). See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. When doing request/reply over JMS then the option replyToMaxConcurrentConsumers is used to control number of concurrent consumers on the reply message listener. | | Integer
-| *camel.component.jms.max-messages-per-task* | The number of messages per task. -1 is unlimited. If you use a range for concurrent consumers (eg min max), then this option can be used to set a value to eg 100 to control how fast the consumers will shrink when less work is required. | -1 | Integer
-| *camel.component.jms.message-converter* | To use a custom Spring org.springframework.jms.support.converter.MessageConverter so you can be in control how to map to/from a javax.jms.Message. The option is a org.springframework.jms.support.converter.MessageConverter type. | | MessageConverter
-| *camel.component.jms.message-created-strategy* | To use the given MessageCreatedStrategy which are invoked when Camel creates new instances of javax.jms.Message objects when Camel is sending a JMS message. The option is a org.apache.camel.component.jms.MessageCreatedStrategy type. | | MessageCreatedStrategy
-| *camel.component.jms.message-id-enabled* | When sending, specifies whether message IDs should be added. This is just an hint to the JMS broker. If the JMS provider accepts this hint, these messages must have the message ID set to null; if the provider ignores the hint, the message ID must be set to its normal unique value. | true | Boolean
-| *camel.component.jms.message-listener-container-factory* | Registry ID of the MessageListenerContainerFactory used to determine what org.springframework.jms.listener.AbstractMessageListenerContainer to use to consume messages. Setting this will automatically set consumerType to Custom. The option is a org.apache.camel.component.jms.MessageListenerContainerFactory type. | | MessageListenerContainerFactory
-| *camel.component.jms.message-timestamp-enabled* | Specifies whether timestamps should be enabled by default on sending messages. This is just an hint to the JMS broker. If the JMS provider accepts this hint, these messages must have the timestamp set to zero; if the provider ignores the hint the timestamp must be set to its normal value. | true | Boolean
-| *camel.component.jms.password* | Password to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory. | | String
-| *camel.component.jms.preserve-message-qos* | Set to true, if you want to send message using the QoS settings specified on the message, instead of the QoS settings on the JMS endpoint. The following three headers are considered JMSPriority, JMSDeliveryMode, and JMSExpiration. You can provide all or only some of them. If not provided, Camel will fall back to use the values from the endpoint instead. So, when using this option, the headers override the values from the endpoint. The explic [...]
-| *camel.component.jms.priority* | Values greater than 1 specify the message priority when sending (where 0 is the lowest priority and 9 is the highest). The explicitQosEnabled option must also be enabled in order for this option to have any effect. | 4 | Integer
-| *camel.component.jms.pub-sub-no-local* | Specifies whether to inhibit the delivery of messages published by its own connection. | false | Boolean
-| *camel.component.jms.queue-browse-strategy* | To use a custom QueueBrowseStrategy when browsing queues. The option is a org.apache.camel.component.jms.QueueBrowseStrategy type. | | QueueBrowseStrategy
-| *camel.component.jms.receive-timeout* | The timeout for receiving messages (in milliseconds). The option is a long type. | 1000 | Long
-| *camel.component.jms.recovery-interval* | Specifies the interval between recovery attempts, i.e. when a connection is being refreshed, in milliseconds. The default is 5000 ms, that is, 5 seconds. The option is a long type. | 5000 | Long
-| *camel.component.jms.reply-to* | Provides an explicit ReplyTo destination (overrides any incoming value of Message.getJMSReplyTo() in consumer). | | String
-| *camel.component.jms.reply-to-cache-level-name* | Sets the cache level by name for the reply consumer when doing request/reply over JMS. This option only applies when using fixed reply queues (not temporary). Camel will by default use: CACHE_CONSUMER for exclusive or shared w/ replyToSelectorName. And CACHE_SESSION for shared without replyToSelectorName. Some JMS brokers such as IBM WebSphere may require to set the replyToCacheLevelName=CACHE_NONE to work. Note: If using temporary queu [...]
-| *camel.component.jms.reply-to-concurrent-consumers* | Specifies the default number of concurrent consumers when doing request/reply over JMS. See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. | 1 | Integer
-| *camel.component.jms.reply-to-delivery-persistent* | Specifies whether to use persistent delivery by default for replies. | true | Boolean
-| *camel.component.jms.reply-to-destination-selector-name* | Sets the JMS Selector using the fixed name to be used so you can filter out your own replies from the others when using a shared queue (that is, if you are not using a temporary reply queue). | | String
-| *camel.component.jms.reply-to-max-concurrent-consumers* | Specifies the maximum number of concurrent consumers when using request/reply over JMS. See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. | | Integer
-| *camel.component.jms.reply-to-on-timeout-max-concurrent-consumers* | Specifies the maximum number of concurrent consumers for continue routing when timeout occurred when using request/reply over JMS. | 1 | Integer
-| *camel.component.jms.reply-to-override* | Provides an explicit ReplyTo destination in the JMS message, which overrides the setting of replyTo. It is useful if you want to forward the message to a remote Queue and receive the reply message from the ReplyTo destination. | | String
-| *camel.component.jms.reply-to-same-destination-allowed* | Whether a JMS consumer is allowed to send a reply message to the same destination that the consumer is using to consume from. This prevents an endless loop by consuming and sending back the same message to itself. | false | Boolean
-| *camel.component.jms.reply-to-type* | Allows for explicitly specifying which kind of strategy to use for replyTo queues when doing request/reply over JMS. Possible values are: Temporary, Shared, or Exclusive. By default Camel will use temporary queues. However if replyTo has been configured, then Shared is used by default. This option allows you to use exclusive queues instead of shared ones. See Camel JMS documentation for more details, and especially the notes about the implications [...]
-| *camel.component.jms.request-timeout* | The timeout for waiting for a reply when using the InOut Exchange Pattern (in milliseconds). The default is 20 seconds. You can include the header CamelJmsRequestTimeout to override this endpoint configured timeout value, and thus have per message individual timeout values. See also the requestTimeoutCheckerInterval option. The option is a long type. | 20000 | Long
-| *camel.component.jms.request-timeout-checker-interval* | Configures how often Camel should check for timed out Exchanges when doing request/reply over JMS. By default Camel checks once per second. But if you must react faster when a timeout occurs, then you can lower this interval, to check more frequently. The timeout is determined by the option requestTimeout. The option is a long type. | 1000 | Long
-| *camel.component.jms.selector* | Sets the JMS selector to use | | String
-| *camel.component.jms.stream-message-type-enabled* | Sets whether StreamMessage type is enabled or not. Message payloads of streaming kind such as files, InputStream, etc will either by sent as BytesMessage or StreamMessage. This option controls which kind will be used. By default BytesMessage is used which enforces the entire message payload to be read into memory. By enabling this option the message payload is read into memory in chunks and each chunk is then written to the StreamMess [...]
-| *camel.component.jms.subscription-durable* | Set whether to make the subscription durable. The durable subscription name to be used can be specified through the subscriptionName property. Default is false. Set this to true to register a durable subscription, typically in combination with a subscriptionName value (unless your message listener class name is good enough as subscription name). Only makes sense when listening to a topic (pub-sub domain), therefore this method switches the p [...]
-| *camel.component.jms.subscription-name* | Set the name of a subscription to create. To be applied in case of a topic (pub-sub domain) with a shared or durable subscription. The subscription name needs to be unique within this client's JMS client id. Default is the class name of the specified message listener. Note: Only 1 concurrent consumer (which is the default of this message listener container) is allowed for each subscription, except for a shared subscription (which requires JMS 2 [...]
-| *camel.component.jms.subscription-shared* | Set whether to make the subscription shared. The shared subscription name to be used can be specified through the subscriptionName property. Default is false. Set this to true to register a shared subscription, typically in combination with a subscriptionName value (unless your message listener class name is good enough as subscription name). Note that shared subscriptions may also be durable, so this flag can (and often will) be combined wit [...]
-| *camel.component.jms.task-executor* | Allows you to specify a custom task executor for consuming messages. The option is a org.springframework.core.task.TaskExecutor type. | | TaskExecutor
-| *camel.component.jms.test-connection-on-startup* | Specifies whether to test the connection on startup. This ensures that when Camel starts that all the JMS consumers have a valid connection to the JMS broker. If a connection cannot be granted then Camel throws an exception on startup. This ensures that Camel is not started with failed connections. The JMS producers is tested as well. | false | Boolean
-| *camel.component.jms.time-to-live* | When sending messages, specifies the time-to-live of the message (in milliseconds). | -1 | Long
-| *camel.component.jms.transacted* | Specifies whether to use transacted mode | false | Boolean
-| *camel.component.jms.transacted-in-out* | Specifies whether InOut operations (request reply) default to using transacted mode If this flag is set to true, then Spring JmsTemplate will have sessionTransacted set to true, and the acknowledgeMode as transacted on the JmsTemplate used for InOut operations. Note from Spring JMS: that within a JTA transaction, the parameters passed to createQueue, createTopic methods are not taken into account. Depending on the Java EE transaction context, t [...]
-| *camel.component.jms.transaction-manager* | The Spring transaction manager to use. The option is a org.springframework.transaction.PlatformTransactionManager type. | | PlatformTransactionManager
-| *camel.component.jms.transaction-name* | The name of the transaction to use. | | String
-| *camel.component.jms.transaction-timeout* | The timeout value of the transaction (in seconds), if using transacted mode. | -1 | Integer
-| *camel.component.jms.transfer-exception* | If enabled and you are using Request Reply messaging (InOut) and an Exchange failed on the consumer side, then the caused Exception will be send back in response as a javax.jms.ObjectMessage. If the client is Camel, the returned Exception is rethrown. This allows you to use Camel JMS as a bridge in your routing - for example, using persistent queues to enable robust routing. Notice that if you also have transferExchange enabled, this option ta [...]
-| *camel.component.jms.transfer-exchange* | You can transfer the exchange over the wire instead of just the body and headers. The following fields are transferred: In body, Out body, Fault body, In headers, Out headers, Fault headers, exchange properties, exchange exception. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level. You must enable this option on both the producer and consumer side, so Camel knows the payloa [...]
-| *camel.component.jms.use-message-i-d-as-correlation-i-d* | Specifies whether JMSMessageID should always be used as JMSCorrelationID for InOut messages. | false | Boolean
-| *camel.component.jms.username* | Username to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory. | | String
-| *camel.component.jms.wait-for-provision-correlation-to-be-updated-counter* | Number of times to wait for provisional correlation id to be updated to the actual correlation id when doing request/reply over JMS and when the option useMessageIDAsCorrelationID is enabled. | 50 | Integer
-| *camel.component.jms.wait-for-provision-correlation-to-be-updated-thread-sleeping-time* | Interval in millis to sleep each time while waiting for provisional correlation id to be updated. The option is a long type. | 100 | Long
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-jmx-starter/src/main/docs/jmx-starter.adoc b/components-starter/camel-jmx-starter/src/main/docs/jmx-starter.adoc
deleted file mode 100644
index d9967c7..0000000
--- a/components-starter/camel-jmx-starter/src/main/docs/jmx-starter.adoc
+++ /dev/null
@@ -1,31 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for jmx
-
-== Spring Boot Auto-Configuration
-
-When using jmx with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-jmx-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 3 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.jmx.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.jmx.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.jmx.enabled* | Whether to enable auto configuration of the jmx component. This is enabled by default. | | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-johnzon-starter/src/main/docs/johnzon-starter.adoc b/components-starter/camel-johnzon-starter/src/main/docs/johnzon-starter.adoc
deleted file mode 100644
index e7ff16b..0000000
--- a/components-starter/camel-johnzon-starter/src/main/docs/johnzon-starter.adoc
+++ /dev/null
@@ -1,32 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for johnzon
-
-== Spring Boot Auto-Configuration
-
-When using johnzon with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-johnzon-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 4 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.dataformat.json-johnzon.enabled* | Whether to enable auto configuration of the json-johnzon data format. This is enabled by default. | | Boolean
-| *camel.dataformat.json-johnzon.object-mapper* | Lookup and use the existing Mapper with the given id. | | String
-| *camel.dataformat.json-johnzon.pretty-print* | To enable pretty printing output nicely formatted. Is by default false. | false | Boolean
-| *camel.dataformat.json-johnzon.unmarshal-type-name* | Class name of the java type to use when unmarshalling | | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-jolt-starter/src/main/docs/jolt-starter.adoc b/components-starter/camel-jolt-starter/src/main/docs/jolt-starter.adoc
deleted file mode 100644
index 03de86f..0000000
--- a/components-starter/camel-jolt-starter/src/main/docs/jolt-starter.adoc
+++ /dev/null
@@ -1,33 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for jolt
-
-== Spring Boot Auto-Configuration
-
-When using jolt with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-jolt-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 5 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.jolt.allow-template-from-header* | Whether to allow to use resource template from header or not (default false). Enabling this allows to specify dynamic templates via message header. However this can be seen as a potential security vulnerability if the header is coming from a malicious user, so use this with care. | false | Boolean
-| *camel.component.jolt.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.jolt.enabled* | Whether to enable auto configuration of the jolt component. This is enabled by default. | | Boolean
-| *camel.component.jolt.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
-| *camel.component.jolt.transform* | Explicitly sets the Transform to use. If not set a Transform specified by the transformDsl will be created. The option is a com.bazaarvoice.jolt.Transform type. | | Transform
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-jooq-starter/src/main/docs/jooq-starter.adoc b/components-starter/camel-jooq-starter/src/main/docs/jooq-starter.adoc
deleted file mode 100644
index 837680c..0000000
--- a/components-starter/camel-jooq-starter/src/main/docs/jooq-starter.adoc
+++ /dev/null
@@ -1,37 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for jooq
-
-== Spring Boot Auto-Configuration
-
-When using jooq with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-jooq-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 9 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.jooq.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.jooq.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.jooq.configuration* | Component configuration (database connection, database entity type, etc.). The option is a org.apache.camel.component.jooq.JooqConfiguration type. | | JooqConfiguration
-| *camel.component.jooq.consume-delete* | Delete entity after it is consumed | true | Boolean
-| *camel.component.jooq.database-configuration* | To use a specific database configuration. The option is a org.jooq.Configuration type. | | Configuration
-| *camel.component.jooq.enabled* | Whether to enable auto configuration of the jooq component. This is enabled by default. | | Boolean
-| *camel.component.jooq.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
-| *camel.component.jooq.operation* | Type of operation to execute on query | | JooqOperation
-| *camel.component.jooq.query* | To execute plain SQL query | | String
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-joor-starter/src/main/docs/joor-starter.adoc b/components-starter/camel-joor-starter/src/main/docs/joor-starter.adoc
deleted file mode 100644
index c6c0c49..0000000
--- a/components-starter/camel-joor-starter/src/main/docs/joor-starter.adoc
+++ /dev/null
@@ -1,34 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for joor
-
-== Spring Boot Auto-Configuration
-
-When using joor with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-joor-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 4 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.language.joor.enabled* | Whether to enable auto configuration of the joor language. This is enabled by default. | | Boolean
-| *camel.language.joor.pre-compile* | Whether the expression should be pre compiled once during initialization phase. If this is turned off, then the expression is reloaded and compiled on each evaluation. | true | Boolean
-| *camel.language.joor.single-quotes* | Whether single quotes can be used as replacement for double quotes. This is convenient when you need to work with strings inside strings. | true | Boolean
-| *camel.language.joor.trim* | Whether to trim the value to remove leading and trailing whitespaces and line breaks | true | Boolean
-|===
-
-
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-jpa-starter/src/main/docs/jpa-starter.adoc b/components-starter/camel-jpa-starter/src/main/docs/jpa-starter.adoc
deleted file mode 100644
index 1f5a1a4..0000000
--- a/components-starter/camel-jpa-starter/src/main/docs/jpa-starter.adoc
+++ /dev/null
@@ -1,36 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for jpa
-
-== Spring Boot Auto-Configuration
-
-When using jpa with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-jpa-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 8 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.jpa.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.jpa.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
-| *camel.component.jpa.enabled* | Whether to enable auto configuration of the jpa component. This is enabled by default. | | Boolean
-| *camel.component.jpa.entity-manager-factory* | To use the EntityManagerFactory. This is strongly recommended to configure. The option is a javax.persistence.EntityManagerFactory type. | | EntityManagerFactory
-| *camel.component.jpa.join-transaction* | The camel-jpa component will join transaction by default. You can use this option to turn this off, for example if you use LOCAL_RESOURCE and join transaction doesn't work with your JPA provider. This option can also be set globally on the JpaComponent, instead of having to set it on all endpoints. | true | Boolean
-| *camel.component.jpa.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then c [...]
-| *camel.component.jpa.shared-entity-manager* | Whether to use Spring's SharedEntityManager for the consumer/producer. Note in most cases joinTransaction should be set to false as this is not an EXTENDED EntityManager. | false | Boolean
-| *camel.component.jpa.transaction-manager* | To use the PlatformTransactionManager for managing transactions. The option is a org.springframework.transaction.PlatformTransactionManager type. | | PlatformTransactionManager
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-jsch-starter/src/main/docs/jsch-starter.adoc b/components-starter/camel-jsch-starter/src/main/docs/jsch-starter.adoc
deleted file mode 100644
index 20ed5bd..0000000
--- a/components-starter/camel-jsch-starter/src/main/docs/jsch-starter.adoc
+++ /dev/null
@@ -1,32 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for jsch
-
-== Spring Boot Auto-Configuration
-
-When using jsch with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-jsch-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 4 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.scp.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.scp.enabled* | Whether to enable auto configuration of the scp component. This is enabled by default. | | Boolean
-| *camel.component.scp.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then c [...]
-| *camel.component.scp.verbose-logging* | JSCH is verbose logging out of the box. Therefore we turn the logging down to DEBUG logging by default. But setting this option to true turns on the verbose logging again. | false | Boolean
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-jslt-starter/src/main/docs/jslt-starter.adoc b/components-starter/camel-jslt-starter/src/main/docs/jslt-starter.adoc
deleted file mode 100644
index fece4a6..0000000
--- a/components-starter/camel-jslt-starter/src/main/docs/jslt-starter.adoc
+++ /dev/null
@@ -1,34 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for jslt
-
-== Spring Boot Auto-Configuration
-
-When using jslt with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-jslt-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 6 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.jslt.allow-template-from-header* | Whether to allow to use resource template from header or not (default false). Enabling this allows to specify dynamic templates via message header. However this can be seen as a potential security vulnerability if the header is coming from a malicious user, so use this with care. | false | Boolean
-| *camel.component.jslt.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.jslt.enabled* | Whether to enable auto configuration of the jslt component. This is enabled by default. | | Boolean
-| *camel.component.jslt.functions* | JSLT can be extended by plugging in functions written in Java. | | Collection
-| *camel.component.jslt.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
-| *camel.component.jslt.object-filter* | JSLT can be extended by plugging in a custom jslt object filter. The option is a com.schibsted.spt.data.jslt.filters.JsonFilter type. | | JsonFilter
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-json-validator-starter/src/main/docs/json-validator-starter.adoc b/components-starter/camel-json-validator-starter/src/main/docs/json-validator-starter.adoc
deleted file mode 100644
index 1d9e851..0000000
--- a/components-starter/camel-json-validator-starter/src/main/docs/json-validator-starter.adoc
+++ /dev/null
@@ -1,31 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for json-validator
-
-== Spring Boot Auto-Configuration
-
-When using json-validator with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-json-validator-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 3 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.json-validator.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.json-validator.enabled* | Whether to enable auto configuration of the json-validator component. This is enabled by default. | | Boolean
-| *camel.component.json-validator.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proce [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-jsonapi-starter/src/main/docs/jsonapi-starter.adoc b/components-starter/camel-jsonapi-starter/src/main/docs/jsonapi-starter.adoc
deleted file mode 100644
index daacfca..0000000
--- a/components-starter/camel-jsonapi-starter/src/main/docs/jsonapi-starter.adoc
+++ /dev/null
@@ -1,31 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for jsonapi
-
-== Spring Boot Auto-Configuration
-
-When using jsonapi with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-jsonapi-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 3 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.dataformat.jsonapi.data-format-types* | The classes to take into account for the marshalling | | Class[]
-| *camel.dataformat.jsonapi.enabled* | Whether to enable auto configuration of the jsonApi data format. This is enabled by default. | | Boolean
-| *camel.dataformat.jsonapi.main-format-type* | The classes to take into account while unmarshalling | | Class
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-jsonata-starter/src/main/docs/jsonata-starter.adoc b/components-starter/camel-jsonata-starter/src/main/docs/jsonata-starter.adoc
deleted file mode 100644
index d8b7979..0000000
--- a/components-starter/camel-jsonata-starter/src/main/docs/jsonata-starter.adoc
+++ /dev/null
@@ -1,31 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for jsonata
-
-== Spring Boot Auto-Configuration
-
-When using jsonata with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-jsonata-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 3 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.jsonata.autowired-enabled* | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean
-| *camel.component.jsonata.enabled* | Whether to enable auto configuration of the jsonata component. This is enabled by default. | | Boolean
-| *camel.component.jsonata.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
-|===
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-jsonb-starter/src/main/docs/jsonb-starter.adoc b/components-starter/camel-jsonb-starter/src/main/docs/jsonb-starter.adoc
deleted file mode 100644
index 5ea1118..0000000
--- a/components-starter/camel-jsonb-starter/src/main/docs/jsonb-starter.adoc
+++ /dev/null
@@ -1,34 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for jsonb
-
-== Spring Boot Auto-Configuration
-
-When using jsonb with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-jsonb-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 4 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.dataformat.json-jsonb.enabled* | Whether to enable auto configuration of the json-jsonb data format. This is enabled by default. | | Boolean
-| *camel.dataformat.json-jsonb.object-mapper* | Lookup and use the existing Jsonb instance with the given id. | | String
-| *camel.dataformat.json-jsonb.pretty-print* | To enable pretty printing output nicely formatted. Is by default false. | false | Boolean
-| *camel.dataformat.json-jsonb.unmarshal-type-name* | Class name of the java type to use when unmarshalling | | String
-|===
-
-
-// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-jsonpath-starter/src/main/docs/jsonpath-starter.adoc b/components-starter/camel-jsonpath-starter/src/main/docs/jsonpath-starter.adoc
deleted file mode 100644
index dc32930..0000000
--- a/components-starter/camel-jsonpath-starter/src/main/docs/jsonpath-starter.adoc
+++ /dev/null
@@ -1,36 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for jsonpath
-
-== Spring Boot Auto-Configuration
-
-When using jsonpath with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-jsonpath-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 8 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.language.jsonpath.allow-easy-predicate* | Whether to allow using the easy predicate parser to pre-parse predicates. | true | Boolean
-| *camel.language.jsonpath.allow-simple* | Whether to allow in inlined simple exceptions in the JsonPath expression | true | Boolean
-| *camel.language.jsonpath.enabled* | Whether to enable auto configuration of the jsonpath language. This is enabled by default. | | Boolean
-| *camel.language.jsonpath.header-name* | Name of header to use as input, instead of the message body | | String
-| *camel.language.jsonpath.option* | To configure additional options on json path. Multiple values can be separated by comma. | | String
-| *camel.language.jsonpath.suppress-exceptions* | Whether to suppress exceptions such as PathNotFoundException. | false | Boolean
-| *camel.language.jsonpath.trim* | Whether to trim the value to remove leading and trailing whitespaces and line breaks | true | Boolean
-| *camel.language.jsonpath.write-as-string* | Whether to write the output of each row/element as a JSON String value instead of a Map/POJO value. | false | Boolean
-|===
-// spring-boot-auto-configure options: END
... 22798 lines suppressed ...