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/11/13 01:11:50 UTC
[camel-kafka-connector] 02/07: remove docs and connectors copies of
hard-coded generated .adoc files
This is an automated email from the ASF dual-hosted git repository.
djencks pushed a commit to branch camel-kafka-connector-0.11.x
in repository https://gitbox.apache.org/repos/asf/camel-kafka-connector.git
commit 24545fd875ca5be464829de1b5c4ea7760029f44
Author: David Jencks <dj...@apache.org>
AuthorDate: Thu Nov 4 11:30:48 2021 -0700
remove docs and connectors copies of hard-coded generated .adoc files
---
.../docs/camel-activemq-kafka-sink-connector.adoc | 200 ------------------
.../camel-activemq-kafka-source-connector.adoc | 201 ------------------
.../main/docs/camel-ahc-kafka-sink-connector.adoc | 74 -------
.../docs/camel-ahc-ws-kafka-sink-connector.adoc | 75 -------
.../docs/camel-ahc-ws-kafka-source-connector.adoc | 75 -------
.../docs/camel-ahc-wss-kafka-sink-connector.adoc | 75 -------
.../docs/camel-ahc-wss-kafka-source-connector.adoc | 75 -------
.../main/docs/camel-amqp-kafka-sink-connector.adoc | 197 ------------------
.../docs/camel-amqp-kafka-source-connector.adoc | 197 ------------------
.../docs/camel-arangodb-kafka-sink-connector.adoc | 74 -------
.../main/docs/camel-as2-kafka-sink-connector.adoc | 84 --------
.../docs/camel-as2-kafka-source-connector.adoc | 85 --------
.../docs/camel-asterisk-kafka-sink-connector.adoc | 59 ------
.../camel-asterisk-kafka-source-connector.adoc | 60 ------
.../docs/camel-atlasmap-kafka-sink-connector.adoc | 62 ------
.../docs/camel-atmos-kafka-sink-connector.adoc | 68 ------
.../docs/camel-atmos-kafka-source-connector.adoc | 70 -------
...-atmosphere-websocket-kafka-sink-connector.adoc | 67 ------
...tmosphere-websocket-kafka-source-connector.adoc | 86 --------
.../docs/camel-atom-kafka-source-connector.adoc | 81 --------
.../camel-atomix-map-kafka-sink-connector.adoc | 84 --------
.../camel-atomix-map-kafka-source-connector.adoc | 86 --------
...amel-atomix-messaging-kafka-sink-connector.adoc | 86 --------
...el-atomix-messaging-kafka-source-connector.adoc | 88 --------
...camel-atomix-multimap-kafka-sink-connector.adoc | 84 --------
.../camel-atomix-queue-kafka-sink-connector.adoc | 80 --------
.../camel-atomix-queue-kafka-source-connector.adoc | 82 --------
.../camel-atomix-set-kafka-sink-connector.adoc | 82 --------
.../camel-atomix-set-kafka-source-connector.adoc | 84 --------
.../camel-atomix-value-kafka-sink-connector.adoc | 82 --------
.../camel-atomix-value-kafka-source-connector.adoc | 84 --------
.../main/docs/camel-avro-kafka-sink-connector.adoc | 71 -------
.../docs/camel-avro-kafka-source-connector.adoc | 73 -------
...l-aws-secrets-manager-kafka-sink-connector.adoc | 84 --------
.../camel-aws2-athena-kafka-sink-connector.adoc | 110 ----------
.../docs/camel-aws2-cw-kafka-sink-connector.adoc | 86 --------
.../docs/camel-aws2-ddb-kafka-sink-connector.adoc | 92 ---------
...amel-aws2-ddbstream-kafka-source-connector.adoc | 102 ---------
.../docs/camel-aws2-ec2-kafka-sink-connector.adoc | 82 --------
.../docs/camel-aws2-ecs-kafka-sink-connector.adoc | 82 --------
.../docs/camel-aws2-eks-kafka-sink-connector.adoc | 82 --------
...amel-aws2-eventbridge-kafka-sink-connector.adoc | 84 --------
.../docs/camel-aws2-iam-kafka-sink-connector.adoc | 82 --------
...aws2-kinesis-firehose-kafka-sink-connector.adoc | 82 --------
.../camel-aws2-kinesis-kafka-sink-connector.adoc | 87 --------
.../camel-aws2-kinesis-kafka-source-connector.adoc | 115 -----------
.../docs/camel-aws2-kms-kafka-sink-connector.adoc | 82 --------
.../camel-aws2-lambda-kafka-sink-connector.adoc | 82 --------
.../docs/camel-aws2-mq-kafka-sink-connector.adoc | 82 --------
.../docs/camel-aws2-msk-kafka-sink-connector.adoc | 82 --------
.../docs/camel-aws2-s3-kafka-sink-connector.adoc | 149 --------------
.../docs/camel-aws2-s3-kafka-source-connector.adoc | 165 ---------------
.../docs/camel-aws2-ses-kafka-sink-connector.adoc | 86 --------
.../docs/camel-aws2-sns-kafka-sink-connector.adoc | 99 ---------
.../docs/camel-aws2-sqs-kafka-sink-connector.adoc | 118 -----------
.../camel-aws2-sqs-kafka-source-connector.adoc | 151 --------------
.../docs/camel-aws2-sts-kafka-sink-connector.adoc | 82 --------
.../camel-aws2-translate-kafka-sink-connector.adoc | 88 --------
.../camel-azure-cosmosdb-kafka-sink-connector.adoc | 95 ---------
...amel-azure-cosmosdb-kafka-source-connector.adoc | 99 ---------
...camel-azure-eventhubs-kafka-sink-connector.adoc | 73 -------
...mel-azure-eventhubs-kafka-source-connector.adoc | 85 --------
...el-azure-storage-blob-kafka-sink-connector.adoc | 104 ----------
...-azure-storage-blob-kafka-source-connector.adoc | 104 ----------
...zure-storage-datalake-kafka-sink-connector.adoc | 116 -----------
...re-storage-datalake-kafka-source-connector.adoc | 132 ------------
...l-azure-storage-queue-kafka-sink-connector.adoc | 79 -------
...azure-storage-queue-kafka-source-connector.adoc | 93 ---------
.../main/docs/camel-bean-kafka-sink-connector.adoc | 61 ------
.../docs/camel-beanstalk-kafka-sink-connector.adoc | 60 ------
.../camel-beanstalk-kafka-source-connector.adoc | 81 --------
.../main/docs/camel-box-kafka-sink-connector.adoc | 88 --------
.../docs/camel-box-kafka-source-connector.adoc | 89 --------
.../docs/camel-braintree-kafka-sink-connector.adoc | 73 -------
.../camel-caffeine-cache-kafka-sink-connector.adoc | 84 --------
...el-caffeine-loadcache-kafka-sink-connector.adoc | 84 --------
.../camel-chatscript-kafka-sink-connector.adoc | 59 ------
.../docs/camel-chunk-kafka-sink-connector.adoc | 65 ------
.../docs/camel-cm-sms-kafka-sink-connector.adoc | 59 ------
.../main/docs/camel-cmis-kafka-sink-connector.adoc | 64 ------
.../docs/camel-cmis-kafka-source-connector.adoc | 66 ------
.../main/docs/camel-coap-kafka-sink-connector.adoc | 64 ------
.../docs/camel-coap-kafka-source-connector.adoc | 67 ------
.../docs/camel-coap+tcp-kafka-sink-connector.adoc | 64 ------
.../camel-coap+tcp-kafka-source-connector.adoc | 67 ------
.../docs/camel-coaps-kafka-sink-connector.adoc | 64 ------
.../docs/camel-coaps-kafka-source-connector.adoc | 67 ------
.../docs/camel-coaps+tcp-kafka-sink-connector.adoc | 64 ------
.../camel-coaps+tcp-kafka-source-connector.adoc | 67 ------
.../docs/camel-cometd-kafka-sink-connector.adoc | 75 -------
.../docs/camel-cometd-kafka-source-connector.adoc | 77 -------
.../docs/camel-cometds-kafka-sink-connector.adoc | 75 -------
.../docs/camel-cometds-kafka-source-connector.adoc | 77 -------
.../docs/camel-consul-kafka-sink-connector.adoc | 99 ---------
.../docs/camel-consul-kafka-source-connector.adoc | 103 ----------
.../camel-controlbus-kafka-sink-connector.adoc | 61 ------
.../docs/camel-corda-kafka-sink-connector.adoc | 62 ------
.../docs/camel-corda-kafka-source-connector.adoc | 76 -------
.../docs/camel-couchbase-kafka-sink-connector.adoc | 73 -------
.../camel-couchbase-kafka-source-connector.adoc | 93 ---------
.../docs/camel-couchdb-kafka-sink-connector.adoc | 61 ------
.../docs/camel-couchdb-kafka-source-connector.adoc | 68 ------
.../main/docs/camel-cql-kafka-sink-connector.adoc | 68 ------
.../docs/camel-cql-kafka-source-connector.adoc | 86 --------
.../docs/camel-cron-kafka-source-connector.adoc | 59 ------
.../docs/camel-crypto-kafka-sink-connector.adoc | 93 ---------
.../main/docs/camel-cxf-kafka-sink-connector.adoc | 90 --------
.../docs/camel-cxf-kafka-source-connector.adoc | 85 --------
.../docs/camel-cxfrs-kafka-sink-connector.adoc | 82 --------
.../docs/camel-cxfrs-kafka-source-connector.adoc | 79 -------
.../camel-dataformat-kafka-sink-connector.adoc | 56 -----
.../docs/camel-direct-kafka-sink-connector.adoc | 61 ------
.../docs/camel-direct-kafka-source-connector.adoc | 58 ------
.../docs/camel-direct-vm-kafka-sink-connector.adoc | 64 ------
.../camel-direct-vm-kafka-source-connector.adoc | 60 ------
.../docs/camel-disruptor-kafka-sink-connector.adoc | 63 ------
.../camel-disruptor-kafka-source-connector.adoc | 65 ------
.../camel-disruptor-vm-kafka-sink-connector.adoc | 63 ------
.../camel-disruptor-vm-kafka-source-connector.adoc | 65 ------
.../main/docs/camel-djl-kafka-sink-connector.adoc | 58 ------
.../main/docs/camel-dns-kafka-sink-connector.adoc | 55 -----
.../docs/camel-docker-kafka-sink-connector.adoc | 90 --------
.../docs/camel-docker-kafka-source-connector.adoc | 92 ---------
.../docs/camel-dozer-kafka-sink-connector.adoc | 61 ------
.../docs/camel-drill-kafka-sink-connector.adoc | 59 ------
.../docs/camel-dropbox-kafka-sink-connector.adoc | 63 ------
.../docs/camel-dropbox-kafka-source-connector.adoc | 65 ------
.../docs/camel-ehcache-kafka-sink-connector.adoc | 75 -------
.../docs/camel-ehcache-kafka-source-connector.adoc | 79 -------
...el-elasticsearch-rest-kafka-sink-connector.adoc | 89 --------
.../docs/camel-elsql-kafka-sink-connector.adoc | 77 -------
.../docs/camel-elsql-kafka-source-connector.adoc | 102 ---------
.../docs/camel-etcd-keys-kafka-sink-connector.adoc | 73 -------
.../camel-etcd-stats-kafka-sink-connector.adoc | 73 -------
.../camel-etcd-stats-kafka-source-connector.adoc | 93 ---------
.../camel-etcd-watch-kafka-source-connector.adoc | 77 -------
.../main/docs/camel-exec-kafka-sink-connector.adoc | 63 ------
.../docs/camel-facebook-kafka-sink-connector.adoc | 181 ----------------
.../camel-facebook-kafka-source-connector.adoc | 183 -----------------
.../main/docs/camel-fhir-kafka-sink-connector.adoc | 104 ----------
.../docs/camel-fhir-kafka-source-connector.adoc | 122 -----------
.../main/docs/camel-file-kafka-sink-connector.adoc | 84 --------
.../docs/camel-file-kafka-source-connector.adoc | 139 -------------
.../camel-file-watch-kafka-source-connector.adoc | 71 -------
.../docs/camel-flatpack-kafka-sink-connector.adoc | 62 ------
.../camel-flatpack-kafka-source-connector.adoc | 80 --------
.../docs/camel-flink-kafka-sink-connector.adoc | 63 ------
.../main/docs/camel-fop-kafka-sink-connector.adoc | 57 ------
.../camel-freemarker-kafka-sink-connector.adoc | 65 ------
.../main/docs/camel-ftp-kafka-sink-connector.adoc | 107 ----------
.../docs/camel-ftp-kafka-source-connector.adoc | 160 ---------------
.../main/docs/camel-ftps-kafka-sink-connector.adoc | 116 -----------
.../docs/camel-ftps-kafka-source-connector.adoc | 169 ---------------
.../docs/camel-ganglia-kafka-sink-connector.adoc | 81 --------
.../docs/camel-geocoder-kafka-sink-connector.adoc | 71 -------
.../main/docs/camel-git-kafka-sink-connector.adoc | 63 ------
.../docs/camel-git-kafka-source-connector.adoc | 59 ------
.../docs/camel-github-kafka-sink-connector.adoc | 69 -------
.../docs/camel-github-kafka-source-connector.adoc | 87 --------
...camel-google-bigquery-kafka-sink-connector.adoc | 62 ------
...l-google-bigquery-sql-kafka-sink-connector.adoc | 59 ------
...camel-google-calendar-kafka-sink-connector.adoc | 77 -------
...mel-google-calendar-kafka-source-connector.adoc | 95 ---------
...gle-calendar-stream-kafka-source-connector.adoc | 105 ----------
.../camel-google-drive-kafka-sink-connector.adoc | 72 -------
.../camel-google-drive-kafka-source-connector.adoc | 90 --------
...amel-google-functions-kafka-sink-connector.adoc | 61 ------
.../camel-google-mail-kafka-sink-connector.adoc | 69 -------
.../camel-google-mail-kafka-source-connector.adoc | 87 --------
...-google-mail-stream-kafka-source-connector.adoc | 93 ---------
.../camel-google-pubsub-kafka-sink-connector.adoc | 70 -------
...camel-google-pubsub-kafka-source-connector.adoc | 67 ------
.../camel-google-sheets-kafka-sink-connector.adoc | 69 -------
...camel-google-sheets-kafka-source-connector.adoc | 89 --------
...oogle-sheets-stream-kafka-source-connector.adoc | 101 ---------
.../camel-google-storage-kafka-sink-connector.adoc | 74 -------
...amel-google-storage-kafka-source-connector.adoc | 98 ---------
.../main/docs/camel-gora-kafka-sink-connector.adoc | 60 ------
.../docs/camel-gora-kafka-source-connector.adoc | 73 -------
.../docs/camel-grape-kafka-sink-connector.adoc | 56 -----
.../docs/camel-graphql-kafka-sink-connector.adoc | 64 ------
.../main/docs/camel-grpc-kafka-sink-connector.adoc | 76 -------
.../docs/camel-grpc-kafka-source-connector.adoc | 79 -------
.../camel-guava-eventbus-kafka-sink-connector.adoc | 58 ------
...amel-guava-eventbus-kafka-source-connector.adoc | 61 ------
...hazelcast-atomicvalue-kafka-sink-connector.adoc | 60 ------
...-hazelcast-instance-kafka-source-connector.adoc | 62 ------
.../camel-hazelcast-list-kafka-sink-connector.adoc | 60 ------
...amel-hazelcast-list-kafka-source-connector.adoc | 62 ------
.../camel-hazelcast-map-kafka-sink-connector.adoc | 60 ------
...camel-hazelcast-map-kafka-source-connector.adoc | 62 ------
...el-hazelcast-multimap-kafka-sink-connector.adoc | 60 ------
...-hazelcast-multimap-kafka-source-connector.adoc | 62 ------
...camel-hazelcast-queue-kafka-sink-connector.adoc | 60 ------
...mel-hazelcast-queue-kafka-source-connector.adoc | 65 ------
...zelcast-replicatedmap-kafka-sink-connector.adoc | 60 ------
...lcast-replicatedmap-kafka-source-connector.adoc | 62 ------
...-hazelcast-ringbuffer-kafka-sink-connector.adoc | 60 ------
.../camel-hazelcast-seda-kafka-sink-connector.adoc | 65 ------
...amel-hazelcast-seda-kafka-source-connector.adoc | 67 ------
.../camel-hazelcast-set-kafka-sink-connector.adoc | 60 ------
...camel-hazelcast-set-kafka-source-connector.adoc | 62 ------
...camel-hazelcast-topic-kafka-sink-connector.adoc | 61 ------
...mel-hazelcast-topic-kafka-source-connector.adoc | 63 ------
.../docs/camel-hbase-kafka-sink-connector.adoc | 65 ------
.../docs/camel-hbase-kafka-source-connector.adoc | 70 -------
.../main/docs/camel-hdfs-kafka-sink-connector.adoc | 81 --------
.../docs/camel-hdfs-kafka-source-connector.adoc | 100 ---------
.../main/docs/camel-http-kafka-sink-connector.adoc | 139 -------------
.../docs/camel-https-kafka-sink-connector.adoc | 143 -------------
...hwcloud-functiongraph-kafka-sink-connector.adoc | 72 -------
.../camel-hwcloud-iam-kafka-sink-connector.adoc | 70 -------
.../camel-hwcloud-smn-kafka-sink-connector.adoc | 72 -------
...camel-iec60870-client-kafka-sink-connector.adoc | 72 -------
...mel-iec60870-client-kafka-source-connector.adoc | 74 -------
...camel-iec60870-server-kafka-sink-connector.adoc | 73 -------
...mel-iec60870-server-kafka-source-connector.adoc | 75 -------
.../camel-ignite-cache-kafka-sink-connector.adoc | 64 ------
.../camel-ignite-cache-kafka-source-connector.adoc | 69 -------
.../camel-ignite-compute-kafka-sink-connector.adoc | 65 ------
...camel-ignite-events-kafka-source-connector.adoc | 64 ------
.../camel-ignite-idgen-kafka-sink-connector.adoc | 63 ------
...amel-ignite-messaging-kafka-sink-connector.adoc | 63 ------
...el-ignite-messaging-kafka-source-connector.adoc | 63 ------
.../camel-ignite-queue-kafka-sink-connector.adoc | 64 ------
.../camel-ignite-set-kafka-sink-connector.adoc | 62 ------
.../main/docs/camel-imap-kafka-sink-connector.adoc | 107 ----------
.../docs/camel-imap-kafka-source-connector.adoc | 146 -------------
.../docs/camel-imaps-kafka-sink-connector.adoc | 107 ----------
.../docs/camel-imaps-kafka-source-connector.adoc | 146 -------------
...l-infinispan-embedded-kafka-sink-connector.adoc | 80 --------
...infinispan-embedded-kafka-source-connector.adoc | 80 --------
.../camel-infinispan-kafka-sink-connector.adoc | 96 ---------
.../camel-infinispan-kafka-source-connector.adoc | 92 ---------
.../docs/camel-influxdb-kafka-sink-connector.adoc | 61 ------
.../main/docs/camel-iota-kafka-sink-connector.adoc | 61 ------
.../main/docs/camel-ipfs-kafka-sink-connector.adoc | 58 ------
.../main/docs/camel-irc-kafka-sink-connector.adoc | 80 --------
.../docs/camel-irc-kafka-source-connector.adoc | 82 --------
.../docs/camel-ironmq-kafka-sink-connector.adoc | 61 ------
.../docs/camel-ironmq-kafka-source-connector.adoc | 83 --------
.../main/docs/camel-jbpm-kafka-sink-connector.adoc | 82 --------
.../docs/camel-jbpm-kafka-source-connector.adoc | 84 --------
.../docs/camel-jcache-kafka-sink-connector.adoc | 75 -------
.../docs/camel-jcache-kafka-source-connector.adoc | 80 --------
.../docs/camel-jclouds-kafka-sink-connector.adoc | 68 ------
.../docs/camel-jclouds-kafka-source-connector.adoc | 62 ------
.../main/docs/camel-jcr-kafka-sink-connector.adoc | 66 ------
.../docs/camel-jcr-kafka-source-connector.adoc | 68 ------
.../main/docs/camel-jdbc-kafka-sink-connector.adoc | 70 -------
.../docs/camel-jetty-kafka-source-connector.adoc | 116 -----------
.../docs/camel-jgroups-kafka-sink-connector.adoc | 58 ------
.../docs/camel-jgroups-kafka-source-connector.adoc | 62 ------
.../camel-jgroups-raft-kafka-sink-connector.adoc | 59 ------
.../camel-jgroups-raft-kafka-source-connector.adoc | 62 ------
.../main/docs/camel-jing-kafka-sink-connector.adoc | 56 -----
.../main/docs/camel-jira-kafka-sink-connector.adoc | 72 -------
.../docs/camel-jira-kafka-source-connector.adoc | 78 -------
.../main/docs/camel-jms-kafka-sink-connector.adoc | 196 ------------------
.../docs/camel-jms-kafka-source-connector.adoc | 196 ------------------
.../docs/camel-jmx-kafka-source-connector.adoc | 83 --------
.../main/docs/camel-jolt-kafka-sink-connector.adoc | 63 ------
.../main/docs/camel-jooq-kafka-sink-connector.adoc | 62 ------
.../docs/camel-jooq-kafka-source-connector.adoc | 78 -------
.../main/docs/camel-jpa-kafka-sink-connector.adoc | 74 -------
.../docs/camel-jpa-kafka-source-connector.adoc | 95 ---------
.../main/docs/camel-jslt-kafka-sink-connector.adoc | 64 ------
.../camel-json-validator-kafka-sink-connector.adoc | 62 ------
.../docs/camel-jsonata-kafka-sink-connector.adoc | 59 ------
.../docs/camel-jt400-kafka-sink-connector.adoc | 69 -------
.../docs/camel-jt400-kafka-source-connector.adoc | 88 --------
.../docs/camel-kafka-kafka-sink-connector.adoc | 188 -----------------
.../docs/camel-kafka-kafka-source-connector.adoc | 178 ----------------
.../docs/camel-kamelet-kafka-sink-connector.adoc | 66 ------
.../docs/camel-kamelet-kafka-source-connector.adoc | 63 ------
.../camel-kamelet-reify-kafka-sink-connector.adoc | 59 ------
...camel-kamelet-reify-kafka-source-connector.adoc | 61 ------
...ubernetes-config-maps-kafka-sink-connector.adoc | 74 -------
...etes-custom-resources-kafka-sink-connector.adoc | 74 -------
...es-custom-resources-kafka-source-connector.adoc | 85 --------
...ubernetes-deployments-kafka-sink-connector.adoc | 74 -------
...ernetes-deployments-kafka-source-connector.adoc | 85 --------
.../camel-kubernetes-hpa-kafka-sink-connector.adoc | 74 -------
...amel-kubernetes-hpa-kafka-source-connector.adoc | 85 --------
.../camel-kubernetes-job-kafka-sink-connector.adoc | 74 -------
...amel-kubernetes-job-kafka-source-connector.adoc | 85 --------
...kubernetes-namespaces-kafka-sink-connector.adoc | 74 -------
...bernetes-namespaces-kafka-source-connector.adoc | 85 --------
...amel-kubernetes-nodes-kafka-sink-connector.adoc | 74 -------
...el-kubernetes-nodes-kafka-source-connector.adoc | 85 --------
...istent-volumes-claims-kafka-sink-connector.adoc | 74 -------
...es-persistent-volumes-kafka-sink-connector.adoc | 74 -------
...camel-kubernetes-pods-kafka-sink-connector.adoc | 74 -------
...mel-kubernetes-pods-kafka-source-connector.adoc | 85 --------
...plication-controllers-kafka-sink-connector.adoc | 74 -------
...ication-controllers-kafka-source-connector.adoc | 85 --------
...netes-resources-quota-kafka-sink-connector.adoc | 74 -------
...el-kubernetes-secrets-kafka-sink-connector.adoc | 74 -------
...etes-service-accounts-kafka-sink-connector.adoc | 74 -------
...l-kubernetes-services-kafka-sink-connector.adoc | 74 -------
...kubernetes-services-kafka-source-connector.adoc | 85 --------
.../main/docs/camel-kudu-kafka-sink-connector.adoc | 58 ------
.../docs/camel-language-kafka-sink-connector.adoc | 62 ------
.../main/docs/camel-ldap-kafka-sink-connector.adoc | 59 ------
.../main/docs/camel-ldif-kafka-sink-connector.adoc | 55 -----
.../main/docs/camel-log-kafka-sink-connector.adoc | 81 --------
.../main/docs/camel-lpr-kafka-sink-connector.adoc | 67 ------
.../docs/camel-lucene-kafka-sink-connector.adoc | 65 ------
.../camel-lumberjack-kafka-source-connector.adoc | 61 ------
.../docs/camel-master-kafka-source-connector.adoc | 60 ------
.../docs/camel-metrics-kafka-sink-connector.adoc | 63 ------
.../camel-micrometer-kafka-sink-connector.adoc | 62 ------
...-microprofile-metrics-kafka-sink-connector.adoc | 68 ------
.../camel-milo-client-kafka-sink-connector.adoc | 105 ----------
.../camel-milo-client-kafka-source-connector.adoc | 107 ----------
.../camel-milo-server-kafka-sink-connector.adoc | 72 -------
.../camel-milo-server-kafka-source-connector.adoc | 74 -------
.../main/docs/camel-mina-kafka-sink-connector.adoc | 99 ---------
.../docs/camel-mina-kafka-source-connector.adoc | 103 ----------
.../docs/camel-minio-kafka-sink-connector.adoc | 92 ---------
.../docs/camel-minio-kafka-source-connector.adoc | 150 --------------
.../main/docs/camel-mllp-kafka-sink-connector.adoc | 73 -------
.../docs/camel-mllp-kafka-source-connector.adoc | 79 -------
.../camel-mongodb-gridfs-kafka-sink-connector.adoc | 60 ------
...amel-mongodb-gridfs-kafka-source-connector.adoc | 68 ------
.../docs/camel-mongodb-kafka-sink-connector.adoc | 78 -------
.../docs/camel-mongodb-kafka-source-connector.adoc | 81 --------
.../main/docs/camel-msv-kafka-sink-connector.adoc | 66 ------
.../docs/camel-mustache-kafka-sink-connector.adoc | 64 ------
.../main/docs/camel-mvel-kafka-sink-connector.adoc | 61 ------
.../camel-mybatis-bean-kafka-sink-connector.adoc | 61 ------
.../docs/camel-mybatis-kafka-sink-connector.adoc | 61 ------
.../docs/camel-mybatis-kafka-source-connector.adoc | 81 --------
.../docs/camel-nagios-kafka-sink-connector.adoc | 66 ------
.../main/docs/camel-nats-kafka-sink-connector.adoc | 78 -------
.../docs/camel-nats-kafka-source-connector.adoc | 82 --------
.../camel-netty-http-kafka-sink-connector.adoc | 164 ---------------
.../camel-netty-http-kafka-source-connector.adoc | 184 -----------------
.../docs/camel-netty-kafka-sink-connector.adoc | 160 ---------------
.../docs/camel-netty-kafka-source-connector.adoc | 172 ----------------
.../docs/camel-nitrite-kafka-sink-connector.adoc | 60 ------
.../docs/camel-nitrite-kafka-source-connector.adoc | 62 ------
.../main/docs/camel-nsq-kafka-sink-connector.adoc | 62 ------
.../docs/camel-nsq-kafka-source-connector.adoc | 71 -------
.../docs/camel-oaipmh-kafka-sink-connector.adoc | 64 ------
.../docs/camel-oaipmh-kafka-source-connector.adoc | 81 --------
.../docs/camel-olingo2-kafka-sink-connector.adoc | 83 --------
.../docs/camel-olingo2-kafka-source-connector.adoc | 103 ----------
.../docs/camel-olingo4-kafka-sink-connector.adoc | 79 -------
.../docs/camel-olingo4-kafka-source-connector.adoc | 99 ---------
...enshift-build-configs-kafka-sink-connector.adoc | 74 -------
...amel-openshift-builds-kafka-sink-connector.adoc | 74 -------
...amel-openstack-cinder-kafka-sink-connector.adoc | 63 ------
...amel-openstack-glance-kafka-sink-connector.adoc | 62 ------
...el-openstack-keystone-kafka-sink-connector.adoc | 62 ------
...mel-openstack-neutron-kafka-sink-connector.adoc | 63 ------
.../camel-openstack-nova-kafka-sink-connector.adoc | 63 ------
...camel-openstack-swift-kafka-sink-connector.adoc | 63 ------
.../camel-optaplanner-kafka-sink-connector.adoc | 60 ------
.../camel-optaplanner-kafka-source-connector.adoc | 60 ------
.../main/docs/camel-paho-kafka-sink-connector.adoc | 110 ----------
.../docs/camel-paho-kafka-source-connector.adoc | 112 ----------
.../camel-paho-mqtt5-kafka-sink-connector.adoc | 110 ----------
.../camel-paho-mqtt5-kafka-source-connector.adoc | 112 ----------
.../main/docs/camel-pdf-kafka-sink-connector.adoc | 63 ------
...pg-replication-slot-kafka-source-connector.adoc | 82 --------
.../docs/camel-pgevent-kafka-sink-connector.adoc | 61 ------
.../docs/camel-pgevent-kafka-source-connector.adoc | 63 ------
...camel-platform-http-kafka-source-connector.adoc | 65 ------
.../main/docs/camel-pop3-kafka-sink-connector.adoc | 107 ----------
.../docs/camel-pop3-kafka-source-connector.adoc | 146 -------------
.../docs/camel-pop3s-kafka-sink-connector.adoc | 107 ----------
.../docs/camel-pop3s-kafka-source-connector.adoc | 146 -------------
.../docs/camel-pubnub-kafka-sink-connector.adoc | 73 -------
.../docs/camel-pubnub-kafka-source-connector.adoc | 75 -------
.../docs/camel-pulsar-kafka-sink-connector.adoc | 87 --------
.../docs/camel-pulsar-kafka-source-connector.adoc | 96 ---------
.../docs/camel-quartz-kafka-source-connector.adoc | 84 --------
.../docs/camel-quickfix-kafka-sink-connector.adoc | 61 ------
.../camel-quickfix-kafka-source-connector.adoc | 63 ------
.../docs/camel-rabbitmq-kafka-sink-connector.adoc | 151 --------------
.../camel-rabbitmq-kafka-source-connector.adoc | 150 --------------
...amel-reactive-streams-kafka-sink-connector.adoc | 62 ------
...el-reactive-streams-kafka-source-connector.adoc | 67 ------
.../camel-rest-api-kafka-source-connector.adoc | 60 ------
.../main/docs/camel-rest-kafka-sink-connector.adoc | 71 -------
.../docs/camel-rest-kafka-source-connector.adoc | 67 ------
.../camel-rest-openapi-kafka-sink-connector.adoc | 69 -------
.../camel-rest-swagger-kafka-sink-connector.adoc | 70 -------
.../docs/camel-resteasy-kafka-sink-connector.adoc | 95 ---------
.../camel-resteasy-kafka-source-connector.adoc | 90 --------
.../docs/camel-rss-kafka-source-connector.adoc | 81 --------
.../main/docs/camel-saga-kafka-sink-connector.adoc | 55 -----
.../camel-salesforce-kafka-sink-connector.adoc | 185 -----------------
.../camel-salesforce-kafka-source-connector.adoc | 174 ----------------
.../camel-sap-netweaver-kafka-sink-connector.adoc | 60 ------
.../camel-scheduler-kafka-source-connector.adoc | 76 -------
.../camel-schematron-kafka-sink-connector.adoc | 58 ------
.../main/docs/camel-scp-kafka-sink-connector.adoc | 80 --------
.../main/docs/camel-seda-kafka-sink-connector.adoc | 69 -------
.../docs/camel-seda-kafka-source-connector.adoc | 67 ------
.../docs/camel-service-kafka-source-connector.adoc | 59 ------
.../camel-servicenow-kafka-sink-connector.adoc | 144 -------------
.../docs/camel-servlet-kafka-source-connector.adoc | 84 --------
.../main/docs/camel-sftp-kafka-sink-connector.adoc | 117 -----------
.../docs/camel-sftp-kafka-source-connector.adoc | 172 ----------------
.../main/docs/camel-sip-kafka-sink-connector.adoc | 93 ---------
.../docs/camel-sip-kafka-source-connector.adoc | 97 ---------
.../main/docs/camel-sips-kafka-sink-connector.adoc | 93 ---------
.../docs/camel-sips-kafka-source-connector.adoc | 97 ---------
.../main/docs/camel-sjms-kafka-sink-connector.adoc | 94 ---------
.../docs/camel-sjms-kafka-source-connector.adoc | 94 ---------
.../docs/camel-sjms2-kafka-sink-connector.adoc | 100 ---------
.../docs/camel-sjms2-kafka-source-connector.adoc | 104 ----------
.../docs/camel-slack-kafka-sink-connector.adoc | 69 -------
.../docs/camel-slack-kafka-source-connector.adoc | 87 --------
.../main/docs/camel-smpp-kafka-sink-connector.adoc | 129 ------------
.../docs/camel-smpp-kafka-source-connector.adoc | 105 ----------
.../docs/camel-smpps-kafka-sink-connector.adoc | 129 ------------
.../docs/camel-smpps-kafka-source-connector.adoc | 105 ----------
.../main/docs/camel-smtp-kafka-sink-connector.adoc | 107 ----------
.../docs/camel-smtp-kafka-source-connector.adoc | 146 -------------
.../docs/camel-smtps-kafka-sink-connector.adoc | 107 ----------
.../docs/camel-smtps-kafka-source-connector.adoc | 146 -------------
.../main/docs/camel-snmp-kafka-sink-connector.adoc | 71 -------
.../docs/camel-snmp-kafka-source-connector.adoc | 90 --------
.../main/docs/camel-solr-kafka-sink-connector.adoc | 73 -------
.../docs/camel-solrCloud-kafka-sink-connector.adoc | 73 -------
.../docs/camel-solrs-kafka-sink-connector.adoc | 73 -------
.../docs/camel-soroush-kafka-sink-connector.adoc | 70 -------
.../docs/camel-soroush-kafka-source-connector.adoc | 69 -------
.../docs/camel-spark-kafka-sink-connector.adoc | 62 ------
.../camel-splunk-hec-kafka-sink-connector.adoc | 65 ------
.../docs/camel-splunk-kafka-sink-connector.adoc | 73 -------
.../docs/camel-splunk-kafka-source-connector.adoc | 91 --------
.../camel-spring-batch-kafka-sink-connector.adoc | 60 ------
.../camel-spring-event-kafka-sink-connector.adoc | 55 -----
.../camel-spring-event-kafka-source-connector.adoc | 57 ------
...el-spring-integration-kafka-sink-connector.adoc | 57 ------
...-spring-integration-kafka-source-connector.adoc | 59 ------
.../camel-spring-jdbc-kafka-sink-connector.adoc | 74 -------
.../camel-spring-ldap-kafka-sink-connector.adoc | 57 ------
...camel-spring-rabbitmq-kafka-sink-connector.adoc | 74 -------
...mel-spring-rabbitmq-kafka-source-connector.adoc | 109 ----------
.../camel-spring-redis-kafka-sink-connector.adoc | 62 ------
.../camel-spring-redis-kafka-source-connector.adoc | 65 ------
.../docs/camel-spring-ws-kafka-sink-connector.adoc | 71 -------
.../camel-spring-ws-kafka-source-connector.adoc | 65 ------
.../main/docs/camel-sql-kafka-sink-connector.adoc | 72 -------
.../docs/camel-sql-kafka-source-connector.adoc | 97 ---------
.../camel-sql-stored-kafka-sink-connector.adoc | 63 ------
.../main/docs/camel-ssh-kafka-sink-connector.adoc | 88 --------
.../docs/camel-ssh-kafka-source-connector.adoc | 108 ----------
.../main/docs/camel-stax-kafka-sink-connector.adoc | 55 -----
.../docs/camel-stitch-kafka-sink-connector.adoc | 70 -------
.../docs/camel-stomp-kafka-sink-connector.adoc | 73 -------
.../docs/camel-stomp-kafka-source-connector.adoc | 75 -------
.../docs/camel-stream-kafka-sink-connector.adoc | 61 ------
.../docs/camel-stream-kafka-source-connector.adoc | 69 -------
...camel-string-template-kafka-sink-connector.adoc | 62 ------
.../main/docs/camel-stub-kafka-sink-connector.adoc | 69 -------
.../docs/camel-stub-kafka-source-connector.adoc | 67 ------
.../docs/camel-telegram-kafka-sink-connector.adoc | 67 ------
.../camel-telegram-kafka-source-connector.adoc | 86 --------
.../docs/camel-thrift-kafka-sink-connector.adoc | 64 ------
.../docs/camel-thrift-kafka-source-connector.adoc | 68 ------
.../main/docs/camel-tika-kafka-sink-connector.adoc | 59 ------
.../docs/camel-timer-kafka-source-connector.adoc | 67 ------
.../docs/camel-twilio-kafka-sink-connector.adoc | 62 ------
.../docs/camel-twilio-kafka-source-connector.adoc | 80 --------
...twitter-directmessage-kafka-sink-connector.adoc | 71 -------
...itter-directmessage-kafka-source-connector.adoc | 103 ----------
.../camel-twitter-search-kafka-sink-connector.adoc | 71 -------
...amel-twitter-search-kafka-source-connector.adoc | 103 ----------
...amel-twitter-timeline-kafka-sink-connector.adoc | 73 -------
...el-twitter-timeline-kafka-source-connector.adoc | 105 ----------
.../docs/camel-undertow-kafka-sink-connector.adoc | 80 --------
.../camel-undertow-kafka-source-connector.adoc | 80 --------
.../docs/camel-validator-kafka-sink-connector.adoc | 65 ------
.../docs/camel-velocity-kafka-sink-connector.adoc | 64 ------
.../camel-vertx-http-kafka-sink-connector.adoc | 93 ---------
.../docs/camel-vertx-kafka-sink-connector.adoc | 62 ------
.../docs/camel-vertx-kafka-source-connector.adoc | 64 ------
.../camel-vertx-kafka-kafka-sink-connector.adoc | 205 ------------------
.../camel-vertx-kafka-kafka-source-connector.adoc | 224 --------------------
...camel-vertx-websocket-kafka-sink-connector.adoc | 65 ------
...mel-vertx-websocket-kafka-source-connector.adoc | 67 ------
.../main/docs/camel-vm-kafka-sink-connector.adoc | 69 -------
.../main/docs/camel-vm-kafka-source-connector.adoc | 67 ------
.../docs/camel-weather-kafka-sink-connector.adoc | 75 -------
.../docs/camel-weather-kafka-source-connector.adoc | 93 ---------
.../docs/camel-web3j-kafka-sink-connector.adoc | 124 -----------
.../docs/camel-web3j-kafka-source-connector.adoc | 80 --------
.../docs/camel-webhook-kafka-source-connector.adoc | 68 ------
...amel-websocket-jsr356-kafka-sink-connector.adoc | 57 ------
...el-websocket-jsr356-kafka-source-connector.adoc | 59 ------
.../docs/camel-websocket-kafka-sink-connector.adoc | 80 --------
.../camel-websocket-kafka-source-connector.adoc | 83 --------
.../main/docs/camel-weka-kafka-sink-connector.adoc | 64 ------
.../docs/camel-wordpress-kafka-sink-connector.adoc | 73 -------
.../camel-wordpress-kafka-source-connector.adoc | 75 -------
.../docs/camel-workday-kafka-sink-connector.adoc | 63 ------
.../docs/camel-xchange-kafka-sink-connector.adoc | 59 ------
.../main/docs/camel-xj-kafka-sink-connector.adoc | 79 -------
...amel-xmlsecurity-sign-kafka-sink-connector.adoc | 108 ----------
...el-xmlsecurity-verify-kafka-sink-connector.adoc | 88 --------
.../main/docs/camel-xmpp-kafka-sink-connector.adoc | 70 -------
.../docs/camel-xmpp-kafka-source-connector.adoc | 74 -------
.../docs/camel-xquery-kafka-sink-connector.adoc | 70 -------
.../docs/camel-xquery-kafka-source-connector.adoc | 88 --------
.../main/docs/camel-xslt-kafka-sink-connector.adoc | 72 -------
.../camel-xslt-saxon-kafka-sink-connector.adoc | 78 -------
.../docs/camel-yammer-kafka-sink-connector.adoc | 66 ------
.../docs/camel-yammer-kafka-source-connector.adoc | 95 ---------
.../docs/camel-zendesk-kafka-sink-connector.adoc | 68 ------
.../docs/camel-zendesk-kafka-source-connector.adoc | 86 --------
.../docs/camel-zookeeper-kafka-sink-connector.adoc | 65 ------
.../camel-zookeeper-kafka-source-connector.adoc | 69 -------
...el-zookeeper-master-kafka-source-connector.adoc | 64 ------
.../camel-activemq-kafka-sink-connector.adoc | 204 ------------------
.../camel-activemq-kafka-source-connector.adoc | 205 ------------------
.../connectors/camel-ahc-kafka-sink-connector.adoc | 78 -------
.../camel-ahc-ws-kafka-sink-connector.adoc | 79 -------
.../camel-ahc-ws-kafka-source-connector.adoc | 79 -------
.../camel-ahc-wss-kafka-sink-connector.adoc | 79 -------
.../camel-ahc-wss-kafka-source-connector.adoc | 79 -------
.../camel-amqp-kafka-sink-connector.adoc | 201 ------------------
.../camel-amqp-kafka-source-connector.adoc | 201 ------------------
.../camel-arangodb-kafka-sink-connector.adoc | 78 -------
.../connectors/camel-as2-kafka-sink-connector.adoc | 88 --------
.../camel-as2-kafka-source-connector.adoc | 89 --------
.../camel-asterisk-kafka-sink-connector.adoc | 63 ------
.../camel-asterisk-kafka-source-connector.adoc | 64 ------
.../camel-atlasmap-kafka-sink-connector.adoc | 66 ------
.../camel-atmos-kafka-sink-connector.adoc | 72 -------
.../camel-atmos-kafka-source-connector.adoc | 74 -------
...-atmosphere-websocket-kafka-sink-connector.adoc | 71 -------
...tmosphere-websocket-kafka-source-connector.adoc | 90 --------
.../camel-atom-kafka-source-connector.adoc | 85 --------
.../camel-atomix-map-kafka-sink-connector.adoc | 88 --------
.../camel-atomix-map-kafka-source-connector.adoc | 90 --------
...amel-atomix-messaging-kafka-sink-connector.adoc | 90 --------
...el-atomix-messaging-kafka-source-connector.adoc | 92 ---------
...camel-atomix-multimap-kafka-sink-connector.adoc | 88 --------
.../camel-atomix-queue-kafka-sink-connector.adoc | 84 --------
.../camel-atomix-queue-kafka-source-connector.adoc | 86 --------
.../camel-atomix-set-kafka-sink-connector.adoc | 86 --------
.../camel-atomix-set-kafka-source-connector.adoc | 88 --------
.../camel-atomix-value-kafka-sink-connector.adoc | 86 --------
.../camel-atomix-value-kafka-source-connector.adoc | 88 --------
.../camel-avro-kafka-sink-connector.adoc | 75 -------
.../camel-avro-kafka-source-connector.adoc | 77 -------
...l-aws-secrets-manager-kafka-sink-connector.adoc | 88 --------
.../camel-aws2-athena-kafka-sink-connector.adoc | 114 -----------
.../camel-aws2-cw-kafka-sink-connector.adoc | 90 --------
.../camel-aws2-ddb-kafka-sink-connector.adoc | 96 ---------
...amel-aws2-ddbstream-kafka-source-connector.adoc | 106 ----------
.../camel-aws2-ec2-kafka-sink-connector.adoc | 86 --------
.../camel-aws2-ecs-kafka-sink-connector.adoc | 86 --------
.../camel-aws2-eks-kafka-sink-connector.adoc | 86 --------
...amel-aws2-eventbridge-kafka-sink-connector.adoc | 88 --------
.../camel-aws2-iam-kafka-sink-connector.adoc | 86 --------
...aws2-kinesis-firehose-kafka-sink-connector.adoc | 86 --------
.../camel-aws2-kinesis-kafka-sink-connector.adoc | 91 --------
.../camel-aws2-kinesis-kafka-source-connector.adoc | 119 -----------
.../camel-aws2-kms-kafka-sink-connector.adoc | 86 --------
.../camel-aws2-lambda-kafka-sink-connector.adoc | 86 --------
.../camel-aws2-mq-kafka-sink-connector.adoc | 86 --------
.../camel-aws2-msk-kafka-sink-connector.adoc | 86 --------
.../camel-aws2-s3-kafka-sink-connector.adoc | 151 --------------
.../camel-aws2-s3-kafka-source-connector.adoc | 167 ---------------
.../camel-aws2-ses-kafka-sink-connector.adoc | 90 --------
.../camel-aws2-sns-kafka-sink-connector.adoc | 103 ----------
.../camel-aws2-sqs-kafka-sink-connector.adoc | 122 -----------
.../camel-aws2-sqs-kafka-source-connector.adoc | 155 --------------
.../camel-aws2-sts-kafka-sink-connector.adoc | 86 --------
.../camel-aws2-translate-kafka-sink-connector.adoc | 92 ---------
.../camel-azure-cosmosdb-kafka-sink-connector.adoc | 99 ---------
...amel-azure-cosmosdb-kafka-source-connector.adoc | 103 ----------
...camel-azure-eventhubs-kafka-sink-connector.adoc | 77 -------
...mel-azure-eventhubs-kafka-source-connector.adoc | 89 --------
...el-azure-storage-blob-kafka-sink-connector.adoc | 108 ----------
...-azure-storage-blob-kafka-source-connector.adoc | 108 ----------
...zure-storage-datalake-kafka-sink-connector.adoc | 120 -----------
...re-storage-datalake-kafka-source-connector.adoc | 136 ------------
...l-azure-storage-queue-kafka-sink-connector.adoc | 83 --------
...azure-storage-queue-kafka-source-connector.adoc | 97 ---------
.../camel-bean-kafka-sink-connector.adoc | 65 ------
.../camel-beanstalk-kafka-sink-connector.adoc | 64 ------
.../camel-beanstalk-kafka-source-connector.adoc | 85 --------
.../connectors/camel-box-kafka-sink-connector.adoc | 92 ---------
.../camel-box-kafka-source-connector.adoc | 93 ---------
.../camel-braintree-kafka-sink-connector.adoc | 73 -------
.../camel-caffeine-cache-kafka-sink-connector.adoc | 88 --------
...el-caffeine-loadcache-kafka-sink-connector.adoc | 88 --------
.../camel-chatscript-kafka-sink-connector.adoc | 63 ------
.../camel-chunk-kafka-sink-connector.adoc | 69 -------
.../camel-cm-sms-kafka-sink-connector.adoc | 63 ------
.../camel-cmis-kafka-sink-connector.adoc | 68 ------
.../camel-cmis-kafka-source-connector.adoc | 70 -------
.../camel-coap+tcp-kafka-sink-connector.adoc | 68 ------
.../camel-coap+tcp-kafka-source-connector.adoc | 71 -------
.../camel-coap-kafka-sink-connector.adoc | 68 ------
.../camel-coap-kafka-source-connector.adoc | 71 -------
.../camel-coaps+tcp-kafka-sink-connector.adoc | 68 ------
.../camel-coaps+tcp-kafka-source-connector.adoc | 71 -------
.../camel-coaps-kafka-sink-connector.adoc | 68 ------
.../camel-coaps-kafka-source-connector.adoc | 71 -------
.../camel-cometd-kafka-sink-connector.adoc | 79 -------
.../camel-cometd-kafka-source-connector.adoc | 81 --------
.../camel-cometds-kafka-sink-connector.adoc | 79 -------
.../camel-cometds-kafka-source-connector.adoc | 81 --------
.../camel-consul-kafka-sink-connector.adoc | 103 ----------
.../camel-consul-kafka-source-connector.adoc | 107 ----------
.../camel-controlbus-kafka-sink-connector.adoc | 65 ------
.../camel-corda-kafka-sink-connector.adoc | 66 ------
.../camel-corda-kafka-source-connector.adoc | 80 --------
.../camel-couchbase-kafka-sink-connector.adoc | 77 -------
.../camel-couchbase-kafka-source-connector.adoc | 97 ---------
.../camel-couchdb-kafka-sink-connector.adoc | 65 ------
.../camel-couchdb-kafka-source-connector.adoc | 72 -------
.../connectors/camel-cql-kafka-sink-connector.adoc | 72 -------
.../camel-cql-kafka-source-connector.adoc | 90 --------
.../camel-cron-kafka-source-connector.adoc | 63 ------
.../camel-crypto-kafka-sink-connector.adoc | 97 ---------
.../connectors/camel-cxf-kafka-sink-connector.adoc | 94 ---------
.../camel-cxf-kafka-source-connector.adoc | 89 --------
.../camel-cxfrs-kafka-sink-connector.adoc | 86 --------
.../camel-cxfrs-kafka-source-connector.adoc | 83 --------
.../camel-dataformat-kafka-sink-connector.adoc | 60 ------
.../camel-direct-kafka-sink-connector.adoc | 65 ------
.../camel-direct-kafka-source-connector.adoc | 62 ------
.../camel-direct-vm-kafka-sink-connector.adoc | 68 ------
.../camel-direct-vm-kafka-source-connector.adoc | 64 ------
.../camel-disruptor-kafka-sink-connector.adoc | 67 ------
.../camel-disruptor-kafka-source-connector.adoc | 69 -------
.../camel-disruptor-vm-kafka-sink-connector.adoc | 67 ------
.../camel-disruptor-vm-kafka-source-connector.adoc | 69 -------
.../connectors/camel-djl-kafka-sink-connector.adoc | 62 ------
.../connectors/camel-dns-kafka-sink-connector.adoc | 59 ------
.../camel-docker-kafka-sink-connector.adoc | 94 ---------
.../camel-docker-kafka-source-connector.adoc | 96 ---------
.../camel-dozer-kafka-sink-connector.adoc | 65 ------
.../camel-drill-kafka-sink-connector.adoc | 63 ------
.../camel-dropbox-kafka-sink-connector.adoc | 67 ------
.../camel-dropbox-kafka-source-connector.adoc | 69 -------
.../camel-ehcache-kafka-sink-connector.adoc | 79 -------
.../camel-ehcache-kafka-source-connector.adoc | 83 --------
...el-elasticsearch-rest-kafka-sink-connector.adoc | 93 ---------
.../camel-elsql-kafka-sink-connector.adoc | 81 --------
.../camel-elsql-kafka-source-connector.adoc | 106 ----------
.../camel-etcd-keys-kafka-sink-connector.adoc | 77 -------
.../camel-etcd-stats-kafka-sink-connector.adoc | 77 -------
.../camel-etcd-stats-kafka-source-connector.adoc | 97 ---------
.../camel-etcd-watch-kafka-source-connector.adoc | 81 --------
.../camel-exec-kafka-sink-connector.adoc | 67 ------
.../camel-facebook-kafka-sink-connector.adoc | 185 -----------------
.../camel-facebook-kafka-source-connector.adoc | 187 -----------------
.../camel-fhir-kafka-sink-connector.adoc | 108 ----------
.../camel-fhir-kafka-source-connector.adoc | 126 ------------
.../camel-file-kafka-sink-connector.adoc | 88 --------
.../camel-file-kafka-source-connector.adoc | 143 -------------
.../camel-file-watch-kafka-source-connector.adoc | 75 -------
.../camel-flatpack-kafka-sink-connector.adoc | 66 ------
.../camel-flatpack-kafka-source-connector.adoc | 84 --------
.../camel-flink-kafka-sink-connector.adoc | 67 ------
.../connectors/camel-fop-kafka-sink-connector.adoc | 61 ------
.../camel-freemarker-kafka-sink-connector.adoc | 69 -------
.../connectors/camel-ftp-kafka-sink-connector.adoc | 111 ----------
.../camel-ftp-kafka-source-connector.adoc | 164 ---------------
.../camel-ftps-kafka-sink-connector.adoc | 120 -----------
.../camel-ftps-kafka-source-connector.adoc | 173 ----------------
.../camel-ganglia-kafka-sink-connector.adoc | 85 --------
.../camel-geocoder-kafka-sink-connector.adoc | 75 -------
.../connectors/camel-git-kafka-sink-connector.adoc | 67 ------
.../camel-git-kafka-source-connector.adoc | 63 ------
.../camel-github-kafka-sink-connector.adoc | 73 -------
.../camel-github-kafka-source-connector.adoc | 91 --------
...camel-google-bigquery-kafka-sink-connector.adoc | 66 ------
...l-google-bigquery-sql-kafka-sink-connector.adoc | 63 ------
...camel-google-calendar-kafka-sink-connector.adoc | 81 --------
...mel-google-calendar-kafka-source-connector.adoc | 99 ---------
...gle-calendar-stream-kafka-source-connector.adoc | 109 ----------
.../camel-google-drive-kafka-sink-connector.adoc | 76 -------
.../camel-google-drive-kafka-source-connector.adoc | 94 ---------
...amel-google-functions-kafka-sink-connector.adoc | 65 ------
.../camel-google-mail-kafka-sink-connector.adoc | 73 -------
.../camel-google-mail-kafka-source-connector.adoc | 91 --------
...-google-mail-stream-kafka-source-connector.adoc | 97 ---------
.../camel-google-pubsub-kafka-sink-connector.adoc | 74 -------
...camel-google-pubsub-kafka-source-connector.adoc | 71 -------
.../camel-google-sheets-kafka-sink-connector.adoc | 73 -------
...camel-google-sheets-kafka-source-connector.adoc | 93 ---------
...oogle-sheets-stream-kafka-source-connector.adoc | 105 ----------
.../camel-google-storage-kafka-sink-connector.adoc | 74 -------
...amel-google-storage-kafka-source-connector.adoc | 98 ---------
.../camel-gora-kafka-sink-connector.adoc | 64 ------
.../camel-gora-kafka-source-connector.adoc | 77 -------
.../camel-grape-kafka-sink-connector.adoc | 60 ------
.../camel-graphql-kafka-sink-connector.adoc | 68 ------
.../camel-grpc-kafka-sink-connector.adoc | 80 --------
.../camel-grpc-kafka-source-connector.adoc | 83 --------
.../camel-guava-eventbus-kafka-sink-connector.adoc | 62 ------
...amel-guava-eventbus-kafka-source-connector.adoc | 65 ------
...hazelcast-atomicvalue-kafka-sink-connector.adoc | 64 ------
...-hazelcast-instance-kafka-source-connector.adoc | 66 ------
.../camel-hazelcast-list-kafka-sink-connector.adoc | 64 ------
...amel-hazelcast-list-kafka-source-connector.adoc | 66 ------
.../camel-hazelcast-map-kafka-sink-connector.adoc | 64 ------
...camel-hazelcast-map-kafka-source-connector.adoc | 66 ------
...el-hazelcast-multimap-kafka-sink-connector.adoc | 64 ------
...-hazelcast-multimap-kafka-source-connector.adoc | 66 ------
...camel-hazelcast-queue-kafka-sink-connector.adoc | 64 ------
...mel-hazelcast-queue-kafka-source-connector.adoc | 69 -------
...zelcast-replicatedmap-kafka-sink-connector.adoc | 64 ------
...lcast-replicatedmap-kafka-source-connector.adoc | 66 ------
...-hazelcast-ringbuffer-kafka-sink-connector.adoc | 64 ------
.../camel-hazelcast-seda-kafka-sink-connector.adoc | 69 -------
...amel-hazelcast-seda-kafka-source-connector.adoc | 71 -------
.../camel-hazelcast-set-kafka-sink-connector.adoc | 64 ------
...camel-hazelcast-set-kafka-source-connector.adoc | 66 ------
...camel-hazelcast-topic-kafka-sink-connector.adoc | 65 ------
...mel-hazelcast-topic-kafka-source-connector.adoc | 67 ------
.../camel-hbase-kafka-sink-connector.adoc | 69 -------
.../camel-hbase-kafka-source-connector.adoc | 74 -------
.../camel-hdfs-kafka-sink-connector.adoc | 85 --------
.../camel-hdfs-kafka-source-connector.adoc | 104 ----------
.../camel-http-kafka-sink-connector.adoc | 143 -------------
.../camel-https-kafka-sink-connector.adoc | 143 -------------
...hwcloud-functiongraph-kafka-sink-connector.adoc | 72 -------
.../camel-hwcloud-iam-kafka-sink-connector.adoc | 70 -------
.../camel-hwcloud-smn-kafka-sink-connector.adoc | 72 -------
...camel-iec60870-client-kafka-sink-connector.adoc | 76 -------
...mel-iec60870-client-kafka-source-connector.adoc | 78 -------
...camel-iec60870-server-kafka-sink-connector.adoc | 77 -------
...mel-iec60870-server-kafka-source-connector.adoc | 79 -------
.../camel-ignite-cache-kafka-sink-connector.adoc | 68 ------
.../camel-ignite-cache-kafka-source-connector.adoc | 73 -------
.../camel-ignite-compute-kafka-sink-connector.adoc | 69 -------
...camel-ignite-events-kafka-source-connector.adoc | 68 ------
.../camel-ignite-idgen-kafka-sink-connector.adoc | 67 ------
...amel-ignite-messaging-kafka-sink-connector.adoc | 67 ------
...el-ignite-messaging-kafka-source-connector.adoc | 67 ------
.../camel-ignite-queue-kafka-sink-connector.adoc | 68 ------
.../camel-ignite-set-kafka-sink-connector.adoc | 66 ------
.../camel-imap-kafka-sink-connector.adoc | 111 ----------
.../camel-imap-kafka-source-connector.adoc | 150 --------------
.../camel-imaps-kafka-sink-connector.adoc | 111 ----------
.../camel-imaps-kafka-source-connector.adoc | 150 --------------
...l-infinispan-embedded-kafka-sink-connector.adoc | 84 --------
...infinispan-embedded-kafka-source-connector.adoc | 84 --------
.../camel-infinispan-kafka-sink-connector.adoc | 100 ---------
.../camel-infinispan-kafka-source-connector.adoc | 96 ---------
.../camel-influxdb-kafka-sink-connector.adoc | 65 ------
.../camel-iota-kafka-sink-connector.adoc | 65 ------
.../camel-ipfs-kafka-sink-connector.adoc | 62 ------
.../connectors/camel-irc-kafka-sink-connector.adoc | 84 --------
.../camel-irc-kafka-source-connector.adoc | 86 --------
.../camel-ironmq-kafka-sink-connector.adoc | 65 ------
.../camel-ironmq-kafka-source-connector.adoc | 87 --------
.../camel-jbpm-kafka-sink-connector.adoc | 86 --------
.../camel-jbpm-kafka-source-connector.adoc | 88 --------
.../camel-jcache-kafka-sink-connector.adoc | 79 -------
.../camel-jcache-kafka-source-connector.adoc | 84 --------
.../camel-jclouds-kafka-sink-connector.adoc | 72 -------
.../camel-jclouds-kafka-source-connector.adoc | 66 ------
.../connectors/camel-jcr-kafka-sink-connector.adoc | 70 -------
.../camel-jcr-kafka-source-connector.adoc | 72 -------
.../camel-jdbc-kafka-sink-connector.adoc | 74 -------
.../camel-jetty-kafka-source-connector.adoc | 120 -----------
.../camel-jgroups-kafka-sink-connector.adoc | 62 ------
.../camel-jgroups-kafka-source-connector.adoc | 66 ------
.../camel-jgroups-raft-kafka-sink-connector.adoc | 63 ------
.../camel-jgroups-raft-kafka-source-connector.adoc | 66 ------
.../camel-jing-kafka-sink-connector.adoc | 60 ------
.../camel-jira-kafka-sink-connector.adoc | 76 -------
.../camel-jira-kafka-source-connector.adoc | 82 --------
.../connectors/camel-jms-kafka-sink-connector.adoc | 200 ------------------
.../camel-jms-kafka-source-connector.adoc | 200 ------------------
.../camel-jmx-kafka-source-connector.adoc | 87 --------
.../camel-jolt-kafka-sink-connector.adoc | 67 ------
.../camel-jooq-kafka-sink-connector.adoc | 66 ------
.../camel-jooq-kafka-source-connector.adoc | 82 --------
.../connectors/camel-jpa-kafka-sink-connector.adoc | 78 -------
.../camel-jpa-kafka-source-connector.adoc | 99 ---------
.../camel-jslt-kafka-sink-connector.adoc | 68 ------
.../camel-json-validator-kafka-sink-connector.adoc | 66 ------
.../camel-jsonata-kafka-sink-connector.adoc | 63 ------
.../camel-jt400-kafka-sink-connector.adoc | 73 -------
.../camel-jt400-kafka-source-connector.adoc | 92 ---------
.../camel-kafka-kafka-sink-connector.adoc | 192 -----------------
.../camel-kafka-kafka-source-connector.adoc | 182 ----------------
.../camel-kamelet-kafka-sink-connector.adoc | 70 -------
.../camel-kamelet-kafka-source-connector.adoc | 67 ------
.../camel-kamelet-reify-kafka-sink-connector.adoc | 59 ------
...camel-kamelet-reify-kafka-source-connector.adoc | 61 ------
...ubernetes-config-maps-kafka-sink-connector.adoc | 78 -------
...etes-custom-resources-kafka-sink-connector.adoc | 78 -------
...es-custom-resources-kafka-source-connector.adoc | 89 --------
...ubernetes-deployments-kafka-sink-connector.adoc | 78 -------
...ernetes-deployments-kafka-source-connector.adoc | 89 --------
.../camel-kubernetes-hpa-kafka-sink-connector.adoc | 78 -------
...amel-kubernetes-hpa-kafka-source-connector.adoc | 89 --------
.../camel-kubernetes-job-kafka-sink-connector.adoc | 78 -------
...amel-kubernetes-job-kafka-source-connector.adoc | 89 --------
...kubernetes-namespaces-kafka-sink-connector.adoc | 78 -------
...bernetes-namespaces-kafka-source-connector.adoc | 89 --------
...amel-kubernetes-nodes-kafka-sink-connector.adoc | 78 -------
...el-kubernetes-nodes-kafka-source-connector.adoc | 89 --------
...istent-volumes-claims-kafka-sink-connector.adoc | 78 -------
...es-persistent-volumes-kafka-sink-connector.adoc | 78 -------
...camel-kubernetes-pods-kafka-sink-connector.adoc | 78 -------
...mel-kubernetes-pods-kafka-source-connector.adoc | 89 --------
...plication-controllers-kafka-sink-connector.adoc | 78 -------
...ication-controllers-kafka-source-connector.adoc | 89 --------
...netes-resources-quota-kafka-sink-connector.adoc | 78 -------
...el-kubernetes-secrets-kafka-sink-connector.adoc | 78 -------
...etes-service-accounts-kafka-sink-connector.adoc | 78 -------
...l-kubernetes-services-kafka-sink-connector.adoc | 78 -------
...kubernetes-services-kafka-source-connector.adoc | 89 --------
.../camel-kudu-kafka-sink-connector.adoc | 62 ------
.../camel-language-kafka-sink-connector.adoc | 66 ------
.../camel-ldap-kafka-sink-connector.adoc | 63 ------
.../camel-ldif-kafka-sink-connector.adoc | 59 ------
.../connectors/camel-log-kafka-sink-connector.adoc | 85 --------
.../connectors/camel-lpr-kafka-sink-connector.adoc | 71 -------
.../camel-lucene-kafka-sink-connector.adoc | 69 -------
.../camel-lumberjack-kafka-source-connector.adoc | 65 ------
.../camel-master-kafka-source-connector.adoc | 64 ------
.../camel-metrics-kafka-sink-connector.adoc | 67 ------
.../camel-micrometer-kafka-sink-connector.adoc | 66 ------
...-microprofile-metrics-kafka-sink-connector.adoc | 72 -------
.../camel-milo-client-kafka-sink-connector.adoc | 109 ----------
.../camel-milo-client-kafka-source-connector.adoc | 111 ----------
.../camel-milo-server-kafka-sink-connector.adoc | 76 -------
.../camel-milo-server-kafka-source-connector.adoc | 78 -------
.../camel-mina-kafka-sink-connector.adoc | 103 ----------
.../camel-mina-kafka-source-connector.adoc | 107 ----------
.../camel-minio-kafka-sink-connector.adoc | 96 ---------
.../camel-minio-kafka-source-connector.adoc | 154 --------------
.../camel-mllp-kafka-sink-connector.adoc | 77 -------
.../camel-mllp-kafka-source-connector.adoc | 83 --------
.../camel-mongodb-gridfs-kafka-sink-connector.adoc | 64 ------
...amel-mongodb-gridfs-kafka-source-connector.adoc | 72 -------
.../camel-mongodb-kafka-sink-connector.adoc | 75 -------
.../camel-mongodb-kafka-source-connector.adoc | 85 --------
.../connectors/camel-msv-kafka-sink-connector.adoc | 70 -------
.../camel-mustache-kafka-sink-connector.adoc | 68 ------
.../camel-mvel-kafka-sink-connector.adoc | 65 ------
.../camel-mybatis-bean-kafka-sink-connector.adoc | 65 ------
.../camel-mybatis-kafka-sink-connector.adoc | 65 ------
.../camel-mybatis-kafka-source-connector.adoc | 85 --------
.../camel-nagios-kafka-sink-connector.adoc | 70 -------
.../camel-nats-kafka-sink-connector.adoc | 82 --------
.../camel-nats-kafka-source-connector.adoc | 86 --------
.../camel-netty-http-kafka-sink-connector.adoc | 168 ---------------
.../camel-netty-http-kafka-source-connector.adoc | 188 -----------------
.../camel-netty-kafka-sink-connector.adoc | 164 ---------------
.../camel-netty-kafka-source-connector.adoc | 176 ----------------
.../camel-nitrite-kafka-sink-connector.adoc | 64 ------
.../camel-nitrite-kafka-source-connector.adoc | 66 ------
.../connectors/camel-nsq-kafka-sink-connector.adoc | 66 ------
.../camel-nsq-kafka-source-connector.adoc | 75 -------
.../camel-oaipmh-kafka-sink-connector.adoc | 68 ------
.../camel-oaipmh-kafka-source-connector.adoc | 85 --------
.../camel-olingo2-kafka-sink-connector.adoc | 87 --------
.../camel-olingo2-kafka-source-connector.adoc | 107 ----------
.../camel-olingo4-kafka-sink-connector.adoc | 83 --------
.../camel-olingo4-kafka-source-connector.adoc | 103 ----------
...enshift-build-configs-kafka-sink-connector.adoc | 78 -------
...amel-openshift-builds-kafka-sink-connector.adoc | 78 -------
...amel-openstack-cinder-kafka-sink-connector.adoc | 67 ------
...amel-openstack-glance-kafka-sink-connector.adoc | 66 ------
...el-openstack-keystone-kafka-sink-connector.adoc | 66 ------
...mel-openstack-neutron-kafka-sink-connector.adoc | 67 ------
.../camel-openstack-nova-kafka-sink-connector.adoc | 67 ------
...camel-openstack-swift-kafka-sink-connector.adoc | 67 ------
.../camel-optaplanner-kafka-sink-connector.adoc | 64 ------
.../camel-optaplanner-kafka-source-connector.adoc | 64 ------
.../camel-paho-kafka-sink-connector.adoc | 114 -----------
.../camel-paho-kafka-source-connector.adoc | 116 -----------
.../camel-paho-mqtt5-kafka-sink-connector.adoc | 114 -----------
.../camel-paho-mqtt5-kafka-source-connector.adoc | 116 -----------
.../connectors/camel-pdf-kafka-sink-connector.adoc | 67 ------
...pg-replication-slot-kafka-source-connector.adoc | 86 --------
.../camel-pgevent-kafka-sink-connector.adoc | 65 ------
.../camel-pgevent-kafka-source-connector.adoc | 67 ------
...camel-platform-http-kafka-source-connector.adoc | 69 -------
.../camel-pop3-kafka-sink-connector.adoc | 111 ----------
.../camel-pop3-kafka-source-connector.adoc | 150 --------------
.../camel-pop3s-kafka-sink-connector.adoc | 111 ----------
.../camel-pop3s-kafka-source-connector.adoc | 150 --------------
.../camel-pubnub-kafka-sink-connector.adoc | 77 -------
.../camel-pubnub-kafka-source-connector.adoc | 79 -------
.../camel-pulsar-kafka-sink-connector.adoc | 91 --------
.../camel-pulsar-kafka-source-connector.adoc | 100 ---------
.../camel-quartz-kafka-source-connector.adoc | 88 --------
.../camel-quickfix-kafka-sink-connector.adoc | 65 ------
.../camel-quickfix-kafka-source-connector.adoc | 67 ------
.../camel-rabbitmq-kafka-sink-connector.adoc | 155 --------------
.../camel-rabbitmq-kafka-source-connector.adoc | 154 --------------
...amel-reactive-streams-kafka-sink-connector.adoc | 66 ------
...el-reactive-streams-kafka-source-connector.adoc | 71 -------
.../camel-rest-api-kafka-source-connector.adoc | 64 ------
.../camel-rest-kafka-sink-connector.adoc | 75 -------
.../camel-rest-kafka-source-connector.adoc | 71 -------
.../camel-rest-openapi-kafka-sink-connector.adoc | 73 -------
.../camel-rest-swagger-kafka-sink-connector.adoc | 74 -------
.../camel-resteasy-kafka-sink-connector.adoc | 99 ---------
.../camel-resteasy-kafka-source-connector.adoc | 94 ---------
.../camel-rss-kafka-source-connector.adoc | 85 --------
.../camel-saga-kafka-sink-connector.adoc | 59 ------
.../camel-salesforce-kafka-sink-connector.adoc | 189 -----------------
.../camel-salesforce-kafka-source-connector.adoc | 178 ----------------
.../camel-sap-netweaver-kafka-sink-connector.adoc | 64 ------
.../camel-scheduler-kafka-source-connector.adoc | 80 --------
.../camel-schematron-kafka-sink-connector.adoc | 62 ------
.../connectors/camel-scp-kafka-sink-connector.adoc | 84 --------
.../camel-seda-kafka-sink-connector.adoc | 73 -------
.../camel-seda-kafka-source-connector.adoc | 71 -------
.../camel-service-kafka-source-connector.adoc | 63 ------
.../camel-servicenow-kafka-sink-connector.adoc | 148 -------------
.../camel-servlet-kafka-source-connector.adoc | 88 --------
.../camel-sftp-kafka-sink-connector.adoc | 121 -----------
.../camel-sftp-kafka-source-connector.adoc | 176 ----------------
.../connectors/camel-sip-kafka-sink-connector.adoc | 97 ---------
.../camel-sip-kafka-source-connector.adoc | 101 ---------
.../camel-sips-kafka-sink-connector.adoc | 97 ---------
.../camel-sips-kafka-source-connector.adoc | 101 ---------
.../camel-sjms-kafka-sink-connector.adoc | 98 ---------
.../camel-sjms-kafka-source-connector.adoc | 98 ---------
.../camel-sjms2-kafka-sink-connector.adoc | 98 ---------
.../camel-sjms2-kafka-source-connector.adoc | 101 ---------
.../camel-slack-kafka-sink-connector.adoc | 73 -------
.../camel-slack-kafka-source-connector.adoc | 91 --------
.../camel-smpp-kafka-sink-connector.adoc | 133 ------------
.../camel-smpp-kafka-source-connector.adoc | 109 ----------
.../camel-smpps-kafka-sink-connector.adoc | 133 ------------
.../camel-smpps-kafka-source-connector.adoc | 109 ----------
.../camel-smtp-kafka-sink-connector.adoc | 111 ----------
.../camel-smtp-kafka-source-connector.adoc | 150 --------------
.../camel-smtps-kafka-sink-connector.adoc | 111 ----------
.../camel-smtps-kafka-source-connector.adoc | 150 --------------
.../camel-snmp-kafka-sink-connector.adoc | 75 -------
.../camel-snmp-kafka-source-connector.adoc | 94 ---------
.../camel-solr-kafka-sink-connector.adoc | 77 -------
.../camel-solrCloud-kafka-sink-connector.adoc | 77 -------
.../camel-solrs-kafka-sink-connector.adoc | 77 -------
.../camel-soroush-kafka-sink-connector.adoc | 74 -------
.../camel-soroush-kafka-source-connector.adoc | 73 -------
.../camel-spark-kafka-sink-connector.adoc | 66 ------
.../camel-splunk-hec-kafka-sink-connector.adoc | 69 -------
.../camel-splunk-kafka-sink-connector.adoc | 77 -------
.../camel-splunk-kafka-source-connector.adoc | 95 ---------
.../camel-spring-batch-kafka-sink-connector.adoc | 64 ------
.../camel-spring-event-kafka-sink-connector.adoc | 59 ------
.../camel-spring-event-kafka-source-connector.adoc | 61 ------
...el-spring-integration-kafka-sink-connector.adoc | 61 ------
...-spring-integration-kafka-source-connector.adoc | 63 ------
.../camel-spring-jdbc-kafka-sink-connector.adoc | 74 -------
.../camel-spring-ldap-kafka-sink-connector.adoc | 61 ------
...camel-spring-rabbitmq-kafka-sink-connector.adoc | 78 -------
...mel-spring-rabbitmq-kafka-source-connector.adoc | 113 ----------
.../camel-spring-redis-kafka-sink-connector.adoc | 66 ------
.../camel-spring-redis-kafka-source-connector.adoc | 69 -------
.../camel-spring-ws-kafka-sink-connector.adoc | 75 -------
.../camel-spring-ws-kafka-source-connector.adoc | 69 -------
.../connectors/camel-sql-kafka-sink-connector.adoc | 76 -------
.../camel-sql-kafka-source-connector.adoc | 101 ---------
.../camel-sql-stored-kafka-sink-connector.adoc | 67 ------
.../connectors/camel-ssh-kafka-sink-connector.adoc | 92 ---------
.../camel-ssh-kafka-source-connector.adoc | 112 ----------
.../camel-stax-kafka-sink-connector.adoc | 59 ------
.../camel-stitch-kafka-sink-connector.adoc | 74 -------
.../camel-stomp-kafka-sink-connector.adoc | 77 -------
.../camel-stomp-kafka-source-connector.adoc | 79 -------
.../camel-stream-kafka-sink-connector.adoc | 65 ------
.../camel-stream-kafka-source-connector.adoc | 73 -------
...camel-string-template-kafka-sink-connector.adoc | 66 ------
.../camel-stub-kafka-sink-connector.adoc | 73 -------
.../camel-stub-kafka-source-connector.adoc | 71 -------
.../camel-syslog-kafka-sink-connector.adoc | 27 ---
.../camel-syslog-kafka-source-connector.adoc | 27 ---
.../camel-telegram-kafka-sink-connector.adoc | 71 -------
.../camel-telegram-kafka-source-connector.adoc | 90 --------
.../camel-thrift-kafka-sink-connector.adoc | 68 ------
.../camel-thrift-kafka-source-connector.adoc | 72 -------
.../camel-tika-kafka-sink-connector.adoc | 63 ------
.../camel-timer-kafka-source-connector.adoc | 71 -------
.../camel-twilio-kafka-sink-connector.adoc | 66 ------
.../camel-twilio-kafka-source-connector.adoc | 84 --------
...twitter-directmessage-kafka-sink-connector.adoc | 75 -------
...itter-directmessage-kafka-source-connector.adoc | 107 ----------
.../camel-twitter-search-kafka-sink-connector.adoc | 75 -------
...amel-twitter-search-kafka-source-connector.adoc | 107 ----------
...amel-twitter-timeline-kafka-sink-connector.adoc | 77 -------
...el-twitter-timeline-kafka-source-connector.adoc | 109 ----------
.../camel-undertow-kafka-sink-connector.adoc | 84 --------
.../camel-undertow-kafka-source-connector.adoc | 84 --------
.../camel-validator-kafka-sink-connector.adoc | 69 -------
.../camel-velocity-kafka-sink-connector.adoc | 68 ------
.../camel-vertx-http-kafka-sink-connector.adoc | 97 ---------
.../camel-vertx-kafka-kafka-sink-connector.adoc | 209 -------------------
.../camel-vertx-kafka-kafka-source-connector.adoc | 228 ---------------------
.../camel-vertx-kafka-sink-connector.adoc | 66 ------
.../camel-vertx-kafka-source-connector.adoc | 68 ------
...camel-vertx-websocket-kafka-sink-connector.adoc | 69 -------
...mel-vertx-websocket-kafka-source-connector.adoc | 71 -------
.../connectors/camel-vm-kafka-sink-connector.adoc | 73 -------
.../camel-vm-kafka-source-connector.adoc | 71 -------
.../camel-weather-kafka-sink-connector.adoc | 79 -------
.../camel-weather-kafka-source-connector.adoc | 97 ---------
.../camel-web3j-kafka-sink-connector.adoc | 128 ------------
.../camel-web3j-kafka-source-connector.adoc | 84 --------
.../camel-webhook-kafka-source-connector.adoc | 72 -------
...amel-websocket-jsr356-kafka-sink-connector.adoc | 61 ------
...el-websocket-jsr356-kafka-source-connector.adoc | 63 ------
.../camel-websocket-kafka-sink-connector.adoc | 84 --------
.../camel-websocket-kafka-source-connector.adoc | 87 --------
.../camel-weka-kafka-sink-connector.adoc | 68 ------
.../camel-wordpress-kafka-sink-connector.adoc | 77 -------
.../camel-wordpress-kafka-source-connector.adoc | 79 -------
.../camel-workday-kafka-sink-connector.adoc | 67 ------
.../camel-xchange-kafka-sink-connector.adoc | 63 ------
.../connectors/camel-xj-kafka-sink-connector.adoc | 83 --------
...amel-xmlsecurity-sign-kafka-sink-connector.adoc | 112 ----------
...el-xmlsecurity-verify-kafka-sink-connector.adoc | 92 ---------
.../camel-xmpp-kafka-sink-connector.adoc | 74 -------
.../camel-xmpp-kafka-source-connector.adoc | 78 -------
.../camel-xquery-kafka-sink-connector.adoc | 74 -------
.../camel-xquery-kafka-source-connector.adoc | 92 ---------
.../camel-xslt-kafka-sink-connector.adoc | 76 -------
.../camel-xslt-saxon-kafka-sink-connector.adoc | 82 --------
.../camel-yammer-kafka-sink-connector.adoc | 70 -------
.../camel-yammer-kafka-source-connector.adoc | 99 ---------
.../camel-zendesk-kafka-sink-connector.adoc | 72 -------
.../camel-zendesk-kafka-source-connector.adoc | 90 --------
.../camel-zookeeper-kafka-sink-connector.adoc | 69 -------
.../camel-zookeeper-kafka-source-connector.adoc | 73 -------
...el-zookeeper-master-kafka-source-connector.adoc | 68 ------
1040 files changed, 87756 deletions(-)
diff --git a/connectors/camel-activemq-kafka-connector/src/main/docs/camel-activemq-kafka-sink-connector.adoc b/connectors/camel-activemq-kafka-connector/src/main/docs/camel-activemq-kafka-sink-connector.adoc
deleted file mode 100644
index 377f0bd..0000000
--- a/connectors/camel-activemq-kafka-connector/src/main/docs/camel-activemq-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,200 +0,0 @@
-// kafka-connector options: START
-[[camel-activemq-kafka-connector-sink]]
-= camel-activemq-kafka-connector sink configuration
-
-Connector Description: Send messages to (or consume from) Apache ActiveMQ. This component extends the Camel JMS component.
-
-When using camel-activemq-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-activemq-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.activemq.CamelActivemqSinkConnector
-----
-
-
-The camel-activemq sink connector supports 149 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.destinationType* | The kind of destination to use One of: [queue] [topic] [temp-queue] [temp-topic] | "queue" | false | MEDIUM
-| *camel.sink.path.destinationName* | Name of the queue or topic to use as destination | null | true | HIGH
-| *camel.sink.endpoint.clientId* | 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. | null | false | MEDIUM
-| *camel.sink.endpoint.connectionFactory* | The connection factory to be use. A connection factory must be configured either on the component or endpoint. | null | false | MEDIUM
-| *camel.sink.endpoint.disableReplyTo* | 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 mes [...]
-| *camel.sink.endpoint.durableSubscriptionName* | The durable subscriber name for specifying durable topic subscriptions. The clientId option must be configured as well. | null | false | MEDIUM
-| *camel.sink.endpoint.jmsMessageType* | 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. One of: [Bytes] [Map] [Object] [Stream] [Text] | null | false | MEDIUM
-| *camel.sink.endpoint.replyTo* | Provides an explicit ReplyTo destination (overrides any incoming value of Message.getJMSReplyTo() in consumer). | null | false | MEDIUM
-| *camel.sink.endpoint.testConnectionOnStartup* | 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 | false | MEDIUM
-| *camel.sink.endpoint.deliveryDelay* | Sets delivery delay to use for send calls for JMS. This option requires JMS 2.0 compliant broker. | -1L | false | MEDIUM
-| *camel.sink.endpoint.deliveryMode* | Specifies the delivery mode to be used. Possible values are those defined by javax.jms.DeliveryMode. NON_PERSISTENT = 1 and PERSISTENT = 2. One of: [1] [2] | null | false | MEDIUM
-| *camel.sink.endpoint.deliveryPersistent* | Specifies whether persistent delivery is used by default. | true | false | MEDIUM
-| *camel.sink.endpoint.explicitQosEnabled* | 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" | false | MEDIUM
-| *camel.sink.endpoint.formatDateHeadersToIso8601* | Sets whether JMS date properties should be formatted according to the ISO 8601 standard. | false | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.preserveMessageQos* | 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 explicit [...]
-| *camel.sink.endpoint.priority* | Values greater than 1 specify the message priority when sending (where 1 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. One of: [1] [2] [3] [4] [5] [6] [7] [8] [9] | 4 | false | MEDIUM
-| *camel.sink.endpoint.replyToConcurrentConsumers* | 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 | false | MEDIUM
-| *camel.sink.endpoint.replyToMaxConcurrentConsumers* | 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. | null | false | MEDIUM
-| *camel.sink.endpoint.replyToOnTimeoutMaxConcurrent Consumers* | Specifies the maximum number of concurrent consumers for continue routing when timeout occurred when using request/reply over JMS. | 1 | false | MEDIUM
-| *camel.sink.endpoint.replyToOverride* | 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. | null | false | MEDIUM
-| *camel.sink.endpoint.replyToType* | 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 if [...]
-| *camel.sink.endpoint.requestTimeout* | 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. | 20000L | false | MEDIUM
-| *camel.sink.endpoint.timeToLive* | When sending messages, specifies the time-to-live of the message (in milliseconds). | -1L | false | MEDIUM
-| *camel.sink.endpoint.allowAdditionalHeaders* | 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. | null | false | MEDIUM
-| *camel.sink.endpoint.allowNullBody* | 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 | false | MEDIUM
-| *camel.sink.endpoint.alwaysCopyMessage* | 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 | false | MEDIUM
-| *camel.sink.endpoint.correlationProperty* | 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. | null | false | MEDIUM
-| *camel.sink.endpoint.disableTimeToLive* | 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 the [...]
-| *camel.sink.endpoint.forceSendOriginalMessage* | 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 | false | MEDIUM
-| *camel.sink.endpoint.includeSentJMSMessageID* | 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 | false | MEDIUM
-| *camel.sink.endpoint.replyToCacheLevelName* | 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 queues t [...]
-| *camel.sink.endpoint.replyToDestinationSelectorName* | 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). | null | false | MEDIUM
-| *camel.sink.endpoint.streamMessageTypeEnabled* | 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 StreamMessage [...]
-| *camel.sink.endpoint.allowSerializedHeaders* | 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 | false | MEDIUM
-| *camel.sink.endpoint.artemisStreamingEnabled* | Whether optimizing for Apache Artemis streaming mode. | true | false | MEDIUM
-| *camel.sink.endpoint.asyncStartListener* | 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 is [...]
-| *camel.sink.endpoint.asyncStopListener* | Whether to stop the JmsConsumer message listener asynchronously, when stopping a route. | false | false | MEDIUM
-| *camel.sink.endpoint.destinationResolver* | 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). | null | false | MEDIUM
-| *camel.sink.endpoint.errorHandler* | 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 erro [...]
-| *camel.sink.endpoint.exceptionListener* | Specifies the JMS Exception Listener that is to be notified of any underlying JMS exceptions. | null | false | MEDIUM
-| *camel.sink.endpoint.headerFilterStrategy* | To use a custom HeaderFilterStrategy to filter header to and from Camel message. | null | false | MEDIUM
-| *camel.sink.endpoint.idleConsumerLimit* | Specify the limit for the number of consumers that are allowed to be idle at any given time. | 1 | false | MEDIUM
-| *camel.sink.endpoint.idleTaskExecutionLimit* | 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 | false | MEDIUM
-| *camel.sink.endpoint.includeAllJMSXProperties* | 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 | false | MEDIUM
-| *camel.sink.endpoint.jmsKeyFormatStrategy* | 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 the o [...]
-| *camel.sink.endpoint.mapJmsMessage* | 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 | false | MEDIUM
-| *camel.sink.endpoint.maxMessagesPerTask* | 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 | false | MEDIUM
-| *camel.sink.endpoint.messageConverter* | 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. | null | false | MEDIUM
-| *camel.sink.endpoint.messageCreatedStrategy* | 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. | null | false | MEDIUM
-| *camel.sink.endpoint.messageIdEnabled* | 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 | false | MEDIUM
-| *camel.sink.endpoint.messageListenerContainer 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. | null | false | MEDIUM
-| *camel.sink.endpoint.messageTimestampEnabled* | 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 | false | MEDIUM
-| *camel.sink.endpoint.pubSubNoLocal* | Specifies whether to inhibit the delivery of messages published by its own connection. | false | false | MEDIUM
-| *camel.sink.endpoint.receiveTimeout* | The timeout for receiving messages (in milliseconds). | 1000L | false | MEDIUM
-| *camel.sink.endpoint.recoveryInterval* | 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. | 5000L | false | MEDIUM
-| *camel.sink.endpoint.requestTimeoutCheckerInterval* | 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. | 1000L | false | MEDIUM
-| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used | false | false | MEDIUM
-| *camel.sink.endpoint.transferException* | 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 tak [...]
-| *camel.sink.endpoint.transferExchange* | 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 payload [...]
-| *camel.sink.endpoint.useMessageIDAsCorrelationID* | Specifies whether JMSMessageID should always be used as JMSCorrelationID for InOut messages. | false | false | MEDIUM
-| *camel.sink.endpoint.waitForProvisionCorrelationTo BeUpdatedCounter* | 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 | false | MEDIUM
-| *camel.sink.endpoint.waitForProvisionCorrelationTo BeUpdatedThreadSleepingTime* | Interval in millis to sleep each time while waiting for provisional correlation id to be updated. | 100L | false | MEDIUM
-| *camel.sink.endpoint.password* | Password to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory. | null | false | MEDIUM
-| *camel.sink.endpoint.username* | Username to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory. | null | false | MEDIUM
-| *camel.sink.endpoint.transacted* | Specifies whether to use transacted mode | false | false | MEDIUM
-| *camel.sink.endpoint.transactedInOut* | 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, the [...]
-| *camel.sink.endpoint.lazyCreateTransactionManager* | If true, Camel will create a JmsTransactionManager, if there is no transactionManager injected when option transacted=true. | true | false | MEDIUM
-| *camel.sink.endpoint.transactionManager* | The Spring transaction manager to use. | null | false | MEDIUM
-| *camel.sink.endpoint.transactionName* | The name of the transaction to use. | null | false | MEDIUM
-| *camel.sink.endpoint.transactionTimeout* | The timeout value of the transaction (in seconds), if using transacted mode. | -1 | false | MEDIUM
-| *camel.component.activemq.brokerURL* | 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) | null | false | MEDIUM
-| *camel.component.activemq.clientId* | 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. | null | false | MEDIUM
-| *camel.component.activemq.connectionFactory* | The connection factory to be use. A connection factory must be configured either on the component or endpoint. | null | false | MEDIUM
-| *camel.component.activemq.disableReplyTo* | 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 differen [...]
-| *camel.component.activemq.durableSubscriptionName* | The durable subscriber name for specifying durable topic subscriptions. The clientId option must be configured as well. | null | false | MEDIUM
-| *camel.component.activemq.jmsMessageType* | 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. One of: [Bytes] [Map] [Object] [Stream] [Text] | null | false | MEDIUM
-| *camel.component.activemq.replyTo* | Provides an explicit ReplyTo destination (overrides any incoming value of Message.getJMSReplyTo() in consumer). | null | false | MEDIUM
-| *camel.component.activemq.testConnectionOnStartup* | 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 | false | MEDIUM
-| *camel.component.activemq.usePooledConnection* | 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 | false | MEDIUM
-| *camel.component.activemq.useSingleConnection* | 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 | false | MEDIUM
-| *camel.component.activemq.deliveryDelay* | Sets delivery delay to use for send calls for JMS. This option requires JMS 2.0 compliant broker. | -1L | false | MEDIUM
-| *camel.component.activemq.deliveryMode* | Specifies the delivery mode to be used. Possible values are those defined by javax.jms.DeliveryMode. NON_PERSISTENT = 1 and PERSISTENT = 2. One of: [1] [2] | null | false | MEDIUM
-| *camel.component.activemq.deliveryPersistent* | Specifies whether persistent delivery is used by default. | true | false | MEDIUM
-| *camel.component.activemq.explicitQosEnabled* | 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" | false | MEDIUM
-| *camel.component.activemq.formatDateHeadersTo Iso8601* | Sets whether JMS date properties should be formatted according to the ISO 8601 standard. | false | false | MEDIUM
-| *camel.component.activemq.lazyStartProducer* | 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.activemq.preserveMessageQos* | 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 exp [...]
-| *camel.component.activemq.priority* | Values greater than 1 specify the message priority when sending (where 1 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. One of: [1] [2] [3] [4] [5] [6] [7] [8] [9] | 4 | false | MEDIUM
-| *camel.component.activemq.replyToConcurrent 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 | false | MEDIUM
-| *camel.component.activemq.replyToMaxConcurrent 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. | null | false | MEDIUM
-| *camel.component.activemq.replyToOnTimeoutMax ConcurrentConsumers* | Specifies the maximum number of concurrent consumers for continue routing when timeout occurred when using request/reply over JMS. | 1 | false | MEDIUM
-| *camel.component.activemq.replyToOverride* | 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. | null | false | MEDIUM
-| *camel.component.activemq.replyToType* | 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 implicatio [...]
-| *camel.component.activemq.requestTimeout* | 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. | 20000L | false | MEDIUM
-| *camel.component.activemq.timeToLive* | When sending messages, specifies the time-to-live of the message (in milliseconds). | -1L | false | MEDIUM
-| *camel.component.activemq.allowAdditionalHeaders* | 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. | null | false | MEDIUM
-| *camel.component.activemq.allowNullBody* | 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 | false | MEDIUM
-| *camel.component.activemq.alwaysCopyMessage* | 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 | false | MEDIUM
-| *camel.component.activemq.correlationProperty* | 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. | null | false | MEDIUM
-| *camel.component.activemq.disableTimeToLive* | 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.activemq.forceSendOriginalMessage* | 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 | false | MEDIUM
-| *camel.component.activemq.includeSentJMSMessageID* | 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 | false | MEDIUM
-| *camel.component.activemq.replyToCacheLevelName* | 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.activemq.replyToDestination SelectorName* | 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). | null | false | MEDIUM
-| *camel.component.activemq.streamMessageTypeEnabled* | 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 StreamMe [...]
-| *camel.component.activemq.allowAutoWiredConnection 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 | false | MEDIUM
-| *camel.component.activemq.allowAutoWiredDestination 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 | false | MEDIUM
-| *camel.component.activemq.allowSerializedHeaders* | 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 | false | MEDIUM
-| *camel.component.activemq.artemisStreamingEnabled* | Whether optimizing for Apache Artemis streaming mode. | true | false | MEDIUM
-| *camel.component.activemq.asyncStartListener* | 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 optio [...]
-| *camel.component.activemq.asyncStopListener* | Whether to stop the JmsConsumer message listener asynchronously, when stopping a route. | false | false | MEDIUM
-| *camel.component.activemq.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.activemq.configuration* | To use a shared JMS configuration | null | false | MEDIUM
-| *camel.component.activemq.destinationResolver* | 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). | null | false | MEDIUM
-| *camel.component.activemq.errorHandler* | 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 [...]
-| *camel.component.activemq.exceptionListener* | Specifies the JMS Exception Listener that is to be notified of any underlying JMS exceptions. | null | false | MEDIUM
-| *camel.component.activemq.idleConsumerLimit* | Specify the limit for the number of consumers that are allowed to be idle at any given time. | 1 | false | MEDIUM
-| *camel.component.activemq.idleTaskExecutionLimit* | 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 | false | MEDIUM
-| *camel.component.activemq.includeAllJMSXProperties* | 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 | false | MEDIUM
-| *camel.component.activemq.jmsKeyFormatStrategy* | 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 [...]
-| *camel.component.activemq.mapJmsMessage* | 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 | false | MEDIUM
-| *camel.component.activemq.maxMessagesPerTask* | 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 | false | MEDIUM
-| *camel.component.activemq.messageConverter* | 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. | null | false | MEDIUM
-| *camel.component.activemq.messageCreatedStrategy* | 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. | null | false | MEDIUM
-| *camel.component.activemq.messageIdEnabled* | 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 | false | MEDIUM
-| *camel.component.activemq.messageListenerContainer 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. | null | false | MEDIUM
-| *camel.component.activemq.messageTimestampEnabled* | 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 | false | MEDIUM
-| *camel.component.activemq.pubSubNoLocal* | Specifies whether to inhibit the delivery of messages published by its own connection. | false | false | MEDIUM
-| *camel.component.activemq.queueBrowseStrategy* | To use a custom QueueBrowseStrategy when browsing queues | null | false | MEDIUM
-| *camel.component.activemq.receiveTimeout* | The timeout for receiving messages (in milliseconds). | 1000L | false | MEDIUM
-| *camel.component.activemq.recoveryInterval* | 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. | 5000L | false | MEDIUM
-| *camel.component.activemq.requestTimeoutChecker 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. | 1000L | false | MEDIUM
-| *camel.component.activemq.synchronous* | Sets whether synchronous processing should be strictly used | false | false | MEDIUM
-| *camel.component.activemq.transferException* | 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 optio [...]
-| *camel.component.activemq.transferExchange* | 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 pa [...]
-| *camel.component.activemq.trustAllPackages* | 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 | false | MEDIUM
-| *camel.component.activemq.useMessageIDAs CorrelationID* | Specifies whether JMSMessageID should always be used as JMSCorrelationID for InOut messages. | false | false | MEDIUM
-| *camel.component.activemq.waitForProvision CorrelationToBeUpdatedCounter* | 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 | false | MEDIUM
-| *camel.component.activemq.waitForProvision CorrelationToBeUpdatedThreadSleepingTime* | Interval in millis to sleep each time while waiting for provisional correlation id to be updated. | 100L | false | MEDIUM
-| *camel.component.activemq.headerFilterStrategy* | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. | null | false | MEDIUM
-| *camel.component.activemq.password* | Password to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory. | null | false | MEDIUM
-| *camel.component.activemq.username* | Username to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory. | null | false | MEDIUM
-| *camel.component.activemq.transacted* | Specifies whether to use transacted mode | false | false | MEDIUM
-| *camel.component.activemq.transactedInOut* | 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.activemq.lazyCreateTransaction Manager* | If true, Camel will create a JmsTransactionManager, if there is no transactionManager injected when option transacted=true. | true | false | MEDIUM
-| *camel.component.activemq.transactionManager* | The Spring transaction manager to use. | null | false | MEDIUM
-| *camel.component.activemq.transactionName* | The name of the transaction to use. | null | false | MEDIUM
-| *camel.component.activemq.transactionTimeout* | The timeout value of the transaction (in seconds), if using transacted mode. | -1 | false | MEDIUM
-|===
-
-
-
-The camel-activemq sink connector has no converters out of the box.
-
-
-
-
-
-The camel-activemq sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-activemq sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-activemq-kafka-connector/src/main/docs/camel-activemq-kafka-source-connector.adoc b/connectors/camel-activemq-kafka-connector/src/main/docs/camel-activemq-kafka-source-connector.adoc
deleted file mode 100644
index 0e2a533..0000000
--- a/connectors/camel-activemq-kafka-connector/src/main/docs/camel-activemq-kafka-source-connector.adoc
+++ /dev/null
@@ -1,201 +0,0 @@
-// kafka-connector options: START
-[[camel-activemq-kafka-connector-source]]
-= camel-activemq-kafka-connector source configuration
-
-Connector description: Send messages to (or consume from) Apache ActiveMQ. This component extends the Camel JMS component.
-
-When using camel-activemq-kafka-connector as source make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-activemq-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Source connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.activemq.CamelActivemqSourceConnector
-----
-
-
-The camel-activemq source connector supports 150 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.source.path.destinationType* | The kind of destination to use One of: [queue] [topic] [temp-queue] [temp-topic] | "queue" | false | MEDIUM
-| *camel.source.path.destinationName* | Name of the queue or topic to use as destination | null | true | HIGH
-| *camel.source.endpoint.clientId* | 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. | null | false | MEDIUM
-| *camel.source.endpoint.connectionFactory* | The connection factory to be use. A connection factory must be configured either on the component or endpoint. | null | false | MEDIUM
-| *camel.source.endpoint.disableReplyTo* | 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.source.endpoint.durableSubscriptionName* | The durable subscriber name for specifying durable topic subscriptions. The clientId option must be configured as well. | null | false | MEDIUM
-| *camel.source.endpoint.jmsMessageType* | 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. One of: [Bytes] [Map] [Object] [Stream] [Text] | null | false | MEDIUM
-| *camel.source.endpoint.replyTo* | Provides an explicit ReplyTo destination (overrides any incoming value of Message.getJMSReplyTo() in consumer). | null | false | MEDIUM
-| *camel.source.endpoint.testConnectionOnStartup* | 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 | false | MEDIUM
-| *camel.source.endpoint.acknowledgementModeName* | The JMS acknowledgement name, which is one of: SESSION_TRANSACTED, CLIENT_ACKNOWLEDGE, AUTO_ACKNOWLEDGE, DUPS_OK_ACKNOWLEDGE One of: [SESSION_TRANSACTED] [CLIENT_ACKNOWLEDGE] [AUTO_ACKNOWLEDGE] [DUPS_OK_ACKNOWLEDGE] | "AUTO_ACKNOWLEDGE" | false | MEDIUM
-| *camel.source.endpoint.artemisConsumerPriority* | Consumer priorities allow you to ensure that high priority consumers receive messages while they are active. Normally, active consumers connected to a queue receive messages from it in a round-robin fashion. When consumer priorities are in use, messages are delivered round-robin if multiple active consumers exist with the same high priority. Messages will only going to lower priority consumers when the high priority consumers do not hav [...]
-| *camel.source.endpoint.asyncConsumer* | 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.source.endpoint.autoStartup* | Specifies whether the consumer container should auto-startup. | true | false | MEDIUM
-| *camel.source.endpoint.cacheLevel* | Sets the cache level by ID for the underlying JMS resources. See cacheLevelName option for more details. | null | false | MEDIUM
-| *camel.source.endpoint.cacheLevelName* | 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. One of: [CACHE_AUTO] [CACHE_CONNECTION] [CACHE_CONSUMER] [CACHE_NONE] [CACHE_SESSION] | "CACHE_AUTO" | false | MEDIUM
-| *camel.source.endpoint.concurrentConsumers* | 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 | false | MEDIUM
-| *camel.source.endpoint.maxConcurrentConsumers* | 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. | null | false | MEDIUM
-| *camel.source.endpoint.replyToDeliveryPersistent* | Specifies whether to use persistent delivery by default for replies. | true | false | MEDIUM
-| *camel.source.endpoint.selector* | Sets the JMS selector to use | null | false | MEDIUM
-| *camel.source.endpoint.subscriptionDurable* | 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.source.endpoint.subscriptionName* | 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.source.endpoint.subscriptionShared* | 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.source.endpoint.acceptMessagesWhileStopping* | 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.source.endpoint.allowReplyManagerQuickStop* | 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 flag [...]
-| *camel.source.endpoint.consumerType* | 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.source.endpoint.defaultTaskExecutorType* | 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 an [...]
-| *camel.source.endpoint.destinationOptions* | Destination Options are a way to provide extended configuration options to a JMS consumer without having to extend the JMS API. The options are encoded using URL query syntax in the destination name that the consumer is created on. See more details at \https://activemq.apache.org/destination-options. | null | false | MEDIUM
-| *camel.source.endpoint.eagerLoadingOfProperties* | 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 | false | MEDIUM
-| *camel.source.endpoint.eagerPoisonBody* | 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}" | false | MEDIUM
-| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | false | MEDIUM
-| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | false | MEDIUM
-| *camel.source.endpoint.exposeListenerSession* | Specifies whether the listener session should be exposed when consuming messages. | false | false | MEDIUM
-| *camel.source.endpoint.replyToSameDestination 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 | false | MEDIUM
-| *camel.source.endpoint.taskExecutor* | Allows you to specify a custom task executor for consuming messages. | null | false | MEDIUM
-| *camel.source.endpoint.allowSerializedHeaders* | 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 | false | MEDIUM
-| *camel.source.endpoint.artemisStreamingEnabled* | Whether optimizing for Apache Artemis streaming mode. | true | false | MEDIUM
-| *camel.source.endpoint.asyncStartListener* | 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.source.endpoint.asyncStopListener* | Whether to stop the JmsConsumer message listener asynchronously, when stopping a route. | false | false | MEDIUM
-| *camel.source.endpoint.destinationResolver* | 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). | null | false | MEDIUM
-| *camel.source.endpoint.errorHandler* | 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.source.endpoint.exceptionListener* | Specifies the JMS Exception Listener that is to be notified of any underlying JMS exceptions. | null | false | MEDIUM
-| *camel.source.endpoint.headerFilterStrategy* | To use a custom HeaderFilterStrategy to filter header to and from Camel message. | null | false | MEDIUM
-| *camel.source.endpoint.idleConsumerLimit* | Specify the limit for the number of consumers that are allowed to be idle at any given time. | 1 | false | MEDIUM
-| *camel.source.endpoint.idleTaskExecutionLimit* | 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 | false | MEDIUM
-| *camel.source.endpoint.includeAllJMSXProperties* | 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 | false | MEDIUM
-| *camel.source.endpoint.jmsKeyFormatStrategy* | 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 the [...]
-| *camel.source.endpoint.mapJmsMessage* | 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 | false | MEDIUM
-| *camel.source.endpoint.maxMessagesPerTask* | 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 | false | MEDIUM
-| *camel.source.endpoint.messageConverter* | 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. | null | false | MEDIUM
-| *camel.source.endpoint.messageCreatedStrategy* | 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. | null | false | MEDIUM
-| *camel.source.endpoint.messageIdEnabled* | 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 | false | MEDIUM
-| *camel.source.endpoint.messageListenerContainer 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. | null | false | MEDIUM
-| *camel.source.endpoint.messageTimestampEnabled* | 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 | false | MEDIUM
-| *camel.source.endpoint.pubSubNoLocal* | Specifies whether to inhibit the delivery of messages published by its own connection. | false | false | MEDIUM
-| *camel.source.endpoint.receiveTimeout* | The timeout for receiving messages (in milliseconds). | 1000L | false | MEDIUM
-| *camel.source.endpoint.recoveryInterval* | 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. | 5000L | false | MEDIUM
-| *camel.source.endpoint.requestTimeoutChecker 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. | 1000L | false | MEDIUM
-| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used | false | false | MEDIUM
-| *camel.source.endpoint.transferException* | 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.source.endpoint.transferExchange* | 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.source.endpoint.useMessageIDAsCorrelationID* | Specifies whether JMSMessageID should always be used as JMSCorrelationID for InOut messages. | false | false | MEDIUM
-| *camel.source.endpoint.waitForProvisionCorrelation ToBeUpdatedCounter* | 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 | false | MEDIUM
-| *camel.source.endpoint.waitForProvisionCorrelation ToBeUpdatedThreadSleepingTime* | Interval in millis to sleep each time while waiting for provisional correlation id to be updated. | 100L | false | MEDIUM
-| *camel.source.endpoint.errorHandlerLoggingLevel* | Allows to configure the default errorHandler logging level for logging uncaught exceptions. One of: [TRACE] [DEBUG] [INFO] [WARN] [ERROR] [OFF] | "WARN" | false | MEDIUM
-| *camel.source.endpoint.errorHandlerLogStackTrace* | Allows to control whether stacktraces should be logged or not, by the default errorHandler. | true | false | MEDIUM
-| *camel.source.endpoint.password* | Password to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory. | null | false | MEDIUM
-| *camel.source.endpoint.username* | Username to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory. | null | false | MEDIUM
-| *camel.source.endpoint.transacted* | Specifies whether to use transacted mode | false | false | MEDIUM
-| *camel.source.endpoint.transactedInOut* | 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.source.endpoint.lazyCreateTransactionManager* | If true, Camel will create a JmsTransactionManager, if there is no transactionManager injected when option transacted=true. | true | false | MEDIUM
-| *camel.source.endpoint.transactionManager* | The Spring transaction manager to use. | null | false | MEDIUM
-| *camel.source.endpoint.transactionName* | The name of the transaction to use. | null | false | MEDIUM
-| *camel.source.endpoint.transactionTimeout* | The timeout value of the transaction (in seconds), if using transacted mode. | -1 | false | MEDIUM
-| *camel.component.activemq.brokerURL* | 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) | null | false | MEDIUM
-| *camel.component.activemq.clientId* | 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. | null | false | MEDIUM
-| *camel.component.activemq.connectionFactory* | The connection factory to be use. A connection factory must be configured either on the component or endpoint. | null | false | MEDIUM
-| *camel.component.activemq.disableReplyTo* | 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 differen [...]
-| *camel.component.activemq.durableSubscriptionName* | The durable subscriber name for specifying durable topic subscriptions. The clientId option must be configured as well. | null | false | MEDIUM
-| *camel.component.activemq.jmsMessageType* | 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. One of: [Bytes] [Map] [Object] [Stream] [Text] | null | false | MEDIUM
-| *camel.component.activemq.replyTo* | Provides an explicit ReplyTo destination (overrides any incoming value of Message.getJMSReplyTo() in consumer). | null | false | MEDIUM
-| *camel.component.activemq.testConnectionOnStartup* | 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 | false | MEDIUM
-| *camel.component.activemq.usePooledConnection* | 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 | false | MEDIUM
-| *camel.component.activemq.useSingleConnection* | 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 | false | MEDIUM
-| *camel.component.activemq.acknowledgementModeName* | The JMS acknowledgement name, which is one of: SESSION_TRANSACTED, CLIENT_ACKNOWLEDGE, AUTO_ACKNOWLEDGE, DUPS_OK_ACKNOWLEDGE One of: [SESSION_TRANSACTED] [CLIENT_ACKNOWLEDGE] [AUTO_ACKNOWLEDGE] [DUPS_OK_ACKNOWLEDGE] | "AUTO_ACKNOWLEDGE" | false | MEDIUM
-| *camel.component.activemq.artemisConsumerPriority* | Consumer priorities allow you to ensure that high priority consumers receive messages while they are active. Normally, active consumers connected to a queue receive messages from it in a round-robin fashion. When consumer priorities are in use, messages are delivered round-robin if multiple active consumers exist with the same high priority. Messages will only going to lower priority consumers when the high priority consumers do not [...]
-| *camel.component.activemq.asyncConsumer* | 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. N [...]
-| *camel.component.activemq.autoStartup* | Specifies whether the consumer container should auto-startup. | true | false | MEDIUM
-| *camel.component.activemq.cacheLevel* | Sets the cache level by ID for the underlying JMS resources. See cacheLevelName option for more details. | null | false | MEDIUM
-| *camel.component.activemq.cacheLevelName* | 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. One of: [CACHE_AUTO] [CACHE_CONNECTION] [CACHE_CONSUMER] [CACHE_NONE] [CACHE_SESSION] | "CACHE_AUTO" | false | MEDIUM
-| *camel.component.activemq.concurrentConsumers* | 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 | false | MEDIUM
-| *camel.component.activemq.maxConcurrentConsumers* | 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. | null | false | MEDIUM
-| *camel.component.activemq.replyToDeliveryPersistent* | Specifies whether to use persistent delivery by default for replies. | true | false | MEDIUM
-| *camel.component.activemq.selector* | Sets the JMS selector to use | null | false | MEDIUM
-| *camel.component.activemq.subscriptionDurable* | 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 t [...]
-| *camel.component.activemq.subscriptionName* | 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 J [...]
-| *camel.component.activemq.subscriptionShared* | 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 [...]
-| *camel.component.activemq.acceptMessagesWhile 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 let [...]
-| *camel.component.activemq.allowReplyManagerQuick 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 [...]
-| *camel.component.activemq.consumerType* | 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.spring [...]
-| *camel.component.activemq.defaultTaskExecutorType* | 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.activemq.eagerLoadingOfProperties* | 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 | false | MEDIUM
-| *camel.component.activemq.eagerPoisonBody* | 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}" | fals [...]
-| *camel.component.activemq.exposeListenerSession* | Specifies whether the listener session should be exposed when consuming messages. | false | false | MEDIUM
-| *camel.component.activemq.replyToSameDestination 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 | false | MEDIUM
-| *camel.component.activemq.taskExecutor* | Allows you to specify a custom task executor for consuming messages. | null | false | MEDIUM
-| *camel.component.activemq.allowAutoWiredConnection 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 | false | MEDIUM
-| *camel.component.activemq.allowAutoWiredDestination 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 | false | MEDIUM
-| *camel.component.activemq.allowSerializedHeaders* | 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 | false | MEDIUM
-| *camel.component.activemq.artemisStreamingEnabled* | Whether optimizing for Apache Artemis streaming mode. | true | false | MEDIUM
-| *camel.component.activemq.asyncStartListener* | 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 optio [...]
-| *camel.component.activemq.asyncStopListener* | Whether to stop the JmsConsumer message listener asynchronously, when stopping a route. | false | false | MEDIUM
-| *camel.component.activemq.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.activemq.configuration* | To use a shared JMS configuration | null | false | MEDIUM
-| *camel.component.activemq.destinationResolver* | 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). | null | false | MEDIUM
-| *camel.component.activemq.errorHandler* | 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 [...]
-| *camel.component.activemq.exceptionListener* | Specifies the JMS Exception Listener that is to be notified of any underlying JMS exceptions. | null | false | MEDIUM
-| *camel.component.activemq.idleConsumerLimit* | Specify the limit for the number of consumers that are allowed to be idle at any given time. | 1 | false | MEDIUM
-| *camel.component.activemq.idleTaskExecutionLimit* | 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 | false | MEDIUM
-| *camel.component.activemq.includeAllJMSXProperties* | 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 | false | MEDIUM
-| *camel.component.activemq.jmsKeyFormatStrategy* | 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 [...]
-| *camel.component.activemq.mapJmsMessage* | 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 | false | MEDIUM
-| *camel.component.activemq.maxMessagesPerTask* | 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 | false | MEDIUM
-| *camel.component.activemq.messageConverter* | 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. | null | false | MEDIUM
-| *camel.component.activemq.messageCreatedStrategy* | 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. | null | false | MEDIUM
-| *camel.component.activemq.messageIdEnabled* | 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 | false | MEDIUM
-| *camel.component.activemq.messageListenerContainer 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. | null | false | MEDIUM
-| *camel.component.activemq.messageTimestampEnabled* | 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 | false | MEDIUM
-| *camel.component.activemq.pubSubNoLocal* | Specifies whether to inhibit the delivery of messages published by its own connection. | false | false | MEDIUM
-| *camel.component.activemq.queueBrowseStrategy* | To use a custom QueueBrowseStrategy when browsing queues | null | false | MEDIUM
-| *camel.component.activemq.receiveTimeout* | The timeout for receiving messages (in milliseconds). | 1000L | false | MEDIUM
-| *camel.component.activemq.recoveryInterval* | 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. | 5000L | false | MEDIUM
-| *camel.component.activemq.requestTimeoutChecker 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. | 1000L | false | MEDIUM
-| *camel.component.activemq.synchronous* | Sets whether synchronous processing should be strictly used | false | false | MEDIUM
-| *camel.component.activemq.transferException* | 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 optio [...]
-| *camel.component.activemq.transferExchange* | 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 pa [...]
-| *camel.component.activemq.trustAllPackages* | 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 | false | MEDIUM
-| *camel.component.activemq.useMessageIDAs CorrelationID* | Specifies whether JMSMessageID should always be used as JMSCorrelationID for InOut messages. | false | false | MEDIUM
-| *camel.component.activemq.waitForProvision CorrelationToBeUpdatedCounter* | 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 | false | MEDIUM
-| *camel.component.activemq.waitForProvision CorrelationToBeUpdatedThreadSleepingTime* | Interval in millis to sleep each time while waiting for provisional correlation id to be updated. | 100L | false | MEDIUM
-| *camel.component.activemq.headerFilterStrategy* | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. | null | false | MEDIUM
-| *camel.component.activemq.errorHandlerLoggingLevel* | Allows to configure the default errorHandler logging level for logging uncaught exceptions. One of: [TRACE] [DEBUG] [INFO] [WARN] [ERROR] [OFF] | "WARN" | false | MEDIUM
-| *camel.component.activemq.errorHandlerLogStackTrace* | Allows to control whether stacktraces should be logged or not, by the default errorHandler. | true | false | MEDIUM
-| *camel.component.activemq.password* | Password to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory. | null | false | MEDIUM
-| *camel.component.activemq.username* | Username to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory. | null | false | MEDIUM
-| *camel.component.activemq.transacted* | Specifies whether to use transacted mode | false | false | MEDIUM
-| *camel.component.activemq.transactedInOut* | 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.activemq.lazyCreateTransaction Manager* | If true, Camel will create a JmsTransactionManager, if there is no transactionManager injected when option transacted=true. | true | false | MEDIUM
-| *camel.component.activemq.transactionManager* | The Spring transaction manager to use. | null | false | MEDIUM
-| *camel.component.activemq.transactionName* | The name of the transaction to use. | null | false | MEDIUM
-| *camel.component.activemq.transactionTimeout* | The timeout value of the transaction (in seconds), if using transacted mode. | -1 | false | MEDIUM
-|===
-
-
-
-The camel-activemq source connector has no converters out of the box.
-
-
-
-
-
-The camel-activemq source connector has no transforms out of the box.
-
-
-
-
-
-The camel-activemq source connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-ahc-kafka-connector/src/main/docs/camel-ahc-kafka-sink-connector.adoc b/connectors/camel-ahc-kafka-connector/src/main/docs/camel-ahc-kafka-sink-connector.adoc
deleted file mode 100644
index eeb49f2..0000000
--- a/connectors/camel-ahc-kafka-connector/src/main/docs/camel-ahc-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,74 +0,0 @@
-// kafka-connector options: START
-[[camel-ahc-kafka-connector-sink]]
-= camel-ahc-kafka-connector sink configuration
-
-Connector Description: Call external HTTP services using Async Http Client.
-
-When using camel-ahc-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-ahc-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.ahc.CamelAhcSinkConnector
-----
-
-
-The camel-ahc sink connector supports 23 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.httpUri* | The URI to use such as \http://hostname:port/path | null | true | HIGH
-| *camel.sink.endpoint.bridgeEndpoint* | If the option is true, then the Exchange.HTTP_URI header is ignored, and use the endpoint's URI for request. You may also set the throwExceptionOnFailure to be false to let the AhcProducer send all the fault response back. | false | false | MEDIUM
-| *camel.sink.endpoint.bufferSize* | The initial in-memory buffer size used when transferring data between Camel and AHC Client. | 4096 | false | MEDIUM
-| *camel.sink.endpoint.connectionClose* | Define if the Connection Close header has to be added to HTTP Request. This parameter is false by default | false | false | MEDIUM
-| *camel.sink.endpoint.cookieHandler* | Configure a cookie handler to maintain a HTTP session | null | false | MEDIUM
-| *camel.sink.endpoint.headerFilterStrategy* | To use a custom HeaderFilterStrategy to filter header to and from Camel message. | null | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.throwExceptionOnFailure* | Option to disable throwing the AhcOperationFailedException in case of failed responses from the remote server. This allows you to get all responses regardless of the HTTP status code. | true | false | MEDIUM
-| *camel.sink.endpoint.transferException* | If enabled and an Exchange failed processing on the consumer side, and if the caused Exception was send back serialized in the response as a application/x-java-serialized-object content type (for example using Jetty or Servlet Camel components). On the producer side the exception will be deserialized and thrown as is, instead of the AhcOperationFailedException. The caused exception is required to be serialized. This is by default turned off. If [...]
-| *camel.sink.endpoint.binding* | To use a custom AhcBinding which allows to control how to bind between AHC and Camel. | null | false | MEDIUM
-| *camel.sink.endpoint.clientConfig* | To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance. | null | false | MEDIUM
-| *camel.sink.endpoint.clientConfigOptions* | To configure the AsyncHttpClientConfig using the key/values from the Map. | null | false | MEDIUM
-| *camel.sink.endpoint.clientConfigRealmOptions* | To configure the AsyncHttpClientConfig Realm using the key/values from the Map. | null | false | MEDIUM
-| *camel.sink.endpoint.sslContextParameters* | Reference to a org.apache.camel.support.jsse.SSLContextParameters in the Registry. This reference overrides any configured SSLContextParameters at the component level. See Using the JSSE Configuration Utility. Note that configuring this option will override any SSL/TLS configuration options provided through the clientConfig option at the endpoint or component level. | null | false | MEDIUM
-| *camel.component.ahc.lazyStartProducer* | 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 cre [...]
-| *camel.component.ahc.allowJavaSerializedObject* | 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 | false | MEDIUM
-| *camel.component.ahc.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.ahc.binding* | To use a custom AhcBinding which allows to control how to bind between AHC and Camel. | null | false | MEDIUM
-| *camel.component.ahc.client* | To use a custom AsyncHttpClient | null | false | MEDIUM
-| *camel.component.ahc.clientConfig* | To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance. | null | false | MEDIUM
-| *camel.component.ahc.headerFilterStrategy* | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. | null | false | MEDIUM
-| *camel.component.ahc.sslContextParameters* | 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. | null | false | MEDIUM
-| *camel.component.ahc.useGlobalSslContextParameters* | Enable usage of global SSL context parameters. | false | false | MEDIUM
-|===
-
-
-
-The camel-ahc sink connector has no converters out of the box.
-
-
-
-
-
-The camel-ahc sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-ahc sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-ahc-ws-kafka-connector/src/main/docs/camel-ahc-ws-kafka-sink-connector.adoc b/connectors/camel-ahc-ws-kafka-connector/src/main/docs/camel-ahc-ws-kafka-sink-connector.adoc
deleted file mode 100644
index be2cde0..0000000
--- a/connectors/camel-ahc-ws-kafka-connector/src/main/docs/camel-ahc-ws-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,75 +0,0 @@
-// kafka-connector options: START
-[[camel-ahc-ws-kafka-connector-sink]]
-= camel-ahc-ws-kafka-connector sink configuration
-
-Connector Description: Exchange data with external Websocket servers using Async Http Client.
-
-When using camel-ahc-ws-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-ahc-ws-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.ahcws.CamelAhcwsSinkConnector
-----
-
-
-The camel-ahc-ws sink connector supports 24 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.httpUri* | The URI to use such as \http://hostname:port/path | null | true | HIGH
-| *camel.sink.endpoint.bridgeEndpoint* | If the option is true, then the Exchange.HTTP_URI header is ignored, and use the endpoint's URI for request. You may also set the throwExceptionOnFailure to be false to let the AhcProducer send all the fault response back. | false | false | MEDIUM
-| *camel.sink.endpoint.bufferSize* | The initial in-memory buffer size used when transferring data between Camel and AHC Client. | 4096 | false | MEDIUM
-| *camel.sink.endpoint.headerFilterStrategy* | To use a custom HeaderFilterStrategy to filter header to and from Camel message. | null | false | MEDIUM
-| *camel.sink.endpoint.throwExceptionOnFailure* | Option to disable throwing the AhcOperationFailedException in case of failed responses from the remote server. This allows you to get all responses regardless of the HTTP status code. | true | false | MEDIUM
-| *camel.sink.endpoint.transferException* | If enabled and an Exchange failed processing on the consumer side, and if the caused Exception was send back serialized in the response as a application/x-java-serialized-object content type (for example using Jetty or Servlet Camel components). On the producer side the exception will be deserialized and thrown as is, instead of the AhcOperationFailedException. The caused exception is required to be serialized. This is by default turned off. If [...]
-| *camel.sink.endpoint.connectionClose* | Define if the Connection Close header has to be added to HTTP Request. This parameter is false by default | false | false | MEDIUM
-| *camel.sink.endpoint.cookieHandler* | Configure a cookie handler to maintain a HTTP session | null | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.useStreaming* | To enable streaming to send data as multiple text fragments. | false | false | MEDIUM
-| *camel.sink.endpoint.binding* | To use a custom AhcBinding which allows to control how to bind between AHC and Camel. | null | false | MEDIUM
-| *camel.sink.endpoint.clientConfig* | To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance. | null | false | MEDIUM
-| *camel.sink.endpoint.clientConfigOptions* | To configure the AsyncHttpClientConfig using the key/values from the Map. | null | false | MEDIUM
-| *camel.sink.endpoint.clientConfigRealmOptions* | To configure the AsyncHttpClientConfig Realm using the key/values from the Map. | null | false | MEDIUM
-| *camel.sink.endpoint.sslContextParameters* | Reference to a org.apache.camel.support.jsse.SSLContextParameters in the Registry. This reference overrides any configured SSLContextParameters at the component level. See Using the JSSE Configuration Utility. Note that configuring this option will override any SSL/TLS configuration options provided through the clientConfig option at the endpoint or component level. | null | false | MEDIUM
-| *camel.component.ahc-ws.lazyStartProducer* | 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.ahc-ws.allowJavaSerializedObject* | 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 | false | MEDIUM
-| *camel.component.ahc-ws.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.ahc-ws.binding* | To use a custom AhcBinding which allows to control how to bind between AHC and Camel. | null | false | MEDIUM
-| *camel.component.ahc-ws.client* | To use a custom AsyncHttpClient | null | false | MEDIUM
-| *camel.component.ahc-ws.clientConfig* | To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance. | null | false | MEDIUM
-| *camel.component.ahc-ws.headerFilterStrategy* | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. | null | false | MEDIUM
-| *camel.component.ahc-ws.sslContextParameters* | 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. | null | false | MEDIUM
-| *camel.component.ahc-ws.useGlobalSslContext Parameters* | Enable usage of global SSL context parameters. | false | false | MEDIUM
-|===
-
-
-
-The camel-ahc-ws sink connector has no converters out of the box.
-
-
-
-
-
-The camel-ahc-ws sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-ahc-ws sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-ahc-ws-kafka-connector/src/main/docs/camel-ahc-ws-kafka-source-connector.adoc b/connectors/camel-ahc-ws-kafka-connector/src/main/docs/camel-ahc-ws-kafka-source-connector.adoc
deleted file mode 100644
index 5c79ae8..0000000
--- a/connectors/camel-ahc-ws-kafka-connector/src/main/docs/camel-ahc-ws-kafka-source-connector.adoc
+++ /dev/null
@@ -1,75 +0,0 @@
-// kafka-connector options: START
-[[camel-ahc-ws-kafka-connector-source]]
-= camel-ahc-ws-kafka-connector source configuration
-
-Connector description: Exchange data with external Websocket servers using Async Http Client.
-
-When using camel-ahc-ws-kafka-connector as source make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-ahc-ws-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Source connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.ahcws.CamelAhcwsSourceConnector
-----
-
-
-The camel-ahc-ws source connector supports 24 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.source.path.httpUri* | The URI to use such as \http://hostname:port/path | null | true | HIGH
-| *camel.source.endpoint.bridgeEndpoint* | If the option is true, then the Exchange.HTTP_URI header is ignored, and use the endpoint's URI for request. You may also set the throwExceptionOnFailure to be false to let the AhcProducer send all the fault response back. | false | false | MEDIUM
-| *camel.source.endpoint.bufferSize* | The initial in-memory buffer size used when transferring data between Camel and AHC Client. | 4096 | false | MEDIUM
-| *camel.source.endpoint.headerFilterStrategy* | To use a custom HeaderFilterStrategy to filter header to and from Camel message. | null | false | MEDIUM
-| *camel.source.endpoint.throwExceptionOnFailure* | Option to disable throwing the AhcOperationFailedException in case of failed responses from the remote server. This allows you to get all responses regardless of the HTTP status code. | true | false | MEDIUM
-| *camel.source.endpoint.transferException* | If enabled and an Exchange failed processing on the consumer side, and if the caused Exception was send back serialized in the response as a application/x-java-serialized-object content type (for example using Jetty or Servlet Camel components). On the producer side the exception will be deserialized and thrown as is, instead of the AhcOperationFailedException. The caused exception is required to be serialized. This is by default turned off. [...]
-| *camel.source.endpoint.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.source.endpoint.sendMessageOnError* | Whether to send an message if the web-socket listener received an error. | false | false | MEDIUM
-| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | false | MEDIUM
-| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | false | MEDIUM
-| *camel.source.endpoint.binding* | To use a custom AhcBinding which allows to control how to bind between AHC and Camel. | null | false | MEDIUM
-| *camel.source.endpoint.clientConfig* | To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance. | null | false | MEDIUM
-| *camel.source.endpoint.clientConfigOptions* | To configure the AsyncHttpClientConfig using the key/values from the Map. | null | false | MEDIUM
-| *camel.source.endpoint.clientConfigRealmOptions* | To configure the AsyncHttpClientConfig Realm using the key/values from the Map. | null | false | MEDIUM
-| *camel.source.endpoint.sslContextParameters* | Reference to a org.apache.camel.support.jsse.SSLContextParameters in the Registry. This reference overrides any configured SSLContextParameters at the component level. See Using the JSSE Configuration Utility. Note that configuring this option will override any SSL/TLS configuration options provided through the clientConfig option at the endpoint or component level. | null | false | MEDIUM
-| *camel.component.ahc-ws.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.component.ahc-ws.allowJavaSerializedObject* | 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 | false | MEDIUM
-| *camel.component.ahc-ws.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.ahc-ws.binding* | To use a custom AhcBinding which allows to control how to bind between AHC and Camel. | null | false | MEDIUM
-| *camel.component.ahc-ws.client* | To use a custom AsyncHttpClient | null | false | MEDIUM
-| *camel.component.ahc-ws.clientConfig* | To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance. | null | false | MEDIUM
-| *camel.component.ahc-ws.headerFilterStrategy* | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. | null | false | MEDIUM
-| *camel.component.ahc-ws.sslContextParameters* | 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. | null | false | MEDIUM
-| *camel.component.ahc-ws.useGlobalSslContext Parameters* | Enable usage of global SSL context parameters. | false | false | MEDIUM
-|===
-
-
-
-The camel-ahc-ws source connector has no converters out of the box.
-
-
-
-
-
-The camel-ahc-ws source connector has no transforms out of the box.
-
-
-
-
-
-The camel-ahc-ws source connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-ahc-wss-kafka-connector/src/main/docs/camel-ahc-wss-kafka-sink-connector.adoc b/connectors/camel-ahc-wss-kafka-connector/src/main/docs/camel-ahc-wss-kafka-sink-connector.adoc
deleted file mode 100644
index 5abae40..0000000
--- a/connectors/camel-ahc-wss-kafka-connector/src/main/docs/camel-ahc-wss-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,75 +0,0 @@
-// kafka-connector options: START
-[[camel-ahc-wss-kafka-connector-sink]]
-= camel-ahc-wss-kafka-connector sink configuration
-
-Connector Description: Exchange data with external Websocket servers using Async Http Client.
-
-When using camel-ahc-wss-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-ahc-wss-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.ahcwss.CamelAhcwssSinkConnector
-----
-
-
-The camel-ahc-wss sink connector supports 24 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.httpUri* | The URI to use such as \http://hostname:port/path | null | true | HIGH
-| *camel.sink.endpoint.bridgeEndpoint* | If the option is true, then the Exchange.HTTP_URI header is ignored, and use the endpoint's URI for request. You may also set the throwExceptionOnFailure to be false to let the AhcProducer send all the fault response back. | false | false | MEDIUM
-| *camel.sink.endpoint.bufferSize* | The initial in-memory buffer size used when transferring data between Camel and AHC Client. | 4096 | false | MEDIUM
-| *camel.sink.endpoint.headerFilterStrategy* | To use a custom HeaderFilterStrategy to filter header to and from Camel message. | null | false | MEDIUM
-| *camel.sink.endpoint.throwExceptionOnFailure* | Option to disable throwing the AhcOperationFailedException in case of failed responses from the remote server. This allows you to get all responses regardless of the HTTP status code. | true | false | MEDIUM
-| *camel.sink.endpoint.transferException* | If enabled and an Exchange failed processing on the consumer side, and if the caused Exception was send back serialized in the response as a application/x-java-serialized-object content type (for example using Jetty or Servlet Camel components). On the producer side the exception will be deserialized and thrown as is, instead of the AhcOperationFailedException. The caused exception is required to be serialized. This is by default turned off. If [...]
-| *camel.sink.endpoint.connectionClose* | Define if the Connection Close header has to be added to HTTP Request. This parameter is false by default | false | false | MEDIUM
-| *camel.sink.endpoint.cookieHandler* | Configure a cookie handler to maintain a HTTP session | null | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.useStreaming* | To enable streaming to send data as multiple text fragments. | false | false | MEDIUM
-| *camel.sink.endpoint.binding* | To use a custom AhcBinding which allows to control how to bind between AHC and Camel. | null | false | MEDIUM
-| *camel.sink.endpoint.clientConfig* | To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance. | null | false | MEDIUM
-| *camel.sink.endpoint.clientConfigOptions* | To configure the AsyncHttpClientConfig using the key/values from the Map. | null | false | MEDIUM
-| *camel.sink.endpoint.clientConfigRealmOptions* | To configure the AsyncHttpClientConfig Realm using the key/values from the Map. | null | false | MEDIUM
-| *camel.sink.endpoint.sslContextParameters* | Reference to a org.apache.camel.support.jsse.SSLContextParameters in the Registry. This reference overrides any configured SSLContextParameters at the component level. See Using the JSSE Configuration Utility. Note that configuring this option will override any SSL/TLS configuration options provided through the clientConfig option at the endpoint or component level. | null | false | MEDIUM
-| *camel.component.ahc-wss.lazyStartProducer* | 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.ahc-wss.allowJavaSerializedObject* | 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 | false | MEDIUM
-| *camel.component.ahc-wss.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.ahc-wss.binding* | To use a custom AhcBinding which allows to control how to bind between AHC and Camel. | null | false | MEDIUM
-| *camel.component.ahc-wss.client* | To use a custom AsyncHttpClient | null | false | MEDIUM
-| *camel.component.ahc-wss.clientConfig* | To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance. | null | false | MEDIUM
-| *camel.component.ahc-wss.headerFilterStrategy* | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. | null | false | MEDIUM
-| *camel.component.ahc-wss.sslContextParameters* | 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. | null | false | MEDIUM
-| *camel.component.ahc-wss.useGlobalSslContext Parameters* | Enable usage of global SSL context parameters. | false | false | MEDIUM
-|===
-
-
-
-The camel-ahc-wss sink connector has no converters out of the box.
-
-
-
-
-
-The camel-ahc-wss sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-ahc-wss sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-ahc-wss-kafka-connector/src/main/docs/camel-ahc-wss-kafka-source-connector.adoc b/connectors/camel-ahc-wss-kafka-connector/src/main/docs/camel-ahc-wss-kafka-source-connector.adoc
deleted file mode 100644
index 7e06962..0000000
--- a/connectors/camel-ahc-wss-kafka-connector/src/main/docs/camel-ahc-wss-kafka-source-connector.adoc
+++ /dev/null
@@ -1,75 +0,0 @@
-// kafka-connector options: START
-[[camel-ahc-wss-kafka-connector-source]]
-= camel-ahc-wss-kafka-connector source configuration
-
-Connector description: Exchange data with external Websocket servers using Async Http Client.
-
-When using camel-ahc-wss-kafka-connector as source make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-ahc-wss-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Source connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.ahcwss.CamelAhcwssSourceConnector
-----
-
-
-The camel-ahc-wss source connector supports 24 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.source.path.httpUri* | The URI to use such as \http://hostname:port/path | null | true | HIGH
-| *camel.source.endpoint.bridgeEndpoint* | If the option is true, then the Exchange.HTTP_URI header is ignored, and use the endpoint's URI for request. You may also set the throwExceptionOnFailure to be false to let the AhcProducer send all the fault response back. | false | false | MEDIUM
-| *camel.source.endpoint.bufferSize* | The initial in-memory buffer size used when transferring data between Camel and AHC Client. | 4096 | false | MEDIUM
-| *camel.source.endpoint.headerFilterStrategy* | To use a custom HeaderFilterStrategy to filter header to and from Camel message. | null | false | MEDIUM
-| *camel.source.endpoint.throwExceptionOnFailure* | Option to disable throwing the AhcOperationFailedException in case of failed responses from the remote server. This allows you to get all responses regardless of the HTTP status code. | true | false | MEDIUM
-| *camel.source.endpoint.transferException* | If enabled and an Exchange failed processing on the consumer side, and if the caused Exception was send back serialized in the response as a application/x-java-serialized-object content type (for example using Jetty or Servlet Camel components). On the producer side the exception will be deserialized and thrown as is, instead of the AhcOperationFailedException. The caused exception is required to be serialized. This is by default turned off. [...]
-| *camel.source.endpoint.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.source.endpoint.sendMessageOnError* | Whether to send an message if the web-socket listener received an error. | false | false | MEDIUM
-| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | false | MEDIUM
-| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | false | MEDIUM
-| *camel.source.endpoint.binding* | To use a custom AhcBinding which allows to control how to bind between AHC and Camel. | null | false | MEDIUM
-| *camel.source.endpoint.clientConfig* | To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance. | null | false | MEDIUM
-| *camel.source.endpoint.clientConfigOptions* | To configure the AsyncHttpClientConfig using the key/values from the Map. | null | false | MEDIUM
-| *camel.source.endpoint.clientConfigRealmOptions* | To configure the AsyncHttpClientConfig Realm using the key/values from the Map. | null | false | MEDIUM
-| *camel.source.endpoint.sslContextParameters* | Reference to a org.apache.camel.support.jsse.SSLContextParameters in the Registry. This reference overrides any configured SSLContextParameters at the component level. See Using the JSSE Configuration Utility. Note that configuring this option will override any SSL/TLS configuration options provided through the clientConfig option at the endpoint or component level. | null | false | MEDIUM
-| *camel.component.ahc-wss.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.component.ahc-wss.allowJavaSerializedObject* | 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 | false | MEDIUM
-| *camel.component.ahc-wss.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.ahc-wss.binding* | To use a custom AhcBinding which allows to control how to bind between AHC and Camel. | null | false | MEDIUM
-| *camel.component.ahc-wss.client* | To use a custom AsyncHttpClient | null | false | MEDIUM
-| *camel.component.ahc-wss.clientConfig* | To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance. | null | false | MEDIUM
-| *camel.component.ahc-wss.headerFilterStrategy* | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. | null | false | MEDIUM
-| *camel.component.ahc-wss.sslContextParameters* | 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. | null | false | MEDIUM
-| *camel.component.ahc-wss.useGlobalSslContext Parameters* | Enable usage of global SSL context parameters. | false | false | MEDIUM
-|===
-
-
-
-The camel-ahc-wss source connector has no converters out of the box.
-
-
-
-
-
-The camel-ahc-wss source connector has no transforms out of the box.
-
-
-
-
-
-The camel-ahc-wss source connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-amqp-kafka-connector/src/main/docs/camel-amqp-kafka-sink-connector.adoc b/connectors/camel-amqp-kafka-connector/src/main/docs/camel-amqp-kafka-sink-connector.adoc
deleted file mode 100644
index ef9a9cf..0000000
--- a/connectors/camel-amqp-kafka-connector/src/main/docs/camel-amqp-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,197 +0,0 @@
-// kafka-connector options: START
-[[camel-amqp-kafka-connector-sink]]
-= camel-amqp-kafka-connector sink configuration
-
-Connector Description: Messaging with AMQP protocol using Apache QPid Client.
-
-When using camel-amqp-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-amqp-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.amqp.CamelAmqpSinkConnector
-----
-
-
-The camel-amqp sink connector supports 146 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.destinationType* | The kind of destination to use One of: [queue] [topic] [temp-queue] [temp-topic] | "queue" | false | MEDIUM
-| *camel.sink.path.destinationName* | Name of the queue or topic to use as destination | null | true | HIGH
-| *camel.sink.endpoint.clientId* | 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. | null | false | MEDIUM
-| *camel.sink.endpoint.connectionFactory* | The connection factory to be use. A connection factory must be configured either on the component or endpoint. | null | false | MEDIUM
-| *camel.sink.endpoint.disableReplyTo* | 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 mes [...]
-| *camel.sink.endpoint.durableSubscriptionName* | The durable subscriber name for specifying durable topic subscriptions. The clientId option must be configured as well. | null | false | MEDIUM
-| *camel.sink.endpoint.jmsMessageType* | 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. One of: [Bytes] [Map] [Object] [Stream] [Text] | null | false | MEDIUM
-| *camel.sink.endpoint.replyTo* | Provides an explicit ReplyTo destination (overrides any incoming value of Message.getJMSReplyTo() in consumer). | null | false | MEDIUM
-| *camel.sink.endpoint.testConnectionOnStartup* | 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 | false | MEDIUM
-| *camel.sink.endpoint.deliveryDelay* | Sets delivery delay to use for send calls for JMS. This option requires JMS 2.0 compliant broker. | -1L | false | MEDIUM
-| *camel.sink.endpoint.deliveryMode* | Specifies the delivery mode to be used. Possible values are those defined by javax.jms.DeliveryMode. NON_PERSISTENT = 1 and PERSISTENT = 2. One of: [1] [2] | null | false | MEDIUM
-| *camel.sink.endpoint.deliveryPersistent* | Specifies whether persistent delivery is used by default. | true | false | MEDIUM
-| *camel.sink.endpoint.explicitQosEnabled* | 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" | false | MEDIUM
-| *camel.sink.endpoint.formatDateHeadersToIso8601* | Sets whether JMS date properties should be formatted according to the ISO 8601 standard. | false | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.preserveMessageQos* | 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 explicit [...]
-| *camel.sink.endpoint.priority* | Values greater than 1 specify the message priority when sending (where 1 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. One of: [1] [2] [3] [4] [5] [6] [7] [8] [9] | 4 | false | MEDIUM
-| *camel.sink.endpoint.replyToConcurrentConsumers* | 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 | false | MEDIUM
-| *camel.sink.endpoint.replyToMaxConcurrentConsumers* | 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. | null | false | MEDIUM
-| *camel.sink.endpoint.replyToOnTimeoutMaxConcurrent Consumers* | Specifies the maximum number of concurrent consumers for continue routing when timeout occurred when using request/reply over JMS. | 1 | false | MEDIUM
-| *camel.sink.endpoint.replyToOverride* | 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. | null | false | MEDIUM
-| *camel.sink.endpoint.replyToType* | 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 if [...]
-| *camel.sink.endpoint.requestTimeout* | 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. | 20000L | false | MEDIUM
-| *camel.sink.endpoint.timeToLive* | When sending messages, specifies the time-to-live of the message (in milliseconds). | -1L | false | MEDIUM
-| *camel.sink.endpoint.allowAdditionalHeaders* | 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. | null | false | MEDIUM
-| *camel.sink.endpoint.allowNullBody* | 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 | false | MEDIUM
-| *camel.sink.endpoint.alwaysCopyMessage* | 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 | false | MEDIUM
-| *camel.sink.endpoint.correlationProperty* | 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. | null | false | MEDIUM
-| *camel.sink.endpoint.disableTimeToLive* | 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 the [...]
-| *camel.sink.endpoint.forceSendOriginalMessage* | 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 | false | MEDIUM
-| *camel.sink.endpoint.includeSentJMSMessageID* | 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 | false | MEDIUM
-| *camel.sink.endpoint.replyToCacheLevelName* | 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 queues t [...]
-| *camel.sink.endpoint.replyToDestinationSelectorName* | 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). | null | false | MEDIUM
-| *camel.sink.endpoint.streamMessageTypeEnabled* | 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 StreamMessage [...]
-| *camel.sink.endpoint.allowSerializedHeaders* | 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 | false | MEDIUM
-| *camel.sink.endpoint.artemisStreamingEnabled* | Whether optimizing for Apache Artemis streaming mode. | true | false | MEDIUM
-| *camel.sink.endpoint.asyncStartListener* | 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 is [...]
-| *camel.sink.endpoint.asyncStopListener* | Whether to stop the JmsConsumer message listener asynchronously, when stopping a route. | false | false | MEDIUM
-| *camel.sink.endpoint.destinationResolver* | 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). | null | false | MEDIUM
-| *camel.sink.endpoint.errorHandler* | 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 erro [...]
-| *camel.sink.endpoint.exceptionListener* | Specifies the JMS Exception Listener that is to be notified of any underlying JMS exceptions. | null | false | MEDIUM
-| *camel.sink.endpoint.headerFilterStrategy* | To use a custom HeaderFilterStrategy to filter header to and from Camel message. | null | false | MEDIUM
-| *camel.sink.endpoint.idleConsumerLimit* | Specify the limit for the number of consumers that are allowed to be idle at any given time. | 1 | false | MEDIUM
-| *camel.sink.endpoint.idleTaskExecutionLimit* | 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 | false | MEDIUM
-| *camel.sink.endpoint.includeAllJMSXProperties* | 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 | false | MEDIUM
-| *camel.sink.endpoint.jmsKeyFormatStrategy* | 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 the o [...]
-| *camel.sink.endpoint.mapJmsMessage* | 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 | false | MEDIUM
-| *camel.sink.endpoint.maxMessagesPerTask* | 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 | false | MEDIUM
-| *camel.sink.endpoint.messageConverter* | 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. | null | false | MEDIUM
-| *camel.sink.endpoint.messageCreatedStrategy* | 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. | null | false | MEDIUM
-| *camel.sink.endpoint.messageIdEnabled* | 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 | false | MEDIUM
-| *camel.sink.endpoint.messageListenerContainer 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. | null | false | MEDIUM
-| *camel.sink.endpoint.messageTimestampEnabled* | 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 | false | MEDIUM
-| *camel.sink.endpoint.pubSubNoLocal* | Specifies whether to inhibit the delivery of messages published by its own connection. | false | false | MEDIUM
-| *camel.sink.endpoint.receiveTimeout* | The timeout for receiving messages (in milliseconds). | 1000L | false | MEDIUM
-| *camel.sink.endpoint.recoveryInterval* | 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. | 5000L | false | MEDIUM
-| *camel.sink.endpoint.requestTimeoutCheckerInterval* | 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. | 1000L | false | MEDIUM
-| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used | false | false | MEDIUM
-| *camel.sink.endpoint.transferException* | 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 tak [...]
-| *camel.sink.endpoint.transferExchange* | 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 payload [...]
-| *camel.sink.endpoint.useMessageIDAsCorrelationID* | Specifies whether JMSMessageID should always be used as JMSCorrelationID for InOut messages. | false | false | MEDIUM
-| *camel.sink.endpoint.waitForProvisionCorrelationTo BeUpdatedCounter* | 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 | false | MEDIUM
-| *camel.sink.endpoint.waitForProvisionCorrelationTo BeUpdatedThreadSleepingTime* | Interval in millis to sleep each time while waiting for provisional correlation id to be updated. | 100L | false | MEDIUM
-| *camel.sink.endpoint.password* | Password to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory. | null | false | MEDIUM
-| *camel.sink.endpoint.username* | Username to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory. | null | false | MEDIUM
-| *camel.sink.endpoint.transacted* | Specifies whether to use transacted mode | false | false | MEDIUM
-| *camel.sink.endpoint.transactedInOut* | 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, the [...]
-| *camel.sink.endpoint.lazyCreateTransactionManager* | If true, Camel will create a JmsTransactionManager, if there is no transactionManager injected when option transacted=true. | true | false | MEDIUM
-| *camel.sink.endpoint.transactionManager* | The Spring transaction manager to use. | null | false | MEDIUM
-| *camel.sink.endpoint.transactionName* | The name of the transaction to use. | null | false | MEDIUM
-| *camel.sink.endpoint.transactionTimeout* | The timeout value of the transaction (in seconds), if using transacted mode. | -1 | false | MEDIUM
-| *camel.component.amqp.clientId* | 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. | null | false | MEDIUM
-| *camel.component.amqp.connectionFactory* | The connection factory to be use. A connection factory must be configured either on the component or endpoint. | null | false | MEDIUM
-| *camel.component.amqp.disableReplyTo* | 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 me [...]
-| *camel.component.amqp.durableSubscriptionName* | The durable subscriber name for specifying durable topic subscriptions. The clientId option must be configured as well. | null | false | MEDIUM
-| *camel.component.amqp.includeAmqpAnnotations* | 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 | false | MEDIUM
-| *camel.component.amqp.jmsMessageType* | 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. One of: [Bytes] [Map] [Object] [Stream] [Text] | null | false | MEDIUM
-| *camel.component.amqp.replyTo* | Provides an explicit ReplyTo destination (overrides any incoming value of Message.getJMSReplyTo() in consumer). | null | false | MEDIUM
-| *camel.component.amqp.testConnectionOnStartup* | 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 | false | MEDIUM
-| *camel.component.amqp.deliveryDelay* | Sets delivery delay to use for send calls for JMS. This option requires JMS 2.0 compliant broker. | -1L | false | MEDIUM
-| *camel.component.amqp.deliveryMode* | Specifies the delivery mode to be used. Possible values are those defined by javax.jms.DeliveryMode. NON_PERSISTENT = 1 and PERSISTENT = 2. One of: [1] [2] | null | false | MEDIUM
-| *camel.component.amqp.deliveryPersistent* | Specifies whether persistent delivery is used by default. | true | false | MEDIUM
-| *camel.component.amqp.explicitQosEnabled* | 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" | false | MEDIUM
-| *camel.component.amqp.formatDateHeadersToIso8601* | Sets whether JMS date properties should be formatted according to the ISO 8601 standard. | false | false | MEDIUM
-| *camel.component.amqp.lazyStartProducer* | 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 cr [...]
-| *camel.component.amqp.preserveMessageQos* | 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 explici [...]
-| *camel.component.amqp.priority* | Values greater than 1 specify the message priority when sending (where 1 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. One of: [1] [2] [3] [4] [5] [6] [7] [8] [9] | 4 | false | MEDIUM
-| *camel.component.amqp.replyToConcurrentConsumers* | 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 | false | MEDIUM
-| *camel.component.amqp.replyToMaxConcurrentConsumers* | 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. | null | false | MEDIUM
-| *camel.component.amqp.replyToOnTimeoutMaxConcurrent Consumers* | Specifies the maximum number of concurrent consumers for continue routing when timeout occurred when using request/reply over JMS. | 1 | false | MEDIUM
-| *camel.component.amqp.replyToOverride* | 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. | null | false | MEDIUM
-| *camel.component.amqp.replyToType* | 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 i [...]
-| *camel.component.amqp.requestTimeout* | 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. | 20000L | false | MEDIUM
-| *camel.component.amqp.timeToLive* | When sending messages, specifies the time-to-live of the message (in milliseconds). | -1L | false | MEDIUM
-| *camel.component.amqp.allowAdditionalHeaders* | 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. | null | false | MEDIUM
-| *camel.component.amqp.allowNullBody* | 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 | false | MEDIUM
-| *camel.component.amqp.alwaysCopyMessage* | 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 | false | MEDIUM
-| *camel.component.amqp.correlationProperty* | 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. | null | false | MEDIUM
-| *camel.component.amqp.disableTimeToLive* | 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 the [...]
-| *camel.component.amqp.forceSendOriginalMessage* | 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 | false | MEDIUM
-| *camel.component.amqp.includeSentJMSMessageID* | 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 | false | MEDIUM
-| *camel.component.amqp.replyToCacheLevelName* | 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 queues [...]
-| *camel.component.amqp.replyToDestinationSelector 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). | null | false | MEDIUM
-| *camel.component.amqp.streamMessageTypeEnabled* | 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 StreamMessag [...]
-| *camel.component.amqp.allowAutoWiredConnection 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 | false | MEDIUM
-| *camel.component.amqp.allowAutoWiredDestination 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 | false | MEDIUM
-| *camel.component.amqp.allowSerializedHeaders* | 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 | false | MEDIUM
-| *camel.component.amqp.artemisStreamingEnabled* | Whether optimizing for Apache Artemis streaming mode. | true | false | MEDIUM
-| *camel.component.amqp.asyncStartListener* | 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 is [...]
-| *camel.component.amqp.asyncStopListener* | Whether to stop the JmsConsumer message listener asynchronously, when stopping a route. | false | false | MEDIUM
-| *camel.component.amqp.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.amqp.configuration* | To use a shared JMS configuration | null | false | MEDIUM
-| *camel.component.amqp.destinationResolver* | 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). | null | false | MEDIUM
-| *camel.component.amqp.errorHandler* | 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.amqp.exceptionListener* | Specifies the JMS Exception Listener that is to be notified of any underlying JMS exceptions. | null | false | MEDIUM
-| *camel.component.amqp.idleConsumerLimit* | Specify the limit for the number of consumers that are allowed to be idle at any given time. | 1 | false | MEDIUM
-| *camel.component.amqp.idleTaskExecutionLimit* | 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 | false | MEDIUM
-| *camel.component.amqp.includeAllJMSXProperties* | 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 | false | MEDIUM
-| *camel.component.amqp.jmsKeyFormatStrategy* | 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 the [...]
-| *camel.component.amqp.mapJmsMessage* | 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 | false | MEDIUM
-| *camel.component.amqp.maxMessagesPerTask* | 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 | false | MEDIUM
-| *camel.component.amqp.messageConverter* | 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. | null | false | MEDIUM
-| *camel.component.amqp.messageCreatedStrategy* | 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. | null | false | MEDIUM
-| *camel.component.amqp.messageIdEnabled* | 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 | false | MEDIUM
-| *camel.component.amqp.messageListenerContainer 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. | null | false | MEDIUM
-| *camel.component.amqp.messageTimestampEnabled* | 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 | false | MEDIUM
-| *camel.component.amqp.pubSubNoLocal* | Specifies whether to inhibit the delivery of messages published by its own connection. | false | false | MEDIUM
-| *camel.component.amqp.queueBrowseStrategy* | To use a custom QueueBrowseStrategy when browsing queues | null | false | MEDIUM
-| *camel.component.amqp.receiveTimeout* | The timeout for receiving messages (in milliseconds). | 1000L | false | MEDIUM
-| *camel.component.amqp.recoveryInterval* | 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. | 5000L | false | MEDIUM
-| *camel.component.amqp.requestTimeoutCheckerInterval* | 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. | 1000L | false | MEDIUM
-| *camel.component.amqp.synchronous* | Sets whether synchronous processing should be strictly used | false | false | MEDIUM
-| *camel.component.amqp.transferException* | 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.amqp.transferExchange* | 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.amqp.useMessageIDAsCorrelationID* | Specifies whether JMSMessageID should always be used as JMSCorrelationID for InOut messages. | false | false | MEDIUM
-| *camel.component.amqp.waitForProvisionCorrelationTo BeUpdatedCounter* | 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 | false | MEDIUM
-| *camel.component.amqp.waitForProvisionCorrelationTo BeUpdatedThreadSleepingTime* | Interval in millis to sleep each time while waiting for provisional correlation id to be updated. | 100L | false | MEDIUM
-| *camel.component.amqp.headerFilterStrategy* | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. | null | false | MEDIUM
-| *camel.component.amqp.password* | Password to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory. | null | false | MEDIUM
-| *camel.component.amqp.username* | Username to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory. | null | false | MEDIUM
-| *camel.component.amqp.transacted* | Specifies whether to use transacted mode | false | false | MEDIUM
-| *camel.component.amqp.transactedInOut* | 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, th [...]
-| *camel.component.amqp.lazyCreateTransactionManager* | If true, Camel will create a JmsTransactionManager, if there is no transactionManager injected when option transacted=true. | true | false | MEDIUM
-| *camel.component.amqp.transactionManager* | The Spring transaction manager to use. | null | false | MEDIUM
-| *camel.component.amqp.transactionName* | The name of the transaction to use. | null | false | MEDIUM
-| *camel.component.amqp.transactionTimeout* | The timeout value of the transaction (in seconds), if using transacted mode. | -1 | false | MEDIUM
-|===
-
-
-
-The camel-amqp sink connector has no converters out of the box.
-
-
-
-
-
-The camel-amqp sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-amqp sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-amqp-kafka-connector/src/main/docs/camel-amqp-kafka-source-connector.adoc b/connectors/camel-amqp-kafka-connector/src/main/docs/camel-amqp-kafka-source-connector.adoc
deleted file mode 100644
index 689012f..0000000
--- a/connectors/camel-amqp-kafka-connector/src/main/docs/camel-amqp-kafka-source-connector.adoc
+++ /dev/null
@@ -1,197 +0,0 @@
-// kafka-connector options: START
-[[camel-amqp-kafka-connector-source]]
-= camel-amqp-kafka-connector source configuration
-
-Connector description: Messaging with AMQP protocol using Apache QPid Client.
-
-When using camel-amqp-kafka-connector as source make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-amqp-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Source connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.amqp.CamelAmqpSourceConnector
-----
-
-
-The camel-amqp source connector supports 146 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.source.path.destinationType* | The kind of destination to use One of: [queue] [topic] [temp-queue] [temp-topic] | "queue" | false | MEDIUM
-| *camel.source.path.destinationName* | Name of the queue or topic to use as destination | null | true | HIGH
-| *camel.source.endpoint.clientId* | 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. | null | false | MEDIUM
-| *camel.source.endpoint.connectionFactory* | The connection factory to be use. A connection factory must be configured either on the component or endpoint. | null | false | MEDIUM
-| *camel.source.endpoint.disableReplyTo* | 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.source.endpoint.durableSubscriptionName* | The durable subscriber name for specifying durable topic subscriptions. The clientId option must be configured as well. | null | false | MEDIUM
-| *camel.source.endpoint.jmsMessageType* | 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. One of: [Bytes] [Map] [Object] [Stream] [Text] | null | false | MEDIUM
-| *camel.source.endpoint.replyTo* | Provides an explicit ReplyTo destination (overrides any incoming value of Message.getJMSReplyTo() in consumer). | null | false | MEDIUM
-| *camel.source.endpoint.testConnectionOnStartup* | 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 | false | MEDIUM
-| *camel.source.endpoint.acknowledgementModeName* | The JMS acknowledgement name, which is one of: SESSION_TRANSACTED, CLIENT_ACKNOWLEDGE, AUTO_ACKNOWLEDGE, DUPS_OK_ACKNOWLEDGE One of: [SESSION_TRANSACTED] [CLIENT_ACKNOWLEDGE] [AUTO_ACKNOWLEDGE] [DUPS_OK_ACKNOWLEDGE] | "AUTO_ACKNOWLEDGE" | false | MEDIUM
-| *camel.source.endpoint.artemisConsumerPriority* | Consumer priorities allow you to ensure that high priority consumers receive messages while they are active. Normally, active consumers connected to a queue receive messages from it in a round-robin fashion. When consumer priorities are in use, messages are delivered round-robin if multiple active consumers exist with the same high priority. Messages will only going to lower priority consumers when the high priority consumers do not hav [...]
-| *camel.source.endpoint.asyncConsumer* | 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.source.endpoint.autoStartup* | Specifies whether the consumer container should auto-startup. | true | false | MEDIUM
-| *camel.source.endpoint.cacheLevel* | Sets the cache level by ID for the underlying JMS resources. See cacheLevelName option for more details. | null | false | MEDIUM
-| *camel.source.endpoint.cacheLevelName* | 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. One of: [CACHE_AUTO] [CACHE_CONNECTION] [CACHE_CONSUMER] [CACHE_NONE] [CACHE_SESSION] | "CACHE_AUTO" | false | MEDIUM
-| *camel.source.endpoint.concurrentConsumers* | 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 | false | MEDIUM
-| *camel.source.endpoint.maxConcurrentConsumers* | 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. | null | false | MEDIUM
-| *camel.source.endpoint.replyToDeliveryPersistent* | Specifies whether to use persistent delivery by default for replies. | true | false | MEDIUM
-| *camel.source.endpoint.selector* | Sets the JMS selector to use | null | false | MEDIUM
-| *camel.source.endpoint.subscriptionDurable* | 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.source.endpoint.subscriptionName* | 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.source.endpoint.subscriptionShared* | 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.source.endpoint.acceptMessagesWhileStopping* | 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.source.endpoint.allowReplyManagerQuickStop* | 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 flag [...]
-| *camel.source.endpoint.consumerType* | 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.source.endpoint.defaultTaskExecutorType* | 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 an [...]
-| *camel.source.endpoint.eagerLoadingOfProperties* | 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 | false | MEDIUM
-| *camel.source.endpoint.eagerPoisonBody* | 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}" | false | MEDIUM
-| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | false | MEDIUM
-| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | false | MEDIUM
-| *camel.source.endpoint.exposeListenerSession* | Specifies whether the listener session should be exposed when consuming messages. | false | false | MEDIUM
-| *camel.source.endpoint.replyToSameDestination 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 | false | MEDIUM
-| *camel.source.endpoint.taskExecutor* | Allows you to specify a custom task executor for consuming messages. | null | false | MEDIUM
-| *camel.source.endpoint.allowSerializedHeaders* | 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 | false | MEDIUM
-| *camel.source.endpoint.artemisStreamingEnabled* | Whether optimizing for Apache Artemis streaming mode. | true | false | MEDIUM
-| *camel.source.endpoint.asyncStartListener* | 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.source.endpoint.asyncStopListener* | Whether to stop the JmsConsumer message listener asynchronously, when stopping a route. | false | false | MEDIUM
-| *camel.source.endpoint.destinationResolver* | 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). | null | false | MEDIUM
-| *camel.source.endpoint.errorHandler* | 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.source.endpoint.exceptionListener* | Specifies the JMS Exception Listener that is to be notified of any underlying JMS exceptions. | null | false | MEDIUM
-| *camel.source.endpoint.headerFilterStrategy* | To use a custom HeaderFilterStrategy to filter header to and from Camel message. | null | false | MEDIUM
-| *camel.source.endpoint.idleConsumerLimit* | Specify the limit for the number of consumers that are allowed to be idle at any given time. | 1 | false | MEDIUM
-| *camel.source.endpoint.idleTaskExecutionLimit* | 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 | false | MEDIUM
-| *camel.source.endpoint.includeAllJMSXProperties* | 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 | false | MEDIUM
-| *camel.source.endpoint.jmsKeyFormatStrategy* | 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 the [...]
-| *camel.source.endpoint.mapJmsMessage* | 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 | false | MEDIUM
-| *camel.source.endpoint.maxMessagesPerTask* | 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 | false | MEDIUM
-| *camel.source.endpoint.messageConverter* | 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. | null | false | MEDIUM
-| *camel.source.endpoint.messageCreatedStrategy* | 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. | null | false | MEDIUM
-| *camel.source.endpoint.messageIdEnabled* | 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 | false | MEDIUM
-| *camel.source.endpoint.messageListenerContainer 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. | null | false | MEDIUM
-| *camel.source.endpoint.messageTimestampEnabled* | 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 | false | MEDIUM
-| *camel.source.endpoint.pubSubNoLocal* | Specifies whether to inhibit the delivery of messages published by its own connection. | false | false | MEDIUM
-| *camel.source.endpoint.receiveTimeout* | The timeout for receiving messages (in milliseconds). | 1000L | false | MEDIUM
-| *camel.source.endpoint.recoveryInterval* | 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. | 5000L | false | MEDIUM
-| *camel.source.endpoint.requestTimeoutChecker 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. | 1000L | false | MEDIUM
-| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used | false | false | MEDIUM
-| *camel.source.endpoint.transferException* | 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.source.endpoint.transferExchange* | 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.source.endpoint.useMessageIDAsCorrelationID* | Specifies whether JMSMessageID should always be used as JMSCorrelationID for InOut messages. | false | false | MEDIUM
-| *camel.source.endpoint.waitForProvisionCorrelation ToBeUpdatedCounter* | 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 | false | MEDIUM
-| *camel.source.endpoint.waitForProvisionCorrelation ToBeUpdatedThreadSleepingTime* | Interval in millis to sleep each time while waiting for provisional correlation id to be updated. | 100L | false | MEDIUM
-| *camel.source.endpoint.errorHandlerLoggingLevel* | Allows to configure the default errorHandler logging level for logging uncaught exceptions. One of: [TRACE] [DEBUG] [INFO] [WARN] [ERROR] [OFF] | "WARN" | false | MEDIUM
-| *camel.source.endpoint.errorHandlerLogStackTrace* | Allows to control whether stacktraces should be logged or not, by the default errorHandler. | true | false | MEDIUM
-| *camel.source.endpoint.password* | Password to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory. | null | false | MEDIUM
-| *camel.source.endpoint.username* | Username to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory. | null | false | MEDIUM
-| *camel.source.endpoint.transacted* | Specifies whether to use transacted mode | false | false | MEDIUM
-| *camel.source.endpoint.transactedInOut* | 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.source.endpoint.lazyCreateTransactionManager* | If true, Camel will create a JmsTransactionManager, if there is no transactionManager injected when option transacted=true. | true | false | MEDIUM
-| *camel.source.endpoint.transactionManager* | The Spring transaction manager to use. | null | false | MEDIUM
-| *camel.source.endpoint.transactionName* | The name of the transaction to use. | null | false | MEDIUM
-| *camel.source.endpoint.transactionTimeout* | The timeout value of the transaction (in seconds), if using transacted mode. | -1 | false | MEDIUM
-| *camel.component.amqp.clientId* | 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. | null | false | MEDIUM
-| *camel.component.amqp.connectionFactory* | The connection factory to be use. A connection factory must be configured either on the component or endpoint. | null | false | MEDIUM
-| *camel.component.amqp.disableReplyTo* | 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 me [...]
-| *camel.component.amqp.durableSubscriptionName* | The durable subscriber name for specifying durable topic subscriptions. The clientId option must be configured as well. | null | false | MEDIUM
-| *camel.component.amqp.includeAmqpAnnotations* | 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 | false | MEDIUM
-| *camel.component.amqp.jmsMessageType* | 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. One of: [Bytes] [Map] [Object] [Stream] [Text] | null | false | MEDIUM
-| *camel.component.amqp.replyTo* | Provides an explicit ReplyTo destination (overrides any incoming value of Message.getJMSReplyTo() in consumer). | null | false | MEDIUM
-| *camel.component.amqp.testConnectionOnStartup* | 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 | false | MEDIUM
-| *camel.component.amqp.acknowledgementModeName* | The JMS acknowledgement name, which is one of: SESSION_TRANSACTED, CLIENT_ACKNOWLEDGE, AUTO_ACKNOWLEDGE, DUPS_OK_ACKNOWLEDGE One of: [SESSION_TRANSACTED] [CLIENT_ACKNOWLEDGE] [AUTO_ACKNOWLEDGE] [DUPS_OK_ACKNOWLEDGE] | "AUTO_ACKNOWLEDGE" | false | MEDIUM
-| *camel.component.amqp.artemisConsumerPriority* | Consumer priorities allow you to ensure that high priority consumers receive messages while they are active. Normally, active consumers connected to a queue receive messages from it in a round-robin fashion. When consumer priorities are in use, messages are delivered round-robin if multiple active consumers exist with the same high priority. Messages will only going to lower priority consumers when the high priority consumers do not have [...]
-| *camel.component.amqp.asyncConsumer* | 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.autoStartup* | Specifies whether the consumer container should auto-startup. | true | false | MEDIUM
-| *camel.component.amqp.cacheLevel* | Sets the cache level by ID for the underlying JMS resources. See cacheLevelName option for more details. | null | false | MEDIUM
-| *camel.component.amqp.cacheLevelName* | 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. One of: [CACHE_AUTO] [CACHE_CONNECTION] [CACHE_CONSUMER] [CACHE_NONE] [CACHE_SESSION] | "CACHE_AUTO" | false | MEDIUM
-| *camel.component.amqp.concurrentConsumers* | 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 | false | MEDIUM
-| *camel.component.amqp.maxConcurrentConsumers* | 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. | null | false | MEDIUM
-| *camel.component.amqp.replyToDeliveryPersistent* | Specifies whether to use persistent delivery by default for replies. | true | false | MEDIUM
-| *camel.component.amqp.selector* | Sets the JMS selector to use | null | false | MEDIUM
-| *camel.component.amqp.subscriptionDurable* | 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.amqp.subscriptionName* | 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.amqp.subscriptionShared* | 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.amqp.acceptMessagesWhileStopping* | 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 q [...]
-| *camel.component.amqp.allowReplyManagerQuickStop* | 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 flag. [...]
-| *camel.component.amqp.consumerType* | 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.amqp.defaultTaskExecutorType* | 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 and [...]
-| *camel.component.amqp.eagerLoadingOfProperties* | 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 | false | MEDIUM
-| *camel.component.amqp.eagerPoisonBody* | 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}" | false | MEDIUM
-| *camel.component.amqp.exposeListenerSession* | Specifies whether the listener session should be exposed when consuming messages. | false | false | MEDIUM
-| *camel.component.amqp.replyToSameDestinationAllowed* | 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 | false | MEDIUM
-| *camel.component.amqp.taskExecutor* | Allows you to specify a custom task executor for consuming messages. | null | false | MEDIUM
-| *camel.component.amqp.allowAutoWiredConnection 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 | false | MEDIUM
-| *camel.component.amqp.allowAutoWiredDestination 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 | false | MEDIUM
-| *camel.component.amqp.allowSerializedHeaders* | 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 | false | MEDIUM
-| *camel.component.amqp.artemisStreamingEnabled* | Whether optimizing for Apache Artemis streaming mode. | true | false | MEDIUM
-| *camel.component.amqp.asyncStartListener* | 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 is [...]
-| *camel.component.amqp.asyncStopListener* | Whether to stop the JmsConsumer message listener asynchronously, when stopping a route. | false | false | MEDIUM
-| *camel.component.amqp.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.amqp.configuration* | To use a shared JMS configuration | null | false | MEDIUM
-| *camel.component.amqp.destinationResolver* | 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). | null | false | MEDIUM
-| *camel.component.amqp.errorHandler* | 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.amqp.exceptionListener* | Specifies the JMS Exception Listener that is to be notified of any underlying JMS exceptions. | null | false | MEDIUM
-| *camel.component.amqp.idleConsumerLimit* | Specify the limit for the number of consumers that are allowed to be idle at any given time. | 1 | false | MEDIUM
-| *camel.component.amqp.idleTaskExecutionLimit* | 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 | false | MEDIUM
-| *camel.component.amqp.includeAllJMSXProperties* | 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 | false | MEDIUM
-| *camel.component.amqp.jmsKeyFormatStrategy* | 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 the [...]
-| *camel.component.amqp.mapJmsMessage* | 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 | false | MEDIUM
-| *camel.component.amqp.maxMessagesPerTask* | 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 | false | MEDIUM
-| *camel.component.amqp.messageConverter* | 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. | null | false | MEDIUM
-| *camel.component.amqp.messageCreatedStrategy* | 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. | null | false | MEDIUM
-| *camel.component.amqp.messageIdEnabled* | 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 | false | MEDIUM
-| *camel.component.amqp.messageListenerContainer 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. | null | false | MEDIUM
-| *camel.component.amqp.messageTimestampEnabled* | 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 | false | MEDIUM
-| *camel.component.amqp.pubSubNoLocal* | Specifies whether to inhibit the delivery of messages published by its own connection. | false | false | MEDIUM
-| *camel.component.amqp.queueBrowseStrategy* | To use a custom QueueBrowseStrategy when browsing queues | null | false | MEDIUM
-| *camel.component.amqp.receiveTimeout* | The timeout for receiving messages (in milliseconds). | 1000L | false | MEDIUM
-| *camel.component.amqp.recoveryInterval* | 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. | 5000L | false | MEDIUM
-| *camel.component.amqp.requestTimeoutCheckerInterval* | 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. | 1000L | false | MEDIUM
-| *camel.component.amqp.synchronous* | Sets whether synchronous processing should be strictly used | false | false | MEDIUM
-| *camel.component.amqp.transferException* | 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.amqp.transferExchange* | 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.amqp.useMessageIDAsCorrelationID* | Specifies whether JMSMessageID should always be used as JMSCorrelationID for InOut messages. | false | false | MEDIUM
-| *camel.component.amqp.waitForProvisionCorrelationTo BeUpdatedCounter* | 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 | false | MEDIUM
-| *camel.component.amqp.waitForProvisionCorrelationTo BeUpdatedThreadSleepingTime* | Interval in millis to sleep each time while waiting for provisional correlation id to be updated. | 100L | false | MEDIUM
-| *camel.component.amqp.headerFilterStrategy* | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. | null | false | MEDIUM
-| *camel.component.amqp.errorHandlerLoggingLevel* | Allows to configure the default errorHandler logging level for logging uncaught exceptions. One of: [TRACE] [DEBUG] [INFO] [WARN] [ERROR] [OFF] | "WARN" | false | MEDIUM
-| *camel.component.amqp.errorHandlerLogStackTrace* | Allows to control whether stacktraces should be logged or not, by the default errorHandler. | true | false | MEDIUM
-| *camel.component.amqp.password* | Password to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory. | null | false | MEDIUM
-| *camel.component.amqp.username* | Username to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory. | null | false | MEDIUM
-| *camel.component.amqp.transacted* | Specifies whether to use transacted mode | false | false | MEDIUM
-| *camel.component.amqp.transactedInOut* | 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, th [...]
-| *camel.component.amqp.lazyCreateTransactionManager* | If true, Camel will create a JmsTransactionManager, if there is no transactionManager injected when option transacted=true. | true | false | MEDIUM
-| *camel.component.amqp.transactionManager* | The Spring transaction manager to use. | null | false | MEDIUM
-| *camel.component.amqp.transactionName* | The name of the transaction to use. | null | false | MEDIUM
-| *camel.component.amqp.transactionTimeout* | The timeout value of the transaction (in seconds), if using transacted mode. | -1 | false | MEDIUM
-|===
-
-
-
-The camel-amqp source connector has no converters out of the box.
-
-
-
-
-
-The camel-amqp source connector has no transforms out of the box.
-
-
-
-
-
-The camel-amqp source connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-arangodb-kafka-connector/src/main/docs/camel-arangodb-kafka-sink-connector.adoc b/connectors/camel-arangodb-kafka-connector/src/main/docs/camel-arangodb-kafka-sink-connector.adoc
deleted file mode 100644
index 01a6e94..0000000
--- a/connectors/camel-arangodb-kafka-connector/src/main/docs/camel-arangodb-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,74 +0,0 @@
-// kafka-connector options: START
-[[camel-arangodb-kafka-connector-sink]]
-= camel-arangodb-kafka-connector sink configuration
-
-Connector Description: Perform operations on ArangoDb when used as a Document Database, or as a Graph Database
-
-When using camel-arangodb-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-arangodb-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.arangodb.CamelArangodbSinkConnector
-----
-
-
-The camel-arangodb sink connector supports 23 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.database* | database name | null | true | HIGH
-| *camel.sink.endpoint.documentCollection* | 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). | null | false | MEDIUM
-| *camel.sink.endpoint.edgeCollection* | 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. | null | false | MEDIUM
-| *camel.sink.endpoint.graph* | Graph name, when using ArangoDb as a Graph Database. Combine this attribute with one of the two attributes vertexCollection and edgeCollection. | null | false | MEDIUM
-| *camel.sink.endpoint.host* | ArangoDB host. If host and port are default, this field is Optional. | null | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.operation* | Operations to perform on ArangoDb. For the operation AQL_QUERY, no need to specify a collection or graph. One of: [SAVE_DOCUMENT] [FIND_DOCUMENT_BY_KEY] [UPDATE_DOCUMENT] [DELETE_DOCUMENT] [AQL_QUERY] [SAVE_VERTEX] [FIND_VERTEX_BY_KEY] [UPDATE_VERTEX] [DELETE_VERTEX] [SAVE_EDGE] [FIND_EDGE_BY_KEY] [UPDATE_EDGE] [DELETE_EDGE] | null | false | MEDIUM
-| *camel.sink.endpoint.port* | ArangoDB exposed port. If host and port are default, this field is Optional. | null | false | MEDIUM
-| *camel.sink.endpoint.vertexCollection* | 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. | null | false | MEDIUM
-| *camel.sink.endpoint.password* | ArangoDB password. If user and password are default, this field is Optional. | null | false | MEDIUM
-| *camel.sink.endpoint.user* | ArangoDB user. If user and password are default, this field is Optional. | null | false | MEDIUM
-| *camel.component.arangodb.configuration* | Component configuration | null | false | MEDIUM
-| *camel.component.arangodb.documentCollection* | 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). | null | false | MEDIUM
-| *camel.component.arangodb.edgeCollection* | 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. | null | false | MEDIUM
-| *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. | null | false | MEDIUM
-| *camel.component.arangodb.host* | ArangoDB host. If host and port are default, this field is Optional. | null | false | MEDIUM
-| *camel.component.arangodb.lazyStartProducer* | 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.arangodb.operation* | Operations to perform on ArangoDb. For the operation AQL_QUERY, no need to specify a collection or graph. One of: [SAVE_DOCUMENT] [FIND_DOCUMENT_BY_KEY] [UPDATE_DOCUMENT] [DELETE_DOCUMENT] [AQL_QUERY] [SAVE_VERTEX] [FIND_VERTEX_BY_KEY] [UPDATE_VERTEX] [DELETE_VERTEX] [SAVE_EDGE] [FIND_EDGE_BY_KEY] [UPDATE_EDGE] [DELETE_EDGE] | null | false | MEDIUM
-| *camel.component.arangodb.port* | ArangoDB exposed port. If host and port are default, this field is Optional. | null | false | MEDIUM
-| *camel.component.arangodb.vertexCollection* | 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. | null | false | MEDIUM
-| *camel.component.arangodb.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.arangodb.password* | ArangoDB password. If user and password are default, this field is Optional. | null | false | MEDIUM
-| *camel.component.arangodb.user* | ArangoDB user. If user and password are default, this field is Optional. | null | false | MEDIUM
-|===
-
-
-
-The camel-arangodb sink connector has no converters out of the box.
-
-
-
-
-
-The camel-arangodb sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-arangodb sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-as2-kafka-connector/src/main/docs/camel-as2-kafka-sink-connector.adoc b/connectors/camel-as2-kafka-connector/src/main/docs/camel-as2-kafka-sink-connector.adoc
deleted file mode 100644
index 32f4ade..0000000
--- a/connectors/camel-as2-kafka-connector/src/main/docs/camel-as2-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,84 +0,0 @@
-// kafka-connector options: START
-[[camel-as2-kafka-connector-sink]]
-= camel-as2-kafka-connector sink configuration
-
-Connector Description: Transfer data securely and reliably using the AS2 protocol (RFC4130).
-
-When using camel-as2-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-as2-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.as2.CamelAs2SinkConnector
-----
-
-
-The camel-as2 sink connector supports 33 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.apiName* | What kind of operation to perform One of: [CLIENT] [SERVER] | null | true | HIGH
-| *camel.sink.path.methodName* | What sub operation to use for the selected operation | null | true | HIGH
-| *camel.sink.endpoint.as2From* | The value of the AS2From header of AS2 message. | null | false | MEDIUM
-| *camel.sink.endpoint.as2MessageStructure* | The structure of AS2 Message. One of: PLAIN - No encryption, no signature, SIGNED - No encryption, signature, ENCRYPTED - Encryption, no signature, ENCRYPTED_SIGNED - Encryption, signature One of: [PLAIN] [SIGNED] [ENCRYPTED] [SIGNED_ENCRYPTED] [PLAIN_COMPRESSED] [SIGNED_COMPRESSED] [ENCRYPTED_COMPRESSED] [ENCRYPTED_COMPRESSED_SIGNED] | null | false | MEDIUM
-| *camel.sink.endpoint.as2To* | The value of the AS2To header of AS2 message. | null | false | MEDIUM
-| *camel.sink.endpoint.as2Version* | The version of the AS2 protocol. One of: [1.0] [1.1] | "1.1" | false | MEDIUM
-| *camel.sink.endpoint.clientFqdn* | The Client Fully Qualified Domain Name (FQDN). Used in message ids sent by endpoint. | "camel.apache.org" | false | MEDIUM
-| *camel.sink.endpoint.compressionAlgorithm* | The algorithm used to compress EDI message. One of: [ZLIB] | null | false | MEDIUM
-| *camel.sink.endpoint.decryptingPrivateKey* | The key used to encrypt the EDI message. | null | false | MEDIUM
-| *camel.sink.endpoint.dispositionNotificationTo* | The value of the Disposition-Notification-To header. Assigning a value to this parameter requests a message disposition notification (MDN) for the AS2 message. | null | false | MEDIUM
-| *camel.sink.endpoint.ediMessageTransferEncoding* | The transfer encoding of EDI message. | null | false | MEDIUM
-| *camel.sink.endpoint.ediMessageType* | The content type of EDI message. One of application/edifact, application/edi-x12, application/edi-consent | null | false | MEDIUM
-| *camel.sink.endpoint.encryptingAlgorithm* | The algorithm used to encrypt EDI message. One of: [AES128_CBC] [AES192_CBC] [AES256_CBC] [AES128_CCM] [AES192_CCM] [AES256_CCM] [AES128_GCM] [AES192_GCM] [AES256_GCM] [CAMELLIA128_CBC] [CAMELLIA192_CBC] [CAMELLIA256_CBC] [CAST5_CBC] [DES_CBC] [DES_EDE3_CBC] [GOST28147_GCFB] [IDEA_CBC] [RC2_CBC] [RC4] [SEED_CBC] | null | false | MEDIUM
-| *camel.sink.endpoint.encryptingCertificateChain* | The chain of certificates used to encrypt EDI message. | null | false | MEDIUM
-| *camel.sink.endpoint.from* | The value of the From header of AS2 message. | null | false | MEDIUM
-| *camel.sink.endpoint.inBody* | Sets the name of a parameter to be passed in the exchange In Body | null | false | MEDIUM
-| *camel.sink.endpoint.mdnMessageTemplate* | The template used to format MDN message | null | false | MEDIUM
-| *camel.sink.endpoint.requestUri* | The request URI of EDI message. | "/" | false | MEDIUM
-| *camel.sink.endpoint.server* | The value included in the Server message header identifying the AS2 Server. | "Camel AS2 Server Endpoint" | false | MEDIUM
-| *camel.sink.endpoint.serverFqdn* | The Server Fully Qualified Domain Name (FQDN). Used in message ids sent by endpoint. | "camel.apache.org" | false | MEDIUM
-| *camel.sink.endpoint.serverPortNumber* | The port number of server. | null | false | MEDIUM
-| *camel.sink.endpoint.signedReceiptMicAlgorithms* | The list of algorithms, in order of preference, requested to generate a message integrity check (MIC) returned in message dispostion notification (MDN) | null | false | MEDIUM
-| *camel.sink.endpoint.signingAlgorithm* | The algorithm used to sign EDI message. One of: [SHA3_224WITHRSA] [SHA3_256WITHRSA] [SHA3_384withRSA] [SHA3_512WITHRSA] [MD5WITHRSA] [SHA1WITHRSA] [MD2WITHRSA] [SHA224WITHRSA] [SHA256WITHRSA] [SHA384WITHRSA] [SHA512WITHRSA] [RIPEMD128WITHRSA] [RIPEMD160WITHRSA] [RIPEMD256WITHRSA] [SHA224WITHDSA] [SHA256WITHDSA] [SHA384WITHDSA] [SHA512WITHDSA] [SHA3_224WITHDSA] [SHA3_256WITHDSA] [SHA3_384WITHDSA] [SHA3_512WITHDSA] [SHA1WITHDSA] [SHA3_224WITHECDSA [...]
-| *camel.sink.endpoint.signingCertificateChain* | The chain of certificates used to sign EDI message. | null | false | MEDIUM
-| *camel.sink.endpoint.signingPrivateKey* | The key used to sign the EDI message. | null | false | MEDIUM
-| *camel.sink.endpoint.subject* | The value of Subject header of AS2 message. | null | false | MEDIUM
-| *camel.sink.endpoint.targetHostname* | The host name (IP or DNS name) of target host. | null | false | MEDIUM
-| *camel.sink.endpoint.targetPortNumber* | The port number of target host. -1 indicates the scheme default port. | null | false | MEDIUM
-| *camel.sink.endpoint.userAgent* | The value included in the User-Agent message header identifying the AS2 user agent. | "Camel AS2 Client Endpoint" | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.component.as2.lazyStartProducer* | 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 cre [...]
-| *camel.component.as2.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.as2.configuration* | Component configuration | null | false | MEDIUM
-|===
-
-
-
-The camel-as2 sink connector has no converters out of the box.
-
-
-
-
-
-The camel-as2 sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-as2 sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-as2-kafka-connector/src/main/docs/camel-as2-kafka-source-connector.adoc b/connectors/camel-as2-kafka-connector/src/main/docs/camel-as2-kafka-source-connector.adoc
deleted file mode 100644
index 53cb370..0000000
--- a/connectors/camel-as2-kafka-connector/src/main/docs/camel-as2-kafka-source-connector.adoc
+++ /dev/null
@@ -1,85 +0,0 @@
-// kafka-connector options: START
-[[camel-as2-kafka-connector-source]]
-= camel-as2-kafka-connector source configuration
-
-Connector description: Transfer data securely and reliably using the AS2 protocol (RFC4130).
-
-When using camel-as2-kafka-connector as source make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-as2-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Source connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.as2.CamelAs2SourceConnector
-----
-
-
-The camel-as2 source connector supports 34 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.source.path.apiName* | What kind of operation to perform One of: [CLIENT] [SERVER] | null | true | HIGH
-| *camel.source.path.methodName* | What sub operation to use for the selected operation | null | true | HIGH
-| *camel.source.endpoint.as2From* | The value of the AS2From header of AS2 message. | null | false | MEDIUM
-| *camel.source.endpoint.as2MessageStructure* | The structure of AS2 Message. One of: PLAIN - No encryption, no signature, SIGNED - No encryption, signature, ENCRYPTED - Encryption, no signature, ENCRYPTED_SIGNED - Encryption, signature One of: [PLAIN] [SIGNED] [ENCRYPTED] [SIGNED_ENCRYPTED] [PLAIN_COMPRESSED] [SIGNED_COMPRESSED] [ENCRYPTED_COMPRESSED] [ENCRYPTED_COMPRESSED_SIGNED] | null | false | MEDIUM
-| *camel.source.endpoint.as2To* | The value of the AS2To header of AS2 message. | null | false | MEDIUM
-| *camel.source.endpoint.as2Version* | The version of the AS2 protocol. One of: [1.0] [1.1] | "1.1" | false | MEDIUM
-| *camel.source.endpoint.clientFqdn* | The Client Fully Qualified Domain Name (FQDN). Used in message ids sent by endpoint. | "camel.apache.org" | false | MEDIUM
-| *camel.source.endpoint.compressionAlgorithm* | The algorithm used to compress EDI message. One of: [ZLIB] | null | false | MEDIUM
-| *camel.source.endpoint.decryptingPrivateKey* | The key used to encrypt the EDI message. | null | false | MEDIUM
-| *camel.source.endpoint.dispositionNotificationTo* | The value of the Disposition-Notification-To header. Assigning a value to this parameter requests a message disposition notification (MDN) for the AS2 message. | null | false | MEDIUM
-| *camel.source.endpoint.ediMessageTransferEncoding* | The transfer encoding of EDI message. | null | false | MEDIUM
-| *camel.source.endpoint.ediMessageType* | The content type of EDI message. One of application/edifact, application/edi-x12, application/edi-consent | null | false | MEDIUM
-| *camel.source.endpoint.encryptingAlgorithm* | The algorithm used to encrypt EDI message. One of: [AES128_CBC] [AES192_CBC] [AES256_CBC] [AES128_CCM] [AES192_CCM] [AES256_CCM] [AES128_GCM] [AES192_GCM] [AES256_GCM] [CAMELLIA128_CBC] [CAMELLIA192_CBC] [CAMELLIA256_CBC] [CAST5_CBC] [DES_CBC] [DES_EDE3_CBC] [GOST28147_GCFB] [IDEA_CBC] [RC2_CBC] [RC4] [SEED_CBC] | null | false | MEDIUM
-| *camel.source.endpoint.encryptingCertificateChain* | The chain of certificates used to encrypt EDI message. | null | false | MEDIUM
-| *camel.source.endpoint.from* | The value of the From header of AS2 message. | null | false | MEDIUM
-| *camel.source.endpoint.inBody* | Sets the name of a parameter to be passed in the exchange In Body | null | false | MEDIUM
-| *camel.source.endpoint.mdnMessageTemplate* | The template used to format MDN message | null | false | MEDIUM
-| *camel.source.endpoint.requestUri* | The request URI of EDI message. | "/" | false | MEDIUM
-| *camel.source.endpoint.server* | The value included in the Server message header identifying the AS2 Server. | "Camel AS2 Server Endpoint" | false | MEDIUM
-| *camel.source.endpoint.serverFqdn* | The Server Fully Qualified Domain Name (FQDN). Used in message ids sent by endpoint. | "camel.apache.org" | false | MEDIUM
-| *camel.source.endpoint.serverPortNumber* | The port number of server. | null | false | MEDIUM
-| *camel.source.endpoint.signedReceiptMicAlgorithms* | The list of algorithms, in order of preference, requested to generate a message integrity check (MIC) returned in message dispostion notification (MDN) | null | false | MEDIUM
-| *camel.source.endpoint.signingAlgorithm* | The algorithm used to sign EDI message. One of: [SHA3_224WITHRSA] [SHA3_256WITHRSA] [SHA3_384withRSA] [SHA3_512WITHRSA] [MD5WITHRSA] [SHA1WITHRSA] [MD2WITHRSA] [SHA224WITHRSA] [SHA256WITHRSA] [SHA384WITHRSA] [SHA512WITHRSA] [RIPEMD128WITHRSA] [RIPEMD160WITHRSA] [RIPEMD256WITHRSA] [SHA224WITHDSA] [SHA256WITHDSA] [SHA384WITHDSA] [SHA512WITHDSA] [SHA3_224WITHDSA] [SHA3_256WITHDSA] [SHA3_384WITHDSA] [SHA3_512WITHDSA] [SHA1WITHDSA] [SHA3_224WITHECD [...]
-| *camel.source.endpoint.signingCertificateChain* | The chain of certificates used to sign EDI message. | null | false | MEDIUM
-| *camel.source.endpoint.signingPrivateKey* | The key used to sign the EDI message. | null | false | MEDIUM
-| *camel.source.endpoint.subject* | The value of Subject header of AS2 message. | null | false | MEDIUM
-| *camel.source.endpoint.targetHostname* | The host name (IP or DNS name) of target host. | null | false | MEDIUM
-| *camel.source.endpoint.targetPortNumber* | The port number of target host. -1 indicates the scheme default port. | null | false | MEDIUM
-| *camel.source.endpoint.userAgent* | The value included in the User-Agent message header identifying the AS2 user agent. | "Camel AS2 Client Endpoint" | false | MEDIUM
-| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | false | MEDIUM
-| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | false | MEDIUM
-| *camel.component.as2.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.component.as2.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.as2.configuration* | Component configuration | null | false | MEDIUM
-|===
-
-
-
-The camel-as2 source connector has no converters out of the box.
-
-
-
-
-
-The camel-as2 source connector has no transforms out of the box.
-
-
-
-
-
-The camel-as2 source connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-asterisk-kafka-connector/src/main/docs/camel-asterisk-kafka-sink-connector.adoc b/connectors/camel-asterisk-kafka-connector/src/main/docs/camel-asterisk-kafka-sink-connector.adoc
deleted file mode 100644
index 9a25d91..0000000
--- a/connectors/camel-asterisk-kafka-connector/src/main/docs/camel-asterisk-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,59 +0,0 @@
-// kafka-connector options: START
-[[camel-asterisk-kafka-connector-sink]]
-= camel-asterisk-kafka-connector sink configuration
-
-Connector Description: Interact with Asterisk PBX Server.
-
-When using camel-asterisk-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-asterisk-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.asterisk.CamelAsteriskSinkConnector
-----
-
-
-The camel-asterisk sink connector supports 8 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.name* | Name of component | null | true | HIGH
-| *camel.sink.endpoint.hostname* | The hostname of the asterisk server | null | true | HIGH
-| *camel.sink.endpoint.password* | Login password | null | true | HIGH
-| *camel.sink.endpoint.username* | Login username | null | true | HIGH
-| *camel.sink.endpoint.action* | What action to perform such as getting queue status, sip peers or extension state. One of: [QUEUE_STATUS] [SIP_PEERS] [EXTENSION_STATE] | null | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.component.asterisk.lazyStartProducer* | 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.asterisk.autowiredEnabled* | 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 | false | MEDIUM
-|===
-
-
-
-The camel-asterisk sink connector has no converters out of the box.
-
-
-
-
-
-The camel-asterisk sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-asterisk sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-asterisk-kafka-connector/src/main/docs/camel-asterisk-kafka-source-connector.adoc b/connectors/camel-asterisk-kafka-connector/src/main/docs/camel-asterisk-kafka-source-connector.adoc
deleted file mode 100644
index 02215be..0000000
--- a/connectors/camel-asterisk-kafka-connector/src/main/docs/camel-asterisk-kafka-source-connector.adoc
+++ /dev/null
@@ -1,60 +0,0 @@
-// kafka-connector options: START
-[[camel-asterisk-kafka-connector-source]]
-= camel-asterisk-kafka-connector source configuration
-
-Connector description: Interact with Asterisk PBX Server.
-
-When using camel-asterisk-kafka-connector as source make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-asterisk-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Source connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.asterisk.CamelAsteriskSourceConnector
-----
-
-
-The camel-asterisk source connector supports 9 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.source.path.name* | Name of component | null | true | HIGH
-| *camel.source.endpoint.hostname* | The hostname of the asterisk server | null | true | HIGH
-| *camel.source.endpoint.password* | Login password | null | true | HIGH
-| *camel.source.endpoint.username* | Login username | null | true | HIGH
-| *camel.source.endpoint.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | false | MEDIUM
-| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | false | MEDIUM
-| *camel.component.asterisk.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.component.asterisk.autowiredEnabled* | 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 | false | MEDIUM
-|===
-
-
-
-The camel-asterisk source connector has no converters out of the box.
-
-
-
-
-
-The camel-asterisk source connector has no transforms out of the box.
-
-
-
-
-
-The camel-asterisk source connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-atlasmap-kafka-connector/src/main/docs/camel-atlasmap-kafka-sink-connector.adoc b/connectors/camel-atlasmap-kafka-connector/src/main/docs/camel-atlasmap-kafka-sink-connector.adoc
deleted file mode 100644
index 45c966b..0000000
--- a/connectors/camel-atlasmap-kafka-connector/src/main/docs/camel-atlasmap-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,62 +0,0 @@
-// kafka-connector options: START
-[[camel-atlasmap-kafka-connector-sink]]
-= camel-atlasmap-kafka-connector sink configuration
-
-Connector Description: Transforms the message using an AtlasMap transformation.
-
-When using camel-atlasmap-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-atlasmap-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.atlasmap.CamelAtlasmapSinkConnector
-----
-
-
-The camel-atlasmap sink connector supports 11 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.resourceUri* | Path to the resource. You can prefix with: classpath, file, http, ref, or bean. classpath, file and http loads the resource using these protocols (classpath is default). ref will lookup the resource in the registry. bean will call a method on a bean to be used as the resource. For bean you can specify the method name after dot, eg bean:myBean.myMethod. | null | true | HIGH
-| *camel.sink.endpoint.allowContextMapAll* | 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 | false | MEDIUM
-| *camel.sink.endpoint.contentCache* | Sets whether to use resource content cache or not | false | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.sourceMapName* | The Exchange property name for a source message map which hold java.util.Map<String, Message> where the key is AtlasMap Document ID. AtlasMap consumes Message bodies as source documents, as well as message headers as source properties where the scope equals to Document ID. | null | false | MEDIUM
-| *camel.sink.endpoint.targetMapMode* | TargetMapMode enum value to specify how multiple target documents are delivered if exist. 'MAP': Stores them into a java.util.Map, and the java.util.Map is set to an exchange property if 'targetMapName' is specified, otherwise message body. 'MESSAGE_HEADER': Stores them into message headers. 'EXCHANGE_PROPERTY': Stores them into exchange properties. ) One of: [MAP] [MESSAGE_HEADER] [EXCHANGE_PROPERTY] | "MAP" | false | MEDIUM
-| *camel.sink.endpoint.targetMapName* | The Exchange property name for a target document map which hold java.util.Map<String, Object> where the key is AtlasMap Document ID. AtlasMap populates multiple target documents into this map. | null | false | MEDIUM
-| *camel.component.atlasmap.lazyStartProducer* | 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.atlasmap.atlasContextFactory* | To use the AtlasContextFactory otherwise a new engine is created. | null | false | MEDIUM
-| *camel.component.atlasmap.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.atlasmap.propertiesFile* | The URI of the properties file which is used for AtlasContextFactory initialization. | null | false | MEDIUM
-|===
-
-
-
-The camel-atlasmap sink connector has no converters out of the box.
-
-
-
-
-
-The camel-atlasmap sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-atlasmap sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-atmos-kafka-connector/src/main/docs/camel-atmos-kafka-sink-connector.adoc b/connectors/camel-atmos-kafka-connector/src/main/docs/camel-atmos-kafka-sink-connector.adoc
deleted file mode 100644
index d16a4af..0000000
--- a/connectors/camel-atmos-kafka-connector/src/main/docs/camel-atmos-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,68 +0,0 @@
-// kafka-connector options: START
-[[camel-atmos-kafka-connector-sink]]
-= camel-atmos-kafka-connector sink configuration
-
-Connector Description: Integrate with EMC's ViPR object data services using the Atmos Client.
-
-When using camel-atmos-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-atmos-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.atmos.CamelAtmosSinkConnector
-----
-
-
-The camel-atmos sink connector supports 17 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.name* | Atmos name | null | false | MEDIUM
-| *camel.sink.path.operation* | Operation to perform One of: [put] [del] [search] [get] [move] | null | true | HIGH
-| *camel.sink.endpoint.localPath* | Local path to put files | null | false | MEDIUM
-| *camel.sink.endpoint.newRemotePath* | New path on Atmos when moving files | null | false | MEDIUM
-| *camel.sink.endpoint.query* | Search query on Atmos | null | false | MEDIUM
-| *camel.sink.endpoint.remotePath* | Where to put files on Atmos | null | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.uri* | Atomos server uri | null | false | MEDIUM
-| *camel.sink.endpoint.fullTokenId* | Atmos client fullTokenId | null | false | MEDIUM
-| *camel.sink.endpoint.secretKey* | The secret key to pass to the Atmos client (should be base64 encoded) | null | false | MEDIUM
-| *camel.sink.endpoint.sslValidation* | Atmos SSL validation | false | false | MEDIUM
-| *camel.component.atmos.lazyStartProducer* | 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.atmos.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.atmos.uri* | The URI of the server for the Atmos client to connect to | null | false | MEDIUM
-| *camel.component.atmos.fullTokenId* | The token id to pass to the Atmos client | null | false | MEDIUM
-| *camel.component.atmos.secretKey* | The secret key to pass to the Atmos client (should be base64 encoded) | null | false | MEDIUM
-| *camel.component.atmos.sslValidation* | Whether the Atmos client should perform SSL validation | false | false | MEDIUM
-|===
-
-
-
-The camel-atmos sink connector has no converters out of the box.
-
-
-
-
-
-The camel-atmos sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-atmos sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-atmos-kafka-connector/src/main/docs/camel-atmos-kafka-source-connector.adoc b/connectors/camel-atmos-kafka-connector/src/main/docs/camel-atmos-kafka-source-connector.adoc
deleted file mode 100644
index 5aa61df..0000000
--- a/connectors/camel-atmos-kafka-connector/src/main/docs/camel-atmos-kafka-source-connector.adoc
+++ /dev/null
@@ -1,70 +0,0 @@
-// kafka-connector options: START
-[[camel-atmos-kafka-connector-source]]
-= camel-atmos-kafka-connector source configuration
-
-Connector description: Integrate with EMC's ViPR object data services using the Atmos Client.
-
-When using camel-atmos-kafka-connector as source make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-atmos-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Source connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.atmos.CamelAtmosSourceConnector
-----
-
-
-The camel-atmos source connector supports 19 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.source.path.name* | Atmos name | null | false | MEDIUM
-| *camel.source.path.operation* | Operation to perform One of: [put] [del] [search] [get] [move] | null | true | HIGH
-| *camel.source.endpoint.localPath* | Local path to put files | null | false | MEDIUM
-| *camel.source.endpoint.newRemotePath* | New path on Atmos when moving files | null | false | MEDIUM
-| *camel.source.endpoint.query* | Search query on Atmos | null | false | MEDIUM
-| *camel.source.endpoint.remotePath* | Where to put files on Atmos | null | false | MEDIUM
-| *camel.source.endpoint.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | false | MEDIUM
-| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | false | MEDIUM
-| *camel.source.endpoint.uri* | Atomos server uri | null | false | MEDIUM
-| *camel.source.endpoint.fullTokenId* | Atmos client fullTokenId | null | false | MEDIUM
-| *camel.source.endpoint.secretKey* | The secret key to pass to the Atmos client (should be base64 encoded) | null | false | MEDIUM
-| *camel.source.endpoint.sslValidation* | Atmos SSL validation | false | false | MEDIUM
-| *camel.component.atmos.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.component.atmos.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.atmos.uri* | The URI of the server for the Atmos client to connect to | null | false | MEDIUM
-| *camel.component.atmos.fullTokenId* | The token id to pass to the Atmos client | null | false | MEDIUM
-| *camel.component.atmos.secretKey* | The secret key to pass to the Atmos client (should be base64 encoded) | null | false | MEDIUM
-| *camel.component.atmos.sslValidation* | Whether the Atmos client should perform SSL validation | false | false | MEDIUM
-|===
-
-
-
-The camel-atmos source connector has no converters out of the box.
-
-
-
-
-
-The camel-atmos source connector has no transforms out of the box.
-
-
-
-
-
-The camel-atmos source connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-atmosphere-websocket-kafka-connector/src/main/docs/camel-atmosphere-websocket-kafka-sink-connector.adoc b/connectors/camel-atmosphere-websocket-kafka-connector/src/main/docs/camel-atmosphere-websocket-kafka-sink-connector.adoc
deleted file mode 100644
index f6dd6c8..0000000
--- a/connectors/camel-atmosphere-websocket-kafka-connector/src/main/docs/camel-atmosphere-websocket-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,67 +0,0 @@
-// kafka-connector options: START
-[[camel-atmosphere-websocket-kafka-connector-sink]]
-= camel-atmosphere-websocket-kafka-connector sink configuration
-
-Connector Description: Expose WebSocket endpoints using the Atmosphere framework.
-
-When using camel-atmosphere-websocket-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-atmosphere-websocket-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.atmospherewebsocket.CamelAtmospherewebsocketSinkConnector
-----
-
-
-The camel-atmosphere-websocket sink connector supports 16 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.servicePath* | Name of websocket endpoint | null | true | HIGH
-| *camel.sink.endpoint.chunked* | If this option is false the Servlet will disable the HTTP streaming and set the content-length header on the response | true | false | MEDIUM
-| *camel.sink.endpoint.disableStreamCache* | Determines whether or not the raw input stream from Servlet is cached or not (Camel will read the stream into a in memory/overflow to file, Stream caching) cache. By default Camel will cache the Servlet input stream to support reading it multiple times to ensure it Camel can retrieve all data from the stream. However you can set this option to true when you for example need to access the raw stream, such as streaming it directly to a file or o [...]
-| *camel.sink.endpoint.headerFilterStrategy* | To use a custom HeaderFilterStrategy to filter header to and from Camel message. | null | false | MEDIUM
-| *camel.sink.endpoint.sendToAll* | Whether to send to all (broadcast) or send to a single receiver. | false | false | MEDIUM
-| *camel.sink.endpoint.transferException* | If enabled and an Exchange failed processing on the consumer side, and if the caused Exception was send back serialized in the response as a application/x-java-serialized-object content type. On the producer side the exception will be deserialized and thrown as is, instead of the HttpOperationFailedException. The caused exception is required to be serialized. This is by default turned off. If you enable this then be aware that Java will deseria [...]
-| *camel.sink.endpoint.useStreaming* | To enable streaming to send data as multiple text fragments. | false | false | MEDIUM
-| *camel.sink.endpoint.httpBinding* | To use a custom HttpBinding to control the mapping between Camel message and HttpClient. | null | false | MEDIUM
-| *camel.sink.endpoint.bridgeEndpoint* | If the option is true, HttpProducer will ignore the Exchange.HTTP_URI header, and use the endpoint's URI for request. You may also set the option throwExceptionOnFailure to be false to let the HttpProducer send all the fault response back. | false | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.component.atmosphere-websocket.lazyStart 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.allowJava SerializedObject* | 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 | false | MEDIUM
-| *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 | false | MEDIUM
-| *camel.component.atmosphere-websocket.httpBinding* | To use a custom HttpBinding to control the mapping between Camel message and HttpClient. | null | false | MEDIUM
-| *camel.component.atmosphere-websocket.http Configuration* | To use the shared HttpConfiguration as base configuration. | null | false | MEDIUM
-| *camel.component.atmosphere-websocket.headerFilter Strategy* | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. | null | false | MEDIUM
-|===
-
-
-
-The camel-atmosphere-websocket sink connector has no converters out of the box.
-
-
-
-
-
-The camel-atmosphere-websocket sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-atmosphere-websocket sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-atmosphere-websocket-kafka-connector/src/main/docs/camel-atmosphere-websocket-kafka-source-connector.adoc b/connectors/camel-atmosphere-websocket-kafka-connector/src/main/docs/camel-atmosphere-websocket-kafka-source-connector.adoc
deleted file mode 100644
index 247aaca..0000000
--- a/connectors/camel-atmosphere-websocket-kafka-connector/src/main/docs/camel-atmosphere-websocket-kafka-source-connector.adoc
+++ /dev/null
@@ -1,86 +0,0 @@
-// kafka-connector options: START
-[[camel-atmosphere-websocket-kafka-connector-source]]
-= camel-atmosphere-websocket-kafka-connector source configuration
-
-Connector description: Expose WebSocket endpoints using the Atmosphere framework.
-
-When using camel-atmosphere-websocket-kafka-connector as source make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-atmosphere-websocket-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Source connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.atmospherewebsocket.CamelAtmospherewebsocketSourceConnector
-----
-
-
-The camel-atmosphere-websocket source connector supports 35 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.source.path.servicePath* | Name of websocket endpoint | null | true | HIGH
-| *camel.source.endpoint.chunked* | If this option is false the Servlet will disable the HTTP streaming and set the content-length header on the response | true | false | MEDIUM
-| *camel.source.endpoint.disableStreamCache* | Determines whether or not the raw input stream from Servlet is cached or not (Camel will read the stream into a in memory/overflow to file, Stream caching) cache. By default Camel will cache the Servlet input stream to support reading it multiple times to ensure it Camel can retrieve all data from the stream. However you can set this option to true when you for example need to access the raw stream, such as streaming it directly to a file or [...]
-| *camel.source.endpoint.headerFilterStrategy* | To use a custom HeaderFilterStrategy to filter header to and from Camel message. | null | false | MEDIUM
-| *camel.source.endpoint.sendToAll* | Whether to send to all (broadcast) or send to a single receiver. | false | false | MEDIUM
-| *camel.source.endpoint.transferException* | If enabled and an Exchange failed processing on the consumer side, and if the caused Exception was send back serialized in the response as a application/x-java-serialized-object content type. On the producer side the exception will be deserialized and thrown as is, instead of the HttpOperationFailedException. The caused exception is required to be serialized. This is by default turned off. If you enable this then be aware that Java will deser [...]
-| *camel.source.endpoint.useStreaming* | To enable streaming to send data as multiple text fragments. | false | false | MEDIUM
-| *camel.source.endpoint.httpBinding* | To use a custom HttpBinding to control the mapping between Camel message and HttpClient. | null | false | MEDIUM
-| *camel.source.endpoint.async* | Configure the consumer to work in async mode | false | false | MEDIUM
-| *camel.source.endpoint.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.source.endpoint.httpMethodRestrict* | Used to only allow consuming if the HttpMethod matches, such as GET/POST/PUT etc. Multiple methods can be specified separated by comma. | null | false | MEDIUM
-| *camel.source.endpoint.matchOnUriPrefix* | Whether or not the consumer should try to find a target consumer by matching the URI prefix if no exact match is found. | false | false | MEDIUM
-| *camel.source.endpoint.muteException* | If enabled and an Exchange failed processing on the consumer side the response's body won't contain the exception's stack trace. | false | false | MEDIUM
-| *camel.source.endpoint.responseBufferSize* | To use a custom buffer size on the javax.servlet.ServletResponse. | null | false | MEDIUM
-| *camel.source.endpoint.servletName* | Name of the servlet to use | "CamelServlet" | false | MEDIUM
-| *camel.source.endpoint.attachmentMultipartBinding* | 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 | false | MEDIUM
-| *camel.source.endpoint.eagerCheckContentAvailable* | Whether to eager check whether the HTTP requests has content if the content-length header is 0 or not present. This can be turned on in case HTTP clients do not send streamed data. | false | false | MEDIUM
-| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | false | MEDIUM
-| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | false | MEDIUM
-| *camel.source.endpoint.fileNameExtWhitelist* | Whitelist of accepted filename extensions for accepting uploaded files. Multiple extensions can be separated by comma, such as txt,xml. | null | false | MEDIUM
-| *camel.source.endpoint.mapHttpMessageBody* | If this option is true then IN exchange Body of the exchange will be mapped to HTTP body. Setting this to false will avoid the HTTP mapping. | true | false | MEDIUM
-| *camel.source.endpoint.mapHttpMessageFormUrlEncoded Body* | If this option is true then IN exchange Form Encoded body of the exchange will be mapped to HTTP. Setting this to false will avoid the HTTP Form Encoded body mapping. | true | false | MEDIUM
-| *camel.source.endpoint.mapHttpMessageHeaders* | If this option is true then IN exchange Headers of the exchange will be mapped to HTTP headers. Setting this to false will avoid the HTTP Headers mapping. | true | false | MEDIUM
-| *camel.source.endpoint.optionsEnabled* | Specifies whether to enable HTTP OPTIONS for this Servlet consumer. By default OPTIONS is turned off. | false | false | MEDIUM
-| *camel.source.endpoint.traceEnabled* | Specifies whether to enable HTTP TRACE for this Servlet consumer. By default TRACE is turned off. | false | false | MEDIUM
-| *camel.component.atmosphere-websocket.bridgeError 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 | false | MEDIUM
-| *camel.component.atmosphere-websocket.servletName* | Default name of servlet to use. The default name is CamelServlet. | "CamelServlet" | false | MEDIUM
-| *camel.component.atmosphere-websocket.attachment MultipartBinding* | 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 | false | MEDIUM
-| *camel.component.atmosphere-websocket.fileNameExt Whitelist* | Whitelist of accepted filename extensions for accepting uploaded files. Multiple extensions can be separated by comma, such as txt,xml. | null | false | MEDIUM
-| *camel.component.atmosphere-websocket.httpRegistry* | To use a custom org.apache.camel.component.servlet.HttpRegistry. | null | false | MEDIUM
-| *camel.component.atmosphere-websocket.allowJava SerializedObject* | 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 | false | MEDIUM
-| *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 | false | MEDIUM
-| *camel.component.atmosphere-websocket.httpBinding* | To use a custom HttpBinding to control the mapping between Camel message and HttpClient. | null | false | MEDIUM
-| *camel.component.atmosphere-websocket.http Configuration* | To use the shared HttpConfiguration as base configuration. | null | false | MEDIUM
-| *camel.component.atmosphere-websocket.headerFilter Strategy* | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. | null | false | MEDIUM
-|===
-
-
-
-The camel-atmosphere-websocket source connector has no converters out of the box.
-
-
-
-
-
-The camel-atmosphere-websocket source connector has no transforms out of the box.
-
-
-
-
-
-The camel-atmosphere-websocket source connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-atom-kafka-connector/src/main/docs/camel-atom-kafka-source-connector.adoc b/connectors/camel-atom-kafka-connector/src/main/docs/camel-atom-kafka-source-connector.adoc
deleted file mode 100644
index a860713..0000000
--- a/connectors/camel-atom-kafka-connector/src/main/docs/camel-atom-kafka-source-connector.adoc
+++ /dev/null
@@ -1,81 +0,0 @@
-// kafka-connector options: START
-[[camel-atom-kafka-connector-source]]
-= camel-atom-kafka-connector source configuration
-
-Connector description: Poll Atom RSS feeds.
-
-When using camel-atom-kafka-connector as source make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-atom-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Source connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.atom.CamelAtomSourceConnector
-----
-
-
-The camel-atom source connector supports 30 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.source.path.feedUri* | The URI to the feed to poll. | null | true | HIGH
-| *camel.source.endpoint.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.source.endpoint.feedHeader* | Sets whether to add the feed object as a header. | true | false | MEDIUM
-| *camel.source.endpoint.filter* | Sets whether to use filtering or not of the entries. | true | false | MEDIUM
-| *camel.source.endpoint.lastUpdate* | Sets the timestamp to be used for filtering entries from the atom feeds. This options is only in conjunction with the splitEntries. | null | false | MEDIUM
-| *camel.source.endpoint.password* | Sets the password to be used for basic authentication when polling from a HTTP feed. | null | false | MEDIUM
-| *camel.source.endpoint.sendEmptyMessageWhenIdle* | If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead. | false | false | MEDIUM
-| *camel.source.endpoint.sortEntries* | Sets whether to sort entries by published date. Only works when splitEntries = true. | false | false | MEDIUM
-| *camel.source.endpoint.splitEntries* | Sets whether or not entries should be sent individually or whether the entire feed should be sent as a single message | true | false | MEDIUM
-| *camel.source.endpoint.throttleEntries* | Sets whether all entries identified in a single feed poll should be delivered immediately. If true, only one entry is processed per delay. Only applicable when splitEntries = true. | true | false | MEDIUM
-| *camel.source.endpoint.username* | Sets the username to be used for basic authentication when polling from a HTTP feed. | null | false | MEDIUM
-| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | false | MEDIUM
-| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | false | MEDIUM
-| *camel.source.endpoint.pollStrategy* | A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel. | null | false | MEDIUM
-| *camel.source.endpoint.backoffErrorThreshold* | The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in. | null | false | MEDIUM
-| *camel.source.endpoint.backoffIdleThreshold* | The number of subsequent idle polls that should happen before the backoffMultipler should kick-in. | null | false | MEDIUM
-| *camel.source.endpoint.backoffMultiplier* | To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured. | null | false | MEDIUM
-| *camel.source.endpoint.delay* | Milliseconds before the next poll. | 500L | false | MEDIUM
-| *camel.source.endpoint.greedy* | If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages. | false | false | MEDIUM
-| *camel.source.endpoint.initialDelay* | Milliseconds before the first poll starts. | 1000L | false | MEDIUM
-| *camel.source.endpoint.repeatCount* | Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever. | 0L | false | MEDIUM
-| *camel.source.endpoint.runLoggingLevel* | The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that. One of: [TRACE] [DEBUG] [INFO] [WARN] [ERROR] [OFF] | "TRACE" | false | MEDIUM
-| *camel.source.endpoint.scheduledExecutorService* | Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool. | null | false | MEDIUM
-| *camel.source.endpoint.scheduler* | To use a cron scheduler from either camel-spring or camel-quartz component. Use value spring or quartz for built in scheduler | "none" | false | MEDIUM
-| *camel.source.endpoint.schedulerProperties* | To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler. | null | false | MEDIUM
-| *camel.source.endpoint.startScheduler* | Whether the scheduler should be auto started. | true | false | MEDIUM
-| *camel.source.endpoint.timeUnit* | Time unit for initialDelay and delay options. One of: [NANOSECONDS] [MICROSECONDS] [MILLISECONDS] [SECONDS] [MINUTES] [HOURS] [DAYS] | "MILLISECONDS" | false | MEDIUM
-| *camel.source.endpoint.useFixedDelay* | Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details. | true | false | MEDIUM
-| *camel.component.atom.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.component.atom.autowiredEnabled* | 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 | false | MEDIUM
-|===
-
-
-
-The camel-atom source connector has no converters out of the box.
-
-
-
-
-
-The camel-atom source connector has no transforms out of the box.
-
-
-
-
-
-The camel-atom source connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-atomix-map-kafka-connector/src/main/docs/camel-atomix-map-kafka-sink-connector.adoc b/connectors/camel-atomix-map-kafka-connector/src/main/docs/camel-atomix-map-kafka-sink-connector.adoc
deleted file mode 100644
index 9911734..0000000
--- a/connectors/camel-atomix-map-kafka-connector/src/main/docs/camel-atomix-map-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,84 +0,0 @@
-// kafka-connector options: START
-[[camel-atomix-map-kafka-connector-sink]]
-= camel-atomix-map-kafka-connector sink configuration
-
-Connector Description: Access Atomix's distributed map.
-
-When using camel-atomix-map-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-atomix-map-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.atomixmap.CamelAtomixmapSinkConnector
-----
-
-
-The camel-atomix-map sink connector supports 33 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.resourceName* | The distributed resource name | null | true | HIGH
-| *camel.sink.endpoint.atomix* | The Atomix instance to use | null | false | MEDIUM
-| *camel.sink.endpoint.configurationUri* | The Atomix configuration uri. | null | false | MEDIUM
-| *camel.sink.endpoint.defaultAction* | The default action. One of: [PUT] [PUT_IF_ABSENT] [GET] [CLEAR] [SIZE] [CONTAINS_KEY] [CONTAINS_VALUE] [IS_EMPTY] [ENTRY_SET] [REMOVE] [REPLACE] [VALUES] | "PUT" | false | MEDIUM
-| *camel.sink.endpoint.key* | The key to use if none is set in the header or to listen for events for a specific key. | null | false | MEDIUM
-| *camel.sink.endpoint.nodes* | The address of the nodes composing the cluster. | null | false | MEDIUM
-| *camel.sink.endpoint.resultHeader* | The header that wil carry the result. | null | false | MEDIUM
-| *camel.sink.endpoint.transportClassName* | The class name (fqn) of the Atomix transport | "io.atomix.catalyst.transport.netty.NettyTransport" | false | MEDIUM
-| *camel.sink.endpoint.ttl* | The resource ttl. | null | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.defaultResourceConfig* | The cluster wide default resource configuration. | null | false | MEDIUM
-| *camel.sink.endpoint.defaultResourceOptions* | The local default resource options. | null | false | MEDIUM
-| *camel.sink.endpoint.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 | false | MEDIUM
-| *camel.sink.endpoint.readConsistency* | The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL] | null | false | MEDIUM
-| *camel.sink.endpoint.resourceConfigs* | Cluster wide resources configuration. | null | false | MEDIUM
-| *camel.sink.endpoint.resourceOptions* | Local resources configurations | null | false | MEDIUM
-| *camel.component.atomix-map.atomix* | The Atomix instance to use | null | false | MEDIUM
-| *camel.component.atomix-map.configuration* | The shared component configuration | null | false | MEDIUM
-| *camel.component.atomix-map.configurationUri* | The path to the AtomixClient configuration | null | false | MEDIUM
-| *camel.component.atomix-map.defaultAction* | The default action. One of: [PUT] [PUT_IF_ABSENT] [GET] [CLEAR] [SIZE] [CONTAINS_KEY] [CONTAINS_VALUE] [IS_EMPTY] [ENTRY_SET] [REMOVE] [REPLACE] [VALUES] | "PUT" | false | MEDIUM
-| *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. | null | false | MEDIUM
-| *camel.component.atomix-map.nodes* | The nodes the AtomixClient should connect to | null | false | MEDIUM
-| *camel.component.atomix-map.resultHeader* | The header that wil carry the result. | null | false | MEDIUM
-| *camel.component.atomix-map.transportClassName* | The class name (fqn) of the Atomix transport | "io.atomix.catalyst.transport.netty.NettyTransport" | false | MEDIUM
-| *camel.component.atomix-map.ttl* | The resource ttl. | null | false | MEDIUM
-| *camel.component.atomix-map.lazyStartProducer* | 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.atomix-map.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.atomix-map.defaultResourceConfig* | The cluster wide default resource configuration. | null | false | MEDIUM
-| *camel.component.atomix-map.defaultResourceOptions* | The local default resource options. | null | false | MEDIUM
-| *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 | false | MEDIUM
-| *camel.component.atomix-map.readConsistency* | The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL] | null | false | MEDIUM
-| *camel.component.atomix-map.resourceConfigs* | Cluster wide resources configuration. | null | false | MEDIUM
-| *camel.component.atomix-map.resourceOptions* | Local resources configurations | null | false | MEDIUM
-|===
-
-
-
-The camel-atomix-map sink connector has no converters out of the box.
-
-
-
-
-
-The camel-atomix-map sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-atomix-map sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-atomix-map-kafka-connector/src/main/docs/camel-atomix-map-kafka-source-connector.adoc b/connectors/camel-atomix-map-kafka-connector/src/main/docs/camel-atomix-map-kafka-source-connector.adoc
deleted file mode 100644
index 5794b11..0000000
--- a/connectors/camel-atomix-map-kafka-connector/src/main/docs/camel-atomix-map-kafka-source-connector.adoc
+++ /dev/null
@@ -1,86 +0,0 @@
-// kafka-connector options: START
-[[camel-atomix-map-kafka-connector-source]]
-= camel-atomix-map-kafka-connector source configuration
-
-Connector description: Access Atomix's distributed map.
-
-When using camel-atomix-map-kafka-connector as source make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-atomix-map-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Source connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.atomixmap.CamelAtomixmapSourceConnector
-----
-
-
-The camel-atomix-map source connector supports 35 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.source.path.resourceName* | The distributed resource name | null | true | HIGH
-| *camel.source.endpoint.atomix* | The Atomix instance to use | null | false | MEDIUM
-| *camel.source.endpoint.configurationUri* | The Atomix configuration uri. | null | false | MEDIUM
-| *camel.source.endpoint.defaultAction* | The default action. One of: [PUT] [PUT_IF_ABSENT] [GET] [CLEAR] [SIZE] [CONTAINS_KEY] [CONTAINS_VALUE] [IS_EMPTY] [ENTRY_SET] [REMOVE] [REPLACE] [VALUES] | "PUT" | false | MEDIUM
-| *camel.source.endpoint.key* | The key to use if none is set in the header or to listen for events for a specific key. | null | false | MEDIUM
-| *camel.source.endpoint.nodes* | The address of the nodes composing the cluster. | null | false | MEDIUM
-| *camel.source.endpoint.resultHeader* | The header that wil carry the result. | null | false | MEDIUM
-| *camel.source.endpoint.transportClassName* | The class name (fqn) of the Atomix transport | "io.atomix.catalyst.transport.netty.NettyTransport" | false | MEDIUM
-| *camel.source.endpoint.ttl* | The resource ttl. | null | false | MEDIUM
-| *camel.source.endpoint.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | false | MEDIUM
-| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | false | MEDIUM
-| *camel.source.endpoint.defaultResourceConfig* | The cluster wide default resource configuration. | null | false | MEDIUM
-| *camel.source.endpoint.defaultResourceOptions* | The local default resource options. | null | false | MEDIUM
-| *camel.source.endpoint.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 | false | MEDIUM
-| *camel.source.endpoint.readConsistency* | The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL] | null | false | MEDIUM
-| *camel.source.endpoint.resourceConfigs* | Cluster wide resources configuration. | null | false | MEDIUM
-| *camel.source.endpoint.resourceOptions* | Local resources configurations | null | false | MEDIUM
-| *camel.component.atomix-map.atomix* | The Atomix instance to use | null | false | MEDIUM
-| *camel.component.atomix-map.configuration* | The shared component configuration | null | false | MEDIUM
-| *camel.component.atomix-map.configurationUri* | The path to the AtomixClient configuration | null | false | MEDIUM
-| *camel.component.atomix-map.defaultAction* | The default action. One of: [PUT] [PUT_IF_ABSENT] [GET] [CLEAR] [SIZE] [CONTAINS_KEY] [CONTAINS_VALUE] [IS_EMPTY] [ENTRY_SET] [REMOVE] [REPLACE] [VALUES] | "PUT" | false | MEDIUM
-| *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. | null | false | MEDIUM
-| *camel.component.atomix-map.nodes* | The nodes the AtomixClient should connect to | null | false | MEDIUM
-| *camel.component.atomix-map.resultHeader* | The header that wil carry the result. | null | false | MEDIUM
-| *camel.component.atomix-map.transportClassName* | The class name (fqn) of the Atomix transport | "io.atomix.catalyst.transport.netty.NettyTransport" | false | MEDIUM
-| *camel.component.atomix-map.ttl* | The resource ttl. | null | false | MEDIUM
-| *camel.component.atomix-map.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.component.atomix-map.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.atomix-map.defaultResourceConfig* | The cluster wide default resource configuration. | null | false | MEDIUM
-| *camel.component.atomix-map.defaultResourceOptions* | The local default resource options. | null | false | MEDIUM
-| *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 | false | MEDIUM
-| *camel.component.atomix-map.readConsistency* | The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL] | null | false | MEDIUM
-| *camel.component.atomix-map.resourceConfigs* | Cluster wide resources configuration. | null | false | MEDIUM
-| *camel.component.atomix-map.resourceOptions* | Local resources configurations | null | false | MEDIUM
-|===
-
-
-
-The camel-atomix-map source connector has no converters out of the box.
-
-
-
-
-
-The camel-atomix-map source connector has no transforms out of the box.
-
-
-
-
-
-The camel-atomix-map source connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-atomix-messaging-kafka-connector/src/main/docs/camel-atomix-messaging-kafka-sink-connector.adoc b/connectors/camel-atomix-messaging-kafka-connector/src/main/docs/camel-atomix-messaging-kafka-sink-connector.adoc
deleted file mode 100644
index 2b9b039..0000000
--- a/connectors/camel-atomix-messaging-kafka-connector/src/main/docs/camel-atomix-messaging-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,86 +0,0 @@
-// kafka-connector options: START
-[[camel-atomix-messaging-kafka-connector-sink]]
-= camel-atomix-messaging-kafka-connector sink configuration
-
-Connector Description: Access Atomix's group messaging.
-
-When using camel-atomix-messaging-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-atomix-messaging-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.atomixmessaging.CamelAtomixmessagingSinkConnector
-----
-
-
-The camel-atomix-messaging sink connector supports 35 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.resourceName* | The distributed resource name | null | true | HIGH
-| *camel.sink.endpoint.atomix* | The Atomix instance to use | null | false | MEDIUM
-| *camel.sink.endpoint.broadcastType* | The broadcast type. One of: [ALL] [RANDOM] | "ALL" | false | MEDIUM
-| *camel.sink.endpoint.channelName* | The messaging channel name | null | false | MEDIUM
-| *camel.sink.endpoint.configurationUri* | The Atomix configuration uri. | null | false | MEDIUM
-| *camel.sink.endpoint.defaultAction* | The default action. One of: [DIRECT] [BROADCAST] | "DIRECT" | false | MEDIUM
-| *camel.sink.endpoint.memberName* | The Atomix Group member name | null | false | MEDIUM
-| *camel.sink.endpoint.nodes* | The address of the nodes composing the cluster. | null | false | MEDIUM
-| *camel.sink.endpoint.resultHeader* | The header that wil carry the result. | null | false | MEDIUM
-| *camel.sink.endpoint.transportClassName* | The class name (fqn) of the Atomix transport | "io.atomix.catalyst.transport.netty.NettyTransport" | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.defaultResourceConfig* | The cluster wide default resource configuration. | null | false | MEDIUM
-| *camel.sink.endpoint.defaultResourceOptions* | The local default resource options. | null | false | MEDIUM
-| *camel.sink.endpoint.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 | false | MEDIUM
-| *camel.sink.endpoint.readConsistency* | The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL] | null | false | MEDIUM
-| *camel.sink.endpoint.resourceConfigs* | Cluster wide resources configuration. | null | false | MEDIUM
-| *camel.sink.endpoint.resourceOptions* | Local resources configurations | null | false | MEDIUM
-| *camel.component.atomix-messaging.atomix* | The Atomix instance to use | null | false | MEDIUM
-| *camel.component.atomix-messaging.broadcastType* | The broadcast type. One of: [ALL] [RANDOM] | "ALL" | false | MEDIUM
-| *camel.component.atomix-messaging.channelName* | The messaging channel name | null | false | MEDIUM
-| *camel.component.atomix-messaging.configuration* | The shared component configuration | null | false | MEDIUM
-| *camel.component.atomix-messaging.configurationUri* | The path to the AtomixClient configuration | null | false | MEDIUM
-| *camel.component.atomix-messaging.defaultAction* | The default action. One of: [DIRECT] [BROADCAST] | "DIRECT" | false | MEDIUM
-| *camel.component.atomix-messaging.memberName* | The Atomix Group member name | null | false | MEDIUM
-| *camel.component.atomix-messaging.nodes* | The nodes the AtomixClient should connect to | null | false | MEDIUM
-| *camel.component.atomix-messaging.resultHeader* | The header that wil carry the result. | null | false | MEDIUM
-| *camel.component.atomix-messaging.transportClass Name* | The class name (fqn) of the Atomix transport | "io.atomix.catalyst.transport.netty.NettyTransport" | false | MEDIUM
-| *camel.component.atomix-messaging.lazyStartProducer* | 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.atomix-messaging.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.atomix-messaging.defaultResource Config* | The cluster wide default resource configuration. | null | false | MEDIUM
-| *camel.component.atomix-messaging.defaultResource Options* | The local default resource options. | null | false | MEDIUM
-| *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 | false | MEDIUM
-| *camel.component.atomix-messaging.readConsistency* | The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL] | null | false | MEDIUM
-| *camel.component.atomix-messaging.resourceConfigs* | Cluster wide resources configuration. | null | false | MEDIUM
-| *camel.component.atomix-messaging.resourceOptions* | Local resources configurations | null | false | MEDIUM
-|===
-
-
-
-The camel-atomix-messaging sink connector has no converters out of the box.
-
-
-
-
-
-The camel-atomix-messaging sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-atomix-messaging sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-atomix-messaging-kafka-connector/src/main/docs/camel-atomix-messaging-kafka-source-connector.adoc b/connectors/camel-atomix-messaging-kafka-connector/src/main/docs/camel-atomix-messaging-kafka-source-connector.adoc
deleted file mode 100644
index 9808c5a..0000000
--- a/connectors/camel-atomix-messaging-kafka-connector/src/main/docs/camel-atomix-messaging-kafka-source-connector.adoc
+++ /dev/null
@@ -1,88 +0,0 @@
-// kafka-connector options: START
-[[camel-atomix-messaging-kafka-connector-source]]
-= camel-atomix-messaging-kafka-connector source configuration
-
-Connector description: Access Atomix's group messaging.
-
-When using camel-atomix-messaging-kafka-connector as source make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-atomix-messaging-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Source connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.atomixmessaging.CamelAtomixmessagingSourceConnector
-----
-
-
-The camel-atomix-messaging source connector supports 37 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.source.path.resourceName* | The distributed resource name | null | true | HIGH
-| *camel.source.endpoint.atomix* | The Atomix instance to use | null | false | MEDIUM
-| *camel.source.endpoint.broadcastType* | The broadcast type. One of: [ALL] [RANDOM] | "ALL" | false | MEDIUM
-| *camel.source.endpoint.channelName* | The messaging channel name | null | false | MEDIUM
-| *camel.source.endpoint.configurationUri* | The Atomix configuration uri. | null | false | MEDIUM
-| *camel.source.endpoint.defaultAction* | The default action. One of: [DIRECT] [BROADCAST] | "DIRECT" | false | MEDIUM
-| *camel.source.endpoint.memberName* | The Atomix Group member name | null | false | MEDIUM
-| *camel.source.endpoint.nodes* | The address of the nodes composing the cluster. | null | false | MEDIUM
-| *camel.source.endpoint.resultHeader* | The header that wil carry the result. | null | false | MEDIUM
-| *camel.source.endpoint.transportClassName* | The class name (fqn) of the Atomix transport | "io.atomix.catalyst.transport.netty.NettyTransport" | false | MEDIUM
-| *camel.source.endpoint.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | false | MEDIUM
-| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | false | MEDIUM
-| *camel.source.endpoint.defaultResourceConfig* | The cluster wide default resource configuration. | null | false | MEDIUM
-| *camel.source.endpoint.defaultResourceOptions* | The local default resource options. | null | false | MEDIUM
-| *camel.source.endpoint.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 | false | MEDIUM
-| *camel.source.endpoint.readConsistency* | The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL] | null | false | MEDIUM
-| *camel.source.endpoint.resourceConfigs* | Cluster wide resources configuration. | null | false | MEDIUM
-| *camel.source.endpoint.resourceOptions* | Local resources configurations | null | false | MEDIUM
-| *camel.component.atomix-messaging.atomix* | The Atomix instance to use | null | false | MEDIUM
-| *camel.component.atomix-messaging.broadcastType* | The broadcast type. One of: [ALL] [RANDOM] | "ALL" | false | MEDIUM
-| *camel.component.atomix-messaging.channelName* | The messaging channel name | null | false | MEDIUM
-| *camel.component.atomix-messaging.configuration* | The shared component configuration | null | false | MEDIUM
-| *camel.component.atomix-messaging.configurationUri* | The path to the AtomixClient configuration | null | false | MEDIUM
-| *camel.component.atomix-messaging.defaultAction* | The default action. One of: [DIRECT] [BROADCAST] | "DIRECT" | false | MEDIUM
-| *camel.component.atomix-messaging.memberName* | The Atomix Group member name | null | false | MEDIUM
-| *camel.component.atomix-messaging.nodes* | The nodes the AtomixClient should connect to | null | false | MEDIUM
-| *camel.component.atomix-messaging.resultHeader* | The header that wil carry the result. | null | false | MEDIUM
-| *camel.component.atomix-messaging.transportClass Name* | The class name (fqn) of the Atomix transport | "io.atomix.catalyst.transport.netty.NettyTransport" | false | MEDIUM
-| *camel.component.atomix-messaging.bridgeError 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 | false | MEDIUM
-| *camel.component.atomix-messaging.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.atomix-messaging.defaultResource Config* | The cluster wide default resource configuration. | null | false | MEDIUM
-| *camel.component.atomix-messaging.defaultResource Options* | The local default resource options. | null | false | MEDIUM
-| *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 | false | MEDIUM
-| *camel.component.atomix-messaging.readConsistency* | The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL] | null | false | MEDIUM
-| *camel.component.atomix-messaging.resourceConfigs* | Cluster wide resources configuration. | null | false | MEDIUM
-| *camel.component.atomix-messaging.resourceOptions* | Local resources configurations | null | false | MEDIUM
-|===
-
-
-
-The camel-atomix-messaging source connector has no converters out of the box.
-
-
-
-
-
-The camel-atomix-messaging source connector has no transforms out of the box.
-
-
-
-
-
-The camel-atomix-messaging source connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-atomix-multimap-kafka-connector/src/main/docs/camel-atomix-multimap-kafka-sink-connector.adoc b/connectors/camel-atomix-multimap-kafka-connector/src/main/docs/camel-atomix-multimap-kafka-sink-connector.adoc
deleted file mode 100644
index fc763f3..0000000
--- a/connectors/camel-atomix-multimap-kafka-connector/src/main/docs/camel-atomix-multimap-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,84 +0,0 @@
-// kafka-connector options: START
-[[camel-atomix-multimap-kafka-connector-sink]]
-= camel-atomix-multimap-kafka-connector sink configuration
-
-Connector Description: Access Atomix's distributed multi map.
-
-When using camel-atomix-multimap-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-atomix-multimap-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.atomixmultimap.CamelAtomixmultimapSinkConnector
-----
-
-
-The camel-atomix-multimap sink connector supports 33 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.resourceName* | The distributed resource name | null | true | HIGH
-| *camel.sink.endpoint.atomix* | The Atomix instance to use | null | false | MEDIUM
-| *camel.sink.endpoint.configurationUri* | The Atomix configuration uri. | null | false | MEDIUM
-| *camel.sink.endpoint.defaultAction* | The default action. One of: [PUT] [GET] [CLEAR] [SIZE] [CONTAINS_KEY] [IS_EMPTY] [REMOVE] [REMOVE_VALUE] | "PUT" | false | MEDIUM
-| *camel.sink.endpoint.key* | The key to use if none is set in the header or to listen for events for a specific key. | null | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.nodes* | The address of the nodes composing the cluster. | null | false | MEDIUM
-| *camel.sink.endpoint.resultHeader* | The header that wil carry the result. | null | false | MEDIUM
-| *camel.sink.endpoint.transportClassName* | The class name (fqn) of the Atomix transport | "io.atomix.catalyst.transport.netty.NettyTransport" | false | MEDIUM
-| *camel.sink.endpoint.ttl* | The resource ttl. | null | false | MEDIUM
-| *camel.sink.endpoint.defaultResourceConfig* | The cluster wide default resource configuration. | null | false | MEDIUM
-| *camel.sink.endpoint.defaultResourceOptions* | The local default resource options. | null | false | MEDIUM
-| *camel.sink.endpoint.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 | false | MEDIUM
-| *camel.sink.endpoint.readConsistency* | The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL] | null | false | MEDIUM
-| *camel.sink.endpoint.resourceConfigs* | Cluster wide resources configuration. | null | false | MEDIUM
-| *camel.sink.endpoint.resourceOptions* | Local resources configurations | null | false | MEDIUM
-| *camel.component.atomix-multimap.atomix* | The Atomix instance to use | null | false | MEDIUM
-| *camel.component.atomix-multimap.configuration* | The shared component configuration | null | false | MEDIUM
-| *camel.component.atomix-multimap.configurationUri* | The path to the AtomixClient configuration | null | false | MEDIUM
-| *camel.component.atomix-multimap.defaultAction* | The default action. One of: [PUT] [GET] [CLEAR] [SIZE] [CONTAINS_KEY] [IS_EMPTY] [REMOVE] [REMOVE_VALUE] | "PUT" | false | MEDIUM
-| *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. | null | false | MEDIUM
-| *camel.component.atomix-multimap.lazyStartProducer* | 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.atomix-multimap.nodes* | The nodes the AtomixClient should connect to | null | false | MEDIUM
-| *camel.component.atomix-multimap.resultHeader* | The header that wil carry the result. | null | false | MEDIUM
-| *camel.component.atomix-multimap.transportClassName* | The class name (fqn) of the Atomix transport | "io.atomix.catalyst.transport.netty.NettyTransport" | false | MEDIUM
-| *camel.component.atomix-multimap.ttl* | The resource ttl. | null | false | MEDIUM
-| *camel.component.atomix-multimap.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.atomix-multimap.defaultResource Config* | The cluster wide default resource configuration. | null | false | MEDIUM
-| *camel.component.atomix-multimap.defaultResource Options* | The local default resource options. | null | false | MEDIUM
-| *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 | false | MEDIUM
-| *camel.component.atomix-multimap.readConsistency* | The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL] | null | false | MEDIUM
-| *camel.component.atomix-multimap.resourceConfigs* | Cluster wide resources configuration. | null | false | MEDIUM
-| *camel.component.atomix-multimap.resourceOptions* | Local resources configurations | null | false | MEDIUM
-|===
-
-
-
-The camel-atomix-multimap sink connector has no converters out of the box.
-
-
-
-
-
-The camel-atomix-multimap sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-atomix-multimap sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-atomix-queue-kafka-connector/src/main/docs/camel-atomix-queue-kafka-sink-connector.adoc b/connectors/camel-atomix-queue-kafka-connector/src/main/docs/camel-atomix-queue-kafka-sink-connector.adoc
deleted file mode 100644
index ec36bd9..0000000
--- a/connectors/camel-atomix-queue-kafka-connector/src/main/docs/camel-atomix-queue-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,80 +0,0 @@
-// kafka-connector options: START
-[[camel-atomix-queue-kafka-connector-sink]]
-= camel-atomix-queue-kafka-connector sink configuration
-
-Connector Description: Access Atomix's distributed queue.
-
-When using camel-atomix-queue-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-atomix-queue-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.atomixqueue.CamelAtomixqueueSinkConnector
-----
-
-
-The camel-atomix-queue sink connector supports 29 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.resourceName* | The distributed resource name | null | true | HIGH
-| *camel.sink.endpoint.atomix* | The Atomix instance to use | null | false | MEDIUM
-| *camel.sink.endpoint.configurationUri* | The Atomix configuration uri. | null | false | MEDIUM
-| *camel.sink.endpoint.defaultAction* | The default action. One of: [ADD] [OFFER] [PEEK] [POLL] [CLEAR] [CONTAINS] [IS_EMPTY] [REMOVE] [SIZE] | "ADD" | false | MEDIUM
-| *camel.sink.endpoint.nodes* | The address of the nodes composing the cluster. | null | false | MEDIUM
-| *camel.sink.endpoint.resultHeader* | The header that wil carry the result. | null | false | MEDIUM
-| *camel.sink.endpoint.transportClassName* | The class name (fqn) of the Atomix transport | "io.atomix.catalyst.transport.netty.NettyTransport" | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.defaultResourceConfig* | The cluster wide default resource configuration. | null | false | MEDIUM
-| *camel.sink.endpoint.defaultResourceOptions* | The local default resource options. | null | false | MEDIUM
-| *camel.sink.endpoint.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 | false | MEDIUM
-| *camel.sink.endpoint.readConsistency* | The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL] | null | false | MEDIUM
-| *camel.sink.endpoint.resourceConfigs* | Cluster wide resources configuration. | null | false | MEDIUM
-| *camel.sink.endpoint.resourceOptions* | Local resources configurations | null | false | MEDIUM
-| *camel.component.atomix-queue.atomix* | The Atomix instance to use | null | false | MEDIUM
-| *camel.component.atomix-queue.configuration* | The shared component configuration | null | false | MEDIUM
-| *camel.component.atomix-queue.configurationUri* | The path to the AtomixClient configuration | null | false | MEDIUM
-| *camel.component.atomix-queue.defaultAction* | The default action. One of: [ADD] [OFFER] [PEEK] [POLL] [CLEAR] [CONTAINS] [IS_EMPTY] [REMOVE] [SIZE] | "ADD" | false | MEDIUM
-| *camel.component.atomix-queue.nodes* | The nodes the AtomixClient should connect to | null | false | MEDIUM
-| *camel.component.atomix-queue.resultHeader* | The header that wil carry the result. | null | false | MEDIUM
-| *camel.component.atomix-queue.transportClassName* | The class name (fqn) of the Atomix transport | "io.atomix.catalyst.transport.netty.NettyTransport" | false | MEDIUM
-| *camel.component.atomix-queue.lazyStartProducer* | 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-queue.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.atomix-queue.defaultResourceConfig* | The cluster wide default resource configuration. | null | false | MEDIUM
-| *camel.component.atomix-queue.defaultResource Options* | The local default resource options. | null | false | MEDIUM
-| *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 | false | MEDIUM
-| *camel.component.atomix-queue.readConsistency* | The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL] | null | false | MEDIUM
-| *camel.component.atomix-queue.resourceConfigs* | Cluster wide resources configuration. | null | false | MEDIUM
-| *camel.component.atomix-queue.resourceOptions* | Local resources configurations | null | false | MEDIUM
-|===
-
-
-
-The camel-atomix-queue sink connector has no converters out of the box.
-
-
-
-
-
-The camel-atomix-queue sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-atomix-queue sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-atomix-queue-kafka-connector/src/main/docs/camel-atomix-queue-kafka-source-connector.adoc b/connectors/camel-atomix-queue-kafka-connector/src/main/docs/camel-atomix-queue-kafka-source-connector.adoc
deleted file mode 100644
index 0114561..0000000
--- a/connectors/camel-atomix-queue-kafka-connector/src/main/docs/camel-atomix-queue-kafka-source-connector.adoc
+++ /dev/null
@@ -1,82 +0,0 @@
-// kafka-connector options: START
-[[camel-atomix-queue-kafka-connector-source]]
-= camel-atomix-queue-kafka-connector source configuration
-
-Connector description: Access Atomix's distributed queue.
-
-When using camel-atomix-queue-kafka-connector as source make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-atomix-queue-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Source connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.atomixqueue.CamelAtomixqueueSourceConnector
-----
-
-
-The camel-atomix-queue source connector supports 31 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.source.path.resourceName* | The distributed resource name | null | true | HIGH
-| *camel.source.endpoint.atomix* | The Atomix instance to use | null | false | MEDIUM
-| *camel.source.endpoint.configurationUri* | The Atomix configuration uri. | null | false | MEDIUM
-| *camel.source.endpoint.defaultAction* | The default action. One of: [ADD] [OFFER] [PEEK] [POLL] [CLEAR] [CONTAINS] [IS_EMPTY] [REMOVE] [SIZE] | "ADD" | false | MEDIUM
-| *camel.source.endpoint.nodes* | The address of the nodes composing the cluster. | null | false | MEDIUM
-| *camel.source.endpoint.resultHeader* | The header that wil carry the result. | null | false | MEDIUM
-| *camel.source.endpoint.transportClassName* | The class name (fqn) of the Atomix transport | "io.atomix.catalyst.transport.netty.NettyTransport" | false | MEDIUM
-| *camel.source.endpoint.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | false | MEDIUM
-| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | false | MEDIUM
-| *camel.source.endpoint.defaultResourceConfig* | The cluster wide default resource configuration. | null | false | MEDIUM
-| *camel.source.endpoint.defaultResourceOptions* | The local default resource options. | null | false | MEDIUM
-| *camel.source.endpoint.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 | false | MEDIUM
-| *camel.source.endpoint.readConsistency* | The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL] | null | false | MEDIUM
-| *camel.source.endpoint.resourceConfigs* | Cluster wide resources configuration. | null | false | MEDIUM
-| *camel.source.endpoint.resourceOptions* | Local resources configurations | null | false | MEDIUM
-| *camel.component.atomix-queue.atomix* | The Atomix instance to use | null | false | MEDIUM
-| *camel.component.atomix-queue.configuration* | The shared component configuration | null | false | MEDIUM
-| *camel.component.atomix-queue.configurationUri* | The path to the AtomixClient configuration | null | false | MEDIUM
-| *camel.component.atomix-queue.defaultAction* | The default action. One of: [ADD] [OFFER] [PEEK] [POLL] [CLEAR] [CONTAINS] [IS_EMPTY] [REMOVE] [SIZE] | "ADD" | false | MEDIUM
-| *camel.component.atomix-queue.nodes* | The nodes the AtomixClient should connect to | null | false | MEDIUM
-| *camel.component.atomix-queue.resultHeader* | The header that wil carry the result. | null | false | MEDIUM
-| *camel.component.atomix-queue.transportClassName* | The class name (fqn) of the Atomix transport | "io.atomix.catalyst.transport.netty.NettyTransport" | false | MEDIUM
-| *camel.component.atomix-queue.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.component.atomix-queue.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.atomix-queue.defaultResourceConfig* | The cluster wide default resource configuration. | null | false | MEDIUM
-| *camel.component.atomix-queue.defaultResource Options* | The local default resource options. | null | false | MEDIUM
-| *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 | false | MEDIUM
-| *camel.component.atomix-queue.readConsistency* | The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL] | null | false | MEDIUM
-| *camel.component.atomix-queue.resourceConfigs* | Cluster wide resources configuration. | null | false | MEDIUM
-| *camel.component.atomix-queue.resourceOptions* | Local resources configurations | null | false | MEDIUM
-|===
-
-
-
-The camel-atomix-queue source connector has no converters out of the box.
-
-
-
-
-
-The camel-atomix-queue source connector has no transforms out of the box.
-
-
-
-
-
-The camel-atomix-queue source connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-atomix-set-kafka-connector/src/main/docs/camel-atomix-set-kafka-sink-connector.adoc b/connectors/camel-atomix-set-kafka-connector/src/main/docs/camel-atomix-set-kafka-sink-connector.adoc
deleted file mode 100644
index 9ef69fe..0000000
--- a/connectors/camel-atomix-set-kafka-connector/src/main/docs/camel-atomix-set-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,82 +0,0 @@
-// kafka-connector options: START
-[[camel-atomix-set-kafka-connector-sink]]
-= camel-atomix-set-kafka-connector sink configuration
-
-Connector Description: Access Atomix's distributed set.
-
-When using camel-atomix-set-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-atomix-set-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.atomixset.CamelAtomixsetSinkConnector
-----
-
-
-The camel-atomix-set sink connector supports 31 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.resourceName* | The distributed resource name | null | true | HIGH
-| *camel.sink.endpoint.atomix* | The Atomix instance to use | null | false | MEDIUM
-| *camel.sink.endpoint.configurationUri* | The Atomix configuration uri. | null | false | MEDIUM
-| *camel.sink.endpoint.defaultAction* | The default action. One of: [ADD] [CLEAR] [CONTAINS] [IS_EMPTY] [REMOVE] [SIZE] | "ADD" | false | MEDIUM
-| *camel.sink.endpoint.nodes* | The address of the nodes composing the cluster. | null | false | MEDIUM
-| *camel.sink.endpoint.resultHeader* | The header that wil carry the result. | null | false | MEDIUM
-| *camel.sink.endpoint.transportClassName* | The class name (fqn) of the Atomix transport | "io.atomix.catalyst.transport.netty.NettyTransport" | false | MEDIUM
-| *camel.sink.endpoint.ttl* | The resource ttl. | null | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.defaultResourceConfig* | The cluster wide default resource configuration. | null | false | MEDIUM
-| *camel.sink.endpoint.defaultResourceOptions* | The local default resource options. | null | false | MEDIUM
-| *camel.sink.endpoint.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 | false | MEDIUM
-| *camel.sink.endpoint.readConsistency* | The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL] | null | false | MEDIUM
-| *camel.sink.endpoint.resourceConfigs* | Cluster wide resources configuration. | null | false | MEDIUM
-| *camel.sink.endpoint.resourceOptions* | Local resources configurations | null | false | MEDIUM
-| *camel.component.atomix-set.atomix* | The Atomix instance to use | null | false | MEDIUM
-| *camel.component.atomix-set.configuration* | The shared component configuration | null | false | MEDIUM
-| *camel.component.atomix-set.configurationUri* | The path to the AtomixClient configuration | null | false | MEDIUM
-| *camel.component.atomix-set.defaultAction* | The default action. One of: [ADD] [CLEAR] [CONTAINS] [IS_EMPTY] [REMOVE] [SIZE] | "ADD" | false | MEDIUM
-| *camel.component.atomix-set.nodes* | The nodes the AtomixClient should connect to | null | false | MEDIUM
-| *camel.component.atomix-set.resultHeader* | The header that wil carry the result. | null | false | MEDIUM
-| *camel.component.atomix-set.transportClassName* | The class name (fqn) of the Atomix transport | "io.atomix.catalyst.transport.netty.NettyTransport" | false | MEDIUM
-| *camel.component.atomix-set.ttl* | The resource ttl. | null | false | MEDIUM
-| *camel.component.atomix-set.lazyStartProducer* | 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.atomix-set.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.atomix-set.defaultResourceConfig* | The cluster wide default resource configuration. | null | false | MEDIUM
-| *camel.component.atomix-set.defaultResourceOptions* | The local default resource options. | null | false | MEDIUM
-| *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 | false | MEDIUM
-| *camel.component.atomix-set.readConsistency* | The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL] | null | false | MEDIUM
-| *camel.component.atomix-set.resourceConfigs* | Cluster wide resources configuration. | null | false | MEDIUM
-| *camel.component.atomix-set.resourceOptions* | Local resources configurations | null | false | MEDIUM
-|===
-
-
-
-The camel-atomix-set sink connector has no converters out of the box.
-
-
-
-
-
-The camel-atomix-set sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-atomix-set sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-atomix-set-kafka-connector/src/main/docs/camel-atomix-set-kafka-source-connector.adoc b/connectors/camel-atomix-set-kafka-connector/src/main/docs/camel-atomix-set-kafka-source-connector.adoc
deleted file mode 100644
index 95cb44e..0000000
--- a/connectors/camel-atomix-set-kafka-connector/src/main/docs/camel-atomix-set-kafka-source-connector.adoc
+++ /dev/null
@@ -1,84 +0,0 @@
-// kafka-connector options: START
-[[camel-atomix-set-kafka-connector-source]]
-= camel-atomix-set-kafka-connector source configuration
-
-Connector description: Access Atomix's distributed set.
-
-When using camel-atomix-set-kafka-connector as source make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-atomix-set-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Source connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.atomixset.CamelAtomixsetSourceConnector
-----
-
-
-The camel-atomix-set source connector supports 33 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.source.path.resourceName* | The distributed resource name | null | true | HIGH
-| *camel.source.endpoint.atomix* | The Atomix instance to use | null | false | MEDIUM
-| *camel.source.endpoint.configurationUri* | The Atomix configuration uri. | null | false | MEDIUM
-| *camel.source.endpoint.defaultAction* | The default action. One of: [ADD] [CLEAR] [CONTAINS] [IS_EMPTY] [REMOVE] [SIZE] | "ADD" | false | MEDIUM
-| *camel.source.endpoint.nodes* | The address of the nodes composing the cluster. | null | false | MEDIUM
-| *camel.source.endpoint.resultHeader* | The header that wil carry the result. | null | false | MEDIUM
-| *camel.source.endpoint.transportClassName* | The class name (fqn) of the Atomix transport | "io.atomix.catalyst.transport.netty.NettyTransport" | false | MEDIUM
-| *camel.source.endpoint.ttl* | The resource ttl. | null | false | MEDIUM
-| *camel.source.endpoint.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | false | MEDIUM
-| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | false | MEDIUM
-| *camel.source.endpoint.defaultResourceConfig* | The cluster wide default resource configuration. | null | false | MEDIUM
-| *camel.source.endpoint.defaultResourceOptions* | The local default resource options. | null | false | MEDIUM
-| *camel.source.endpoint.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 | false | MEDIUM
-| *camel.source.endpoint.readConsistency* | The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL] | null | false | MEDIUM
-| *camel.source.endpoint.resourceConfigs* | Cluster wide resources configuration. | null | false | MEDIUM
-| *camel.source.endpoint.resourceOptions* | Local resources configurations | null | false | MEDIUM
-| *camel.component.atomix-set.atomix* | The Atomix instance to use | null | false | MEDIUM
-| *camel.component.atomix-set.configuration* | The shared component configuration | null | false | MEDIUM
-| *camel.component.atomix-set.configurationUri* | The path to the AtomixClient configuration | null | false | MEDIUM
-| *camel.component.atomix-set.defaultAction* | The default action. One of: [ADD] [CLEAR] [CONTAINS] [IS_EMPTY] [REMOVE] [SIZE] | "ADD" | false | MEDIUM
-| *camel.component.atomix-set.nodes* | The nodes the AtomixClient should connect to | null | false | MEDIUM
-| *camel.component.atomix-set.resultHeader* | The header that wil carry the result. | null | false | MEDIUM
-| *camel.component.atomix-set.transportClassName* | The class name (fqn) of the Atomix transport | "io.atomix.catalyst.transport.netty.NettyTransport" | false | MEDIUM
-| *camel.component.atomix-set.ttl* | The resource ttl. | null | false | MEDIUM
-| *camel.component.atomix-set.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.component.atomix-set.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.atomix-set.defaultResourceConfig* | The cluster wide default resource configuration. | null | false | MEDIUM
-| *camel.component.atomix-set.defaultResourceOptions* | The local default resource options. | null | false | MEDIUM
-| *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 | false | MEDIUM
-| *camel.component.atomix-set.readConsistency* | The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL] | null | false | MEDIUM
-| *camel.component.atomix-set.resourceConfigs* | Cluster wide resources configuration. | null | false | MEDIUM
-| *camel.component.atomix-set.resourceOptions* | Local resources configurations | null | false | MEDIUM
-|===
-
-
-
-The camel-atomix-set source connector has no converters out of the box.
-
-
-
-
-
-The camel-atomix-set source connector has no transforms out of the box.
-
-
-
-
-
-The camel-atomix-set source connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-atomix-value-kafka-connector/src/main/docs/camel-atomix-value-kafka-sink-connector.adoc b/connectors/camel-atomix-value-kafka-connector/src/main/docs/camel-atomix-value-kafka-sink-connector.adoc
deleted file mode 100644
index fd6c595..0000000
--- a/connectors/camel-atomix-value-kafka-connector/src/main/docs/camel-atomix-value-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,82 +0,0 @@
-// kafka-connector options: START
-[[camel-atomix-value-kafka-connector-sink]]
-= camel-atomix-value-kafka-connector sink configuration
-
-Connector Description: Access Atomix's distributed value.
-
-When using camel-atomix-value-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-atomix-value-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.atomixvalue.CamelAtomixvalueSinkConnector
-----
-
-
-The camel-atomix-value sink connector supports 31 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.resourceName* | The distributed resource name | null | true | HIGH
-| *camel.sink.endpoint.atomix* | The Atomix instance to use | null | false | MEDIUM
-| *camel.sink.endpoint.configurationUri* | The Atomix configuration uri. | null | false | MEDIUM
-| *camel.sink.endpoint.defaultAction* | The default action. One of: [SET] [GET] [GET_AND_SET] [COMPARE_AND_SET] | "SET" | false | MEDIUM
-| *camel.sink.endpoint.nodes* | The address of the nodes composing the cluster. | null | false | MEDIUM
-| *camel.sink.endpoint.resultHeader* | The header that wil carry the result. | null | false | MEDIUM
-| *camel.sink.endpoint.transportClassName* | The class name (fqn) of the Atomix transport | "io.atomix.catalyst.transport.netty.NettyTransport" | false | MEDIUM
-| *camel.sink.endpoint.ttl* | The resource ttl. | null | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.defaultResourceConfig* | The cluster wide default resource configuration. | null | false | MEDIUM
-| *camel.sink.endpoint.defaultResourceOptions* | The local default resource options. | null | false | MEDIUM
-| *camel.sink.endpoint.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 | false | MEDIUM
-| *camel.sink.endpoint.readConsistency* | The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL] | null | false | MEDIUM
-| *camel.sink.endpoint.resourceConfigs* | Cluster wide resources configuration. | null | false | MEDIUM
-| *camel.sink.endpoint.resourceOptions* | Local resources configurations | null | false | MEDIUM
-| *camel.component.atomix-value.atomix* | The Atomix instance to use | null | false | MEDIUM
-| *camel.component.atomix-value.configuration* | The shared component configuration | null | false | MEDIUM
-| *camel.component.atomix-value.configurationUri* | The path to the AtomixClient configuration | null | false | MEDIUM
-| *camel.component.atomix-value.defaultAction* | The default action. One of: [SET] [GET] [GET_AND_SET] [COMPARE_AND_SET] | "SET" | false | MEDIUM
-| *camel.component.atomix-value.nodes* | The nodes the AtomixClient should connect to | null | false | MEDIUM
-| *camel.component.atomix-value.resultHeader* | The header that wil carry the result. | null | false | MEDIUM
-| *camel.component.atomix-value.transportClassName* | The class name (fqn) of the Atomix transport | "io.atomix.catalyst.transport.netty.NettyTransport" | false | MEDIUM
-| *camel.component.atomix-value.ttl* | The resource ttl. | null | false | MEDIUM
-| *camel.component.atomix-value.lazyStartProducer* | 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-value.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.atomix-value.defaultResourceConfig* | The cluster wide default resource configuration. | null | false | MEDIUM
-| *camel.component.atomix-value.defaultResource Options* | The local default resource options. | null | false | MEDIUM
-| *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 | false | MEDIUM
-| *camel.component.atomix-value.readConsistency* | The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL] | null | false | MEDIUM
-| *camel.component.atomix-value.resourceConfigs* | Cluster wide resources configuration. | null | false | MEDIUM
-| *camel.component.atomix-value.resourceOptions* | Local resources configurations | null | false | MEDIUM
-|===
-
-
-
-The camel-atomix-value sink connector has no converters out of the box.
-
-
-
-
-
-The camel-atomix-value sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-atomix-value sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-atomix-value-kafka-connector/src/main/docs/camel-atomix-value-kafka-source-connector.adoc b/connectors/camel-atomix-value-kafka-connector/src/main/docs/camel-atomix-value-kafka-source-connector.adoc
deleted file mode 100644
index 4c8a650..0000000
--- a/connectors/camel-atomix-value-kafka-connector/src/main/docs/camel-atomix-value-kafka-source-connector.adoc
+++ /dev/null
@@ -1,84 +0,0 @@
-// kafka-connector options: START
-[[camel-atomix-value-kafka-connector-source]]
-= camel-atomix-value-kafka-connector source configuration
-
-Connector description: Access Atomix's distributed value.
-
-When using camel-atomix-value-kafka-connector as source make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-atomix-value-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Source connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.atomixvalue.CamelAtomixvalueSourceConnector
-----
-
-
-The camel-atomix-value source connector supports 33 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.source.path.resourceName* | The distributed resource name | null | true | HIGH
-| *camel.source.endpoint.atomix* | The Atomix instance to use | null | false | MEDIUM
-| *camel.source.endpoint.configurationUri* | The Atomix configuration uri. | null | false | MEDIUM
-| *camel.source.endpoint.defaultAction* | The default action. One of: [SET] [GET] [GET_AND_SET] [COMPARE_AND_SET] | "SET" | false | MEDIUM
-| *camel.source.endpoint.nodes* | The address of the nodes composing the cluster. | null | false | MEDIUM
-| *camel.source.endpoint.resultHeader* | The header that wil carry the result. | null | false | MEDIUM
-| *camel.source.endpoint.transportClassName* | The class name (fqn) of the Atomix transport | "io.atomix.catalyst.transport.netty.NettyTransport" | false | MEDIUM
-| *camel.source.endpoint.ttl* | The resource ttl. | null | false | MEDIUM
-| *camel.source.endpoint.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | false | MEDIUM
-| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | false | MEDIUM
-| *camel.source.endpoint.defaultResourceConfig* | The cluster wide default resource configuration. | null | false | MEDIUM
-| *camel.source.endpoint.defaultResourceOptions* | The local default resource options. | null | false | MEDIUM
-| *camel.source.endpoint.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 | false | MEDIUM
-| *camel.source.endpoint.readConsistency* | The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL] | null | false | MEDIUM
-| *camel.source.endpoint.resourceConfigs* | Cluster wide resources configuration. | null | false | MEDIUM
-| *camel.source.endpoint.resourceOptions* | Local resources configurations | null | false | MEDIUM
-| *camel.component.atomix-value.atomix* | The Atomix instance to use | null | false | MEDIUM
-| *camel.component.atomix-value.configuration* | The shared component configuration | null | false | MEDIUM
-| *camel.component.atomix-value.configurationUri* | The path to the AtomixClient configuration | null | false | MEDIUM
-| *camel.component.atomix-value.defaultAction* | The default action. One of: [SET] [GET] [GET_AND_SET] [COMPARE_AND_SET] | "SET" | false | MEDIUM
-| *camel.component.atomix-value.nodes* | The nodes the AtomixClient should connect to | null | false | MEDIUM
-| *camel.component.atomix-value.resultHeader* | The header that wil carry the result. | null | false | MEDIUM
-| *camel.component.atomix-value.transportClassName* | The class name (fqn) of the Atomix transport | "io.atomix.catalyst.transport.netty.NettyTransport" | false | MEDIUM
-| *camel.component.atomix-value.ttl* | The resource ttl. | null | false | MEDIUM
-| *camel.component.atomix-value.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.component.atomix-value.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.atomix-value.defaultResourceConfig* | The cluster wide default resource configuration. | null | false | MEDIUM
-| *camel.component.atomix-value.defaultResource Options* | The local default resource options. | null | false | MEDIUM
-| *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 | false | MEDIUM
-| *camel.component.atomix-value.readConsistency* | The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL] | null | false | MEDIUM
-| *camel.component.atomix-value.resourceConfigs* | Cluster wide resources configuration. | null | false | MEDIUM
-| *camel.component.atomix-value.resourceOptions* | Local resources configurations | null | false | MEDIUM
-|===
-
-
-
-The camel-atomix-value source connector has no converters out of the box.
-
-
-
-
-
-The camel-atomix-value source connector has no transforms out of the box.
-
-
-
-
-
-The camel-atomix-value source connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-avro-kafka-connector/src/main/docs/camel-avro-kafka-sink-connector.adoc b/connectors/camel-avro-kafka-connector/src/main/docs/camel-avro-kafka-sink-connector.adoc
deleted file mode 100644
index 56d2b32..0000000
--- a/connectors/camel-avro-kafka-connector/src/main/docs/camel-avro-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,71 +0,0 @@
-// kafka-connector options: START
-[[camel-avro-kafka-connector-sink]]
-= camel-avro-kafka-connector sink configuration
-
-Connector Description: Produce or consume Apache Avro RPC services.
-
-When using camel-avro-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-avro-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.avro.CamelAvroSinkConnector
-----
-
-
-The camel-avro sink connector supports 20 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.transport* | Transport to use, can be either http or netty One of: [http] [netty] | null | true | HIGH
-| *camel.sink.path.port* | Port number to use | null | true | HIGH
-| *camel.sink.path.host* | Hostname to use | null | true | HIGH
-| *camel.sink.path.messageName* | The name of the message to send. | null | false | MEDIUM
-| *camel.sink.endpoint.protocol* | Avro protocol to use | null | false | MEDIUM
-| *camel.sink.endpoint.protocolClassName* | Avro protocol to use defined by the FQN class name | null | false | MEDIUM
-| *camel.sink.endpoint.protocolLocation* | Avro protocol location | null | false | MEDIUM
-| *camel.sink.endpoint.reflectionProtocol* | If protocol object provided is reflection protocol. Should be used only with protocol parameter because for protocolClassName protocol type will be auto detected | false | false | MEDIUM
-| *camel.sink.endpoint.singleParameter* | If true, consumer parameter won't be wrapped into array. Will fail if protocol specifies more then 1 parameter for the message | false | false | MEDIUM
-| *camel.sink.endpoint.uriAuthority* | Authority to use (username and password) | null | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.component.avro.protocol* | Avro protocol to use | null | false | MEDIUM
-| *camel.component.avro.protocolClassName* | Avro protocol to use defined by the FQN class name | null | false | MEDIUM
-| *camel.component.avro.protocolLocation* | Avro protocol location | null | false | MEDIUM
-| *camel.component.avro.reflectionProtocol* | If protocol object provided is reflection protocol. Should be used only with protocol parameter because for protocolClassName protocol type will be auto detected | false | false | MEDIUM
-| *camel.component.avro.singleParameter* | If true, consumer parameter won't be wrapped into array. Will fail if protocol specifies more then 1 parameter for the message | false | false | MEDIUM
-| *camel.component.avro.uriAuthority* | Authority to use (username and password) | null | false | MEDIUM
-| *camel.component.avro.lazyStartProducer* | 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 cr [...]
-| *camel.component.avro.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.avro.configuration* | To use a shared AvroConfiguration to configure options once | null | false | MEDIUM
-|===
-
-
-
-The camel-avro sink connector has no converters out of the box.
-
-
-
-
-
-The camel-avro sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-avro sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-avro-kafka-connector/src/main/docs/camel-avro-kafka-source-connector.adoc b/connectors/camel-avro-kafka-connector/src/main/docs/camel-avro-kafka-source-connector.adoc
deleted file mode 100644
index 9481b42..0000000
--- a/connectors/camel-avro-kafka-connector/src/main/docs/camel-avro-kafka-source-connector.adoc
+++ /dev/null
@@ -1,73 +0,0 @@
-// kafka-connector options: START
-[[camel-avro-kafka-connector-source]]
-= camel-avro-kafka-connector source configuration
-
-Connector description: Produce or consume Apache Avro RPC services.
-
-When using camel-avro-kafka-connector as source make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-avro-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Source connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.avro.CamelAvroSourceConnector
-----
-
-
-The camel-avro source connector supports 22 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.source.path.transport* | Transport to use, can be either http or netty One of: [http] [netty] | null | true | HIGH
-| *camel.source.path.port* | Port number to use | null | true | HIGH
-| *camel.source.path.host* | Hostname to use | null | true | HIGH
-| *camel.source.path.messageName* | The name of the message to send. | null | false | MEDIUM
-| *camel.source.endpoint.protocol* | Avro protocol to use | null | false | MEDIUM
-| *camel.source.endpoint.protocolClassName* | Avro protocol to use defined by the FQN class name | null | false | MEDIUM
-| *camel.source.endpoint.protocolLocation* | Avro protocol location | null | false | MEDIUM
-| *camel.source.endpoint.reflectionProtocol* | If protocol object provided is reflection protocol. Should be used only with protocol parameter because for protocolClassName protocol type will be auto detected | false | false | MEDIUM
-| *camel.source.endpoint.singleParameter* | If true, consumer parameter won't be wrapped into array. Will fail if protocol specifies more then 1 parameter for the message | false | false | MEDIUM
-| *camel.source.endpoint.uriAuthority* | Authority to use (username and password) | null | false | MEDIUM
-| *camel.source.endpoint.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | false | MEDIUM
-| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | false | MEDIUM
-| *camel.component.avro.protocol* | Avro protocol to use | null | false | MEDIUM
-| *camel.component.avro.protocolClassName* | Avro protocol to use defined by the FQN class name | null | false | MEDIUM
-| *camel.component.avro.protocolLocation* | Avro protocol location | null | false | MEDIUM
-| *camel.component.avro.reflectionProtocol* | If protocol object provided is reflection protocol. Should be used only with protocol parameter because for protocolClassName protocol type will be auto detected | false | false | MEDIUM
-| *camel.component.avro.singleParameter* | If true, consumer parameter won't be wrapped into array. Will fail if protocol specifies more then 1 parameter for the message | false | false | MEDIUM
-| *camel.component.avro.uriAuthority* | Authority to use (username and password) | null | false | MEDIUM
-| *camel.component.avro.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.component.avro.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.avro.configuration* | To use a shared AvroConfiguration to configure options once | null | false | MEDIUM
-|===
-
-
-
-The camel-avro source connector has no converters out of the box.
-
-
-
-
-
-The camel-avro source connector has no transforms out of the box.
-
-
-
-
-
-The camel-avro source connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-aws-secrets-manager-kafka-connector/src/main/docs/camel-aws-secrets-manager-kafka-sink-connector.adoc b/connectors/camel-aws-secrets-manager-kafka-connector/src/main/docs/camel-aws-secrets-manager-kafka-sink-connector.adoc
deleted file mode 100644
index 9ae4964..0000000
--- a/connectors/camel-aws-secrets-manager-kafka-connector/src/main/docs/camel-aws-secrets-manager-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,84 +0,0 @@
-// kafka-connector options: START
-[[camel-aws-secrets-manager-kafka-connector-sink]]
-= camel-aws-secrets-manager-kafka-connector sink configuration
-
-Connector Description: Manage AWS Secrets Manager services using AWS SDK version 2.x.
-
-When using camel-aws-secrets-manager-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-aws-secrets-manager-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.awssecretsmanager.CamelAwssecretsmanagerSinkConnector
-----
-
-
-The camel-aws-secrets-manager sink connector supports 33 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.label* | Logical name | null | true | HIGH
-| *camel.sink.endpoint.binaryPayload* | Set if the secret is binary or not | false | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.operation* | The operation to perform One of: [listSecrets] [createSecret] [getSecret] [describeSecret] [deleteSecret] [rotateSecret] [updateSecret] [replicateSecretToRegions] | null | true | HIGH
-| *camel.sink.endpoint.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.sink.endpoint.pojoRequest* | If we want to use a POJO request as body or not | false | false | MEDIUM
-| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the Secrets Manager client | null | false | MEDIUM
-| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the Secrets Manager client | null | false | MEDIUM
-| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the Secrets Manager client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *camel.sink.endpoint.region* | The region in which Secrets Manager 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() | null | false | MEDIUM
-| *camel.sink.endpoint.secretsManagerClient* | To use a existing configured AWS Secrets Manager as client | null | false | MEDIUM
-| *camel.sink.endpoint.trustAllCertificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.sink.endpoint.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.sink.endpoint.useDefaultCredentialsProvider* | Set whether the Translate client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | false | false | MEDIUM
-| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-| *camel.component.aws-secrets-manager.binaryPayload* | Set if the secret is binary or not | false | false | MEDIUM
-| *camel.component.aws-secrets-manager.configuration* | Component configuration | null | false | MEDIUM
-| *camel.component.aws-secrets-manager.lazyStart 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.aws-secrets-manager.operation* | The operation to perform One of: [listSecrets] [createSecret] [getSecret] [describeSecret] [deleteSecret] [rotateSecret] [updateSecret] [replicateSecretToRegions] | null | true | HIGH
-| *camel.component.aws-secrets-manager.override Endpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.component.aws-secrets-manager.pojoRequest* | If we want to use a POJO request as body or not | false | false | MEDIUM
-| *camel.component.aws-secrets-manager.proxyHost* | To define a proxy host when instantiating the Secrets Manager client | null | false | MEDIUM
-| *camel.component.aws-secrets-manager.proxyPort* | To define a proxy port when instantiating the Secrets Manager client | null | false | MEDIUM
-| *camel.component.aws-secrets-manager.proxyProtocol* | To define a proxy protocol when instantiating the Secrets Manager client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *camel.component.aws-secrets-manager.region* | The region in which Secrets Manager 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() | null | false | MEDIUM
-| *camel.component.aws-secrets-manager.secretsManager Client* | To use a existing configured AWS Secrets Manager as client | null | false | MEDIUM
-| *camel.component.aws-secrets-manager.trustAll Certificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.component.aws-secrets-manager.uriEndpoint Override* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.component.aws-secrets-manager.useDefault CredentialsProvider* | Set whether the Translate client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | false | false | MEDIUM
-| *camel.component.aws-secrets-manager.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 | false | MEDIUM
-| *camel.component.aws-secrets-manager.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.component.aws-secrets-manager.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-|===
-
-
-
-The camel-aws-secrets-manager sink connector has no converters out of the box.
-
-
-
-
-
-The camel-aws-secrets-manager sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-aws-secrets-manager sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-aws2-athena-kafka-connector/src/main/docs/camel-aws2-athena-kafka-sink-connector.adoc b/connectors/camel-aws2-athena-kafka-connector/src/main/docs/camel-aws2-athena-kafka-sink-connector.adoc
deleted file mode 100644
index ef2eef1..0000000
--- a/connectors/camel-aws2-athena-kafka-connector/src/main/docs/camel-aws2-athena-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,110 +0,0 @@
-// kafka-connector options: START
-[[camel-aws2-athena-kafka-connector-sink]]
-= camel-aws2-athena-kafka-connector sink configuration
-
-Connector Description: Access AWS Athena service using AWS SDK version 2.x.
-
-When using camel-aws2-athena-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-aws2-athena-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.aws2athena.CamelAws2athenaSinkConnector
-----
-
-
-The camel-aws2-athena sink connector supports 59 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.label* | Logical name | null | true | HIGH
-| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key. | null | false | MEDIUM
-| *camel.sink.endpoint.amazonAthenaClient* | The AmazonAthena instance to use as the client. | null | false | MEDIUM
-| *camel.sink.endpoint.database* | The Athena database to use. | null | false | MEDIUM
-| *camel.sink.endpoint.delay* | Milliseconds before the next poll for query execution status. See the section 'Waiting for Query Completion and Retrying Failed Queries' to learn more. | 2000L | false | MEDIUM
-| *camel.sink.endpoint.encryptionOption* | The encryption type to use when storing query results in S3. One of SSE_S3, SSE_KMS, or CSE_KMS. One of: [SSE_S3] [SSE_KMS] [CSE_KMS] [null] | null | false | MEDIUM
-| *camel.sink.endpoint.includeTrace* | Include useful trace information at the beginning of queries as an SQL comment (prefixed with --). | false | false | MEDIUM
-| *camel.sink.endpoint.initialDelay* | Milliseconds before the first poll for query execution status. See the section 'Waiting for Query Completion and Retrying Failed Queries' to learn more. | 1000L | false | MEDIUM
-| *camel.sink.endpoint.kmsKey* | For SSE-KMS and CSE-KMS, this is the KMS key ARN or ID. | null | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.maxAttempts* | 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 | false | MEDIUM
-| *camel.sink.endpoint.maxResults* | 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. | null | false | MEDIUM
-| *camel.sink.endpoint.nextToken* | Pagination token to use in the case where the response from the previous request was truncated. | null | false | MEDIUM
-| *camel.sink.endpoint.operation* | The Athena API function to call. One of: [getQueryExecution] [getQueryResults] [listQueryExecutions] [startQueryExecution] | "startQueryExecution" | false | MEDIUM
-| *camel.sink.endpoint.outputLocation* | 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 ('/'). | null | false | MEDIUM
-| *camel.sink.endpoint.outputType* | 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). One of: [StreamList] [SelectList] [S3Pointer] | "StreamList" | false | MEDIUM
-| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the Athena client. | null | false | MEDIUM
-| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the Athena client. | null | false | MEDIUM
-| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the Athena client. One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *camel.sink.endpoint.queryExecutionId* | The unique ID identifying the query execution. | null | false | MEDIUM
-| *camel.sink.endpoint.queryString* | 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. | null | false | MEDIUM
-| *camel.sink.endpoint.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(). | null | false | MEDIUM
-| *camel.sink.endpoint.resetWaitTimeoutOnRetry* | 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 | false | MEDIUM
-| *camel.sink.endpoint.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 Retrying Fail [...]
-| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key. | null | false | MEDIUM
-| *camel.sink.endpoint.useDefaultCredentialsProvider* | Set whether the Athena client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in | false | false | MEDIUM
-| *camel.sink.endpoint.waitTimeout* | 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. | 0L | false | MEDIUM
-| *camel.sink.endpoint.workGroup* | The workgroup to use for running the query. | null | false | MEDIUM
-| *camel.sink.endpoint.clientRequestToken* | A unique string to ensure issues queries are idempotent. It is unlikely you will need to set this. | null | false | MEDIUM
-| *camel.component.aws2-athena.accessKey* | Amazon AWS Access Key. | null | false | MEDIUM
-| *camel.component.aws2-athena.amazonAthenaClient* | The AmazonAthena instance to use as the client. | null | false | MEDIUM
-| *camel.component.aws2-athena.configuration* | The component configuration. | null | false | MEDIUM
-| *camel.component.aws2-athena.database* | The Athena database to use. | null | false | MEDIUM
-| *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. | 2000L | false | MEDIUM
-| *camel.component.aws2-athena.encryptionOption* | The encryption type to use when storing query results in S3. One of SSE_S3, SSE_KMS, or CSE_KMS. One of: [SSE_S3] [SSE_KMS] [CSE_KMS] [null] | null | false | MEDIUM
-| *camel.component.aws2-athena.includeTrace* | Include useful trace information at the beginning of queries as an SQL comment (prefixed with --). | false | false | MEDIUM
-| *camel.component.aws2-athena.initialDelay* | Milliseconds before the first poll for query execution status. See the section 'Waiting for Query Completion and Retrying Failed Queries' to learn more. | 1000L | false | MEDIUM
-| *camel.component.aws2-athena.kmsKey* | For SSE-KMS and CSE-KMS, this is the KMS key ARN or ID. | null | false | MEDIUM
-| *camel.component.aws2-athena.lazyStartProducer* | 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.aws2-athena.maxAttempts* | 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 | false | MEDIUM
-| *camel.component.aws2-athena.maxResults* | 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. | null | false | MEDIUM
-| *camel.component.aws2-athena.nextToken* | Pagination token to use in the case where the response from the previous request was truncated. | null | false | MEDIUM
-| *camel.component.aws2-athena.operation* | The Athena API function to call. One of: [getQueryExecution] [getQueryResults] [listQueryExecutions] [startQueryExecution] | "startQueryExecution" | false | MEDIUM
-| *camel.component.aws2-athena.outputLocation* | 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 ('/'). | null | false | MEDIUM
-| *camel.component.aws2-athena.outputType* | 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). One of: [StreamList] [SelectList] [S3Pointer] | "StreamList" | false | MEDIUM
-| *camel.component.aws2-athena.proxyHost* | To define a proxy host when instantiating the Athena client. | null | false | MEDIUM
-| *camel.component.aws2-athena.proxyPort* | To define a proxy port when instantiating the Athena client. | null | false | MEDIUM
-| *camel.component.aws2-athena.proxyProtocol* | To define a proxy protocol when instantiating the Athena client. One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *camel.component.aws2-athena.queryExecutionId* | The unique ID identifying the query execution. | null | false | MEDIUM
-| *camel.component.aws2-athena.queryString* | 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. | null | false | MEDIUM
-| *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(). | null | false | MEDIUM
-| *camel.component.aws2-athena.resetWaitTimeoutOn 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 | false | MEDIUM
-| *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.secretKey* | Amazon AWS Secret Key. | null | false | MEDIUM
-| *camel.component.aws2-athena.useDefaultCredentials Provider* | Set whether the Athena client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in | false | false | MEDIUM
-| *camel.component.aws2-athena.waitTimeout* | 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. | 0L | false | MEDIUM
-| *camel.component.aws2-athena.workGroup* | The workgroup to use for running the query. | null | false | MEDIUM
-| *camel.component.aws2-athena.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.aws2-athena.clientRequestToken* | A unique string to ensure issues queries are idempotent. It is unlikely you will need to set this. | null | false | MEDIUM
-|===
-
-
-
-The camel-aws2-athena sink connector has no converters out of the box.
-
-
-
-
-
-The camel-aws2-athena sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-aws2-athena sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-aws2-cw-kafka-connector/src/main/docs/camel-aws2-cw-kafka-sink-connector.adoc b/connectors/camel-aws2-cw-kafka-connector/src/main/docs/camel-aws2-cw-kafka-sink-connector.adoc
deleted file mode 100644
index 4d4ef6c..0000000
--- a/connectors/camel-aws2-cw-kafka-connector/src/main/docs/camel-aws2-cw-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,86 +0,0 @@
-// kafka-connector options: START
-[[camel-aws2-cw-kafka-connector-sink]]
-= camel-aws2-cw-kafka-connector sink configuration
-
-Connector Description: Sending metrics to AWS CloudWatch using AWS SDK version 2.x.
-
-When using camel-aws2-cw-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-aws2-cw-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.aws2cw.CamelAws2cwSinkConnector
-----
-
-
-The camel-aws2-cw sink connector supports 35 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.namespace* | The metric namespace | null | true | HIGH
-| *camel.sink.endpoint.amazonCwClient* | To use the AmazonCloudWatch as the client | null | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.name* | The metric name | null | false | MEDIUM
-| *camel.sink.endpoint.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the CW client | null | false | MEDIUM
-| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the CW client | null | false | MEDIUM
-| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the CW client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *camel.sink.endpoint.region* | The region in which CW 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() | null | false | MEDIUM
-| *camel.sink.endpoint.timestamp* | The metric timestamp | null | false | MEDIUM
-| *camel.sink.endpoint.trustAllCertificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.sink.endpoint.unit* | The metric unit | null | false | MEDIUM
-| *camel.sink.endpoint.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.sink.endpoint.useDefaultCredentialsProvider* | 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 | false | MEDIUM
-| *camel.sink.endpoint.value* | The metric value | null | false | MEDIUM
-| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-| *camel.component.aws2-cw.amazonCwClient* | To use the AmazonCloudWatch as the client | null | false | MEDIUM
-| *camel.component.aws2-cw.configuration* | The component configuration | null | false | MEDIUM
-| *camel.component.aws2-cw.lazyStartProducer* | 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.aws2-cw.name* | The metric name | null | false | MEDIUM
-| *camel.component.aws2-cw.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.component.aws2-cw.proxyHost* | To define a proxy host when instantiating the CW client | null | false | MEDIUM
-| *camel.component.aws2-cw.proxyPort* | To define a proxy port when instantiating the CW client | null | false | MEDIUM
-| *camel.component.aws2-cw.proxyProtocol* | To define a proxy protocol when instantiating the CW client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *camel.component.aws2-cw.region* | The region in which CW 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() | null | false | MEDIUM
-| *camel.component.aws2-cw.timestamp* | The metric timestamp | null | false | MEDIUM
-| *camel.component.aws2-cw.trustAllCertificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.component.aws2-cw.unit* | The metric unit | null | false | MEDIUM
-| *camel.component.aws2-cw.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.component.aws2-cw.useDefaultCredentials 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 | false | MEDIUM
-| *camel.component.aws2-cw.value* | The metric value | null | false | MEDIUM
-| *camel.component.aws2-cw.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.aws2-cw.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.component.aws2-cw.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-|===
-
-
-
-The camel-aws2-cw sink connector has no converters out of the box.
-
-
-
-
-
-The camel-aws2-cw sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-aws2-cw sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-aws2-ddb-kafka-connector/src/main/docs/camel-aws2-ddb-kafka-sink-connector.adoc b/connectors/camel-aws2-ddb-kafka-connector/src/main/docs/camel-aws2-ddb-kafka-sink-connector.adoc
deleted file mode 100644
index 3e73ea1..0000000
--- a/connectors/camel-aws2-ddb-kafka-connector/src/main/docs/camel-aws2-ddb-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,92 +0,0 @@
-// kafka-connector options: START
-[[camel-aws2-ddb-kafka-connector-sink]]
-= camel-aws2-ddb-kafka-connector sink configuration
-
-Connector Description: Store and retrieve data from AWS DynamoDB service using AWS SDK version 2.x.
-
-When using camel-aws2-ddb-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-aws2-ddb-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.aws2ddb.CamelAws2ddbSinkConnector
-----
-
-
-The camel-aws2-ddb sink connector supports 41 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.tableName* | The name of the table currently worked with. | null | true | HIGH
-| *camel.sink.endpoint.amazonDDBClient* | To use the AmazonDynamoDB as the client | null | false | MEDIUM
-| *camel.sink.endpoint.consistentRead* | Determines whether or not strong consistency should be enforced when data is read. | false | false | MEDIUM
-| *camel.sink.endpoint.keyAttributeName* | Attribute name when creating table | null | false | MEDIUM
-| *camel.sink.endpoint.keyAttributeType* | Attribute type when creating table | null | false | MEDIUM
-| *camel.sink.endpoint.keyScalarType* | The key scalar type, it can be S (String), N (Number) and B (Bytes) | null | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.operation* | What operation to perform One of: [BatchGetItems] [DeleteItem] [DeleteTable] [DescribeTable] [GetItem] [PutItem] [Query] [Scan] [UpdateItem] [UpdateTable] | "PutItem" | false | MEDIUM
-| *camel.sink.endpoint.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the DDB client | null | false | MEDIUM
-| *camel.sink.endpoint.proxyPort* | 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() | null | false | MEDIUM
-| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the DDB client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *camel.sink.endpoint.readCapacity* | The provisioned throughput to reserve for reading resources from your table | null | false | MEDIUM
-| *camel.sink.endpoint.region* | The region in which DDB client needs to work | null | false | MEDIUM
-| *camel.sink.endpoint.trustAllCertificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.sink.endpoint.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.sink.endpoint.useDefaultCredentialsProvider* | 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 | false | MEDIUM
-| *camel.sink.endpoint.writeCapacity* | The provisioned throughput to reserved for writing resources to your table | null | false | MEDIUM
-| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-| *camel.component.aws2-ddb.amazonDDBClient* | To use the AmazonDynamoDB as the client | null | false | MEDIUM
-| *camel.component.aws2-ddb.configuration* | The component configuration | null | false | MEDIUM
-| *camel.component.aws2-ddb.consistentRead* | Determines whether or not strong consistency should be enforced when data is read. | false | false | MEDIUM
-| *camel.component.aws2-ddb.keyAttributeName* | Attribute name when creating table | null | false | MEDIUM
-| *camel.component.aws2-ddb.keyAttributeType* | Attribute type when creating table | null | false | MEDIUM
-| *camel.component.aws2-ddb.keyScalarType* | The key scalar type, it can be S (String), N (Number) and B (Bytes) | null | false | MEDIUM
-| *camel.component.aws2-ddb.lazyStartProducer* | 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.aws2-ddb.operation* | What operation to perform One of: [BatchGetItems] [DeleteItem] [DeleteTable] [DescribeTable] [GetItem] [PutItem] [Query] [Scan] [UpdateItem] [UpdateTable] | "PutItem" | false | MEDIUM
-| *camel.component.aws2-ddb.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.component.aws2-ddb.proxyHost* | To define a proxy host when instantiating the DDB client | null | false | MEDIUM
-| *camel.component.aws2-ddb.proxyPort* | 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() | null | false | MEDIUM
-| *camel.component.aws2-ddb.proxyProtocol* | To define a proxy protocol when instantiating the DDB client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *camel.component.aws2-ddb.readCapacity* | The provisioned throughput to reserve for reading resources from your table | null | false | MEDIUM
-| *camel.component.aws2-ddb.region* | The region in which DDB client needs to work | null | false | MEDIUM
-| *camel.component.aws2-ddb.trustAllCertificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.component.aws2-ddb.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.component.aws2-ddb.useDefaultCredentials 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 | false | MEDIUM
-| *camel.component.aws2-ddb.writeCapacity* | The provisioned throughput to reserved for writing resources to your table | null | false | MEDIUM
-| *camel.component.aws2-ddb.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.aws2-ddb.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.component.aws2-ddb.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-|===
-
-
-
-The camel-aws2-ddb sink connector has no converters out of the box.
-
-
-
-
-
-The camel-aws2-ddb sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-aws2-ddb sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-aws2-ddbstream-kafka-connector/src/main/docs/camel-aws2-ddbstream-kafka-source-connector.adoc b/connectors/camel-aws2-ddbstream-kafka-connector/src/main/docs/camel-aws2-ddbstream-kafka-source-connector.adoc
deleted file mode 100644
index 492d75a..0000000
--- a/connectors/camel-aws2-ddbstream-kafka-connector/src/main/docs/camel-aws2-ddbstream-kafka-source-connector.adoc
+++ /dev/null
@@ -1,102 +0,0 @@
-// kafka-connector options: START
-[[camel-aws2-ddbstream-kafka-connector-source]]
-= camel-aws2-ddbstream-kafka-connector source configuration
-
-Connector description: Receive messages from AWS DynamoDB Stream service using AWS SDK version 2.x.
-
-When using camel-aws2-ddbstream-kafka-connector as source make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-aws2-ddbstream-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Source connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.aws2ddbstream.CamelAws2ddbstreamSourceConnector
-----
-
-
-The camel-aws2-ddbstream source connector supports 51 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.source.path.tableName* | Name of the dynamodb table | null | true | HIGH
-| *camel.source.endpoint.amazonDynamoDbStreamsClient* | Amazon DynamoDB client to use for all requests for this endpoint | null | false | MEDIUM
-| *camel.source.endpoint.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.source.endpoint.iteratorType* | 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. One of: [TRIM_HORIZON] [LATEST] [AT_SEQUENCE_NUMBER] [AFTER_SEQUENCE_NUMBER] [null] | "LATEST" | false | MEDIUM
-| *camel.source.endpoint.maxResultsPerRequest* | Maximum number of records that will be fetched in each poll | null | false | MEDIUM
-| *camel.source.endpoint.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.source.endpoint.proxyHost* | To define a proxy host when instantiating the DDBStreams client | null | false | MEDIUM
-| *camel.source.endpoint.proxyPort* | To define a proxy port when instantiating the DDBStreams client | null | false | MEDIUM
-| *camel.source.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the DDBStreams client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *camel.source.endpoint.region* | The region in which DDBStreams client needs to work | null | false | MEDIUM
-| *camel.source.endpoint.sendEmptyMessageWhenIdle* | If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead. | false | false | MEDIUM
-| *camel.source.endpoint.sequenceNumberProvider* | 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. | null | false | MEDIUM
-| *camel.source.endpoint.trustAllCertificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.source.endpoint.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.source.endpoint.useDefaultCredentials Provider* | Set whether the DynamoDB Streams client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | false | false | MEDIUM
-| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | false | MEDIUM
-| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | false | MEDIUM
-| *camel.source.endpoint.pollStrategy* | A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel. | null | false | MEDIUM
-| *camel.source.endpoint.backoffErrorThreshold* | The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in. | null | false | MEDIUM
-| *camel.source.endpoint.backoffIdleThreshold* | The number of subsequent idle polls that should happen before the backoffMultipler should kick-in. | null | false | MEDIUM
-| *camel.source.endpoint.backoffMultiplier* | To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured. | null | false | MEDIUM
-| *camel.source.endpoint.delay* | Milliseconds before the next poll. | 500L | false | MEDIUM
-| *camel.source.endpoint.greedy* | If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages. | false | false | MEDIUM
-| *camel.source.endpoint.initialDelay* | Milliseconds before the first poll starts. | 1000L | false | MEDIUM
-| *camel.source.endpoint.repeatCount* | Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever. | 0L | false | MEDIUM
-| *camel.source.endpoint.runLoggingLevel* | The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that. One of: [TRACE] [DEBUG] [INFO] [WARN] [ERROR] [OFF] | "TRACE" | false | MEDIUM
-| *camel.source.endpoint.scheduledExecutorService* | Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool. | null | false | MEDIUM
-| *camel.source.endpoint.scheduler* | To use a cron scheduler from either camel-spring or camel-quartz component. Use value spring or quartz for built in scheduler | "none" | false | MEDIUM
-| *camel.source.endpoint.schedulerProperties* | To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler. | null | false | MEDIUM
-| *camel.source.endpoint.startScheduler* | Whether the scheduler should be auto started. | true | false | MEDIUM
-| *camel.source.endpoint.timeUnit* | Time unit for initialDelay and delay options. One of: [NANOSECONDS] [MICROSECONDS] [MILLISECONDS] [SECONDS] [MINUTES] [HOURS] [DAYS] | "MILLISECONDS" | false | MEDIUM
-| *camel.source.endpoint.useFixedDelay* | Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details. | true | false | MEDIUM
-| *camel.source.endpoint.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.source.endpoint.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-| *camel.component.aws2-ddbstream.amazonDynamoDb StreamsClient* | Amazon DynamoDB client to use for all requests for this endpoint | null | false | MEDIUM
-| *camel.component.aws2-ddbstream.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.component.aws2-ddbstream.configuration* | The component configuration | null | false | MEDIUM
-| *camel.component.aws2-ddbstream.iteratorType* | 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. One of: [TRIM_HORIZON] [LATEST] [AT_SEQUENCE_NUMBER] [AFTER_SEQUENCE_NUMBER] [null] | "LATEST" | false | MEDIUM
-| *camel.component.aws2-ddbstream.maxResultsPer Request* | Maximum number of records that will be fetched in each poll | null | false | MEDIUM
-| *camel.component.aws2-ddbstream.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.component.aws2-ddbstream.proxyHost* | To define a proxy host when instantiating the DDBStreams client | null | false | MEDIUM
-| *camel.component.aws2-ddbstream.proxyPort* | To define a proxy port when instantiating the DDBStreams client | null | false | MEDIUM
-| *camel.component.aws2-ddbstream.proxyProtocol* | To define a proxy protocol when instantiating the DDBStreams client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *camel.component.aws2-ddbstream.region* | The region in which DDBStreams client needs to work | null | false | MEDIUM
-| *camel.component.aws2-ddbstream.sequenceNumber 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. | null | false | MEDIUM
-| *camel.component.aws2-ddbstream.trustAll Certificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.component.aws2-ddbstream.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.component.aws2-ddbstream.useDefault CredentialsProvider* | Set whether the DynamoDB Streams client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | false | false | MEDIUM
-| *camel.component.aws2-ddbstream.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.aws2-ddbstream.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.component.aws2-ddbstream.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-|===
-
-
-
-The camel-aws2-ddbstream source connector has no converters out of the box.
-
-
-
-
-
-The camel-aws2-ddbstream source connector has no transforms out of the box.
-
-
-
-
-
-The camel-aws2-ddbstream source connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-aws2-ec2-kafka-connector/src/main/docs/camel-aws2-ec2-kafka-sink-connector.adoc b/connectors/camel-aws2-ec2-kafka-connector/src/main/docs/camel-aws2-ec2-kafka-sink-connector.adoc
deleted file mode 100644
index 3930557..0000000
--- a/connectors/camel-aws2-ec2-kafka-connector/src/main/docs/camel-aws2-ec2-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,82 +0,0 @@
-// kafka-connector options: START
-[[camel-aws2-ec2-kafka-connector-sink]]
-= camel-aws2-ec2-kafka-connector sink configuration
-
-Connector Description: Manage AWS EC2 instances using AWS SDK version 2.x.
-
-When using camel-aws2-ec2-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-aws2-ec2-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.aws2ec2.CamelAws2ec2SinkConnector
-----
-
-
-The camel-aws2-ec2 sink connector supports 31 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.label* | Logical name | null | true | HIGH
-| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.sink.endpoint.amazonEc2Client* | To use a existing configured AmazonEC2Client as client | null | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.operation* | The operation to perform. It can be createAndRunInstances, startInstances, stopInstances, terminateInstances, describeInstances, describeInstancesStatus, rebootInstances, monitorInstances, unmonitorInstances, createTags or deleteTags One of: [createAndRunInstances] [startInstances] [stopInstances] [terminateInstances] [describeInstances] [describeInstancesStatus] [rebootInstances] [monitorInstances] [unmonitorInstances] [createTags] [deleteTags] | null [...]
-| *camel.sink.endpoint.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.sink.endpoint.pojoRequest* | If we want to use a POJO request as body or not | false | false | MEDIUM
-| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the EC2 client | null | false | MEDIUM
-| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the EC2 client | null | false | MEDIUM
-| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the EC2 client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *camel.sink.endpoint.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() | null | false | MEDIUM
-| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-| *camel.sink.endpoint.trustAllCertificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.sink.endpoint.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.sink.endpoint.useDefaultCredentialsProvider* | Set whether the EC2 client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | false | false | MEDIUM
-| *camel.component.aws2-ec2.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.component.aws2-ec2.amazonEc2Client* | To use a existing configured AmazonEC2Client as client | null | false | MEDIUM
-| *camel.component.aws2-ec2.configuration* | The component configuration | null | false | MEDIUM
-| *camel.component.aws2-ec2.lazyStartProducer* | 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.aws2-ec2.operation* | The operation to perform. It can be createAndRunInstances, startInstances, stopInstances, terminateInstances, describeInstances, describeInstancesStatus, rebootInstances, monitorInstances, unmonitorInstances, createTags or deleteTags One of: [createAndRunInstances] [startInstances] [stopInstances] [terminateInstances] [describeInstances] [describeInstancesStatus] [rebootInstances] [monitorInstances] [unmonitorInstances] [createTags] [deleteTags] | [...]
-| *camel.component.aws2-ec2.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.component.aws2-ec2.pojoRequest* | If we want to use a POJO request as body or not | false | false | MEDIUM
-| *camel.component.aws2-ec2.proxyHost* | To define a proxy host when instantiating the EC2 client | null | false | MEDIUM
-| *camel.component.aws2-ec2.proxyPort* | To define a proxy port when instantiating the EC2 client | null | false | MEDIUM
-| *camel.component.aws2-ec2.proxyProtocol* | To define a proxy protocol when instantiating the EC2 client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *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() | null | false | MEDIUM
-| *camel.component.aws2-ec2.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-| *camel.component.aws2-ec2.trustAllCertificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.component.aws2-ec2.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.component.aws2-ec2.useDefaultCredentials Provider* | Set whether the EC2 client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | false | false | MEDIUM
-| *camel.component.aws2-ec2.autowiredEnabled* | 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 | false | MEDIUM
-|===
-
-
-
-The camel-aws2-ec2 sink connector has no converters out of the box.
-
-
-
-
-
-The camel-aws2-ec2 sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-aws2-ec2 sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-aws2-ecs-kafka-connector/src/main/docs/camel-aws2-ecs-kafka-sink-connector.adoc b/connectors/camel-aws2-ecs-kafka-connector/src/main/docs/camel-aws2-ecs-kafka-sink-connector.adoc
deleted file mode 100644
index 9a73f8b..0000000
--- a/connectors/camel-aws2-ecs-kafka-connector/src/main/docs/camel-aws2-ecs-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,82 +0,0 @@
-// kafka-connector options: START
-[[camel-aws2-ecs-kafka-connector-sink]]
-= camel-aws2-ecs-kafka-connector sink configuration
-
-Connector Description: Manage AWS ECS cluster instances using AWS SDK version 2.x.
-
-When using camel-aws2-ecs-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-aws2-ecs-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.aws2ecs.CamelAws2ecsSinkConnector
-----
-
-
-The camel-aws2-ecs sink connector supports 31 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.label* | Logical name | null | true | HIGH
-| *camel.sink.endpoint.ecsClient* | To use a existing configured AWS ECS as client | null | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.operation* | The operation to perform One of: [listClusters] [describeCluster] [createCluster] [deleteCluster] | null | true | HIGH
-| *camel.sink.endpoint.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.sink.endpoint.pojoRequest* | If we want to use a POJO request as body or not | false | false | MEDIUM
-| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the ECS client | null | false | MEDIUM
-| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the ECS client | null | false | MEDIUM
-| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the ECS client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *camel.sink.endpoint.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() | null | false | MEDIUM
-| *camel.sink.endpoint.trustAllCertificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.sink.endpoint.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.sink.endpoint.useDefaultCredentialsProvider* | Set whether the ECS client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | false | false | MEDIUM
-| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-| *camel.component.aws2-ecs.configuration* | Component configuration | null | false | MEDIUM
-| *camel.component.aws2-ecs.ecsClient* | To use a existing configured AWS ECS as client | null | false | MEDIUM
-| *camel.component.aws2-ecs.lazyStartProducer* | 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.aws2-ecs.operation* | The operation to perform One of: [listClusters] [describeCluster] [createCluster] [deleteCluster] | null | true | HIGH
-| *camel.component.aws2-ecs.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.component.aws2-ecs.pojoRequest* | If we want to use a POJO request as body or not | false | false | MEDIUM
-| *camel.component.aws2-ecs.proxyHost* | To define a proxy host when instantiating the ECS client | null | false | MEDIUM
-| *camel.component.aws2-ecs.proxyPort* | To define a proxy port when instantiating the ECS client | null | false | MEDIUM
-| *camel.component.aws2-ecs.proxyProtocol* | To define a proxy protocol when instantiating the ECS client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *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() | null | false | MEDIUM
-| *camel.component.aws2-ecs.trustAllCertificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.component.aws2-ecs.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.component.aws2-ecs.useDefaultCredentials Provider* | Set whether the ECS client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | false | false | MEDIUM
-| *camel.component.aws2-ecs.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.aws2-ecs.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.component.aws2-ecs.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-|===
-
-
-
-The camel-aws2-ecs sink connector has no converters out of the box.
-
-
-
-
-
-The camel-aws2-ecs sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-aws2-ecs sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-aws2-eks-kafka-connector/src/main/docs/camel-aws2-eks-kafka-sink-connector.adoc b/connectors/camel-aws2-eks-kafka-connector/src/main/docs/camel-aws2-eks-kafka-sink-connector.adoc
deleted file mode 100644
index cb5a075..0000000
--- a/connectors/camel-aws2-eks-kafka-connector/src/main/docs/camel-aws2-eks-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,82 +0,0 @@
-// kafka-connector options: START
-[[camel-aws2-eks-kafka-connector-sink]]
-= camel-aws2-eks-kafka-connector sink configuration
-
-Connector Description: Manage AWS EKS cluster instances using AWS SDK version 2.x.
-
-When using camel-aws2-eks-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-aws2-eks-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.aws2eks.CamelAws2eksSinkConnector
-----
-
-
-The camel-aws2-eks sink connector supports 31 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.label* | Logical name | null | true | HIGH
-| *camel.sink.endpoint.eksClient* | To use a existing configured AWS EKS as client | null | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.operation* | The operation to perform One of: [listClusters] [describeCluster] [createCluster] [deleteCluster] | null | true | HIGH
-| *camel.sink.endpoint.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.sink.endpoint.pojoRequest* | If we want to use a POJO request as body or not | false | false | MEDIUM
-| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the EKS client | null | false | MEDIUM
-| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the EKS client | null | false | MEDIUM
-| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the EKS client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *camel.sink.endpoint.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() | null | false | MEDIUM
-| *camel.sink.endpoint.trustAllCertificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.sink.endpoint.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.sink.endpoint.useDefaultCredentialsProvider* | Set whether the EKS client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | false | false | MEDIUM
-| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-| *camel.component.aws2-eks.configuration* | Component configuration | null | false | MEDIUM
-| *camel.component.aws2-eks.eksClient* | To use a existing configured AWS EKS as client | null | false | MEDIUM
-| *camel.component.aws2-eks.lazyStartProducer* | 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.aws2-eks.operation* | The operation to perform One of: [listClusters] [describeCluster] [createCluster] [deleteCluster] | null | true | HIGH
-| *camel.component.aws2-eks.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.component.aws2-eks.pojoRequest* | If we want to use a POJO request as body or not | false | false | MEDIUM
-| *camel.component.aws2-eks.proxyHost* | To define a proxy host when instantiating the EKS client | null | false | MEDIUM
-| *camel.component.aws2-eks.proxyPort* | To define a proxy port when instantiating the EKS client | null | false | MEDIUM
-| *camel.component.aws2-eks.proxyProtocol* | To define a proxy protocol when instantiating the EKS client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *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() | null | false | MEDIUM
-| *camel.component.aws2-eks.trustAllCertificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.component.aws2-eks.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.component.aws2-eks.useDefaultCredentials Provider* | Set whether the EKS client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | false | false | MEDIUM
-| *camel.component.aws2-eks.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.aws2-eks.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.component.aws2-eks.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-|===
-
-
-
-The camel-aws2-eks sink connector has no converters out of the box.
-
-
-
-
-
-The camel-aws2-eks sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-aws2-eks sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-aws2-eventbridge-kafka-connector/src/main/docs/camel-aws2-eventbridge-kafka-sink-connector.adoc b/connectors/camel-aws2-eventbridge-kafka-connector/src/main/docs/camel-aws2-eventbridge-kafka-sink-connector.adoc
deleted file mode 100644
index d26cf41..0000000
--- a/connectors/camel-aws2-eventbridge-kafka-connector/src/main/docs/camel-aws2-eventbridge-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,84 +0,0 @@
-// kafka-connector options: START
-[[camel-aws2-eventbridge-kafka-connector-sink]]
-= camel-aws2-eventbridge-kafka-connector sink configuration
-
-Connector Description: Manage AWS Eventbridge cluster instances using AWS SDK version 2.x.
-
-When using camel-aws2-eventbridge-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-aws2-eventbridge-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.aws2eventbridge.CamelAws2eventbridgeSinkConnector
-----
-
-
-The camel-aws2-eventbridge sink connector supports 33 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.eventbusNameOrArn* | Event bus name or ARN | null | true | HIGH
-| *camel.sink.endpoint.eventbridgeClient* | To use a existing configured AWS Eventbridge as client | null | false | MEDIUM
-| *camel.sink.endpoint.eventPatternFile* | EventPattern File | null | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.operation* | The operation to perform One of: [putRule] [putTargets] [removeTargets] [deleteRule] [enableRule] [disableRule] [describeRule] [listRules] [listTargetsByRule] [listRuleNamesByTarget] | "putRule" | true | HIGH
-| *camel.sink.endpoint.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.sink.endpoint.pojoRequest* | If we want to use a POJO request as body or not | false | false | MEDIUM
-| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the Eventbridge client | null | false | MEDIUM
-| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the Eventbridge client | null | false | MEDIUM
-| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the Eventbridge client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *camel.sink.endpoint.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() | null | false | MEDIUM
-| *camel.sink.endpoint.trustAllCertificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.sink.endpoint.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.sink.endpoint.useDefaultCredentialsProvider* | Set whether the Eventbridge client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | false | false | MEDIUM
-| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-| *camel.component.aws2-eventbridge.configuration* | Component configuration | null | false | MEDIUM
-| *camel.component.aws2-eventbridge.eventbridgeClient* | To use a existing configured AWS Eventbridge as client | null | false | MEDIUM
-| *camel.component.aws2-eventbridge.eventPatternFile* | EventPattern File | null | false | MEDIUM
-| *camel.component.aws2-eventbridge.lazyStartProducer* | 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-eventbridge.operation* | The operation to perform One of: [putRule] [putTargets] [removeTargets] [deleteRule] [enableRule] [disableRule] [describeRule] [listRules] [listTargetsByRule] [listRuleNamesByTarget] | "putRule" | true | HIGH
-| *camel.component.aws2-eventbridge.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.component.aws2-eventbridge.pojoRequest* | If we want to use a POJO request as body or not | false | false | MEDIUM
-| *camel.component.aws2-eventbridge.proxyHost* | To define a proxy host when instantiating the Eventbridge client | null | false | MEDIUM
-| *camel.component.aws2-eventbridge.proxyPort* | To define a proxy port when instantiating the Eventbridge client | null | false | MEDIUM
-| *camel.component.aws2-eventbridge.proxyProtocol* | To define a proxy protocol when instantiating the Eventbridge client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *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() | null | false | MEDIUM
-| *camel.component.aws2-eventbridge.trustAll Certificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.component.aws2-eventbridge.uriEndpoint Override* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.component.aws2-eventbridge.useDefault CredentialsProvider* | Set whether the Eventbridge client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | false | false | MEDIUM
-| *camel.component.aws2-eventbridge.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.aws2-eventbridge.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.component.aws2-eventbridge.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-|===
-
-
-
-The camel-aws2-eventbridge sink connector has no converters out of the box.
-
-
-
-
-
-The camel-aws2-eventbridge sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-aws2-eventbridge sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-aws2-iam-kafka-connector/src/main/docs/camel-aws2-iam-kafka-sink-connector.adoc b/connectors/camel-aws2-iam-kafka-connector/src/main/docs/camel-aws2-iam-kafka-sink-connector.adoc
deleted file mode 100644
index 4c84a9c..0000000
--- a/connectors/camel-aws2-iam-kafka-connector/src/main/docs/camel-aws2-iam-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,82 +0,0 @@
-// kafka-connector options: START
-[[camel-aws2-iam-kafka-connector-sink]]
-= camel-aws2-iam-kafka-connector sink configuration
-
-Connector Description: Manage AWS IAM instances using AWS SDK version 2.x.
-
-When using camel-aws2-iam-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-aws2-iam-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.aws2iam.CamelAws2iamSinkConnector
-----
-
-
-The camel-aws2-iam sink connector supports 31 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.label* | Logical name | null | true | HIGH
-| *camel.sink.endpoint.iamClient* | To use a existing configured AWS IAM as client | null | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.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. One of: [listAccessKeys] [createUser] [deleteUser] [getUser] [listUsers] [createAccessKey] [deleteAccessKey] [updateAccessKey] [createGroup] [deleteGroup] [listGroups] [addUserToGroup] [removeUserFromGroup] | null | false | MEDIUM
-| *camel.sink.endpoint.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.sink.endpoint.pojoRequest* | If we want to use a POJO request as body or not | false | false | MEDIUM
-| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the IAM client | null | false | MEDIUM
-| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the IAM client | null | false | MEDIUM
-| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the IAM client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *camel.sink.endpoint.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" | false | MEDIUM
-| *camel.sink.endpoint.trustAllCertificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.sink.endpoint.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.sink.endpoint.useDefaultCredentialsProvider* | Set whether the IAM client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | false | false | MEDIUM
-| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-| *camel.component.aws2-iam.configuration* | Component configuration | null | false | MEDIUM
-| *camel.component.aws2-iam.iamClient* | To use a existing configured AWS IAM as client | null | false | MEDIUM
-| *camel.component.aws2-iam.lazyStartProducer* | 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.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. One of: [listAccessKeys] [createUser] [deleteUser] [getUser] [listUsers] [createAccessKey] [deleteAccessKey] [updateAccessKey] [createGroup] [deleteGroup] [listGroups] [addUserToGroup] [removeUserFromGroup] | null | false | MEDIUM
-| *camel.component.aws2-iam.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.component.aws2-iam.pojoRequest* | If we want to use a POJO request as body or not | false | false | MEDIUM
-| *camel.component.aws2-iam.proxyHost* | To define a proxy host when instantiating the IAM client | null | false | MEDIUM
-| *camel.component.aws2-iam.proxyPort* | To define a proxy port when instantiating the IAM client | null | false | MEDIUM
-| *camel.component.aws2-iam.proxyProtocol* | To define a proxy protocol when instantiating the IAM client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *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" | false | MEDIUM
-| *camel.component.aws2-iam.trustAllCertificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.component.aws2-iam.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.component.aws2-iam.useDefaultCredentials Provider* | Set whether the IAM client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | false | false | MEDIUM
-| *camel.component.aws2-iam.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.aws2-iam.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.component.aws2-iam.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-|===
-
-
-
-The camel-aws2-iam sink connector has no converters out of the box.
-
-
-
-
-
-The camel-aws2-iam sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-aws2-iam sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-aws2-kinesis-firehose-kafka-connector/src/main/docs/camel-aws2-kinesis-firehose-kafka-sink-connector.adoc b/connectors/camel-aws2-kinesis-firehose-kafka-connector/src/main/docs/camel-aws2-kinesis-firehose-kafka-sink-connector.adoc
deleted file mode 100644
index 0f58034..0000000
--- a/connectors/camel-aws2-kinesis-firehose-kafka-connector/src/main/docs/camel-aws2-kinesis-firehose-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,82 +0,0 @@
-// kafka-connector options: START
-[[camel-aws2-kinesis-firehose-kafka-connector-sink]]
-= camel-aws2-kinesis-firehose-kafka-connector sink configuration
-
-Connector Description: Produce data to AWS Kinesis Firehose streams using AWS SDK version 2.x.
-
-When using camel-aws2-kinesis-firehose-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-aws2-kinesis-firehose-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.aws2kinesisfirehose.CamelAws2kinesisfirehoseSinkConnector
-----
-
-
-The camel-aws2-kinesis-firehose sink connector supports 31 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.streamName* | Name of the stream | null | true | HIGH
-| *camel.sink.endpoint.amazonKinesisFirehoseClient* | Amazon Kinesis Firehose client to use for all requests for this endpoint | null | false | MEDIUM
-| *camel.sink.endpoint.cborEnabled* | This option will set the CBOR_ENABLED property during the execution | true | false | MEDIUM
-| *camel.sink.endpoint.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.operation* | The operation to do in case the user don't want to send only a record One of: [sendBatchRecord] [createDeliveryStream] [deleteDeliveryStream] [describeDeliveryStream] [updateDestination] | null | false | MEDIUM
-| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the Kinesis Firehose client | null | false | MEDIUM
-| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the Kinesis Firehose client | null | false | MEDIUM
-| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the Kinesis Firehose client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *camel.sink.endpoint.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() | null | false | MEDIUM
-| *camel.sink.endpoint.trustAllCertificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.sink.endpoint.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.sink.endpoint.useDefaultCredentialsProvider* | Set whether the Kinesis Firehose client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | false | false | MEDIUM
-| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-| *camel.component.aws2-kinesis-firehose.amazon KinesisFirehoseClient* | Amazon Kinesis Firehose client to use for all requests for this endpoint | null | false | MEDIUM
-| *camel.component.aws2-kinesis-firehose.cborEnabled* | This option will set the CBOR_ENABLED property during the execution | true | false | MEDIUM
-| * camel.component.aws2-kinesis-firehose.configuration* | Component configuration | null | false | MEDIUM
-| *camel.component.aws2-kinesis-firehose.override Endpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.component.aws2-kinesis-firehose.lazyStart 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.aws2-kinesis-firehose.operation* | The operation to do in case the user don't want to send only a record One of: [sendBatchRecord] [createDeliveryStream] [deleteDeliveryStream] [describeDeliveryStream] [updateDestination] | null | false | MEDIUM
-| *camel.component.aws2-kinesis-firehose.proxyHost* | To define a proxy host when instantiating the Kinesis Firehose client | null | false | MEDIUM
-| *camel.component.aws2-kinesis-firehose.proxyPort* | To define a proxy port when instantiating the Kinesis Firehose client | null | false | MEDIUM
-| *camel.component.aws2-kinesis-firehose.proxy Protocol* | To define a proxy protocol when instantiating the Kinesis Firehose client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *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() | null | false | MEDIUM
-| *camel.component.aws2-kinesis-firehose.trustAll Certificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.component.aws2-kinesis-firehose.uriEndpoint Override* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.component.aws2-kinesis-firehose.useDefault CredentialsProvider* | Set whether the Kinesis Firehose client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | false | false | MEDIUM
-| *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 | false | MEDIUM
-| *camel.component.aws2-kinesis-firehose.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.component.aws2-kinesis-firehose.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-|===
-
-
-
-The camel-aws2-kinesis-firehose sink connector has no converters out of the box.
-
-
-
-
-
-The camel-aws2-kinesis-firehose sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-aws2-kinesis-firehose sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-aws2-kinesis-kafka-connector/src/main/docs/camel-aws2-kinesis-kafka-sink-connector.adoc b/connectors/camel-aws2-kinesis-kafka-connector/src/main/docs/camel-aws2-kinesis-kafka-sink-connector.adoc
deleted file mode 100644
index 59b7323..0000000
--- a/connectors/camel-aws2-kinesis-kafka-connector/src/main/docs/camel-aws2-kinesis-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,87 +0,0 @@
-// kafka-connector options: START
-[[camel-aws2-kinesis-kafka-connector-sink]]
-= camel-aws2-kinesis-kafka-connector sink configuration
-
-Connector Description: Consume and produce records from and to AWS Kinesis Streams using AWS SDK version 2.x.
-
-When using camel-aws2-kinesis-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-aws2-kinesis-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.aws2kinesis.CamelAws2kinesisSinkConnector
-----
-
-
-The camel-aws2-kinesis sink connector supports 29 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.streamName* | Name of the stream | null | true | HIGH
-| *camel.sink.endpoint.amazonKinesisClient* | Amazon Kinesis client to use for all requests for this endpoint | null | false | MEDIUM
-| *camel.sink.endpoint.cborEnabled* | This option will set the CBOR_ENABLED property during the execution | true | false | MEDIUM
-| *camel.sink.endpoint.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the Kinesis client | null | false | MEDIUM
-| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the Kinesis client | null | false | MEDIUM
-| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the Kinesis client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *camel.sink.endpoint.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() | null | false | MEDIUM
-| *camel.sink.endpoint.trustAllCertificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.sink.endpoint.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.sink.endpoint.useDefaultCredentialsProvider* | Set whether the Kinesis client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | false | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-| *camel.component.aws2-kinesis.amazonKinesisClient* | Amazon Kinesis client to use for all requests for this endpoint | null | false | MEDIUM
-| *camel.component.aws2-kinesis.cborEnabled* | This option will set the CBOR_ENABLED property during the execution | true | false | MEDIUM
-| *camel.component.aws2-kinesis.configuration* | Component configuration | null | false | MEDIUM
-| *camel.component.aws2-kinesis.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.component.aws2-kinesis.proxyHost* | To define a proxy host when instantiating the Kinesis client | null | false | MEDIUM
-| *camel.component.aws2-kinesis.proxyPort* | To define a proxy port when instantiating the Kinesis client | null | false | MEDIUM
-| *camel.component.aws2-kinesis.proxyProtocol* | To define a proxy protocol when instantiating the Kinesis client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *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() | null | false | MEDIUM
-| *camel.component.aws2-kinesis.trustAllCertificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.component.aws2-kinesis.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.component.aws2-kinesis.useDefaultCredentials Provider* | Set whether the Kinesis client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | false | false | MEDIUM
-| *camel.component.aws2-kinesis.lazyStartProducer* | 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.aws2-kinesis.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.aws2-kinesis.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.component.aws2-kinesis.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-|===
-
-
-
-The camel-aws2-kinesis sink connector has no converters out of the box.
-
-
-
-
-
-The camel-aws2-kinesis sink connector supports 1 transforms out of the box, which are listed below.
-
-
-
-[source,java]
-----
-
-org.apache.camel.kafkaconnector.aws2kinesis.transformers.KinesisRecordDataTransforms
-
-----
-
-
-
-The camel-aws2-kinesis sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-aws2-kinesis-kafka-connector/src/main/docs/camel-aws2-kinesis-kafka-source-connector.adoc b/connectors/camel-aws2-kinesis-kafka-connector/src/main/docs/camel-aws2-kinesis-kafka-source-connector.adoc
deleted file mode 100644
index 49e8601..0000000
--- a/connectors/camel-aws2-kinesis-kafka-connector/src/main/docs/camel-aws2-kinesis-kafka-source-connector.adoc
+++ /dev/null
@@ -1,115 +0,0 @@
-// kafka-connector options: START
-[[camel-aws2-kinesis-kafka-connector-source]]
-= camel-aws2-kinesis-kafka-connector source configuration
-
-Connector description: Consume and produce records from and to AWS Kinesis Streams using AWS SDK version 2.x.
-
-When using camel-aws2-kinesis-kafka-connector as source make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-aws2-kinesis-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Source connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.aws2kinesis.CamelAws2kinesisSourceConnector
-----
-
-
-The camel-aws2-kinesis source connector supports 57 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.source.path.streamName* | Name of the stream | null | true | HIGH
-| *camel.source.endpoint.amazonKinesisClient* | Amazon Kinesis client to use for all requests for this endpoint | null | false | MEDIUM
-| *camel.source.endpoint.cborEnabled* | This option will set the CBOR_ENABLED property during the execution | true | false | MEDIUM
-| *camel.source.endpoint.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.source.endpoint.proxyHost* | To define a proxy host when instantiating the Kinesis client | null | false | MEDIUM
-| *camel.source.endpoint.proxyPort* | To define a proxy port when instantiating the Kinesis client | null | false | MEDIUM
-| *camel.source.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the Kinesis client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *camel.source.endpoint.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() | null | false | MEDIUM
-| *camel.source.endpoint.trustAllCertificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.source.endpoint.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.source.endpoint.useDefaultCredentials Provider* | Set whether the Kinesis client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | false | false | MEDIUM
-| *camel.source.endpoint.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.source.endpoint.iteratorType* | Defines where in the Kinesis stream to start getting records One of: [AT_SEQUENCE_NUMBER] [AFTER_SEQUENCE_NUMBER] [TRIM_HORIZON] [LATEST] [AT_TIMESTAMP] [null] | "TRIM_HORIZON" | false | MEDIUM
-| *camel.source.endpoint.maxResultsPerRequest* | Maximum number of records that will be fetched in each poll | 1 | false | MEDIUM
-| *camel.source.endpoint.sendEmptyMessageWhenIdle* | If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead. | false | false | MEDIUM
-| *camel.source.endpoint.sequenceNumber* | The sequence number to start polling from. Required if iteratorType is set to AFTER_SEQUENCE_NUMBER or AT_SEQUENCE_NUMBER | null | false | MEDIUM
-| *camel.source.endpoint.shardClosed* | 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 One of: [ignore] [fail] [silent] | "ignore" | false | MEDIUM
-| *camel.source.endpoint.shardId* | Defines which shardId in the Kinesis stream to get records from | null | false | MEDIUM
-| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | false | MEDIUM
-| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | false | MEDIUM
-| *camel.source.endpoint.pollStrategy* | A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel. | null | false | MEDIUM
-| *camel.source.endpoint.backoffErrorThreshold* | The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in. | null | false | MEDIUM
-| *camel.source.endpoint.backoffIdleThreshold* | The number of subsequent idle polls that should happen before the backoffMultipler should kick-in. | null | false | MEDIUM
-| *camel.source.endpoint.backoffMultiplier* | To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured. | null | false | MEDIUM
-| *camel.source.endpoint.delay* | Milliseconds before the next poll. | 500L | false | MEDIUM
-| *camel.source.endpoint.greedy* | If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages. | false | false | MEDIUM
-| *camel.source.endpoint.initialDelay* | Milliseconds before the first poll starts. | 1000L | false | MEDIUM
-| *camel.source.endpoint.repeatCount* | Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever. | 0L | false | MEDIUM
-| *camel.source.endpoint.runLoggingLevel* | The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that. One of: [TRACE] [DEBUG] [INFO] [WARN] [ERROR] [OFF] | "TRACE" | false | MEDIUM
-| *camel.source.endpoint.scheduledExecutorService* | Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool. | null | false | MEDIUM
-| *camel.source.endpoint.scheduler* | To use a cron scheduler from either camel-spring or camel-quartz component. Use value spring or quartz for built in scheduler | "none" | false | MEDIUM
-| *camel.source.endpoint.schedulerProperties* | To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler. | null | false | MEDIUM
-| *camel.source.endpoint.startScheduler* | Whether the scheduler should be auto started. | true | false | MEDIUM
-| *camel.source.endpoint.timeUnit* | Time unit for initialDelay and delay options. One of: [NANOSECONDS] [MICROSECONDS] [MILLISECONDS] [SECONDS] [MINUTES] [HOURS] [DAYS] | "MILLISECONDS" | false | MEDIUM
-| *camel.source.endpoint.useFixedDelay* | Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details. | true | false | MEDIUM
-| *camel.source.endpoint.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.source.endpoint.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-| *camel.component.aws2-kinesis.amazonKinesisClient* | Amazon Kinesis client to use for all requests for this endpoint | null | false | MEDIUM
-| *camel.component.aws2-kinesis.cborEnabled* | This option will set the CBOR_ENABLED property during the execution | true | false | MEDIUM
-| *camel.component.aws2-kinesis.configuration* | Component configuration | null | false | MEDIUM
-| *camel.component.aws2-kinesis.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.component.aws2-kinesis.proxyHost* | To define a proxy host when instantiating the Kinesis client | null | false | MEDIUM
-| *camel.component.aws2-kinesis.proxyPort* | To define a proxy port when instantiating the Kinesis client | null | false | MEDIUM
-| *camel.component.aws2-kinesis.proxyProtocol* | To define a proxy protocol when instantiating the Kinesis client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *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() | null | false | MEDIUM
-| *camel.component.aws2-kinesis.trustAllCertificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.component.aws2-kinesis.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.component.aws2-kinesis.useDefaultCredentials Provider* | Set whether the Kinesis client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | false | false | MEDIUM
-| *camel.component.aws2-kinesis.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.component.aws2-kinesis.iteratorType* | Defines where in the Kinesis stream to start getting records One of: [AT_SEQUENCE_NUMBER] [AFTER_SEQUENCE_NUMBER] [TRIM_HORIZON] [LATEST] [AT_TIMESTAMP] [null] | "TRIM_HORIZON" | false | MEDIUM
-| *camel.component.aws2-kinesis.maxResultsPerRequest* | Maximum number of records that will be fetched in each poll | 1 | false | MEDIUM
-| *camel.component.aws2-kinesis.sequenceNumber* | The sequence number to start polling from. Required if iteratorType is set to AFTER_SEQUENCE_NUMBER or AT_SEQUENCE_NUMBER | null | false | MEDIUM
-| *camel.component.aws2-kinesis.shardClosed* | 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 One of: [ignore] [fail] [silent] | "ignore" | false | MEDIUM
-| *camel.component.aws2-kinesis.shardId* | Defines which shardId in the Kinesis stream to get records from | null | false | MEDIUM
-| *camel.component.aws2-kinesis.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.aws2-kinesis.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.component.aws2-kinesis.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-|===
-
-
-
-The camel-aws2-kinesis source connector has no converters out of the box.
-
-
-
-
-
-The camel-aws2-kinesis source connector supports 1 transforms out of the box, which are listed below.
-
-
-
-[source,java]
-----
-
-org.apache.camel.kafkaconnector.aws2kinesis.transformers.KinesisRecordDataTransforms
-
-----
-
-
-
-The camel-aws2-kinesis source connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-aws2-kms-kafka-connector/src/main/docs/camel-aws2-kms-kafka-sink-connector.adoc b/connectors/camel-aws2-kms-kafka-connector/src/main/docs/camel-aws2-kms-kafka-sink-connector.adoc
deleted file mode 100644
index 23e0ecf..0000000
--- a/connectors/camel-aws2-kms-kafka-connector/src/main/docs/camel-aws2-kms-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,82 +0,0 @@
-// kafka-connector options: START
-[[camel-aws2-kms-kafka-connector-sink]]
-= camel-aws2-kms-kafka-connector sink configuration
-
-Connector Description: Manage keys stored in AWS KMS instances using AWS SDK version 2.x.
-
-When using camel-aws2-kms-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-aws2-kms-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.aws2kms.CamelAws2kmsSinkConnector
-----
-
-
-The camel-aws2-kms sink connector supports 31 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.label* | Logical name | null | true | HIGH
-| *camel.sink.endpoint.kmsClient* | To use a existing configured AWS KMS as client | null | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.operation* | The operation to perform One of: [listKeys] [createKey] [disableKey] [scheduleKeyDeletion] [describeKey] [enableKey] | null | true | HIGH
-| *camel.sink.endpoint.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.sink.endpoint.pojoRequest* | If we want to use a POJO request as body or not | false | false | MEDIUM
-| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the KMS client | null | false | MEDIUM
-| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the KMS client | null | false | MEDIUM
-| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the KMS client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *camel.sink.endpoint.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() | null | false | MEDIUM
-| *camel.sink.endpoint.trustAllCertificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.sink.endpoint.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.sink.endpoint.useDefaultCredentialsProvider* | Set whether the KMS client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | false | false | MEDIUM
-| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-| *camel.component.aws2-kms.configuration* | Component configuration | null | false | MEDIUM
-| *camel.component.aws2-kms.kmsClient* | To use a existing configured AWS KMS as client | null | false | MEDIUM
-| *camel.component.aws2-kms.lazyStartProducer* | 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.aws2-kms.operation* | The operation to perform One of: [listKeys] [createKey] [disableKey] [scheduleKeyDeletion] [describeKey] [enableKey] | null | true | HIGH
-| *camel.component.aws2-kms.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.component.aws2-kms.pojoRequest* | If we want to use a POJO request as body or not | false | false | MEDIUM
-| *camel.component.aws2-kms.proxyHost* | To define a proxy host when instantiating the KMS client | null | false | MEDIUM
-| *camel.component.aws2-kms.proxyPort* | To define a proxy port when instantiating the KMS client | null | false | MEDIUM
-| *camel.component.aws2-kms.proxyProtocol* | To define a proxy protocol when instantiating the KMS client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *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() | null | false | MEDIUM
-| *camel.component.aws2-kms.trustAllCertificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.component.aws2-kms.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.component.aws2-kms.useDefaultCredentials Provider* | Set whether the KMS client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | false | false | MEDIUM
-| *camel.component.aws2-kms.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.aws2-kms.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.component.aws2-kms.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-|===
-
-
-
-The camel-aws2-kms sink connector has no converters out of the box.
-
-
-
-
-
-The camel-aws2-kms sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-aws2-kms sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-aws2-lambda-kafka-connector/src/main/docs/camel-aws2-lambda-kafka-sink-connector.adoc b/connectors/camel-aws2-lambda-kafka-connector/src/main/docs/camel-aws2-lambda-kafka-sink-connector.adoc
deleted file mode 100644
index 1c39c89..0000000
--- a/connectors/camel-aws2-lambda-kafka-connector/src/main/docs/camel-aws2-lambda-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,82 +0,0 @@
-// kafka-connector options: START
-[[camel-aws2-lambda-kafka-connector-sink]]
-= camel-aws2-lambda-kafka-connector sink configuration
-
-Connector Description: Manage and invoke AWS Lambda functions using AWS SDK version 2.x.
-
-When using camel-aws2-lambda-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-aws2-lambda-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.aws2lambda.CamelAws2lambdaSinkConnector
-----
-
-
-The camel-aws2-lambda sink connector supports 31 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.function* | Name of the Lambda function. | null | true | HIGH
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.operation* | The operation to perform. It can be listFunctions, getFunction, createFunction, deleteFunction or invokeFunction One of: [listFunctions] [getFunction] [createAlias] [deleteAlias] [getAlias] [listAliases] [createFunction] [deleteFunction] [invokeFunction] [updateFunction] [createEventSourceMapping] [deleteEventSourceMapping] [listEventSourceMapping] [listTags] [tagResource] [untagResource] [publishVersion] [listVersions] | "invokeFunction" | false | MEDIUM
-| *camel.sink.endpoint.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.sink.endpoint.pojoRequest* | If we want to use a POJO request as body or not | false | false | MEDIUM
-| *camel.sink.endpoint.region* | The region in which Lambda 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() | null | false | MEDIUM
-| *camel.sink.endpoint.trustAllCertificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.sink.endpoint.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.sink.endpoint.useDefaultCredentialsProvider* | Set whether the Lambda client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | false | false | MEDIUM
-| *camel.sink.endpoint.awsLambdaClient* | To use a existing configured AwsLambdaClient as client | null | false | MEDIUM
-| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the Lambda client | null | false | MEDIUM
-| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the Lambda client | null | false | MEDIUM
-| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the Lambda client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-| *camel.component.aws2-lambda.configuration* | Component configuration | null | false | MEDIUM
-| *camel.component.aws2-lambda.lazyStartProducer* | 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.aws2-lambda.operation* | The operation to perform. It can be listFunctions, getFunction, createFunction, deleteFunction or invokeFunction One of: [listFunctions] [getFunction] [createAlias] [deleteAlias] [getAlias] [listAliases] [createFunction] [deleteFunction] [invokeFunction] [updateFunction] [createEventSourceMapping] [deleteEventSourceMapping] [listEventSourceMapping] [listTags] [tagResource] [untagResource] [publishVersion] [listVersions] | "invokeFunction" | fal [...]
-| *camel.component.aws2-lambda.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.component.aws2-lambda.pojoRequest* | If we want to use a POJO request as body or not | false | false | MEDIUM
-| *camel.component.aws2-lambda.region* | The region in which Lambda 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() | null | false | MEDIUM
-| *camel.component.aws2-lambda.trustAllCertificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.component.aws2-lambda.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.component.aws2-lambda.useDefaultCredentials Provider* | Set whether the Lambda client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | false | false | MEDIUM
-| *camel.component.aws2-lambda.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.aws2-lambda.awsLambdaClient* | To use a existing configured AwsLambdaClient as client | null | false | MEDIUM
-| *camel.component.aws2-lambda.proxyHost* | To define a proxy host when instantiating the Lambda client | null | false | MEDIUM
-| *camel.component.aws2-lambda.proxyPort* | To define a proxy port when instantiating the Lambda client | null | false | MEDIUM
-| *camel.component.aws2-lambda.proxyProtocol* | To define a proxy protocol when instantiating the Lambda client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *camel.component.aws2-lambda.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.component.aws2-lambda.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-|===
-
-
-
-The camel-aws2-lambda sink connector has no converters out of the box.
-
-
-
-
-
-The camel-aws2-lambda sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-aws2-lambda sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-aws2-mq-kafka-connector/src/main/docs/camel-aws2-mq-kafka-sink-connector.adoc b/connectors/camel-aws2-mq-kafka-connector/src/main/docs/camel-aws2-mq-kafka-sink-connector.adoc
deleted file mode 100644
index cf9667d..0000000
--- a/connectors/camel-aws2-mq-kafka-connector/src/main/docs/camel-aws2-mq-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,82 +0,0 @@
-// kafka-connector options: START
-[[camel-aws2-mq-kafka-connector-sink]]
-= camel-aws2-mq-kafka-connector sink configuration
-
-Connector Description: Manage AWS MQ instances using AWS SDK version 2.x.
-
-When using camel-aws2-mq-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-aws2-mq-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.aws2mq.CamelAws2mqSinkConnector
-----
-
-
-The camel-aws2-mq sink connector supports 31 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.label* | Logical name | null | true | HIGH
-| *camel.sink.endpoint.amazonMqClient* | To use a existing configured AmazonMQClient as client | null | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.operation* | The operation to perform. It can be listBrokers,createBroker,deleteBroker One of: [listBrokers] [createBroker] [deleteBroker] [rebootBroker] [updateBroker] [describeBroker] | null | true | HIGH
-| *camel.sink.endpoint.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.sink.endpoint.pojoRequest* | If we want to use a POJO request as body or not | false | false | MEDIUM
-| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the MQ client | null | false | MEDIUM
-| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the MQ client | null | false | MEDIUM
-| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the MQ client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *camel.sink.endpoint.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() | null | false | MEDIUM
-| *camel.sink.endpoint.trustAllCertificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.sink.endpoint.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.sink.endpoint.useDefaultCredentialsProvider* | Set whether the MQ client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | false | false | MEDIUM
-| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-| *camel.component.aws2-mq.amazonMqClient* | To use a existing configured AmazonMQClient as client | null | false | MEDIUM
-| *camel.component.aws2-mq.configuration* | Component configuration | null | false | MEDIUM
-| *camel.component.aws2-mq.lazyStartProducer* | 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.aws2-mq.operation* | The operation to perform. It can be listBrokers,createBroker,deleteBroker One of: [listBrokers] [createBroker] [deleteBroker] [rebootBroker] [updateBroker] [describeBroker] | null | true | HIGH
-| *camel.component.aws2-mq.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.component.aws2-mq.pojoRequest* | If we want to use a POJO request as body or not | false | false | MEDIUM
-| *camel.component.aws2-mq.proxyHost* | To define a proxy host when instantiating the MQ client | null | false | MEDIUM
-| *camel.component.aws2-mq.proxyPort* | To define a proxy port when instantiating the MQ client | null | false | MEDIUM
-| *camel.component.aws2-mq.proxyProtocol* | To define a proxy protocol when instantiating the MQ client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *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() | null | false | MEDIUM
-| *camel.component.aws2-mq.trustAllCertificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.component.aws2-mq.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.component.aws2-mq.useDefaultCredentials Provider* | Set whether the MQ client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | false | false | MEDIUM
-| *camel.component.aws2-mq.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.aws2-mq.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.component.aws2-mq.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-|===
-
-
-
-The camel-aws2-mq sink connector has no converters out of the box.
-
-
-
-
-
-The camel-aws2-mq sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-aws2-mq sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-aws2-msk-kafka-connector/src/main/docs/camel-aws2-msk-kafka-sink-connector.adoc b/connectors/camel-aws2-msk-kafka-connector/src/main/docs/camel-aws2-msk-kafka-sink-connector.adoc
deleted file mode 100644
index 91dd2f2..0000000
--- a/connectors/camel-aws2-msk-kafka-connector/src/main/docs/camel-aws2-msk-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,82 +0,0 @@
-// kafka-connector options: START
-[[camel-aws2-msk-kafka-connector-sink]]
-= camel-aws2-msk-kafka-connector sink configuration
-
-Connector Description: Manage AWS MSK instances using AWS SDK version 2.x.
-
-When using camel-aws2-msk-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-aws2-msk-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.aws2msk.CamelAws2mskSinkConnector
-----
-
-
-The camel-aws2-msk sink connector supports 31 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.label* | Logical name | null | true | HIGH
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.mskClient* | To use a existing configured AWS MSK as client | null | false | MEDIUM
-| *camel.sink.endpoint.operation* | The operation to perform One of: [listClusters] [createCluster] [deleteCluster] [describeCluster] | null | true | HIGH
-| *camel.sink.endpoint.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.sink.endpoint.pojoRequest* | If we want to use a POJO request as body or not | false | false | MEDIUM
-| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the MSK client | null | false | MEDIUM
-| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the MSK client | null | false | MEDIUM
-| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the MSK client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *camel.sink.endpoint.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() | null | false | MEDIUM
-| *camel.sink.endpoint.trustAllCertificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.sink.endpoint.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.sink.endpoint.useDefaultCredentialsProvider* | Set whether the Kafka client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | false | false | MEDIUM
-| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-| *camel.component.aws2-msk.configuration* | Component configuration | null | false | MEDIUM
-| *camel.component.aws2-msk.lazyStartProducer* | 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.aws2-msk.mskClient* | To use a existing configured AWS MSK as client | null | false | MEDIUM
-| *camel.component.aws2-msk.operation* | The operation to perform One of: [listClusters] [createCluster] [deleteCluster] [describeCluster] | null | true | HIGH
-| *camel.component.aws2-msk.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.component.aws2-msk.pojoRequest* | If we want to use a POJO request as body or not | false | false | MEDIUM
-| *camel.component.aws2-msk.proxyHost* | To define a proxy host when instantiating the MSK client | null | false | MEDIUM
-| *camel.component.aws2-msk.proxyPort* | To define a proxy port when instantiating the MSK client | null | false | MEDIUM
-| *camel.component.aws2-msk.proxyProtocol* | To define a proxy protocol when instantiating the MSK client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *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() | null | false | MEDIUM
-| *camel.component.aws2-msk.trustAllCertificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.component.aws2-msk.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.component.aws2-msk.useDefaultCredentials Provider* | Set whether the Kafka client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | false | false | MEDIUM
-| *camel.component.aws2-msk.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.aws2-msk.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.component.aws2-msk.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-|===
-
-
-
-The camel-aws2-msk sink connector has no converters out of the box.
-
-
-
-
-
-The camel-aws2-msk sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-aws2-msk sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-aws2-s3-kafka-connector/src/main/docs/camel-aws2-s3-kafka-sink-connector.adoc b/connectors/camel-aws2-s3-kafka-connector/src/main/docs/camel-aws2-s3-kafka-sink-connector.adoc
deleted file mode 100644
index c4cb87a..0000000
--- a/connectors/camel-aws2-s3-kafka-connector/src/main/docs/camel-aws2-s3-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,149 +0,0 @@
-// kafka-connector options: START
-[[camel-aws2-s3-kafka-connector-sink]]
-= camel-aws2-s3-kafka-connector sink configuration
-
-Connector Description: Store and retrieve objects from AWS S3 Storage Service using AWS SDK version 2.x.
-
-When using camel-aws2-s3-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-aws2-s3-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.aws2s3.CamelAws2s3SinkConnector
-----
-
-
-The camel-aws2-s3 sink connector supports 71 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.bucketNameOrArn* | Bucket name or ARN | null | true | HIGH
-| *camel.sink.endpoint.amazonS3Client* | Reference to a com.amazonaws.services.s3.AmazonS3 in the registry. | null | false | MEDIUM
-| *camel.sink.endpoint.amazonS3Presigner* | An S3 Presigner for Request, used mainly in createDownloadLink operation | null | false | MEDIUM
-| *camel.sink.endpoint.autoCreateBucket* | 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. | false | false | MEDIUM
-| *camel.sink.endpoint.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.sink.endpoint.pojoRequest* | If we want to use a POJO request as body or not | false | false | MEDIUM
-| *camel.sink.endpoint.policy* | The policy for this queue to set in the com.amazonaws.services.s3.AmazonS3#setBucketPolicy() method. | null | false | MEDIUM
-| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the SQS client | null | false | MEDIUM
-| *camel.sink.endpoint.proxyPort* | Specify a proxy port to be used inside the client definition. | null | false | MEDIUM
-| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the S3 client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *camel.sink.endpoint.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() | null | false | MEDIUM
-| *camel.sink.endpoint.trustAllCertificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.sink.endpoint.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.sink.endpoint.useDefaultCredentialsProvider* | 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 | false | MEDIUM
-| *camel.sink.endpoint.customerAlgorithm* | Define the customer algorithm to use in case CustomerKey is enabled | null | false | MEDIUM
-| *camel.sink.endpoint.customerKeyId* | Define the id of Customer key to use in case CustomerKey is enabled | null | false | MEDIUM
-| *camel.sink.endpoint.customerKeyMD5* | Define the MD5 of Customer key to use in case CustomerKey is enabled | null | false | MEDIUM
-| *camel.sink.endpoint.batchMessageNumber* | The number of messages composing a batch in streaming upload mode | 10 | false | MEDIUM
-| *camel.sink.endpoint.batchSize* | The batch size (in bytes) in streaming upload mode | 1000000 | false | MEDIUM
-| *camel.sink.endpoint.deleteAfterWrite* | Delete file object after the S3 file has been uploaded | false | false | MEDIUM
-| *camel.sink.endpoint.keyName* | Setting the key name for an element in the bucket through endpoint parameter | null | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.multiPartUpload* | If it is true, camel will upload the file with multi part format, the part size is decided by the option of partSize | false | false | MEDIUM
-| *camel.sink.endpoint.namingStrategy* | The naming strategy to use in streaming upload mode One of: [progressive] [random] | "progressive" | false | MEDIUM
-| *camel.sink.endpoint.operation* | The operation to do in case the user don't want to do only an upload One of: [copyObject] [listObjects] [deleteObject] [deleteBucket] [listBuckets] [getObject] [getObjectRange] [createDownloadLink] | null | false | MEDIUM
-| *camel.sink.endpoint.partSize* | Setup the partSize which is used in multi part upload, the default size is 25M. | 26214400L | false | MEDIUM
-| *camel.sink.endpoint.restartingPolicy* | The restarting policy to use in streaming upload mode One of: [override] [lastPart] | "override" | false | MEDIUM
-| *camel.sink.endpoint.storageClass* | The storage class to set in the com.amazonaws.services.s3.model.PutObjectRequest request. | null | false | MEDIUM
-| *camel.sink.endpoint.streamingUploadMode* | When stream mode is true the upload to bucket will be done in streaming | false | false | MEDIUM
-| *camel.sink.endpoint.streamingUploadTimeout* | While streaming upload mode is true, this option set the timeout to complete upload | null | false | MEDIUM
-| *camel.sink.endpoint.awsKMSKeyId* | Define the id of KMS key to use in case KMS is enabled | null | false | MEDIUM
-| *camel.sink.endpoint.useAwsKMS* | Define if KMS must be used or not | false | false | MEDIUM
-| *camel.sink.endpoint.useCustomerKey* | Define if Customer Key must be used or not | false | false | MEDIUM
-| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-| *camel.component.aws2-s3.amazonS3Client* | Reference to a com.amazonaws.services.s3.AmazonS3 in the registry. | null | false | MEDIUM
-| *camel.component.aws2-s3.amazonS3Presigner* | An S3 Presigner for Request, used mainly in createDownloadLink operation | null | false | MEDIUM
-| *camel.component.aws2-s3.autoCreateBucket* | 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. | false | false | MEDIUM
-| *camel.component.aws2-s3.configuration* | The component configuration | null | false | MEDIUM
-| *camel.component.aws2-s3.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.component.aws2-s3.pojoRequest* | If we want to use a POJO request as body or not | false | false | MEDIUM
-| *camel.component.aws2-s3.policy* | The policy for this queue to set in the com.amazonaws.services.s3.AmazonS3#setBucketPolicy() method. | null | false | MEDIUM
-| *camel.component.aws2-s3.proxyHost* | To define a proxy host when instantiating the SQS client | null | false | MEDIUM
-| *camel.component.aws2-s3.proxyPort* | Specify a proxy port to be used inside the client definition. | null | false | MEDIUM
-| *camel.component.aws2-s3.proxyProtocol* | To define a proxy protocol when instantiating the S3 client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *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() | null | false | MEDIUM
-| *camel.component.aws2-s3.trustAllCertificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.component.aws2-s3.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.component.aws2-s3.useDefaultCredentials 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 | false | MEDIUM
-| *camel.component.aws2-s3.customerAlgorithm* | Define the customer algorithm to use in case CustomerKey is enabled | null | false | MEDIUM
-| *camel.component.aws2-s3.customerKeyId* | Define the id of Customer key to use in case CustomerKey is enabled | null | false | MEDIUM
-| *camel.component.aws2-s3.customerKeyMD5* | Define the MD5 of Customer key to use in case CustomerKey is enabled | null | false | MEDIUM
-| *camel.component.aws2-s3.batchMessageNumber* | The number of messages composing a batch in streaming upload mode | 10 | false | MEDIUM
-| *camel.component.aws2-s3.batchSize* | The batch size (in bytes) in streaming upload mode | 1000000 | false | MEDIUM
-| *camel.component.aws2-s3.deleteAfterWrite* | Delete file object after the S3 file has been uploaded | false | false | MEDIUM
-| *camel.component.aws2-s3.keyName* | Setting the key name for an element in the bucket through endpoint parameter | null | false | MEDIUM
-| *camel.component.aws2-s3.lazyStartProducer* | 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.aws2-s3.multiPartUpload* | If it is true, camel will upload the file with multi part format, the part size is decided by the option of partSize | false | false | MEDIUM
-| *camel.component.aws2-s3.namingStrategy* | The naming strategy to use in streaming upload mode One of: [progressive] [random] | "progressive" | false | MEDIUM
-| *camel.component.aws2-s3.operation* | The operation to do in case the user don't want to do only an upload One of: [copyObject] [listObjects] [deleteObject] [deleteBucket] [listBuckets] [getObject] [getObjectRange] [createDownloadLink] | null | false | MEDIUM
-| *camel.component.aws2-s3.partSize* | Setup the partSize which is used in multi part upload, the default size is 25M. | 26214400L | false | MEDIUM
-| *camel.component.aws2-s3.restartingPolicy* | The restarting policy to use in streaming upload mode One of: [override] [lastPart] | "override" | false | MEDIUM
-| *camel.component.aws2-s3.storageClass* | The storage class to set in the com.amazonaws.services.s3.model.PutObjectRequest request. | null | false | MEDIUM
-| *camel.component.aws2-s3.streamingUploadMode* | When stream mode is true the upload to bucket will be done in streaming | false | false | MEDIUM
-| *camel.component.aws2-s3.streamingUploadTimeout* | While streaming upload mode is true, this option set the timeout to complete upload | null | false | MEDIUM
-| *camel.component.aws2-s3.awsKMSKeyId* | Define the id of KMS key to use in case KMS is enabled | null | false | MEDIUM
-| *camel.component.aws2-s3.useAwsKMS* | Define if KMS must be used or not | false | false | MEDIUM
-| *camel.component.aws2-s3.useCustomerKey* | Define if Customer Key must be used or not | false | false | MEDIUM
-| *camel.component.aws2-s3.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.aws2-s3.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.component.aws2-s3.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-|===
-
-
-
-The camel-aws2-s3 sink connector supports 1 converters out of the box, which are listed below.
-
-
-
-[source,java]
-----
-
-org.apache.camel.kafkaconnector.aws2s3.converters.S3ObjectConverter
-
-----
-
-
-
-The camel-aws2-s3 sink connector supports 3 transforms out of the box, which are listed below.
-
-
-
-[source,java]
-----
-
-org.apache.camel.kafkaconnector.aws2s3.transformers.JSONToRecordTransforms
-
-org.apache.camel.kafkaconnector.aws2s3.transformers.RecordToJSONTransforms
-
-org.apache.camel.kafkaconnector.aws2s3.transformers.S3ObjectTransforms
-
-----
-
-
-
-The camel-aws2-s3 sink connector supports 1 aggregation strategies out of the box, which are listed below.
-
-
-
-[source,java]
-----
-
-org.apache.camel.kafkaconnector.aws2s3.aggregation.NewlineAggregationStrategy
-
-----
-// kafka-connector options: END
diff --git a/connectors/camel-aws2-s3-kafka-connector/src/main/docs/camel-aws2-s3-kafka-source-connector.adoc b/connectors/camel-aws2-s3-kafka-connector/src/main/docs/camel-aws2-s3-kafka-source-connector.adoc
deleted file mode 100644
index ffb30bb..0000000
--- a/connectors/camel-aws2-s3-kafka-connector/src/main/docs/camel-aws2-s3-kafka-source-connector.adoc
+++ /dev/null
@@ -1,165 +0,0 @@
-// kafka-connector options: START
-[[camel-aws2-s3-kafka-connector-source]]
-= camel-aws2-s3-kafka-connector source configuration
-
-Connector description: Store and retrieve objects from AWS S3 Storage Service using AWS SDK version 2.x.
-
-When using camel-aws2-s3-kafka-connector as source make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-aws2-s3-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Source connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.aws2s3.CamelAws2s3SourceConnector
-----
-
-
-The camel-aws2-s3 source connector supports 87 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.source.path.bucketNameOrArn* | Bucket name or ARN | null | true | HIGH
-| *camel.source.endpoint.amazonS3Client* | Reference to a com.amazonaws.services.s3.AmazonS3 in the registry. | null | false | MEDIUM
-| *camel.source.endpoint.amazonS3Presigner* | An S3 Presigner for Request, used mainly in createDownloadLink operation | null | false | MEDIUM
-| *camel.source.endpoint.autoCreateBucket* | 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. | false | false | MEDIUM
-| *camel.source.endpoint.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.source.endpoint.pojoRequest* | If we want to use a POJO request as body or not | false | false | MEDIUM
-| *camel.source.endpoint.policy* | The policy for this queue to set in the com.amazonaws.services.s3.AmazonS3#setBucketPolicy() method. | null | false | MEDIUM
-| *camel.source.endpoint.proxyHost* | To define a proxy host when instantiating the SQS client | null | false | MEDIUM
-| *camel.source.endpoint.proxyPort* | Specify a proxy port to be used inside the client definition. | null | false | MEDIUM
-| *camel.source.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the S3 client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *camel.source.endpoint.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() | null | false | MEDIUM
-| *camel.source.endpoint.trustAllCertificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.source.endpoint.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.source.endpoint.useDefaultCredentials 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 | false | MEDIUM
-| *camel.source.endpoint.customerAlgorithm* | Define the customer algorithm to use in case CustomerKey is enabled | null | false | MEDIUM
-| *camel.source.endpoint.customerKeyId* | Define the id of Customer key to use in case CustomerKey is enabled | null | false | MEDIUM
-| *camel.source.endpoint.customerKeyMD5* | Define the MD5 of Customer key to use in case CustomerKey is enabled | null | false | MEDIUM
-| *camel.source.endpoint.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.source.endpoint.deleteAfterRead* | 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 only [...]
-| *camel.source.endpoint.delimiter* | The delimiter which is used in the com.amazonaws.services.s3.model.ListObjectsRequest to only consume objects we are interested in. | null | false | MEDIUM
-| *camel.source.endpoint.destinationBucket* | Define the destination bucket where an object must be moved when moveAfterRead is set to true. | null | false | MEDIUM
-| *camel.source.endpoint.destinationBucketPrefix* | Define the destination bucket prefix to use when an object must be moved and moveAfterRead is set to true. | null | false | MEDIUM
-| *camel.source.endpoint.destinationBucketSuffix* | Define the destination bucket suffix to use when an object must be moved and moveAfterRead is set to true. | null | false | MEDIUM
-| *camel.source.endpoint.doneFileName* | If provided, Camel will only consume files if a done file exists. | null | false | MEDIUM
-| *camel.source.endpoint.fileName* | To get the object from the bucket with the given file name | null | false | MEDIUM
-| *camel.source.endpoint.ignoreBody* | If it is true, the S3 Object Body will be ignored completely, if it is set to false the S3 Object will be put in the body. Setting this to true, will override any behavior defined by includeBody option. | false | false | MEDIUM
-| *camel.source.endpoint.includeBody* | 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, while in case of includeBody false then it will be up to the caller to close t [...]
-| *camel.source.endpoint.includeFolders* | 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 | false | MEDIUM
-| *camel.source.endpoint.maxConnections* | Set the maxConnections parameter in the S3 client configuration | 60 | false | MEDIUM
-| *camel.source.endpoint.maxMessagesPerPoll* | Gets the maximum number of messages as a limit to poll at each polling. Gets the maximum number of messages as a limit to poll at each polling. The default value is 10. Use 0 or a negative number to set it as unlimited. | 10 | false | MEDIUM
-| *camel.source.endpoint.moveAfterRead* | 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 | false | MEDIUM
-| *camel.source.endpoint.prefix* | The prefix which is used in the com.amazonaws.services.s3.model.ListObjectsRequest to only consume objects we are interested in. | null | false | MEDIUM
-| *camel.source.endpoint.sendEmptyMessageWhenIdle* | If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead. | false | false | MEDIUM
-| *camel.source.endpoint.autocloseBody* | 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 | false | MEDIUM
-| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | false | MEDIUM
-| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | false | MEDIUM
-| *camel.source.endpoint.pollStrategy* | A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel. | null | false | MEDIUM
-| *camel.source.endpoint.backoffErrorThreshold* | The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in. | null | false | MEDIUM
-| *camel.source.endpoint.backoffIdleThreshold* | The number of subsequent idle polls that should happen before the backoffMultipler should kick-in. | null | false | MEDIUM
-| *camel.source.endpoint.backoffMultiplier* | To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured. | null | false | MEDIUM
-| *camel.source.endpoint.delay* | Milliseconds before the next poll. | 500L | false | MEDIUM
-| *camel.source.endpoint.greedy* | If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages. | false | false | MEDIUM
-| *camel.source.endpoint.initialDelay* | Milliseconds before the first poll starts. | 1000L | false | MEDIUM
-| *camel.source.endpoint.repeatCount* | Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever. | 0L | false | MEDIUM
-| *camel.source.endpoint.runLoggingLevel* | The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that. One of: [TRACE] [DEBUG] [INFO] [WARN] [ERROR] [OFF] | "TRACE" | false | MEDIUM
-| *camel.source.endpoint.scheduledExecutorService* | Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool. | null | false | MEDIUM
-| *camel.source.endpoint.scheduler* | To use a cron scheduler from either camel-spring or camel-quartz component. Use value spring or quartz for built in scheduler | "none" | false | MEDIUM
-| *camel.source.endpoint.schedulerProperties* | To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler. | null | false | MEDIUM
-| *camel.source.endpoint.startScheduler* | Whether the scheduler should be auto started. | true | false | MEDIUM
-| *camel.source.endpoint.timeUnit* | Time unit for initialDelay and delay options. One of: [NANOSECONDS] [MICROSECONDS] [MILLISECONDS] [SECONDS] [MINUTES] [HOURS] [DAYS] | "MILLISECONDS" | false | MEDIUM
-| *camel.source.endpoint.useFixedDelay* | Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details. | true | false | MEDIUM
-| *camel.source.endpoint.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.source.endpoint.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-| *camel.component.aws2-s3.amazonS3Client* | Reference to a com.amazonaws.services.s3.AmazonS3 in the registry. | null | false | MEDIUM
-| *camel.component.aws2-s3.amazonS3Presigner* | An S3 Presigner for Request, used mainly in createDownloadLink operation | null | false | MEDIUM
-| *camel.component.aws2-s3.autoCreateBucket* | 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. | false | false | MEDIUM
-| *camel.component.aws2-s3.configuration* | The component configuration | null | false | MEDIUM
-| *camel.component.aws2-s3.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.component.aws2-s3.pojoRequest* | If we want to use a POJO request as body or not | false | false | MEDIUM
-| *camel.component.aws2-s3.policy* | The policy for this queue to set in the com.amazonaws.services.s3.AmazonS3#setBucketPolicy() method. | null | false | MEDIUM
-| *camel.component.aws2-s3.proxyHost* | To define a proxy host when instantiating the SQS client | null | false | MEDIUM
-| *camel.component.aws2-s3.proxyPort* | Specify a proxy port to be used inside the client definition. | null | false | MEDIUM
-| *camel.component.aws2-s3.proxyProtocol* | To define a proxy protocol when instantiating the S3 client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *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() | null | false | MEDIUM
-| *camel.component.aws2-s3.trustAllCertificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.component.aws2-s3.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.component.aws2-s3.useDefaultCredentials 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 | false | MEDIUM
-| *camel.component.aws2-s3.customerAlgorithm* | Define the customer algorithm to use in case CustomerKey is enabled | null | false | MEDIUM
-| *camel.component.aws2-s3.customerKeyId* | Define the id of Customer key to use in case CustomerKey is enabled | null | false | MEDIUM
-| *camel.component.aws2-s3.customerKeyMD5* | Define the MD5 of Customer key to use in case CustomerKey is enabled | null | false | MEDIUM
-| *camel.component.aws2-s3.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.component.aws2-s3.deleteAfterRead* | 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 onl [...]
-| *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. | null | false | MEDIUM
-| *camel.component.aws2-s3.destinationBucket* | Define the destination bucket where an object must be moved when moveAfterRead is set to true. | null | false | MEDIUM
-| *camel.component.aws2-s3.destinationBucketPrefix* | Define the destination bucket prefix to use when an object must be moved and moveAfterRead is set to true. | null | false | MEDIUM
-| *camel.component.aws2-s3.destinationBucketSuffix* | Define the destination bucket suffix to use when an object must be moved and moveAfterRead is set to true. | null | false | MEDIUM
-| *camel.component.aws2-s3.doneFileName* | If provided, Camel will only consume files if a done file exists. | null | false | MEDIUM
-| *camel.component.aws2-s3.fileName* | To get the object from the bucket with the given file name | null | false | MEDIUM
-| *camel.component.aws2-s3.ignoreBody* | If it is true, the S3 Object Body will be ignored completely, if it is set to false the S3 Object will be put in the body. Setting this to true, will override any behavior defined by includeBody option. | false | false | MEDIUM
-| *camel.component.aws2-s3.includeBody* | 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, while in case of includeBody false then it will be up to the caller to close [...]
-| *camel.component.aws2-s3.includeFolders* | 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 | false | MEDIUM
-| *camel.component.aws2-s3.moveAfterRead* | 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 | false | MEDIUM
-| *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. | null | false | MEDIUM
-| *camel.component.aws2-s3.autocloseBody* | 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 | false | MEDIUM
-| *camel.component.aws2-s3.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.aws2-s3.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.component.aws2-s3.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-|===
-
-
-
-The camel-aws2-s3 source connector supports 1 converters out of the box, which are listed below.
-
-
-
-[source,java]
-----
-
-org.apache.camel.kafkaconnector.aws2s3.converters.S3ObjectConverter
-
-----
-
-
-
-The camel-aws2-s3 source connector supports 3 transforms out of the box, which are listed below.
-
-
-
-[source,java]
-----
-
-org.apache.camel.kafkaconnector.aws2s3.transformers.JSONToRecordTransforms
-
-org.apache.camel.kafkaconnector.aws2s3.transformers.RecordToJSONTransforms
-
-org.apache.camel.kafkaconnector.aws2s3.transformers.S3ObjectTransforms
-
-----
-
-
-
-The camel-aws2-s3 source connector supports 1 aggregation strategies out of the box, which are listed below.
-
-
-
-[source,java]
-----
-
-org.apache.camel.kafkaconnector.aws2s3.aggregation.NewlineAggregationStrategy
-
-----
-// kafka-connector options: END
diff --git a/connectors/camel-aws2-ses-kafka-connector/src/main/docs/camel-aws2-ses-kafka-sink-connector.adoc b/connectors/camel-aws2-ses-kafka-connector/src/main/docs/camel-aws2-ses-kafka-sink-connector.adoc
deleted file mode 100644
index b2343e3..0000000
--- a/connectors/camel-aws2-ses-kafka-connector/src/main/docs/camel-aws2-ses-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,86 +0,0 @@
-// kafka-connector options: START
-[[camel-aws2-ses-kafka-connector-sink]]
-= camel-aws2-ses-kafka-connector sink configuration
-
-Connector Description: Send e-mails through AWS SES service using AWS SDK version 2.x.
-
-When using camel-aws2-ses-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-aws2-ses-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.aws2ses.CamelAws2sesSinkConnector
-----
-
-
-The camel-aws2-ses sink connector supports 35 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.from* | The sender's email address. | null | true | HIGH
-| *camel.sink.endpoint.amazonSESClient* | To use the AmazonSimpleEmailService as the client | null | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the SES client | null | false | MEDIUM
-| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the SES client | null | false | MEDIUM
-| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the SES client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *camel.sink.endpoint.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() | null | false | MEDIUM
-| *camel.sink.endpoint.replyToAddresses* | List of reply-to email address(es) for the message, override it using 'CamelAwsSesReplyToAddresses' header. | null | false | MEDIUM
-| *camel.sink.endpoint.returnPath* | The email address to which bounce notifications are to be forwarded, override it using 'CamelAwsSesReturnPath' header. | null | false | MEDIUM
-| *camel.sink.endpoint.subject* | The subject which is used if the message header 'CamelAwsSesSubject' is not present. | null | false | MEDIUM
-| *camel.sink.endpoint.to* | List of destination email address. Can be overriden with 'CamelAwsSesTo' header. | null | false | MEDIUM
-| *camel.sink.endpoint.trustAllCertificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.sink.endpoint.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.sink.endpoint.useDefaultCredentialsProvider* | Set whether the Ses client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | false | false | MEDIUM
-| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-| *camel.component.aws2-ses.amazonSESClient* | To use the AmazonSimpleEmailService as the client | null | false | MEDIUM
-| *camel.component.aws2-ses.configuration* | component configuration | null | false | MEDIUM
-| *camel.component.aws2-ses.lazyStartProducer* | 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.aws2-ses.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.component.aws2-ses.proxyHost* | To define a proxy host when instantiating the SES client | null | false | MEDIUM
-| *camel.component.aws2-ses.proxyPort* | To define a proxy port when instantiating the SES client | null | false | MEDIUM
-| *camel.component.aws2-ses.proxyProtocol* | To define a proxy protocol when instantiating the SES client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *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() | null | false | MEDIUM
-| *camel.component.aws2-ses.replyToAddresses* | List of reply-to email address(es) for the message, override it using 'CamelAwsSesReplyToAddresses' header. | null | false | MEDIUM
-| *camel.component.aws2-ses.returnPath* | The email address to which bounce notifications are to be forwarded, override it using 'CamelAwsSesReturnPath' header. | null | false | MEDIUM
-| *camel.component.aws2-ses.subject* | The subject which is used if the message header 'CamelAwsSesSubject' is not present. | null | false | MEDIUM
-| *camel.component.aws2-ses.to* | List of destination email address. Can be overriden with 'CamelAwsSesTo' header. | null | false | MEDIUM
-| *camel.component.aws2-ses.trustAllCertificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.component.aws2-ses.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.component.aws2-ses.useDefaultCredentials Provider* | Set whether the Ses client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | false | false | MEDIUM
-| *camel.component.aws2-ses.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.aws2-ses.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.component.aws2-ses.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-|===
-
-
-
-The camel-aws2-ses sink connector has no converters out of the box.
-
-
-
-
-
-The camel-aws2-ses sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-aws2-ses sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-aws2-sns-kafka-connector/src/main/docs/camel-aws2-sns-kafka-sink-connector.adoc b/connectors/camel-aws2-sns-kafka-connector/src/main/docs/camel-aws2-sns-kafka-sink-connector.adoc
deleted file mode 100644
index f36dc00..0000000
--- a/connectors/camel-aws2-sns-kafka-connector/src/main/docs/camel-aws2-sns-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,99 +0,0 @@
-// kafka-connector options: START
-[[camel-aws2-sns-kafka-connector-sink]]
-= camel-aws2-sns-kafka-connector sink configuration
-
-Connector Description: Send messages to an AWS Simple Notification Topic using AWS SDK version 2.x.
-
-When using camel-aws2-sns-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-aws2-sns-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.aws2sns.CamelAws2snsSinkConnector
-----
-
-
-The camel-aws2-sns sink connector supports 48 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.topicNameOrArn* | Topic name or ARN | null | true | HIGH
-| *camel.sink.endpoint.amazonSNSClient* | To use the AmazonSNS as the client | null | false | MEDIUM
-| *camel.sink.endpoint.autoCreateTopic* | Setting the autocreation of the topic | false | false | MEDIUM
-| *camel.sink.endpoint.headerFilterStrategy* | To use a custom HeaderFilterStrategy to map headers to/from Camel. | null | false | MEDIUM
-| *camel.sink.endpoint.kmsMasterKeyId* | The ID of an AWS-managed customer master key (CMK) for Amazon SNS or a custom CMK. | null | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.messageDeduplicationIdStrategy* | 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. One of: [useExchangeId] [useContentBasedDeduplication] | "useExchangeId" | false | MEDIUM
-| *camel.sink.endpoint.messageGroupIdStrategy* | 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. One of: [useConstant] [useExchangeId] [usePropertyValue] | null | false | MEDIUM
-| *camel.sink.endpoint.messageStructure* | The message structure to use such as json | null | false | MEDIUM
-| *camel.sink.endpoint.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.sink.endpoint.policy* | The policy for this topic. Is loaded by default from classpath, but you can prefix with classpath:, file:, or http: to load the resource from different systems. | null | false | MEDIUM
-| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the SNS client | null | false | MEDIUM
-| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the SNS client | null | false | MEDIUM
-| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the SNS client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *camel.sink.endpoint.queueUrl* | The queueUrl to subscribe to | null | false | MEDIUM
-| *camel.sink.endpoint.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() | null | false | MEDIUM
-| *camel.sink.endpoint.serverSideEncryptionEnabled* | Define if Server Side Encryption is enabled or not on the topic | false | false | MEDIUM
-| *camel.sink.endpoint.subject* | The subject which is used if the message header 'CamelAwsSnsSubject' is not present. | null | false | MEDIUM
-| *camel.sink.endpoint.subscribeSNStoSQS* | Define if the subscription between SNS Topic and SQS must be done or not | false | false | MEDIUM
-| *camel.sink.endpoint.trustAllCertificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.sink.endpoint.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.sink.endpoint.useDefaultCredentialsProvider* | 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 | false | MEDIUM
-| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-| *camel.component.aws2-sns.amazonSNSClient* | To use the AmazonSNS as the client | null | false | MEDIUM
-| *camel.component.aws2-sns.autoCreateTopic* | Setting the autocreation of the topic | false | false | MEDIUM
-| *camel.component.aws2-sns.configuration* | Component configuration | null | false | MEDIUM
-| *camel.component.aws2-sns.kmsMasterKeyId* | The ID of an AWS-managed customer master key (CMK) for Amazon SNS or a custom CMK. | null | false | MEDIUM
-| *camel.component.aws2-sns.lazyStartProducer* | 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.aws2-sns.messageDeduplicationId 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. One of: [useExchangeId] [useContentBasedDeduplication] | "useExchangeId" | false | MEDIUM
-| *camel.component.aws2-sns.messageGroupIdStrategy* | 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. One of: [useConstant] [useExchangeId] [usePropertyValue] | null | false | MEDIUM
-| *camel.component.aws2-sns.messageStructure* | The message structure to use such as json | null | false | MEDIUM
-| *camel.component.aws2-sns.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.component.aws2-sns.policy* | The policy for this topic. Is loaded by default from classpath, but you can prefix with classpath:, file:, or http: to load the resource from different systems. | null | false | MEDIUM
-| *camel.component.aws2-sns.proxyHost* | To define a proxy host when instantiating the SNS client | null | false | MEDIUM
-| *camel.component.aws2-sns.proxyPort* | To define a proxy port when instantiating the SNS client | null | false | MEDIUM
-| *camel.component.aws2-sns.proxyProtocol* | To define a proxy protocol when instantiating the SNS client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *camel.component.aws2-sns.queueUrl* | The queueUrl to subscribe to | null | false | MEDIUM
-| *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() | null | false | MEDIUM
-| *camel.component.aws2-sns.serverSideEncryption Enabled* | Define if Server Side Encryption is enabled or not on the topic | false | false | MEDIUM
-| *camel.component.aws2-sns.subject* | The subject which is used if the message header 'CamelAwsSnsSubject' is not present. | null | false | MEDIUM
-| *camel.component.aws2-sns.subscribeSNStoSQS* | Define if the subscription between SNS Topic and SQS must be done or not | false | false | MEDIUM
-| *camel.component.aws2-sns.trustAllCertificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.component.aws2-sns.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.component.aws2-sns.useDefaultCredentials 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 | false | MEDIUM
-| *camel.component.aws2-sns.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.aws2-sns.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.component.aws2-sns.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-|===
-
-
-
-The camel-aws2-sns sink connector has no converters out of the box.
-
-
-
-
-
-The camel-aws2-sns sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-aws2-sns sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-aws2-sqs-kafka-connector/src/main/docs/camel-aws2-sqs-kafka-sink-connector.adoc b/connectors/camel-aws2-sqs-kafka-connector/src/main/docs/camel-aws2-sqs-kafka-sink-connector.adoc
deleted file mode 100644
index 80d7a6f..0000000
--- a/connectors/camel-aws2-sqs-kafka-connector/src/main/docs/camel-aws2-sqs-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,118 +0,0 @@
-// kafka-connector options: START
-[[camel-aws2-sqs-kafka-connector-sink]]
-= camel-aws2-sqs-kafka-connector sink configuration
-
-Connector Description: Sending and receive messages to/from AWS SQS service using AWS SDK version 2.x.
-
-When using camel-aws2-sqs-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-aws2-sqs-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.aws2sqs.CamelAws2sqsSinkConnector
-----
-
-
-The camel-aws2-sqs sink connector supports 60 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.queueNameOrArn* | Queue name or ARN | null | true | HIGH
-| *camel.sink.endpoint.amazonAWSHost* | The hostname of the Amazon AWS cloud. | "amazonaws.com" | false | MEDIUM
-| *camel.sink.endpoint.amazonSQSClient* | To use the AmazonSQS as client | null | false | MEDIUM
-| *camel.sink.endpoint.autoCreateQueue* | Setting the autocreation of the queue | false | false | MEDIUM
-| *camel.sink.endpoint.headerFilterStrategy* | To use a custom HeaderFilterStrategy to map headers to/from Camel. | null | false | MEDIUM
-| *camel.sink.endpoint.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.sink.endpoint.protocol* | The underlying protocol used to communicate with SQS | "https" | false | MEDIUM
-| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the SQS client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *camel.sink.endpoint.queueOwnerAWSAccountId* | Specify the queue owner aws account id when you need to connect the queue with different account owner. | null | false | MEDIUM
-| *camel.sink.endpoint.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() | null | false | MEDIUM
-| *camel.sink.endpoint.trustAllCertificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.sink.endpoint.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.sink.endpoint.useDefaultCredentialsProvider* | 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 | false | MEDIUM
-| *camel.sink.endpoint.batchSeparator* | Set the separator when passing a String to send batch message operation | "," | false | MEDIUM
-| *camel.sink.endpoint.delaySeconds* | Delay sending messages for a number of seconds. | null | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.messageDeduplicationIdStrategy* | 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. One of: [useExchangeId] [useContentBasedDeduplication] | "useExchangeId" | false | MEDIUM
-| *camel.sink.endpoint.messageGroupIdStrategy* | 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. One of: [useConstant] [useExchangeId] [usePropertyValue] | null | false | MEDIUM
-| *camel.sink.endpoint.operation* | The operation to do in case the user don't want to send only a message One of: [sendBatchMessage] [deleteMessage] [listQueues] [purgeQueue] | null | false | MEDIUM
-| *camel.sink.endpoint.delayQueue* | Define if you want to apply delaySeconds option to the queue or on single messages | false | false | MEDIUM
-| *camel.sink.endpoint.queueUrl* | 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. | null | false | MEDIUM
-| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the SQS client | null | false | MEDIUM
-| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the SQS client | null | false | MEDIUM
-| *camel.sink.endpoint.maximumMessageSize* | The maximumMessageSize (in bytes) an SQS message can contain for this queue. | null | false | MEDIUM
-| *camel.sink.endpoint.messageRetentionPeriod* | The messageRetentionPeriod (in seconds) a message will be retained by SQS for this queue. | null | false | MEDIUM
-| *camel.sink.endpoint.policy* | The policy for this queue. It can be loaded by default from classpath, but you can prefix with classpath:, file:, or http: to load the resource from different systems. | null | false | MEDIUM
-| *camel.sink.endpoint.receiveMessageWaitTimeSeconds* | If you do not specify WaitTimeSeconds in the request, the queue attribute ReceiveMessageWaitTimeSeconds is used to determine how long to wait. | null | false | MEDIUM
-| *camel.sink.endpoint.redrivePolicy* | Specify the policy that send message to DeadLetter queue. See detail at Amazon docs. | null | false | MEDIUM
-| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-| *camel.component.aws2-sqs.amazonAWSHost* | The hostname of the Amazon AWS cloud. | "amazonaws.com" | false | MEDIUM
-| *camel.component.aws2-sqs.amazonSQSClient* | To use the AmazonSQS as client | null | false | MEDIUM
-| *camel.component.aws2-sqs.autoCreateQueue* | Setting the autocreation of the queue | false | false | MEDIUM
-| *camel.component.aws2-sqs.configuration* | The AWS SQS default configuration | null | false | MEDIUM
-| *camel.component.aws2-sqs.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.component.aws2-sqs.protocol* | The underlying protocol used to communicate with SQS | "https" | false | MEDIUM
-| *camel.component.aws2-sqs.proxyProtocol* | To define a proxy protocol when instantiating the SQS client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *camel.component.aws2-sqs.queueOwnerAWSAccountId* | Specify the queue owner aws account id when you need to connect the queue with different account owner. | null | false | MEDIUM
-| *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() | null | false | MEDIUM
-| *camel.component.aws2-sqs.trustAllCertificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.component.aws2-sqs.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.component.aws2-sqs.useDefaultCredentials 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 | false | MEDIUM
-| *camel.component.aws2-sqs.batchSeparator* | Set the separator when passing a String to send batch message operation | "," | false | MEDIUM
-| *camel.component.aws2-sqs.delaySeconds* | Delay sending messages for a number of seconds. | null | false | MEDIUM
-| *camel.component.aws2-sqs.lazyStartProducer* | 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.aws2-sqs.messageDeduplicationId 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. One of: [useExchangeId] [useContentBasedDeduplication] | "useExchangeId" | false | MEDIUM
-| *camel.component.aws2-sqs.messageGroupIdStrategy* | 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. One of: [useConstant] [useExchangeId] [usePropertyValue] | null | false | MEDIUM
-| *camel.component.aws2-sqs.operation* | The operation to do in case the user don't want to send only a message One of: [sendBatchMessage] [deleteMessage] [listQueues] [purgeQueue] | null | false | MEDIUM
-| *camel.component.aws2-sqs.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.aws2-sqs.delayQueue* | Define if you want to apply delaySeconds option to the queue or on single messages | false | false | MEDIUM
-| *camel.component.aws2-sqs.queueUrl* | 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. | null | false | MEDIUM
-| *camel.component.aws2-sqs.proxyHost* | To define a proxy host when instantiating the SQS client | null | false | MEDIUM
-| *camel.component.aws2-sqs.proxyPort* | To define a proxy port when instantiating the SQS client | null | false | MEDIUM
-| *camel.component.aws2-sqs.maximumMessageSize* | The maximumMessageSize (in bytes) an SQS message can contain for this queue. | null | false | MEDIUM
-| *camel.component.aws2-sqs.messageRetentionPeriod* | The messageRetentionPeriod (in seconds) a message will be retained by SQS for this queue. | null | false | MEDIUM
-| *camel.component.aws2-sqs.policy* | The policy for this queue. It can be loaded by default from classpath, but you can prefix with classpath:, file:, or http: to load the resource from different systems. | null | false | MEDIUM
-| *camel.component.aws2-sqs.receiveMessageWaitTime Seconds* | If you do not specify WaitTimeSeconds in the request, the queue attribute ReceiveMessageWaitTimeSeconds is used to determine how long to wait. | null | false | MEDIUM
-| *camel.component.aws2-sqs.redrivePolicy* | Specify the policy that send message to DeadLetter queue. See detail at Amazon docs. | null | false | MEDIUM
-| *camel.component.aws2-sqs.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.component.aws2-sqs.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-|===
-
-
-
-The camel-aws2-sqs sink connector has no converters out of the box.
-
-
-
-
-
-The camel-aws2-sqs sink connector supports 1 transforms out of the box, which are listed below.
-
-
-
-[source,java]
-----
-
-org.apache.camel.kafkaconnector.aws2sqs.transformers.SQSKeySetterTransforms
-
-----
-
-
-
-The camel-aws2-sqs sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-aws2-sqs-kafka-connector/src/main/docs/camel-aws2-sqs-kafka-source-connector.adoc b/connectors/camel-aws2-sqs-kafka-connector/src/main/docs/camel-aws2-sqs-kafka-source-connector.adoc
deleted file mode 100644
index 1f125b6..0000000
--- a/connectors/camel-aws2-sqs-kafka-connector/src/main/docs/camel-aws2-sqs-kafka-source-connector.adoc
+++ /dev/null
@@ -1,151 +0,0 @@
-// kafka-connector options: START
-[[camel-aws2-sqs-kafka-connector-source]]
-= camel-aws2-sqs-kafka-connector source configuration
-
-Connector description: Sending and receive messages to/from AWS SQS service using AWS SDK version 2.x.
-
-When using camel-aws2-sqs-kafka-connector as source make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-aws2-sqs-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Source connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.aws2sqs.CamelAws2sqsSourceConnector
-----
-
-
-The camel-aws2-sqs source connector supports 93 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.source.path.queueNameOrArn* | Queue name or ARN | null | true | HIGH
-| *camel.source.endpoint.amazonAWSHost* | The hostname of the Amazon AWS cloud. | "amazonaws.com" | false | MEDIUM
-| *camel.source.endpoint.amazonSQSClient* | To use the AmazonSQS as client | null | false | MEDIUM
-| *camel.source.endpoint.autoCreateQueue* | Setting the autocreation of the queue | false | false | MEDIUM
-| *camel.source.endpoint.headerFilterStrategy* | To use a custom HeaderFilterStrategy to map headers to/from Camel. | null | false | MEDIUM
-| *camel.source.endpoint.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.source.endpoint.protocol* | The underlying protocol used to communicate with SQS | "https" | false | MEDIUM
-| *camel.source.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the SQS client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *camel.source.endpoint.queueOwnerAWSAccountId* | Specify the queue owner aws account id when you need to connect the queue with different account owner. | null | false | MEDIUM
-| *camel.source.endpoint.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() | null | false | MEDIUM
-| *camel.source.endpoint.trustAllCertificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.source.endpoint.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.source.endpoint.useDefaultCredentials 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 | false | MEDIUM
-| *camel.source.endpoint.attributeNames* | A list of attribute names to receive when consuming. Multiple names can be separated by comma. | null | false | MEDIUM
-| *camel.source.endpoint.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.source.endpoint.concurrentConsumers* | Allows you to use multiple threads to poll the sqs queue to increase throughput | 1 | false | MEDIUM
-| *camel.source.endpoint.defaultVisibilityTimeout* | The default visibility timeout (in seconds) | null | false | MEDIUM
-| *camel.source.endpoint.deleteAfterRead* | Delete message from SQS after it has been read | true | false | MEDIUM
-| *camel.source.endpoint.deleteIfFiltered* | Whether or not to send the DeleteMessage to the SQS queue if the exchange has property with key Sqs2Constants#SQS_DELETE_FILTERED (CamelAwsSqsDeleteFiltered) set to true. | true | false | MEDIUM
-| *camel.source.endpoint.extendMessageVisibility* | 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 | false | MEDIUM
-| *camel.source.endpoint.kmsDataKeyReusePeriodSeconds* | 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). | null | false | MEDIUM
-| *camel.source.endpoint.kmsMasterKeyId* | The ID of an AWS-managed customer master key (CMK) for Amazon SQS or a custom CMK. | null | false | MEDIUM
-| *camel.source.endpoint.maxMessagesPerPoll* | Gets the maximum number of messages as a limit to poll at each polling. Is default unlimited, but use 0 or negative number to disable it as unlimited. | null | false | MEDIUM
-| *camel.source.endpoint.messageAttributeNames* | A list of message attribute names to receive when consuming. Multiple names can be separated by comma. | null | false | MEDIUM
-| *camel.source.endpoint.sendEmptyMessageWhenIdle* | If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead. | false | false | MEDIUM
-| *camel.source.endpoint.serverSideEncryptionEnabled* | Define if Server Side Encryption is enabled or not on the queue | false | false | MEDIUM
-| *camel.source.endpoint.visibilityTimeout* | 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. | null | false | MEDIUM
-| *camel.source.endpoint.waitTimeSeconds* | 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. | null | false | MEDIUM
-| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | false | MEDIUM
-| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | false | MEDIUM
-| *camel.source.endpoint.pollStrategy* | A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel. | null | false | MEDIUM
-| *camel.source.endpoint.delayQueue* | Define if you want to apply delaySeconds option to the queue or on single messages | false | false | MEDIUM
-| *camel.source.endpoint.queueUrl* | 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. | null | false | MEDIUM
-| *camel.source.endpoint.proxyHost* | To define a proxy host when instantiating the SQS client | null | false | MEDIUM
-| *camel.source.endpoint.proxyPort* | To define a proxy port when instantiating the SQS client | null | false | MEDIUM
-| *camel.source.endpoint.maximumMessageSize* | The maximumMessageSize (in bytes) an SQS message can contain for this queue. | null | false | MEDIUM
-| *camel.source.endpoint.messageRetentionPeriod* | The messageRetentionPeriod (in seconds) a message will be retained by SQS for this queue. | null | false | MEDIUM
-| *camel.source.endpoint.policy* | The policy for this queue. It can be loaded by default from classpath, but you can prefix with classpath:, file:, or http: to load the resource from different systems. | null | false | MEDIUM
-| *camel.source.endpoint.receiveMessageWaitTime Seconds* | If you do not specify WaitTimeSeconds in the request, the queue attribute ReceiveMessageWaitTimeSeconds is used to determine how long to wait. | null | false | MEDIUM
-| *camel.source.endpoint.redrivePolicy* | Specify the policy that send message to DeadLetter queue. See detail at Amazon docs. | null | false | MEDIUM
-| *camel.source.endpoint.backoffErrorThreshold* | The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in. | null | false | MEDIUM
-| *camel.source.endpoint.backoffIdleThreshold* | The number of subsequent idle polls that should happen before the backoffMultipler should kick-in. | null | false | MEDIUM
-| *camel.source.endpoint.backoffMultiplier* | To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured. | null | false | MEDIUM
-| *camel.source.endpoint.delay* | Milliseconds before the next poll. | 500L | false | MEDIUM
-| *camel.source.endpoint.greedy* | If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages. | false | false | MEDIUM
-| *camel.source.endpoint.initialDelay* | Milliseconds before the first poll starts. | 1000L | false | MEDIUM
-| *camel.source.endpoint.repeatCount* | Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever. | 0L | false | MEDIUM
-| *camel.source.endpoint.runLoggingLevel* | The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that. One of: [TRACE] [DEBUG] [INFO] [WARN] [ERROR] [OFF] | "TRACE" | false | MEDIUM
-| *camel.source.endpoint.scheduledExecutorService* | Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool. | null | false | MEDIUM
-| *camel.source.endpoint.scheduler* | To use a cron scheduler from either camel-spring or camel-quartz component. Use value spring or quartz for built in scheduler | "none" | false | MEDIUM
-| *camel.source.endpoint.schedulerProperties* | To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler. | null | false | MEDIUM
-| *camel.source.endpoint.startScheduler* | Whether the scheduler should be auto started. | true | false | MEDIUM
-| *camel.source.endpoint.timeUnit* | Time unit for initialDelay and delay options. One of: [NANOSECONDS] [MICROSECONDS] [MILLISECONDS] [SECONDS] [MINUTES] [HOURS] [DAYS] | "MILLISECONDS" | false | MEDIUM
-| *camel.source.endpoint.useFixedDelay* | Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details. | true | false | MEDIUM
-| *camel.source.endpoint.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.source.endpoint.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-| *camel.component.aws2-sqs.amazonAWSHost* | The hostname of the Amazon AWS cloud. | "amazonaws.com" | false | MEDIUM
-| *camel.component.aws2-sqs.amazonSQSClient* | To use the AmazonSQS as client | null | false | MEDIUM
-| *camel.component.aws2-sqs.autoCreateQueue* | Setting the autocreation of the queue | false | false | MEDIUM
-| *camel.component.aws2-sqs.configuration* | The AWS SQS default configuration | null | false | MEDIUM
-| *camel.component.aws2-sqs.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.component.aws2-sqs.protocol* | The underlying protocol used to communicate with SQS | "https" | false | MEDIUM
-| *camel.component.aws2-sqs.proxyProtocol* | To define a proxy protocol when instantiating the SQS client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *camel.component.aws2-sqs.queueOwnerAWSAccountId* | Specify the queue owner aws account id when you need to connect the queue with different account owner. | null | false | MEDIUM
-| *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() | null | false | MEDIUM
-| *camel.component.aws2-sqs.trustAllCertificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.component.aws2-sqs.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.component.aws2-sqs.useDefaultCredentials 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 | false | MEDIUM
-| *camel.component.aws2-sqs.attributeNames* | A list of attribute names to receive when consuming. Multiple names can be separated by comma. | null | false | MEDIUM
-| *camel.component.aws2-sqs.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.component.aws2-sqs.concurrentConsumers* | Allows you to use multiple threads to poll the sqs queue to increase throughput | 1 | false | MEDIUM
-| *camel.component.aws2-sqs.defaultVisibilityTimeout* | The default visibility timeout (in seconds) | null | false | MEDIUM
-| *camel.component.aws2-sqs.deleteAfterRead* | Delete message from SQS after it has been read | true | false | MEDIUM
-| *camel.component.aws2-sqs.deleteIfFiltered* | Whether or not to send the DeleteMessage to the SQS queue if the exchange has property with key Sqs2Constants#SQS_DELETE_FILTERED (CamelAwsSqsDeleteFiltered) set to true. | true | false | MEDIUM
-| *camel.component.aws2-sqs.extendMessageVisibility* | 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 | false | MEDIUM
-| *camel.component.aws2-sqs.kmsDataKeyReusePeriod 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). | null | false | MEDIUM
-| *camel.component.aws2-sqs.kmsMasterKeyId* | The ID of an AWS-managed customer master key (CMK) for Amazon SQS or a custom CMK. | null | false | MEDIUM
-| *camel.component.aws2-sqs.messageAttributeNames* | A list of message attribute names to receive when consuming. Multiple names can be separated by comma. | null | false | MEDIUM
-| *camel.component.aws2-sqs.serverSideEncryption Enabled* | Define if Server Side Encryption is enabled or not on the queue | false | false | MEDIUM
-| *camel.component.aws2-sqs.visibilityTimeout* | 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. | null | false | MEDIUM
-| *camel.component.aws2-sqs.waitTimeSeconds* | 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. | null | false | MEDIUM
-| *camel.component.aws2-sqs.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.aws2-sqs.delayQueue* | Define if you want to apply delaySeconds option to the queue or on single messages | false | false | MEDIUM
-| *camel.component.aws2-sqs.queueUrl* | 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. | null | false | MEDIUM
-| *camel.component.aws2-sqs.proxyHost* | To define a proxy host when instantiating the SQS client | null | false | MEDIUM
-| *camel.component.aws2-sqs.proxyPort* | To define a proxy port when instantiating the SQS client | null | false | MEDIUM
-| *camel.component.aws2-sqs.maximumMessageSize* | The maximumMessageSize (in bytes) an SQS message can contain for this queue. | null | false | MEDIUM
-| *camel.component.aws2-sqs.messageRetentionPeriod* | The messageRetentionPeriod (in seconds) a message will be retained by SQS for this queue. | null | false | MEDIUM
-| *camel.component.aws2-sqs.policy* | The policy for this queue. It can be loaded by default from classpath, but you can prefix with classpath:, file:, or http: to load the resource from different systems. | null | false | MEDIUM
-| *camel.component.aws2-sqs.receiveMessageWaitTime Seconds* | If you do not specify WaitTimeSeconds in the request, the queue attribute ReceiveMessageWaitTimeSeconds is used to determine how long to wait. | null | false | MEDIUM
-| *camel.component.aws2-sqs.redrivePolicy* | Specify the policy that send message to DeadLetter queue. See detail at Amazon docs. | null | false | MEDIUM
-| *camel.component.aws2-sqs.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.component.aws2-sqs.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-|===
-
-
-
-The camel-aws2-sqs source connector has no converters out of the box.
-
-
-
-
-
-The camel-aws2-sqs source connector supports 1 transforms out of the box, which are listed below.
-
-
-
-[source,java]
-----
-
-org.apache.camel.kafkaconnector.aws2sqs.transformers.SQSKeySetterTransforms
-
-----
-
-
-
-The camel-aws2-sqs source connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-aws2-sts-kafka-connector/src/main/docs/camel-aws2-sts-kafka-sink-connector.adoc b/connectors/camel-aws2-sts-kafka-connector/src/main/docs/camel-aws2-sts-kafka-sink-connector.adoc
deleted file mode 100644
index 5fbd0f7..0000000
--- a/connectors/camel-aws2-sts-kafka-connector/src/main/docs/camel-aws2-sts-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,82 +0,0 @@
-// kafka-connector options: START
-[[camel-aws2-sts-kafka-connector-sink]]
-= camel-aws2-sts-kafka-connector sink configuration
-
-Connector Description: Manage AWS STS cluster instances using AWS SDK version 2.x.
-
-When using camel-aws2-sts-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-aws2-sts-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.aws2sts.CamelAws2stsSinkConnector
-----
-
-
-The camel-aws2-sts sink connector supports 31 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.label* | Logical name | null | true | HIGH
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.operation* | The operation to perform One of: [assumeRole] [getSessionToken] [getFederationToken] | "assumeRole" | true | HIGH
-| *camel.sink.endpoint.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.sink.endpoint.pojoRequest* | If we want to use a POJO request as body or not | false | false | MEDIUM
-| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the STS client | null | false | MEDIUM
-| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the STS client | null | false | MEDIUM
-| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the STS client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *camel.sink.endpoint.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" | false | MEDIUM
-| *camel.sink.endpoint.stsClient* | To use a existing configured AWS STS as client | null | false | MEDIUM
-| *camel.sink.endpoint.trustAllCertificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.sink.endpoint.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.sink.endpoint.useDefaultCredentialsProvider* | Set whether the STS client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | false | false | MEDIUM
-| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-| *camel.component.aws2-sts.configuration* | Component configuration | null | false | MEDIUM
-| *camel.component.aws2-sts.lazyStartProducer* | 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.aws2-sts.operation* | The operation to perform One of: [assumeRole] [getSessionToken] [getFederationToken] | "assumeRole" | true | HIGH
-| *camel.component.aws2-sts.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.component.aws2-sts.pojoRequest* | If we want to use a POJO request as body or not | false | false | MEDIUM
-| *camel.component.aws2-sts.proxyHost* | To define a proxy host when instantiating the STS client | null | false | MEDIUM
-| *camel.component.aws2-sts.proxyPort* | To define a proxy port when instantiating the STS client | null | false | MEDIUM
-| *camel.component.aws2-sts.proxyProtocol* | To define a proxy protocol when instantiating the STS client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *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" | false | MEDIUM
-| *camel.component.aws2-sts.stsClient* | To use a existing configured AWS STS as client | null | false | MEDIUM
-| *camel.component.aws2-sts.trustAllCertificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.component.aws2-sts.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.component.aws2-sts.useDefaultCredentials Provider* | Set whether the STS client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | false | false | MEDIUM
-| *camel.component.aws2-sts.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.aws2-sts.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.component.aws2-sts.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-|===
-
-
-
-The camel-aws2-sts sink connector has no converters out of the box.
-
-
-
-
-
-The camel-aws2-sts sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-aws2-sts sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-aws2-translate-kafka-connector/src/main/docs/camel-aws2-translate-kafka-sink-connector.adoc b/connectors/camel-aws2-translate-kafka-connector/src/main/docs/camel-aws2-translate-kafka-sink-connector.adoc
deleted file mode 100644
index 456d6d8..0000000
--- a/connectors/camel-aws2-translate-kafka-connector/src/main/docs/camel-aws2-translate-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,88 +0,0 @@
-// kafka-connector options: START
-[[camel-aws2-translate-kafka-connector-sink]]
-= camel-aws2-translate-kafka-connector sink configuration
-
-Connector Description: Translate texts using AWS Translate and AWS SDK version 2.x.
-
-When using camel-aws2-translate-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-aws2-translate-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.aws2translate.CamelAws2translateSinkConnector
-----
-
-
-The camel-aws2-translate sink connector supports 37 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.label* | Logical name | null | true | HIGH
-| *camel.sink.endpoint.autodetectSourceLanguage* | Being able to autodetect the source language | false | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.operation* | The operation to perform One of: [translateText] | "translateText" | true | HIGH
-| *camel.sink.endpoint.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.sink.endpoint.pojoRequest* | If we want to use a POJO request as body or not | false | false | MEDIUM
-| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the Translate client | null | false | MEDIUM
-| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the Translate client | null | false | MEDIUM
-| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the Translate client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *camel.sink.endpoint.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() | null | false | MEDIUM
-| *camel.sink.endpoint.sourceLanguage* | Source language to use | null | false | MEDIUM
-| *camel.sink.endpoint.targetLanguage* | Target language to use | null | false | MEDIUM
-| *camel.sink.endpoint.translateClient* | To use a existing configured AWS Translate as client | null | false | MEDIUM
-| *camel.sink.endpoint.trustAllCertificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.sink.endpoint.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.sink.endpoint.useDefaultCredentialsProvider* | Set whether the Translate client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | false | false | MEDIUM
-| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-| *camel.component.aws2-translate.autodetectSource Language* | Being able to autodetect the source language | false | false | MEDIUM
-| *camel.component.aws2-translate.configuration* | Component configuration | null | false | MEDIUM
-| *camel.component.aws2-translate.lazyStartProducer* | 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-translate.operation* | The operation to perform One of: [translateText] | "translateText" | true | HIGH
-| *camel.component.aws2-translate.overrideEndpoint* | Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option | false | false | MEDIUM
-| *camel.component.aws2-translate.pojoRequest* | If we want to use a POJO request as body or not | false | false | MEDIUM
-| *camel.component.aws2-translate.proxyHost* | To define a proxy host when instantiating the Translate client | null | false | MEDIUM
-| *camel.component.aws2-translate.proxyPort* | To define a proxy port when instantiating the Translate client | null | false | MEDIUM
-| *camel.component.aws2-translate.proxyProtocol* | To define a proxy protocol when instantiating the Translate client One of: [HTTP] [HTTPS] | "HTTPS" | false | MEDIUM
-| *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() | null | false | MEDIUM
-| *camel.component.aws2-translate.sourceLanguage* | Source language to use | null | false | MEDIUM
-| *camel.component.aws2-translate.targetLanguage* | Target language to use | null | false | MEDIUM
-| *camel.component.aws2-translate.translateClient* | To use a existing configured AWS Translate as client | null | false | MEDIUM
-| *camel.component.aws2-translate.trustAll Certificates* | If we want to trust all certificates in case of overriding the endpoint | false | false | MEDIUM
-| *camel.component.aws2-translate.uriEndpointOverride* | Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option | null | false | MEDIUM
-| *camel.component.aws2-translate.useDefault CredentialsProvider* | Set whether the Translate client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | false | false | MEDIUM
-| *camel.component.aws2-translate.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.aws2-translate.accessKey* | Amazon AWS Access Key | null | false | MEDIUM
-| *camel.component.aws2-translate.secretKey* | Amazon AWS Secret Key | null | false | MEDIUM
-|===
-
-
-
-The camel-aws2-translate sink connector has no converters out of the box.
-
-
-
-
-
-The camel-aws2-translate sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-aws2-translate sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-azure-cosmosdb-kafka-connector/src/main/docs/camel-azure-cosmosdb-kafka-sink-connector.adoc b/connectors/camel-azure-cosmosdb-kafka-connector/src/main/docs/camel-azure-cosmosdb-kafka-sink-connector.adoc
deleted file mode 100644
index 9da6714..0000000
--- a/connectors/camel-azure-cosmosdb-kafka-connector/src/main/docs/camel-azure-cosmosdb-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,95 +0,0 @@
-// kafka-connector options: START
-[[camel-azure-cosmosdb-kafka-connector-sink]]
-= camel-azure-cosmosdb-kafka-connector sink configuration
-
-Connector Description: To read and write records to the CosmosDB database on Azure cloud platform.
-
-When using camel-azure-cosmosdb-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-azure-cosmosdb-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.azurecosmosdb.CamelAzurecosmosdbSinkConnector
-----
-
-
-The camel-azure-cosmosdb sink connector supports 44 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.databaseName* | The name of the Cosmos database that component should connect to. In case you are producing data and have createDatabaseIfNotExists=true, the component will automatically auto create a Cosmos database. | null | false | MEDIUM
-| *camel.sink.path.containerName* | The name of the Cosmos container that component should connect to. In case you are producing data and have createContainerIfNotExists=true, the component will automatically auto create a Cosmos container. | null | false | MEDIUM
-| *camel.sink.endpoint.clientTelemetryEnabled* | Sets the flag to enable client telemetry which will periodically collect database operations aggregation statistics, system information like cpu/memory and send it to cosmos monitoring service, which will be helpful during debugging. DEFAULT value is false indicating this is opt in feature, by default no telemetry collection. | false | false | MEDIUM
-| *camel.sink.endpoint.connectionSharingAcrossClients Enabled* | Enables connections sharing across multiple Cosmos Clients. The default is false. When you have multiple instances of Cosmos Client in the same JVM interacting to multiple Cosmos accounts, enabling this allows connection sharing in Direct mode if possible between instances of Cosmos Client. Please note, when setting this option, the connection configuration (e.g., socket timeout config, idle timeout config) of the first ins [...]
-| *camel.sink.endpoint.consistencyLevel* | Sets the consistency levels supported for Azure Cosmos DB client operations in the Azure Cosmos DB service. The requested ConsistencyLevel must match or be weaker than that provisioned for the database account. Consistency levels by order of strength are STRONG, BOUNDED_STALENESS, SESSION and EVENTUAL. Refer to consistency level documentation for additional details: \https://docs.microsoft.com/en-us/azure/cosmos-db/consistency-levels One of: [St [...]
-| *camel.sink.endpoint.containerPartitionKeyPath* | Sets the container partition key path. | null | false | MEDIUM
-| *camel.sink.endpoint.contentResponseOnWriteEnabled* | Sets the boolean to only return the headers and status code in Cosmos DB response in case of Create, Update and Delete operations on CosmosItem. In Consumer, it is enabled by default because of the ChangeFeed in the consumer that needs this flag to be enabled and thus is shouldn't be overridden. In Producer, it advised to disable it since it reduces the network overhead | true | false | MEDIUM
-| *camel.sink.endpoint.cosmosAsyncClient* | Inject an external CosmosAsyncClient into the component which provides a client-side logical representation of the Azure Cosmos DB service. This asynchronous client is used to configure and execute requests against the service. | null | false | MEDIUM
-| *camel.sink.endpoint.createContainerIfNotExists* | Sets if the component should create Cosmos container automatically in case it doesn't exist in Cosmos database | false | false | MEDIUM
-| *camel.sink.endpoint.createDatabaseIfNotExists* | Sets if the component should create Cosmos database automatically in case it doesn't exist in Cosmos account | false | false | MEDIUM
-| *camel.sink.endpoint.databaseEndpoint* | Sets the Azure Cosmos database endpoint the component will connect to. | null | true | HIGH
-| *camel.sink.endpoint.multipleWriteRegionsEnabled* | Sets the flag to enable writes on any regions for geo-replicated database accounts in the Azure Cosmos DB service. When the value of this property is true, the SDK will direct write operations to available writable regions of geo-replicated database account. Writable regions are ordered by PreferredRegions property. Setting the property value to true has no effect until EnableMultipleWriteRegions in DatabaseAccount is also set to true [...]
-| *camel.sink.endpoint.preferredRegions* | Sets the preferred regions for geo-replicated database accounts. For example, East US as the preferred region. When EnableEndpointDiscovery is true and PreferredRegions is non-empty, the SDK will prefer to use the regions in the container in the order they are specified to perform operations. | null | false | MEDIUM
-| *camel.sink.endpoint.readRequestsFallbackEnabled* | Sets whether to allow for reads to go to multiple regions configured on an account of Azure Cosmos DB service. DEFAULT value is true. If this property is not set, the default is true for all Consistency Levels other than Bounded Staleness, The default is false for Bounded Staleness. 1. endpointDiscoveryEnabled is true 2. the Azure Cosmos DB account has more than one region | true | false | MEDIUM
-| *camel.sink.endpoint.throughputProperties* | Sets throughput of the resources in the Azure Cosmos DB service. | null | false | MEDIUM
-| *camel.sink.endpoint.itemId* | Sets the itemId in case needed for operation on item like delete, replace | null | false | MEDIUM
-| *camel.sink.endpoint.itemPartitionKey* | Sets partition key. Represents a partition key value in the Azure Cosmos DB database service. A partition key identifies the partition where the item is stored in. | null | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.operation* | The CosmosDB operation that can be used with this component on the producer. One of: [listDatabases] [createDatabase] [queryDatabases] [deleteDatabase] [createContainer] [replaceDatabaseThroughput] [listContainers] [queryContainers] [deleteContainer] [replaceContainerThroughput] [createItem] [upsertItem] [deleteItem] [replaceItem] [readItem] [readAllItems] [queryItems] | "listDatabases" | false | MEDIUM
-| *camel.sink.endpoint.query* | An SQL query to execute on a given resources. To learn more about Cosmos SQL API, check this link {link \https://docs.microsoft.com/en-us/azure/cosmos-db/sql-query-getting-started} | null | false | MEDIUM
-| *camel.sink.endpoint.queryRequestOptions* | Set additional QueryRequestOptions that can be used with queryItems, queryContainers, queryDatabases, listDatabases, listItems, listContainers operations | null | false | MEDIUM
-| *camel.sink.endpoint.accountKey* | Sets either a master or readonly key used to perform authentication for accessing resource. | null | true | HIGH
-| *camel.component.azure-cosmosdb.clientTelemetry Enabled* | Sets the flag to enable client telemetry which will periodically collect database operations aggregation statistics, system information like cpu/memory and send it to cosmos monitoring service, which will be helpful during debugging. DEFAULT value is false indicating this is opt in feature, by default no telemetry collection. | false | false | MEDIUM
-| *camel.component.azure-cosmosdb.configuration* | The component configurations | null | false | MEDIUM
-| *camel.component.azure-cosmosdb.connectionSharing AcrossClientsEnabled* | Enables connections sharing across multiple Cosmos Clients. The default is false. When you have multiple instances of Cosmos Client in the same JVM interacting to multiple Cosmos accounts, enabling this allows connection sharing in Direct mode if possible between instances of Cosmos Client. Please note, when setting this option, the connection configuration (e.g., socket timeout config, idle timeout config) of th [...]
-| *camel.component.azure-cosmosdb.consistencyLevel* | Sets the consistency levels supported for Azure Cosmos DB client operations in the Azure Cosmos DB service. The requested ConsistencyLevel must match or be weaker than that provisioned for the database account. Consistency levels by order of strength are STRONG, BOUNDED_STALENESS, SESSION and EVENTUAL. Refer to consistency level documentation for additional details: \https://docs.microsoft.com/en-us/azure/cosmos-db/consistency-levels [...]
-| *camel.component.azure-cosmosdb.containerPartition KeyPath* | Sets the container partition key path. | null | false | MEDIUM
-| *camel.component.azure-cosmosdb.contentResponseOn WriteEnabled* | Sets the boolean to only return the headers and status code in Cosmos DB response in case of Create, Update and Delete operations on CosmosItem. In Consumer, it is enabled by default because of the ChangeFeed in the consumer that needs this flag to be enabled and thus is shouldn't be overridden. In Producer, it advised to disable it since it reduces the network overhead | true | false | MEDIUM
-| *camel.component.azure-cosmosdb.cosmosAsyncClient* | Inject an external CosmosAsyncClient into the component which provides a client-side logical representation of the Azure Cosmos DB service. This asynchronous client is used to configure and execute requests against the service. | null | false | MEDIUM
-| *camel.component.azure-cosmosdb.createContainerIf NotExists* | Sets if the component should create Cosmos container automatically in case it doesn't exist in Cosmos database | false | false | MEDIUM
-| *camel.component.azure-cosmosdb.createDatabaseIfNot Exists* | Sets if the component should create Cosmos database automatically in case it doesn't exist in Cosmos account | false | false | MEDIUM
-| *camel.component.azure-cosmosdb.databaseEndpoint* | Sets the Azure Cosmos database endpoint the component will connect to. | null | true | HIGH
-| *camel.component.azure-cosmosdb.multipleWrite RegionsEnabled* | Sets the flag to enable writes on any regions for geo-replicated database accounts in the Azure Cosmos DB service. When the value of this property is true, the SDK will direct write operations to available writable regions of geo-replicated database account. Writable regions are ordered by PreferredRegions property. Setting the property value to true has no effect until EnableMultipleWriteRegions in DatabaseAccount is also [...]
-| *camel.component.azure-cosmosdb.preferredRegions* | Sets the preferred regions for geo-replicated database accounts. For example, East US as the preferred region. When EnableEndpointDiscovery is true and PreferredRegions is non-empty, the SDK will prefer to use the regions in the container in the order they are specified to perform operations. | null | false | MEDIUM
-| *camel.component.azure-cosmosdb.readRequests FallbackEnabled* | Sets whether to allow for reads to go to multiple regions configured on an account of Azure Cosmos DB service. DEFAULT value is true. If this property is not set, the default is true for all Consistency Levels other than Bounded Staleness, The default is false for Bounded Staleness. 1. endpointDiscoveryEnabled is true 2. the Azure Cosmos DB account has more than one region | true | false | MEDIUM
-| *camel.component.azure-cosmosdb.throughput Properties* | Sets throughput of the resources in the Azure Cosmos DB service. | null | false | MEDIUM
-| *camel.component.azure-cosmosdb.itemId* | Sets the itemId in case needed for operation on item like delete, replace | null | false | MEDIUM
-| *camel.component.azure-cosmosdb.itemPartitionKey* | Sets partition key. Represents a partition key value in the Azure Cosmos DB database service. A partition key identifies the partition where the item is stored in. | null | false | MEDIUM
-| *camel.component.azure-cosmosdb.lazyStartProducer* | 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.azure-cosmosdb.operation* | The CosmosDB operation that can be used with this component on the producer. One of: [listDatabases] [createDatabase] [queryDatabases] [deleteDatabase] [createContainer] [replaceDatabaseThroughput] [listContainers] [queryContainers] [deleteContainer] [replaceContainerThroughput] [createItem] [upsertItem] [deleteItem] [replaceItem] [readItem] [readAllItems] [queryItems] | "listDatabases" | false | MEDIUM
-| *camel.component.azure-cosmosdb.query* | An SQL query to execute on a given resources. To learn more about Cosmos SQL API, check this link {link \https://docs.microsoft.com/en-us/azure/cosmos-db/sql-query-getting-started} | null | false | MEDIUM
-| *camel.component.azure-cosmosdb.queryRequestOptions* | Set additional QueryRequestOptions that can be used with queryItems, queryContainers, queryDatabases, listDatabases, listItems, listContainers operations | null | false | MEDIUM
-| *camel.component.azure-cosmosdb.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.azure-cosmosdb.accountKey* | Sets either a master or readonly key used to perform authentication for accessing resource. | null | true | HIGH
-|===
-
-
-
-The camel-azure-cosmosdb sink connector has no converters out of the box.
-
-
-
-
-
-The camel-azure-cosmosdb sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-azure-cosmosdb sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-azure-cosmosdb-kafka-connector/src/main/docs/camel-azure-cosmosdb-kafka-source-connector.adoc b/connectors/camel-azure-cosmosdb-kafka-connector/src/main/docs/camel-azure-cosmosdb-kafka-source-connector.adoc
deleted file mode 100644
index 8490e9f..0000000
--- a/connectors/camel-azure-cosmosdb-kafka-connector/src/main/docs/camel-azure-cosmosdb-kafka-source-connector.adoc
+++ /dev/null
@@ -1,99 +0,0 @@
-// kafka-connector options: START
-[[camel-azure-cosmosdb-kafka-connector-source]]
-= camel-azure-cosmosdb-kafka-connector source configuration
-
-Connector description: To read and write records to the CosmosDB database on Azure cloud platform.
-
-When using camel-azure-cosmosdb-kafka-connector as source make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-azure-cosmosdb-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Source connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.azurecosmosdb.CamelAzurecosmosdbSourceConnector
-----
-
-
-The camel-azure-cosmosdb source connector supports 48 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.source.path.databaseName* | The name of the Cosmos database that component should connect to. In case you are producing data and have createDatabaseIfNotExists=true, the component will automatically auto create a Cosmos database. | null | false | MEDIUM
-| *camel.source.path.containerName* | The name of the Cosmos container that component should connect to. In case you are producing data and have createContainerIfNotExists=true, the component will automatically auto create a Cosmos container. | null | false | MEDIUM
-| *camel.source.endpoint.clientTelemetryEnabled* | Sets the flag to enable client telemetry which will periodically collect database operations aggregation statistics, system information like cpu/memory and send it to cosmos monitoring service, which will be helpful during debugging. DEFAULT value is false indicating this is opt in feature, by default no telemetry collection. | false | false | MEDIUM
-| *camel.source.endpoint.connectionSharingAcross ClientsEnabled* | Enables connections sharing across multiple Cosmos Clients. The default is false. When you have multiple instances of Cosmos Client in the same JVM interacting to multiple Cosmos accounts, enabling this allows connection sharing in Direct mode if possible between instances of Cosmos Client. Please note, when setting this option, the connection configuration (e.g., socket timeout config, idle timeout config) of the first i [...]
-| *camel.source.endpoint.consistencyLevel* | Sets the consistency levels supported for Azure Cosmos DB client operations in the Azure Cosmos DB service. The requested ConsistencyLevel must match or be weaker than that provisioned for the database account. Consistency levels by order of strength are STRONG, BOUNDED_STALENESS, SESSION and EVENTUAL. Refer to consistency level documentation for additional details: \https://docs.microsoft.com/en-us/azure/cosmos-db/consistency-levels One of: [ [...]
-| *camel.source.endpoint.containerPartitionKeyPath* | Sets the container partition key path. | null | false | MEDIUM
-| *camel.source.endpoint.contentResponseOnWrite Enabled* | Sets the boolean to only return the headers and status code in Cosmos DB response in case of Create, Update and Delete operations on CosmosItem. In Consumer, it is enabled by default because of the ChangeFeed in the consumer that needs this flag to be enabled and thus is shouldn't be overridden. In Producer, it advised to disable it since it reduces the network overhead | true | false | MEDIUM
-| *camel.source.endpoint.cosmosAsyncClient* | Inject an external CosmosAsyncClient into the component which provides a client-side logical representation of the Azure Cosmos DB service. This asynchronous client is used to configure and execute requests against the service. | null | false | MEDIUM
-| *camel.source.endpoint.createContainerIfNotExists* | Sets if the component should create Cosmos container automatically in case it doesn't exist in Cosmos database | false | false | MEDIUM
-| *camel.source.endpoint.createDatabaseIfNotExists* | Sets if the component should create Cosmos database automatically in case it doesn't exist in Cosmos account | false | false | MEDIUM
-| *camel.source.endpoint.databaseEndpoint* | Sets the Azure Cosmos database endpoint the component will connect to. | null | true | HIGH
-| *camel.source.endpoint.multipleWriteRegionsEnabled* | Sets the flag to enable writes on any regions for geo-replicated database accounts in the Azure Cosmos DB service. When the value of this property is true, the SDK will direct write operations to available writable regions of geo-replicated database account. Writable regions are ordered by PreferredRegions property. Setting the property value to true has no effect until EnableMultipleWriteRegions in DatabaseAccount is also set to tr [...]
-| *camel.source.endpoint.preferredRegions* | Sets the preferred regions for geo-replicated database accounts. For example, East US as the preferred region. When EnableEndpointDiscovery is true and PreferredRegions is non-empty, the SDK will prefer to use the regions in the container in the order they are specified to perform operations. | null | false | MEDIUM
-| *camel.source.endpoint.readRequestsFallbackEnabled* | Sets whether to allow for reads to go to multiple regions configured on an account of Azure Cosmos DB service. DEFAULT value is true. If this property is not set, the default is true for all Consistency Levels other than Bounded Staleness, The default is false for Bounded Staleness. 1. endpointDiscoveryEnabled is true 2. the Azure Cosmos DB account has more than one region | true | false | MEDIUM
-| *camel.source.endpoint.throughputProperties* | Sets throughput of the resources in the Azure Cosmos DB service. | null | false | MEDIUM
-| *camel.source.endpoint.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.source.endpoint.changeFeedProcessorOptions* | Sets the ChangeFeedProcessorOptions to be used. Unless specifically set the default values that will be used are: maximum items per page or FeedResponse: 100 lease renew interval: 17 seconds lease acquire interval: 13 seconds lease expiration interval: 60 seconds feed poll delay: 5 seconds maximum scale count: unlimited | null | false | MEDIUM
-| *camel.source.endpoint.createLeaseContainerIfNot Exists* | Sets if the component should create Cosmos lease container for the consumer automatically in case it doesn't exist in Cosmos database | false | false | MEDIUM
-| *camel.source.endpoint.createLeaseDatabaseIfNot Exists* | Sets if the component should create Cosmos lease database for the consumer automatically in case it doesn't exist in Cosmos account | false | false | MEDIUM
-| *camel.source.endpoint.hostName* | Sets the hostname. The host: a host is an application instance that uses the change feed processor to listen for changes. Multiple instances with the same lease configuration can run in parallel, but each instance should have a different instance name. If not specified, this will be a generated random hostname. | null | false | MEDIUM
-| *camel.source.endpoint.leaseContainerName* | Sets the lease container which acts as a state storage and coordinates processing the change feed across multiple workers. The lease container can be stored in the same account as the monitored container or in a separate account. It will be auto created if createLeaseContainerIfNotExists is set to true. | "camel-lease" | false | MEDIUM
-| *camel.source.endpoint.leaseDatabaseName* | Sets the lease database where the leaseContainerName will be stored. If it is not specified, this component will store the lease container in the same database that is specified in databaseName. It will be auto created if createLeaseDatabaseIfNotExists is set to true. | null | false | MEDIUM
-| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | false | MEDIUM
-| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | false | MEDIUM
-| *camel.source.endpoint.accountKey* | Sets either a master or readonly key used to perform authentication for accessing resource. | null | true | HIGH
-| *camel.component.azure-cosmosdb.clientTelemetry Enabled* | Sets the flag to enable client telemetry which will periodically collect database operations aggregation statistics, system information like cpu/memory and send it to cosmos monitoring service, which will be helpful during debugging. DEFAULT value is false indicating this is opt in feature, by default no telemetry collection. | false | false | MEDIUM
-| *camel.component.azure-cosmosdb.configuration* | The component configurations | null | false | MEDIUM
-| *camel.component.azure-cosmosdb.connectionSharing AcrossClientsEnabled* | Enables connections sharing across multiple Cosmos Clients. The default is false. When you have multiple instances of Cosmos Client in the same JVM interacting to multiple Cosmos accounts, enabling this allows connection sharing in Direct mode if possible between instances of Cosmos Client. Please note, when setting this option, the connection configuration (e.g., socket timeout config, idle timeout config) of th [...]
-| *camel.component.azure-cosmosdb.consistencyLevel* | Sets the consistency levels supported for Azure Cosmos DB client operations in the Azure Cosmos DB service. The requested ConsistencyLevel must match or be weaker than that provisioned for the database account. Consistency levels by order of strength are STRONG, BOUNDED_STALENESS, SESSION and EVENTUAL. Refer to consistency level documentation for additional details: \https://docs.microsoft.com/en-us/azure/cosmos-db/consistency-levels [...]
-| *camel.component.azure-cosmosdb.containerPartition KeyPath* | Sets the container partition key path. | null | false | MEDIUM
-| *camel.component.azure-cosmosdb.contentResponseOn WriteEnabled* | Sets the boolean to only return the headers and status code in Cosmos DB response in case of Create, Update and Delete operations on CosmosItem. In Consumer, it is enabled by default because of the ChangeFeed in the consumer that needs this flag to be enabled and thus is shouldn't be overridden. In Producer, it advised to disable it since it reduces the network overhead | true | false | MEDIUM
-| *camel.component.azure-cosmosdb.cosmosAsyncClient* | Inject an external CosmosAsyncClient into the component which provides a client-side logical representation of the Azure Cosmos DB service. This asynchronous client is used to configure and execute requests against the service. | null | false | MEDIUM
-| *camel.component.azure-cosmosdb.createContainerIf NotExists* | Sets if the component should create Cosmos container automatically in case it doesn't exist in Cosmos database | false | false | MEDIUM
-| *camel.component.azure-cosmosdb.createDatabaseIfNot Exists* | Sets if the component should create Cosmos database automatically in case it doesn't exist in Cosmos account | false | false | MEDIUM
-| *camel.component.azure-cosmosdb.databaseEndpoint* | Sets the Azure Cosmos database endpoint the component will connect to. | null | true | HIGH
-| *camel.component.azure-cosmosdb.multipleWrite RegionsEnabled* | Sets the flag to enable writes on any regions for geo-replicated database accounts in the Azure Cosmos DB service. When the value of this property is true, the SDK will direct write operations to available writable regions of geo-replicated database account. Writable regions are ordered by PreferredRegions property. Setting the property value to true has no effect until EnableMultipleWriteRegions in DatabaseAccount is also [...]
-| *camel.component.azure-cosmosdb.preferredRegions* | Sets the preferred regions for geo-replicated database accounts. For example, East US as the preferred region. When EnableEndpointDiscovery is true and PreferredRegions is non-empty, the SDK will prefer to use the regions in the container in the order they are specified to perform operations. | null | false | MEDIUM
-| *camel.component.azure-cosmosdb.readRequests FallbackEnabled* | Sets whether to allow for reads to go to multiple regions configured on an account of Azure Cosmos DB service. DEFAULT value is true. If this property is not set, the default is true for all Consistency Levels other than Bounded Staleness, The default is false for Bounded Staleness. 1. endpointDiscoveryEnabled is true 2. the Azure Cosmos DB account has more than one region | true | false | MEDIUM
-| *camel.component.azure-cosmosdb.throughput Properties* | Sets throughput of the resources in the Azure Cosmos DB service. | null | false | MEDIUM
-| *camel.component.azure-cosmosdb.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.component.azure-cosmosdb.changeFeedProcessor Options* | Sets the ChangeFeedProcessorOptions to be used. Unless specifically set the default values that will be used are: maximum items per page or FeedResponse: 100 lease renew interval: 17 seconds lease acquire interval: 13 seconds lease expiration interval: 60 seconds feed poll delay: 5 seconds maximum scale count: unlimited | null | false | MEDIUM
-| *camel.component.azure-cosmosdb.createLease ContainerIfNotExists* | Sets if the component should create Cosmos lease container for the consumer automatically in case it doesn't exist in Cosmos database | false | false | MEDIUM
-| *camel.component.azure-cosmosdb.createLeaseDatabase IfNotExists* | Sets if the component should create Cosmos lease database for the consumer automatically in case it doesn't exist in Cosmos account | false | false | MEDIUM
-| *camel.component.azure-cosmosdb.hostName* | Sets the hostname. The host: a host is an application instance that uses the change feed processor to listen for changes. Multiple instances with the same lease configuration can run in parallel, but each instance should have a different instance name. If not specified, this will be a generated random hostname. | null | false | MEDIUM
-| *camel.component.azure-cosmosdb.leaseContainerName* | Sets the lease container which acts as a state storage and coordinates processing the change feed across multiple workers. The lease container can be stored in the same account as the monitored container or in a separate account. It will be auto created if createLeaseContainerIfNotExists is set to true. | "camel-lease" | false | MEDIUM
-| *camel.component.azure-cosmosdb.leaseDatabaseName* | Sets the lease database where the leaseContainerName will be stored. If it is not specified, this component will store the lease container in the same database that is specified in databaseName. It will be auto created if createLeaseDatabaseIfNotExists is set to true. | null | false | MEDIUM
-| *camel.component.azure-cosmosdb.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.azure-cosmosdb.accountKey* | Sets either a master or readonly key used to perform authentication for accessing resource. | null | true | HIGH
-|===
-
-
-
-The camel-azure-cosmosdb source connector has no converters out of the box.
-
-
-
-
-
-The camel-azure-cosmosdb source connector has no transforms out of the box.
-
-
-
-
-
-The camel-azure-cosmosdb source connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-azure-eventhubs-kafka-connector/src/main/docs/camel-azure-eventhubs-kafka-sink-connector.adoc b/connectors/camel-azure-eventhubs-kafka-connector/src/main/docs/camel-azure-eventhubs-kafka-sink-connector.adoc
deleted file mode 100644
index ee436a1..0000000
--- a/connectors/camel-azure-eventhubs-kafka-connector/src/main/docs/camel-azure-eventhubs-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,73 +0,0 @@
-// kafka-connector options: START
-[[camel-azure-eventhubs-kafka-connector-sink]]
-= camel-azure-eventhubs-kafka-connector sink configuration
-
-Connector Description: The azure-eventhubs component that integrates Azure Event Hubs using AMQP protocol. Azure EventHubs is a highly scalable publish-subscribe service that can ingest millions of events per second and stream them to multiple consumers.
-
-When using camel-azure-eventhubs-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-azure-eventhubs-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.azureeventhubs.CamelAzureeventhubsSinkConnector
-----
-
-
-The camel-azure-eventhubs sink connector supports 22 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.namespace* | EventHubs namespace created in Azure Portal | null | false | MEDIUM
-| *camel.sink.path.eventHubName* | EventHubs name under a specific namcespace | null | false | MEDIUM
-| *camel.sink.endpoint.amqpRetryOptions* | Sets the retry policy for EventHubAsyncClient. If not specified, the default retry options are used. | null | false | MEDIUM
-| *camel.sink.endpoint.amqpTransportType* | Sets the transport type by which all the communication with Azure Event Hubs occurs. Default value is AmqpTransportType#AMQP. One of: [Amqp] [AmqpWebSockets] | "AMQP" | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.partitionId* | 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. | null | false | MEDIUM
-| *camel.sink.endpoint.partitionKey* | 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 partition, but th [...]
-| *camel.sink.endpoint.producerAsyncClient* | 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. | null | false | MEDIUM
-| *camel.sink.endpoint.connectionString* | 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 | null | false | MEDIUM
-| *camel.sink.endpoint.sharedAccessKey* | The generated value for the SharedAccessName | null | false | MEDIUM
-| *camel.sink.endpoint.sharedAccessName* | The name you chose for your EventHubs SAS keys | null | false | MEDIUM
-| *camel.component.azure-eventhubs.amqpRetryOptions* | Sets the retry policy for EventHubAsyncClient. If not specified, the default retry options are used. | null | false | MEDIUM
-| *camel.component.azure-eventhubs.amqpTransportType* | Sets the transport type by which all the communication with Azure Event Hubs occurs. Default value is AmqpTransportType#AMQP. One of: [Amqp] [AmqpWebSockets] | "AMQP" | false | MEDIUM
-| *camel.component.azure-eventhubs.configuration* | The component configurations | null | false | MEDIUM
-| *camel.component.azure-eventhubs.lazyStartProducer* | 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.azure-eventhubs.partitionId* | 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. | null | false | MEDIUM
-| *camel.component.azure-eventhubs.partitionKey* | 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 parti [...]
-| *camel.component.azure-eventhubs.producerAsync 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. | null | false | MEDIUM
-| *camel.component.azure-eventhubs.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.azure-eventhubs.connectionString* | 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 | null | false | MEDIUM
-| *camel.component.azure-eventhubs.sharedAccessKey* | The generated value for the SharedAccessName | null | false | MEDIUM
-| *camel.component.azure-eventhubs.sharedAccessName* | The name you chose for your EventHubs SAS keys | null | false | MEDIUM
-|===
-
-
-
-The camel-azure-eventhubs sink connector has no converters out of the box.
-
-
-
-
-
-The camel-azure-eventhubs sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-azure-eventhubs sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-azure-eventhubs-kafka-connector/src/main/docs/camel-azure-eventhubs-kafka-source-connector.adoc b/connectors/camel-azure-eventhubs-kafka-connector/src/main/docs/camel-azure-eventhubs-kafka-source-connector.adoc
deleted file mode 100644
index ce37798..0000000
--- a/connectors/camel-azure-eventhubs-kafka-connector/src/main/docs/camel-azure-eventhubs-kafka-source-connector.adoc
+++ /dev/null
@@ -1,85 +0,0 @@
-// kafka-connector options: START
-[[camel-azure-eventhubs-kafka-connector-source]]
-= camel-azure-eventhubs-kafka-connector source configuration
-
-Connector description: The azure-eventhubs component that integrates Azure Event Hubs using AMQP protocol. Azure EventHubs is a highly scalable publish-subscribe service that can ingest millions of events per second and stream them to multiple consumers.
-
-When using camel-azure-eventhubs-kafka-connector as source make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-azure-eventhubs-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Source connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.azureeventhubs.CamelAzureeventhubsSourceConnector
-----
-
-
-The camel-azure-eventhubs source connector supports 34 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.source.path.namespace* | EventHubs namespace created in Azure Portal | null | false | MEDIUM
-| *camel.source.path.eventHubName* | EventHubs name under a specific namcespace | null | false | MEDIUM
-| *camel.source.endpoint.amqpRetryOptions* | Sets the retry policy for EventHubAsyncClient. If not specified, the default retry options are used. | null | false | MEDIUM
-| *camel.source.endpoint.amqpTransportType* | Sets the transport type by which all the communication with Azure Event Hubs occurs. Default value is AmqpTransportType#AMQP. One of: [Amqp] [AmqpWebSockets] | "AMQP" | false | MEDIUM
-| *camel.source.endpoint.blobAccessKey* | 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 | null | false | MEDIUM
-| *camel.source.endpoint.blobAccountName* | In case you chose the default BlobCheckpointStore, this sets Azure account name to be used for authentication with azure blob services. | null | false | MEDIUM
-| *camel.source.endpoint.blobContainerName* | In case you chose the default BlobCheckpointStore, this sets the blob container that shall be used by the BlobCheckpointStore to store the checkpoint offsets | null | false | MEDIUM
-| *camel.source.endpoint.blobStorageSharedKey Credential* | In case you chose the default BlobCheckpointStore, StorageSharedKeyCredential can be injected to create the azure client, this holds the important authentication information | null | false | MEDIUM
-| *camel.source.endpoint.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.source.endpoint.checkpointStore* | 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 | "BlobCheckpointStore" | false | MEDIUM
-| *camel.source.endpoint.consumerGroupName* | 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" | false | MEDIUM
-| *camel.source.endpoint.eventPosition* | 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. | null | false | MEDIUM
-| *camel.source.endpoint.prefetchCount* | 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 | false | MEDIUM
-| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | false | MEDIUM
-| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | false | MEDIUM
-| *camel.source.endpoint.connectionString* | 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 | null | false | MEDIUM
-| *camel.source.endpoint.sharedAccessKey* | The generated value for the SharedAccessName | null | false | MEDIUM
-| *camel.source.endpoint.sharedAccessName* | The name you chose for your EventHubs SAS keys | null | false | MEDIUM
-| *camel.component.azure-eventhubs.amqpRetryOptions* | Sets the retry policy for EventHubAsyncClient. If not specified, the default retry options are used. | null | false | MEDIUM
-| *camel.component.azure-eventhubs.amqpTransportType* | Sets the transport type by which all the communication with Azure Event Hubs occurs. Default value is AmqpTransportType#AMQP. One of: [Amqp] [AmqpWebSockets] | "AMQP" | false | MEDIUM
-| *camel.component.azure-eventhubs.configuration* | The component configurations | null | false | MEDIUM
-| *camel.component.azure-eventhubs.blobAccessKey* | 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 | null | false | MEDIUM
-| *camel.component.azure-eventhubs.blobAccountName* | In case you chose the default BlobCheckpointStore, this sets Azure account name to be used for authentication with azure blob services. | null | false | MEDIUM
-| *camel.component.azure-eventhubs.blobContainerName* | In case you chose the default BlobCheckpointStore, this sets the blob container that shall be used by the BlobCheckpointStore to store the checkpoint offsets | null | false | MEDIUM
-| *camel.component.azure-eventhubs.blobStorageShared KeyCredential* | In case you chose the default BlobCheckpointStore, StorageSharedKeyCredential can be injected to create the azure client, this holds the important authentication information | null | false | MEDIUM
-| *camel.component.azure-eventhubs.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.component.azure-eventhubs.checkpointStore* | 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 | "BlobCheckpointStore" | false | MEDIUM
-| *camel.component.azure-eventhubs.consumerGroupName* | 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" | false | MEDIUM
-| *camel.component.azure-eventhubs.eventPosition* | 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. | null | false | MEDIUM
-| *camel.component.azure-eventhubs.prefetchCount* | 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 | false | MEDIUM
-| *camel.component.azure-eventhubs.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.azure-eventhubs.connectionString* | 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 | null | false | MEDIUM
-| *camel.component.azure-eventhubs.sharedAccessKey* | The generated value for the SharedAccessName | null | false | MEDIUM
-| *camel.component.azure-eventhubs.sharedAccessName* | The name you chose for your EventHubs SAS keys | null | false | MEDIUM
-|===
-
-
-
-The camel-azure-eventhubs source connector has no converters out of the box.
-
-
-
-
-
-The camel-azure-eventhubs source connector has no transforms out of the box.
-
-
-
-
-
-The camel-azure-eventhubs source connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-azure-storage-blob-kafka-connector/src/main/docs/camel-azure-storage-blob-kafka-sink-connector.adoc b/connectors/camel-azure-storage-blob-kafka-connector/src/main/docs/camel-azure-storage-blob-kafka-sink-connector.adoc
deleted file mode 100644
index 7c743cd..0000000
--- a/connectors/camel-azure-storage-blob-kafka-connector/src/main/docs/camel-azure-storage-blob-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,104 +0,0 @@
-// kafka-connector options: START
-[[camel-azure-storage-blob-kafka-connector-sink]]
-= camel-azure-storage-blob-kafka-connector sink configuration
-
-Connector Description: Store and retrieve blobs from Azure Storage Blob Service using SDK v12.
-
-When using camel-azure-storage-blob-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-azure-storage-blob-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.azurestorageblob.CamelAzurestorageblobSinkConnector
-----
-
-
-The camel-azure-storage-blob sink connector supports 53 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.accountName* | Azure account name to be used for authentication with azure blob services | null | false | MEDIUM
-| *camel.sink.path.containerName* | The blob container name | null | false | MEDIUM
-| *camel.sink.endpoint.blobName* | The blob name, to consume specific blob from a container. However on producer, is only required for the operations on the blob level | null | false | MEDIUM
-| *camel.sink.endpoint.blobOffset* | Set the blob offset for the upload or download operations, default is 0 | 0L | false | MEDIUM
-| *camel.sink.endpoint.blobServiceClient* | 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 getBlobContainerClient(String), and operations on a blob are [...]
-| *camel.sink.endpoint.blobType* | The blob type in order to initiate the appropriate settings for each blob type One of: [blockblob] [appendblob] [pageblob] | "blockblob" | false | MEDIUM
-| *camel.sink.endpoint.closeStreamAfterRead* | Close the stream after read or keep it open, default is true | true | false | MEDIUM
-| *camel.sink.endpoint.credentials* | StorageSharedKeyCredential can be injected to create the azure client, this holds the important authentication information | null | false | MEDIUM
-| *camel.sink.endpoint.dataCount* | How many bytes to include in the range. Must be greater than or equal to 0 if specified. | null | false | MEDIUM
-| *camel.sink.endpoint.fileDir* | The file directory where the downloaded blobs will be saved to, this can be used in both, producer and consumer | null | false | MEDIUM
-| *camel.sink.endpoint.maxResultsPerPage* | 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. | null | false | MEDIUM
-| *camel.sink.endpoint.maxRetryRequests* | Specifies the maximum number of additional HTTP Get requests that will be made while reading the data from a response body. | 0 | false | MEDIUM
-| *camel.sink.endpoint.prefix* | Filters the results to return only blobs whose names begin with the specified prefix. May be null to return all blobs. | null | false | MEDIUM
-| *camel.sink.endpoint.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. | null | false | MEDIUM
-| *camel.sink.endpoint.serviceClient* | 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), and operations [...]
-| *camel.sink.endpoint.timeout* | An optional timeout value beyond which a RuntimeException will be raised. | null | false | MEDIUM
-| *camel.sink.endpoint.blobSequenceNumber* | 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" | false | MEDIUM
-| *camel.sink.endpoint.blockListType* | Specifies which type of blocks to return. One of: [committed] [uncommitted] [all] | "COMMITTED" | false | MEDIUM
-| *camel.sink.endpoint.closeStreamAfterWrite* | Close the stream after write or keep it open, default is true | true | false | MEDIUM
-| *camel.sink.endpoint.commitBlockListLater* | When is set to true, the staged blocks will not be committed directly. | true | false | MEDIUM
-| *camel.sink.endpoint.createAppendBlob* | When is set to true, the append blocks will be created when committing append blocks. | true | false | MEDIUM
-| *camel.sink.endpoint.createPageBlob* | When is set to true, the page blob will be created when uploading page blob. | true | false | MEDIUM
-| *camel.sink.endpoint.downloadLinkExpiration* | Override the default expiration (millis) of URL download link. | null | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.operation* | The blob operation that can be used with this component on the producer One of: [listBlobContainers] [createBlobContainer] [deleteBlobContainer] [listBlobs] [getBlob] [deleteBlob] [downloadBlobToFile] [downloadLink] [uploadBlockBlob] [stageBlockBlobList] [commitBlobBlockList] [getBlobBlockList] [createAppendBlob] [commitAppendBlob] [createPageBlob] [uploadPageBlob] [resizePageBlob] [clearPageBlob] [getPageBlobRanges] | "listBlobContainers" | false | MEDIUM
-| *camel.sink.endpoint.pageBlobSize* | 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" | false | MEDIUM
-| *camel.sink.endpoint.accessKey* | Access key for the associated azure account name to be used for authentication with azure blob services | null | false | MEDIUM
-| *camel.component.azure-storage-blob.blobName* | The blob name, to consume specific blob from a container. However on producer, is only required for the operations on the blob level | null | false | MEDIUM
-| *camel.component.azure-storage-blob.blobOffset* | Set the blob offset for the upload or download operations, default is 0 | 0L | false | MEDIUM
-| *camel.component.azure-storage-blob.blobType* | The blob type in order to initiate the appropriate settings for each blob type One of: [blockblob] [appendblob] [pageblob] | "blockblob" | false | MEDIUM
-| *camel.component.azure-storage-blob.closeStream AfterRead* | Close the stream after read or keep it open, default is true | true | false | MEDIUM
-| *camel.component.azure-storage-blob.configuration* | The component configurations | null | false | MEDIUM
-| *camel.component.azure-storage-blob.credentials* | StorageSharedKeyCredential can be injected to create the azure client, this holds the important authentication information | null | false | MEDIUM
-| *camel.component.azure-storage-blob.dataCount* | How many bytes to include in the range. Must be greater than or equal to 0 if specified. | null | false | MEDIUM
-| *camel.component.azure-storage-blob.fileDir* | The file directory where the downloaded blobs will be saved to, this can be used in both, producer and consumer | null | false | MEDIUM
-| *camel.component.azure-storage-blob.maxResultsPer 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. | null | false | MEDIUM
-| *camel.component.azure-storage-blob.maxRetry Requests* | Specifies the maximum number of additional HTTP Get requests that will be made while reading the data from a response body. | 0 | false | MEDIUM
-| *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. | null | false | MEDIUM
-| *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. | null | false | MEDIUM
-| *camel.component.azure-storage-blob.serviceClient* | 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. | null | false | MEDIUM
-| *camel.component.azure-storage-blob.blobSequence 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" | false | MEDIUM
-| *camel.component.azure-storage-blob.blockListType* | Specifies which type of blocks to return. One of: [committed] [uncommitted] [all] | "COMMITTED" | false | MEDIUM
-| *camel.component.azure-storage-blob.closeStream AfterWrite* | Close the stream after write or keep it open, default is true | true | false | MEDIUM
-| *camel.component.azure-storage-blob.commitBlockList Later* | When is set to true, the staged blocks will not be committed directly. | true | false | MEDIUM
-| *camel.component.azure-storage-blob.createAppend Blob* | When is set to true, the append blocks will be created when committing append blocks. | true | false | MEDIUM
-| *camel.component.azure-storage-blob.createPageBlob* | When is set to true, the page blob will be created when uploading page blob. | true | false | MEDIUM
-| *camel.component.azure-storage-blob.downloadLink Expiration* | Override the default expiration (millis) of URL download link. | null | false | MEDIUM
-| *camel.component.azure-storage-blob.lazyStart 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 pr [...]
-| *camel.component.azure-storage-blob.operation* | The blob operation that can be used with this component on the producer One of: [listBlobContainers] [createBlobContainer] [deleteBlobContainer] [listBlobs] [getBlob] [deleteBlob] [downloadBlobToFile] [downloadLink] [uploadBlockBlob] [stageBlockBlobList] [commitBlobBlockList] [getBlobBlockList] [createAppendBlob] [commitAppendBlob] [createPageBlob] [uploadPageBlob] [resizePageBlob] [clearPageBlob] [getPageBlobRanges] | "listBlobContainer [...]
-| *camel.component.azure-storage-blob.pageBlobSize* | 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" | false | MEDIUM
-| *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 | false | MEDIUM
-| *camel.component.azure-storage-blob.accessKey* | Access key for the associated azure account name to be used for authentication with azure blob services | null | false | MEDIUM
-|===
-
-
-
-The camel-azure-storage-blob sink connector has no converters out of the box.
-
-
-
-
-
-The camel-azure-storage-blob sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-azure-storage-blob sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-azure-storage-blob-kafka-connector/src/main/docs/camel-azure-storage-blob-kafka-source-connector.adoc b/connectors/camel-azure-storage-blob-kafka-connector/src/main/docs/camel-azure-storage-blob-kafka-source-connector.adoc
deleted file mode 100644
index dc0f020..0000000
--- a/connectors/camel-azure-storage-blob-kafka-connector/src/main/docs/camel-azure-storage-blob-kafka-source-connector.adoc
+++ /dev/null
@@ -1,104 +0,0 @@
-// kafka-connector options: START
-[[camel-azure-storage-blob-kafka-connector-source]]
-= camel-azure-storage-blob-kafka-connector source configuration
-
-Connector description: Store and retrieve blobs from Azure Storage Blob Service using SDK v12.
-
-When using camel-azure-storage-blob-kafka-connector as source make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-azure-storage-blob-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Source connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.azurestorageblob.CamelAzurestorageblobSourceConnector
-----
-
-
-The camel-azure-storage-blob source connector supports 53 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.source.path.accountName* | Azure account name to be used for authentication with azure blob services | null | false | MEDIUM
-| *camel.source.path.containerName* | The blob container name | null | false | MEDIUM
-| *camel.source.endpoint.blobName* | The blob name, to consume specific blob from a container. However on producer, is only required for the operations on the blob level | null | false | MEDIUM
-| *camel.source.endpoint.blobOffset* | Set the blob offset for the upload or download operations, default is 0 | 0L | false | MEDIUM
-| *camel.source.endpoint.blobServiceClient* | 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 getBlobContainerClient(String), and operations on a blob a [...]
-| *camel.source.endpoint.blobType* | The blob type in order to initiate the appropriate settings for each blob type One of: [blockblob] [appendblob] [pageblob] | "blockblob" | false | MEDIUM
-| *camel.source.endpoint.closeStreamAfterRead* | Close the stream after read or keep it open, default is true | true | false | MEDIUM
-| *camel.source.endpoint.credentials* | StorageSharedKeyCredential can be injected to create the azure client, this holds the important authentication information | null | false | MEDIUM
-| *camel.source.endpoint.dataCount* | How many bytes to include in the range. Must be greater than or equal to 0 if specified. | null | false | MEDIUM
-| *camel.source.endpoint.fileDir* | The file directory where the downloaded blobs will be saved to, this can be used in both, producer and consumer | null | false | MEDIUM
-| *camel.source.endpoint.maxResultsPerPage* | 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. | null | false | MEDIUM
-| *camel.source.endpoint.maxRetryRequests* | Specifies the maximum number of additional HTTP Get requests that will be made while reading the data from a response body. | 0 | false | MEDIUM
-| *camel.source.endpoint.prefix* | Filters the results to return only blobs whose names begin with the specified prefix. May be null to return all blobs. | null | false | MEDIUM
-| *camel.source.endpoint.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. | null | false | MEDIUM
-| *camel.source.endpoint.serviceClient* | 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), and operatio [...]
-| *camel.source.endpoint.timeout* | An optional timeout value beyond which a RuntimeException will be raised. | null | false | MEDIUM
-| *camel.source.endpoint.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.source.endpoint.sendEmptyMessageWhenIdle* | If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead. | false | false | MEDIUM
-| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | false | MEDIUM
-| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | false | MEDIUM
-| *camel.source.endpoint.pollStrategy* | A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel. | null | false | MEDIUM
-| *camel.source.endpoint.backoffErrorThreshold* | The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in. | null | false | MEDIUM
-| *camel.source.endpoint.backoffIdleThreshold* | The number of subsequent idle polls that should happen before the backoffMultipler should kick-in. | null | false | MEDIUM
-| *camel.source.endpoint.backoffMultiplier* | To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured. | null | false | MEDIUM
-| *camel.source.endpoint.delay* | Milliseconds before the next poll. | 500L | false | MEDIUM
-| *camel.source.endpoint.greedy* | If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages. | false | false | MEDIUM
-| *camel.source.endpoint.initialDelay* | Milliseconds before the first poll starts. | 1000L | false | MEDIUM
-| *camel.source.endpoint.repeatCount* | Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever. | 0L | false | MEDIUM
-| *camel.source.endpoint.runLoggingLevel* | The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that. One of: [TRACE] [DEBUG] [INFO] [WARN] [ERROR] [OFF] | "TRACE" | false | MEDIUM
-| *camel.source.endpoint.scheduledExecutorService* | Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool. | null | false | MEDIUM
-| *camel.source.endpoint.scheduler* | To use a cron scheduler from either camel-spring or camel-quartz component. Use value spring or quartz for built in scheduler | "none" | false | MEDIUM
-| *camel.source.endpoint.schedulerProperties* | To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler. | null | false | MEDIUM
-| *camel.source.endpoint.startScheduler* | Whether the scheduler should be auto started. | true | false | MEDIUM
-| *camel.source.endpoint.timeUnit* | Time unit for initialDelay and delay options. One of: [NANOSECONDS] [MICROSECONDS] [MILLISECONDS] [SECONDS] [MINUTES] [HOURS] [DAYS] | "MILLISECONDS" | false | MEDIUM
-| *camel.source.endpoint.useFixedDelay* | Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details. | true | false | MEDIUM
-| *camel.source.endpoint.accessKey* | Access key for the associated azure account name to be used for authentication with azure blob services | null | false | MEDIUM
-| *camel.component.azure-storage-blob.blobName* | The blob name, to consume specific blob from a container. However on producer, is only required for the operations on the blob level | null | false | MEDIUM
-| *camel.component.azure-storage-blob.blobOffset* | Set the blob offset for the upload or download operations, default is 0 | 0L | false | MEDIUM
-| *camel.component.azure-storage-blob.blobType* | The blob type in order to initiate the appropriate settings for each blob type One of: [blockblob] [appendblob] [pageblob] | "blockblob" | false | MEDIUM
-| *camel.component.azure-storage-blob.closeStream AfterRead* | Close the stream after read or keep it open, default is true | true | false | MEDIUM
-| *camel.component.azure-storage-blob.configuration* | The component configurations | null | false | MEDIUM
-| *camel.component.azure-storage-blob.credentials* | StorageSharedKeyCredential can be injected to create the azure client, this holds the important authentication information | null | false | MEDIUM
-| *camel.component.azure-storage-blob.dataCount* | How many bytes to include in the range. Must be greater than or equal to 0 if specified. | null | false | MEDIUM
-| *camel.component.azure-storage-blob.fileDir* | The file directory where the downloaded blobs will be saved to, this can be used in both, producer and consumer | null | false | MEDIUM
-| *camel.component.azure-storage-blob.maxResultsPer 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. | null | false | MEDIUM
-| *camel.component.azure-storage-blob.maxRetry Requests* | Specifies the maximum number of additional HTTP Get requests that will be made while reading the data from a response body. | 0 | false | MEDIUM
-| *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. | null | false | MEDIUM
-| *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. | null | false | MEDIUM
-| *camel.component.azure-storage-blob.serviceClient* | 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. | null | false | MEDIUM
-| *camel.component.azure-storage-blob.bridgeError 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 | false | MEDIUM
-| *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 | false | MEDIUM
-| *camel.component.azure-storage-blob.accessKey* | Access key for the associated azure account name to be used for authentication with azure blob services | null | false | MEDIUM
-|===
-
-
-
-The camel-azure-storage-blob source connector has no converters out of the box.
-
-
-
-
-
-The camel-azure-storage-blob source connector has no transforms out of the box.
-
-
-
-
-
-The camel-azure-storage-blob source connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-azure-storage-datalake-kafka-connector/src/main/docs/camel-azure-storage-datalake-kafka-sink-connector.adoc b/connectors/camel-azure-storage-datalake-kafka-connector/src/main/docs/camel-azure-storage-datalake-kafka-sink-connector.adoc
deleted file mode 100644
index 7f9b684..0000000
--- a/connectors/camel-azure-storage-datalake-kafka-connector/src/main/docs/camel-azure-storage-datalake-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,116 +0,0 @@
-// kafka-connector options: START
-[[camel-azure-storage-datalake-kafka-connector-sink]]
-= camel-azure-storage-datalake-kafka-connector sink configuration
-
-Connector Description: Camel Azure Datalake Gen2 Component
-
-When using camel-azure-storage-datalake-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-azure-storage-datalake-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.azurestoragedatalake.CamelAzurestoragedatalakeSinkConnector
-----
-
-
-The camel-azure-storage-datalake sink connector supports 65 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.accountName* | name of the azure account | null | false | MEDIUM
-| *camel.sink.path.fileSystemName* | name of filesystem to be used | null | false | MEDIUM
-| *camel.sink.endpoint.accountKey* | account key for authentication | null | false | MEDIUM
-| *camel.sink.endpoint.clientId* | client id for azure account | null | false | MEDIUM
-| *camel.sink.endpoint.clientSecret* | client secret for azure account | null | false | MEDIUM
-| *camel.sink.endpoint.clientSecretCredential* | client secret credential for authentication | null | false | MEDIUM
-| *camel.sink.endpoint.close* | Whether or not a file changed event raised indicates completion (true) or modification (false) | null | false | MEDIUM
-| *camel.sink.endpoint.closeStreamAfterRead* | check for closing stream after read | null | false | MEDIUM
-| *camel.sink.endpoint.dataCount* | count number of bytes to download | null | false | MEDIUM
-| *camel.sink.endpoint.dataLakeServiceClient* | service client of datalake | null | false | MEDIUM
-| *camel.sink.endpoint.directoryName* | directory of the file to be handled in component | null | false | MEDIUM
-| *camel.sink.endpoint.downloadLinkExpiration* | download link expiration time | null | false | MEDIUM
-| *camel.sink.endpoint.expression* | expression for queryInputStream | null | false | MEDIUM
-| *camel.sink.endpoint.fileDir* | directory of file to do operations in the local system | null | false | MEDIUM
-| *camel.sink.endpoint.fileName* | name of file to be handled in component | null | false | MEDIUM
-| *camel.sink.endpoint.fileOffset* | offset position in file for different operations | null | false | MEDIUM
-| *camel.sink.endpoint.maxResults* | maximum number of results to show at a time | null | false | MEDIUM
-| *camel.sink.endpoint.maxRetryRequests* | no of retries to a given request | null | false | MEDIUM
-| *camel.sink.endpoint.openOptions* | set open options for creating file | null | false | MEDIUM
-| *camel.sink.endpoint.path* | path in azure datalake for operations | null | false | MEDIUM
-| *camel.sink.endpoint.permission* | permission string for the file | null | false | MEDIUM
-| *camel.sink.endpoint.position* | This parameter allows the caller to upload data in parallel and control the order in which it is appended to the file. | null | false | MEDIUM
-| *camel.sink.endpoint.recursive* | recursively include all paths | null | false | MEDIUM
-| *camel.sink.endpoint.regex* | regular expression for matching file names | null | false | MEDIUM
-| *camel.sink.endpoint.retainUncommitedData* | Whether or not uncommitted data is to be retained after the operation | null | false | MEDIUM
-| *camel.sink.endpoint.serviceClient* | datalake service client for azure storage datalake | null | false | MEDIUM
-| *camel.sink.endpoint.sharedKeyCredential* | shared key credential for azure datalake gen2 | null | false | MEDIUM
-| *camel.sink.endpoint.tenantId* | tenant id for azure account | null | false | MEDIUM
-| *camel.sink.endpoint.timeout* | Timeout for operation | null | false | MEDIUM
-| *camel.sink.endpoint.umask* | umask permission for file | null | false | MEDIUM
-| *camel.sink.endpoint.userPrincipalNameReturned* | whether or not to use upn | null | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.operation* | operation to be performed One of: [listFileSystem] [listFiles] | "listFileSystem" | false | MEDIUM
-| *camel.component.azure-storage-datalake.accountKey* | account key for authentication | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.clientId* | client id for azure account | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.client Secret* | client secret for azure account | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.client SecretCredential* | client secret credential for authentication | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.close* | Whether or not a file changed event raised indicates completion (true) or modification (false) | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.closeStream AfterRead* | check for closing stream after read | null | false | MEDIUM
-| * camel.component.azure-storage-datalake.configuration* | configuration object for datalake | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.dataCount* | count number of bytes to download | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.directory Name* | directory of the file to be handled in component | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.download LinkExpiration* | download link expiration time | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.expression* | expression for queryInputStream | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.fileDir* | directory of file to do operations in the local system | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.fileName* | name of file to be handled in component | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.fileOffset* | offset position in file for different operations | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.maxResults* | maximum number of results to show at a time | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.maxRetry Requests* | no of retries to a given request | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.openOptions* | set open options for creating file | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.path* | path in azure datalake for operations | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.permission* | permission string for the file | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.position* | This parameter allows the caller to upload data in parallel and control the order in which it is appended to the file. | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.recursive* | recursively include all paths | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.regex* | regular expression for matching file names | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.retain UncommitedData* | Whether or not uncommitted data is to be retained after the operation | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.service Client* | datalake service client for azure storage datalake | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.sharedKey Credential* | shared key credential for azure datalake gen2 | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.tenantId* | tenant id for azure account | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.timeout* | Timeout for operation | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.umask* | umask permission for file | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.user PrincipalNameReturned* | whether or not to use upn | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.lazyStart 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.azure-storage-datalake.operation* | operation to be performed One of: [listFileSystem] [listFiles] | "listFileSystem" | false | MEDIUM
-| *camel.component.azure-storage-datalake.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 | false | MEDIUM
-|===
-
-
-
-The camel-azure-storage-datalake sink connector has no converters out of the box.
-
-
-
-
-
-The camel-azure-storage-datalake sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-azure-storage-datalake sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-azure-storage-datalake-kafka-connector/src/main/docs/camel-azure-storage-datalake-kafka-source-connector.adoc b/connectors/camel-azure-storage-datalake-kafka-connector/src/main/docs/camel-azure-storage-datalake-kafka-source-connector.adoc
deleted file mode 100644
index edfb45f..0000000
--- a/connectors/camel-azure-storage-datalake-kafka-connector/src/main/docs/camel-azure-storage-datalake-kafka-source-connector.adoc
+++ /dev/null
@@ -1,132 +0,0 @@
-// kafka-connector options: START
-[[camel-azure-storage-datalake-kafka-connector-source]]
-= camel-azure-storage-datalake-kafka-connector source configuration
-
-Connector description: Camel Azure Datalake Gen2 Component
-
-When using camel-azure-storage-datalake-kafka-connector as source make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-azure-storage-datalake-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Source connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.azurestoragedatalake.CamelAzurestoragedatalakeSourceConnector
-----
-
-
-The camel-azure-storage-datalake source connector supports 81 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.source.path.accountName* | name of the azure account | null | false | MEDIUM
-| *camel.source.path.fileSystemName* | name of filesystem to be used | null | false | MEDIUM
-| *camel.source.endpoint.accountKey* | account key for authentication | null | false | MEDIUM
-| *camel.source.endpoint.clientId* | client id for azure account | null | false | MEDIUM
-| *camel.source.endpoint.clientSecret* | client secret for azure account | null | false | MEDIUM
-| *camel.source.endpoint.clientSecretCredential* | client secret credential for authentication | null | false | MEDIUM
-| *camel.source.endpoint.close* | Whether or not a file changed event raised indicates completion (true) or modification (false) | null | false | MEDIUM
-| *camel.source.endpoint.closeStreamAfterRead* | check for closing stream after read | null | false | MEDIUM
-| *camel.source.endpoint.dataCount* | count number of bytes to download | null | false | MEDIUM
-| *camel.source.endpoint.dataLakeServiceClient* | service client of datalake | null | false | MEDIUM
-| *camel.source.endpoint.directoryName* | directory of the file to be handled in component | null | false | MEDIUM
-| *camel.source.endpoint.downloadLinkExpiration* | download link expiration time | null | false | MEDIUM
-| *camel.source.endpoint.expression* | expression for queryInputStream | null | false | MEDIUM
-| *camel.source.endpoint.fileDir* | directory of file to do operations in the local system | null | false | MEDIUM
-| *camel.source.endpoint.fileName* | name of file to be handled in component | null | false | MEDIUM
-| *camel.source.endpoint.fileOffset* | offset position in file for different operations | null | false | MEDIUM
-| *camel.source.endpoint.maxResults* | maximum number of results to show at a time | null | false | MEDIUM
-| *camel.source.endpoint.maxRetryRequests* | no of retries to a given request | null | false | MEDIUM
-| *camel.source.endpoint.openOptions* | set open options for creating file | null | false | MEDIUM
-| *camel.source.endpoint.path* | path in azure datalake for operations | null | false | MEDIUM
-| *camel.source.endpoint.permission* | permission string for the file | null | false | MEDIUM
-| *camel.source.endpoint.position* | This parameter allows the caller to upload data in parallel and control the order in which it is appended to the file. | null | false | MEDIUM
-| *camel.source.endpoint.recursive* | recursively include all paths | null | false | MEDIUM
-| *camel.source.endpoint.regex* | regular expression for matching file names | null | false | MEDIUM
-| *camel.source.endpoint.retainUncommitedData* | Whether or not uncommitted data is to be retained after the operation | null | false | MEDIUM
-| *camel.source.endpoint.serviceClient* | datalake service client for azure storage datalake | null | false | MEDIUM
-| *camel.source.endpoint.sharedKeyCredential* | shared key credential for azure datalake gen2 | null | false | MEDIUM
-| *camel.source.endpoint.tenantId* | tenant id for azure account | null | false | MEDIUM
-| *camel.source.endpoint.timeout* | Timeout for operation | null | false | MEDIUM
-| *camel.source.endpoint.umask* | umask permission for file | null | false | MEDIUM
-| *camel.source.endpoint.userPrincipalNameReturned* | whether or not to use upn | null | false | MEDIUM
-| *camel.source.endpoint.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.source.endpoint.sendEmptyMessageWhenIdle* | If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead. | false | false | MEDIUM
-| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | false | MEDIUM
-| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | false | MEDIUM
-| *camel.source.endpoint.pollStrategy* | A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel. | null | false | MEDIUM
-| *camel.source.endpoint.backoffErrorThreshold* | The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in. | null | false | MEDIUM
-| *camel.source.endpoint.backoffIdleThreshold* | The number of subsequent idle polls that should happen before the backoffMultipler should kick-in. | null | false | MEDIUM
-| *camel.source.endpoint.backoffMultiplier* | To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured. | null | false | MEDIUM
-| *camel.source.endpoint.delay* | Milliseconds before the next poll. | 500L | false | MEDIUM
-| *camel.source.endpoint.greedy* | If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages. | false | false | MEDIUM
-| *camel.source.endpoint.initialDelay* | Milliseconds before the first poll starts. | 1000L | false | MEDIUM
-| *camel.source.endpoint.repeatCount* | Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever. | 0L | false | MEDIUM
-| *camel.source.endpoint.runLoggingLevel* | The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that. One of: [TRACE] [DEBUG] [INFO] [WARN] [ERROR] [OFF] | "TRACE" | false | MEDIUM
-| *camel.source.endpoint.scheduledExecutorService* | Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool. | null | false | MEDIUM
-| *camel.source.endpoint.scheduler* | To use a cron scheduler from either camel-spring or camel-quartz component. Use value spring or quartz for built in scheduler | "none" | false | MEDIUM
-| *camel.source.endpoint.schedulerProperties* | To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler. | null | false | MEDIUM
-| *camel.source.endpoint.startScheduler* | Whether the scheduler should be auto started. | true | false | MEDIUM
-| *camel.source.endpoint.timeUnit* | Time unit for initialDelay and delay options. One of: [NANOSECONDS] [MICROSECONDS] [MILLISECONDS] [SECONDS] [MINUTES] [HOURS] [DAYS] | "MILLISECONDS" | false | MEDIUM
-| *camel.source.endpoint.useFixedDelay* | Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details. | true | false | MEDIUM
-| *camel.component.azure-storage-datalake.accountKey* | account key for authentication | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.clientId* | client id for azure account | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.client Secret* | client secret for azure account | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.client SecretCredential* | client secret credential for authentication | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.close* | Whether or not a file changed event raised indicates completion (true) or modification (false) | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.closeStream AfterRead* | check for closing stream after read | null | false | MEDIUM
-| * camel.component.azure-storage-datalake.configuration* | configuration object for datalake | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.dataCount* | count number of bytes to download | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.directory Name* | directory of the file to be handled in component | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.download LinkExpiration* | download link expiration time | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.expression* | expression for queryInputStream | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.fileDir* | directory of file to do operations in the local system | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.fileName* | name of file to be handled in component | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.fileOffset* | offset position in file for different operations | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.maxResults* | maximum number of results to show at a time | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.maxRetry Requests* | no of retries to a given request | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.openOptions* | set open options for creating file | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.path* | path in azure datalake for operations | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.permission* | permission string for the file | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.position* | This parameter allows the caller to upload data in parallel and control the order in which it is appended to the file. | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.recursive* | recursively include all paths | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.regex* | regular expression for matching file names | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.retain UncommitedData* | Whether or not uncommitted data is to be retained after the operation | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.service Client* | datalake service client for azure storage datalake | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.sharedKey Credential* | shared key credential for azure datalake gen2 | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.tenantId* | tenant id for azure account | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.timeout* | Timeout for operation | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.umask* | umask permission for file | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.user PrincipalNameReturned* | whether or not to use upn | null | false | MEDIUM
-| *camel.component.azure-storage-datalake.bridgeError 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 | false | MEDIUM
-| *camel.component.azure-storage-datalake.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 | false | MEDIUM
-|===
-
-
-
-The camel-azure-storage-datalake source connector has no converters out of the box.
-
-
-
-
-
-The camel-azure-storage-datalake source connector has no transforms out of the box.
-
-
-
-
-
-The camel-azure-storage-datalake source connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-azure-storage-queue-kafka-connector/src/main/docs/camel-azure-storage-queue-kafka-sink-connector.adoc b/connectors/camel-azure-storage-queue-kafka-connector/src/main/docs/camel-azure-storage-queue-kafka-sink-connector.adoc
deleted file mode 100644
index 42e0124..0000000
--- a/connectors/camel-azure-storage-queue-kafka-connector/src/main/docs/camel-azure-storage-queue-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,79 +0,0 @@
-// kafka-connector options: START
-[[camel-azure-storage-queue-kafka-connector-sink]]
-= camel-azure-storage-queue-kafka-connector sink configuration
-
-Connector Description: The azure-storage-queue component is used for storing and retrieving the messages to/from Azure Storage Queue using Azure SDK v12.
-
-When using camel-azure-storage-queue-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-azure-storage-queue-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.azurestoragequeue.CamelAzurestoragequeueSinkConnector
-----
-
-
-The camel-azure-storage-queue sink connector supports 28 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.accountName* | Azure account name to be used for authentication with azure queue services | null | false | MEDIUM
-| *camel.sink.path.queueName* | The queue resource name | null | false | MEDIUM
-| *camel.sink.endpoint.serviceClient* | 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 updating properties of [...]
-| *camel.sink.endpoint.createQueue* | When is set to true, the queue will be automatically created when sending messages to the queue. | false | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.operation* | Queue service operation hint to the producer One of: [listQueues] [createQueue] [deleteQueue] [clearQueue] [sendMessage] [deleteMessage] [receiveMessages] [peekMessages] [updateMessage] | null | false | MEDIUM
-| *camel.sink.endpoint.maxMessages* | 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" | false | MEDIUM
-| *camel.sink.endpoint.messageId* | The ID of the message to be deleted or updated. | null | false | MEDIUM
-| *camel.sink.endpoint.popReceipt* | Unique identifier that must match for the message to be deleted or updated. | null | false | MEDIUM
-| *camel.sink.endpoint.timeout* | An optional timeout applied to the operation. If a response is not returned before the timeout concludes a RuntimeException will be thrown. | null | false | MEDIUM
-| *camel.sink.endpoint.timeToLive* | 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 are typesafe. | null [...]
-| *camel.sink.endpoint.visibilityTimeout* | 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. | null | false | MEDIUM
-| *camel.sink.endpoint.accessKey* | Access key for the associated azure account name to be used for authentication with azure queue services | null | false | MEDIUM
-| *camel.sink.endpoint.credentials* | StorageSharedKeyCredential can be injected to create the azure client, this holds the important authentication information | null | false | MEDIUM
-| *camel.component.azure-storage-queue.configuration* | The component configurations | null | false | MEDIUM
-| *camel.component.azure-storage-queue.serviceClient* | 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 updati [...]
-| *camel.component.azure-storage-queue.createQueue* | When is set to true, the queue will be automatically created when sending messages to the queue. | false | false | MEDIUM
-| *camel.component.azure-storage-queue.lazyStart 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-queue.operation* | Queue service operation hint to the producer One of: [listQueues] [createQueue] [deleteQueue] [clearQueue] [sendMessage] [deleteMessage] [receiveMessages] [peekMessages] [updateMessage] | null | false | MEDIUM
-| *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 | false | MEDIUM
-| *camel.component.azure-storage-queue.maxMessages* | 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" | false | MEDIUM
-| *camel.component.azure-storage-queue.messageId* | The ID of the message to be deleted or updated. | null | false | MEDIUM
-| *camel.component.azure-storage-queue.popReceipt* | Unique identifier that must match for the message to be deleted or updated. | null | false | MEDIUM
-| *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. | null | false | MEDIUM
-| *camel.component.azure-storage-queue.timeToLive* | 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 are [...]
-| *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. | null | false | MEDIUM
-| *camel.component.azure-storage-queue.accessKey* | Access key for the associated azure account name to be used for authentication with azure queue services | null | false | MEDIUM
-| *camel.component.azure-storage-queue.credentials* | StorageSharedKeyCredential can be injected to create the azure client, this holds the important authentication information | null | false | MEDIUM
-|===
-
-
-
-The camel-azure-storage-queue sink connector has no converters out of the box.
-
-
-
-
-
-The camel-azure-storage-queue sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-azure-storage-queue sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-azure-storage-queue-kafka-connector/src/main/docs/camel-azure-storage-queue-kafka-source-connector.adoc b/connectors/camel-azure-storage-queue-kafka-connector/src/main/docs/camel-azure-storage-queue-kafka-source-connector.adoc
deleted file mode 100644
index 194154c..0000000
--- a/connectors/camel-azure-storage-queue-kafka-connector/src/main/docs/camel-azure-storage-queue-kafka-source-connector.adoc
+++ /dev/null
@@ -1,93 +0,0 @@
-// kafka-connector options: START
-[[camel-azure-storage-queue-kafka-connector-source]]
-= camel-azure-storage-queue-kafka-connector source configuration
-
-Connector description: The azure-storage-queue component is used for storing and retrieving the messages to/from Azure Storage Queue using Azure SDK v12.
-
-When using camel-azure-storage-queue-kafka-connector as source make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-azure-storage-queue-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Source connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.azurestoragequeue.CamelAzurestoragequeueSourceConnector
-----
-
-
-The camel-azure-storage-queue source connector supports 42 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.source.path.accountName* | Azure account name to be used for authentication with azure queue services | null | false | MEDIUM
-| *camel.source.path.queueName* | The queue resource name | null | false | MEDIUM
-| *camel.source.endpoint.serviceClient* | 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 updating properties [...]
-| *camel.source.endpoint.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.source.endpoint.sendEmptyMessageWhenIdle* | If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead. | false | false | MEDIUM
-| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | false | MEDIUM
-| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | false | MEDIUM
-| *camel.source.endpoint.pollStrategy* | A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel. | null | false | MEDIUM
-| *camel.source.endpoint.maxMessages* | 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" | false | MEDIUM
-| *camel.source.endpoint.messageId* | The ID of the message to be deleted or updated. | null | false | MEDIUM
-| *camel.source.endpoint.popReceipt* | Unique identifier that must match for the message to be deleted or updated. | null | false | MEDIUM
-| *camel.source.endpoint.timeout* | An optional timeout applied to the operation. If a response is not returned before the timeout concludes a RuntimeException will be thrown. | null | false | MEDIUM
-| *camel.source.endpoint.timeToLive* | 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 are typesafe. | nu [...]
-| *camel.source.endpoint.visibilityTimeout* | 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. | null | false | MEDIUM
-| *camel.source.endpoint.backoffErrorThreshold* | The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in. | null | false | MEDIUM
-| *camel.source.endpoint.backoffIdleThreshold* | The number of subsequent idle polls that should happen before the backoffMultipler should kick-in. | null | false | MEDIUM
-| *camel.source.endpoint.backoffMultiplier* | To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured. | null | false | MEDIUM
-| *camel.source.endpoint.delay* | Milliseconds before the next poll. | 500L | false | MEDIUM
-| *camel.source.endpoint.greedy* | If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages. | false | false | MEDIUM
-| *camel.source.endpoint.initialDelay* | Milliseconds before the first poll starts. | 1000L | false | MEDIUM
-| *camel.source.endpoint.repeatCount* | Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever. | 0L | false | MEDIUM
-| *camel.source.endpoint.runLoggingLevel* | The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that. One of: [TRACE] [DEBUG] [INFO] [WARN] [ERROR] [OFF] | "TRACE" | false | MEDIUM
-| *camel.source.endpoint.scheduledExecutorService* | Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool. | null | false | MEDIUM
-| *camel.source.endpoint.scheduler* | To use a cron scheduler from either camel-spring or camel-quartz component. Use value spring or quartz for built in scheduler | "none" | false | MEDIUM
-| *camel.source.endpoint.schedulerProperties* | To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler. | null | false | MEDIUM
-| *camel.source.endpoint.startScheduler* | Whether the scheduler should be auto started. | true | false | MEDIUM
-| *camel.source.endpoint.timeUnit* | Time unit for initialDelay and delay options. One of: [NANOSECONDS] [MICROSECONDS] [MILLISECONDS] [SECONDS] [MINUTES] [HOURS] [DAYS] | "MILLISECONDS" | false | MEDIUM
-| *camel.source.endpoint.useFixedDelay* | Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details. | true | false | MEDIUM
-| *camel.source.endpoint.accessKey* | Access key for the associated azure account name to be used for authentication with azure queue services | null | false | MEDIUM
-| *camel.source.endpoint.credentials* | StorageSharedKeyCredential can be injected to create the azure client, this holds the important authentication information | null | false | MEDIUM
-| *camel.component.azure-storage-queue.configuration* | The component configurations | null | false | MEDIUM
-| *camel.component.azure-storage-queue.serviceClient* | 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 updati [...]
-| *camel.component.azure-storage-queue.bridgeError 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 | false | MEDIUM
-| *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 | false | MEDIUM
-| *camel.component.azure-storage-queue.maxMessages* | 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" | false | MEDIUM
-| *camel.component.azure-storage-queue.messageId* | The ID of the message to be deleted or updated. | null | false | MEDIUM
-| *camel.component.azure-storage-queue.popReceipt* | Unique identifier that must match for the message to be deleted or updated. | null | false | MEDIUM
-| *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. | null | false | MEDIUM
-| *camel.component.azure-storage-queue.timeToLive* | 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 are [...]
-| *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. | null | false | MEDIUM
-| *camel.component.azure-storage-queue.accessKey* | Access key for the associated azure account name to be used for authentication with azure queue services | null | false | MEDIUM
-| *camel.component.azure-storage-queue.credentials* | StorageSharedKeyCredential can be injected to create the azure client, this holds the important authentication information | null | false | MEDIUM
-|===
-
-
-
-The camel-azure-storage-queue source connector has no converters out of the box.
-
-
-
-
-
-The camel-azure-storage-queue source connector has no transforms out of the box.
-
-
-
-
-
-The camel-azure-storage-queue source connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-bean-kafka-connector/src/main/docs/camel-bean-kafka-sink-connector.adoc b/connectors/camel-bean-kafka-connector/src/main/docs/camel-bean-kafka-sink-connector.adoc
deleted file mode 100644
index 867ad06..0000000
--- a/connectors/camel-bean-kafka-connector/src/main/docs/camel-bean-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,61 +0,0 @@
-// kafka-connector options: START
-[[camel-bean-kafka-connector-sink]]
-= camel-bean-kafka-connector sink configuration
-
-Connector Description: Invoke methods of Java beans stored in Camel registry.
-
-When using camel-bean-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-bean-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.bean.CamelBeanSinkConnector
-----
-
-
-The camel-bean sink connector supports 10 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.beanName* | Sets the name of the bean to invoke | null | true | HIGH
-| *camel.sink.endpoint.cache* | Use scope option instead. | null | false | LOW
-| *camel.sink.endpoint.method* | Sets the name of the method to invoke on the bean | null | false | MEDIUM
-| *camel.sink.endpoint.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.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.parameters* | Used for configuring additional properties on the bean | null | false | MEDIUM
-| *camel.component.bean.cache* | Use singleton option instead. | "true" | false | LOW
-| *camel.component.bean.lazyStartProducer* | 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 cr [...]
-| *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.bean.autowiredEnabled* | 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 | false | MEDIUM
-|===
-
-
-
-The camel-bean sink connector has no converters out of the box.
-
-
-
-
-
-The camel-bean sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-bean sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-beanstalk-kafka-connector/src/main/docs/camel-beanstalk-kafka-sink-connector.adoc b/connectors/camel-beanstalk-kafka-connector/src/main/docs/camel-beanstalk-kafka-sink-connector.adoc
deleted file mode 100644
index d388b1b..0000000
--- a/connectors/camel-beanstalk-kafka-connector/src/main/docs/camel-beanstalk-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,60 +0,0 @@
-// kafka-connector options: START
-[[camel-beanstalk-kafka-connector-sink]]
-= camel-beanstalk-kafka-connector sink configuration
-
-Connector Description: Retrieve and post-process Beanstalk jobs.
-
-When using camel-beanstalk-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-beanstalk-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.beanstalk.CamelBeanstalkSinkConnector
-----
-
-
-The camel-beanstalk sink connector supports 9 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.connectionSettings* | Connection settings host:port/tube | null | false | MEDIUM
-| *camel.sink.endpoint.command* | put means to put the job into Beanstalk. Job body is specified in the Camel message body. Job ID will be returned in beanstalk.jobId message header. delete, release, touch or bury expect Job ID in the message header beanstalk.jobId. Result of the operation is returned in beanstalk.result message header kick expects the number of jobs to kick in the message body and returns the number of jobs actually kicked out in the message header beanstalk.result. One [...]
-| *camel.sink.endpoint.jobDelay* | Job delay in seconds. | 0 | false | MEDIUM
-| *camel.sink.endpoint.jobPriority* | Job priority. (0 is the highest, see Beanstalk protocol) | 1000L | false | MEDIUM
-| *camel.sink.endpoint.jobTimeToRun* | Job time to run in seconds. (when 0, the beanstalkd daemon raises it to 1 automatically, see Beanstalk protocol) | 60 | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.component.beanstalk.lazyStartProducer* | 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.beanstalk.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.beanstalk.connectionSettings 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) | null | false | MEDIUM
-|===
-
-
-
-The camel-beanstalk sink connector has no converters out of the box.
-
-
-
-
-
-The camel-beanstalk sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-beanstalk sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-beanstalk-kafka-connector/src/main/docs/camel-beanstalk-kafka-source-connector.adoc b/connectors/camel-beanstalk-kafka-connector/src/main/docs/camel-beanstalk-kafka-source-connector.adoc
deleted file mode 100644
index 97dfcb8..0000000
--- a/connectors/camel-beanstalk-kafka-connector/src/main/docs/camel-beanstalk-kafka-source-connector.adoc
+++ /dev/null
@@ -1,81 +0,0 @@
-// kafka-connector options: START
-[[camel-beanstalk-kafka-connector-source]]
-= camel-beanstalk-kafka-connector source configuration
-
-Connector description: Retrieve and post-process Beanstalk jobs.
-
-When using camel-beanstalk-kafka-connector as source make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-beanstalk-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Source connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.beanstalk.CamelBeanstalkSourceConnector
-----
-
-
-The camel-beanstalk source connector supports 30 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.source.path.connectionSettings* | Connection settings host:port/tube | null | false | MEDIUM
-| *camel.source.endpoint.command* | put means to put the job into Beanstalk. Job body is specified in the Camel message body. Job ID will be returned in beanstalk.jobId message header. delete, release, touch or bury expect Job ID in the message header beanstalk.jobId. Result of the operation is returned in beanstalk.result message header kick expects the number of jobs to kick in the message body and returns the number of jobs actually kicked out in the message header beanstalk.result. O [...]
-| *camel.source.endpoint.jobDelay* | Job delay in seconds. | 0 | false | MEDIUM
-| *camel.source.endpoint.jobPriority* | Job priority. (0 is the highest, see Beanstalk protocol) | 1000L | false | MEDIUM
-| *camel.source.endpoint.jobTimeToRun* | Job time to run in seconds. (when 0, the beanstalkd daemon raises it to 1 automatically, see Beanstalk protocol) | 60 | false | MEDIUM
-| *camel.source.endpoint.awaitJob* | Whether to wait for job to complete before ack the job from beanstalk | true | false | MEDIUM
-| *camel.source.endpoint.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.source.endpoint.onFailure* | Command to use when processing failed. One of: [bury] [release] [put] [touch] [delete] [kick] | null | false | MEDIUM
-| *camel.source.endpoint.sendEmptyMessageWhenIdle* | If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead. | false | false | MEDIUM
-| *camel.source.endpoint.useBlockIO* | Whether to use blockIO. | true | false | MEDIUM
-| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | false | MEDIUM
-| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | false | MEDIUM
-| *camel.source.endpoint.pollStrategy* | A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel. | null | false | MEDIUM
-| *camel.source.endpoint.backoffErrorThreshold* | The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in. | null | false | MEDIUM
-| *camel.source.endpoint.backoffIdleThreshold* | The number of subsequent idle polls that should happen before the backoffMultipler should kick-in. | null | false | MEDIUM
-| *camel.source.endpoint.backoffMultiplier* | To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured. | null | false | MEDIUM
-| *camel.source.endpoint.delay* | Milliseconds before the next poll. | 500L | false | MEDIUM
-| *camel.source.endpoint.greedy* | If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages. | false | false | MEDIUM
-| *camel.source.endpoint.initialDelay* | Milliseconds before the first poll starts. | 1000L | false | MEDIUM
-| *camel.source.endpoint.repeatCount* | Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever. | 0L | false | MEDIUM
-| *camel.source.endpoint.runLoggingLevel* | The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that. One of: [TRACE] [DEBUG] [INFO] [WARN] [ERROR] [OFF] | "TRACE" | false | MEDIUM
-| *camel.source.endpoint.scheduledExecutorService* | Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool. | null | false | MEDIUM
-| *camel.source.endpoint.scheduler* | To use a cron scheduler from either camel-spring or camel-quartz component. Use value spring or quartz for built in scheduler | "none" | false | MEDIUM
-| *camel.source.endpoint.schedulerProperties* | To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler. | null | false | MEDIUM
-| *camel.source.endpoint.startScheduler* | Whether the scheduler should be auto started. | true | false | MEDIUM
-| *camel.source.endpoint.timeUnit* | Time unit for initialDelay and delay options. One of: [NANOSECONDS] [MICROSECONDS] [MILLISECONDS] [SECONDS] [MINUTES] [HOURS] [DAYS] | "MILLISECONDS" | false | MEDIUM
-| *camel.source.endpoint.useFixedDelay* | Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details. | true | false | MEDIUM
-| *camel.component.beanstalk.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.component.beanstalk.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.beanstalk.connectionSettings 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) | null | false | MEDIUM
-|===
-
-
-
-The camel-beanstalk source connector has no converters out of the box.
-
-
-
-
-
-The camel-beanstalk source connector has no transforms out of the box.
-
-
-
-
-
-The camel-beanstalk source connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-box-kafka-connector/src/main/docs/camel-box-kafka-sink-connector.adoc b/connectors/camel-box-kafka-connector/src/main/docs/camel-box-kafka-sink-connector.adoc
deleted file mode 100644
index 69ea9f4..0000000
--- a/connectors/camel-box-kafka-connector/src/main/docs/camel-box-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,88 +0,0 @@
-// kafka-connector options: START
-[[camel-box-kafka-connector-sink]]
-= camel-box-kafka-connector sink configuration
-
-Connector Description: Upload, download and manage files, folders, groups, collaborations, etc. on box.com.
-
-When using camel-box-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-box-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.box.CamelBoxSinkConnector
-----
-
-
-The camel-box sink connector supports 37 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.apiName* | What kind of operation to perform One of: [COLLABORATIONS] [COMMENTS] [EVENT_LOGS] [FILES] [FOLDERS] [GROUPS] [EVENTS] [SEARCH] [TASKS] [USERS] | null | true | HIGH
-| *camel.sink.path.methodName* | What sub operation to use for the selected operation | null | true | HIGH
-| *camel.sink.endpoint.clientId* | Box application client ID | null | false | MEDIUM
-| *camel.sink.endpoint.enterpriseId* | The enterprise ID to use for an App Enterprise. | null | false | MEDIUM
-| *camel.sink.endpoint.inBody* | Sets the name of a parameter to be passed in the exchange In Body | null | false | MEDIUM
-| *camel.sink.endpoint.userId* | The user ID to use for an App User. | null | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.httpParams* | Custom HTTP params for settings like proxy host | null | false | MEDIUM
-| *camel.sink.endpoint.authenticationType* | 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" | false | MEDIUM
-| *camel.sink.endpoint.accessTokenCache* | Custom Access Token Cache for storing and retrieving access tokens. | null | false | MEDIUM
-| *camel.sink.endpoint.clientSecret* | Box application client secret | null | false | MEDIUM
-| *camel.sink.endpoint.encryptionAlgorithm* | The type of encryption algorithm for JWT. Supported Algorithms: RSA_SHA_256 RSA_SHA_384 RSA_SHA_512 One of: [RSA_SHA_256] [RSA_SHA_384] [RSA_SHA_512] | "RSA_SHA_256" | false | MEDIUM
-| *camel.sink.endpoint.maxCacheEntries* | The maximum number of access tokens in cache. | 100 | false | MEDIUM
-| *camel.sink.endpoint.privateKeyFile* | The private key for generating the JWT signature. | null | false | MEDIUM
-| *camel.sink.endpoint.privateKeyPassword* | The password for the private key. | null | false | MEDIUM
-| *camel.sink.endpoint.publicKeyId* | The ID for public key for validating the JWT signature. | null | false | MEDIUM
-| *camel.sink.endpoint.sslContextParameters* | To configure security using SSLContextParameters. | null | false | MEDIUM
-| *camel.sink.endpoint.userName* | Box user name, MUST be provided | null | false | MEDIUM
-| *camel.sink.endpoint.userPassword* | Box user password, MUST be provided if authSecureStorage is not set, or returns null on first call | null | false | MEDIUM
-| *camel.component.box.clientId* | Box application client ID | null | false | MEDIUM
-| *camel.component.box.configuration* | To use the shared configuration | null | false | MEDIUM
-| *camel.component.box.enterpriseId* | The enterprise ID to use for an App Enterprise. | null | false | MEDIUM
-| *camel.component.box.userId* | The user ID to use for an App User. | null | false | MEDIUM
-| *camel.component.box.lazyStartProducer* | 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 cre [...]
-| *camel.component.box.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.box.httpParams* | Custom HTTP params for settings like proxy host | null | false | MEDIUM
-| *camel.component.box.authenticationType* | 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" | false | MEDIUM
-| *camel.component.box.accessTokenCache* | Custom Access Token Cache for storing and retrieving access tokens. | null | false | MEDIUM
-| *camel.component.box.clientSecret* | Box application client secret | null | false | MEDIUM
-| *camel.component.box.encryptionAlgorithm* | The type of encryption algorithm for JWT. Supported Algorithms: RSA_SHA_256 RSA_SHA_384 RSA_SHA_512 One of: [RSA_SHA_256] [RSA_SHA_384] [RSA_SHA_512] | "RSA_SHA_256" | false | MEDIUM
-| *camel.component.box.maxCacheEntries* | The maximum number of access tokens in cache. | 100 | false | MEDIUM
-| *camel.component.box.privateKeyFile* | The private key for generating the JWT signature. | null | false | MEDIUM
-| *camel.component.box.privateKeyPassword* | The password for the private key. | null | false | MEDIUM
-| *camel.component.box.publicKeyId* | The ID for public key for validating the JWT signature. | null | false | MEDIUM
-| *camel.component.box.sslContextParameters* | To configure security using SSLContextParameters. | null | false | MEDIUM
-| *camel.component.box.userName* | Box user name, MUST be provided | null | false | MEDIUM
-| *camel.component.box.userPassword* | Box user password, MUST be provided if authSecureStorage is not set, or returns null on first call | null | false | MEDIUM
-|===
-
-
-
-The camel-box sink connector has no converters out of the box.
-
-
-
-
-
-The camel-box sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-box sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-box-kafka-connector/src/main/docs/camel-box-kafka-source-connector.adoc b/connectors/camel-box-kafka-connector/src/main/docs/camel-box-kafka-source-connector.adoc
deleted file mode 100644
index 7c2540a..0000000
--- a/connectors/camel-box-kafka-connector/src/main/docs/camel-box-kafka-source-connector.adoc
+++ /dev/null
@@ -1,89 +0,0 @@
-// kafka-connector options: START
-[[camel-box-kafka-connector-source]]
-= camel-box-kafka-connector source configuration
-
-Connector description: Upload, download and manage files, folders, groups, collaborations, etc. on box.com.
-
-When using camel-box-kafka-connector as source make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-box-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Source connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.box.CamelBoxSourceConnector
-----
-
-
-The camel-box source connector supports 38 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.source.path.apiName* | What kind of operation to perform One of: [COLLABORATIONS] [COMMENTS] [EVENT_LOGS] [FILES] [FOLDERS] [GROUPS] [EVENTS] [SEARCH] [TASKS] [USERS] | null | true | HIGH
-| *camel.source.path.methodName* | What sub operation to use for the selected operation | null | true | HIGH
-| *camel.source.endpoint.clientId* | Box application client ID | null | false | MEDIUM
-| *camel.source.endpoint.enterpriseId* | The enterprise ID to use for an App Enterprise. | null | false | MEDIUM
-| *camel.source.endpoint.inBody* | Sets the name of a parameter to be passed in the exchange In Body | null | false | MEDIUM
-| *camel.source.endpoint.userId* | The user ID to use for an App User. | null | false | MEDIUM
-| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | false | MEDIUM
-| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | false | MEDIUM
-| *camel.source.endpoint.httpParams* | Custom HTTP params for settings like proxy host | null | false | MEDIUM
-| *camel.source.endpoint.authenticationType* | 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" | false | MEDIUM
-| *camel.source.endpoint.accessTokenCache* | Custom Access Token Cache for storing and retrieving access tokens. | null | false | MEDIUM
-| *camel.source.endpoint.clientSecret* | Box application client secret | null | false | MEDIUM
-| *camel.source.endpoint.encryptionAlgorithm* | The type of encryption algorithm for JWT. Supported Algorithms: RSA_SHA_256 RSA_SHA_384 RSA_SHA_512 One of: [RSA_SHA_256] [RSA_SHA_384] [RSA_SHA_512] | "RSA_SHA_256" | false | MEDIUM
-| *camel.source.endpoint.maxCacheEntries* | The maximum number of access tokens in cache. | 100 | false | MEDIUM
-| *camel.source.endpoint.privateKeyFile* | The private key for generating the JWT signature. | null | false | MEDIUM
-| *camel.source.endpoint.privateKeyPassword* | The password for the private key. | null | false | MEDIUM
-| *camel.source.endpoint.publicKeyId* | The ID for public key for validating the JWT signature. | null | false | MEDIUM
-| *camel.source.endpoint.sslContextParameters* | To configure security using SSLContextParameters. | null | false | MEDIUM
-| *camel.source.endpoint.userName* | Box user name, MUST be provided | null | false | MEDIUM
-| *camel.source.endpoint.userPassword* | Box user password, MUST be provided if authSecureStorage is not set, or returns null on first call | null | false | MEDIUM
-| *camel.component.box.clientId* | Box application client ID | null | false | MEDIUM
-| *camel.component.box.configuration* | To use the shared configuration | null | false | MEDIUM
-| *camel.component.box.enterpriseId* | The enterprise ID to use for an App Enterprise. | null | false | MEDIUM
-| *camel.component.box.userId* | The user ID to use for an App User. | null | false | MEDIUM
-| *camel.component.box.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.component.box.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.box.httpParams* | Custom HTTP params for settings like proxy host | null | false | MEDIUM
-| *camel.component.box.authenticationType* | 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" | false | MEDIUM
-| *camel.component.box.accessTokenCache* | Custom Access Token Cache for storing and retrieving access tokens. | null | false | MEDIUM
-| *camel.component.box.clientSecret* | Box application client secret | null | false | MEDIUM
-| *camel.component.box.encryptionAlgorithm* | The type of encryption algorithm for JWT. Supported Algorithms: RSA_SHA_256 RSA_SHA_384 RSA_SHA_512 One of: [RSA_SHA_256] [RSA_SHA_384] [RSA_SHA_512] | "RSA_SHA_256" | false | MEDIUM
-| *camel.component.box.maxCacheEntries* | The maximum number of access tokens in cache. | 100 | false | MEDIUM
-| *camel.component.box.privateKeyFile* | The private key for generating the JWT signature. | null | false | MEDIUM
-| *camel.component.box.privateKeyPassword* | The password for the private key. | null | false | MEDIUM
-| *camel.component.box.publicKeyId* | The ID for public key for validating the JWT signature. | null | false | MEDIUM
-| *camel.component.box.sslContextParameters* | To configure security using SSLContextParameters. | null | false | MEDIUM
-| *camel.component.box.userName* | Box user name, MUST be provided | null | false | MEDIUM
-| *camel.component.box.userPassword* | Box user password, MUST be provided if authSecureStorage is not set, or returns null on first call | null | false | MEDIUM
-|===
-
-
-
-The camel-box source connector has no converters out of the box.
-
-
-
-
-
-The camel-box source connector has no transforms out of the box.
-
-
-
-
-
-The camel-box source connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-braintree-kafka-connector/src/main/docs/camel-braintree-kafka-sink-connector.adoc b/connectors/camel-braintree-kafka-connector/src/main/docs/camel-braintree-kafka-sink-connector.adoc
deleted file mode 100644
index 36a72e2..0000000
--- a/connectors/camel-braintree-kafka-connector/src/main/docs/camel-braintree-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,73 +0,0 @@
-// kafka-connector options: START
-[[camel-braintree-kafka-connector-sink]]
-= camel-braintree-kafka-connector sink configuration
-
-Connector Description: Process payments using Braintree Payments.
-
-When using camel-braintree-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-braintree-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.braintree.CamelBraintreeSinkConnector
-----
-
-
-The camel-braintree sink connector supports 18 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.apiName* | What kind of operation to perform One of: [ADD_ON] [ADDRESS] [CLIENT_TOKEN] [CREDIT_CARD_VERIFICATION] [CUSTOMER] [DISCOUNT] [DISPUTE] [DOCUMENT_UPLOAD] [MERCHANT_ACCOUNT] [PAYMENT_METHOD] [PAYMENT_METHOD_NONCE] [PLAN] [REPORT] [SETTLEMENT_BATCH_SUMMARY] [SUBSCRIPTION] [TRANSACTION] [WEBHOOK_NOTIFICATION] | null | true | HIGH
-| *camel.sink.path.methodName* | What sub operation to use for the selected operation One of: [accept] [addFileEvidence] [addTextEvidence] [cancel] [cancelRelease] [cloneTransaction] [create] [createForCurrency] [credit] [delete] [fetchMerchantAccounts] [finalize] [find] [generate] [grant] [holdInEscrow] [parse] [refund] [releaseFromEscrow] [removeEvidence] [retryCharge] [revoke] [sale] [search] [submitForPartialSettlement] [submitForSettlement] [transactionLevelFees] [update] [updateDet [...]
-| *camel.sink.endpoint.environment* | The environment Either SANDBOX or PRODUCTION | null | false | MEDIUM
-| *camel.sink.endpoint.inBody* | Sets the name of a parameter to be passed in the exchange In Body | null | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.merchantId* | The merchant id provided by Braintree. | null | false | MEDIUM
-| *camel.sink.endpoint.httpReadTimeout* | Set read timeout for http calls. | null | false | MEDIUM
-| *camel.sink.endpoint.httpLogLevel* | Set logging level for http calls, see java.util.logging.Level One of: [OFF] [SEVERE] [WARNING] [INFO] [CONFIG] [FINE] [FINER] [FINEST] [ALL] | null | false | MEDIUM
-| *camel.sink.endpoint.httpLogName* | Set log category to use to log http calls. | "Braintree" | false | MEDIUM
-| *camel.sink.endpoint.logHandlerEnabled* | Sets whether to enable the BraintreeLogHandler. It may be desirable to set this to 'false' where an existing JUL - SLF4J logger bridge is on the classpath. This option can also be configured globally on the BraintreeComponent. | true | false | MEDIUM
-| *camel.sink.endpoint.proxyHost* | The proxy host | null | false | MEDIUM
-| *camel.sink.endpoint.proxyPort* | The proxy port | null | false | MEDIUM
-| *camel.sink.endpoint.accessToken* | The access token granted by a merchant to another in order to process transactions on their behalf. Used in place of environment, merchant id, public key and private key fields. | null | false | MEDIUM
-| *camel.sink.endpoint.privateKey* | The private key provided by Braintree. | null | false | MEDIUM
-| *camel.sink.endpoint.publicKey* | The public key provided by Braintree. | null | false | MEDIUM
-| *camel.component.braintree.lazyStartProducer* | 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.braintree.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.braintree.configuration* | Component configuration | null | false | MEDIUM
-|===
-
-
-
-The camel-braintree sink connector has no converters out of the box.
-
-
-
-
-
-The camel-braintree sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-braintree sink connector has no aggregation strategies out of the box.
-
-
-
-
-// kafka-connector options: END
diff --git a/connectors/camel-caffeine-cache-kafka-connector/src/main/docs/camel-caffeine-cache-kafka-sink-connector.adoc b/connectors/camel-caffeine-cache-kafka-connector/src/main/docs/camel-caffeine-cache-kafka-sink-connector.adoc
deleted file mode 100644
index fbc30b0..0000000
--- a/connectors/camel-caffeine-cache-kafka-connector/src/main/docs/camel-caffeine-cache-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,84 +0,0 @@
-// kafka-connector options: START
-[[camel-caffeine-cache-kafka-connector-sink]]
-= camel-caffeine-cache-kafka-connector sink configuration
-
-Connector Description: Perform caching operations using Caffeine Cache.
-
-When using camel-caffeine-cache-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-caffeine-cache-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.caffeinecache.CamelCaffeinecacheSinkConnector
-----
-
-
-The camel-caffeine-cache sink connector supports 33 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.cacheName* | the cache name | null | true | HIGH
-| *camel.sink.endpoint.action* | To configure the default cache action. If an action is set in the message header, then the operation from the header takes precedence. | null | false | MEDIUM
-| *camel.sink.endpoint.cacheLoader* | To configure a CacheLoader in case of a LoadCache use | null | false | MEDIUM
-| *camel.sink.endpoint.createCacheIfNotExist* | Configure if a cache need to be created if it does exist or can't be pre-configured. | true | false | MEDIUM
-| *camel.sink.endpoint.evictionType* | Set the eviction Type for this cache One of: [size_based] [time_based] | "SIZE_BASED" | false | MEDIUM
-| *camel.sink.endpoint.expireAfterAccessTime* | Set the expire After Access Time in case of time based Eviction (in seconds) | 300 | false | MEDIUM
-| *camel.sink.endpoint.expireAfterWriteTime* | Set the expire After Access Write in case of time based Eviction (in seconds) | 300 | false | MEDIUM
-| *camel.sink.endpoint.initialCapacity* | Set the initial Capacity for the cache | 10000 | false | MEDIUM
-| *camel.sink.endpoint.key* | To configure the default action key. If a key is set in the message header, then the key from the header takes precedence. | null | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.maximumSize* | Set the maximum size for the cache | 10000 | false | MEDIUM
-| *camel.sink.endpoint.removalListener* | Set a specific removal Listener for the cache | null | false | MEDIUM
-| *camel.sink.endpoint.statsCounter* | Set a specific Stats Counter for the cache stats | null | false | MEDIUM
-| *camel.sink.endpoint.statsEnabled* | To enable stats on the cache | false | false | MEDIUM
-| *camel.sink.endpoint.keyType* | The cache key type, default java.lang.Object | null | false | MEDIUM
-| *camel.sink.endpoint.valueType* | The cache value type, default java.lang.Object | null | false | MEDIUM
-| *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. | null | false | MEDIUM
-| *camel.component.caffeine-cache.cacheLoader* | To configure a CacheLoader in case of a LoadCache use | null | false | MEDIUM
-| *camel.component.caffeine-cache.createCacheIfNot Exist* | Configure if a cache need to be created if it does exist or can't be pre-configured. | true | false | MEDIUM
-| *camel.component.caffeine-cache.evictionType* | Set the eviction Type for this cache One of: [size_based] [time_based] | "SIZE_BASED" | false | MEDIUM
-| *camel.component.caffeine-cache.expireAfterAccess Time* | Set the expire After Access Time in case of time based Eviction (in seconds) | 300 | false | MEDIUM
-| *camel.component.caffeine-cache.expireAfterWrite Time* | Set the expire After Access Write in case of time based Eviction (in seconds) | 300 | false | MEDIUM
-| *camel.component.caffeine-cache.initialCapacity* | Set the initial Capacity for the cache | 10000 | false | MEDIUM
-| *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. | null | false | MEDIUM
-| *camel.component.caffeine-cache.lazyStartProducer* | 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.caffeine-cache.maximumSize* | Set the maximum size for the cache | 10000 | false | MEDIUM
-| *camel.component.caffeine-cache.removalListener* | Set a specific removal Listener for the cache | null | false | MEDIUM
-| *camel.component.caffeine-cache.statsCounter* | Set a specific Stats Counter for the cache stats | null | false | MEDIUM
-| *camel.component.caffeine-cache.statsEnabled* | To enable stats on the cache | false | false | MEDIUM
-| *camel.component.caffeine-cache.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.caffeine-cache.configuration* | Sets the global component configuration | null | false | MEDIUM
-| *camel.component.caffeine-cache.keyType* | The cache key type, default java.lang.Object | null | false | MEDIUM
-| *camel.component.caffeine-cache.valueType* | The cache value type, default java.lang.Object | null | false | MEDIUM
-|===
-
-
-
-The camel-caffeine-cache sink connector has no converters out of the box.
-
-
-
-
-
-The camel-caffeine-cache sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-caffeine-cache sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-caffeine-loadcache-kafka-connector/src/main/docs/camel-caffeine-loadcache-kafka-sink-connector.adoc b/connectors/camel-caffeine-loadcache-kafka-connector/src/main/docs/camel-caffeine-loadcache-kafka-sink-connector.adoc
deleted file mode 100644
index 457c1e3..0000000
--- a/connectors/camel-caffeine-loadcache-kafka-connector/src/main/docs/camel-caffeine-loadcache-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,84 +0,0 @@
-// kafka-connector options: START
-[[camel-caffeine-loadcache-kafka-connector-sink]]
-= camel-caffeine-loadcache-kafka-connector sink configuration
-
-Connector Description: Perform caching operations using Caffeine Cache with an attached CacheLoader.
-
-When using camel-caffeine-loadcache-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-caffeine-loadcache-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.caffeineloadcache.CamelCaffeineloadcacheSinkConnector
-----
-
-
-The camel-caffeine-loadcache sink connector supports 33 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.cacheName* | the cache name | null | true | HIGH
-| *camel.sink.endpoint.action* | To configure the default cache action. If an action is set in the message header, then the operation from the header takes precedence. | null | false | MEDIUM
-| *camel.sink.endpoint.cacheLoader* | To configure a CacheLoader in case of a LoadCache use | null | false | MEDIUM
-| *camel.sink.endpoint.createCacheIfNotExist* | Configure if a cache need to be created if it does exist or can't be pre-configured. | true | false | MEDIUM
-| *camel.sink.endpoint.evictionType* | Set the eviction Type for this cache One of: [size_based] [time_based] | "SIZE_BASED" | false | MEDIUM
-| *camel.sink.endpoint.expireAfterAccessTime* | Set the expire After Access Time in case of time based Eviction (in seconds) | 300 | false | MEDIUM
-| *camel.sink.endpoint.expireAfterWriteTime* | Set the expire After Access Write in case of time based Eviction (in seconds) | 300 | false | MEDIUM
-| *camel.sink.endpoint.initialCapacity* | Set the initial Capacity for the cache | 10000 | false | MEDIUM
-| *camel.sink.endpoint.key* | To configure the default action key. If a key is set in the message header, then the key from the header takes precedence. | null | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.maximumSize* | Set the maximum size for the cache | 10000 | false | MEDIUM
-| *camel.sink.endpoint.removalListener* | Set a specific removal Listener for the cache | null | false | MEDIUM
-| *camel.sink.endpoint.statsCounter* | Set a specific Stats Counter for the cache stats | null | false | MEDIUM
-| *camel.sink.endpoint.statsEnabled* | To enable stats on the cache | false | false | MEDIUM
-| *camel.sink.endpoint.keyType* | The cache key type, default java.lang.Object | null | false | MEDIUM
-| *camel.sink.endpoint.valueType* | The cache value type, default java.lang.Object | null | false | MEDIUM
-| *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. | null | false | MEDIUM
-| *camel.component.caffeine-loadcache.cacheLoader* | To configure a CacheLoader in case of a LoadCache use | null | false | MEDIUM
-| *camel.component.caffeine-loadcache.createCacheIf NotExist* | Configure if a cache need to be created if it does exist or can't be pre-configured. | true | false | MEDIUM
-| *camel.component.caffeine-loadcache.evictionType* | Set the eviction Type for this cache One of: [size_based] [time_based] | "SIZE_BASED" | false | MEDIUM
-| *camel.component.caffeine-loadcache.expireAfter AccessTime* | Set the expire After Access Time in case of time based Eviction (in seconds) | 300 | false | MEDIUM
-| *camel.component.caffeine-loadcache.expireAfter WriteTime* | Set the expire After Access Write in case of time based Eviction (in seconds) | 300 | false | MEDIUM
-| *camel.component.caffeine-loadcache.initialCapacity* | Set the initial Capacity for the cache | 10000 | false | MEDIUM
-| *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. | null | false | MEDIUM
-| *camel.component.caffeine-loadcache.lazyStart 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 pr [...]
-| *camel.component.caffeine-loadcache.maximumSize* | Set the maximum size for the cache | 10000 | false | MEDIUM
-| *camel.component.caffeine-loadcache.removalListener* | Set a specific removal Listener for the cache | null | false | MEDIUM
-| *camel.component.caffeine-loadcache.statsCounter* | Set a specific Stats Counter for the cache stats | null | false | MEDIUM
-| *camel.component.caffeine-loadcache.statsEnabled* | To enable stats on the cache | false | false | MEDIUM
-| *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 | false | MEDIUM
-| *camel.component.caffeine-loadcache.configuration* | Sets the global component configuration | null | false | MEDIUM
-| *camel.component.caffeine-loadcache.keyType* | The cache key type, default java.lang.Object | null | false | MEDIUM
-| *camel.component.caffeine-loadcache.valueType* | The cache value type, default java.lang.Object | null | false | MEDIUM
-|===
-
-
-
-The camel-caffeine-loadcache sink connector has no converters out of the box.
-
-
-
-
-
-The camel-caffeine-loadcache sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-caffeine-loadcache sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-chatscript-kafka-connector/src/main/docs/camel-chatscript-kafka-sink-connector.adoc b/connectors/camel-chatscript-kafka-connector/src/main/docs/camel-chatscript-kafka-sink-connector.adoc
deleted file mode 100644
index f404da7..0000000
--- a/connectors/camel-chatscript-kafka-connector/src/main/docs/camel-chatscript-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,59 +0,0 @@
-// kafka-connector options: START
-[[camel-chatscript-kafka-connector-sink]]
-= camel-chatscript-kafka-connector sink configuration
-
-Connector Description: Chat with a ChatScript Server.
-
-When using camel-chatscript-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-chatscript-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.chatscript.CamelChatscriptSinkConnector
-----
-
-
-The camel-chatscript sink connector supports 8 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.host* | Hostname or IP of the server on which CS server is running | null | true | HIGH
-| *camel.sink.path.port* | Port on which ChatScript is listening to | 1024 | false | MEDIUM
-| *camel.sink.path.botName* | Name of the Bot in CS to converse with | null | true | HIGH
-| *camel.sink.endpoint.chatUserName* | Username who initializes the CS conversation. To be set when chat is initialized from camel route | null | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.resetChat* | Issues :reset command to start a new conversation everytime | false | false | MEDIUM
-| *camel.component.chatscript.lazyStartProducer* | 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.chatscript.autowiredEnabled* | 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 | false | MEDIUM
-|===
-
-
-
-The camel-chatscript sink connector has no converters out of the box.
-
-
-
-
-
-The camel-chatscript sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-chatscript sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-chunk-kafka-connector/src/main/docs/camel-chunk-kafka-sink-connector.adoc b/connectors/camel-chunk-kafka-connector/src/main/docs/camel-chunk-kafka-sink-connector.adoc
deleted file mode 100644
index d48f391..0000000
--- a/connectors/camel-chunk-kafka-connector/src/main/docs/camel-chunk-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,65 +0,0 @@
-// kafka-connector options: START
-[[camel-chunk-kafka-connector-sink]]
-= camel-chunk-kafka-connector sink configuration
-
-Connector Description: Transform messages using Chunk templating engine.
-
-When using camel-chunk-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-chunk-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.chunk.CamelChunkSinkConnector
-----
-
-
-The camel-chunk sink connector supports 14 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.resourceUri* | Path to the resource. You can prefix with: classpath, file, http, ref, or bean. classpath, file and http loads the resource using these protocols (classpath is default). ref will lookup the resource in the registry. bean will call a method on a bean to be used as the resource. For bean you can specify the method name after dot, eg bean:myBean.myMethod. | null | true | HIGH
-| *camel.sink.endpoint.allowContextMapAll* | 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 | false | MEDIUM
-| *camel.sink.endpoint.allowTemplateFromHeader* | 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 | false | MEDIUM
-| *camel.sink.endpoint.contentCache* | Sets whether to use resource content cache or not | false | false | MEDIUM
-| *camel.sink.endpoint.encoding* | Define the encoding of the body | null | false | MEDIUM
-| *camel.sink.endpoint.extension* | Define the file extension of the template | null | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.themeFolder* | Define the themes folder to scan | null | false | MEDIUM
-| *camel.sink.endpoint.themeLayer* | Define the theme layer to elaborate | null | false | MEDIUM
-| *camel.sink.endpoint.themeSubfolder* | Define the themes subfolder to scan | null | false | MEDIUM
-| *camel.component.chunk.allowContextMapAll* | 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 | false | MEDIUM
-| *camel.component.chunk.allowTemplateFromHeader* | 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 | false | MEDIUM
-| *camel.component.chunk.lazyStartProducer* | 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.chunk.autowiredEnabled* | 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 | false | MEDIUM
-|===
-
-
-
-The camel-chunk sink connector has no converters out of the box.
-
-
-
-
-
-The camel-chunk sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-chunk sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-cm-sms-kafka-connector/src/main/docs/camel-cm-sms-kafka-sink-connector.adoc b/connectors/camel-cm-sms-kafka-connector/src/main/docs/camel-cm-sms-kafka-sink-connector.adoc
deleted file mode 100644
index 8d173ec..0000000
--- a/connectors/camel-cm-sms-kafka-connector/src/main/docs/camel-cm-sms-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,59 +0,0 @@
-// kafka-connector options: START
-[[camel-cm-sms-kafka-connector-sink]]
-= camel-cm-sms-kafka-connector sink configuration
-
-Connector Description: Send SMS messages via CM SMS Gateway.
-
-When using camel-cm-sms-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-cm-sms-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.cmsms.CamelCmsmsSinkConnector
-----
-
-
-The camel-cm-sms sink connector supports 8 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.host* | SMS Provider HOST with scheme | null | true | HIGH
-| *camel.sink.endpoint.defaultFrom* | This is the sender name. The maximum length is 11 characters. | null | true | HIGH
-| *camel.sink.endpoint.defaultMaxNumberOfParts* | If it is a multipart message forces the max number. Message can be truncated. Technically the gateway will first check if a message is larger than 160 characters, if so, the message will be cut into multiple 153 characters parts limited by these parameters. | 8 | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.productToken* | The unique token to use | null | true | HIGH
-| *camel.sink.endpoint.testConnectionOnStartup* | Whether to test the connection to the SMS Gateway on startup | false | false | MEDIUM
-| *camel.component.cm-sms.lazyStartProducer* | 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.cm-sms.autowiredEnabled* | 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 | false | MEDIUM
-|===
-
-
-
-The camel-cm-sms sink connector has no converters out of the box.
-
-
-
-
-
-The camel-cm-sms sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-cm-sms sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-cmis-kafka-connector/src/main/docs/camel-cmis-kafka-sink-connector.adoc b/connectors/camel-cmis-kafka-connector/src/main/docs/camel-cmis-kafka-sink-connector.adoc
deleted file mode 100644
index b0da501..0000000
--- a/connectors/camel-cmis-kafka-connector/src/main/docs/camel-cmis-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,64 +0,0 @@
-// kafka-connector options: START
-[[camel-cmis-kafka-connector-sink]]
-= camel-cmis-kafka-connector sink configuration
-
-Connector Description: Read and write data from to/from a CMIS compliant content repositories.
-
-When using camel-cmis-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-cmis-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.cmis.CamelCmisSinkConnector
-----
-
-
-The camel-cmis sink connector supports 13 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.cmsUrl* | URL to the cmis repository | null | true | HIGH
-| *camel.sink.endpoint.pageSize* | Number of nodes to retrieve per page | 100 | false | MEDIUM
-| *camel.sink.endpoint.readContent* | If set to true, the content of document node will be retrieved in addition to the properties | false | false | MEDIUM
-| *camel.sink.endpoint.readCount* | Max number of nodes to read | null | false | MEDIUM
-| *camel.sink.endpoint.repositoryId* | The Id of the repository to use. If not specified the first available repository is used | null | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.queryMode* | If true, will execute the cmis query from the message body and return result, otherwise will create a node in the cmis repository | false | false | MEDIUM
-| *camel.sink.endpoint.sessionFacadeFactory* | To use a custom CMISSessionFacadeFactory to create the CMISSessionFacade instances | null | false | MEDIUM
-| *camel.sink.endpoint.password* | Password for the cmis repository | null | false | MEDIUM
-| *camel.sink.endpoint.username* | Username for the cmis repository | null | false | MEDIUM
-| *camel.component.cmis.lazyStartProducer* | 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 cr [...]
-| *camel.component.cmis.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.cmis.sessionFacadeFactory* | To use a custom CMISSessionFacadeFactory to create the CMISSessionFacade instances | null | false | MEDIUM
-|===
-
-
-
-The camel-cmis sink connector has no converters out of the box.
-
-
-
-
-
-The camel-cmis sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-cmis sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-cmis-kafka-connector/src/main/docs/camel-cmis-kafka-source-connector.adoc b/connectors/camel-cmis-kafka-connector/src/main/docs/camel-cmis-kafka-source-connector.adoc
deleted file mode 100644
index 70cf991..0000000
--- a/connectors/camel-cmis-kafka-connector/src/main/docs/camel-cmis-kafka-source-connector.adoc
+++ /dev/null
@@ -1,66 +0,0 @@
-// kafka-connector options: START
-[[camel-cmis-kafka-connector-source]]
-= camel-cmis-kafka-connector source configuration
-
-Connector description: Read and write data from to/from a CMIS compliant content repositories.
-
-When using camel-cmis-kafka-connector as source make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-cmis-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Source connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.cmis.CamelCmisSourceConnector
-----
-
-
-The camel-cmis source connector supports 15 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.source.path.cmsUrl* | URL to the cmis repository | null | true | HIGH
-| *camel.source.endpoint.pageSize* | Number of nodes to retrieve per page | 100 | false | MEDIUM
-| *camel.source.endpoint.readContent* | If set to true, the content of document node will be retrieved in addition to the properties | false | false | MEDIUM
-| *camel.source.endpoint.readCount* | Max number of nodes to read | null | false | MEDIUM
-| *camel.source.endpoint.repositoryId* | The Id of the repository to use. If not specified the first available repository is used | null | false | MEDIUM
-| *camel.source.endpoint.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.source.endpoint.query* | The cmis query to execute against the repository. If not specified, the consumer will retrieve every node from the content repository by iterating the content tree recursively | null | false | MEDIUM
-| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | false | MEDIUM
-| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | false | MEDIUM
-| *camel.source.endpoint.sessionFacadeFactory* | To use a custom CMISSessionFacadeFactory to create the CMISSessionFacade instances | null | false | MEDIUM
-| *camel.source.endpoint.password* | Password for the cmis repository | null | false | MEDIUM
-| *camel.source.endpoint.username* | Username for the cmis repository | null | false | MEDIUM
-| *camel.component.cmis.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.component.cmis.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.cmis.sessionFacadeFactory* | To use a custom CMISSessionFacadeFactory to create the CMISSessionFacade instances | null | false | MEDIUM
-|===
-
-
-
-The camel-cmis source connector has no converters out of the box.
-
-
-
-
-
-The camel-cmis source connector has no transforms out of the box.
-
-
-
-
-
-The camel-cmis source connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-coap-kafka-connector/src/main/docs/camel-coap-kafka-sink-connector.adoc b/connectors/camel-coap-kafka-connector/src/main/docs/camel-coap-kafka-sink-connector.adoc
deleted file mode 100644
index 7046476..0000000
--- a/connectors/camel-coap-kafka-connector/src/main/docs/camel-coap-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,64 +0,0 @@
-// kafka-connector options: START
-[[camel-coap-kafka-connector-sink]]
-= camel-coap-kafka-connector sink configuration
-
-Connector Description: Send and receive messages to/from COAP capable devices.
-
-When using camel-coap-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-coap-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.coap.CamelCoapSinkConnector
-----
-
-
-The camel-coap sink connector supports 13 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.uri* | The URI for the CoAP endpoint | null | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.alias* | Sets the alias used to query the KeyStore for the private key and certificate. This parameter is used when we are enabling TLS with certificates on the service side, and similarly on the client side when TLS is used with certificates and client authentication. If the parameter is not specified then the default behavior is to use the first alias in the keystore that contains a key entry. This configuration parameter does not apply to configuring TLS via a R [...]
-| *camel.sink.endpoint.cipherSuites* | Sets the cipherSuites String. This is a comma separated String of ciphersuites to configure. If it is not specified, then it falls back to getting the ciphersuites from the sslContextParameters object. | null | false | MEDIUM
-| *camel.sink.endpoint.clientAuthentication* | Sets the configuration options for server-side client-authentication requirements. The value must be one of NONE, WANT, REQUIRE. If this value is not specified, then it falls back to checking the sslContextParameters.getServerParameters().getClientAuthentication() value. | null | false | MEDIUM
-| *camel.sink.endpoint.privateKey* | Set the configured private key for use with Raw Public Key. | null | false | MEDIUM
-| *camel.sink.endpoint.pskStore* | Set the PskStore to use for pre-shared key. | null | false | MEDIUM
-| *camel.sink.endpoint.publicKey* | Set the configured public key for use with Raw Public Key. | null | false | MEDIUM
-| *camel.sink.endpoint.recommendedCipherSuitesOnly* | The CBC cipher suites are not recommended. If you want to use them, you first need to set the recommendedCipherSuitesOnly option to false. | true | false | MEDIUM
-| *camel.sink.endpoint.sslContextParameters* | Set the SSLContextParameters object for setting up TLS. This is required for coapstcp, and for coaps when we are using certificates for TLS (as opposed to RPK or PKS). | null | false | MEDIUM
-| *camel.sink.endpoint.trustedRpkStore* | Set the TrustedRpkStore to use to determine trust in raw public keys. | null | false | MEDIUM
-| *camel.component.coap.lazyStartProducer* | 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 cr [...]
-| *camel.component.coap.autowiredEnabled* | 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 | false | MEDIUM
-|===
-
-
-
-The camel-coap sink connector has no converters out of the box.
-
-
-
-
-
-The camel-coap sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-coap sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-coap-kafka-connector/src/main/docs/camel-coap-kafka-source-connector.adoc b/connectors/camel-coap-kafka-connector/src/main/docs/camel-coap-kafka-source-connector.adoc
deleted file mode 100644
index 549be5d..0000000
--- a/connectors/camel-coap-kafka-connector/src/main/docs/camel-coap-kafka-source-connector.adoc
+++ /dev/null
@@ -1,67 +0,0 @@
-// kafka-connector options: START
-[[camel-coap-kafka-connector-source]]
-= camel-coap-kafka-connector source configuration
-
-Connector description: Send and receive messages to/from COAP capable devices.
-
-When using camel-coap-kafka-connector as source make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-coap-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Source connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.coap.CamelCoapSourceConnector
-----
-
-
-The camel-coap source connector supports 16 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.source.path.uri* | The URI for the CoAP endpoint | null | false | MEDIUM
-| *camel.source.endpoint.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.source.endpoint.coapMethodRestrict* | Comma separated list of methods that the CoAP consumer will bind to. The default is to bind to all methods (DELETE, GET, POST, PUT). One of: [DELETE] [GET] [POST] [PUT] | null | false | MEDIUM
-| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | false | MEDIUM
-| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | false | MEDIUM
-| *camel.source.endpoint.alias* | Sets the alias used to query the KeyStore for the private key and certificate. This parameter is used when we are enabling TLS with certificates on the service side, and similarly on the client side when TLS is used with certificates and client authentication. If the parameter is not specified then the default behavior is to use the first alias in the keystore that contains a key entry. This configuration parameter does not apply to configuring TLS via a [...]
-| *camel.source.endpoint.cipherSuites* | Sets the cipherSuites String. This is a comma separated String of ciphersuites to configure. If it is not specified, then it falls back to getting the ciphersuites from the sslContextParameters object. | null | false | MEDIUM
-| *camel.source.endpoint.clientAuthentication* | Sets the configuration options for server-side client-authentication requirements. The value must be one of NONE, WANT, REQUIRE. If this value is not specified, then it falls back to checking the sslContextParameters.getServerParameters().getClientAuthentication() value. | null | false | MEDIUM
-| *camel.source.endpoint.privateKey* | Set the configured private key for use with Raw Public Key. | null | false | MEDIUM
-| *camel.source.endpoint.pskStore* | Set the PskStore to use for pre-shared key. | null | false | MEDIUM
-| *camel.source.endpoint.publicKey* | Set the configured public key for use with Raw Public Key. | null | false | MEDIUM
-| *camel.source.endpoint.recommendedCipherSuitesOnly* | The CBC cipher suites are not recommended. If you want to use them, you first need to set the recommendedCipherSuitesOnly option to false. | true | false | MEDIUM
-| *camel.source.endpoint.sslContextParameters* | Set the SSLContextParameters object for setting up TLS. This is required for coapstcp, and for coaps when we are using certificates for TLS (as opposed to RPK or PKS). | null | false | MEDIUM
-| *camel.source.endpoint.trustedRpkStore* | Set the TrustedRpkStore to use to determine trust in raw public keys. | null | false | MEDIUM
-| *camel.component.coap.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.component.coap.autowiredEnabled* | 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 | false | MEDIUM
-|===
-
-
-
-The camel-coap source connector has no converters out of the box.
-
-
-
-
-
-The camel-coap source connector has no transforms out of the box.
-
-
-
-
-
-The camel-coap source connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-coap-tcp-kafka-connector/src/main/docs/camel-coap+tcp-kafka-sink-connector.adoc b/connectors/camel-coap-tcp-kafka-connector/src/main/docs/camel-coap+tcp-kafka-sink-connector.adoc
deleted file mode 100644
index d7e8ce4..0000000
--- a/connectors/camel-coap-tcp-kafka-connector/src/main/docs/camel-coap+tcp-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,64 +0,0 @@
-// kafka-connector options: START
-[[camel-coap-tcp-kafka-connector-sink]]
-= camel-coap-tcp-kafka-connector sink configuration
-
-Connector Description: Send and receive messages to/from COAP capable devices.
-
-When using camel-coap-tcp-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-coap+tcp-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.coaptcp.CamelCoaptcpSinkConnector
-----
-
-
-The camel-coap-tcp sink connector supports 13 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.uri* | The URI for the CoAP endpoint | null | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.alias* | Sets the alias used to query the KeyStore for the private key and certificate. This parameter is used when we are enabling TLS with certificates on the service side, and similarly on the client side when TLS is used with certificates and client authentication. If the parameter is not specified then the default behavior is to use the first alias in the keystore that contains a key entry. This configuration parameter does not apply to configuring TLS via a R [...]
-| *camel.sink.endpoint.cipherSuites* | Sets the cipherSuites String. This is a comma separated String of ciphersuites to configure. If it is not specified, then it falls back to getting the ciphersuites from the sslContextParameters object. | null | false | MEDIUM
-| *camel.sink.endpoint.clientAuthentication* | Sets the configuration options for server-side client-authentication requirements. The value must be one of NONE, WANT, REQUIRE. If this value is not specified, then it falls back to checking the sslContextParameters.getServerParameters().getClientAuthentication() value. | null | false | MEDIUM
-| *camel.sink.endpoint.privateKey* | Set the configured private key for use with Raw Public Key. | null | false | MEDIUM
-| *camel.sink.endpoint.pskStore* | Set the PskStore to use for pre-shared key. | null | false | MEDIUM
-| *camel.sink.endpoint.publicKey* | Set the configured public key for use with Raw Public Key. | null | false | MEDIUM
-| *camel.sink.endpoint.recommendedCipherSuitesOnly* | The CBC cipher suites are not recommended. If you want to use them, you first need to set the recommendedCipherSuitesOnly option to false. | true | false | MEDIUM
-| *camel.sink.endpoint.sslContextParameters* | Set the SSLContextParameters object for setting up TLS. This is required for coapstcp, and for coaps when we are using certificates for TLS (as opposed to RPK or PKS). | null | false | MEDIUM
-| *camel.sink.endpoint.trustedRpkStore* | Set the TrustedRpkStore to use to determine trust in raw public keys. | null | false | MEDIUM
-| *camel.component.coap-tcp.lazyStartProducer* | 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.coap-tcp.autowiredEnabled* | 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 | false | MEDIUM
-|===
-
-
-
-The camel-coap-tcp sink connector has no converters out of the box.
-
-
-
-
-
-The camel-coap-tcp sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-coap-tcp sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-coap-tcp-kafka-connector/src/main/docs/camel-coap+tcp-kafka-source-connector.adoc b/connectors/camel-coap-tcp-kafka-connector/src/main/docs/camel-coap+tcp-kafka-source-connector.adoc
deleted file mode 100644
index bffaf6e..0000000
--- a/connectors/camel-coap-tcp-kafka-connector/src/main/docs/camel-coap+tcp-kafka-source-connector.adoc
+++ /dev/null
@@ -1,67 +0,0 @@
-// kafka-connector options: START
-[[camel-coap-tcp-kafka-connector-source]]
-= camel-coap-tcp-kafka-connector source configuration
-
-Connector description: Send and receive messages to/from COAP capable devices.
-
-When using camel-coap-tcp-kafka-connector as source make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-coap+tcp-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Source connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.coaptcp.CamelCoaptcpSourceConnector
-----
-
-
-The camel-coap-tcp source connector supports 16 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.source.path.uri* | The URI for the CoAP endpoint | null | false | MEDIUM
-| *camel.source.endpoint.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.source.endpoint.coapMethodRestrict* | Comma separated list of methods that the CoAP consumer will bind to. The default is to bind to all methods (DELETE, GET, POST, PUT). One of: [DELETE] [GET] [POST] [PUT] | null | false | MEDIUM
-| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | false | MEDIUM
-| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | false | MEDIUM
-| *camel.source.endpoint.alias* | Sets the alias used to query the KeyStore for the private key and certificate. This parameter is used when we are enabling TLS with certificates on the service side, and similarly on the client side when TLS is used with certificates and client authentication. If the parameter is not specified then the default behavior is to use the first alias in the keystore that contains a key entry. This configuration parameter does not apply to configuring TLS via a [...]
-| *camel.source.endpoint.cipherSuites* | Sets the cipherSuites String. This is a comma separated String of ciphersuites to configure. If it is not specified, then it falls back to getting the ciphersuites from the sslContextParameters object. | null | false | MEDIUM
-| *camel.source.endpoint.clientAuthentication* | Sets the configuration options for server-side client-authentication requirements. The value must be one of NONE, WANT, REQUIRE. If this value is not specified, then it falls back to checking the sslContextParameters.getServerParameters().getClientAuthentication() value. | null | false | MEDIUM
-| *camel.source.endpoint.privateKey* | Set the configured private key for use with Raw Public Key. | null | false | MEDIUM
-| *camel.source.endpoint.pskStore* | Set the PskStore to use for pre-shared key. | null | false | MEDIUM
-| *camel.source.endpoint.publicKey* | Set the configured public key for use with Raw Public Key. | null | false | MEDIUM
-| *camel.source.endpoint.recommendedCipherSuitesOnly* | The CBC cipher suites are not recommended. If you want to use them, you first need to set the recommendedCipherSuitesOnly option to false. | true | false | MEDIUM
-| *camel.source.endpoint.sslContextParameters* | Set the SSLContextParameters object for setting up TLS. This is required for coapstcp, and for coaps when we are using certificates for TLS (as opposed to RPK or PKS). | null | false | MEDIUM
-| *camel.source.endpoint.trustedRpkStore* | Set the TrustedRpkStore to use to determine trust in raw public keys. | null | false | MEDIUM
-| *camel.component.coap-tcp.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.component.coap-tcp.autowiredEnabled* | 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 | false | MEDIUM
-|===
-
-
-
-The camel-coap-tcp source connector has no converters out of the box.
-
-
-
-
-
-The camel-coap-tcp source connector has no transforms out of the box.
-
-
-
-
-
-The camel-coap-tcp source connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-coaps-kafka-connector/src/main/docs/camel-coaps-kafka-sink-connector.adoc b/connectors/camel-coaps-kafka-connector/src/main/docs/camel-coaps-kafka-sink-connector.adoc
deleted file mode 100644
index 38f76ff..0000000
--- a/connectors/camel-coaps-kafka-connector/src/main/docs/camel-coaps-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,64 +0,0 @@
-// kafka-connector options: START
-[[camel-coaps-kafka-connector-sink]]
-= camel-coaps-kafka-connector sink configuration
-
-Connector Description: Send and receive messages to/from COAP capable devices.
-
-When using camel-coaps-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-coaps-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.coaps.CamelCoapsSinkConnector
-----
-
-
-The camel-coaps sink connector supports 13 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.uri* | The URI for the CoAP endpoint | null | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.alias* | Sets the alias used to query the KeyStore for the private key and certificate. This parameter is used when we are enabling TLS with certificates on the service side, and similarly on the client side when TLS is used with certificates and client authentication. If the parameter is not specified then the default behavior is to use the first alias in the keystore that contains a key entry. This configuration parameter does not apply to configuring TLS via a R [...]
-| *camel.sink.endpoint.cipherSuites* | Sets the cipherSuites String. This is a comma separated String of ciphersuites to configure. If it is not specified, then it falls back to getting the ciphersuites from the sslContextParameters object. | null | false | MEDIUM
-| *camel.sink.endpoint.clientAuthentication* | Sets the configuration options for server-side client-authentication requirements. The value must be one of NONE, WANT, REQUIRE. If this value is not specified, then it falls back to checking the sslContextParameters.getServerParameters().getClientAuthentication() value. | null | false | MEDIUM
-| *camel.sink.endpoint.privateKey* | Set the configured private key for use with Raw Public Key. | null | false | MEDIUM
-| *camel.sink.endpoint.pskStore* | Set the PskStore to use for pre-shared key. | null | false | MEDIUM
-| *camel.sink.endpoint.publicKey* | Set the configured public key for use with Raw Public Key. | null | false | MEDIUM
-| *camel.sink.endpoint.recommendedCipherSuitesOnly* | The CBC cipher suites are not recommended. If you want to use them, you first need to set the recommendedCipherSuitesOnly option to false. | true | false | MEDIUM
-| *camel.sink.endpoint.sslContextParameters* | Set the SSLContextParameters object for setting up TLS. This is required for coapstcp, and for coaps when we are using certificates for TLS (as opposed to RPK or PKS). | null | false | MEDIUM
-| *camel.sink.endpoint.trustedRpkStore* | Set the TrustedRpkStore to use to determine trust in raw public keys. | null | false | MEDIUM
-| *camel.component.coaps.lazyStartProducer* | 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.coaps.autowiredEnabled* | 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 | false | MEDIUM
-|===
-
-
-
-The camel-coaps sink connector has no converters out of the box.
-
-
-
-
-
-The camel-coaps sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-coaps sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-coaps-kafka-connector/src/main/docs/camel-coaps-kafka-source-connector.adoc b/connectors/camel-coaps-kafka-connector/src/main/docs/camel-coaps-kafka-source-connector.adoc
deleted file mode 100644
index 1460d2d..0000000
--- a/connectors/camel-coaps-kafka-connector/src/main/docs/camel-coaps-kafka-source-connector.adoc
+++ /dev/null
@@ -1,67 +0,0 @@
-// kafka-connector options: START
-[[camel-coaps-kafka-connector-source]]
-= camel-coaps-kafka-connector source configuration
-
-Connector description: Send and receive messages to/from COAP capable devices.
-
-When using camel-coaps-kafka-connector as source make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-coaps-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Source connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.coaps.CamelCoapsSourceConnector
-----
-
-
-The camel-coaps source connector supports 16 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.source.path.uri* | The URI for the CoAP endpoint | null | false | MEDIUM
-| *camel.source.endpoint.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.source.endpoint.coapMethodRestrict* | Comma separated list of methods that the CoAP consumer will bind to. The default is to bind to all methods (DELETE, GET, POST, PUT). One of: [DELETE] [GET] [POST] [PUT] | null | false | MEDIUM
-| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | false | MEDIUM
-| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | false | MEDIUM
-| *camel.source.endpoint.alias* | Sets the alias used to query the KeyStore for the private key and certificate. This parameter is used when we are enabling TLS with certificates on the service side, and similarly on the client side when TLS is used with certificates and client authentication. If the parameter is not specified then the default behavior is to use the first alias in the keystore that contains a key entry. This configuration parameter does not apply to configuring TLS via a [...]
-| *camel.source.endpoint.cipherSuites* | Sets the cipherSuites String. This is a comma separated String of ciphersuites to configure. If it is not specified, then it falls back to getting the ciphersuites from the sslContextParameters object. | null | false | MEDIUM
-| *camel.source.endpoint.clientAuthentication* | Sets the configuration options for server-side client-authentication requirements. The value must be one of NONE, WANT, REQUIRE. If this value is not specified, then it falls back to checking the sslContextParameters.getServerParameters().getClientAuthentication() value. | null | false | MEDIUM
-| *camel.source.endpoint.privateKey* | Set the configured private key for use with Raw Public Key. | null | false | MEDIUM
-| *camel.source.endpoint.pskStore* | Set the PskStore to use for pre-shared key. | null | false | MEDIUM
-| *camel.source.endpoint.publicKey* | Set the configured public key for use with Raw Public Key. | null | false | MEDIUM
-| *camel.source.endpoint.recommendedCipherSuitesOnly* | The CBC cipher suites are not recommended. If you want to use them, you first need to set the recommendedCipherSuitesOnly option to false. | true | false | MEDIUM
-| *camel.source.endpoint.sslContextParameters* | Set the SSLContextParameters object for setting up TLS. This is required for coapstcp, and for coaps when we are using certificates for TLS (as opposed to RPK or PKS). | null | false | MEDIUM
-| *camel.source.endpoint.trustedRpkStore* | Set the TrustedRpkStore to use to determine trust in raw public keys. | null | false | MEDIUM
-| *camel.component.coaps.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.component.coaps.autowiredEnabled* | 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 | false | MEDIUM
-|===
-
-
-
-The camel-coaps source connector has no converters out of the box.
-
-
-
-
-
-The camel-coaps source connector has no transforms out of the box.
-
-
-
-
-
-The camel-coaps source connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-coaps-tcp-kafka-connector/src/main/docs/camel-coaps+tcp-kafka-sink-connector.adoc b/connectors/camel-coaps-tcp-kafka-connector/src/main/docs/camel-coaps+tcp-kafka-sink-connector.adoc
deleted file mode 100644
index 2a0b06c..0000000
--- a/connectors/camel-coaps-tcp-kafka-connector/src/main/docs/camel-coaps+tcp-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,64 +0,0 @@
-// kafka-connector options: START
-[[camel-coaps-tcp-kafka-connector-sink]]
-= camel-coaps-tcp-kafka-connector sink configuration
-
-Connector Description: Send and receive messages to/from COAP capable devices.
-
-When using camel-coaps-tcp-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-coaps+tcp-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.coapstcp.CamelCoapstcpSinkConnector
-----
-
-
-The camel-coaps-tcp sink connector supports 13 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.uri* | The URI for the CoAP endpoint | null | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.alias* | Sets the alias used to query the KeyStore for the private key and certificate. This parameter is used when we are enabling TLS with certificates on the service side, and similarly on the client side when TLS is used with certificates and client authentication. If the parameter is not specified then the default behavior is to use the first alias in the keystore that contains a key entry. This configuration parameter does not apply to configuring TLS via a R [...]
-| *camel.sink.endpoint.cipherSuites* | Sets the cipherSuites String. This is a comma separated String of ciphersuites to configure. If it is not specified, then it falls back to getting the ciphersuites from the sslContextParameters object. | null | false | MEDIUM
-| *camel.sink.endpoint.clientAuthentication* | Sets the configuration options for server-side client-authentication requirements. The value must be one of NONE, WANT, REQUIRE. If this value is not specified, then it falls back to checking the sslContextParameters.getServerParameters().getClientAuthentication() value. | null | false | MEDIUM
-| *camel.sink.endpoint.privateKey* | Set the configured private key for use with Raw Public Key. | null | false | MEDIUM
-| *camel.sink.endpoint.pskStore* | Set the PskStore to use for pre-shared key. | null | false | MEDIUM
-| *camel.sink.endpoint.publicKey* | Set the configured public key for use with Raw Public Key. | null | false | MEDIUM
-| *camel.sink.endpoint.recommendedCipherSuitesOnly* | The CBC cipher suites are not recommended. If you want to use them, you first need to set the recommendedCipherSuitesOnly option to false. | true | false | MEDIUM
-| *camel.sink.endpoint.sslContextParameters* | Set the SSLContextParameters object for setting up TLS. This is required for coapstcp, and for coaps when we are using certificates for TLS (as opposed to RPK or PKS). | null | false | MEDIUM
-| *camel.sink.endpoint.trustedRpkStore* | Set the TrustedRpkStore to use to determine trust in raw public keys. | null | false | MEDIUM
-| *camel.component.coaps-tcp.lazyStartProducer* | 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.coaps-tcp.autowiredEnabled* | 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 | false | MEDIUM
-|===
-
-
-
-The camel-coaps-tcp sink connector has no converters out of the box.
-
-
-
-
-
-The camel-coaps-tcp sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-coaps-tcp sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-coaps-tcp-kafka-connector/src/main/docs/camel-coaps+tcp-kafka-source-connector.adoc b/connectors/camel-coaps-tcp-kafka-connector/src/main/docs/camel-coaps+tcp-kafka-source-connector.adoc
deleted file mode 100644
index 0c6caa9..0000000
--- a/connectors/camel-coaps-tcp-kafka-connector/src/main/docs/camel-coaps+tcp-kafka-source-connector.adoc
+++ /dev/null
@@ -1,67 +0,0 @@
-// kafka-connector options: START
-[[camel-coaps-tcp-kafka-connector-source]]
-= camel-coaps-tcp-kafka-connector source configuration
-
-Connector description: Send and receive messages to/from COAP capable devices.
-
-When using camel-coaps-tcp-kafka-connector as source make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-coaps+tcp-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Source connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.coapstcp.CamelCoapstcpSourceConnector
-----
-
-
-The camel-coaps-tcp source connector supports 16 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.source.path.uri* | The URI for the CoAP endpoint | null | false | MEDIUM
-| *camel.source.endpoint.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.source.endpoint.coapMethodRestrict* | Comma separated list of methods that the CoAP consumer will bind to. The default is to bind to all methods (DELETE, GET, POST, PUT). One of: [DELETE] [GET] [POST] [PUT] | null | false | MEDIUM
-| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | false | MEDIUM
-| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | false | MEDIUM
-| *camel.source.endpoint.alias* | Sets the alias used to query the KeyStore for the private key and certificate. This parameter is used when we are enabling TLS with certificates on the service side, and similarly on the client side when TLS is used with certificates and client authentication. If the parameter is not specified then the default behavior is to use the first alias in the keystore that contains a key entry. This configuration parameter does not apply to configuring TLS via a [...]
-| *camel.source.endpoint.cipherSuites* | Sets the cipherSuites String. This is a comma separated String of ciphersuites to configure. If it is not specified, then it falls back to getting the ciphersuites from the sslContextParameters object. | null | false | MEDIUM
-| *camel.source.endpoint.clientAuthentication* | Sets the configuration options for server-side client-authentication requirements. The value must be one of NONE, WANT, REQUIRE. If this value is not specified, then it falls back to checking the sslContextParameters.getServerParameters().getClientAuthentication() value. | null | false | MEDIUM
-| *camel.source.endpoint.privateKey* | Set the configured private key for use with Raw Public Key. | null | false | MEDIUM
-| *camel.source.endpoint.pskStore* | Set the PskStore to use for pre-shared key. | null | false | MEDIUM
-| *camel.source.endpoint.publicKey* | Set the configured public key for use with Raw Public Key. | null | false | MEDIUM
-| *camel.source.endpoint.recommendedCipherSuitesOnly* | The CBC cipher suites are not recommended. If you want to use them, you first need to set the recommendedCipherSuitesOnly option to false. | true | false | MEDIUM
-| *camel.source.endpoint.sslContextParameters* | Set the SSLContextParameters object for setting up TLS. This is required for coapstcp, and for coaps when we are using certificates for TLS (as opposed to RPK or PKS). | null | false | MEDIUM
-| *camel.source.endpoint.trustedRpkStore* | Set the TrustedRpkStore to use to determine trust in raw public keys. | null | false | MEDIUM
-| *camel.component.coaps-tcp.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.component.coaps-tcp.autowiredEnabled* | 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 | false | MEDIUM
-|===
-
-
-
-The camel-coaps-tcp source connector has no converters out of the box.
-
-
-
-
-
-The camel-coaps-tcp source connector has no transforms out of the box.
-
-
-
-
-
-The camel-coaps-tcp source connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-cometd-kafka-connector/src/main/docs/camel-cometd-kafka-sink-connector.adoc b/connectors/camel-cometd-kafka-connector/src/main/docs/camel-cometd-kafka-sink-connector.adoc
deleted file mode 100644
index 13e3907..0000000
--- a/connectors/camel-cometd-kafka-connector/src/main/docs/camel-cometd-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,75 +0,0 @@
-// kafka-connector options: START
-[[camel-cometd-kafka-connector-sink]]
-= camel-cometd-kafka-connector sink configuration
-
-Connector Description: Offers publish/subscribe, peer-to-peer (via a server), and RPC style messaging using the CometD/Bayeux protocol.
-
-When using camel-cometd-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-cometd-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.cometd.CamelCometdSinkConnector
-----
-
-
-The camel-cometd sink connector supports 24 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.host* | Hostname | null | true | HIGH
-| *camel.sink.path.port* | Host port number | null | true | HIGH
-| *camel.sink.path.channelName* | The channelName represents a topic that can be subscribed to by the Camel endpoints. | null | true | HIGH
-| *camel.sink.endpoint.allowedOrigins* | The origins domain that support to cross, if the crosssOriginFilterOn is true | "*" | false | MEDIUM
-| *camel.sink.endpoint.baseResource* | The root directory for the web resources or classpath. Use the protocol file: or classpath: depending if you want that the component loads the resource from file system or classpath. Classpath is required for OSGI deployment where the resources are packaged in the jar | null | false | MEDIUM
-| *camel.sink.endpoint.crossOriginFilterOn* | If true, the server will support for cross-domain filtering | false | false | MEDIUM
-| *camel.sink.endpoint.filterPath* | The filterPath will be used by the CrossOriginFilter, if the crosssOriginFilterOn is true | null | false | MEDIUM
-| *camel.sink.endpoint.interval* | The client side poll timeout in milliseconds. How long a client will wait between reconnects | null | false | MEDIUM
-| *camel.sink.endpoint.jsonCommented* | If true, the server will accept JSON wrapped in a comment and will generate JSON wrapped in a comment. This is a defence against Ajax Hijacking. | true | false | MEDIUM
-| *camel.sink.endpoint.logLevel* | Logging level. 0=none, 1=info, 2=debug. One of: [0] [1] [2] | 1 | false | MEDIUM
-| *camel.sink.endpoint.maxInterval* | The max client side poll timeout in milliseconds. A client will be removed if a connection is not received in this time. | 30000 | false | MEDIUM
-| *camel.sink.endpoint.multiFrameInterval* | The client side poll timeout, if multiple connections are detected from the same browser. | 1500 | false | MEDIUM
-| *camel.sink.endpoint.timeout* | The server side poll timeout in milliseconds. This is how long the server will hold a reconnect request before responding. | 240000 | false | MEDIUM
-| *camel.sink.endpoint.disconnectLocalSession* | Whether to disconnect local sessions after publishing a message to its channel. Disconnecting local session is needed as they are not swept by default by CometD, and therefore you can run out of memory. | false | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.component.cometd.lazyStartProducer* | 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.cometd.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.cometd.extensions* | To use a list of custom BayeuxServer.Extension that allows modifying incoming and outgoing requests. | null | false | MEDIUM
-| *camel.component.cometd.securityPolicy* | To use a custom configured SecurityPolicy to control authorization | null | false | MEDIUM
-| *camel.component.cometd.sslContextParameters* | To configure security using SSLContextParameters | null | false | MEDIUM
-| *camel.component.cometd.sslKeyPassword* | The password for the keystore when using SSL. | null | false | MEDIUM
-| *camel.component.cometd.sslKeystore* | The path to the keystore. | null | false | MEDIUM
-| *camel.component.cometd.sslPassword* | The password when using SSL. | null | false | MEDIUM
-| *camel.component.cometd.useGlobalSslContext Parameters* | Enable usage of global SSL context parameters. | false | false | MEDIUM
-|===
-
-
-
-The camel-cometd sink connector has no converters out of the box.
-
-
-
-
-
-The camel-cometd sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-cometd sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-cometd-kafka-connector/src/main/docs/camel-cometd-kafka-source-connector.adoc b/connectors/camel-cometd-kafka-connector/src/main/docs/camel-cometd-kafka-source-connector.adoc
deleted file mode 100644
index dd7dad2..0000000
--- a/connectors/camel-cometd-kafka-connector/src/main/docs/camel-cometd-kafka-source-connector.adoc
+++ /dev/null
@@ -1,77 +0,0 @@
-// kafka-connector options: START
-[[camel-cometd-kafka-connector-source]]
-= camel-cometd-kafka-connector source configuration
-
-Connector description: Offers publish/subscribe, peer-to-peer (via a server), and RPC style messaging using the CometD/Bayeux protocol.
-
-When using camel-cometd-kafka-connector as source make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-cometd-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Source connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.cometd.CamelCometdSourceConnector
-----
-
-
-The camel-cometd source connector supports 26 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.source.path.host* | Hostname | null | true | HIGH
-| *camel.source.path.port* | Host port number | null | true | HIGH
-| *camel.source.path.channelName* | The channelName represents a topic that can be subscribed to by the Camel endpoints. | null | true | HIGH
-| *camel.source.endpoint.allowedOrigins* | The origins domain that support to cross, if the crosssOriginFilterOn is true | "*" | false | MEDIUM
-| *camel.source.endpoint.baseResource* | The root directory for the web resources or classpath. Use the protocol file: or classpath: depending if you want that the component loads the resource from file system or classpath. Classpath is required for OSGI deployment where the resources are packaged in the jar | null | false | MEDIUM
-| *camel.source.endpoint.crossOriginFilterOn* | If true, the server will support for cross-domain filtering | false | false | MEDIUM
-| *camel.source.endpoint.filterPath* | The filterPath will be used by the CrossOriginFilter, if the crosssOriginFilterOn is true | null | false | MEDIUM
-| *camel.source.endpoint.interval* | The client side poll timeout in milliseconds. How long a client will wait between reconnects | null | false | MEDIUM
-| *camel.source.endpoint.jsonCommented* | If true, the server will accept JSON wrapped in a comment and will generate JSON wrapped in a comment. This is a defence against Ajax Hijacking. | true | false | MEDIUM
-| *camel.source.endpoint.logLevel* | Logging level. 0=none, 1=info, 2=debug. One of: [0] [1] [2] | 1 | false | MEDIUM
-| *camel.source.endpoint.maxInterval* | The max client side poll timeout in milliseconds. A client will be removed if a connection is not received in this time. | 30000 | false | MEDIUM
-| *camel.source.endpoint.multiFrameInterval* | The client side poll timeout, if multiple connections are detected from the same browser. | 1500 | false | MEDIUM
-| *camel.source.endpoint.timeout* | The server side poll timeout in milliseconds. This is how long the server will hold a reconnect request before responding. | 240000 | false | MEDIUM
-| *camel.source.endpoint.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.source.endpoint.sessionHeadersEnabled* | Whether to include the server session headers in the Camel message when creating a Camel Message for incoming requests. | false | false | MEDIUM
-| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | false | MEDIUM
-| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | false | MEDIUM
-| *camel.component.cometd.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.component.cometd.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.cometd.extensions* | To use a list of custom BayeuxServer.Extension that allows modifying incoming and outgoing requests. | null | false | MEDIUM
-| *camel.component.cometd.securityPolicy* | To use a custom configured SecurityPolicy to control authorization | null | false | MEDIUM
-| *camel.component.cometd.sslContextParameters* | To configure security using SSLContextParameters | null | false | MEDIUM
-| *camel.component.cometd.sslKeyPassword* | The password for the keystore when using SSL. | null | false | MEDIUM
-| *camel.component.cometd.sslKeystore* | The path to the keystore. | null | false | MEDIUM
-| *camel.component.cometd.sslPassword* | The password when using SSL. | null | false | MEDIUM
-| *camel.component.cometd.useGlobalSslContext Parameters* | Enable usage of global SSL context parameters. | false | false | MEDIUM
-|===
-
-
-
-The camel-cometd source connector has no converters out of the box.
-
-
-
-
-
-The camel-cometd source connector has no transforms out of the box.
-
-
-
-
-
-The camel-cometd source connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-cometds-kafka-connector/src/main/docs/camel-cometds-kafka-sink-connector.adoc b/connectors/camel-cometds-kafka-connector/src/main/docs/camel-cometds-kafka-sink-connector.adoc
deleted file mode 100644
index d43381c..0000000
--- a/connectors/camel-cometds-kafka-connector/src/main/docs/camel-cometds-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,75 +0,0 @@
-// kafka-connector options: START
-[[camel-cometds-kafka-connector-sink]]
-= camel-cometds-kafka-connector sink configuration
-
-Connector Description: Offers publish/subscribe, peer-to-peer (via a server), and RPC style messaging using the CometD/Bayeux protocol.
-
-When using camel-cometds-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-cometds-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.cometds.CamelCometdsSinkConnector
-----
-
-
-The camel-cometds sink connector supports 24 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.host* | Hostname | null | true | HIGH
-| *camel.sink.path.port* | Host port number | null | true | HIGH
-| *camel.sink.path.channelName* | The channelName represents a topic that can be subscribed to by the Camel endpoints. | null | true | HIGH
-| *camel.sink.endpoint.allowedOrigins* | The origins domain that support to cross, if the crosssOriginFilterOn is true | "*" | false | MEDIUM
-| *camel.sink.endpoint.baseResource* | The root directory for the web resources or classpath. Use the protocol file: or classpath: depending if you want that the component loads the resource from file system or classpath. Classpath is required for OSGI deployment where the resources are packaged in the jar | null | false | MEDIUM
-| *camel.sink.endpoint.crossOriginFilterOn* | If true, the server will support for cross-domain filtering | false | false | MEDIUM
-| *camel.sink.endpoint.filterPath* | The filterPath will be used by the CrossOriginFilter, if the crosssOriginFilterOn is true | null | false | MEDIUM
-| *camel.sink.endpoint.interval* | The client side poll timeout in milliseconds. How long a client will wait between reconnects | null | false | MEDIUM
-| *camel.sink.endpoint.jsonCommented* | If true, the server will accept JSON wrapped in a comment and will generate JSON wrapped in a comment. This is a defence against Ajax Hijacking. | true | false | MEDIUM
-| *camel.sink.endpoint.logLevel* | Logging level. 0=none, 1=info, 2=debug. One of: [0] [1] [2] | 1 | false | MEDIUM
-| *camel.sink.endpoint.maxInterval* | The max client side poll timeout in milliseconds. A client will be removed if a connection is not received in this time. | 30000 | false | MEDIUM
-| *camel.sink.endpoint.multiFrameInterval* | The client side poll timeout, if multiple connections are detected from the same browser. | 1500 | false | MEDIUM
-| *camel.sink.endpoint.timeout* | The server side poll timeout in milliseconds. This is how long the server will hold a reconnect request before responding. | 240000 | false | MEDIUM
-| *camel.sink.endpoint.disconnectLocalSession* | Whether to disconnect local sessions after publishing a message to its channel. Disconnecting local session is needed as they are not swept by default by CometD, and therefore you can run out of memory. | false | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.component.cometds.lazyStartProducer* | 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.cometds.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.cometds.extensions* | To use a list of custom BayeuxServer.Extension that allows modifying incoming and outgoing requests. | null | false | MEDIUM
-| *camel.component.cometds.securityPolicy* | To use a custom configured SecurityPolicy to control authorization | null | false | MEDIUM
-| *camel.component.cometds.sslContextParameters* | To configure security using SSLContextParameters | null | false | MEDIUM
-| *camel.component.cometds.sslKeyPassword* | The password for the keystore when using SSL. | null | false | MEDIUM
-| *camel.component.cometds.sslKeystore* | The path to the keystore. | null | false | MEDIUM
-| *camel.component.cometds.sslPassword* | The password when using SSL. | null | false | MEDIUM
-| *camel.component.cometds.useGlobalSslContext Parameters* | Enable usage of global SSL context parameters. | false | false | MEDIUM
-|===
-
-
-
-The camel-cometds sink connector has no converters out of the box.
-
-
-
-
-
-The camel-cometds sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-cometds sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-cometds-kafka-connector/src/main/docs/camel-cometds-kafka-source-connector.adoc b/connectors/camel-cometds-kafka-connector/src/main/docs/camel-cometds-kafka-source-connector.adoc
deleted file mode 100644
index 074e36d..0000000
--- a/connectors/camel-cometds-kafka-connector/src/main/docs/camel-cometds-kafka-source-connector.adoc
+++ /dev/null
@@ -1,77 +0,0 @@
-// kafka-connector options: START
-[[camel-cometds-kafka-connector-source]]
-= camel-cometds-kafka-connector source configuration
-
-Connector description: Offers publish/subscribe, peer-to-peer (via a server), and RPC style messaging using the CometD/Bayeux protocol.
-
-When using camel-cometds-kafka-connector as source make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-cometds-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Source connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.cometds.CamelCometdsSourceConnector
-----
-
-
-The camel-cometds source connector supports 26 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.source.path.host* | Hostname | null | true | HIGH
-| *camel.source.path.port* | Host port number | null | true | HIGH
-| *camel.source.path.channelName* | The channelName represents a topic that can be subscribed to by the Camel endpoints. | null | true | HIGH
-| *camel.source.endpoint.allowedOrigins* | The origins domain that support to cross, if the crosssOriginFilterOn is true | "*" | false | MEDIUM
-| *camel.source.endpoint.baseResource* | The root directory for the web resources or classpath. Use the protocol file: or classpath: depending if you want that the component loads the resource from file system or classpath. Classpath is required for OSGI deployment where the resources are packaged in the jar | null | false | MEDIUM
-| *camel.source.endpoint.crossOriginFilterOn* | If true, the server will support for cross-domain filtering | false | false | MEDIUM
-| *camel.source.endpoint.filterPath* | The filterPath will be used by the CrossOriginFilter, if the crosssOriginFilterOn is true | null | false | MEDIUM
-| *camel.source.endpoint.interval* | The client side poll timeout in milliseconds. How long a client will wait between reconnects | null | false | MEDIUM
-| *camel.source.endpoint.jsonCommented* | If true, the server will accept JSON wrapped in a comment and will generate JSON wrapped in a comment. This is a defence against Ajax Hijacking. | true | false | MEDIUM
-| *camel.source.endpoint.logLevel* | Logging level. 0=none, 1=info, 2=debug. One of: [0] [1] [2] | 1 | false | MEDIUM
-| *camel.source.endpoint.maxInterval* | The max client side poll timeout in milliseconds. A client will be removed if a connection is not received in this time. | 30000 | false | MEDIUM
-| *camel.source.endpoint.multiFrameInterval* | The client side poll timeout, if multiple connections are detected from the same browser. | 1500 | false | MEDIUM
-| *camel.source.endpoint.timeout* | The server side poll timeout in milliseconds. This is how long the server will hold a reconnect request before responding. | 240000 | false | MEDIUM
-| *camel.source.endpoint.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.source.endpoint.sessionHeadersEnabled* | Whether to include the server session headers in the Camel message when creating a Camel Message for incoming requests. | false | false | MEDIUM
-| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | false | MEDIUM
-| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | false | MEDIUM
-| *camel.component.cometds.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.component.cometds.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.cometds.extensions* | To use a list of custom BayeuxServer.Extension that allows modifying incoming and outgoing requests. | null | false | MEDIUM
-| *camel.component.cometds.securityPolicy* | To use a custom configured SecurityPolicy to control authorization | null | false | MEDIUM
-| *camel.component.cometds.sslContextParameters* | To configure security using SSLContextParameters | null | false | MEDIUM
-| *camel.component.cometds.sslKeyPassword* | The password for the keystore when using SSL. | null | false | MEDIUM
-| *camel.component.cometds.sslKeystore* | The path to the keystore. | null | false | MEDIUM
-| *camel.component.cometds.sslPassword* | The password when using SSL. | null | false | MEDIUM
-| *camel.component.cometds.useGlobalSslContext Parameters* | Enable usage of global SSL context parameters. | false | false | MEDIUM
-|===
-
-
-
-The camel-cometds source connector has no converters out of the box.
-
-
-
-
-
-The camel-cometds source connector has no transforms out of the box.
-
-
-
-
-
-The camel-cometds source connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-consul-kafka-connector/src/main/docs/camel-consul-kafka-sink-connector.adoc b/connectors/camel-consul-kafka-connector/src/main/docs/camel-consul-kafka-sink-connector.adoc
deleted file mode 100644
index f3e446c..0000000
--- a/connectors/camel-consul-kafka-connector/src/main/docs/camel-consul-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,99 +0,0 @@
-// kafka-connector options: START
-[[camel-consul-kafka-connector-sink]]
-= camel-consul-kafka-connector sink configuration
-
-Connector Description: Integrate with Consul service discovery and configuration store.
-
-When using camel-consul-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-consul-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.consul.CamelConsulSinkConnector
-----
-
-
-The camel-consul sink connector supports 48 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.sink.path.apiEndpoint* | The API endpoint | null | true | HIGH
-| *camel.sink.endpoint.connectTimeout* | Connect timeout for OkHttpClient | null | false | MEDIUM
-| *camel.sink.endpoint.connectTimeoutMillis* | Connect timeout for OkHttpClient. Deprecation note: Use connectTimeout instead | null | false | LOW
-| *camel.sink.endpoint.consulClient* | Reference to a com.orbitz.consul.Consul in the registry. | null | false | MEDIUM
-| *camel.sink.endpoint.key* | The default key. Can be overridden by CamelConsulKey | null | false | MEDIUM
-| *camel.sink.endpoint.pingInstance* | Configure if the AgentClient should attempt a ping before returning the Consul instance | true | false | MEDIUM
-| *camel.sink.endpoint.readTimeout* | Read timeout for OkHttpClient | null | false | MEDIUM
-| *camel.sink.endpoint.readTimeoutMillis* | Read timeout for OkHttpClient. Deprecation note: Use readTimeout instead | null | false | LOW
-| *camel.sink.endpoint.tags* | Set tags. You can separate multiple tags by comma. | null | false | MEDIUM
-| *camel.sink.endpoint.url* | The Consul agent URL | null | false | MEDIUM
-| *camel.sink.endpoint.writeTimeout* | Write timeout for OkHttpClient | null | false | MEDIUM
-| *camel.sink.endpoint.writeTimeoutMillis* | Write timeout for OkHttpClient. Deprecation note: Use writeTimeout instead | null | false | LOW
-| *camel.sink.endpoint.action* | The default action. Can be overridden by CamelConsulAction | null | false | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | 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 cre [...]
-| *camel.sink.endpoint.valueAsString* | Default to transform values retrieved from Consul i.e. on KV endpoint to string. | false | false | MEDIUM
-| *camel.sink.endpoint.consistencyMode* | The consistencyMode used for queries, default ConsistencyMode.DEFAULT One of: [DEFAULT] [STALE] [CONSISTENT] | "DEFAULT" | false | MEDIUM
-| *camel.sink.endpoint.datacenter* | The data center | null | false | MEDIUM
-| *camel.sink.endpoint.nearNode* | The near node to use for queries. | null | false | MEDIUM
-| *camel.sink.endpoint.nodeMeta* | The note meta-data to use for queries. | null | false | MEDIUM
-| *camel.sink.endpoint.aclToken* | Sets the ACL token to be used with Consul | null | false | MEDIUM
-| *camel.sink.endpoint.password* | Sets the password to be used for basic authentication | null | false | MEDIUM
-| *camel.sink.endpoint.sslContextParameters* | SSL configuration using an org.apache.camel.support.jsse.SSLContextParameters instance. | null | false | MEDIUM
-| *camel.sink.endpoint.userName* | Sets the username to be used for basic authentication | null | false | MEDIUM
-| *camel.component.consul.connectTimeout* | Connect timeout for OkHttpClient | null | false | MEDIUM
-| *camel.component.consul.connectTimeoutMillis* | Connect timeout for OkHttpClient. Deprecation note: Use connectTimeout instead | null | false | LOW
-| *camel.component.consul.consulClient* | Reference to a com.orbitz.consul.Consul in the registry. | null | false | MEDIUM
-| *camel.component.consul.key* | The default key. Can be overridden by CamelConsulKey | null | false | MEDIUM
-| *camel.component.consul.pingInstance* | Configure if the AgentClient should attempt a ping before returning the Consul instance | true | false | MEDIUM
-| *camel.component.consul.readTimeout* | Read timeout for OkHttpClient | null | false | MEDIUM
-| *camel.component.consul.readTimeoutMillis* | Read timeout for OkHttpClient. Deprecation note: Use readTimeout instead | null | false | LOW
-| *camel.component.consul.tags* | Set tags. You can separate multiple tags by comma. | null | false | MEDIUM
-| *camel.component.consul.url* | The Consul agent URL | null | false | MEDIUM
-| *camel.component.consul.writeTimeout* | Write timeout for OkHttpClient | null | false | MEDIUM
-| *camel.component.consul.writeTimeoutMillis* | Write timeout for OkHttpClient. Deprecation note: Use writeTimeout instead | null | false | LOW
-| *camel.component.consul.action* | The default action. Can be overridden by CamelConsulAction | null | false | MEDIUM
-| *camel.component.consul.lazyStartProducer* | 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.consul.valueAsString* | Default to transform values retrieved from Consul i.e. on KV endpoint to string. | false | false | MEDIUM
-| *camel.component.consul.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.consul.configuration* | Consul configuration | null | false | MEDIUM
-| *camel.component.consul.consistencyMode* | The consistencyMode used for queries, default ConsistencyMode.DEFAULT One of: [DEFAULT] [STALE] [CONSISTENT] | "DEFAULT" | false | MEDIUM
-| *camel.component.consul.datacenter* | The data center | null | false | MEDIUM
-| *camel.component.consul.nearNode* | The near node to use for queries. | null | false | MEDIUM
-| *camel.component.consul.nodeMeta* | The note meta-data to use for queries. | null | false | MEDIUM
-| *camel.component.consul.aclToken* | Sets the ACL token to be used with Consul | null | false | MEDIUM
-| *camel.component.consul.password* | Sets the password to be used for basic authentication | null | false | MEDIUM
-| *camel.component.consul.sslContextParameters* | SSL configuration using an org.apache.camel.support.jsse.SSLContextParameters instance. | null | false | MEDIUM
-| *camel.component.consul.useGlobalSslContext Parameters* | Enable usage of global SSL context parameters. | false | false | MEDIUM
-| *camel.component.consul.userName* | Sets the username to be used for basic authentication | null | false | MEDIUM
-|===
-
-
-
-The camel-consul sink connector has no converters out of the box.
-
-
-
-
-
-The camel-consul sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-consul sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/connectors/camel-consul-kafka-connector/src/main/docs/camel-consul-kafka-source-connector.adoc b/connectors/camel-consul-kafka-connector/src/main/docs/camel-consul-kafka-source-connector.adoc
deleted file mode 100644
index fbb45fb..0000000
--- a/connectors/camel-consul-kafka-connector/src/main/docs/camel-consul-kafka-source-connector.adoc
+++ /dev/null
@@ -1,103 +0,0 @@
-// kafka-connector options: START
-[[camel-consul-kafka-connector-source]]
-= camel-consul-kafka-connector source configuration
-
-Connector description: Integrate with Consul service discovery and configuration store.
-
-When using camel-consul-kafka-connector as source make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-consul-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Source connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.consul.CamelConsulSourceConnector
-----
-
-
-The camel-consul source connector supports 52 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,1,1",options="header"]
-|===
-| Name | Description | Default | Required | Priority
-| *camel.source.path.apiEndpoint* | The API endpoint | null | true | HIGH
-| *camel.source.endpoint.connectTimeout* | Connect timeout for OkHttpClient | null | false | MEDIUM
-| *camel.source.endpoint.connectTimeoutMillis* | Connect timeout for OkHttpClient. Deprecation note: Use connectTimeout instead | null | false | LOW
-| *camel.source.endpoint.consulClient* | Reference to a com.orbitz.consul.Consul in the registry. | null | false | MEDIUM
-| *camel.source.endpoint.key* | The default key. Can be overridden by CamelConsulKey | null | false | MEDIUM
-| *camel.source.endpoint.pingInstance* | Configure if the AgentClient should attempt a ping before returning the Consul instance | true | false | MEDIUM
-| *camel.source.endpoint.readTimeout* | Read timeout for OkHttpClient | null | false | MEDIUM
-| *camel.source.endpoint.readTimeoutMillis* | Read timeout for OkHttpClient. Deprecation note: Use readTimeout instead | null | false | LOW
-| *camel.source.endpoint.tags* | Set tags. You can separate multiple tags by comma. | null | false | MEDIUM
-| *camel.source.endpoint.url* | The Consul agent URL | null | false | MEDIUM
-| *camel.source.endpoint.writeTimeout* | Write timeout for OkHttpClient | null | false | MEDIUM
-| *camel.source.endpoint.writeTimeoutMillis* | Write timeout for OkHttpClient. Deprecation note: Use writeTimeout instead | null | false | LOW
-| *camel.source.endpoint.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | false | MEDIUM
-| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | false | MEDIUM
-| *camel.source.endpoint.consistencyMode* | The consistencyMode used for queries, default ConsistencyMode.DEFAULT One of: [DEFAULT] [STALE] [CONSISTENT] | "DEFAULT" | false | MEDIUM
-| *camel.source.endpoint.datacenter* | The data center | null | false | MEDIUM
-| *camel.source.endpoint.nearNode* | The near node to use for queries. | null | false | MEDIUM
-| *camel.source.endpoint.nodeMeta* | The note meta-data to use for queries. | null | false | MEDIUM
-| *camel.source.endpoint.aclToken* | Sets the ACL token to be used with Consul | null | false | MEDIUM
-| *camel.source.endpoint.password* | Sets the password to be used for basic authentication | null | false | MEDIUM
-| *camel.source.endpoint.sslContextParameters* | SSL configuration using an org.apache.camel.support.jsse.SSLContextParameters instance. | null | false | MEDIUM
-| *camel.source.endpoint.userName* | Sets the username to be used for basic authentication | null | false | MEDIUM
-| *camel.source.endpoint.blockSeconds* | The second to wait for a watch event, default 10 seconds | "10" | false | MEDIUM
-| *camel.source.endpoint.firstIndex* | The first index for watch for, default 0 | "0" | false | MEDIUM
-| *camel.source.endpoint.recursive* | Recursively watch, default false | false | false | MEDIUM
-| *camel.component.consul.connectTimeout* | Connect timeout for OkHttpClient | null | false | MEDIUM
-| *camel.component.consul.connectTimeoutMillis* | Connect timeout for OkHttpClient. Deprecation note: Use connectTimeout instead | null | false | LOW
-| *camel.component.consul.consulClient* | Reference to a com.orbitz.consul.Consul in the registry. | null | false | MEDIUM
-| *camel.component.consul.key* | The default key. Can be overridden by CamelConsulKey | null | false | MEDIUM
-| *camel.component.consul.pingInstance* | Configure if the AgentClient should attempt a ping before returning the Consul instance | true | false | MEDIUM
-| *camel.component.consul.readTimeout* | Read timeout for OkHttpClient | null | false | MEDIUM
-| *camel.component.consul.readTimeoutMillis* | Read timeout for OkHttpClient. Deprecation note: Use readTimeout instead | null | false | LOW
-| *camel.component.consul.tags* | Set tags. You can separate multiple tags by comma. | null | false | MEDIUM
-| *camel.component.consul.url* | The Consul agent URL | null | false | MEDIUM
-| *camel.component.consul.writeTimeout* | Write timeout for OkHttpClient | null | false | MEDIUM
-| *camel.component.consul.writeTimeoutMillis* | Write timeout for OkHttpClient. Deprecation note: Use writeTimeout instead | null | false | LOW
-| *camel.component.consul.bridgeErrorHandler* | 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 | false | MEDIUM
-| *camel.component.consul.autowiredEnabled* | 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 | false | MEDIUM
-| *camel.component.consul.configuration* | Consul configuration | null | false | MEDIUM
-| *camel.component.consul.consistencyMode* | The consistencyMode used for queries, default ConsistencyMode.DEFAULT One of: [DEFAULT] [STALE] [CONSISTENT] | "DEFAULT" | false | MEDIUM
-| *camel.component.consul.datacenter* | The data center | null | false | MEDIUM
... 85044 lines suppressed ...