You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by ac...@apache.org on 2020/10/06 06:25:13 UTC
[camel-kafka-connector] 02/06: Generator a JSON metadata file for
each connector, first generation cycle
This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a commit to branch json-generator
in repository https://gitbox.apache.org/repos/asf/camel-kafka-connector.git
commit 5b80134418f87f40f0fb4e8edf301bb8274b150e
Author: Andrea Cosentino <an...@gmail.com>
AuthorDate: Tue Oct 6 07:47:29 2020 +0200
Generator a JSON metadata file for each connector, first generation cycle
---
.../camel-activemq-kafka-sink-connector.json | 893 +++++++++++++++++++++
.../camel-activemq-kafka-source-connector.json | 893 +++++++++++++++++++++
.../resources/camel-ahc-kafka-sink-connector.json | 161 ++++
.../camel-ahc-ws-kafka-sink-connector.json | 167 ++++
.../camel-ahc-ws-kafka-source-connector.json | 167 ++++
.../camel-ahc-wss-kafka-sink-connector.json | 167 ++++
.../camel-ahc-wss-kafka-source-connector.json | 167 ++++
.../resources/camel-amqp-kafka-sink-connector.json | 875 ++++++++++++++++++++
.../camel-amqp-kafka-source-connector.json | 875 ++++++++++++++++++++
.../resources/camel-apns-kafka-sink-connector.json | 59 ++
.../camel-apns-kafka-source-connector.json | 167 ++++
.../camel-arangodb-kafka-sink-connector.json | 161 ++++
.../resources/camel-as2-kafka-sink-connector.json | 221 +++++
.../camel-as2-kafka-source-connector.json | 329 ++++++++
.../camel-asterisk-kafka-sink-connector.json | 71 ++
.../camel-asterisk-kafka-source-connector.json | 77 ++
.../camel-atmos-kafka-sink-connector.json | 125 +++
.../camel-atmos-kafka-source-connector.json | 137 ++++
...-atmosphere-websocket-kafka-sink-connector.json | 137 ++++
...tmosphere-websocket-kafka-source-connector.json | 233 ++++++
.../camel-atom-kafka-source-connector.json | 203 +++++
.../camel-atomix-map-kafka-sink-connector.json | 221 +++++
.../camel-atomix-map-kafka-source-connector.json | 233 ++++++
...amel-atomix-messaging-kafka-sink-connector.json | 233 ++++++
...el-atomix-messaging-kafka-source-connector.json | 245 ++++++
...camel-atomix-multimap-kafka-sink-connector.json | 221 +++++
.../camel-atomix-queue-kafka-sink-connector.json | 197 +++++
.../camel-atomix-queue-kafka-source-connector.json | 209 +++++
.../camel-atomix-set-kafka-sink-connector.json | 209 +++++
.../camel-atomix-set-kafka-source-connector.json | 221 +++++
.../camel-atomix-value-kafka-sink-connector.json | 209 +++++
.../camel-atomix-value-kafka-source-connector.json | 221 +++++
.../resources/camel-avro-kafka-sink-connector.json | 143 ++++
.../camel-avro-kafka-source-connector.json | 155 ++++
.../camel-aws-cw-kafka-sink-connector.json | 197 +++++
.../camel-aws-ddb-kafka-sink-connector.json | 221 +++++
...camel-aws-ddbstream-kafka-source-connector.json | 293 +++++++
...-aws-kinesis-firehose-kafka-sink-connector.json | 149 ++++
.../camel-aws-kinesis-kafka-sink-connector.json | 149 ++++
.../camel-aws-kinesis-kafka-source-connector.json | 317 ++++++++
.../camel-aws-lambda-kafka-sink-connector.json | 161 ++++
.../camel-aws-s3-kafka-sink-connector.json | 401 +++++++++
.../camel-aws-s3-kafka-source-connector.json | 485 +++++++++++
.../camel-aws-sdb-kafka-sink-connector.json | 107 +++
.../camel-aws-ses-kafka-sink-connector.json | 197 +++++
.../camel-aws-sns-kafka-sink-connector.json | 263 ++++++
.../camel-aws-sqs-kafka-sink-connector.json | 335 ++++++++
.../camel-aws-sqs-kafka-source-connector.json | 545 +++++++++++++
.../camel-aws-swf-kafka-sink-connector.json | 293 +++++++
.../camel-aws-swf-kafka-source-connector.json | 269 +++++++
.../camel-aws-translate-kafka-sink-connector.json | 197 +++++
.../camel-aws2-athena-kafka-sink-connector.json | 377 +++++++++
.../camel-aws2-cw-kafka-sink-connector.json | 209 +++++
.../camel-aws2-ddb-kafka-sink-connector.json | 233 ++++++
...amel-aws2-ddbstream-kafka-source-connector.json | 305 +++++++
...aws2-kinesis-firehose-kafka-sink-connector.json | 173 ++++
.../camel-aws2-kinesis-kafka-sink-connector.json | 161 ++++
.../camel-aws2-kinesis-kafka-source-connector.json | 329 ++++++++
.../camel-aws2-lambda-kafka-sink-connector.json | 185 +++++
.../camel-aws2-s3-kafka-sink-connector.json | 377 +++++++++
.../camel-aws2-s3-kafka-source-connector.json | 521 ++++++++++++
.../camel-aws2-ses-kafka-sink-connector.json | 209 +++++
.../camel-aws2-sns-kafka-sink-connector.json | 263 ++++++
.../camel-aws2-sqs-kafka-sink-connector.json | 347 ++++++++
.../camel-aws2-sqs-kafka-source-connector.json | 557 +++++++++++++
.../camel-aws2-sts-kafka-sink-connector.json | 185 +++++
.../camel-aws2-translate-kafka-sink-connector.json | 221 +++++
.../camel-azure-blob-kafka-sink-connector.json | 269 +++++++
.../camel-azure-blob-kafka-source-connector.json | 209 +++++
...camel-azure-eventhubs-kafka-sink-connector.json | 167 ++++
...mel-azure-eventhubs-kafka-source-connector.json | 239 ++++++
.../camel-azure-queue-kafka-sink-connector.json | 161 ++++
.../camel-azure-queue-kafka-source-connector.json | 125 +++
...el-azure-storage-blob-kafka-sink-connector.json | 341 ++++++++
...-azure-storage-blob-kafka-source-connector.json | 245 ++++++
...l-azure-storage-queue-kafka-sink-connector.json | 203 +++++
...azure-storage-queue-kafka-source-connector.json | 191 +++++
.../resources/camel-bean-kafka-sink-connector.json | 83 ++
.../camel-beanstalk-kafka-sink-connector.json | 77 ++
.../camel-beanstalk-kafka-source-connector.json | 203 +++++
.../resources/camel-box-kafka-sink-connector.json | 245 ++++++
.../camel-box-kafka-source-connector.json | 353 ++++++++
.../camel-braintree-kafka-sink-connector.json | 131 +++
.../camel-braintree-kafka-source-connector.json | 239 ++++++
.../camel-caffeine-cache-kafka-sink-connector.json | 233 ++++++
...el-caffeine-loadcache-kafka-sink-connector.json | 233 ++++++
.../camel-chatscript-kafka-sink-connector.json | 71 ++
.../camel-chunk-kafka-sink-connector.json | 107 +++
.../camel-cm-sms-kafka-sink-connector.json | 71 ++
.../resources/camel-cmis-kafka-sink-connector.json | 101 +++
.../camel-cmis-kafka-source-connector.json | 113 +++
.../resources/camel-coap-kafka-sink-connector.json | 101 +++
.../camel-coap-kafka-source-connector.json | 119 +++
.../camel-coap+tcp-kafka-sink-connector.json | 101 +++
.../camel-coap+tcp-kafka-source-connector.json | 119 +++
.../camel-coaps-kafka-sink-connector.json | 101 +++
.../camel-coaps-kafka-source-connector.json | 119 +++
.../camel-coaps+tcp-kafka-sink-connector.json | 101 +++
.../camel-coaps+tcp-kafka-source-connector.json | 119 +++
.../camel-cometd-kafka-sink-connector.json | 167 ++++
.../camel-cometd-kafka-source-connector.json | 179 +++++
.../camel-cometds-kafka-sink-connector.json | 167 ++++
.../camel-cometds-kafka-source-connector.json | 179 +++++
.../camel-consul-kafka-sink-connector.json | 311 +++++++
.../camel-consul-kafka-source-connector.json | 335 ++++++++
.../camel-controlbus-kafka-sink-connector.json | 83 ++
.../camel-corda-kafka-sink-connector.json | 89 ++
.../camel-corda-kafka-source-connector.json | 173 ++++
.../camel-couchbase-kafka-sink-connector.json | 149 ++++
.../camel-couchbase-kafka-source-connector.json | 263 ++++++
.../camel-couchdb-kafka-sink-connector.json | 83 ++
.../camel-couchdb-kafka-source-connector.json | 125 +++
.../resources/camel-cql-kafka-sink-connector.json | 125 +++
.../camel-cql-kafka-source-connector.json | 233 ++++++
.../camel-cron-kafka-source-connector.json | 71 ++
.../camel-crypto-cms-kafka-sink-connector.json | 149 ++++
.../camel-crypto-kafka-sink-connector.json | 275 +++++++
.../resources/camel-cxf-kafka-sink-connector.json | 251 ++++++
.../camel-cxf-kafka-source-connector.json | 227 ++++++
.../camel-cxfrs-kafka-sink-connector.json | 203 +++++
.../camel-cxfrs-kafka-source-connector.json | 191 +++++
.../camel-dataformat-kafka-sink-connector.json | 53 ++
.../camel-direct-kafka-sink-connector.json | 77 ++
.../camel-direct-kafka-source-connector.json | 59 ++
.../camel-direct-vm-kafka-sink-connector.json | 101 +++
.../camel-direct-vm-kafka-source-connector.json | 77 ++
.../camel-disruptor-kafka-sink-connector.json | 95 +++
.../camel-disruptor-kafka-source-connector.json | 107 +++
.../camel-disruptor-vm-kafka-sink-connector.json | 95 +++
.../camel-disruptor-vm-kafka-source-connector.json | 107 +++
.../resources/camel-djl-kafka-sink-connector.json | 65 ++
.../resources/camel-dns-kafka-sink-connector.json | 47 ++
.../camel-docker-kafka-sink-connector.json | 257 ++++++
.../camel-docker-kafka-source-connector.json | 269 +++++++
.../camel-dozer-kafka-sink-connector.json | 83 ++
.../camel-drill-kafka-sink-connector.json | 71 ++
.../camel-dropbox-kafka-sink-connector.json | 95 +++
.../camel-dropbox-kafka-source-connector.json | 107 +++
.../camel-ehcache-kafka-sink-connector.json | 167 ++++
.../camel-ehcache-kafka-source-connector.json | 191 +++++
...el-elasticsearch-rest-kafka-sink-connector.json | 209 +++++
.../camel-elsql-kafka-sink-connector.json | 185 +++++
.../camel-elsql-kafka-source-connector.json | 335 ++++++++
.../camel-etcd-keys-kafka-sink-connector.json | 155 ++++
.../camel-etcd-stats-kafka-sink-connector.json | 155 ++++
.../camel-etcd-stats-kafka-source-connector.json | 275 +++++++
.../camel-etcd-watch-kafka-source-connector.json | 179 +++++
.../resources/camel-exec-kafka-sink-connector.json | 95 +++
.../camel-facebook-kafka-sink-connector.json | 803 ++++++++++++++++++
.../camel-facebook-kafka-source-connector.json | 815 +++++++++++++++++++
.../resources/camel-fhir-kafka-sink-connector.json | 341 ++++++++
.../camel-fhir-kafka-source-connector.json | 449 +++++++++++
.../resources/camel-file-kafka-sink-connector.json | 173 ++++
.../camel-file-kafka-source-connector.json | 491 +++++++++++
.../camel-file-watch-kafka-source-connector.json | 143 ++++
.../camel-flatpack-kafka-sink-connector.json | 89 ++
.../camel-flatpack-kafka-source-connector.json | 197 +++++
.../camel-flink-kafka-sink-connector.json | 95 +++
.../resources/camel-fop-kafka-sink-connector.json | 59 ++
.../camel-freemarker-kafka-sink-connector.json | 101 +++
.../resources/camel-ftp-kafka-sink-connector.json | 311 +++++++
.../camel-ftp-kafka-source-connector.json | 617 ++++++++++++++
.../resources/camel-ftps-kafka-sink-connector.json | 365 +++++++++
.../camel-ftps-kafka-source-connector.json | 671 ++++++++++++++++
.../camel-ganglia-kafka-sink-connector.json | 203 +++++
.../camel-geocoder-kafka-sink-connector.json | 137 ++++
.../resources/camel-git-kafka-sink-connector.json | 95 +++
.../camel-git-kafka-source-connector.json | 101 +++
.../camel-github-kafka-sink-connector.json | 95 +++
.../camel-github-kafka-source-connector.json | 95 +++
...camel-google-bigquery-kafka-sink-connector.json | 89 ++
...l-google-bigquery-sql-kafka-sink-connector.json | 71 ++
...camel-google-calendar-kafka-sink-connector.json | 179 +++++
...mel-google-calendar-kafka-source-connector.json | 287 +++++++
...gle-calendar-stream-kafka-source-connector.json | 299 +++++++
.../camel-google-drive-kafka-sink-connector.json | 149 ++++
.../camel-google-drive-kafka-source-connector.json | 257 ++++++
.../camel-google-mail-kafka-sink-connector.json | 131 +++
.../camel-google-mail-kafka-source-connector.json | 239 ++++++
...-google-mail-stream-kafka-source-connector.json | 275 +++++++
.../camel-google-pubsub-kafka-sink-connector.json | 107 +++
...camel-google-pubsub-kafka-source-connector.json | 107 +++
.../camel-google-sheets-kafka-sink-connector.json | 131 +++
...camel-google-sheets-kafka-source-connector.json | 239 ++++++
...oogle-sheets-stream-kafka-source-connector.json | 323 ++++++++
.../resources/camel-gora-kafka-sink-connector.json | 77 ++
.../camel-gora-kafka-source-connector.json | 155 ++++
.../camel-grape-kafka-sink-connector.json | 53 ++
.../camel-graphql-kafka-sink-connector.json | 95 +++
.../resources/camel-grpc-kafka-sink-connector.json | 161 ++++
.../camel-grpc-kafka-source-connector.json | 173 ++++
.../camel-guava-eventbus-kafka-sink-connector.json | 65 ++
...amel-guava-eventbus-kafka-source-connector.json | 83 ++
...hazelcast-atomicvalue-kafka-sink-connector.json | 77 ++
...-hazelcast-instance-kafka-source-connector.json | 89 ++
.../camel-hazelcast-list-kafka-sink-connector.json | 77 ++
...amel-hazelcast-list-kafka-source-connector.json | 89 ++
.../camel-hazelcast-map-kafka-sink-connector.json | 77 ++
...camel-hazelcast-map-kafka-source-connector.json | 89 ++
...el-hazelcast-multimap-kafka-sink-connector.json | 77 ++
...-hazelcast-multimap-kafka-source-connector.json | 89 ++
...camel-hazelcast-queue-kafka-sink-connector.json | 77 ++
...mel-hazelcast-queue-kafka-source-connector.json | 107 +++
...zelcast-replicatedmap-kafka-sink-connector.json | 77 ++
...lcast-replicatedmap-kafka-source-connector.json | 89 ++
...-hazelcast-ringbuffer-kafka-sink-connector.json | 77 ++
.../camel-hazelcast-seda-kafka-sink-connector.json | 107 +++
...amel-hazelcast-seda-kafka-source-connector.json | 119 +++
.../camel-hazelcast-set-kafka-sink-connector.json | 77 ++
...camel-hazelcast-set-kafka-source-connector.json | 89 ++
...camel-hazelcast-topic-kafka-sink-connector.json | 83 ++
...mel-hazelcast-topic-kafka-source-connector.json | 95 +++
.../camel-hbase-kafka-sink-connector.json | 107 +++
.../camel-hbase-kafka-source-connector.json | 137 ++++
.../resources/camel-hdfs-kafka-sink-connector.json | 203 +++++
.../camel-hdfs-kafka-source-connector.json | 317 ++++++++
.../camel-hipchat-kafka-sink-connector.json | 77 ++
.../camel-hipchat-kafka-source-connector.json | 185 +++++
.../resources/camel-http-kafka-sink-connector.json | 491 +++++++++++
.../camel-https-kafka-sink-connector.json | 491 +++++++++++
...camel-iec60870-client-kafka-sink-connector.json | 149 ++++
...mel-iec60870-client-kafka-source-connector.json | 161 ++++
...camel-iec60870-server-kafka-sink-connector.json | 155 ++++
...mel-iec60870-server-kafka-source-connector.json | 167 ++++
.../camel-ignite-cache-kafka-sink-connector.json | 101 +++
.../camel-ignite-cache-kafka-source-connector.json | 131 +++
.../camel-ignite-compute-kafka-sink-connector.json | 107 +++
...camel-ignite-events-kafka-source-connector.json | 101 +++
.../camel-ignite-idgen-kafka-sink-connector.json | 95 +++
...amel-ignite-messaging-kafka-sink-connector.json | 95 +++
...el-ignite-messaging-kafka-source-connector.json | 95 +++
.../camel-ignite-queue-kafka-sink-connector.json | 101 +++
.../camel-ignite-set-kafka-sink-connector.json | 89 ++
.../resources/camel-imap-kafka-sink-connector.json | 359 +++++++++
.../camel-imap-kafka-source-connector.json | 581 ++++++++++++++
.../camel-imaps-kafka-sink-connector.json | 359 +++++++++
.../camel-imaps-kafka-source-connector.json | 581 ++++++++++++++
.../camel-infinispan-kafka-sink-connector.json | 173 ++++
.../camel-infinispan-kafka-source-connector.json | 233 ++++++
.../camel-influxdb-kafka-sink-connector.json | 83 ++
.../resources/camel-iota-kafka-sink-connector.json | 83 ++
.../resources/camel-ipfs-kafka-sink-connector.json | 65 ++
.../resources/camel-irc-kafka-sink-connector.json | 197 +++++
.../camel-irc-kafka-source-connector.json | 209 +++++
.../camel-ironmq-kafka-sink-connector.json | 83 ++
.../camel-ironmq-kafka-source-connector.json | 215 +++++
.../resources/camel-jbpm-kafka-sink-connector.json | 209 +++++
.../camel-jbpm-kafka-source-connector.json | 215 +++++
.../camel-jcache-kafka-sink-connector.json | 161 ++++
.../camel-jcache-kafka-source-connector.json | 191 +++++
.../camel-jclouds-kafka-sink-connector.json | 125 +++
.../camel-jclouds-kafka-source-connector.json | 89 ++
.../resources/camel-jcr-kafka-sink-connector.json | 113 +++
.../camel-jcr-kafka-source-connector.json | 125 +++
.../resources/camel-jdbc-kafka-sink-connector.json | 125 +++
.../camel-jetty-kafka-source-connector.json | 413 ++++++++++
.../camel-jgroups-kafka-sink-connector.json | 65 ++
.../camel-jgroups-kafka-source-connector.json | 89 ++
.../camel-jgroups-raft-kafka-sink-connector.json | 71 ++
.../camel-jgroups-raft-kafka-source-connector.json | 89 ++
.../resources/camel-jing-kafka-sink-connector.json | 53 ++
.../resources/camel-jira-kafka-sink-connector.json | 149 ++++
.../camel-jira-kafka-source-connector.json | 185 +++++
.../resources/camel-jms-kafka-sink-connector.json | 869 ++++++++++++++++++++
.../camel-jms-kafka-source-connector.json | 869 ++++++++++++++++++++
.../camel-jmx-kafka-source-connector.json | 215 +++++
.../resources/camel-jolt-kafka-sink-connector.json | 95 +++
.../resources/camel-jooq-kafka-sink-connector.json | 89 ++
.../camel-jooq-kafka-source-connector.json | 185 +++++
.../resources/camel-jpa-kafka-sink-connector.json | 161 ++++
.../camel-jpa-kafka-source-connector.json | 287 +++++++
.../resources/camel-jslt-kafka-sink-connector.json | 89 ++
.../camel-json-validator-kafka-sink-connector.json | 89 ++
.../camel-jsonata-kafka-sink-connector.json | 71 ++
.../camel-jt400-kafka-sink-connector.json | 131 +++
.../camel-jt400-kafka-source-connector.json | 239 ++++++
...ubernetes-config-maps-kafka-sink-connector.json | 161 ++++
...ubernetes-deployments-kafka-sink-connector.json | 161 ++++
...ernetes-deployments-kafka-source-connector.json | 197 +++++
.../camel-kubernetes-hpa-kafka-sink-connector.json | 161 ++++
...amel-kubernetes-hpa-kafka-source-connector.json | 197 +++++
.../camel-kubernetes-job-kafka-sink-connector.json | 161 ++++
...amel-kubernetes-job-kafka-source-connector.json | 197 +++++
...kubernetes-namespaces-kafka-sink-connector.json | 161 ++++
...bernetes-namespaces-kafka-source-connector.json | 197 +++++
...amel-kubernetes-nodes-kafka-sink-connector.json | 161 ++++
...el-kubernetes-nodes-kafka-source-connector.json | 197 +++++
...istent-volumes-claims-kafka-sink-connector.json | 161 ++++
...es-persistent-volumes-kafka-sink-connector.json | 161 ++++
...camel-kubernetes-pods-kafka-sink-connector.json | 161 ++++
...mel-kubernetes-pods-kafka-source-connector.json | 197 +++++
...plication-controllers-kafka-sink-connector.json | 161 ++++
...ication-controllers-kafka-source-connector.json | 197 +++++
...netes-resources-quota-kafka-sink-connector.json | 161 ++++
...el-kubernetes-secrets-kafka-sink-connector.json | 161 ++++
...etes-service-accounts-kafka-sink-connector.json | 161 ++++
...l-kubernetes-services-kafka-sink-connector.json | 161 ++++
...kubernetes-services-kafka-source-connector.json | 197 +++++
.../resources/camel-kudu-kafka-sink-connector.json | 65 ++
.../camel-language-kafka-sink-connector.json | 89 ++
.../resources/camel-ldap-kafka-sink-connector.json | 71 ++
.../resources/camel-ldif-kafka-sink-connector.json | 47 ++
.../resources/camel-log-kafka-sink-connector.json | 203 +++++
.../resources/camel-lpr-kafka-sink-connector.json | 119 +++
.../camel-lucene-kafka-sink-connector.json | 107 +++
.../camel-lumberjack-kafka-source-connector.json | 83 ++
.../camel-master-kafka-source-connector.json | 77 ++
.../camel-metrics-kafka-sink-connector.json | 95 +++
.../camel-micrometer-kafka-sink-connector.json | 89 ++
...-microprofile-metrics-kafka-sink-connector.json | 125 +++
.../camel-milo-client-kafka-sink-connector.json | 317 ++++++++
.../camel-milo-client-kafka-source-connector.json | 329 ++++++++
.../camel-milo-server-kafka-sink-connector.json | 149 ++++
.../camel-milo-server-kafka-source-connector.json | 161 ++++
.../resources/camel-mina-kafka-sink-connector.json | 311 +++++++
.../camel-mina-kafka-source-connector.json | 335 ++++++++
.../camel-minio-kafka-sink-connector.json | 269 +++++++
.../camel-minio-kafka-source-connector.json | 617 ++++++++++++++
.../resources/camel-mllp-kafka-sink-connector.json | 161 ++++
.../camel-mllp-kafka-source-connector.json | 203 +++++
.../camel-mongodb-gridfs-kafka-sink-connector.json | 77 ++
...amel-mongodb-gridfs-kafka-source-connector.json | 125 +++
.../camel-mongodb-kafka-sink-connector.json | 167 ++++
.../camel-mongodb-kafka-source-connector.json | 185 +++++
.../resources/camel-msv-kafka-sink-connector.json | 113 +++
.../camel-mustache-kafka-sink-connector.json | 101 +++
.../resources/camel-mvel-kafka-sink-connector.json | 83 ++
.../camel-mybatis-bean-kafka-sink-connector.json | 83 ++
.../camel-mybatis-kafka-sink-connector.json | 83 ++
.../camel-mybatis-kafka-source-connector.json | 203 +++++
.../camel-nagios-kafka-sink-connector.json | 113 +++
.../resources/camel-nats-kafka-sink-connector.json | 173 ++++
.../camel-nats-kafka-source-connector.json | 203 +++++
.../camel-netty-http-kafka-sink-connector.json | 683 ++++++++++++++++
.../camel-netty-http-kafka-source-connector.json | 803 ++++++++++++++++++
.../camel-netty-kafka-sink-connector.json | 659 +++++++++++++++
.../camel-netty-kafka-source-connector.json | 731 +++++++++++++++++
.../camel-nitrite-kafka-sink-connector.json | 77 ++
.../camel-nitrite-kafka-source-connector.json | 89 ++
.../resources/camel-nsq-kafka-sink-connector.json | 89 ++
.../camel-nsq-kafka-source-connector.json | 137 ++++
.../camel-oaipmh-kafka-sink-connector.json | 101 +++
.../camel-oaipmh-kafka-source-connector.json | 203 +++++
.../camel-olingo2-kafka-sink-connector.json | 215 +++++
.../camel-olingo2-kafka-source-connector.json | 335 ++++++++
.../camel-olingo4-kafka-sink-connector.json | 191 +++++
.../camel-olingo4-kafka-source-connector.json | 311 +++++++
...enshift-build-configs-kafka-sink-connector.json | 161 ++++
...amel-openshift-builds-kafka-sink-connector.json | 161 ++++
...amel-openstack-cinder-kafka-sink-connector.json | 95 +++
...amel-openstack-glance-kafka-sink-connector.json | 89 ++
...el-openstack-keystone-kafka-sink-connector.json | 89 ++
...mel-openstack-neutron-kafka-sink-connector.json | 95 +++
.../camel-openstack-nova-kafka-sink-connector.json | 95 +++
...camel-openstack-swift-kafka-sink-connector.json | 95 +++
.../camel-optaplanner-kafka-sink-connector.json | 65 ++
.../camel-optaplanner-kafka-source-connector.json | 65 ++
.../resources/camel-paho-kafka-sink-connector.json | 377 +++++++++
.../camel-paho-kafka-source-connector.json | 389 +++++++++
.../resources/camel-pdf-kafka-sink-connector.json | 95 +++
...pg-replication-slot-kafka-source-connector.json | 209 +++++
.../camel-pgevent-kafka-sink-connector.json | 83 ++
.../camel-pgevent-kafka-source-connector.json | 95 +++
...camel-platform-http-kafka-source-connector.json | 107 +++
.../resources/camel-pop3-kafka-sink-connector.json | 359 +++++++++
.../camel-pop3-kafka-source-connector.json | 581 ++++++++++++++
.../camel-pop3s-kafka-sink-connector.json | 359 +++++++++
.../camel-pop3s-kafka-source-connector.json | 581 ++++++++++++++
.../camel-pubnub-kafka-sink-connector.json | 101 +++
.../camel-pubnub-kafka-source-connector.json | 113 +++
.../camel-pulsar-kafka-sink-connector.json | 239 ++++++
.../camel-pulsar-kafka-source-connector.json | 281 +++++++
.../camel-quartz-kafka-source-connector.json | 221 +++++
.../camel-quickfix-kafka-sink-connector.json | 83 ++
.../camel-quickfix-kafka-source-connector.json | 95 +++
.../camel-rabbitmq-kafka-sink-connector.json | 599 ++++++++++++++
.../camel-rabbitmq-kafka-source-connector.json | 599 ++++++++++++++
...amel-reactive-streams-kafka-sink-connector.json | 89 ++
...el-reactive-streams-kafka-source-connector.json | 119 +++
.../camel-rest-api-kafka-source-connector.json | 77 ++
.../resources/camel-rest-kafka-sink-connector.json | 143 ++++
.../camel-rest-kafka-source-connector.json | 119 +++
.../camel-rest-openapi-kafka-sink-connector.json | 131 +++
.../camel-rest-swagger-kafka-sink-connector.json | 137 ++++
.../camel-resteasy-kafka-sink-connector.json | 227 ++++++
.../camel-resteasy-kafka-source-connector.json | 215 +++++
.../camel-rss-kafka-source-connector.json | 203 +++++
.../resources/camel-saga-kafka-sink-connector.json | 47 ++
.../camel-salesforce-kafka-sink-connector.json | 689 ++++++++++++++++
.../camel-salesforce-kafka-source-connector.json | 707 ++++++++++++++++
.../camel-sap-netweaver-kafka-sink-connector.json | 77 ++
.../camel-scheduler-kafka-source-connector.json | 167 ++++
.../camel-schematron-kafka-sink-connector.json | 65 ++
.../resources/camel-scp-kafka-sink-connector.json | 191 +++++
.../resources/camel-seda-kafka-sink-connector.json | 131 +++
.../camel-seda-kafka-source-connector.json | 119 +++
.../camel-service-kafka-source-connector.json | 71 ++
.../camel-servicenow-kafka-sink-connector.json | 581 ++++++++++++++
.../camel-servlet-kafka-source-connector.json | 221 +++++
.../resources/camel-sftp-kafka-sink-connector.json | 365 +++++++++
.../camel-sftp-kafka-source-connector.json | 683 ++++++++++++++++
.../resources/camel-sip-kafka-sink-connector.json | 275 +++++++
.../camel-sip-kafka-source-connector.json | 299 +++++++
.../resources/camel-sips-kafka-sink-connector.json | 275 +++++++
.../camel-sips-kafka-source-connector.json | 299 +++++++
.../camel-sjms-batch-kafka-source-connector.json | 197 +++++
.../resources/camel-sjms-kafka-sink-connector.json | 263 ++++++
.../camel-sjms-kafka-source-connector.json | 311 +++++++
.../camel-sjms2-kafka-sink-connector.json | 263 ++++++
.../camel-sjms2-kafka-source-connector.json | 329 ++++++++
.../camel-slack-kafka-sink-connector.json | 77 ++
.../camel-slack-kafka-source-connector.json | 179 +++++
.../resources/camel-smpp-kafka-sink-connector.json | 455 +++++++++++
.../camel-smpp-kafka-source-connector.json | 311 +++++++
.../camel-smpps-kafka-sink-connector.json | 455 +++++++++++
.../camel-smpps-kafka-source-connector.json | 311 +++++++
.../resources/camel-smtp-kafka-sink-connector.json | 359 +++++++++
.../camel-smtp-kafka-source-connector.json | 581 ++++++++++++++
.../camel-smtps-kafka-sink-connector.json | 359 +++++++++
.../camel-smtps-kafka-source-connector.json | 581 ++++++++++++++
.../resources/camel-snmp-kafka-sink-connector.json | 143 ++++
.../camel-snmp-kafka-source-connector.json | 257 ++++++
.../resources/camel-solr-kafka-sink-connector.json | 131 +++
.../camel-solrCloud-kafka-sink-connector.json | 131 +++
.../camel-solrs-kafka-sink-connector.json | 131 +++
.../camel-soroush-kafka-sink-connector.json | 137 ++++
.../camel-soroush-kafka-source-connector.json | 131 +++
.../camel-spark-kafka-sink-connector.json | 89 ++
.../camel-splunk-hec-kafka-sink-connector.json | 89 ++
.../camel-splunk-kafka-sink-connector.json | 149 ++++
.../camel-splunk-kafka-source-connector.json | 263 ++++++
.../camel-spring-batch-kafka-sink-connector.json | 77 ++
.../camel-spring-event-kafka-sink-connector.json | 47 ++
.../camel-spring-event-kafka-source-connector.json | 59 ++
...el-spring-integration-kafka-sink-connector.json | 59 ++
...-spring-integration-kafka-source-connector.json | 71 ++
.../camel-spring-ldap-kafka-sink-connector.json | 59 ++
.../camel-spring-redis-kafka-sink-connector.json | 83 ++
.../camel-spring-redis-kafka-source-connector.json | 101 +++
.../camel-spring-ws-kafka-sink-connector.json | 143 ++++
.../camel-spring-ws-kafka-source-connector.json | 101 +++
.../resources/camel-sql-kafka-sink-connector.json | 155 ++++
.../camel-sql-kafka-source-connector.json | 305 +++++++
.../camel-sql-stored-kafka-sink-connector.json | 89 ++
.../resources/camel-ssh-kafka-sink-connector.json | 203 +++++
.../camel-ssh-kafka-source-connector.json | 323 ++++++++
.../resources/camel-stax-kafka-sink-connector.json | 47 ++
.../camel-stomp-kafka-sink-connector.json | 155 ++++
.../camel-stomp-kafka-source-connector.json | 167 ++++
.../camel-stream-kafka-sink-connector.json | 83 ++
.../camel-stream-kafka-source-connector.json | 131 +++
...camel-string-template-kafka-sink-connector.json | 89 ++
.../resources/camel-stub-kafka-sink-connector.json | 131 +++
.../camel-stub-kafka-source-connector.json | 119 +++
.../camel-telegram-kafka-sink-connector.json | 119 +++
.../camel-telegram-kafka-source-connector.json | 233 ++++++
.../camel-thrift-kafka-sink-connector.json | 95 +++
.../camel-thrift-kafka-source-connector.json | 119 +++
.../resources/camel-tika-kafka-sink-connector.json | 71 ++
.../camel-timer-kafka-source-connector.json | 113 +++
.../camel-twilio-kafka-sink-connector.json | 89 ++
.../camel-twilio-kafka-source-connector.json | 197 +++++
...twitter-directmessage-kafka-sink-connector.json | 143 ++++
...itter-directmessage-kafka-source-connector.json | 335 ++++++++
.../camel-twitter-search-kafka-sink-connector.json | 143 ++++
...amel-twitter-search-kafka-source-connector.json | 335 ++++++++
...amel-twitter-timeline-kafka-sink-connector.json | 149 ++++
...el-twitter-timeline-kafka-source-connector.json | 341 ++++++++
.../camel-undertow-kafka-sink-connector.json | 197 +++++
.../camel-undertow-kafka-source-connector.json | 197 +++++
.../camel-validator-kafka-sink-connector.json | 107 +++
.../camel-velocity-kafka-sink-connector.json | 101 +++
.../camel-vertx-http-kafka-sink-connector.json | 263 ++++++
.../camel-vertx-kafka-sink-connector.json | 89 ++
.../camel-vertx-kafka-source-connector.json | 101 +++
...camel-vertx-websocket-kafka-sink-connector.json | 95 +++
...mel-vertx-websocket-kafka-source-connector.json | 113 +++
.../resources/camel-vm-kafka-sink-connector.json | 131 +++
.../resources/camel-vm-kafka-source-connector.json | 119 +++
.../camel-weather-kafka-sink-connector.json | 167 ++++
.../camel-weather-kafka-source-connector.json | 275 +++++++
.../camel-web3j-kafka-sink-connector.json | 461 +++++++++++
.../camel-web3j-kafka-source-connector.json | 197 +++++
.../camel-webhook-kafka-source-connector.json | 125 +++
...amel-websocket-jsr356-kafka-sink-connector.json | 59 ++
...el-websocket-jsr356-kafka-source-connector.json | 71 ++
.../camel-websocket-kafka-sink-connector.json | 197 +++++
.../camel-websocket-kafka-source-connector.json | 215 +++++
.../resources/camel-weka-kafka-sink-connector.json | 101 +++
.../camel-wordpress-kafka-sink-connector.json | 155 ++++
.../camel-wordpress-kafka-source-connector.json | 167 ++++
.../camel-workday-kafka-sink-connector.json | 95 +++
.../camel-xchange-kafka-sink-connector.json | 71 ++
.../resources/camel-xj-kafka-sink-connector.json | 191 +++++
...amel-xmlsecurity-sign-kafka-sink-connector.json | 365 +++++++++
...el-xmlsecurity-verify-kafka-sink-connector.json | 245 ++++++
.../resources/camel-xmpp-kafka-sink-connector.json | 137 ++++
.../camel-xmpp-kafka-source-connector.json | 161 ++++
.../camel-xquery-kafka-sink-connector.json | 137 ++++
.../camel-xquery-kafka-source-connector.json | 245 ++++++
.../resources/camel-xslt-kafka-sink-connector.json | 149 ++++
.../camel-xslt-saxon-kafka-sink-connector.json | 185 +++++
.../camel-yammer-kafka-sink-connector.json | 113 +++
.../camel-yammer-kafka-source-connector.json | 287 +++++++
.../camel-zendesk-kafka-sink-connector.json | 95 +++
.../camel-zendesk-kafka-source-connector.json | 203 +++++
.../camel-zookeeper-kafka-sink-connector.json | 107 +++
.../camel-zookeeper-kafka-source-connector.json | 131 +++
...el-zookeeper-master-kafka-source-connector.json | 101 +++
509 files changed, 101911 insertions(+)
diff --git a/connectors/camel-activemq-kafka-connector/src/generated/resources/camel-activemq-kafka-sink-connector.json b/connectors/camel-activemq-kafka-connector/src/generated/resources/camel-activemq-kafka-sink-connector.json
new file mode 100644
index 0000000..62d0e0c
--- /dev/null
+++ b/connectors/camel-activemq-kafka-connector/src/generated/resources/camel-activemq-kafka-sink-connector.json
@@ -0,0 +1,893 @@
+{
+ "connector": {
+ "class": "org.apache.camel.kafkaconnector.activemq.CamelActivemqSinkConnector",
+ "artifactId": "camel-activemq",
+ "groupId": "org.apache.camel",
+ "title": "camel-activemq",
+ "version": "0.6.0-SNAPSHOT"
+ },
+ "properties": {
+ "camel.sink.path.destinationType": {
+ "name": "camel.sink.path.destinationType",
+ "description": "The kind of destination to use One of: [queue] [topic] [temp-queue] [temp-topic]",
+ "defaultValue": "\"queue\"",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.path.destinationName": {
+ "name": "camel.sink.path.destinationName",
+ "description": "Name of the queue or topic to use as destination",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.sink.endpoint.clientId": {
+ "name": "camel.sink.endpoint.clientId",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.connectionFactory": {
+ "name": "camel.sink.endpoint.connectionFactory",
+ "description": "The connection factory to be use. A connection factory must be configured either on the component or endpoint.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.disableReplyTo": {
+ "name": "camel.sink.endpoint.disableReplyTo",
+ "description": "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 message brokers and you w [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.durableSubscriptionName": {
+ "name": "camel.sink.endpoint.durableSubscriptionName",
+ "description": "The durable subscriber name for specifying durable topic subscriptions. The clientId option must be configured as well.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.jmsMessageType": {
+ "name": "camel.sink.endpoint.jmsMessageType",
+ "description": "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]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.testConnectionOnStartup": {
+ "name": "camel.sink.endpoint.testConnectionOnStartup",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.deliveryDelay": {
+ "name": "camel.sink.endpoint.deliveryDelay",
+ "description": "Sets delivery delay to use for send calls for JMS. This option requires JMS 2.0 compliant broker.",
+ "defaultValue": "-1L",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.deliveryMode": {
+ "name": "camel.sink.endpoint.deliveryMode",
+ "description": "Specifies the delivery mode to be used. Possibles values are those defined by javax.jms.DeliveryMode. NON_PERSISTENT = 1 and PERSISTENT = 2. One of: [1] [2]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.deliveryPersistent": {
+ "name": "camel.sink.endpoint.deliveryPersistent",
+ "description": "Specifies whether persistent delivery is used by default.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.explicitQosEnabled": {
+ "name": "camel.sink.endpoint.explicitQosEnabled",
+ "description": "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.",
+ "defaultValue": "\"false\"",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.formatDateHeadersToIso8601": {
+ "name": "camel.sink.endpoint.formatDateHeadersToIso8601",
+ "description": "Sets whether JMS date properties should be formatted according to the ISO 8601 standard.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.lazyStartProducer": {
+ "name": "camel.sink.endpoint.lazyStartProducer",
+ "description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be 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 creating and starting the pr [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.preserveMessageQos": {
+ "name": "camel.sink.endpoint.preserveMessageQos",
+ "description": "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 explicitQosEnabled option, by cont [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.priority": {
+ "name": "camel.sink.endpoint.priority",
+ "description": "Values greater than 1 specify the message priority when sending (where 0 is the lowest priority and 9 is the highest). The explicitQosEnabled option must also be enabled in order for this option to have any effect. One of: [1] [2] [3] [4] [5] [6] [7] [8] [9]",
+ "defaultValue": "4",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.replyToConcurrentConsumers": {
+ "name": "camel.sink.endpoint.replyToConcurrentConsumers",
+ "description": "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.",
+ "defaultValue": "1",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.replyToMaxConcurrentConsumers": {
+ "name": "camel.sink.endpoint.replyToMaxConcurrentConsumers",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.replyToOnTimeoutMaxConcurrentConsumers": {
+ "name": "camel.sink.endpoint.replyToOnTimeoutMaxConcurrentConsumers",
+ "description": "Specifies the maximum number of concurrent consumers for continue routing when timeout occurred when using request\/reply over JMS.",
+ "defaultValue": "1",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.replyToOverride": {
+ "name": "camel.sink.endpoint.replyToOverride",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.replyToType": {
+ "name": "camel.sink.endpoint.replyToType",
+ "description": "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 running in a clus [...]
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.requestTimeout": {
+ "name": "camel.sink.endpoint.requestTimeout",
+ "description": "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.",
+ "defaultValue": "20000L",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.timeToLive": {
+ "name": "camel.sink.endpoint.timeToLive",
+ "description": "When sending messages, specifies the time-to-live of the message (in milliseconds).",
+ "defaultValue": "-1L",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.allowAdditionalHeaders": {
+ "name": "camel.sink.endpoint.allowAdditionalHeaders",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.allowNullBody": {
+ "name": "camel.sink.endpoint.allowNullBody",
+ "description": "Whether to allow sending messages with no body. If this option is false and the message body is null, then an JMSException is thrown.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.alwaysCopyMessage": {
+ "name": "camel.sink.endpoint.alwaysCopyMessage",
+ "description": "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)",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.correlationProperty": {
+ "name": "camel.sink.endpoint.correlationProperty",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.disableTimeToLive": {
+ "name": "camel.sink.endpoint.disableTimeToLive",
+ "description": "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 message will not expire [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.forceSendOriginalMessage": {
+ "name": "camel.sink.endpoint.forceSendOriginalMessage",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.includeSentJMSMessageID": {
+ "name": "camel.sink.endpoint.includeSentJMSMessageID",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.replyToCacheLevelName": {
+ "name": "camel.sink.endpoint.replyToCacheLevelName",
+ "description": "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 then CACHE_NONE is not allow [...]
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.replyToDestinationSelectorName": {
+ "name": "camel.sink.endpoint.replyToDestinationSelectorName",
+ "description": "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).",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.streamMessageTypeEnabled": {
+ "name": "camel.sink.endpoint.streamMessageTypeEnabled",
+ "description": "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 until no more data.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.allowSerializedHeaders": {
+ "name": "camel.sink.endpoint.allowSerializedHeaders",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.artemisStreamingEnabled": {
+ "name": "camel.sink.endpoint.artemisStreamingEnabled",
+ "description": "Whether optimizing for Apache Artemis streaming mode.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.asyncStartListener": {
+ "name": "camel.sink.endpoint.asyncStartListener",
+ "description": "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 used, then beware that if [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.asyncStopListener": {
+ "name": "camel.sink.endpoint.asyncStopListener",
+ "description": "Whether to stop the JmsConsumer message listener asynchronously, when stopping a route.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.basicPropertyBinding": {
+ "name": "camel.sink.endpoint.basicPropertyBinding",
+ "description": "Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.destinationResolver": {
+ "name": "camel.sink.endpoint.destinationResolver",
+ "description": "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).",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.errorHandler": {
+ "name": "camel.sink.endpoint.errorHandler",
+ "description": "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 errorHandler.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.exceptionListener": {
+ "name": "camel.sink.endpoint.exceptionListener",
+ "description": "Specifies the JMS Exception Listener that is to be notified of any underlying JMS exceptions.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.headerFilterStrategy": {
+ "name": "camel.sink.endpoint.headerFilterStrategy",
+ "description": "To use a custom HeaderFilterStrategy to filter header to and from Camel message.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.idleConsumerLimit": {
+ "name": "camel.sink.endpoint.idleConsumerLimit",
+ "description": "Specify the limit for the number of consumers that are allowed to be idle at any given time.",
+ "defaultValue": "1",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.idleTaskExecutionLimit": {
+ "name": "camel.sink.endpoint.idleTaskExecutionLimit",
+ "description": "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.",
+ "defaultValue": "1",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.includeAllJMSXProperties": {
+ "name": "camel.sink.endpoint.includeAllJMSXProperties",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.jmsKeyFormatStrategy": {
+ "name": "camel.sink.endpoint.jmsKeyFormatStrategy",
+ "description": "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 org.apache.camel.component.jm [...]
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.mapJmsMessage": {
+ "name": "camel.sink.endpoint.mapJmsMessage",
+ "description": "Specifies whether Camel should auto map the received JMS message to a suited payload type, such as javax.jms.TextMessage to a String etc.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.maxMessagesPerTask": {
+ "name": "camel.sink.endpoint.maxMessagesPerTask",
+ "description": "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.",
+ "defaultValue": "-1",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.messageConverter": {
+ "name": "camel.sink.endpoint.messageConverter",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.messageCreatedStrategy": {
+ "name": "camel.sink.endpoint.messageCreatedStrategy",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.messageIdEnabled": {
+ "name": "camel.sink.endpoint.messageIdEnabled",
+ "description": "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.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.messageListenerContainerFactory": {
+ "name": "camel.sink.endpoint.messageListenerContainerFactory",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.messageTimestampEnabled": {
+ "name": "camel.sink.endpoint.messageTimestampEnabled",
+ "description": "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.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.pubSubNoLocal": {
+ "name": "camel.sink.endpoint.pubSubNoLocal",
+ "description": "Specifies whether to inhibit the delivery of messages published by its own connection.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.receiveTimeout": {
+ "name": "camel.sink.endpoint.receiveTimeout",
+ "description": "The timeout for receiving messages (in milliseconds).",
+ "defaultValue": "1000L",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.recoveryInterval": {
+ "name": "camel.sink.endpoint.recoveryInterval",
+ "description": "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.",
+ "defaultValue": "5000L",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.requestTimeoutCheckerInterval": {
+ "name": "camel.sink.endpoint.requestTimeoutCheckerInterval",
+ "description": "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.",
+ "defaultValue": "1000L",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.synchronous": {
+ "name": "camel.sink.endpoint.synchronous",
+ "description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.transferException": {
+ "name": "camel.sink.endpoint.transferException",
+ "description": "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 takes precedence. The caught [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.transferExchange": {
+ "name": "camel.sink.endpoint.transferExchange",
+ "description": "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 payloads is an Exchange and not [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.useMessageIDAsCorrelationID": {
+ "name": "camel.sink.endpoint.useMessageIDAsCorrelationID",
+ "description": "Specifies whether JMSMessageID should always be used as JMSCorrelationID for InOut messages.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.waitForProvisionCorrelationToBeUpdatedCounter": {
+ "name": "camel.sink.endpoint.waitForProvisionCorrelationToBeUpdatedCounter",
+ "description": "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.",
+ "defaultValue": "50",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.waitForProvisionCorrelationToBeUpdatedThreadSleepingTime": {
+ "name": "camel.sink.endpoint.waitForProvisionCorrelationToBeUpdatedThreadSleepingTime",
+ "description": "Interval in millis to sleep each time while waiting for provisional correlation id to be updated.",
+ "defaultValue": "100L",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.password": {
+ "name": "camel.sink.endpoint.password",
+ "description": "Password to use with the ConnectionFactory. You can also configure username\/password directly on the ConnectionFactory.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.username": {
+ "name": "camel.sink.endpoint.username",
+ "description": "Username to use with the ConnectionFactory. You can also configure username\/password directly on the ConnectionFactory.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.transacted": {
+ "name": "camel.sink.endpoint.transacted",
+ "description": "Specifies whether to use transacted mode",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.transactedInOut": {
+ "name": "camel.sink.endpoint.transactedInOut",
+ "description": "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 container makes its ow [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.lazyCreateTransactionManager": {
+ "name": "camel.sink.endpoint.lazyCreateTransactionManager",
+ "description": "If true, Camel will create a JmsTransactionManager, if there is no transactionManager injected when option transacted=true.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.transactionManager": {
+ "name": "camel.sink.endpoint.transactionManager",
+ "description": "The Spring transaction manager to use.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.transactionName": {
+ "name": "camel.sink.endpoint.transactionName",
+ "description": "The name of the transaction to use.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.transactionTimeout": {
+ "name": "camel.sink.endpoint.transactionTimeout",
+ "description": "The timeout value of the transaction (in seconds), if using transacted mode.",
+ "defaultValue": "-1",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.brokerURL": {
+ "name": "camel.component.activemq.brokerURL",
+ "description": "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)",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.clientId": {
+ "name": "camel.component.activemq.clientId",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.connectionFactory": {
+ "name": "camel.component.activemq.connectionFactory",
+ "description": "The connection factory to be use. A connection factory must be configured either on the component or endpoint.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.disableReplyTo": {
+ "name": "camel.component.activemq.disableReplyTo",
+ "description": "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 message brokers and you w [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.durableSubscriptionName": {
+ "name": "camel.component.activemq.durableSubscriptionName",
+ "description": "The durable subscriber name for specifying durable topic subscriptions. The clientId option must be configured as well.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.jmsMessageType": {
+ "name": "camel.component.activemq.jmsMessageType",
+ "description": "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]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.testConnectionOnStartup": {
+ "name": "camel.component.activemq.testConnectionOnStartup",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.usePooledConnection": {
+ "name": "camel.component.activemq.usePooledConnection",
+ "description": "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.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.useSingleConnection": {
+ "name": "camel.component.activemq.useSingleConnection",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.deliveryDelay": {
+ "name": "camel.component.activemq.deliveryDelay",
+ "description": "Sets delivery delay to use for send calls for JMS. This option requires JMS 2.0 compliant broker.",
+ "defaultValue": "-1L",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.deliveryMode": {
+ "name": "camel.component.activemq.deliveryMode",
+ "description": "Specifies the delivery mode to be used. Possibles values are those defined by javax.jms.DeliveryMode. NON_PERSISTENT = 1 and PERSISTENT = 2. One of: [1] [2]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.deliveryPersistent": {
+ "name": "camel.component.activemq.deliveryPersistent",
+ "description": "Specifies whether persistent delivery is used by default.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.explicitQosEnabled": {
+ "name": "camel.component.activemq.explicitQosEnabled",
+ "description": "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.",
+ "defaultValue": "\"false\"",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.formatDateHeadersToIso8601": {
+ "name": "camel.component.activemq.formatDateHeadersToIso8601",
+ "description": "Sets whether JMS date properties should be formatted according to the ISO 8601 standard.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.lazyStartProducer": {
+ "name": "camel.component.activemq.lazyStartProducer",
+ "description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be 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 creating and starting the pr [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.preserveMessageQos": {
+ "name": "camel.component.activemq.preserveMessageQos",
+ "description": "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 explicitQosEnabled option, by cont [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.priority": {
+ "name": "camel.component.activemq.priority",
+ "description": "Values greater than 1 specify the message priority when sending (where 0 is the lowest priority and 9 is the highest). The explicitQosEnabled option must also be enabled in order for this option to have any effect. One of: [1] [2] [3] [4] [5] [6] [7] [8] [9]",
+ "defaultValue": "4",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.replyToConcurrentConsumers": {
+ "name": "camel.component.activemq.replyToConcurrentConsumers",
+ "description": "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.",
+ "defaultValue": "1",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.replyToMaxConcurrentConsumers": {
+ "name": "camel.component.activemq.replyToMaxConcurrentConsumers",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.replyToOnTimeoutMaxConcurrentConsumers": {
+ "name": "camel.component.activemq.replyToOnTimeoutMaxConcurrentConsumers",
+ "description": "Specifies the maximum number of concurrent consumers for continue routing when timeout occurred when using request\/reply over JMS.",
+ "defaultValue": "1",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.replyToOverride": {
+ "name": "camel.component.activemq.replyToOverride",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.replyToType": {
+ "name": "camel.component.activemq.replyToType",
+ "description": "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 running in a clus [...]
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.requestTimeout": {
+ "name": "camel.component.activemq.requestTimeout",
+ "description": "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.",
+ "defaultValue": "20000L",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.timeToLive": {
+ "name": "camel.component.activemq.timeToLive",
+ "description": "When sending messages, specifies the time-to-live of the message (in milliseconds).",
+ "defaultValue": "-1L",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.allowAdditionalHeaders": {
+ "name": "camel.component.activemq.allowAdditionalHeaders",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.allowNullBody": {
+ "name": "camel.component.activemq.allowNullBody",
+ "description": "Whether to allow sending messages with no body. If this option is false and the message body is null, then an JMSException is thrown.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.alwaysCopyMessage": {
+ "name": "camel.component.activemq.alwaysCopyMessage",
+ "description": "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)",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.correlationProperty": {
+ "name": "camel.component.activemq.correlationProperty",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.disableTimeToLive": {
+ "name": "camel.component.activemq.disableTimeToLive",
+ "description": "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 message will not expire [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.forceSendOriginalMessage": {
+ "name": "camel.component.activemq.forceSendOriginalMessage",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.includeSentJMSMessageID": {
+ "name": "camel.component.activemq.includeSentJMSMessageID",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.replyToCacheLevelName": {
+ "name": "camel.component.activemq.replyToCacheLevelName",
+ "description": "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 then CACHE_NONE is not allow [...]
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.replyToDestinationSelectorName": {
+ "name": "camel.component.activemq.replyToDestinationSelectorName",
+ "description": "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).",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.streamMessageTypeEnabled": {
+ "name": "camel.component.activemq.streamMessageTypeEnabled",
+ "description": "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 until no more data.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.allowAutoWiredConnectionFactory": {
+ "name": "camel.component.activemq.allowAutoWiredConnectionFactory",
+ "description": "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.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.allowAutoWiredDestinationResolver": {
+ "name": "camel.component.activemq.allowAutoWiredDestinationResolver",
+ "description": "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.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.allowSerializedHeaders": {
+ "name": "camel.component.activemq.allowSerializedHeaders",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.artemisStreamingEnabled": {
+ "name": "camel.component.activemq.artemisStreamingEnabled",
+ "description": "Whether optimizing for Apache Artemis streaming mode.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.asyncStartListener": {
+ "name": "camel.component.activemq.asyncStartListener",
+ "description": "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 used, then beware that if [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.asyncStopListener": {
+ "name": "camel.component.activemq.asyncStopListener",
+ "description": "Whether to stop the JmsConsumer message listener asynchronously, when stopping a route.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.basicPropertyBinding": {
+ "name": "camel.component.activemq.basicPropertyBinding",
+ "description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.configuration": {
+ "name": "camel.component.activemq.configuration",
+ "description": "To use a shared JMS configuration",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.destinationResolver": {
+ "name": "camel.component.activemq.destinationResolver",
+ "description": "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).",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.errorHandler": {
+ "name": "camel.component.activemq.errorHandler",
+ "description": "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 errorHandler.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.exceptionListener": {
+ "name": "camel.component.activemq.exceptionListener",
+ "description": "Specifies the JMS Exception Listener that is to be notified of any underlying JMS exceptions.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.idleConsumerLimit": {
+ "name": "camel.component.activemq.idleConsumerLimit",
+ "description": "Specify the limit for the number of consumers that are allowed to be idle at any given time.",
+ "defaultValue": "1",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.idleTaskExecutionLimit": {
+ "name": "camel.component.activemq.idleTaskExecutionLimit",
+ "description": "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.",
+ "defaultValue": "1",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.includeAllJMSXProperties": {
+ "name": "camel.component.activemq.includeAllJMSXProperties",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.jmsKeyFormatStrategy": {
+ "name": "camel.component.activemq.jmsKeyFormatStrategy",
+ "description": "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 org.apache.camel.component.jm [...]
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.mapJmsMessage": {
+ "name": "camel.component.activemq.mapJmsMessage",
+ "description": "Specifies whether Camel should auto map the received JMS message to a suited payload type, such as javax.jms.TextMessage to a String etc.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.maxMessagesPerTask": {
+ "name": "camel.component.activemq.maxMessagesPerTask",
+ "description": "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.",
+ "defaultValue": "-1",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.messageConverter": {
+ "name": "camel.component.activemq.messageConverter",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.messageCreatedStrategy": {
+ "name": "camel.component.activemq.messageCreatedStrategy",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.messageIdEnabled": {
+ "name": "camel.component.activemq.messageIdEnabled",
+ "description": "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.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.messageListenerContainerFactory": {
+ "name": "camel.component.activemq.messageListenerContainerFactory",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.messageTimestampEnabled": {
+ "name": "camel.component.activemq.messageTimestampEnabled",
+ "description": "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.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.pubSubNoLocal": {
+ "name": "camel.component.activemq.pubSubNoLocal",
+ "description": "Specifies whether to inhibit the delivery of messages published by its own connection.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.queueBrowseStrategy": {
+ "name": "camel.component.activemq.queueBrowseStrategy",
+ "description": "To use a custom QueueBrowseStrategy when browsing queues",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.receiveTimeout": {
+ "name": "camel.component.activemq.receiveTimeout",
+ "description": "The timeout for receiving messages (in milliseconds).",
+ "defaultValue": "1000L",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.recoveryInterval": {
+ "name": "camel.component.activemq.recoveryInterval",
+ "description": "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.",
+ "defaultValue": "5000L",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.requestTimeoutCheckerInterval": {
+ "name": "camel.component.activemq.requestTimeoutCheckerInterval",
+ "description": "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.",
+ "defaultValue": "1000L",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.transferException": {
+ "name": "camel.component.activemq.transferException",
+ "description": "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 takes precedence. The caught [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.transferExchange": {
+ "name": "camel.component.activemq.transferExchange",
+ "description": "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 payloads is an Exchange and not [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.trustAllPackages": {
+ "name": "camel.component.activemq.trustAllPackages",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.useMessageIDAsCorrelationID": {
+ "name": "camel.component.activemq.useMessageIDAsCorrelationID",
+ "description": "Specifies whether JMSMessageID should always be used as JMSCorrelationID for InOut messages.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.waitForProvisionCorrelationToBeUpdatedCounter": {
+ "name": "camel.component.activemq.waitForProvisionCorrelationToBeUpdatedCounter",
+ "description": "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.",
+ "defaultValue": "50",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.waitForProvisionCorrelationToBeUpdatedThreadSleepingTime": {
+ "name": "camel.component.activemq.waitForProvisionCorrelationToBeUpdatedThreadSleepingTime",
+ "description": "Interval in millis to sleep each time while waiting for provisional correlation id to be updated.",
+ "defaultValue": "100L",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.headerFilterStrategy": {
+ "name": "camel.component.activemq.headerFilterStrategy",
+ "description": "To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.password": {
+ "name": "camel.component.activemq.password",
+ "description": "Password to use with the ConnectionFactory. You can also configure username\/password directly on the ConnectionFactory.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.username": {
+ "name": "camel.component.activemq.username",
+ "description": "Username to use with the ConnectionFactory. You can also configure username\/password directly on the ConnectionFactory.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.transacted": {
+ "name": "camel.component.activemq.transacted",
+ "description": "Specifies whether to use transacted mode",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.transactedInOut": {
+ "name": "camel.component.activemq.transactedInOut",
+ "description": "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 container makes its ow [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.lazyCreateTransactionManager": {
+ "name": "camel.component.activemq.lazyCreateTransactionManager",
+ "description": "If true, Camel will create a JmsTransactionManager, if there is no transactionManager injected when option transacted=true.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.transactionManager": {
+ "name": "camel.component.activemq.transactionManager",
+ "description": "The Spring transaction manager to use.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.transactionName": {
+ "name": "camel.component.activemq.transactionName",
+ "description": "The name of the transaction to use.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.transactionTimeout": {
+ "name": "camel.component.activemq.transactionTimeout",
+ "description": "The timeout value of the transaction (in seconds), if using transacted mode.",
+ "defaultValue": "-1",
+ "priority": "MEDIUM"
+ }
+ }
+}
diff --git a/connectors/camel-activemq-kafka-connector/src/generated/resources/camel-activemq-kafka-source-connector.json b/connectors/camel-activemq-kafka-connector/src/generated/resources/camel-activemq-kafka-source-connector.json
new file mode 100644
index 0000000..5972743
--- /dev/null
+++ b/connectors/camel-activemq-kafka-connector/src/generated/resources/camel-activemq-kafka-source-connector.json
@@ -0,0 +1,893 @@
+{
+ "connector": {
+ "class": "org.apache.camel.kafkaconnector.activemq.CamelActivemqSourceConnector",
+ "artifactId": "camel-activemq",
+ "groupId": "org.apache.camel",
+ "title": "camel-activemq",
+ "version": "0.6.0-SNAPSHOT"
+ },
+ "properties": {
+ "camel.source.path.destinationType": {
+ "name": "camel.source.path.destinationType",
+ "description": "The kind of destination to use One of: [queue] [topic] [temp-queue] [temp-topic]",
+ "defaultValue": "\"queue\"",
+ "priority": "MEDIUM"
+ },
+ "camel.source.path.destinationName": {
+ "name": "camel.source.path.destinationName",
+ "description": "Name of the queue or topic to use as destination",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.source.endpoint.clientId": {
+ "name": "camel.source.endpoint.clientId",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.connectionFactory": {
+ "name": "camel.source.endpoint.connectionFactory",
+ "description": "The connection factory to be use. A connection factory must be configured either on the component or endpoint.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.disableReplyTo": {
+ "name": "camel.source.endpoint.disableReplyTo",
+ "description": "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 message brokers and you w [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.durableSubscriptionName": {
+ "name": "camel.source.endpoint.durableSubscriptionName",
+ "description": "The durable subscriber name for specifying durable topic subscriptions. The clientId option must be configured as well.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.jmsMessageType": {
+ "name": "camel.source.endpoint.jmsMessageType",
+ "description": "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]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.testConnectionOnStartup": {
+ "name": "camel.source.endpoint.testConnectionOnStartup",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.acknowledgementModeName": {
+ "name": "camel.source.endpoint.acknowledgementModeName",
+ "description": "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]",
+ "defaultValue": "\"AUTO_ACKNOWLEDGE\"",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.asyncConsumer": {
+ "name": "camel.source.endpoint.asyncConsumer",
+ "description": "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 if transacted has been [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.autoStartup": {
+ "name": "camel.source.endpoint.autoStartup",
+ "description": "Specifies whether the consumer container should auto-startup.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.cacheLevel": {
+ "name": "camel.source.endpoint.cacheLevel",
+ "description": "Sets the cache level by ID for the underlying JMS resources. See cacheLevelName option for more details.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.cacheLevelName": {
+ "name": "camel.source.endpoint.cacheLevelName",
+ "description": "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]",
+ "defaultValue": "\"CACHE_AUTO\"",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.concurrentConsumers": {
+ "name": "camel.source.endpoint.concurrentConsumers",
+ "description": "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.",
+ "defaultValue": "1",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.maxConcurrentConsumers": {
+ "name": "camel.source.endpoint.maxConcurrentConsumers",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.replyTo": {
+ "name": "camel.source.endpoint.replyTo",
+ "description": "Provides an explicit ReplyTo destination, which overrides any incoming value of Message.getJMSReplyTo().",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.replyToDeliveryPersistent": {
+ "name": "camel.source.endpoint.replyToDeliveryPersistent",
+ "description": "Specifies whether to use persistent delivery by default for replies.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.selector": {
+ "name": "camel.source.endpoint.selector",
+ "description": "Sets the JMS selector to use",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.subscriptionDurable": {
+ "name": "camel.source.endpoint.subscriptionDurable",
+ "description": "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 pubSubDomain flag as well.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.subscriptionName": {
+ "name": "camel.source.endpoint.subscriptionName",
+ "description": "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.0).",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.subscriptionShared": {
+ "name": "camel.source.endpoint.subscriptionShared",
+ "description": "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 with subscriptionDurable as we [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.acceptMessagesWhileStopping": {
+ "name": "camel.source.endpoint.acceptMessagesWhileStopping",
+ "description": "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 queue on the JMS broker. To avoid thi [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.allowReplyManagerQuickStop": {
+ "name": "camel.source.endpoint.allowReplyManagerQuickStop",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.consumerType": {
+ "name": "camel.source.endpoint.consumerType",
+ "description": "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.springframework.jms.listener.Ab [...]
+ "defaultValue": "\"Default\"",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.defaultTaskExecutorType": {
+ "name": "camel.source.endpoint.defaultTaskExecutorType",
+ "description": "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 SimpleAsync for reply consumers [...]
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.eagerLoadingOfProperties": {
+ "name": "camel.source.endpoint.eagerLoadingOfProperties",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.eagerPoisonBody": {
+ "name": "camel.source.endpoint.eagerPoisonBody",
+ "description": "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.",
+ "defaultValue": "\"Poison JMS message due to ${exception.message}\"",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.exceptionHandler": {
+ "name": "camel.source.endpoint.exceptionHandler",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.exchangePattern": {
+ "name": "camel.source.endpoint.exchangePattern",
+ "description": "Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.exposeListenerSession": {
+ "name": "camel.source.endpoint.exposeListenerSession",
+ "description": "Specifies whether the listener session should be exposed when consuming messages.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.replyToSameDestinationAllowed": {
+ "name": "camel.source.endpoint.replyToSameDestinationAllowed",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.taskExecutor": {
+ "name": "camel.source.endpoint.taskExecutor",
+ "description": "Allows you to specify a custom task executor for consuming messages.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.allowSerializedHeaders": {
+ "name": "camel.source.endpoint.allowSerializedHeaders",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.artemisStreamingEnabled": {
+ "name": "camel.source.endpoint.artemisStreamingEnabled",
+ "description": "Whether optimizing for Apache Artemis streaming mode.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.asyncStartListener": {
+ "name": "camel.source.endpoint.asyncStartListener",
+ "description": "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 used, then beware that if [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.asyncStopListener": {
+ "name": "camel.source.endpoint.asyncStopListener",
+ "description": "Whether to stop the JmsConsumer message listener asynchronously, when stopping a route.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.basicPropertyBinding": {
+ "name": "camel.source.endpoint.basicPropertyBinding",
+ "description": "Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.destinationResolver": {
+ "name": "camel.source.endpoint.destinationResolver",
+ "description": "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).",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.errorHandler": {
+ "name": "camel.source.endpoint.errorHandler",
+ "description": "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 errorHandler.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.exceptionListener": {
+ "name": "camel.source.endpoint.exceptionListener",
+ "description": "Specifies the JMS Exception Listener that is to be notified of any underlying JMS exceptions.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.headerFilterStrategy": {
+ "name": "camel.source.endpoint.headerFilterStrategy",
+ "description": "To use a custom HeaderFilterStrategy to filter header to and from Camel message.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.idleConsumerLimit": {
+ "name": "camel.source.endpoint.idleConsumerLimit",
+ "description": "Specify the limit for the number of consumers that are allowed to be idle at any given time.",
+ "defaultValue": "1",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.idleTaskExecutionLimit": {
+ "name": "camel.source.endpoint.idleTaskExecutionLimit",
+ "description": "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.",
+ "defaultValue": "1",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.includeAllJMSXProperties": {
+ "name": "camel.source.endpoint.includeAllJMSXProperties",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.jmsKeyFormatStrategy": {
+ "name": "camel.source.endpoint.jmsKeyFormatStrategy",
+ "description": "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 org.apache.camel.component.jm [...]
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.mapJmsMessage": {
+ "name": "camel.source.endpoint.mapJmsMessage",
+ "description": "Specifies whether Camel should auto map the received JMS message to a suited payload type, such as javax.jms.TextMessage to a String etc.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.maxMessagesPerTask": {
+ "name": "camel.source.endpoint.maxMessagesPerTask",
+ "description": "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.",
+ "defaultValue": "-1",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.messageConverter": {
+ "name": "camel.source.endpoint.messageConverter",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.messageCreatedStrategy": {
+ "name": "camel.source.endpoint.messageCreatedStrategy",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.messageIdEnabled": {
+ "name": "camel.source.endpoint.messageIdEnabled",
+ "description": "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.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.messageListenerContainerFactory": {
+ "name": "camel.source.endpoint.messageListenerContainerFactory",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.messageTimestampEnabled": {
+ "name": "camel.source.endpoint.messageTimestampEnabled",
+ "description": "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.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.pubSubNoLocal": {
+ "name": "camel.source.endpoint.pubSubNoLocal",
+ "description": "Specifies whether to inhibit the delivery of messages published by its own connection.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.receiveTimeout": {
+ "name": "camel.source.endpoint.receiveTimeout",
+ "description": "The timeout for receiving messages (in milliseconds).",
+ "defaultValue": "1000L",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.recoveryInterval": {
+ "name": "camel.source.endpoint.recoveryInterval",
+ "description": "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.",
+ "defaultValue": "5000L",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.requestTimeoutCheckerInterval": {
+ "name": "camel.source.endpoint.requestTimeoutCheckerInterval",
+ "description": "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.",
+ "defaultValue": "1000L",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.synchronous": {
+ "name": "camel.source.endpoint.synchronous",
+ "description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.transferException": {
+ "name": "camel.source.endpoint.transferException",
+ "description": "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 takes precedence. The caught [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.transferExchange": {
+ "name": "camel.source.endpoint.transferExchange",
+ "description": "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 payloads is an Exchange and not [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.useMessageIDAsCorrelationID": {
+ "name": "camel.source.endpoint.useMessageIDAsCorrelationID",
+ "description": "Specifies whether JMSMessageID should always be used as JMSCorrelationID for InOut messages.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.waitForProvisionCorrelationToBeUpdatedCounter": {
+ "name": "camel.source.endpoint.waitForProvisionCorrelationToBeUpdatedCounter",
+ "description": "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.",
+ "defaultValue": "50",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.waitForProvisionCorrelationToBeUpdatedThreadSleepingTime": {
+ "name": "camel.source.endpoint.waitForProvisionCorrelationToBeUpdatedThreadSleepingTime",
+ "description": "Interval in millis to sleep each time while waiting for provisional correlation id to be updated.",
+ "defaultValue": "100L",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.errorHandlerLoggingLevel": {
+ "name": "camel.source.endpoint.errorHandlerLoggingLevel",
+ "description": "Allows to configure the default errorHandler logging level for logging uncaught exceptions. One of: [TRACE] [DEBUG] [INFO] [WARN] [ERROR] [OFF]",
+ "defaultValue": "\"WARN\"",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.errorHandlerLogStackTrace": {
+ "name": "camel.source.endpoint.errorHandlerLogStackTrace",
+ "description": "Allows to control whether stacktraces should be logged or not, by the default errorHandler.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.password": {
+ "name": "camel.source.endpoint.password",
+ "description": "Password to use with the ConnectionFactory. You can also configure username\/password directly on the ConnectionFactory.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.username": {
+ "name": "camel.source.endpoint.username",
+ "description": "Username to use with the ConnectionFactory. You can also configure username\/password directly on the ConnectionFactory.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.transacted": {
+ "name": "camel.source.endpoint.transacted",
+ "description": "Specifies whether to use transacted mode",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.transactedInOut": {
+ "name": "camel.source.endpoint.transactedInOut",
+ "description": "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 container makes its ow [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.lazyCreateTransactionManager": {
+ "name": "camel.source.endpoint.lazyCreateTransactionManager",
+ "description": "If true, Camel will create a JmsTransactionManager, if there is no transactionManager injected when option transacted=true.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.transactionManager": {
+ "name": "camel.source.endpoint.transactionManager",
+ "description": "The Spring transaction manager to use.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.transactionName": {
+ "name": "camel.source.endpoint.transactionName",
+ "description": "The name of the transaction to use.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.transactionTimeout": {
+ "name": "camel.source.endpoint.transactionTimeout",
+ "description": "The timeout value of the transaction (in seconds), if using transacted mode.",
+ "defaultValue": "-1",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.brokerURL": {
+ "name": "camel.component.activemq.brokerURL",
+ "description": "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)",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.clientId": {
+ "name": "camel.component.activemq.clientId",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.connectionFactory": {
+ "name": "camel.component.activemq.connectionFactory",
+ "description": "The connection factory to be use. A connection factory must be configured either on the component or endpoint.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.disableReplyTo": {
+ "name": "camel.component.activemq.disableReplyTo",
+ "description": "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 message brokers and you w [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.durableSubscriptionName": {
+ "name": "camel.component.activemq.durableSubscriptionName",
+ "description": "The durable subscriber name for specifying durable topic subscriptions. The clientId option must be configured as well.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.jmsMessageType": {
+ "name": "camel.component.activemq.jmsMessageType",
+ "description": "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]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.testConnectionOnStartup": {
+ "name": "camel.component.activemq.testConnectionOnStartup",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.usePooledConnection": {
+ "name": "camel.component.activemq.usePooledConnection",
+ "description": "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.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.useSingleConnection": {
+ "name": "camel.component.activemq.useSingleConnection",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.acknowledgementModeName": {
+ "name": "camel.component.activemq.acknowledgementModeName",
+ "description": "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]",
+ "defaultValue": "\"AUTO_ACKNOWLEDGE\"",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.asyncConsumer": {
+ "name": "camel.component.activemq.asyncConsumer",
+ "description": "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 if transacted has been [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.autoStartup": {
+ "name": "camel.component.activemq.autoStartup",
+ "description": "Specifies whether the consumer container should auto-startup.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.cacheLevel": {
+ "name": "camel.component.activemq.cacheLevel",
+ "description": "Sets the cache level by ID for the underlying JMS resources. See cacheLevelName option for more details.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.cacheLevelName": {
+ "name": "camel.component.activemq.cacheLevelName",
+ "description": "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]",
+ "defaultValue": "\"CACHE_AUTO\"",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.concurrentConsumers": {
+ "name": "camel.component.activemq.concurrentConsumers",
+ "description": "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.",
+ "defaultValue": "1",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.maxConcurrentConsumers": {
+ "name": "camel.component.activemq.maxConcurrentConsumers",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.replyTo": {
+ "name": "camel.component.activemq.replyTo",
+ "description": "Provides an explicit ReplyTo destination, which overrides any incoming value of Message.getJMSReplyTo().",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.replyToDeliveryPersistent": {
+ "name": "camel.component.activemq.replyToDeliveryPersistent",
+ "description": "Specifies whether to use persistent delivery by default for replies.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.selector": {
+ "name": "camel.component.activemq.selector",
+ "description": "Sets the JMS selector to use",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.subscriptionDurable": {
+ "name": "camel.component.activemq.subscriptionDurable",
+ "description": "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 pubSubDomain flag as well.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.subscriptionName": {
+ "name": "camel.component.activemq.subscriptionName",
+ "description": "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.0).",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.subscriptionShared": {
+ "name": "camel.component.activemq.subscriptionShared",
+ "description": "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 with subscriptionDurable as we [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.acceptMessagesWhileStopping": {
+ "name": "camel.component.activemq.acceptMessagesWhileStopping",
+ "description": "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 queue on the JMS broker. To avoid thi [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.allowReplyManagerQuickStop": {
+ "name": "camel.component.activemq.allowReplyManagerQuickStop",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.consumerType": {
+ "name": "camel.component.activemq.consumerType",
+ "description": "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.springframework.jms.listener.Ab [...]
+ "defaultValue": "\"Default\"",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.defaultTaskExecutorType": {
+ "name": "camel.component.activemq.defaultTaskExecutorType",
+ "description": "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 SimpleAsync for reply consumers [...]
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.eagerLoadingOfProperties": {
+ "name": "camel.component.activemq.eagerLoadingOfProperties",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.eagerPoisonBody": {
+ "name": "camel.component.activemq.eagerPoisonBody",
+ "description": "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.",
+ "defaultValue": "\"Poison JMS message due to ${exception.message}\"",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.exposeListenerSession": {
+ "name": "camel.component.activemq.exposeListenerSession",
+ "description": "Specifies whether the listener session should be exposed when consuming messages.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.replyToSameDestinationAllowed": {
+ "name": "camel.component.activemq.replyToSameDestinationAllowed",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.taskExecutor": {
+ "name": "camel.component.activemq.taskExecutor",
+ "description": "Allows you to specify a custom task executor for consuming messages.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.allowAutoWiredConnectionFactory": {
+ "name": "camel.component.activemq.allowAutoWiredConnectionFactory",
+ "description": "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.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.allowAutoWiredDestinationResolver": {
+ "name": "camel.component.activemq.allowAutoWiredDestinationResolver",
+ "description": "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.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.allowSerializedHeaders": {
+ "name": "camel.component.activemq.allowSerializedHeaders",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.artemisStreamingEnabled": {
+ "name": "camel.component.activemq.artemisStreamingEnabled",
+ "description": "Whether optimizing for Apache Artemis streaming mode.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.asyncStartListener": {
+ "name": "camel.component.activemq.asyncStartListener",
+ "description": "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 used, then beware that if [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.asyncStopListener": {
+ "name": "camel.component.activemq.asyncStopListener",
+ "description": "Whether to stop the JmsConsumer message listener asynchronously, when stopping a route.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.basicPropertyBinding": {
+ "name": "camel.component.activemq.basicPropertyBinding",
+ "description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.configuration": {
+ "name": "camel.component.activemq.configuration",
+ "description": "To use a shared JMS configuration",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.destinationResolver": {
+ "name": "camel.component.activemq.destinationResolver",
+ "description": "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).",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.errorHandler": {
+ "name": "camel.component.activemq.errorHandler",
+ "description": "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 errorHandler.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.exceptionListener": {
+ "name": "camel.component.activemq.exceptionListener",
+ "description": "Specifies the JMS Exception Listener that is to be notified of any underlying JMS exceptions.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.idleConsumerLimit": {
+ "name": "camel.component.activemq.idleConsumerLimit",
+ "description": "Specify the limit for the number of consumers that are allowed to be idle at any given time.",
+ "defaultValue": "1",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.idleTaskExecutionLimit": {
+ "name": "camel.component.activemq.idleTaskExecutionLimit",
+ "description": "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.",
+ "defaultValue": "1",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.includeAllJMSXProperties": {
+ "name": "camel.component.activemq.includeAllJMSXProperties",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.jmsKeyFormatStrategy": {
+ "name": "camel.component.activemq.jmsKeyFormatStrategy",
+ "description": "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 org.apache.camel.component.jm [...]
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.mapJmsMessage": {
+ "name": "camel.component.activemq.mapJmsMessage",
+ "description": "Specifies whether Camel should auto map the received JMS message to a suited payload type, such as javax.jms.TextMessage to a String etc.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.maxMessagesPerTask": {
+ "name": "camel.component.activemq.maxMessagesPerTask",
+ "description": "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.",
+ "defaultValue": "-1",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.messageConverter": {
+ "name": "camel.component.activemq.messageConverter",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.messageCreatedStrategy": {
+ "name": "camel.component.activemq.messageCreatedStrategy",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.messageIdEnabled": {
+ "name": "camel.component.activemq.messageIdEnabled",
+ "description": "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.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.messageListenerContainerFactory": {
+ "name": "camel.component.activemq.messageListenerContainerFactory",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.messageTimestampEnabled": {
+ "name": "camel.component.activemq.messageTimestampEnabled",
+ "description": "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.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.pubSubNoLocal": {
+ "name": "camel.component.activemq.pubSubNoLocal",
+ "description": "Specifies whether to inhibit the delivery of messages published by its own connection.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.queueBrowseStrategy": {
+ "name": "camel.component.activemq.queueBrowseStrategy",
+ "description": "To use a custom QueueBrowseStrategy when browsing queues",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.receiveTimeout": {
+ "name": "camel.component.activemq.receiveTimeout",
+ "description": "The timeout for receiving messages (in milliseconds).",
+ "defaultValue": "1000L",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.recoveryInterval": {
+ "name": "camel.component.activemq.recoveryInterval",
+ "description": "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.",
+ "defaultValue": "5000L",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.requestTimeoutCheckerInterval": {
+ "name": "camel.component.activemq.requestTimeoutCheckerInterval",
+ "description": "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.",
+ "defaultValue": "1000L",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.transferException": {
+ "name": "camel.component.activemq.transferException",
+ "description": "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 takes precedence. The caught [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.transferExchange": {
+ "name": "camel.component.activemq.transferExchange",
+ "description": "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 payloads is an Exchange and not [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.trustAllPackages": {
+ "name": "camel.component.activemq.trustAllPackages",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.useMessageIDAsCorrelationID": {
+ "name": "camel.component.activemq.useMessageIDAsCorrelationID",
+ "description": "Specifies whether JMSMessageID should always be used as JMSCorrelationID for InOut messages.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.waitForProvisionCorrelationToBeUpdatedCounter": {
+ "name": "camel.component.activemq.waitForProvisionCorrelationToBeUpdatedCounter",
+ "description": "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.",
+ "defaultValue": "50",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.waitForProvisionCorrelationToBeUpdatedThreadSleepingTime": {
+ "name": "camel.component.activemq.waitForProvisionCorrelationToBeUpdatedThreadSleepingTime",
+ "description": "Interval in millis to sleep each time while waiting for provisional correlation id to be updated.",
+ "defaultValue": "100L",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.headerFilterStrategy": {
+ "name": "camel.component.activemq.headerFilterStrategy",
+ "description": "To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.errorHandlerLoggingLevel": {
+ "name": "camel.component.activemq.errorHandlerLoggingLevel",
+ "description": "Allows to configure the default errorHandler logging level for logging uncaught exceptions. One of: [TRACE] [DEBUG] [INFO] [WARN] [ERROR] [OFF]",
+ "defaultValue": "\"WARN\"",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.errorHandlerLogStackTrace": {
+ "name": "camel.component.activemq.errorHandlerLogStackTrace",
+ "description": "Allows to control whether stacktraces should be logged or not, by the default errorHandler.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.password": {
+ "name": "camel.component.activemq.password",
+ "description": "Password to use with the ConnectionFactory. You can also configure username\/password directly on the ConnectionFactory.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.username": {
+ "name": "camel.component.activemq.username",
+ "description": "Username to use with the ConnectionFactory. You can also configure username\/password directly on the ConnectionFactory.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.transacted": {
+ "name": "camel.component.activemq.transacted",
+ "description": "Specifies whether to use transacted mode",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.transactedInOut": {
+ "name": "camel.component.activemq.transactedInOut",
+ "description": "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 container makes its ow [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.lazyCreateTransactionManager": {
+ "name": "camel.component.activemq.lazyCreateTransactionManager",
+ "description": "If true, Camel will create a JmsTransactionManager, if there is no transactionManager injected when option transacted=true.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.transactionManager": {
+ "name": "camel.component.activemq.transactionManager",
+ "description": "The Spring transaction manager to use.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.transactionName": {
+ "name": "camel.component.activemq.transactionName",
+ "description": "The name of the transaction to use.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.activemq.transactionTimeout": {
+ "name": "camel.component.activemq.transactionTimeout",
+ "description": "The timeout value of the transaction (in seconds), if using transacted mode.",
+ "defaultValue": "-1",
+ "priority": "MEDIUM"
+ }
+ }
+}
diff --git a/connectors/camel-ahc-kafka-connector/src/generated/resources/camel-ahc-kafka-sink-connector.json b/connectors/camel-ahc-kafka-connector/src/generated/resources/camel-ahc-kafka-sink-connector.json
new file mode 100644
index 0000000..9888efa
--- /dev/null
+++ b/connectors/camel-ahc-kafka-connector/src/generated/resources/camel-ahc-kafka-sink-connector.json
@@ -0,0 +1,161 @@
+{
+ "connector": {
+ "class": "org.apache.camel.kafkaconnector.ahc.CamelAhcSinkConnector",
+ "artifactId": "camel-ahc",
+ "groupId": "org.apache.camel",
+ "title": "camel-ahc",
+ "version": "0.6.0-SNAPSHOT"
+ },
+ "properties": {
+ "camel.sink.path.httpUri": {
+ "name": "camel.sink.path.httpUri",
+ "description": "The URI to use such as http:\/\/hostname:port\/path",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.sink.endpoint.bridgeEndpoint": {
+ "name": "camel.sink.endpoint.bridgeEndpoint",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.bufferSize": {
+ "name": "camel.sink.endpoint.bufferSize",
+ "description": "The initial in-memory buffer size used when transferring data between Camel and AHC Client.",
+ "defaultValue": "4096",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.connectionClose": {
+ "name": "camel.sink.endpoint.connectionClose",
+ "description": "Define if the Connection Close header has to be added to HTTP Request. This parameter is false by default",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.cookieHandler": {
+ "name": "camel.sink.endpoint.cookieHandler",
+ "description": "Configure a cookie handler to maintain a HTTP session",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.headerFilterStrategy": {
+ "name": "camel.sink.endpoint.headerFilterStrategy",
+ "description": "To use a custom HeaderFilterStrategy to filter header to and from Camel message.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.lazyStartProducer": {
+ "name": "camel.sink.endpoint.lazyStartProducer",
+ "description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be 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 creating and starting the pr [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.throwExceptionOnFailure": {
+ "name": "camel.sink.endpoint.throwExceptionOnFailure",
+ "description": "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.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.transferException": {
+ "name": "camel.sink.endpoint.transferException",
+ "description": "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 you enable this then be [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.basicPropertyBinding": {
+ "name": "camel.sink.endpoint.basicPropertyBinding",
+ "description": "Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.binding": {
+ "name": "camel.sink.endpoint.binding",
+ "description": "To use a custom AhcBinding which allows to control how to bind between AHC and Camel.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.clientConfig": {
+ "name": "camel.sink.endpoint.clientConfig",
+ "description": "To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.clientConfigOptions": {
+ "name": "camel.sink.endpoint.clientConfigOptions",
+ "description": "To configure the AsyncHttpClientConfig using the key\/values from the Map.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.synchronous": {
+ "name": "camel.sink.endpoint.synchronous",
+ "description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.clientConfigRealmOptions": {
+ "name": "camel.sink.endpoint.clientConfigRealmOptions",
+ "description": "To configure the AsyncHttpClientConfig Realm using the key\/values from the Map.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.sslContextParameters": {
+ "name": "camel.sink.endpoint.sslContextParameters",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc.lazyStartProducer": {
+ "name": "camel.component.ahc.lazyStartProducer",
+ "description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be 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 creating and starting the pr [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc.allowJavaSerializedObject": {
+ "name": "camel.component.ahc.allowJavaSerializedObject",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc.basicPropertyBinding": {
+ "name": "camel.component.ahc.basicPropertyBinding",
+ "description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc.binding": {
+ "name": "camel.component.ahc.binding",
+ "description": "To use a custom AhcBinding which allows to control how to bind between AHC and Camel.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc.client": {
+ "name": "camel.component.ahc.client",
+ "description": "To use a custom AsyncHttpClient",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc.clientConfig": {
+ "name": "camel.component.ahc.clientConfig",
+ "description": "To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc.headerFilterStrategy": {
+ "name": "camel.component.ahc.headerFilterStrategy",
+ "description": "To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc.sslContextParameters": {
+ "name": "camel.component.ahc.sslContextParameters",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc.useGlobalSslContextParameters": {
+ "name": "camel.component.ahc.useGlobalSslContextParameters",
+ "description": "Enable usage of global SSL context parameters.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ }
+ }
+}
diff --git a/connectors/camel-ahc-ws-kafka-connector/src/generated/resources/camel-ahc-ws-kafka-sink-connector.json b/connectors/camel-ahc-ws-kafka-connector/src/generated/resources/camel-ahc-ws-kafka-sink-connector.json
new file mode 100644
index 0000000..408dd98
--- /dev/null
+++ b/connectors/camel-ahc-ws-kafka-connector/src/generated/resources/camel-ahc-ws-kafka-sink-connector.json
@@ -0,0 +1,167 @@
+{
+ "connector": {
+ "class": "org.apache.camel.kafkaconnector.ahcws.CamelAhcwsSinkConnector",
+ "artifactId": "camel-ahc-ws",
+ "groupId": "org.apache.camel",
+ "title": "camel-ahc-ws",
+ "version": "0.6.0-SNAPSHOT"
+ },
+ "properties": {
+ "camel.sink.path.httpUri": {
+ "name": "camel.sink.path.httpUri",
+ "description": "The URI to use such as http:\/\/hostname:port\/path",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.sink.endpoint.bridgeEndpoint": {
+ "name": "camel.sink.endpoint.bridgeEndpoint",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.bufferSize": {
+ "name": "camel.sink.endpoint.bufferSize",
+ "description": "The initial in-memory buffer size used when transferring data between Camel and AHC Client.",
+ "defaultValue": "4096",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.headerFilterStrategy": {
+ "name": "camel.sink.endpoint.headerFilterStrategy",
+ "description": "To use a custom HeaderFilterStrategy to filter header to and from Camel message.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.throwExceptionOnFailure": {
+ "name": "camel.sink.endpoint.throwExceptionOnFailure",
+ "description": "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.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.transferException": {
+ "name": "camel.sink.endpoint.transferException",
+ "description": "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 you enable this then be [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.connectionClose": {
+ "name": "camel.sink.endpoint.connectionClose",
+ "description": "Define if the Connection Close header has to be added to HTTP Request. This parameter is false by default",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.cookieHandler": {
+ "name": "camel.sink.endpoint.cookieHandler",
+ "description": "Configure a cookie handler to maintain a HTTP session",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.lazyStartProducer": {
+ "name": "camel.sink.endpoint.lazyStartProducer",
+ "description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be 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 creating and starting the pr [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.useStreaming": {
+ "name": "camel.sink.endpoint.useStreaming",
+ "description": "To enable streaming to send data as multiple text fragments.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.basicPropertyBinding": {
+ "name": "camel.sink.endpoint.basicPropertyBinding",
+ "description": "Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.binding": {
+ "name": "camel.sink.endpoint.binding",
+ "description": "To use a custom AhcBinding which allows to control how to bind between AHC and Camel.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.clientConfig": {
+ "name": "camel.sink.endpoint.clientConfig",
+ "description": "To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.clientConfigOptions": {
+ "name": "camel.sink.endpoint.clientConfigOptions",
+ "description": "To configure the AsyncHttpClientConfig using the key\/values from the Map.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.synchronous": {
+ "name": "camel.sink.endpoint.synchronous",
+ "description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.clientConfigRealmOptions": {
+ "name": "camel.sink.endpoint.clientConfigRealmOptions",
+ "description": "To configure the AsyncHttpClientConfig Realm using the key\/values from the Map.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.sslContextParameters": {
+ "name": "camel.sink.endpoint.sslContextParameters",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc-ws.lazyStartProducer": {
+ "name": "camel.component.ahc-ws.lazyStartProducer",
+ "description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be 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 creating and starting the pr [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc-ws.allowJavaSerializedObject": {
+ "name": "camel.component.ahc-ws.allowJavaSerializedObject",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc-ws.basicPropertyBinding": {
+ "name": "camel.component.ahc-ws.basicPropertyBinding",
+ "description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc-ws.binding": {
+ "name": "camel.component.ahc-ws.binding",
+ "description": "To use a custom AhcBinding which allows to control how to bind between AHC and Camel.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc-ws.client": {
+ "name": "camel.component.ahc-ws.client",
+ "description": "To use a custom AsyncHttpClient",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc-ws.clientConfig": {
+ "name": "camel.component.ahc-ws.clientConfig",
+ "description": "To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc-ws.headerFilterStrategy": {
+ "name": "camel.component.ahc-ws.headerFilterStrategy",
+ "description": "To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc-ws.sslContextParameters": {
+ "name": "camel.component.ahc-ws.sslContextParameters",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc-ws.useGlobalSslContextParameters": {
+ "name": "camel.component.ahc-ws.useGlobalSslContextParameters",
+ "description": "Enable usage of global SSL context parameters.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ }
+ }
+}
diff --git a/connectors/camel-ahc-ws-kafka-connector/src/generated/resources/camel-ahc-ws-kafka-source-connector.json b/connectors/camel-ahc-ws-kafka-connector/src/generated/resources/camel-ahc-ws-kafka-source-connector.json
new file mode 100644
index 0000000..77918f7
--- /dev/null
+++ b/connectors/camel-ahc-ws-kafka-connector/src/generated/resources/camel-ahc-ws-kafka-source-connector.json
@@ -0,0 +1,167 @@
+{
+ "connector": {
+ "class": "org.apache.camel.kafkaconnector.ahcws.CamelAhcwsSourceConnector",
+ "artifactId": "camel-ahc-ws",
+ "groupId": "org.apache.camel",
+ "title": "camel-ahc-ws",
+ "version": "0.6.0-SNAPSHOT"
+ },
+ "properties": {
+ "camel.source.path.httpUri": {
+ "name": "camel.source.path.httpUri",
+ "description": "The URI to use such as http:\/\/hostname:port\/path",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.source.endpoint.bridgeEndpoint": {
+ "name": "camel.source.endpoint.bridgeEndpoint",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.bufferSize": {
+ "name": "camel.source.endpoint.bufferSize",
+ "description": "The initial in-memory buffer size used when transferring data between Camel and AHC Client.",
+ "defaultValue": "4096",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.headerFilterStrategy": {
+ "name": "camel.source.endpoint.headerFilterStrategy",
+ "description": "To use a custom HeaderFilterStrategy to filter header to and from Camel message.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.throwExceptionOnFailure": {
+ "name": "camel.source.endpoint.throwExceptionOnFailure",
+ "description": "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.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.transferException": {
+ "name": "camel.source.endpoint.transferException",
+ "description": "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 you enable this then be [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.bridgeErrorHandler": {
+ "name": "camel.source.endpoint.bridgeErrorHandler",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.sendMessageOnError": {
+ "name": "camel.source.endpoint.sendMessageOnError",
+ "description": "Whether to send an message if the web-socket listener received an error.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.exceptionHandler": {
+ "name": "camel.source.endpoint.exceptionHandler",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.exchangePattern": {
+ "name": "camel.source.endpoint.exchangePattern",
+ "description": "Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.basicPropertyBinding": {
+ "name": "camel.source.endpoint.basicPropertyBinding",
+ "description": "Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.binding": {
+ "name": "camel.source.endpoint.binding",
+ "description": "To use a custom AhcBinding which allows to control how to bind between AHC and Camel.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.clientConfig": {
+ "name": "camel.source.endpoint.clientConfig",
+ "description": "To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.clientConfigOptions": {
+ "name": "camel.source.endpoint.clientConfigOptions",
+ "description": "To configure the AsyncHttpClientConfig using the key\/values from the Map.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.synchronous": {
+ "name": "camel.source.endpoint.synchronous",
+ "description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.clientConfigRealmOptions": {
+ "name": "camel.source.endpoint.clientConfigRealmOptions",
+ "description": "To configure the AsyncHttpClientConfig Realm using the key\/values from the Map.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.sslContextParameters": {
+ "name": "camel.source.endpoint.sslContextParameters",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc-ws.bridgeErrorHandler": {
+ "name": "camel.component.ahc-ws.bridgeErrorHandler",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc-ws.allowJavaSerializedObject": {
+ "name": "camel.component.ahc-ws.allowJavaSerializedObject",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc-ws.basicPropertyBinding": {
+ "name": "camel.component.ahc-ws.basicPropertyBinding",
+ "description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc-ws.binding": {
+ "name": "camel.component.ahc-ws.binding",
+ "description": "To use a custom AhcBinding which allows to control how to bind between AHC and Camel.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc-ws.client": {
+ "name": "camel.component.ahc-ws.client",
+ "description": "To use a custom AsyncHttpClient",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc-ws.clientConfig": {
+ "name": "camel.component.ahc-ws.clientConfig",
+ "description": "To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc-ws.headerFilterStrategy": {
+ "name": "camel.component.ahc-ws.headerFilterStrategy",
+ "description": "To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc-ws.sslContextParameters": {
+ "name": "camel.component.ahc-ws.sslContextParameters",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc-ws.useGlobalSslContextParameters": {
+ "name": "camel.component.ahc-ws.useGlobalSslContextParameters",
+ "description": "Enable usage of global SSL context parameters.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ }
+ }
+}
diff --git a/connectors/camel-ahc-wss-kafka-connector/src/generated/resources/camel-ahc-wss-kafka-sink-connector.json b/connectors/camel-ahc-wss-kafka-connector/src/generated/resources/camel-ahc-wss-kafka-sink-connector.json
new file mode 100644
index 0000000..be37c68
--- /dev/null
+++ b/connectors/camel-ahc-wss-kafka-connector/src/generated/resources/camel-ahc-wss-kafka-sink-connector.json
@@ -0,0 +1,167 @@
+{
+ "connector": {
+ "class": "org.apache.camel.kafkaconnector.ahcwss.CamelAhcwssSinkConnector",
+ "artifactId": "camel-ahc-wss",
+ "groupId": "org.apache.camel",
+ "title": "camel-ahc-wss",
+ "version": "0.6.0-SNAPSHOT"
+ },
+ "properties": {
+ "camel.sink.path.httpUri": {
+ "name": "camel.sink.path.httpUri",
+ "description": "The URI to use such as http:\/\/hostname:port\/path",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.sink.endpoint.bridgeEndpoint": {
+ "name": "camel.sink.endpoint.bridgeEndpoint",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.bufferSize": {
+ "name": "camel.sink.endpoint.bufferSize",
+ "description": "The initial in-memory buffer size used when transferring data between Camel and AHC Client.",
+ "defaultValue": "4096",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.headerFilterStrategy": {
+ "name": "camel.sink.endpoint.headerFilterStrategy",
+ "description": "To use a custom HeaderFilterStrategy to filter header to and from Camel message.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.throwExceptionOnFailure": {
+ "name": "camel.sink.endpoint.throwExceptionOnFailure",
+ "description": "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.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.transferException": {
+ "name": "camel.sink.endpoint.transferException",
+ "description": "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 you enable this then be [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.connectionClose": {
+ "name": "camel.sink.endpoint.connectionClose",
+ "description": "Define if the Connection Close header has to be added to HTTP Request. This parameter is false by default",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.cookieHandler": {
+ "name": "camel.sink.endpoint.cookieHandler",
+ "description": "Configure a cookie handler to maintain a HTTP session",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.lazyStartProducer": {
+ "name": "camel.sink.endpoint.lazyStartProducer",
+ "description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be 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 creating and starting the pr [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.useStreaming": {
+ "name": "camel.sink.endpoint.useStreaming",
+ "description": "To enable streaming to send data as multiple text fragments.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.basicPropertyBinding": {
+ "name": "camel.sink.endpoint.basicPropertyBinding",
+ "description": "Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.binding": {
+ "name": "camel.sink.endpoint.binding",
+ "description": "To use a custom AhcBinding which allows to control how to bind between AHC and Camel.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.clientConfig": {
+ "name": "camel.sink.endpoint.clientConfig",
+ "description": "To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.clientConfigOptions": {
+ "name": "camel.sink.endpoint.clientConfigOptions",
+ "description": "To configure the AsyncHttpClientConfig using the key\/values from the Map.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.synchronous": {
+ "name": "camel.sink.endpoint.synchronous",
+ "description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.clientConfigRealmOptions": {
+ "name": "camel.sink.endpoint.clientConfigRealmOptions",
+ "description": "To configure the AsyncHttpClientConfig Realm using the key\/values from the Map.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.sslContextParameters": {
+ "name": "camel.sink.endpoint.sslContextParameters",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc-wss.lazyStartProducer": {
+ "name": "camel.component.ahc-wss.lazyStartProducer",
+ "description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be 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 creating and starting the pr [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc-wss.allowJavaSerializedObject": {
+ "name": "camel.component.ahc-wss.allowJavaSerializedObject",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc-wss.basicPropertyBinding": {
+ "name": "camel.component.ahc-wss.basicPropertyBinding",
+ "description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc-wss.binding": {
+ "name": "camel.component.ahc-wss.binding",
+ "description": "To use a custom AhcBinding which allows to control how to bind between AHC and Camel.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc-wss.client": {
+ "name": "camel.component.ahc-wss.client",
+ "description": "To use a custom AsyncHttpClient",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc-wss.clientConfig": {
+ "name": "camel.component.ahc-wss.clientConfig",
+ "description": "To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc-wss.headerFilterStrategy": {
+ "name": "camel.component.ahc-wss.headerFilterStrategy",
+ "description": "To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc-wss.sslContextParameters": {
+ "name": "camel.component.ahc-wss.sslContextParameters",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc-wss.useGlobalSslContextParameters": {
+ "name": "camel.component.ahc-wss.useGlobalSslContextParameters",
+ "description": "Enable usage of global SSL context parameters.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ }
+ }
+}
diff --git a/connectors/camel-ahc-wss-kafka-connector/src/generated/resources/camel-ahc-wss-kafka-source-connector.json b/connectors/camel-ahc-wss-kafka-connector/src/generated/resources/camel-ahc-wss-kafka-source-connector.json
new file mode 100644
index 0000000..de7d49d
--- /dev/null
+++ b/connectors/camel-ahc-wss-kafka-connector/src/generated/resources/camel-ahc-wss-kafka-source-connector.json
@@ -0,0 +1,167 @@
+{
+ "connector": {
+ "class": "org.apache.camel.kafkaconnector.ahcwss.CamelAhcwssSourceConnector",
+ "artifactId": "camel-ahc-wss",
+ "groupId": "org.apache.camel",
+ "title": "camel-ahc-wss",
+ "version": "0.6.0-SNAPSHOT"
+ },
+ "properties": {
+ "camel.source.path.httpUri": {
+ "name": "camel.source.path.httpUri",
+ "description": "The URI to use such as http:\/\/hostname:port\/path",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.source.endpoint.bridgeEndpoint": {
+ "name": "camel.source.endpoint.bridgeEndpoint",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.bufferSize": {
+ "name": "camel.source.endpoint.bufferSize",
+ "description": "The initial in-memory buffer size used when transferring data between Camel and AHC Client.",
+ "defaultValue": "4096",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.headerFilterStrategy": {
+ "name": "camel.source.endpoint.headerFilterStrategy",
+ "description": "To use a custom HeaderFilterStrategy to filter header to and from Camel message.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.throwExceptionOnFailure": {
+ "name": "camel.source.endpoint.throwExceptionOnFailure",
+ "description": "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.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.transferException": {
+ "name": "camel.source.endpoint.transferException",
+ "description": "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 you enable this then be [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.bridgeErrorHandler": {
+ "name": "camel.source.endpoint.bridgeErrorHandler",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.sendMessageOnError": {
+ "name": "camel.source.endpoint.sendMessageOnError",
+ "description": "Whether to send an message if the web-socket listener received an error.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.exceptionHandler": {
+ "name": "camel.source.endpoint.exceptionHandler",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.exchangePattern": {
+ "name": "camel.source.endpoint.exchangePattern",
+ "description": "Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.basicPropertyBinding": {
+ "name": "camel.source.endpoint.basicPropertyBinding",
+ "description": "Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.binding": {
+ "name": "camel.source.endpoint.binding",
+ "description": "To use a custom AhcBinding which allows to control how to bind between AHC and Camel.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.clientConfig": {
+ "name": "camel.source.endpoint.clientConfig",
+ "description": "To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.clientConfigOptions": {
+ "name": "camel.source.endpoint.clientConfigOptions",
+ "description": "To configure the AsyncHttpClientConfig using the key\/values from the Map.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.synchronous": {
+ "name": "camel.source.endpoint.synchronous",
+ "description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.clientConfigRealmOptions": {
+ "name": "camel.source.endpoint.clientConfigRealmOptions",
+ "description": "To configure the AsyncHttpClientConfig Realm using the key\/values from the Map.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.sslContextParameters": {
+ "name": "camel.source.endpoint.sslContextParameters",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc-wss.bridgeErrorHandler": {
+ "name": "camel.component.ahc-wss.bridgeErrorHandler",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc-wss.allowJavaSerializedObject": {
+ "name": "camel.component.ahc-wss.allowJavaSerializedObject",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc-wss.basicPropertyBinding": {
+ "name": "camel.component.ahc-wss.basicPropertyBinding",
+ "description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc-wss.binding": {
+ "name": "camel.component.ahc-wss.binding",
+ "description": "To use a custom AhcBinding which allows to control how to bind between AHC and Camel.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc-wss.client": {
+ "name": "camel.component.ahc-wss.client",
+ "description": "To use a custom AsyncHttpClient",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc-wss.clientConfig": {
+ "name": "camel.component.ahc-wss.clientConfig",
+ "description": "To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc-wss.headerFilterStrategy": {
+ "name": "camel.component.ahc-wss.headerFilterStrategy",
+ "description": "To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc-wss.sslContextParameters": {
+ "name": "camel.component.ahc-wss.sslContextParameters",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.ahc-wss.useGlobalSslContextParameters": {
+ "name": "camel.component.ahc-wss.useGlobalSslContextParameters",
+ "description": "Enable usage of global SSL context parameters.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ }
+ }
+}
diff --git a/connectors/camel-amqp-kafka-connector/src/generated/resources/camel-amqp-kafka-sink-connector.json b/connectors/camel-amqp-kafka-connector/src/generated/resources/camel-amqp-kafka-sink-connector.json
new file mode 100644
index 0000000..89862f6
--- /dev/null
+++ b/connectors/camel-amqp-kafka-connector/src/generated/resources/camel-amqp-kafka-sink-connector.json
@@ -0,0 +1,875 @@
+{
+ "connector": {
+ "class": "org.apache.camel.kafkaconnector.amqp.CamelAmqpSinkConnector",
+ "artifactId": "camel-amqp",
+ "groupId": "org.apache.camel",
+ "title": "camel-amqp",
+ "version": "0.6.0-SNAPSHOT"
+ },
+ "properties": {
+ "camel.sink.path.destinationType": {
+ "name": "camel.sink.path.destinationType",
+ "description": "The kind of destination to use One of: [queue] [topic] [temp-queue] [temp-topic]",
+ "defaultValue": "\"queue\"",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.path.destinationName": {
+ "name": "camel.sink.path.destinationName",
+ "description": "Name of the queue or topic to use as destination",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.sink.endpoint.clientId": {
+ "name": "camel.sink.endpoint.clientId",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.connectionFactory": {
+ "name": "camel.sink.endpoint.connectionFactory",
+ "description": "The connection factory to be use. A connection factory must be configured either on the component or endpoint.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.disableReplyTo": {
+ "name": "camel.sink.endpoint.disableReplyTo",
+ "description": "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 message brokers and you w [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.durableSubscriptionName": {
+ "name": "camel.sink.endpoint.durableSubscriptionName",
+ "description": "The durable subscriber name for specifying durable topic subscriptions. The clientId option must be configured as well.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.jmsMessageType": {
+ "name": "camel.sink.endpoint.jmsMessageType",
+ "description": "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]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.testConnectionOnStartup": {
+ "name": "camel.sink.endpoint.testConnectionOnStartup",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.deliveryDelay": {
+ "name": "camel.sink.endpoint.deliveryDelay",
+ "description": "Sets delivery delay to use for send calls for JMS. This option requires JMS 2.0 compliant broker.",
+ "defaultValue": "-1L",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.deliveryMode": {
+ "name": "camel.sink.endpoint.deliveryMode",
+ "description": "Specifies the delivery mode to be used. Possibles values are those defined by javax.jms.DeliveryMode. NON_PERSISTENT = 1 and PERSISTENT = 2. One of: [1] [2]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.deliveryPersistent": {
+ "name": "camel.sink.endpoint.deliveryPersistent",
+ "description": "Specifies whether persistent delivery is used by default.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.explicitQosEnabled": {
+ "name": "camel.sink.endpoint.explicitQosEnabled",
+ "description": "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.",
+ "defaultValue": "\"false\"",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.formatDateHeadersToIso8601": {
+ "name": "camel.sink.endpoint.formatDateHeadersToIso8601",
+ "description": "Sets whether JMS date properties should be formatted according to the ISO 8601 standard.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.lazyStartProducer": {
+ "name": "camel.sink.endpoint.lazyStartProducer",
+ "description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be 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 creating and starting the pr [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.preserveMessageQos": {
+ "name": "camel.sink.endpoint.preserveMessageQos",
+ "description": "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 explicitQosEnabled option, by cont [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.priority": {
+ "name": "camel.sink.endpoint.priority",
+ "description": "Values greater than 1 specify the message priority when sending (where 0 is the lowest priority and 9 is the highest). The explicitQosEnabled option must also be enabled in order for this option to have any effect. One of: [1] [2] [3] [4] [5] [6] [7] [8] [9]",
+ "defaultValue": "4",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.replyToConcurrentConsumers": {
+ "name": "camel.sink.endpoint.replyToConcurrentConsumers",
+ "description": "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.",
+ "defaultValue": "1",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.replyToMaxConcurrentConsumers": {
+ "name": "camel.sink.endpoint.replyToMaxConcurrentConsumers",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.replyToOnTimeoutMaxConcurrentConsumers": {
+ "name": "camel.sink.endpoint.replyToOnTimeoutMaxConcurrentConsumers",
+ "description": "Specifies the maximum number of concurrent consumers for continue routing when timeout occurred when using request\/reply over JMS.",
+ "defaultValue": "1",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.replyToOverride": {
+ "name": "camel.sink.endpoint.replyToOverride",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.replyToType": {
+ "name": "camel.sink.endpoint.replyToType",
+ "description": "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 running in a clus [...]
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.requestTimeout": {
+ "name": "camel.sink.endpoint.requestTimeout",
+ "description": "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.",
+ "defaultValue": "20000L",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.timeToLive": {
+ "name": "camel.sink.endpoint.timeToLive",
+ "description": "When sending messages, specifies the time-to-live of the message (in milliseconds).",
+ "defaultValue": "-1L",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.allowAdditionalHeaders": {
+ "name": "camel.sink.endpoint.allowAdditionalHeaders",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.allowNullBody": {
+ "name": "camel.sink.endpoint.allowNullBody",
+ "description": "Whether to allow sending messages with no body. If this option is false and the message body is null, then an JMSException is thrown.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.alwaysCopyMessage": {
+ "name": "camel.sink.endpoint.alwaysCopyMessage",
+ "description": "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)",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.correlationProperty": {
+ "name": "camel.sink.endpoint.correlationProperty",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.disableTimeToLive": {
+ "name": "camel.sink.endpoint.disableTimeToLive",
+ "description": "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 message will not expire [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.forceSendOriginalMessage": {
+ "name": "camel.sink.endpoint.forceSendOriginalMessage",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.includeSentJMSMessageID": {
+ "name": "camel.sink.endpoint.includeSentJMSMessageID",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.replyToCacheLevelName": {
+ "name": "camel.sink.endpoint.replyToCacheLevelName",
+ "description": "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 then CACHE_NONE is not allow [...]
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.replyToDestinationSelectorName": {
+ "name": "camel.sink.endpoint.replyToDestinationSelectorName",
+ "description": "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).",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.streamMessageTypeEnabled": {
+ "name": "camel.sink.endpoint.streamMessageTypeEnabled",
+ "description": "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 until no more data.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.allowSerializedHeaders": {
+ "name": "camel.sink.endpoint.allowSerializedHeaders",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.artemisStreamingEnabled": {
+ "name": "camel.sink.endpoint.artemisStreamingEnabled",
+ "description": "Whether optimizing for Apache Artemis streaming mode.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.asyncStartListener": {
+ "name": "camel.sink.endpoint.asyncStartListener",
+ "description": "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 used, then beware that if [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.asyncStopListener": {
+ "name": "camel.sink.endpoint.asyncStopListener",
+ "description": "Whether to stop the JmsConsumer message listener asynchronously, when stopping a route.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.basicPropertyBinding": {
+ "name": "camel.sink.endpoint.basicPropertyBinding",
+ "description": "Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.destinationResolver": {
+ "name": "camel.sink.endpoint.destinationResolver",
+ "description": "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).",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.errorHandler": {
+ "name": "camel.sink.endpoint.errorHandler",
+ "description": "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 errorHandler.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.exceptionListener": {
+ "name": "camel.sink.endpoint.exceptionListener",
+ "description": "Specifies the JMS Exception Listener that is to be notified of any underlying JMS exceptions.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.headerFilterStrategy": {
+ "name": "camel.sink.endpoint.headerFilterStrategy",
+ "description": "To use a custom HeaderFilterStrategy to filter header to and from Camel message.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.idleConsumerLimit": {
+ "name": "camel.sink.endpoint.idleConsumerLimit",
+ "description": "Specify the limit for the number of consumers that are allowed to be idle at any given time.",
+ "defaultValue": "1",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.idleTaskExecutionLimit": {
+ "name": "camel.sink.endpoint.idleTaskExecutionLimit",
+ "description": "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.",
+ "defaultValue": "1",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.includeAllJMSXProperties": {
+ "name": "camel.sink.endpoint.includeAllJMSXProperties",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.jmsKeyFormatStrategy": {
+ "name": "camel.sink.endpoint.jmsKeyFormatStrategy",
+ "description": "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 org.apache.camel.component.jm [...]
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.mapJmsMessage": {
+ "name": "camel.sink.endpoint.mapJmsMessage",
+ "description": "Specifies whether Camel should auto map the received JMS message to a suited payload type, such as javax.jms.TextMessage to a String etc.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.maxMessagesPerTask": {
+ "name": "camel.sink.endpoint.maxMessagesPerTask",
+ "description": "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.",
+ "defaultValue": "-1",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.messageConverter": {
+ "name": "camel.sink.endpoint.messageConverter",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.messageCreatedStrategy": {
+ "name": "camel.sink.endpoint.messageCreatedStrategy",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.messageIdEnabled": {
+ "name": "camel.sink.endpoint.messageIdEnabled",
+ "description": "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.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.messageListenerContainerFactory": {
+ "name": "camel.sink.endpoint.messageListenerContainerFactory",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.messageTimestampEnabled": {
+ "name": "camel.sink.endpoint.messageTimestampEnabled",
+ "description": "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.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.pubSubNoLocal": {
+ "name": "camel.sink.endpoint.pubSubNoLocal",
+ "description": "Specifies whether to inhibit the delivery of messages published by its own connection.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.receiveTimeout": {
+ "name": "camel.sink.endpoint.receiveTimeout",
+ "description": "The timeout for receiving messages (in milliseconds).",
+ "defaultValue": "1000L",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.recoveryInterval": {
+ "name": "camel.sink.endpoint.recoveryInterval",
+ "description": "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.",
+ "defaultValue": "5000L",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.requestTimeoutCheckerInterval": {
+ "name": "camel.sink.endpoint.requestTimeoutCheckerInterval",
+ "description": "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.",
+ "defaultValue": "1000L",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.synchronous": {
+ "name": "camel.sink.endpoint.synchronous",
+ "description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.transferException": {
+ "name": "camel.sink.endpoint.transferException",
+ "description": "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 takes precedence. The caught [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.transferExchange": {
+ "name": "camel.sink.endpoint.transferExchange",
+ "description": "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 payloads is an Exchange and not [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.useMessageIDAsCorrelationID": {
+ "name": "camel.sink.endpoint.useMessageIDAsCorrelationID",
+ "description": "Specifies whether JMSMessageID should always be used as JMSCorrelationID for InOut messages.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.waitForProvisionCorrelationToBeUpdatedCounter": {
+ "name": "camel.sink.endpoint.waitForProvisionCorrelationToBeUpdatedCounter",
+ "description": "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.",
+ "defaultValue": "50",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.waitForProvisionCorrelationToBeUpdatedThreadSleepingTime": {
+ "name": "camel.sink.endpoint.waitForProvisionCorrelationToBeUpdatedThreadSleepingTime",
+ "description": "Interval in millis to sleep each time while waiting for provisional correlation id to be updated.",
+ "defaultValue": "100L",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.password": {
+ "name": "camel.sink.endpoint.password",
+ "description": "Password to use with the ConnectionFactory. You can also configure username\/password directly on the ConnectionFactory.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.username": {
+ "name": "camel.sink.endpoint.username",
+ "description": "Username to use with the ConnectionFactory. You can also configure username\/password directly on the ConnectionFactory.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.transacted": {
+ "name": "camel.sink.endpoint.transacted",
+ "description": "Specifies whether to use transacted mode",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.transactedInOut": {
+ "name": "camel.sink.endpoint.transactedInOut",
+ "description": "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 container makes its ow [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.lazyCreateTransactionManager": {
+ "name": "camel.sink.endpoint.lazyCreateTransactionManager",
+ "description": "If true, Camel will create a JmsTransactionManager, if there is no transactionManager injected when option transacted=true.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.transactionManager": {
+ "name": "camel.sink.endpoint.transactionManager",
+ "description": "The Spring transaction manager to use.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.transactionName": {
+ "name": "camel.sink.endpoint.transactionName",
+ "description": "The name of the transaction to use.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.transactionTimeout": {
+ "name": "camel.sink.endpoint.transactionTimeout",
+ "description": "The timeout value of the transaction (in seconds), if using transacted mode.",
+ "defaultValue": "-1",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.clientId": {
+ "name": "camel.component.amqp.clientId",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.connectionFactory": {
+ "name": "camel.component.amqp.connectionFactory",
+ "description": "The connection factory to be use. A connection factory must be configured either on the component or endpoint.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.disableReplyTo": {
+ "name": "camel.component.amqp.disableReplyTo",
+ "description": "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 message brokers and you w [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.durableSubscriptionName": {
+ "name": "camel.component.amqp.durableSubscriptionName",
+ "description": "The durable subscriber name for specifying durable topic subscriptions. The clientId option must be configured as well.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.includeAmqpAnnotations": {
+ "name": "camel.component.amqp.includeAmqpAnnotations",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.jmsMessageType": {
+ "name": "camel.component.amqp.jmsMessageType",
+ "description": "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]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.testConnectionOnStartup": {
+ "name": "camel.component.amqp.testConnectionOnStartup",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.deliveryDelay": {
+ "name": "camel.component.amqp.deliveryDelay",
+ "description": "Sets delivery delay to use for send calls for JMS. This option requires JMS 2.0 compliant broker.",
+ "defaultValue": "-1L",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.deliveryMode": {
+ "name": "camel.component.amqp.deliveryMode",
+ "description": "Specifies the delivery mode to be used. Possibles values are those defined by javax.jms.DeliveryMode. NON_PERSISTENT = 1 and PERSISTENT = 2. One of: [1] [2]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.deliveryPersistent": {
+ "name": "camel.component.amqp.deliveryPersistent",
+ "description": "Specifies whether persistent delivery is used by default.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.explicitQosEnabled": {
+ "name": "camel.component.amqp.explicitQosEnabled",
+ "description": "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.",
+ "defaultValue": "\"false\"",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.formatDateHeadersToIso8601": {
+ "name": "camel.component.amqp.formatDateHeadersToIso8601",
+ "description": "Sets whether JMS date properties should be formatted according to the ISO 8601 standard.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.lazyStartProducer": {
+ "name": "camel.component.amqp.lazyStartProducer",
+ "description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be 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 creating and starting the pr [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.preserveMessageQos": {
+ "name": "camel.component.amqp.preserveMessageQos",
+ "description": "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 explicitQosEnabled option, by cont [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.priority": {
+ "name": "camel.component.amqp.priority",
+ "description": "Values greater than 1 specify the message priority when sending (where 0 is the lowest priority and 9 is the highest). The explicitQosEnabled option must also be enabled in order for this option to have any effect. One of: [1] [2] [3] [4] [5] [6] [7] [8] [9]",
+ "defaultValue": "4",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.replyToConcurrentConsumers": {
+ "name": "camel.component.amqp.replyToConcurrentConsumers",
+ "description": "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.",
+ "defaultValue": "1",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.replyToMaxConcurrentConsumers": {
+ "name": "camel.component.amqp.replyToMaxConcurrentConsumers",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.replyToOnTimeoutMaxConcurrentConsumers": {
+ "name": "camel.component.amqp.replyToOnTimeoutMaxConcurrentConsumers",
+ "description": "Specifies the maximum number of concurrent consumers for continue routing when timeout occurred when using request\/reply over JMS.",
+ "defaultValue": "1",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.replyToOverride": {
+ "name": "camel.component.amqp.replyToOverride",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.replyToType": {
+ "name": "camel.component.amqp.replyToType",
+ "description": "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 running in a clus [...]
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.requestTimeout": {
+ "name": "camel.component.amqp.requestTimeout",
+ "description": "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.",
+ "defaultValue": "20000L",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.timeToLive": {
+ "name": "camel.component.amqp.timeToLive",
+ "description": "When sending messages, specifies the time-to-live of the message (in milliseconds).",
+ "defaultValue": "-1L",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.allowAdditionalHeaders": {
+ "name": "camel.component.amqp.allowAdditionalHeaders",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.allowNullBody": {
+ "name": "camel.component.amqp.allowNullBody",
+ "description": "Whether to allow sending messages with no body. If this option is false and the message body is null, then an JMSException is thrown.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.alwaysCopyMessage": {
+ "name": "camel.component.amqp.alwaysCopyMessage",
+ "description": "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)",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.correlationProperty": {
+ "name": "camel.component.amqp.correlationProperty",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.disableTimeToLive": {
+ "name": "camel.component.amqp.disableTimeToLive",
+ "description": "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 message will not expire [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.forceSendOriginalMessage": {
+ "name": "camel.component.amqp.forceSendOriginalMessage",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.includeSentJMSMessageID": {
+ "name": "camel.component.amqp.includeSentJMSMessageID",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.replyToCacheLevelName": {
+ "name": "camel.component.amqp.replyToCacheLevelName",
+ "description": "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 then CACHE_NONE is not allow [...]
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.replyToDestinationSelectorName": {
+ "name": "camel.component.amqp.replyToDestinationSelectorName",
+ "description": "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).",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.streamMessageTypeEnabled": {
+ "name": "camel.component.amqp.streamMessageTypeEnabled",
+ "description": "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 until no more data.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.allowAutoWiredConnectionFactory": {
+ "name": "camel.component.amqp.allowAutoWiredConnectionFactory",
+ "description": "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.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.allowAutoWiredDestinationResolver": {
+ "name": "camel.component.amqp.allowAutoWiredDestinationResolver",
+ "description": "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.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.allowSerializedHeaders": {
+ "name": "camel.component.amqp.allowSerializedHeaders",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.artemisStreamingEnabled": {
+ "name": "camel.component.amqp.artemisStreamingEnabled",
+ "description": "Whether optimizing for Apache Artemis streaming mode.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.asyncStartListener": {
+ "name": "camel.component.amqp.asyncStartListener",
+ "description": "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 used, then beware that if [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.asyncStopListener": {
+ "name": "camel.component.amqp.asyncStopListener",
+ "description": "Whether to stop the JmsConsumer message listener asynchronously, when stopping a route.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.basicPropertyBinding": {
+ "name": "camel.component.amqp.basicPropertyBinding",
+ "description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.configuration": {
+ "name": "camel.component.amqp.configuration",
+ "description": "To use a shared JMS configuration",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.destinationResolver": {
+ "name": "camel.component.amqp.destinationResolver",
+ "description": "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).",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.errorHandler": {
+ "name": "camel.component.amqp.errorHandler",
+ "description": "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 errorHandler.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.exceptionListener": {
+ "name": "camel.component.amqp.exceptionListener",
+ "description": "Specifies the JMS Exception Listener that is to be notified of any underlying JMS exceptions.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.idleConsumerLimit": {
+ "name": "camel.component.amqp.idleConsumerLimit",
+ "description": "Specify the limit for the number of consumers that are allowed to be idle at any given time.",
+ "defaultValue": "1",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.idleTaskExecutionLimit": {
+ "name": "camel.component.amqp.idleTaskExecutionLimit",
+ "description": "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.",
+ "defaultValue": "1",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.includeAllJMSXProperties": {
+ "name": "camel.component.amqp.includeAllJMSXProperties",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.jmsKeyFormatStrategy": {
+ "name": "camel.component.amqp.jmsKeyFormatStrategy",
+ "description": "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 org.apache.camel.component.jm [...]
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.mapJmsMessage": {
+ "name": "camel.component.amqp.mapJmsMessage",
+ "description": "Specifies whether Camel should auto map the received JMS message to a suited payload type, such as javax.jms.TextMessage to a String etc.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.maxMessagesPerTask": {
+ "name": "camel.component.amqp.maxMessagesPerTask",
+ "description": "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.",
+ "defaultValue": "-1",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.messageConverter": {
+ "name": "camel.component.amqp.messageConverter",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.messageCreatedStrategy": {
+ "name": "camel.component.amqp.messageCreatedStrategy",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.messageIdEnabled": {
+ "name": "camel.component.amqp.messageIdEnabled",
+ "description": "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.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.messageListenerContainerFactory": {
+ "name": "camel.component.amqp.messageListenerContainerFactory",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.messageTimestampEnabled": {
+ "name": "camel.component.amqp.messageTimestampEnabled",
+ "description": "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.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.pubSubNoLocal": {
+ "name": "camel.component.amqp.pubSubNoLocal",
+ "description": "Specifies whether to inhibit the delivery of messages published by its own connection.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.queueBrowseStrategy": {
+ "name": "camel.component.amqp.queueBrowseStrategy",
+ "description": "To use a custom QueueBrowseStrategy when browsing queues",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.receiveTimeout": {
+ "name": "camel.component.amqp.receiveTimeout",
+ "description": "The timeout for receiving messages (in milliseconds).",
+ "defaultValue": "1000L",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.recoveryInterval": {
+ "name": "camel.component.amqp.recoveryInterval",
+ "description": "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.",
+ "defaultValue": "5000L",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.requestTimeoutCheckerInterval": {
+ "name": "camel.component.amqp.requestTimeoutCheckerInterval",
+ "description": "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.",
+ "defaultValue": "1000L",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.transferException": {
+ "name": "camel.component.amqp.transferException",
+ "description": "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 takes precedence. The caught [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.transferExchange": {
+ "name": "camel.component.amqp.transferExchange",
+ "description": "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 payloads is an Exchange and not [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.useMessageIDAsCorrelationID": {
+ "name": "camel.component.amqp.useMessageIDAsCorrelationID",
+ "description": "Specifies whether JMSMessageID should always be used as JMSCorrelationID for InOut messages.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.waitForProvisionCorrelationToBeUpdatedCounter": {
+ "name": "camel.component.amqp.waitForProvisionCorrelationToBeUpdatedCounter",
+ "description": "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.",
+ "defaultValue": "50",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.waitForProvisionCorrelationToBeUpdatedThreadSleepingTime": {
+ "name": "camel.component.amqp.waitForProvisionCorrelationToBeUpdatedThreadSleepingTime",
+ "description": "Interval in millis to sleep each time while waiting for provisional correlation id to be updated.",
+ "defaultValue": "100L",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.headerFilterStrategy": {
+ "name": "camel.component.amqp.headerFilterStrategy",
+ "description": "To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.password": {
+ "name": "camel.component.amqp.password",
+ "description": "Password to use with the ConnectionFactory. You can also configure username\/password directly on the ConnectionFactory.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.username": {
+ "name": "camel.component.amqp.username",
+ "description": "Username to use with the ConnectionFactory. You can also configure username\/password directly on the ConnectionFactory.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.transacted": {
+ "name": "camel.component.amqp.transacted",
+ "description": "Specifies whether to use transacted mode",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.transactedInOut": {
+ "name": "camel.component.amqp.transactedInOut",
+ "description": "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 container makes its ow [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.lazyCreateTransactionManager": {
+ "name": "camel.component.amqp.lazyCreateTransactionManager",
+ "description": "If true, Camel will create a JmsTransactionManager, if there is no transactionManager injected when option transacted=true.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.transactionManager": {
+ "name": "camel.component.amqp.transactionManager",
+ "description": "The Spring transaction manager to use.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.transactionName": {
+ "name": "camel.component.amqp.transactionName",
+ "description": "The name of the transaction to use.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.transactionTimeout": {
+ "name": "camel.component.amqp.transactionTimeout",
+ "description": "The timeout value of the transaction (in seconds), if using transacted mode.",
+ "defaultValue": "-1",
+ "priority": "MEDIUM"
+ }
+ }
+}
diff --git a/connectors/camel-amqp-kafka-connector/src/generated/resources/camel-amqp-kafka-source-connector.json b/connectors/camel-amqp-kafka-connector/src/generated/resources/camel-amqp-kafka-source-connector.json
new file mode 100644
index 0000000..4987b9f
--- /dev/null
+++ b/connectors/camel-amqp-kafka-connector/src/generated/resources/camel-amqp-kafka-source-connector.json
@@ -0,0 +1,875 @@
+{
+ "connector": {
+ "class": "org.apache.camel.kafkaconnector.amqp.CamelAmqpSourceConnector",
+ "artifactId": "camel-amqp",
+ "groupId": "org.apache.camel",
+ "title": "camel-amqp",
+ "version": "0.6.0-SNAPSHOT"
+ },
+ "properties": {
+ "camel.source.path.destinationType": {
+ "name": "camel.source.path.destinationType",
+ "description": "The kind of destination to use One of: [queue] [topic] [temp-queue] [temp-topic]",
+ "defaultValue": "\"queue\"",
+ "priority": "MEDIUM"
+ },
+ "camel.source.path.destinationName": {
+ "name": "camel.source.path.destinationName",
+ "description": "Name of the queue or topic to use as destination",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.source.endpoint.clientId": {
+ "name": "camel.source.endpoint.clientId",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.connectionFactory": {
+ "name": "camel.source.endpoint.connectionFactory",
+ "description": "The connection factory to be use. A connection factory must be configured either on the component or endpoint.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.disableReplyTo": {
+ "name": "camel.source.endpoint.disableReplyTo",
+ "description": "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 message brokers and you w [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.durableSubscriptionName": {
+ "name": "camel.source.endpoint.durableSubscriptionName",
+ "description": "The durable subscriber name for specifying durable topic subscriptions. The clientId option must be configured as well.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.jmsMessageType": {
+ "name": "camel.source.endpoint.jmsMessageType",
+ "description": "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]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.testConnectionOnStartup": {
+ "name": "camel.source.endpoint.testConnectionOnStartup",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.acknowledgementModeName": {
+ "name": "camel.source.endpoint.acknowledgementModeName",
+ "description": "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]",
+ "defaultValue": "\"AUTO_ACKNOWLEDGE\"",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.asyncConsumer": {
+ "name": "camel.source.endpoint.asyncConsumer",
+ "description": "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 if transacted has been [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.autoStartup": {
+ "name": "camel.source.endpoint.autoStartup",
+ "description": "Specifies whether the consumer container should auto-startup.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.cacheLevel": {
+ "name": "camel.source.endpoint.cacheLevel",
+ "description": "Sets the cache level by ID for the underlying JMS resources. See cacheLevelName option for more details.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.cacheLevelName": {
+ "name": "camel.source.endpoint.cacheLevelName",
+ "description": "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]",
+ "defaultValue": "\"CACHE_AUTO\"",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.concurrentConsumers": {
+ "name": "camel.source.endpoint.concurrentConsumers",
+ "description": "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.",
+ "defaultValue": "1",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.maxConcurrentConsumers": {
+ "name": "camel.source.endpoint.maxConcurrentConsumers",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.replyTo": {
+ "name": "camel.source.endpoint.replyTo",
+ "description": "Provides an explicit ReplyTo destination, which overrides any incoming value of Message.getJMSReplyTo().",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.replyToDeliveryPersistent": {
+ "name": "camel.source.endpoint.replyToDeliveryPersistent",
+ "description": "Specifies whether to use persistent delivery by default for replies.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.selector": {
+ "name": "camel.source.endpoint.selector",
+ "description": "Sets the JMS selector to use",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.subscriptionDurable": {
+ "name": "camel.source.endpoint.subscriptionDurable",
+ "description": "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 pubSubDomain flag as well.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.subscriptionName": {
+ "name": "camel.source.endpoint.subscriptionName",
+ "description": "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.0).",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.subscriptionShared": {
+ "name": "camel.source.endpoint.subscriptionShared",
+ "description": "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 with subscriptionDurable as we [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.acceptMessagesWhileStopping": {
+ "name": "camel.source.endpoint.acceptMessagesWhileStopping",
+ "description": "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 queue on the JMS broker. To avoid thi [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.allowReplyManagerQuickStop": {
+ "name": "camel.source.endpoint.allowReplyManagerQuickStop",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.consumerType": {
+ "name": "camel.source.endpoint.consumerType",
+ "description": "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.springframework.jms.listener.Ab [...]
+ "defaultValue": "\"Default\"",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.defaultTaskExecutorType": {
+ "name": "camel.source.endpoint.defaultTaskExecutorType",
+ "description": "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 SimpleAsync for reply consumers [...]
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.eagerLoadingOfProperties": {
+ "name": "camel.source.endpoint.eagerLoadingOfProperties",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.eagerPoisonBody": {
+ "name": "camel.source.endpoint.eagerPoisonBody",
+ "description": "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.",
+ "defaultValue": "\"Poison JMS message due to ${exception.message}\"",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.exceptionHandler": {
+ "name": "camel.source.endpoint.exceptionHandler",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.exchangePattern": {
+ "name": "camel.source.endpoint.exchangePattern",
+ "description": "Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.exposeListenerSession": {
+ "name": "camel.source.endpoint.exposeListenerSession",
+ "description": "Specifies whether the listener session should be exposed when consuming messages.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.replyToSameDestinationAllowed": {
+ "name": "camel.source.endpoint.replyToSameDestinationAllowed",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.taskExecutor": {
+ "name": "camel.source.endpoint.taskExecutor",
+ "description": "Allows you to specify a custom task executor for consuming messages.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.allowSerializedHeaders": {
+ "name": "camel.source.endpoint.allowSerializedHeaders",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.artemisStreamingEnabled": {
+ "name": "camel.source.endpoint.artemisStreamingEnabled",
+ "description": "Whether optimizing for Apache Artemis streaming mode.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.asyncStartListener": {
+ "name": "camel.source.endpoint.asyncStartListener",
+ "description": "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 used, then beware that if [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.asyncStopListener": {
+ "name": "camel.source.endpoint.asyncStopListener",
+ "description": "Whether to stop the JmsConsumer message listener asynchronously, when stopping a route.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.basicPropertyBinding": {
+ "name": "camel.source.endpoint.basicPropertyBinding",
+ "description": "Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.destinationResolver": {
+ "name": "camel.source.endpoint.destinationResolver",
+ "description": "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).",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.errorHandler": {
+ "name": "camel.source.endpoint.errorHandler",
+ "description": "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 errorHandler.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.exceptionListener": {
+ "name": "camel.source.endpoint.exceptionListener",
+ "description": "Specifies the JMS Exception Listener that is to be notified of any underlying JMS exceptions.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.headerFilterStrategy": {
+ "name": "camel.source.endpoint.headerFilterStrategy",
+ "description": "To use a custom HeaderFilterStrategy to filter header to and from Camel message.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.idleConsumerLimit": {
+ "name": "camel.source.endpoint.idleConsumerLimit",
+ "description": "Specify the limit for the number of consumers that are allowed to be idle at any given time.",
+ "defaultValue": "1",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.idleTaskExecutionLimit": {
+ "name": "camel.source.endpoint.idleTaskExecutionLimit",
+ "description": "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.",
+ "defaultValue": "1",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.includeAllJMSXProperties": {
+ "name": "camel.source.endpoint.includeAllJMSXProperties",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.jmsKeyFormatStrategy": {
+ "name": "camel.source.endpoint.jmsKeyFormatStrategy",
+ "description": "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 org.apache.camel.component.jm [...]
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.mapJmsMessage": {
+ "name": "camel.source.endpoint.mapJmsMessage",
+ "description": "Specifies whether Camel should auto map the received JMS message to a suited payload type, such as javax.jms.TextMessage to a String etc.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.maxMessagesPerTask": {
+ "name": "camel.source.endpoint.maxMessagesPerTask",
+ "description": "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.",
+ "defaultValue": "-1",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.messageConverter": {
+ "name": "camel.source.endpoint.messageConverter",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.messageCreatedStrategy": {
+ "name": "camel.source.endpoint.messageCreatedStrategy",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.messageIdEnabled": {
+ "name": "camel.source.endpoint.messageIdEnabled",
+ "description": "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.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.messageListenerContainerFactory": {
+ "name": "camel.source.endpoint.messageListenerContainerFactory",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.messageTimestampEnabled": {
+ "name": "camel.source.endpoint.messageTimestampEnabled",
+ "description": "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.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.pubSubNoLocal": {
+ "name": "camel.source.endpoint.pubSubNoLocal",
+ "description": "Specifies whether to inhibit the delivery of messages published by its own connection.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.receiveTimeout": {
+ "name": "camel.source.endpoint.receiveTimeout",
+ "description": "The timeout for receiving messages (in milliseconds).",
+ "defaultValue": "1000L",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.recoveryInterval": {
+ "name": "camel.source.endpoint.recoveryInterval",
+ "description": "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.",
+ "defaultValue": "5000L",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.requestTimeoutCheckerInterval": {
+ "name": "camel.source.endpoint.requestTimeoutCheckerInterval",
+ "description": "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.",
+ "defaultValue": "1000L",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.synchronous": {
+ "name": "camel.source.endpoint.synchronous",
+ "description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.transferException": {
+ "name": "camel.source.endpoint.transferException",
+ "description": "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 takes precedence. The caught [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.transferExchange": {
+ "name": "camel.source.endpoint.transferExchange",
+ "description": "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 payloads is an Exchange and not [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.useMessageIDAsCorrelationID": {
+ "name": "camel.source.endpoint.useMessageIDAsCorrelationID",
+ "description": "Specifies whether JMSMessageID should always be used as JMSCorrelationID for InOut messages.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.waitForProvisionCorrelationToBeUpdatedCounter": {
+ "name": "camel.source.endpoint.waitForProvisionCorrelationToBeUpdatedCounter",
+ "description": "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.",
+ "defaultValue": "50",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.waitForProvisionCorrelationToBeUpdatedThreadSleepingTime": {
+ "name": "camel.source.endpoint.waitForProvisionCorrelationToBeUpdatedThreadSleepingTime",
+ "description": "Interval in millis to sleep each time while waiting for provisional correlation id to be updated.",
+ "defaultValue": "100L",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.errorHandlerLoggingLevel": {
+ "name": "camel.source.endpoint.errorHandlerLoggingLevel",
+ "description": "Allows to configure the default errorHandler logging level for logging uncaught exceptions. One of: [TRACE] [DEBUG] [INFO] [WARN] [ERROR] [OFF]",
+ "defaultValue": "\"WARN\"",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.errorHandlerLogStackTrace": {
+ "name": "camel.source.endpoint.errorHandlerLogStackTrace",
+ "description": "Allows to control whether stacktraces should be logged or not, by the default errorHandler.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.password": {
+ "name": "camel.source.endpoint.password",
+ "description": "Password to use with the ConnectionFactory. You can also configure username\/password directly on the ConnectionFactory.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.username": {
+ "name": "camel.source.endpoint.username",
+ "description": "Username to use with the ConnectionFactory. You can also configure username\/password directly on the ConnectionFactory.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.transacted": {
+ "name": "camel.source.endpoint.transacted",
+ "description": "Specifies whether to use transacted mode",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.transactedInOut": {
+ "name": "camel.source.endpoint.transactedInOut",
+ "description": "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 container makes its ow [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.lazyCreateTransactionManager": {
+ "name": "camel.source.endpoint.lazyCreateTransactionManager",
+ "description": "If true, Camel will create a JmsTransactionManager, if there is no transactionManager injected when option transacted=true.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.transactionManager": {
+ "name": "camel.source.endpoint.transactionManager",
+ "description": "The Spring transaction manager to use.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.transactionName": {
+ "name": "camel.source.endpoint.transactionName",
+ "description": "The name of the transaction to use.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.transactionTimeout": {
+ "name": "camel.source.endpoint.transactionTimeout",
+ "description": "The timeout value of the transaction (in seconds), if using transacted mode.",
+ "defaultValue": "-1",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.clientId": {
+ "name": "camel.component.amqp.clientId",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.connectionFactory": {
+ "name": "camel.component.amqp.connectionFactory",
+ "description": "The connection factory to be use. A connection factory must be configured either on the component or endpoint.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.disableReplyTo": {
+ "name": "camel.component.amqp.disableReplyTo",
+ "description": "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 message brokers and you w [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.durableSubscriptionName": {
+ "name": "camel.component.amqp.durableSubscriptionName",
+ "description": "The durable subscriber name for specifying durable topic subscriptions. The clientId option must be configured as well.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.includeAmqpAnnotations": {
+ "name": "camel.component.amqp.includeAmqpAnnotations",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.jmsMessageType": {
+ "name": "camel.component.amqp.jmsMessageType",
+ "description": "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]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.testConnectionOnStartup": {
+ "name": "camel.component.amqp.testConnectionOnStartup",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.acknowledgementModeName": {
+ "name": "camel.component.amqp.acknowledgementModeName",
+ "description": "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]",
+ "defaultValue": "\"AUTO_ACKNOWLEDGE\"",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.asyncConsumer": {
+ "name": "camel.component.amqp.asyncConsumer",
+ "description": "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 if transacted has been [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.autoStartup": {
+ "name": "camel.component.amqp.autoStartup",
+ "description": "Specifies whether the consumer container should auto-startup.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.cacheLevel": {
+ "name": "camel.component.amqp.cacheLevel",
+ "description": "Sets the cache level by ID for the underlying JMS resources. See cacheLevelName option for more details.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.cacheLevelName": {
+ "name": "camel.component.amqp.cacheLevelName",
+ "description": "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]",
+ "defaultValue": "\"CACHE_AUTO\"",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.concurrentConsumers": {
+ "name": "camel.component.amqp.concurrentConsumers",
+ "description": "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.",
+ "defaultValue": "1",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.maxConcurrentConsumers": {
+ "name": "camel.component.amqp.maxConcurrentConsumers",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.replyTo": {
+ "name": "camel.component.amqp.replyTo",
+ "description": "Provides an explicit ReplyTo destination, which overrides any incoming value of Message.getJMSReplyTo().",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.replyToDeliveryPersistent": {
+ "name": "camel.component.amqp.replyToDeliveryPersistent",
+ "description": "Specifies whether to use persistent delivery by default for replies.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.selector": {
+ "name": "camel.component.amqp.selector",
+ "description": "Sets the JMS selector to use",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.subscriptionDurable": {
+ "name": "camel.component.amqp.subscriptionDurable",
+ "description": "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 pubSubDomain flag as well.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.subscriptionName": {
+ "name": "camel.component.amqp.subscriptionName",
+ "description": "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.0).",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.subscriptionShared": {
+ "name": "camel.component.amqp.subscriptionShared",
+ "description": "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 with subscriptionDurable as we [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.acceptMessagesWhileStopping": {
+ "name": "camel.component.amqp.acceptMessagesWhileStopping",
+ "description": "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 queue on the JMS broker. To avoid thi [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.allowReplyManagerQuickStop": {
+ "name": "camel.component.amqp.allowReplyManagerQuickStop",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.consumerType": {
+ "name": "camel.component.amqp.consumerType",
+ "description": "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.springframework.jms.listener.Ab [...]
+ "defaultValue": "\"Default\"",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.defaultTaskExecutorType": {
+ "name": "camel.component.amqp.defaultTaskExecutorType",
+ "description": "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 SimpleAsync for reply consumers [...]
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.eagerLoadingOfProperties": {
+ "name": "camel.component.amqp.eagerLoadingOfProperties",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.eagerPoisonBody": {
+ "name": "camel.component.amqp.eagerPoisonBody",
+ "description": "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.",
+ "defaultValue": "\"Poison JMS message due to ${exception.message}\"",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.exposeListenerSession": {
+ "name": "camel.component.amqp.exposeListenerSession",
+ "description": "Specifies whether the listener session should be exposed when consuming messages.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.replyToSameDestinationAllowed": {
+ "name": "camel.component.amqp.replyToSameDestinationAllowed",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.taskExecutor": {
+ "name": "camel.component.amqp.taskExecutor",
+ "description": "Allows you to specify a custom task executor for consuming messages.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.allowAutoWiredConnectionFactory": {
+ "name": "camel.component.amqp.allowAutoWiredConnectionFactory",
+ "description": "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.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.allowAutoWiredDestinationResolver": {
+ "name": "camel.component.amqp.allowAutoWiredDestinationResolver",
+ "description": "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.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.allowSerializedHeaders": {
+ "name": "camel.component.amqp.allowSerializedHeaders",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.artemisStreamingEnabled": {
+ "name": "camel.component.amqp.artemisStreamingEnabled",
+ "description": "Whether optimizing for Apache Artemis streaming mode.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.asyncStartListener": {
+ "name": "camel.component.amqp.asyncStartListener",
+ "description": "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 used, then beware that if [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.asyncStopListener": {
+ "name": "camel.component.amqp.asyncStopListener",
+ "description": "Whether to stop the JmsConsumer message listener asynchronously, when stopping a route.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.basicPropertyBinding": {
+ "name": "camel.component.amqp.basicPropertyBinding",
+ "description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.configuration": {
+ "name": "camel.component.amqp.configuration",
+ "description": "To use a shared JMS configuration",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.destinationResolver": {
+ "name": "camel.component.amqp.destinationResolver",
+ "description": "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).",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.errorHandler": {
+ "name": "camel.component.amqp.errorHandler",
+ "description": "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 errorHandler.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.exceptionListener": {
+ "name": "camel.component.amqp.exceptionListener",
+ "description": "Specifies the JMS Exception Listener that is to be notified of any underlying JMS exceptions.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.idleConsumerLimit": {
+ "name": "camel.component.amqp.idleConsumerLimit",
+ "description": "Specify the limit for the number of consumers that are allowed to be idle at any given time.",
+ "defaultValue": "1",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.idleTaskExecutionLimit": {
+ "name": "camel.component.amqp.idleTaskExecutionLimit",
+ "description": "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.",
+ "defaultValue": "1",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.includeAllJMSXProperties": {
+ "name": "camel.component.amqp.includeAllJMSXProperties",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.jmsKeyFormatStrategy": {
+ "name": "camel.component.amqp.jmsKeyFormatStrategy",
+ "description": "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 org.apache.camel.component.jm [...]
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.mapJmsMessage": {
+ "name": "camel.component.amqp.mapJmsMessage",
+ "description": "Specifies whether Camel should auto map the received JMS message to a suited payload type, such as javax.jms.TextMessage to a String etc.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.maxMessagesPerTask": {
+ "name": "camel.component.amqp.maxMessagesPerTask",
+ "description": "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.",
+ "defaultValue": "-1",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.messageConverter": {
+ "name": "camel.component.amqp.messageConverter",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.messageCreatedStrategy": {
+ "name": "camel.component.amqp.messageCreatedStrategy",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.messageIdEnabled": {
+ "name": "camel.component.amqp.messageIdEnabled",
+ "description": "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.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.messageListenerContainerFactory": {
+ "name": "camel.component.amqp.messageListenerContainerFactory",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.messageTimestampEnabled": {
+ "name": "camel.component.amqp.messageTimestampEnabled",
+ "description": "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.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.pubSubNoLocal": {
+ "name": "camel.component.amqp.pubSubNoLocal",
+ "description": "Specifies whether to inhibit the delivery of messages published by its own connection.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.queueBrowseStrategy": {
+ "name": "camel.component.amqp.queueBrowseStrategy",
+ "description": "To use a custom QueueBrowseStrategy when browsing queues",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.receiveTimeout": {
+ "name": "camel.component.amqp.receiveTimeout",
+ "description": "The timeout for receiving messages (in milliseconds).",
+ "defaultValue": "1000L",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.recoveryInterval": {
+ "name": "camel.component.amqp.recoveryInterval",
+ "description": "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.",
+ "defaultValue": "5000L",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.requestTimeoutCheckerInterval": {
+ "name": "camel.component.amqp.requestTimeoutCheckerInterval",
+ "description": "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.",
+ "defaultValue": "1000L",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.transferException": {
+ "name": "camel.component.amqp.transferException",
+ "description": "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 takes precedence. The caught [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.transferExchange": {
+ "name": "camel.component.amqp.transferExchange",
+ "description": "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 payloads is an Exchange and not [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.useMessageIDAsCorrelationID": {
+ "name": "camel.component.amqp.useMessageIDAsCorrelationID",
+ "description": "Specifies whether JMSMessageID should always be used as JMSCorrelationID for InOut messages.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.waitForProvisionCorrelationToBeUpdatedCounter": {
+ "name": "camel.component.amqp.waitForProvisionCorrelationToBeUpdatedCounter",
+ "description": "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.",
+ "defaultValue": "50",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.waitForProvisionCorrelationToBeUpdatedThreadSleepingTime": {
+ "name": "camel.component.amqp.waitForProvisionCorrelationToBeUpdatedThreadSleepingTime",
+ "description": "Interval in millis to sleep each time while waiting for provisional correlation id to be updated.",
+ "defaultValue": "100L",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.headerFilterStrategy": {
+ "name": "camel.component.amqp.headerFilterStrategy",
+ "description": "To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.errorHandlerLoggingLevel": {
+ "name": "camel.component.amqp.errorHandlerLoggingLevel",
+ "description": "Allows to configure the default errorHandler logging level for logging uncaught exceptions. One of: [TRACE] [DEBUG] [INFO] [WARN] [ERROR] [OFF]",
+ "defaultValue": "\"WARN\"",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.errorHandlerLogStackTrace": {
+ "name": "camel.component.amqp.errorHandlerLogStackTrace",
+ "description": "Allows to control whether stacktraces should be logged or not, by the default errorHandler.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.password": {
+ "name": "camel.component.amqp.password",
+ "description": "Password to use with the ConnectionFactory. You can also configure username\/password directly on the ConnectionFactory.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.username": {
+ "name": "camel.component.amqp.username",
+ "description": "Username to use with the ConnectionFactory. You can also configure username\/password directly on the ConnectionFactory.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.transacted": {
+ "name": "camel.component.amqp.transacted",
+ "description": "Specifies whether to use transacted mode",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.transactedInOut": {
+ "name": "camel.component.amqp.transactedInOut",
+ "description": "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 container makes its ow [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.lazyCreateTransactionManager": {
+ "name": "camel.component.amqp.lazyCreateTransactionManager",
+ "description": "If true, Camel will create a JmsTransactionManager, if there is no transactionManager injected when option transacted=true.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.transactionManager": {
+ "name": "camel.component.amqp.transactionManager",
+ "description": "The Spring transaction manager to use.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.transactionName": {
+ "name": "camel.component.amqp.transactionName",
+ "description": "The name of the transaction to use.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.amqp.transactionTimeout": {
+ "name": "camel.component.amqp.transactionTimeout",
+ "description": "The timeout value of the transaction (in seconds), if using transacted mode.",
+ "defaultValue": "-1",
+ "priority": "MEDIUM"
+ }
+ }
+}
diff --git a/connectors/camel-apns-kafka-connector/src/generated/resources/camel-apns-kafka-sink-connector.json b/connectors/camel-apns-kafka-connector/src/generated/resources/camel-apns-kafka-sink-connector.json
new file mode 100644
index 0000000..0c36070
--- /dev/null
+++ b/connectors/camel-apns-kafka-connector/src/generated/resources/camel-apns-kafka-sink-connector.json
@@ -0,0 +1,59 @@
+{
+ "connector": {
+ "class": "org.apache.camel.kafkaconnector.apns.CamelApnsSinkConnector",
+ "artifactId": "camel-apns",
+ "groupId": "org.apache.camel",
+ "title": "camel-apns",
+ "version": "0.6.0-SNAPSHOT"
+ },
+ "properties": {
+ "camel.sink.path.name": {
+ "name": "camel.sink.path.name",
+ "description": "Name of the endpoint",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.tokens": {
+ "name": "camel.sink.endpoint.tokens",
+ "description": "Configure this property in case you want to statically declare tokens related to devices you want to notify. Tokens are separated by comma.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.lazyStartProducer": {
+ "name": "camel.sink.endpoint.lazyStartProducer",
+ "description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be 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 creating and starting the pr [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.basicPropertyBinding": {
+ "name": "camel.sink.endpoint.basicPropertyBinding",
+ "description": "Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.synchronous": {
+ "name": "camel.sink.endpoint.synchronous",
+ "description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.apns.apnsService": {
+ "name": "camel.component.apns.apnsService",
+ "description": "The ApnsService to use. The org.apache.camel.component.apns.factory.ApnsServiceFactory can be used to build a ApnsService",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.component.apns.lazyStartProducer": {
+ "name": "camel.component.apns.lazyStartProducer",
+ "description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be 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 creating and starting the pr [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.apns.basicPropertyBinding": {
+ "name": "camel.component.apns.basicPropertyBinding",
+ "description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ }
+ }
+}
diff --git a/connectors/camel-apns-kafka-connector/src/generated/resources/camel-apns-kafka-source-connector.json b/connectors/camel-apns-kafka-connector/src/generated/resources/camel-apns-kafka-source-connector.json
new file mode 100644
index 0000000..5df9e2d
--- /dev/null
+++ b/connectors/camel-apns-kafka-connector/src/generated/resources/camel-apns-kafka-source-connector.json
@@ -0,0 +1,167 @@
+{
+ "connector": {
+ "class": "org.apache.camel.kafkaconnector.apns.CamelApnsSourceConnector",
+ "artifactId": "camel-apns",
+ "groupId": "org.apache.camel",
+ "title": "camel-apns",
+ "version": "0.6.0-SNAPSHOT"
+ },
+ "properties": {
+ "camel.source.path.name": {
+ "name": "camel.source.path.name",
+ "description": "Name of the endpoint",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.tokens": {
+ "name": "camel.source.endpoint.tokens",
+ "description": "Configure this property in case you want to statically declare tokens related to devices you want to notify. Tokens are separated by comma.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.bridgeErrorHandler": {
+ "name": "camel.source.endpoint.bridgeErrorHandler",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.sendEmptyMessageWhenIdle": {
+ "name": "camel.source.endpoint.sendEmptyMessageWhenIdle",
+ "description": "If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.exceptionHandler": {
+ "name": "camel.source.endpoint.exceptionHandler",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.exchangePattern": {
+ "name": "camel.source.endpoint.exchangePattern",
+ "description": "Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.pollStrategy": {
+ "name": "camel.source.endpoint.pollStrategy",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.basicPropertyBinding": {
+ "name": "camel.source.endpoint.basicPropertyBinding",
+ "description": "Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.synchronous": {
+ "name": "camel.source.endpoint.synchronous",
+ "description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.backoffErrorThreshold": {
+ "name": "camel.source.endpoint.backoffErrorThreshold",
+ "description": "The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.backoffIdleThreshold": {
+ "name": "camel.source.endpoint.backoffIdleThreshold",
+ "description": "The number of subsequent idle polls that should happen before the backoffMultipler should kick-in.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.backoffMultiplier": {
+ "name": "camel.source.endpoint.backoffMultiplier",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.delay": {
+ "name": "camel.source.endpoint.delay",
+ "description": "Milliseconds before the next poll.",
+ "defaultValue": "500L",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.greedy": {
+ "name": "camel.source.endpoint.greedy",
+ "description": "If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.initialDelay": {
+ "name": "camel.source.endpoint.initialDelay",
+ "description": "Milliseconds before the first poll starts.",
+ "defaultValue": "1000L",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.repeatCount": {
+ "name": "camel.source.endpoint.repeatCount",
+ "description": "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.",
+ "defaultValue": "0L",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.runLoggingLevel": {
+ "name": "camel.source.endpoint.runLoggingLevel",
+ "description": "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]",
+ "defaultValue": "\"TRACE\"",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.scheduledExecutorService": {
+ "name": "camel.source.endpoint.scheduledExecutorService",
+ "description": "Allows for configuring a custom\/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.scheduler": {
+ "name": "camel.source.endpoint.scheduler",
+ "description": "To use a cron scheduler from either camel-spring or camel-quartz component. Use value spring or quartz for built in scheduler",
+ "defaultValue": "\"none\"",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.schedulerProperties": {
+ "name": "camel.source.endpoint.schedulerProperties",
+ "description": "To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.startScheduler": {
+ "name": "camel.source.endpoint.startScheduler",
+ "description": "Whether the scheduler should be auto started.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.timeUnit": {
+ "name": "camel.source.endpoint.timeUnit",
+ "description": "Time unit for initialDelay and delay options. One of: [NANOSECONDS] [MICROSECONDS] [MILLISECONDS] [SECONDS] [MINUTES] [HOURS] [DAYS]",
+ "defaultValue": "\"MILLISECONDS\"",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.useFixedDelay": {
+ "name": "camel.source.endpoint.useFixedDelay",
+ "description": "Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.apns.apnsService": {
+ "name": "camel.component.apns.apnsService",
+ "description": "The ApnsService to use. The org.apache.camel.component.apns.factory.ApnsServiceFactory can be used to build a ApnsService",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.component.apns.bridgeErrorHandler": {
+ "name": "camel.component.apns.bridgeErrorHandler",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.apns.basicPropertyBinding": {
+ "name": "camel.component.apns.basicPropertyBinding",
+ "description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ }
+ }
+}
diff --git a/connectors/camel-arangodb-kafka-connector/src/generated/resources/camel-arangodb-kafka-sink-connector.json b/connectors/camel-arangodb-kafka-connector/src/generated/resources/camel-arangodb-kafka-sink-connector.json
new file mode 100644
index 0000000..7cfd1ec
--- /dev/null
+++ b/connectors/camel-arangodb-kafka-connector/src/generated/resources/camel-arangodb-kafka-sink-connector.json
@@ -0,0 +1,161 @@
+{
+ "connector": {
+ "class": "org.apache.camel.kafkaconnector.arangodb.CamelArangodbSinkConnector",
+ "artifactId": "camel-arangodb",
+ "groupId": "org.apache.camel",
+ "title": "camel-arangodb",
+ "version": "0.6.0-SNAPSHOT"
+ },
+ "properties": {
+ "camel.sink.path.database": {
+ "name": "camel.sink.path.database",
+ "description": "database name",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.sink.endpoint.documentCollection": {
+ "name": "camel.sink.endpoint.documentCollection",
+ "description": "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).",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.edgeCollection": {
+ "name": "camel.sink.endpoint.edgeCollection",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.graph": {
+ "name": "camel.sink.endpoint.graph",
+ "description": "Graph name, when using ArangoDb as a Graph Database. Combine this attribute with one of the two attributes vertexCollection and edgeCollection.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.host": {
+ "name": "camel.sink.endpoint.host",
+ "description": "ArangoDB host. If host and port are default, this field is Optional.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.lazyStartProducer": {
+ "name": "camel.sink.endpoint.lazyStartProducer",
+ "description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be 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 creating and starting the pr [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.operation": {
+ "name": "camel.sink.endpoint.operation",
+ "description": "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]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.port": {
+ "name": "camel.sink.endpoint.port",
+ "description": "ArangoDB exposed port. If host and port are default, this field is Optional.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.vertexCollection": {
+ "name": "camel.sink.endpoint.vertexCollection",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.basicPropertyBinding": {
+ "name": "camel.sink.endpoint.basicPropertyBinding",
+ "description": "Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.synchronous": {
+ "name": "camel.sink.endpoint.synchronous",
+ "description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.password": {
+ "name": "camel.sink.endpoint.password",
+ "description": "ArangoDB password. If user and password are default, this field is Optional.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.user": {
+ "name": "camel.sink.endpoint.user",
+ "description": "ArangoDB user. If user and password are default, this field is Optional.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.arangodb.configuration": {
+ "name": "camel.component.arangodb.configuration",
+ "description": "Component configuration",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.arangodb.documentCollection": {
+ "name": "camel.component.arangodb.documentCollection",
+ "description": "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).",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.arangodb.edgeCollection": {
+ "name": "camel.component.arangodb.edgeCollection",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.arangodb.graph": {
+ "name": "camel.component.arangodb.graph",
+ "description": "Graph name, when using ArangoDb as a Graph Database. Combine this attribute with one of the two attributes vertexCollection and edgeCollection.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.arangodb.host": {
+ "name": "camel.component.arangodb.host",
+ "description": "ArangoDB host. If host and port are default, this field is Optional.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.arangodb.lazyStartProducer": {
+ "name": "camel.component.arangodb.lazyStartProducer",
+ "description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be 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 creating and starting the pr [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.arangodb.operation": {
+ "name": "camel.component.arangodb.operation",
+ "description": "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]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.arangodb.port": {
+ "name": "camel.component.arangodb.port",
+ "description": "ArangoDB exposed port. If host and port are default, this field is Optional.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.arangodb.vertexCollection": {
+ "name": "camel.component.arangodb.vertexCollection",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.arangodb.basicPropertyBinding": {
+ "name": "camel.component.arangodb.basicPropertyBinding",
+ "description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.arangodb.password": {
+ "name": "camel.component.arangodb.password",
+ "description": "ArangoDB password. If user and password are default, this field is Optional.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.arangodb.user": {
+ "name": "camel.component.arangodb.user",
+ "description": "ArangoDB user. If user and password are default, this field is Optional.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ }
+ }
+}
diff --git a/connectors/camel-as2-kafka-connector/src/generated/resources/camel-as2-kafka-sink-connector.json b/connectors/camel-as2-kafka-connector/src/generated/resources/camel-as2-kafka-sink-connector.json
new file mode 100644
index 0000000..5429057
--- /dev/null
+++ b/connectors/camel-as2-kafka-connector/src/generated/resources/camel-as2-kafka-sink-connector.json
@@ -0,0 +1,221 @@
+{
+ "connector": {
+ "class": "org.apache.camel.kafkaconnector.as2.CamelAs2SinkConnector",
+ "artifactId": "camel-as2",
+ "groupId": "org.apache.camel",
+ "title": "camel-as2",
+ "version": "0.6.0-SNAPSHOT"
+ },
+ "properties": {
+ "camel.sink.path.apiName": {
+ "name": "camel.sink.path.apiName",
+ "description": "What kind of operation to perform One of: [CLIENT] [SERVER]",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.sink.path.methodName": {
+ "name": "camel.sink.path.methodName",
+ "description": "What sub operation to use for the selected operation",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.sink.endpoint.as2From": {
+ "name": "camel.sink.endpoint.as2From",
+ "description": "The value of the AS2From header of AS2 message.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.as2MessageStructure": {
+ "name": "camel.sink.endpoint.as2MessageStructure",
+ "description": "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]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.as2To": {
+ "name": "camel.sink.endpoint.as2To",
+ "description": "The value of the AS2To header of AS2 message.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.as2Version": {
+ "name": "camel.sink.endpoint.as2Version",
+ "description": "The version of the AS2 protocol. One of: [1.0] [1.1]",
+ "defaultValue": "\"1.1\"",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.clientFqdn": {
+ "name": "camel.sink.endpoint.clientFqdn",
+ "description": "The Client Fully Qualified Domain Name (FQDN). Used in message ids sent by endpoint.",
+ "defaultValue": "\"camel.apache.org\"",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.compressionAlgorithm": {
+ "name": "camel.sink.endpoint.compressionAlgorithm",
+ "description": "The algorithm used to compress EDI message. One of: [ZLIB]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.decryptingPrivateKey": {
+ "name": "camel.sink.endpoint.decryptingPrivateKey",
+ "description": "The key used to encrypt the EDI message.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.dispositionNotificationTo": {
+ "name": "camel.sink.endpoint.dispositionNotificationTo",
+ "description": "The value of the Disposition-Notification-To header. Assigning a value to this parameter requests a message disposition notification (MDN) for the AS2 message.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.ediMessageTransferEncoding": {
+ "name": "camel.sink.endpoint.ediMessageTransferEncoding",
+ "description": "The transfer encoding of EDI message.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.ediMessageType": {
+ "name": "camel.sink.endpoint.ediMessageType",
+ "description": "The content type of EDI message. One of application\/edifact, application\/edi-x12, application\/edi-consent",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.encryptingAlgorithm": {
+ "name": "camel.sink.endpoint.encryptingAlgorithm",
+ "description": "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]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.encryptingCertificateChain": {
+ "name": "camel.sink.endpoint.encryptingCertificateChain",
+ "description": "The chain of certificates used to encrypt EDI message.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.from": {
+ "name": "camel.sink.endpoint.from",
+ "description": "The value of the From header of AS2 message.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.inBody": {
+ "name": "camel.sink.endpoint.inBody",
+ "description": "Sets the name of a parameter to be passed in the exchange In Body",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.mdnMessageTemplate": {
+ "name": "camel.sink.endpoint.mdnMessageTemplate",
+ "description": "The template used to format MDN message",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.requestUri": {
+ "name": "camel.sink.endpoint.requestUri",
+ "description": "The request URI of EDI message.",
+ "defaultValue": "\"\/\"",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.server": {
+ "name": "camel.sink.endpoint.server",
+ "description": "The value included in the Server message header identifying the AS2 Server.",
+ "defaultValue": "\"Camel AS2 Server Endpoint\"",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.serverFqdn": {
+ "name": "camel.sink.endpoint.serverFqdn",
+ "description": "The Server Fully Qualified Domain Name (FQDN). Used in message ids sent by endpoint.",
+ "defaultValue": "\"camel.apache.org\"",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.serverPortNumber": {
+ "name": "camel.sink.endpoint.serverPortNumber",
+ "description": "The port number of server.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.signedReceiptMicAlgorithms": {
+ "name": "camel.sink.endpoint.signedReceiptMicAlgorithms",
+ "description": "The list of algorithms, in order of preference, requested to generate a message integrity check (MIC) returned in message dispostion notification (MDN)",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.signingAlgorithm": {
+ "name": "camel.sink.endpoint.signingAlgorithm",
+ "description": "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] [SHA3_256WITHECDSA] [S [...]
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.signingCertificateChain": {
+ "name": "camel.sink.endpoint.signingCertificateChain",
+ "description": "The chain of certificates used to sign EDI message.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.signingPrivateKey": {
+ "name": "camel.sink.endpoint.signingPrivateKey",
+ "description": "The key used to sign the EDI message.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.subject": {
+ "name": "camel.sink.endpoint.subject",
+ "description": "The value of Subject header of AS2 message.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.targetHostname": {
+ "name": "camel.sink.endpoint.targetHostname",
+ "description": "The host name (IP or DNS name) of target host.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.targetPortNumber": {
+ "name": "camel.sink.endpoint.targetPortNumber",
+ "description": "The port number of target host. -1 indicates the scheme default port.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.userAgent": {
+ "name": "camel.sink.endpoint.userAgent",
+ "description": "The value included in the User-Agent message header identifying the AS2 user agent.",
+ "defaultValue": "\"Camel AS2 Client Endpoint\"",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.lazyStartProducer": {
+ "name": "camel.sink.endpoint.lazyStartProducer",
+ "description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be 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 creating and starting the pr [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.basicPropertyBinding": {
+ "name": "camel.sink.endpoint.basicPropertyBinding",
+ "description": "Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.synchronous": {
+ "name": "camel.sink.endpoint.synchronous",
+ "description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.as2.lazyStartProducer": {
+ "name": "camel.component.as2.lazyStartProducer",
+ "description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be 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 creating and starting the pr [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.as2.basicPropertyBinding": {
+ "name": "camel.component.as2.basicPropertyBinding",
+ "description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.as2.configuration": {
+ "name": "camel.component.as2.configuration",
+ "description": "Component configuration",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ }
+ }
+}
diff --git a/connectors/camel-as2-kafka-connector/src/generated/resources/camel-as2-kafka-source-connector.json b/connectors/camel-as2-kafka-connector/src/generated/resources/camel-as2-kafka-source-connector.json
new file mode 100644
index 0000000..c0c2c03
--- /dev/null
+++ b/connectors/camel-as2-kafka-connector/src/generated/resources/camel-as2-kafka-source-connector.json
@@ -0,0 +1,329 @@
+{
+ "connector": {
+ "class": "org.apache.camel.kafkaconnector.as2.CamelAs2SourceConnector",
+ "artifactId": "camel-as2",
+ "groupId": "org.apache.camel",
+ "title": "camel-as2",
+ "version": "0.6.0-SNAPSHOT"
+ },
+ "properties": {
+ "camel.source.path.apiName": {
+ "name": "camel.source.path.apiName",
+ "description": "What kind of operation to perform One of: [CLIENT] [SERVER]",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.source.path.methodName": {
+ "name": "camel.source.path.methodName",
+ "description": "What sub operation to use for the selected operation",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.source.endpoint.as2From": {
+ "name": "camel.source.endpoint.as2From",
+ "description": "The value of the AS2From header of AS2 message.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.as2MessageStructure": {
+ "name": "camel.source.endpoint.as2MessageStructure",
+ "description": "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]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.as2To": {
+ "name": "camel.source.endpoint.as2To",
+ "description": "The value of the AS2To header of AS2 message.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.as2Version": {
+ "name": "camel.source.endpoint.as2Version",
+ "description": "The version of the AS2 protocol. One of: [1.0] [1.1]",
+ "defaultValue": "\"1.1\"",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.clientFqdn": {
+ "name": "camel.source.endpoint.clientFqdn",
+ "description": "The Client Fully Qualified Domain Name (FQDN). Used in message ids sent by endpoint.",
+ "defaultValue": "\"camel.apache.org\"",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.compressionAlgorithm": {
+ "name": "camel.source.endpoint.compressionAlgorithm",
+ "description": "The algorithm used to compress EDI message. One of: [ZLIB]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.decryptingPrivateKey": {
+ "name": "camel.source.endpoint.decryptingPrivateKey",
+ "description": "The key used to encrypt the EDI message.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.dispositionNotificationTo": {
+ "name": "camel.source.endpoint.dispositionNotificationTo",
+ "description": "The value of the Disposition-Notification-To header. Assigning a value to this parameter requests a message disposition notification (MDN) for the AS2 message.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.ediMessageTransferEncoding": {
+ "name": "camel.source.endpoint.ediMessageTransferEncoding",
+ "description": "The transfer encoding of EDI message.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.ediMessageType": {
+ "name": "camel.source.endpoint.ediMessageType",
+ "description": "The content type of EDI message. One of application\/edifact, application\/edi-x12, application\/edi-consent",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.encryptingAlgorithm": {
+ "name": "camel.source.endpoint.encryptingAlgorithm",
+ "description": "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]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.encryptingCertificateChain": {
+ "name": "camel.source.endpoint.encryptingCertificateChain",
+ "description": "The chain of certificates used to encrypt EDI message.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.from": {
+ "name": "camel.source.endpoint.from",
+ "description": "The value of the From header of AS2 message.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.inBody": {
+ "name": "camel.source.endpoint.inBody",
+ "description": "Sets the name of a parameter to be passed in the exchange In Body",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.mdnMessageTemplate": {
+ "name": "camel.source.endpoint.mdnMessageTemplate",
+ "description": "The template used to format MDN message",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.requestUri": {
+ "name": "camel.source.endpoint.requestUri",
+ "description": "The request URI of EDI message.",
+ "defaultValue": "\"\/\"",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.server": {
+ "name": "camel.source.endpoint.server",
+ "description": "The value included in the Server message header identifying the AS2 Server.",
+ "defaultValue": "\"Camel AS2 Server Endpoint\"",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.serverFqdn": {
+ "name": "camel.source.endpoint.serverFqdn",
+ "description": "The Server Fully Qualified Domain Name (FQDN). Used in message ids sent by endpoint.",
+ "defaultValue": "\"camel.apache.org\"",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.serverPortNumber": {
+ "name": "camel.source.endpoint.serverPortNumber",
+ "description": "The port number of server.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.signedReceiptMicAlgorithms": {
+ "name": "camel.source.endpoint.signedReceiptMicAlgorithms",
+ "description": "The list of algorithms, in order of preference, requested to generate a message integrity check (MIC) returned in message dispostion notification (MDN)",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.signingAlgorithm": {
+ "name": "camel.source.endpoint.signingAlgorithm",
+ "description": "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] [SHA3_256WITHECDSA] [S [...]
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.signingCertificateChain": {
+ "name": "camel.source.endpoint.signingCertificateChain",
+ "description": "The chain of certificates used to sign EDI message.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.signingPrivateKey": {
+ "name": "camel.source.endpoint.signingPrivateKey",
+ "description": "The key used to sign the EDI message.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.subject": {
+ "name": "camel.source.endpoint.subject",
+ "description": "The value of Subject header of AS2 message.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.targetHostname": {
+ "name": "camel.source.endpoint.targetHostname",
+ "description": "The host name (IP or DNS name) of target host.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.targetPortNumber": {
+ "name": "camel.source.endpoint.targetPortNumber",
+ "description": "The port number of target host. -1 indicates the scheme default port.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.userAgent": {
+ "name": "camel.source.endpoint.userAgent",
+ "description": "The value included in the User-Agent message header identifying the AS2 user agent.",
+ "defaultValue": "\"Camel AS2 Client Endpoint\"",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.bridgeErrorHandler": {
+ "name": "camel.source.endpoint.bridgeErrorHandler",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.sendEmptyMessageWhenIdle": {
+ "name": "camel.source.endpoint.sendEmptyMessageWhenIdle",
+ "description": "If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.exceptionHandler": {
+ "name": "camel.source.endpoint.exceptionHandler",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.exchangePattern": {
+ "name": "camel.source.endpoint.exchangePattern",
+ "description": "Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.pollStrategy": {
+ "name": "camel.source.endpoint.pollStrategy",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.basicPropertyBinding": {
+ "name": "camel.source.endpoint.basicPropertyBinding",
+ "description": "Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.synchronous": {
+ "name": "camel.source.endpoint.synchronous",
+ "description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.backoffErrorThreshold": {
+ "name": "camel.source.endpoint.backoffErrorThreshold",
+ "description": "The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.backoffIdleThreshold": {
+ "name": "camel.source.endpoint.backoffIdleThreshold",
+ "description": "The number of subsequent idle polls that should happen before the backoffMultipler should kick-in.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.backoffMultiplier": {
+ "name": "camel.source.endpoint.backoffMultiplier",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.delay": {
+ "name": "camel.source.endpoint.delay",
+ "description": "Milliseconds before the next poll.",
+ "defaultValue": "500L",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.greedy": {
+ "name": "camel.source.endpoint.greedy",
+ "description": "If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.initialDelay": {
+ "name": "camel.source.endpoint.initialDelay",
+ "description": "Milliseconds before the first poll starts.",
+ "defaultValue": "1000L",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.repeatCount": {
+ "name": "camel.source.endpoint.repeatCount",
+ "description": "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.",
+ "defaultValue": "0L",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.runLoggingLevel": {
+ "name": "camel.source.endpoint.runLoggingLevel",
+ "description": "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]",
+ "defaultValue": "\"TRACE\"",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.scheduledExecutorService": {
+ "name": "camel.source.endpoint.scheduledExecutorService",
+ "description": "Allows for configuring a custom\/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.scheduler": {
+ "name": "camel.source.endpoint.scheduler",
+ "description": "To use a cron scheduler from either camel-spring or camel-quartz component. Use value spring or quartz for built in scheduler",
+ "defaultValue": "\"none\"",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.schedulerProperties": {
+ "name": "camel.source.endpoint.schedulerProperties",
+ "description": "To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.startScheduler": {
+ "name": "camel.source.endpoint.startScheduler",
+ "description": "Whether the scheduler should be auto started.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.timeUnit": {
+ "name": "camel.source.endpoint.timeUnit",
+ "description": "Time unit for initialDelay and delay options. One of: [NANOSECONDS] [MICROSECONDS] [MILLISECONDS] [SECONDS] [MINUTES] [HOURS] [DAYS]",
+ "defaultValue": "\"MILLISECONDS\"",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.useFixedDelay": {
+ "name": "camel.source.endpoint.useFixedDelay",
+ "description": "Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.as2.bridgeErrorHandler": {
+ "name": "camel.component.as2.bridgeErrorHandler",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.as2.basicPropertyBinding": {
+ "name": "camel.component.as2.basicPropertyBinding",
+ "description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.as2.configuration": {
+ "name": "camel.component.as2.configuration",
+ "description": "Component configuration",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ }
+ }
+}
diff --git a/connectors/camel-asterisk-kafka-connector/src/generated/resources/camel-asterisk-kafka-sink-connector.json b/connectors/camel-asterisk-kafka-connector/src/generated/resources/camel-asterisk-kafka-sink-connector.json
new file mode 100644
index 0000000..1ef0b8d
--- /dev/null
+++ b/connectors/camel-asterisk-kafka-connector/src/generated/resources/camel-asterisk-kafka-sink-connector.json
@@ -0,0 +1,71 @@
+{
+ "connector": {
+ "class": "org.apache.camel.kafkaconnector.asterisk.CamelAsteriskSinkConnector",
+ "artifactId": "camel-asterisk",
+ "groupId": "org.apache.camel",
+ "title": "camel-asterisk",
+ "version": "0.6.0-SNAPSHOT"
+ },
+ "properties": {
+ "camel.sink.path.name": {
+ "name": "camel.sink.path.name",
+ "description": "Name of component",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.sink.endpoint.hostname": {
+ "name": "camel.sink.endpoint.hostname",
+ "description": "The hostname of the asterisk server",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.sink.endpoint.password": {
+ "name": "camel.sink.endpoint.password",
+ "description": "Login password",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.sink.endpoint.username": {
+ "name": "camel.sink.endpoint.username",
+ "description": "Login username",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.sink.endpoint.action": {
+ "name": "camel.sink.endpoint.action",
+ "description": "What action to perform such as getting queue status, sip peers or extension state. One of: [QUEUE_STATUS] [SIP_PEERS] [EXTENSION_STATE]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.lazyStartProducer": {
+ "name": "camel.sink.endpoint.lazyStartProducer",
+ "description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be 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 creating and starting the pr [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.basicPropertyBinding": {
+ "name": "camel.sink.endpoint.basicPropertyBinding",
+ "description": "Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.synchronous": {
+ "name": "camel.sink.endpoint.synchronous",
+ "description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.asterisk.lazyStartProducer": {
+ "name": "camel.component.asterisk.lazyStartProducer",
+ "description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be 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 creating and starting the pr [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.asterisk.basicPropertyBinding": {
+ "name": "camel.component.asterisk.basicPropertyBinding",
+ "description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ }
+ }
+}
diff --git a/connectors/camel-asterisk-kafka-connector/src/generated/resources/camel-asterisk-kafka-source-connector.json b/connectors/camel-asterisk-kafka-connector/src/generated/resources/camel-asterisk-kafka-source-connector.json
new file mode 100644
index 0000000..f55fac3
--- /dev/null
+++ b/connectors/camel-asterisk-kafka-connector/src/generated/resources/camel-asterisk-kafka-source-connector.json
@@ -0,0 +1,77 @@
+{
+ "connector": {
+ "class": "org.apache.camel.kafkaconnector.asterisk.CamelAsteriskSourceConnector",
+ "artifactId": "camel-asterisk",
+ "groupId": "org.apache.camel",
+ "title": "camel-asterisk",
+ "version": "0.6.0-SNAPSHOT"
+ },
+ "properties": {
+ "camel.source.path.name": {
+ "name": "camel.source.path.name",
+ "description": "Name of component",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.source.endpoint.hostname": {
+ "name": "camel.source.endpoint.hostname",
+ "description": "The hostname of the asterisk server",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.source.endpoint.password": {
+ "name": "camel.source.endpoint.password",
+ "description": "Login password",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.source.endpoint.username": {
+ "name": "camel.source.endpoint.username",
+ "description": "Login username",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.source.endpoint.bridgeErrorHandler": {
+ "name": "camel.source.endpoint.bridgeErrorHandler",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.exceptionHandler": {
+ "name": "camel.source.endpoint.exceptionHandler",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.exchangePattern": {
+ "name": "camel.source.endpoint.exchangePattern",
+ "description": "Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.basicPropertyBinding": {
+ "name": "camel.source.endpoint.basicPropertyBinding",
+ "description": "Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.synchronous": {
+ "name": "camel.source.endpoint.synchronous",
+ "description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.asterisk.bridgeErrorHandler": {
+ "name": "camel.component.asterisk.bridgeErrorHandler",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.asterisk.basicPropertyBinding": {
+ "name": "camel.component.asterisk.basicPropertyBinding",
+ "description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ }
+ }
+}
diff --git a/connectors/camel-atmos-kafka-connector/src/generated/resources/camel-atmos-kafka-sink-connector.json b/connectors/camel-atmos-kafka-connector/src/generated/resources/camel-atmos-kafka-sink-connector.json
new file mode 100644
index 0000000..0b8b23a
--- /dev/null
+++ b/connectors/camel-atmos-kafka-connector/src/generated/resources/camel-atmos-kafka-sink-connector.json
@@ -0,0 +1,125 @@
+{
+ "connector": {
+ "class": "org.apache.camel.kafkaconnector.atmos.CamelAtmosSinkConnector",
+ "artifactId": "camel-atmos",
+ "groupId": "org.apache.camel",
+ "title": "camel-atmos",
+ "version": "0.6.0-SNAPSHOT"
+ },
+ "properties": {
+ "camel.sink.path.name": {
+ "name": "camel.sink.path.name",
+ "description": "Atmos name",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.path.operation": {
+ "name": "camel.sink.path.operation",
+ "description": "Operation to perform One of: [put] [del] [search] [get] [move]",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.sink.endpoint.localPath": {
+ "name": "camel.sink.endpoint.localPath",
+ "description": "Local path to put files",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.newRemotePath": {
+ "name": "camel.sink.endpoint.newRemotePath",
+ "description": "New path on Atmos when moving files",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.query": {
+ "name": "camel.sink.endpoint.query",
+ "description": "Search query on Atmos",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.remotePath": {
+ "name": "camel.sink.endpoint.remotePath",
+ "description": "Where to put files on Atmos",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.lazyStartProducer": {
+ "name": "camel.sink.endpoint.lazyStartProducer",
+ "description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be 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 creating and starting the pr [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.basicPropertyBinding": {
+ "name": "camel.sink.endpoint.basicPropertyBinding",
+ "description": "Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.synchronous": {
+ "name": "camel.sink.endpoint.synchronous",
+ "description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.uri": {
+ "name": "camel.sink.endpoint.uri",
+ "description": "Atomos server uri",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.fullTokenId": {
+ "name": "camel.sink.endpoint.fullTokenId",
+ "description": "Atmos client fullTokenId",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.secretKey": {
+ "name": "camel.sink.endpoint.secretKey",
+ "description": "The secret key to pass to the Atmos client (should be base64 encoded)",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.sslValidation": {
+ "name": "camel.sink.endpoint.sslValidation",
+ "description": "Atmos SSL validation",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atmos.lazyStartProducer": {
+ "name": "camel.component.atmos.lazyStartProducer",
+ "description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be 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 creating and starting the pr [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atmos.basicPropertyBinding": {
+ "name": "camel.component.atmos.basicPropertyBinding",
+ "description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atmos.uri": {
+ "name": "camel.component.atmos.uri",
+ "description": "The URI of the server for the Atmos client to connect to",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atmos.fullTokenId": {
+ "name": "camel.component.atmos.fullTokenId",
+ "description": "The token id to pass to the Atmos client",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atmos.secretKey": {
+ "name": "camel.component.atmos.secretKey",
+ "description": "The secret key to pass to the Atmos client (should be base64 encoded)",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atmos.sslValidation": {
+ "name": "camel.component.atmos.sslValidation",
+ "description": "Whether the Atmos client should perform SSL validation",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ }
+ }
+}
diff --git a/connectors/camel-atmos-kafka-connector/src/generated/resources/camel-atmos-kafka-source-connector.json b/connectors/camel-atmos-kafka-connector/src/generated/resources/camel-atmos-kafka-source-connector.json
new file mode 100644
index 0000000..c733143
--- /dev/null
+++ b/connectors/camel-atmos-kafka-connector/src/generated/resources/camel-atmos-kafka-source-connector.json
@@ -0,0 +1,137 @@
+{
+ "connector": {
+ "class": "org.apache.camel.kafkaconnector.atmos.CamelAtmosSourceConnector",
+ "artifactId": "camel-atmos",
+ "groupId": "org.apache.camel",
+ "title": "camel-atmos",
+ "version": "0.6.0-SNAPSHOT"
+ },
+ "properties": {
+ "camel.source.path.name": {
+ "name": "camel.source.path.name",
+ "description": "Atmos name",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.path.operation": {
+ "name": "camel.source.path.operation",
+ "description": "Operation to perform One of: [put] [del] [search] [get] [move]",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.source.endpoint.localPath": {
+ "name": "camel.source.endpoint.localPath",
+ "description": "Local path to put files",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.newRemotePath": {
+ "name": "camel.source.endpoint.newRemotePath",
+ "description": "New path on Atmos when moving files",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.query": {
+ "name": "camel.source.endpoint.query",
+ "description": "Search query on Atmos",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.remotePath": {
+ "name": "camel.source.endpoint.remotePath",
+ "description": "Where to put files on Atmos",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.bridgeErrorHandler": {
+ "name": "camel.source.endpoint.bridgeErrorHandler",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.exceptionHandler": {
+ "name": "camel.source.endpoint.exceptionHandler",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.exchangePattern": {
+ "name": "camel.source.endpoint.exchangePattern",
+ "description": "Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.basicPropertyBinding": {
+ "name": "camel.source.endpoint.basicPropertyBinding",
+ "description": "Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.synchronous": {
+ "name": "camel.source.endpoint.synchronous",
+ "description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.uri": {
+ "name": "camel.source.endpoint.uri",
+ "description": "Atomos server uri",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.fullTokenId": {
+ "name": "camel.source.endpoint.fullTokenId",
+ "description": "Atmos client fullTokenId",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.secretKey": {
+ "name": "camel.source.endpoint.secretKey",
+ "description": "The secret key to pass to the Atmos client (should be base64 encoded)",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.sslValidation": {
+ "name": "camel.source.endpoint.sslValidation",
+ "description": "Atmos SSL validation",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atmos.bridgeErrorHandler": {
+ "name": "camel.component.atmos.bridgeErrorHandler",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atmos.basicPropertyBinding": {
+ "name": "camel.component.atmos.basicPropertyBinding",
+ "description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atmos.uri": {
+ "name": "camel.component.atmos.uri",
+ "description": "The URI of the server for the Atmos client to connect to",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atmos.fullTokenId": {
+ "name": "camel.component.atmos.fullTokenId",
+ "description": "The token id to pass to the Atmos client",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atmos.secretKey": {
+ "name": "camel.component.atmos.secretKey",
+ "description": "The secret key to pass to the Atmos client (should be base64 encoded)",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atmos.sslValidation": {
+ "name": "camel.component.atmos.sslValidation",
+ "description": "Whether the Atmos client should perform SSL validation",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ }
+ }
+}
diff --git a/connectors/camel-atmosphere-websocket-kafka-connector/src/generated/resources/camel-atmosphere-websocket-kafka-sink-connector.json b/connectors/camel-atmosphere-websocket-kafka-connector/src/generated/resources/camel-atmosphere-websocket-kafka-sink-connector.json
new file mode 100644
index 0000000..b661458
--- /dev/null
+++ b/connectors/camel-atmosphere-websocket-kafka-connector/src/generated/resources/camel-atmosphere-websocket-kafka-sink-connector.json
@@ -0,0 +1,137 @@
+{
+ "connector": {
+ "class": "org.apache.camel.kafkaconnector.atmospherewebsocket.CamelAtmospherewebsocketSinkConnector",
+ "artifactId": "camel-atmosphere-websocket",
+ "groupId": "org.apache.camel",
+ "title": "camel-atmosphere-websocket",
+ "version": "0.6.0-SNAPSHOT"
+ },
+ "properties": {
+ "camel.sink.path.servicePath": {
+ "name": "camel.sink.path.servicePath",
+ "description": "Name of websocket endpoint",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.sink.endpoint.chunked": {
+ "name": "camel.sink.endpoint.chunked",
+ "description": "If this option is false the Servlet will disable the HTTP streaming and set the content-length header on the response",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.disableStreamCache": {
+ "name": "camel.sink.endpoint.disableStreamCache",
+ "description": "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 other persistent store. De [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.headerFilterStrategy": {
+ "name": "camel.sink.endpoint.headerFilterStrategy",
+ "description": "To use a custom HeaderFilterStrategy to filter header to and from Camel message.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.sendToAll": {
+ "name": "camel.sink.endpoint.sendToAll",
+ "description": "Whether to send to all (broadcast) or send to a single receiver.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.transferException": {
+ "name": "camel.sink.endpoint.transferException",
+ "description": "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 deserialize the incoming data f [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.useStreaming": {
+ "name": "camel.sink.endpoint.useStreaming",
+ "description": "To enable streaming to send data as multiple text fragments.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.httpBinding": {
+ "name": "camel.sink.endpoint.httpBinding",
+ "description": "To use a custom HttpBinding to control the mapping between Camel message and HttpClient.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.bridgeEndpoint": {
+ "name": "camel.sink.endpoint.bridgeEndpoint",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.lazyStartProducer": {
+ "name": "camel.sink.endpoint.lazyStartProducer",
+ "description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be 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 creating and starting the pr [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.basicPropertyBinding": {
+ "name": "camel.sink.endpoint.basicPropertyBinding",
+ "description": "Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.mapHttpMessageBody": {
+ "name": "camel.sink.endpoint.mapHttpMessageBody",
+ "description": "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.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.mapHttpMessageFormUrlEncodedBody": {
+ "name": "camel.sink.endpoint.mapHttpMessageFormUrlEncodedBody",
+ "description": "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.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.mapHttpMessageHeaders": {
+ "name": "camel.sink.endpoint.mapHttpMessageHeaders",
+ "description": "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.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.synchronous": {
+ "name": "camel.sink.endpoint.synchronous",
+ "description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atmosphere-websocket.lazyStartProducer": {
+ "name": "camel.component.atmosphere-websocket.lazyStartProducer",
+ "description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be 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 creating and starting the pr [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atmosphere-websocket.allowJavaSerializedObject": {
+ "name": "camel.component.atmosphere-websocket.allowJavaSerializedObject",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atmosphere-websocket.basicPropertyBinding": {
+ "name": "camel.component.atmosphere-websocket.basicPropertyBinding",
+ "description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atmosphere-websocket.httpBinding": {
+ "name": "camel.component.atmosphere-websocket.httpBinding",
+ "description": "To use a custom HttpBinding to control the mapping between Camel message and HttpClient.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atmosphere-websocket.httpConfiguration": {
+ "name": "camel.component.atmosphere-websocket.httpConfiguration",
+ "description": "To use the shared HttpConfiguration as base configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atmosphere-websocket.headerFilterStrategy": {
+ "name": "camel.component.atmosphere-websocket.headerFilterStrategy",
+ "description": "To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ }
+ }
+}
diff --git a/connectors/camel-atmosphere-websocket-kafka-connector/src/generated/resources/camel-atmosphere-websocket-kafka-source-connector.json b/connectors/camel-atmosphere-websocket-kafka-connector/src/generated/resources/camel-atmosphere-websocket-kafka-source-connector.json
new file mode 100644
index 0000000..b2e5357
--- /dev/null
+++ b/connectors/camel-atmosphere-websocket-kafka-connector/src/generated/resources/camel-atmosphere-websocket-kafka-source-connector.json
@@ -0,0 +1,233 @@
+{
+ "connector": {
+ "class": "org.apache.camel.kafkaconnector.atmospherewebsocket.CamelAtmospherewebsocketSourceConnector",
+ "artifactId": "camel-atmosphere-websocket",
+ "groupId": "org.apache.camel",
+ "title": "camel-atmosphere-websocket",
+ "version": "0.6.0-SNAPSHOT"
+ },
+ "properties": {
+ "camel.source.path.servicePath": {
+ "name": "camel.source.path.servicePath",
+ "description": "Name of websocket endpoint",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.source.endpoint.chunked": {
+ "name": "camel.source.endpoint.chunked",
+ "description": "If this option is false the Servlet will disable the HTTP streaming and set the content-length header on the response",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.disableStreamCache": {
+ "name": "camel.source.endpoint.disableStreamCache",
+ "description": "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 other persistent store. De [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.headerFilterStrategy": {
+ "name": "camel.source.endpoint.headerFilterStrategy",
+ "description": "To use a custom HeaderFilterStrategy to filter header to and from Camel message.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.sendToAll": {
+ "name": "camel.source.endpoint.sendToAll",
+ "description": "Whether to send to all (broadcast) or send to a single receiver.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.transferException": {
+ "name": "camel.source.endpoint.transferException",
+ "description": "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 deserialize the incoming data f [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.useStreaming": {
+ "name": "camel.source.endpoint.useStreaming",
+ "description": "To enable streaming to send data as multiple text fragments.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.httpBinding": {
+ "name": "camel.source.endpoint.httpBinding",
+ "description": "To use a custom HttpBinding to control the mapping between Camel message and HttpClient.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.async": {
+ "name": "camel.source.endpoint.async",
+ "description": "Configure the consumer to work in async mode",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.bridgeErrorHandler": {
+ "name": "camel.source.endpoint.bridgeErrorHandler",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.httpMethodRestrict": {
+ "name": "camel.source.endpoint.httpMethodRestrict",
+ "description": "Used to only allow consuming if the HttpMethod matches, such as GET\/POST\/PUT etc. Multiple methods can be specified separated by comma.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.matchOnUriPrefix": {
+ "name": "camel.source.endpoint.matchOnUriPrefix",
+ "description": "Whether or not the consumer should try to find a target consumer by matching the URI prefix if no exact match is found.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.muteException": {
+ "name": "camel.source.endpoint.muteException",
+ "description": "If enabled and an Exchange failed processing on the consumer side the response's body won't contain the exception's stack trace.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.responseBufferSize": {
+ "name": "camel.source.endpoint.responseBufferSize",
+ "description": "To use a custom buffer size on the javax.servlet.ServletResponse.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.servletName": {
+ "name": "camel.source.endpoint.servletName",
+ "description": "Name of the servlet to use",
+ "defaultValue": "\"CamelServlet\"",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.attachmentMultipartBinding": {
+ "name": "camel.source.endpoint.attachmentMultipartBinding",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.eagerCheckContentAvailable": {
+ "name": "camel.source.endpoint.eagerCheckContentAvailable",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.exceptionHandler": {
+ "name": "camel.source.endpoint.exceptionHandler",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.exchangePattern": {
+ "name": "camel.source.endpoint.exchangePattern",
+ "description": "Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.fileNameExtWhitelist": {
+ "name": "camel.source.endpoint.fileNameExtWhitelist",
+ "description": "Whitelist of accepted filename extensions for accepting uploaded files. Multiple extensions can be separated by comma, such as txt,xml.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.optionsEnabled": {
+ "name": "camel.source.endpoint.optionsEnabled",
+ "description": "Specifies whether to enable HTTP OPTIONS for this Servlet consumer. By default OPTIONS is turned off.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.traceEnabled": {
+ "name": "camel.source.endpoint.traceEnabled",
+ "description": "Specifies whether to enable HTTP TRACE for this Servlet consumer. By default TRACE is turned off.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.basicPropertyBinding": {
+ "name": "camel.source.endpoint.basicPropertyBinding",
+ "description": "Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.mapHttpMessageBody": {
+ "name": "camel.source.endpoint.mapHttpMessageBody",
+ "description": "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.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.mapHttpMessageFormUrlEncodedBody": {
+ "name": "camel.source.endpoint.mapHttpMessageFormUrlEncodedBody",
+ "description": "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.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.mapHttpMessageHeaders": {
+ "name": "camel.source.endpoint.mapHttpMessageHeaders",
+ "description": "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.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.synchronous": {
+ "name": "camel.source.endpoint.synchronous",
+ "description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atmosphere-websocket.bridgeErrorHandler": {
+ "name": "camel.component.atmosphere-websocket.bridgeErrorHandler",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atmosphere-websocket.servletName": {
+ "name": "camel.component.atmosphere-websocket.servletName",
+ "description": "Default name of servlet to use. The default name is CamelServlet.",
+ "defaultValue": "\"CamelServlet\"",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atmosphere-websocket.attachmentMultipartBinding": {
+ "name": "camel.component.atmosphere-websocket.attachmentMultipartBinding",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atmosphere-websocket.fileNameExtWhitelist": {
+ "name": "camel.component.atmosphere-websocket.fileNameExtWhitelist",
+ "description": "Whitelist of accepted filename extensions for accepting uploaded files. Multiple extensions can be separated by comma, such as txt,xml.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atmosphere-websocket.httpRegistry": {
+ "name": "camel.component.atmosphere-websocket.httpRegistry",
+ "description": "To use a custom org.apache.camel.component.servlet.HttpRegistry.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atmosphere-websocket.allowJavaSerializedObject": {
+ "name": "camel.component.atmosphere-websocket.allowJavaSerializedObject",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atmosphere-websocket.basicPropertyBinding": {
+ "name": "camel.component.atmosphere-websocket.basicPropertyBinding",
+ "description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atmosphere-websocket.httpBinding": {
+ "name": "camel.component.atmosphere-websocket.httpBinding",
+ "description": "To use a custom HttpBinding to control the mapping between Camel message and HttpClient.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atmosphere-websocket.httpConfiguration": {
+ "name": "camel.component.atmosphere-websocket.httpConfiguration",
+ "description": "To use the shared HttpConfiguration as base configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atmosphere-websocket.headerFilterStrategy": {
+ "name": "camel.component.atmosphere-websocket.headerFilterStrategy",
+ "description": "To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ }
+ }
+}
diff --git a/connectors/camel-atom-kafka-connector/src/generated/resources/camel-atom-kafka-source-connector.json b/connectors/camel-atom-kafka-connector/src/generated/resources/camel-atom-kafka-source-connector.json
new file mode 100644
index 0000000..8fe9bde
--- /dev/null
+++ b/connectors/camel-atom-kafka-connector/src/generated/resources/camel-atom-kafka-source-connector.json
@@ -0,0 +1,203 @@
+{
+ "connector": {
+ "class": "org.apache.camel.kafkaconnector.atom.CamelAtomSourceConnector",
+ "artifactId": "camel-atom",
+ "groupId": "org.apache.camel",
+ "title": "camel-atom",
+ "version": "0.6.0-SNAPSHOT"
+ },
+ "properties": {
+ "camel.source.path.feedUri": {
+ "name": "camel.source.path.feedUri",
+ "description": "The URI to the feed to poll.",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.source.endpoint.bridgeErrorHandler": {
+ "name": "camel.source.endpoint.bridgeErrorHandler",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.feedHeader": {
+ "name": "camel.source.endpoint.feedHeader",
+ "description": "Sets whether to add the feed object as a header.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.filter": {
+ "name": "camel.source.endpoint.filter",
+ "description": "Sets whether to use filtering or not of the entries.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.lastUpdate": {
+ "name": "camel.source.endpoint.lastUpdate",
+ "description": "Sets the timestamp to be used for filtering entries from the atom feeds. This options is only in conjunction with the splitEntries.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.password": {
+ "name": "camel.source.endpoint.password",
+ "description": "Sets the password to be used for basic authentication when polling from a HTTP feed.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.sendEmptyMessageWhenIdle": {
+ "name": "camel.source.endpoint.sendEmptyMessageWhenIdle",
+ "description": "If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.sortEntries": {
+ "name": "camel.source.endpoint.sortEntries",
+ "description": "Sets whether to sort entries by published date. Only works when splitEntries = true.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.splitEntries": {
+ "name": "camel.source.endpoint.splitEntries",
+ "description": "Sets whether or not entries should be sent individually or whether the entire feed should be sent as a single message",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.throttleEntries": {
+ "name": "camel.source.endpoint.throttleEntries",
+ "description": "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.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.username": {
+ "name": "camel.source.endpoint.username",
+ "description": "Sets the username to be used for basic authentication when polling from a HTTP feed.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.exceptionHandler": {
+ "name": "camel.source.endpoint.exceptionHandler",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.exchangePattern": {
+ "name": "camel.source.endpoint.exchangePattern",
+ "description": "Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.pollStrategy": {
+ "name": "camel.source.endpoint.pollStrategy",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.basicPropertyBinding": {
+ "name": "camel.source.endpoint.basicPropertyBinding",
+ "description": "Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.synchronous": {
+ "name": "camel.source.endpoint.synchronous",
+ "description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.backoffErrorThreshold": {
+ "name": "camel.source.endpoint.backoffErrorThreshold",
+ "description": "The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.backoffIdleThreshold": {
+ "name": "camel.source.endpoint.backoffIdleThreshold",
+ "description": "The number of subsequent idle polls that should happen before the backoffMultipler should kick-in.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.backoffMultiplier": {
+ "name": "camel.source.endpoint.backoffMultiplier",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.delay": {
+ "name": "camel.source.endpoint.delay",
+ "description": "Milliseconds before the next poll.",
+ "defaultValue": "500L",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.greedy": {
+ "name": "camel.source.endpoint.greedy",
+ "description": "If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.initialDelay": {
+ "name": "camel.source.endpoint.initialDelay",
+ "description": "Milliseconds before the first poll starts.",
+ "defaultValue": "1000L",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.repeatCount": {
+ "name": "camel.source.endpoint.repeatCount",
+ "description": "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.",
+ "defaultValue": "0L",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.runLoggingLevel": {
+ "name": "camel.source.endpoint.runLoggingLevel",
+ "description": "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]",
+ "defaultValue": "\"TRACE\"",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.scheduledExecutorService": {
+ "name": "camel.source.endpoint.scheduledExecutorService",
+ "description": "Allows for configuring a custom\/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.scheduler": {
+ "name": "camel.source.endpoint.scheduler",
+ "description": "To use a cron scheduler from either camel-spring or camel-quartz component. Use value spring or quartz for built in scheduler",
+ "defaultValue": "\"none\"",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.schedulerProperties": {
+ "name": "camel.source.endpoint.schedulerProperties",
+ "description": "To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.startScheduler": {
+ "name": "camel.source.endpoint.startScheduler",
+ "description": "Whether the scheduler should be auto started.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.timeUnit": {
+ "name": "camel.source.endpoint.timeUnit",
+ "description": "Time unit for initialDelay and delay options. One of: [NANOSECONDS] [MICROSECONDS] [MILLISECONDS] [SECONDS] [MINUTES] [HOURS] [DAYS]",
+ "defaultValue": "\"MILLISECONDS\"",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.useFixedDelay": {
+ "name": "camel.source.endpoint.useFixedDelay",
+ "description": "Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atom.bridgeErrorHandler": {
+ "name": "camel.component.atom.bridgeErrorHandler",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atom.basicPropertyBinding": {
+ "name": "camel.component.atom.basicPropertyBinding",
+ "description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ }
+ }
+}
diff --git a/connectors/camel-atomix-map-kafka-connector/src/generated/resources/camel-atomix-map-kafka-sink-connector.json b/connectors/camel-atomix-map-kafka-connector/src/generated/resources/camel-atomix-map-kafka-sink-connector.json
new file mode 100644
index 0000000..cd90388
--- /dev/null
+++ b/connectors/camel-atomix-map-kafka-connector/src/generated/resources/camel-atomix-map-kafka-sink-connector.json
@@ -0,0 +1,221 @@
+{
+ "connector": {
+ "class": "org.apache.camel.kafkaconnector.atomixmap.CamelAtomixmapSinkConnector",
+ "artifactId": "camel-atomix-map",
+ "groupId": "org.apache.camel",
+ "title": "camel-atomix-map",
+ "version": "0.6.0-SNAPSHOT"
+ },
+ "properties": {
+ "camel.sink.path.resourceName": {
+ "name": "camel.sink.path.resourceName",
+ "description": "The distributed resource name",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.sink.endpoint.atomix": {
+ "name": "camel.sink.endpoint.atomix",
+ "description": "The Atomix instance to use",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.configurationUri": {
+ "name": "camel.sink.endpoint.configurationUri",
+ "description": "The Atomix configuration uri.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.defaultAction": {
+ "name": "camel.sink.endpoint.defaultAction",
+ "description": "The default action. One of: [PUT] [PUT_IF_ABSENT] [GET] [CLEAR] [SIZE] [CONTAINS_KEY] [CONTAINS_VALUE] [IS_EMPTY] [ENTRY_SET] [REMOVE] [REPLACE] [VALUES]",
+ "defaultValue": "\"PUT\"",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.key": {
+ "name": "camel.sink.endpoint.key",
+ "description": "The key to use if none is set in the header or to listen for events for a specific key.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.nodes": {
+ "name": "camel.sink.endpoint.nodes",
+ "description": "The address of the nodes composing the cluster.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.resultHeader": {
+ "name": "camel.sink.endpoint.resultHeader",
+ "description": "The header that wil carry the result.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.transportClassName": {
+ "name": "camel.sink.endpoint.transportClassName",
+ "description": "The class name (fqn) of the Atomix transport",
+ "defaultValue": "\"io.atomix.catalyst.transport.netty.NettyTransport\"",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.ttl": {
+ "name": "camel.sink.endpoint.ttl",
+ "description": "The resource ttl.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.lazyStartProducer": {
+ "name": "camel.sink.endpoint.lazyStartProducer",
+ "description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be 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 creating and starting the pr [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.basicPropertyBinding": {
+ "name": "camel.sink.endpoint.basicPropertyBinding",
+ "description": "Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.defaultResourceConfig": {
+ "name": "camel.sink.endpoint.defaultResourceConfig",
+ "description": "The cluster wide default resource configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.defaultResourceOptions": {
+ "name": "camel.sink.endpoint.defaultResourceOptions",
+ "description": "The local default resource options.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.ephemeral": {
+ "name": "camel.sink.endpoint.ephemeral",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.readConsistency": {
+ "name": "camel.sink.endpoint.readConsistency",
+ "description": "The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.resourceConfigs": {
+ "name": "camel.sink.endpoint.resourceConfigs",
+ "description": "Cluster wide resources configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.resourceOptions": {
+ "name": "camel.sink.endpoint.resourceOptions",
+ "description": "Local resources configurations",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.synchronous": {
+ "name": "camel.sink.endpoint.synchronous",
+ "description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-map.atomix": {
+ "name": "camel.component.atomix-map.atomix",
+ "description": "The Atomix instance to use",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-map.configuration": {
+ "name": "camel.component.atomix-map.configuration",
+ "description": "The shared component configuration",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-map.configurationUri": {
+ "name": "camel.component.atomix-map.configurationUri",
+ "description": "The path to the AtomixClient configuration",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-map.defaultAction": {
+ "name": "camel.component.atomix-map.defaultAction",
+ "description": "The default action. One of: [PUT] [PUT_IF_ABSENT] [GET] [CLEAR] [SIZE] [CONTAINS_KEY] [CONTAINS_VALUE] [IS_EMPTY] [ENTRY_SET] [REMOVE] [REPLACE] [VALUES]",
+ "defaultValue": "\"PUT\"",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-map.key": {
+ "name": "camel.component.atomix-map.key",
+ "description": "The key to use if none is set in the header or to listen for events for a specific key.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-map.nodes": {
+ "name": "camel.component.atomix-map.nodes",
+ "description": "The nodes the AtomixClient should connect to",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-map.resultHeader": {
+ "name": "camel.component.atomix-map.resultHeader",
+ "description": "The header that wil carry the result.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-map.transportClassName": {
+ "name": "camel.component.atomix-map.transportClassName",
+ "description": "The class name (fqn) of the Atomix transport",
+ "defaultValue": "\"io.atomix.catalyst.transport.netty.NettyTransport\"",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-map.ttl": {
+ "name": "camel.component.atomix-map.ttl",
+ "description": "The resource ttl.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-map.lazyStartProducer": {
+ "name": "camel.component.atomix-map.lazyStartProducer",
+ "description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be 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 creating and starting the pr [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-map.basicPropertyBinding": {
+ "name": "camel.component.atomix-map.basicPropertyBinding",
+ "description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-map.defaultResourceConfig": {
+ "name": "camel.component.atomix-map.defaultResourceConfig",
+ "description": "The cluster wide default resource configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-map.defaultResourceOptions": {
+ "name": "camel.component.atomix-map.defaultResourceOptions",
+ "description": "The local default resource options.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-map.ephemeral": {
+ "name": "camel.component.atomix-map.ephemeral",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-map.readConsistency": {
+ "name": "camel.component.atomix-map.readConsistency",
+ "description": "The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-map.resourceConfigs": {
+ "name": "camel.component.atomix-map.resourceConfigs",
+ "description": "Cluster wide resources configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-map.resourceOptions": {
+ "name": "camel.component.atomix-map.resourceOptions",
+ "description": "Local resources configurations",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ }
+ }
+}
diff --git a/connectors/camel-atomix-map-kafka-connector/src/generated/resources/camel-atomix-map-kafka-source-connector.json b/connectors/camel-atomix-map-kafka-connector/src/generated/resources/camel-atomix-map-kafka-source-connector.json
new file mode 100644
index 0000000..176a89e
--- /dev/null
+++ b/connectors/camel-atomix-map-kafka-connector/src/generated/resources/camel-atomix-map-kafka-source-connector.json
@@ -0,0 +1,233 @@
+{
+ "connector": {
+ "class": "org.apache.camel.kafkaconnector.atomixmap.CamelAtomixmapSourceConnector",
+ "artifactId": "camel-atomix-map",
+ "groupId": "org.apache.camel",
+ "title": "camel-atomix-map",
+ "version": "0.6.0-SNAPSHOT"
+ },
+ "properties": {
+ "camel.source.path.resourceName": {
+ "name": "camel.source.path.resourceName",
+ "description": "The distributed resource name",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.source.endpoint.atomix": {
+ "name": "camel.source.endpoint.atomix",
+ "description": "The Atomix instance to use",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.configurationUri": {
+ "name": "camel.source.endpoint.configurationUri",
+ "description": "The Atomix configuration uri.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.defaultAction": {
+ "name": "camel.source.endpoint.defaultAction",
+ "description": "The default action. One of: [PUT] [PUT_IF_ABSENT] [GET] [CLEAR] [SIZE] [CONTAINS_KEY] [CONTAINS_VALUE] [IS_EMPTY] [ENTRY_SET] [REMOVE] [REPLACE] [VALUES]",
+ "defaultValue": "\"PUT\"",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.key": {
+ "name": "camel.source.endpoint.key",
+ "description": "The key to use if none is set in the header or to listen for events for a specific key.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.nodes": {
+ "name": "camel.source.endpoint.nodes",
+ "description": "The address of the nodes composing the cluster.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.resultHeader": {
+ "name": "camel.source.endpoint.resultHeader",
+ "description": "The header that wil carry the result.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.transportClassName": {
+ "name": "camel.source.endpoint.transportClassName",
+ "description": "The class name (fqn) of the Atomix transport",
+ "defaultValue": "\"io.atomix.catalyst.transport.netty.NettyTransport\"",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.ttl": {
+ "name": "camel.source.endpoint.ttl",
+ "description": "The resource ttl.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.bridgeErrorHandler": {
+ "name": "camel.source.endpoint.bridgeErrorHandler",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.exceptionHandler": {
+ "name": "camel.source.endpoint.exceptionHandler",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.exchangePattern": {
+ "name": "camel.source.endpoint.exchangePattern",
+ "description": "Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.basicPropertyBinding": {
+ "name": "camel.source.endpoint.basicPropertyBinding",
+ "description": "Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.defaultResourceConfig": {
+ "name": "camel.source.endpoint.defaultResourceConfig",
+ "description": "The cluster wide default resource configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.defaultResourceOptions": {
+ "name": "camel.source.endpoint.defaultResourceOptions",
+ "description": "The local default resource options.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.ephemeral": {
+ "name": "camel.source.endpoint.ephemeral",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.readConsistency": {
+ "name": "camel.source.endpoint.readConsistency",
+ "description": "The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.resourceConfigs": {
+ "name": "camel.source.endpoint.resourceConfigs",
+ "description": "Cluster wide resources configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.resourceOptions": {
+ "name": "camel.source.endpoint.resourceOptions",
+ "description": "Local resources configurations",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.synchronous": {
+ "name": "camel.source.endpoint.synchronous",
+ "description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-map.atomix": {
+ "name": "camel.component.atomix-map.atomix",
+ "description": "The Atomix instance to use",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-map.configuration": {
+ "name": "camel.component.atomix-map.configuration",
+ "description": "The shared component configuration",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-map.configurationUri": {
+ "name": "camel.component.atomix-map.configurationUri",
+ "description": "The path to the AtomixClient configuration",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-map.defaultAction": {
+ "name": "camel.component.atomix-map.defaultAction",
+ "description": "The default action. One of: [PUT] [PUT_IF_ABSENT] [GET] [CLEAR] [SIZE] [CONTAINS_KEY] [CONTAINS_VALUE] [IS_EMPTY] [ENTRY_SET] [REMOVE] [REPLACE] [VALUES]",
+ "defaultValue": "\"PUT\"",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-map.key": {
+ "name": "camel.component.atomix-map.key",
+ "description": "The key to use if none is set in the header or to listen for events for a specific key.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-map.nodes": {
+ "name": "camel.component.atomix-map.nodes",
+ "description": "The nodes the AtomixClient should connect to",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-map.resultHeader": {
+ "name": "camel.component.atomix-map.resultHeader",
+ "description": "The header that wil carry the result.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-map.transportClassName": {
+ "name": "camel.component.atomix-map.transportClassName",
+ "description": "The class name (fqn) of the Atomix transport",
+ "defaultValue": "\"io.atomix.catalyst.transport.netty.NettyTransport\"",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-map.ttl": {
+ "name": "camel.component.atomix-map.ttl",
+ "description": "The resource ttl.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-map.bridgeErrorHandler": {
+ "name": "camel.component.atomix-map.bridgeErrorHandler",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-map.basicPropertyBinding": {
+ "name": "camel.component.atomix-map.basicPropertyBinding",
+ "description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-map.defaultResourceConfig": {
+ "name": "camel.component.atomix-map.defaultResourceConfig",
+ "description": "The cluster wide default resource configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-map.defaultResourceOptions": {
+ "name": "camel.component.atomix-map.defaultResourceOptions",
+ "description": "The local default resource options.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-map.ephemeral": {
+ "name": "camel.component.atomix-map.ephemeral",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-map.readConsistency": {
+ "name": "camel.component.atomix-map.readConsistency",
+ "description": "The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-map.resourceConfigs": {
+ "name": "camel.component.atomix-map.resourceConfigs",
+ "description": "Cluster wide resources configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-map.resourceOptions": {
+ "name": "camel.component.atomix-map.resourceOptions",
+ "description": "Local resources configurations",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ }
+ }
+}
diff --git a/connectors/camel-atomix-messaging-kafka-connector/src/generated/resources/camel-atomix-messaging-kafka-sink-connector.json b/connectors/camel-atomix-messaging-kafka-connector/src/generated/resources/camel-atomix-messaging-kafka-sink-connector.json
new file mode 100644
index 0000000..d5951c3
--- /dev/null
+++ b/connectors/camel-atomix-messaging-kafka-connector/src/generated/resources/camel-atomix-messaging-kafka-sink-connector.json
@@ -0,0 +1,233 @@
+{
+ "connector": {
+ "class": "org.apache.camel.kafkaconnector.atomixmessaging.CamelAtomixmessagingSinkConnector",
+ "artifactId": "camel-atomix-messaging",
+ "groupId": "org.apache.camel",
+ "title": "camel-atomix-messaging",
+ "version": "0.6.0-SNAPSHOT"
+ },
+ "properties": {
+ "camel.sink.path.resourceName": {
+ "name": "camel.sink.path.resourceName",
+ "description": "The distributed resource name",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.sink.endpoint.atomix": {
+ "name": "camel.sink.endpoint.atomix",
+ "description": "The Atomix instance to use",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.broadcastType": {
+ "name": "camel.sink.endpoint.broadcastType",
+ "description": "The broadcast type. One of: [ALL] [RANDOM]",
+ "defaultValue": "\"ALL\"",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.channelName": {
+ "name": "camel.sink.endpoint.channelName",
+ "description": "The messaging channel name",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.configurationUri": {
+ "name": "camel.sink.endpoint.configurationUri",
+ "description": "The Atomix configuration uri.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.defaultAction": {
+ "name": "camel.sink.endpoint.defaultAction",
+ "description": "The default action. One of: [DIRECT] [BROADCAST]",
+ "defaultValue": "\"DIRECT\"",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.memberName": {
+ "name": "camel.sink.endpoint.memberName",
+ "description": "The Atomix Group member name",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.nodes": {
+ "name": "camel.sink.endpoint.nodes",
+ "description": "The address of the nodes composing the cluster.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.resultHeader": {
+ "name": "camel.sink.endpoint.resultHeader",
+ "description": "The header that wil carry the result.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.transportClassName": {
+ "name": "camel.sink.endpoint.transportClassName",
+ "description": "The class name (fqn) of the Atomix transport",
+ "defaultValue": "\"io.atomix.catalyst.transport.netty.NettyTransport\"",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.lazyStartProducer": {
+ "name": "camel.sink.endpoint.lazyStartProducer",
+ "description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be 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 creating and starting the pr [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.basicPropertyBinding": {
+ "name": "camel.sink.endpoint.basicPropertyBinding",
+ "description": "Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.defaultResourceConfig": {
+ "name": "camel.sink.endpoint.defaultResourceConfig",
+ "description": "The cluster wide default resource configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.defaultResourceOptions": {
+ "name": "camel.sink.endpoint.defaultResourceOptions",
+ "description": "The local default resource options.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.ephemeral": {
+ "name": "camel.sink.endpoint.ephemeral",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.readConsistency": {
+ "name": "camel.sink.endpoint.readConsistency",
+ "description": "The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.resourceConfigs": {
+ "name": "camel.sink.endpoint.resourceConfigs",
+ "description": "Cluster wide resources configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.resourceOptions": {
+ "name": "camel.sink.endpoint.resourceOptions",
+ "description": "Local resources configurations",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.synchronous": {
+ "name": "camel.sink.endpoint.synchronous",
+ "description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-messaging.atomix": {
+ "name": "camel.component.atomix-messaging.atomix",
+ "description": "The Atomix instance to use",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-messaging.broadcastType": {
+ "name": "camel.component.atomix-messaging.broadcastType",
+ "description": "The broadcast type. One of: [ALL] [RANDOM]",
+ "defaultValue": "\"ALL\"",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-messaging.channelName": {
+ "name": "camel.component.atomix-messaging.channelName",
+ "description": "The messaging channel name",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-messaging.configuration": {
+ "name": "camel.component.atomix-messaging.configuration",
+ "description": "The shared component configuration",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-messaging.configurationUri": {
+ "name": "camel.component.atomix-messaging.configurationUri",
+ "description": "The path to the AtomixClient configuration",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-messaging.defaultAction": {
+ "name": "camel.component.atomix-messaging.defaultAction",
+ "description": "The default action. One of: [DIRECT] [BROADCAST]",
+ "defaultValue": "\"DIRECT\"",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-messaging.memberName": {
+ "name": "camel.component.atomix-messaging.memberName",
+ "description": "The Atomix Group member name",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-messaging.nodes": {
+ "name": "camel.component.atomix-messaging.nodes",
+ "description": "The nodes the AtomixClient should connect to",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-messaging.resultHeader": {
+ "name": "camel.component.atomix-messaging.resultHeader",
+ "description": "The header that wil carry the result.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-messaging.transportClassName": {
+ "name": "camel.component.atomix-messaging.transportClassName",
+ "description": "The class name (fqn) of the Atomix transport",
+ "defaultValue": "\"io.atomix.catalyst.transport.netty.NettyTransport\"",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-messaging.lazyStartProducer": {
+ "name": "camel.component.atomix-messaging.lazyStartProducer",
+ "description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be 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 creating and starting the pr [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-messaging.basicPropertyBinding": {
+ "name": "camel.component.atomix-messaging.basicPropertyBinding",
+ "description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-messaging.defaultResourceConfig": {
+ "name": "camel.component.atomix-messaging.defaultResourceConfig",
+ "description": "The cluster wide default resource configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-messaging.defaultResourceOptions": {
+ "name": "camel.component.atomix-messaging.defaultResourceOptions",
+ "description": "The local default resource options.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-messaging.ephemeral": {
+ "name": "camel.component.atomix-messaging.ephemeral",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-messaging.readConsistency": {
+ "name": "camel.component.atomix-messaging.readConsistency",
+ "description": "The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-messaging.resourceConfigs": {
+ "name": "camel.component.atomix-messaging.resourceConfigs",
+ "description": "Cluster wide resources configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-messaging.resourceOptions": {
+ "name": "camel.component.atomix-messaging.resourceOptions",
+ "description": "Local resources configurations",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ }
+ }
+}
diff --git a/connectors/camel-atomix-messaging-kafka-connector/src/generated/resources/camel-atomix-messaging-kafka-source-connector.json b/connectors/camel-atomix-messaging-kafka-connector/src/generated/resources/camel-atomix-messaging-kafka-source-connector.json
new file mode 100644
index 0000000..305def8
--- /dev/null
+++ b/connectors/camel-atomix-messaging-kafka-connector/src/generated/resources/camel-atomix-messaging-kafka-source-connector.json
@@ -0,0 +1,245 @@
+{
+ "connector": {
+ "class": "org.apache.camel.kafkaconnector.atomixmessaging.CamelAtomixmessagingSourceConnector",
+ "artifactId": "camel-atomix-messaging",
+ "groupId": "org.apache.camel",
+ "title": "camel-atomix-messaging",
+ "version": "0.6.0-SNAPSHOT"
+ },
+ "properties": {
+ "camel.source.path.resourceName": {
+ "name": "camel.source.path.resourceName",
+ "description": "The distributed resource name",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.source.endpoint.atomix": {
+ "name": "camel.source.endpoint.atomix",
+ "description": "The Atomix instance to use",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.broadcastType": {
+ "name": "camel.source.endpoint.broadcastType",
+ "description": "The broadcast type. One of: [ALL] [RANDOM]",
+ "defaultValue": "\"ALL\"",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.channelName": {
+ "name": "camel.source.endpoint.channelName",
+ "description": "The messaging channel name",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.configurationUri": {
+ "name": "camel.source.endpoint.configurationUri",
+ "description": "The Atomix configuration uri.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.defaultAction": {
+ "name": "camel.source.endpoint.defaultAction",
+ "description": "The default action. One of: [DIRECT] [BROADCAST]",
+ "defaultValue": "\"DIRECT\"",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.memberName": {
+ "name": "camel.source.endpoint.memberName",
+ "description": "The Atomix Group member name",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.nodes": {
+ "name": "camel.source.endpoint.nodes",
+ "description": "The address of the nodes composing the cluster.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.resultHeader": {
+ "name": "camel.source.endpoint.resultHeader",
+ "description": "The header that wil carry the result.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.transportClassName": {
+ "name": "camel.source.endpoint.transportClassName",
+ "description": "The class name (fqn) of the Atomix transport",
+ "defaultValue": "\"io.atomix.catalyst.transport.netty.NettyTransport\"",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.bridgeErrorHandler": {
+ "name": "camel.source.endpoint.bridgeErrorHandler",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.exceptionHandler": {
+ "name": "camel.source.endpoint.exceptionHandler",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.exchangePattern": {
+ "name": "camel.source.endpoint.exchangePattern",
+ "description": "Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.basicPropertyBinding": {
+ "name": "camel.source.endpoint.basicPropertyBinding",
+ "description": "Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.defaultResourceConfig": {
+ "name": "camel.source.endpoint.defaultResourceConfig",
+ "description": "The cluster wide default resource configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.defaultResourceOptions": {
+ "name": "camel.source.endpoint.defaultResourceOptions",
+ "description": "The local default resource options.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.ephemeral": {
+ "name": "camel.source.endpoint.ephemeral",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.readConsistency": {
+ "name": "camel.source.endpoint.readConsistency",
+ "description": "The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.resourceConfigs": {
+ "name": "camel.source.endpoint.resourceConfigs",
+ "description": "Cluster wide resources configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.resourceOptions": {
+ "name": "camel.source.endpoint.resourceOptions",
+ "description": "Local resources configurations",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.synchronous": {
+ "name": "camel.source.endpoint.synchronous",
+ "description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-messaging.atomix": {
+ "name": "camel.component.atomix-messaging.atomix",
+ "description": "The Atomix instance to use",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-messaging.broadcastType": {
+ "name": "camel.component.atomix-messaging.broadcastType",
+ "description": "The broadcast type. One of: [ALL] [RANDOM]",
+ "defaultValue": "\"ALL\"",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-messaging.channelName": {
+ "name": "camel.component.atomix-messaging.channelName",
+ "description": "The messaging channel name",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-messaging.configuration": {
+ "name": "camel.component.atomix-messaging.configuration",
+ "description": "The shared component configuration",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-messaging.configurationUri": {
+ "name": "camel.component.atomix-messaging.configurationUri",
+ "description": "The path to the AtomixClient configuration",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-messaging.defaultAction": {
+ "name": "camel.component.atomix-messaging.defaultAction",
+ "description": "The default action. One of: [DIRECT] [BROADCAST]",
+ "defaultValue": "\"DIRECT\"",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-messaging.memberName": {
+ "name": "camel.component.atomix-messaging.memberName",
+ "description": "The Atomix Group member name",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-messaging.nodes": {
+ "name": "camel.component.atomix-messaging.nodes",
+ "description": "The nodes the AtomixClient should connect to",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-messaging.resultHeader": {
+ "name": "camel.component.atomix-messaging.resultHeader",
+ "description": "The header that wil carry the result.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-messaging.transportClassName": {
+ "name": "camel.component.atomix-messaging.transportClassName",
+ "description": "The class name (fqn) of the Atomix transport",
+ "defaultValue": "\"io.atomix.catalyst.transport.netty.NettyTransport\"",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-messaging.bridgeErrorHandler": {
+ "name": "camel.component.atomix-messaging.bridgeErrorHandler",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-messaging.basicPropertyBinding": {
+ "name": "camel.component.atomix-messaging.basicPropertyBinding",
+ "description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-messaging.defaultResourceConfig": {
+ "name": "camel.component.atomix-messaging.defaultResourceConfig",
+ "description": "The cluster wide default resource configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-messaging.defaultResourceOptions": {
+ "name": "camel.component.atomix-messaging.defaultResourceOptions",
+ "description": "The local default resource options.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-messaging.ephemeral": {
+ "name": "camel.component.atomix-messaging.ephemeral",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-messaging.readConsistency": {
+ "name": "camel.component.atomix-messaging.readConsistency",
+ "description": "The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-messaging.resourceConfigs": {
+ "name": "camel.component.atomix-messaging.resourceConfigs",
+ "description": "Cluster wide resources configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-messaging.resourceOptions": {
+ "name": "camel.component.atomix-messaging.resourceOptions",
+ "description": "Local resources configurations",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ }
+ }
+}
diff --git a/connectors/camel-atomix-multimap-kafka-connector/src/generated/resources/camel-atomix-multimap-kafka-sink-connector.json b/connectors/camel-atomix-multimap-kafka-connector/src/generated/resources/camel-atomix-multimap-kafka-sink-connector.json
new file mode 100644
index 0000000..6d60b1f
--- /dev/null
+++ b/connectors/camel-atomix-multimap-kafka-connector/src/generated/resources/camel-atomix-multimap-kafka-sink-connector.json
@@ -0,0 +1,221 @@
+{
+ "connector": {
+ "class": "org.apache.camel.kafkaconnector.atomixmultimap.CamelAtomixmultimapSinkConnector",
+ "artifactId": "camel-atomix-multimap",
+ "groupId": "org.apache.camel",
+ "title": "camel-atomix-multimap",
+ "version": "0.6.0-SNAPSHOT"
+ },
+ "properties": {
+ "camel.sink.path.resourceName": {
+ "name": "camel.sink.path.resourceName",
+ "description": "The distributed resource name",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.sink.endpoint.atomix": {
+ "name": "camel.sink.endpoint.atomix",
+ "description": "The Atomix instance to use",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.configurationUri": {
+ "name": "camel.sink.endpoint.configurationUri",
+ "description": "The Atomix configuration uri.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.defaultAction": {
+ "name": "camel.sink.endpoint.defaultAction",
+ "description": "The default action. One of: [PUT] [GET] [CLEAR] [SIZE] [CONTAINS_KEY] [IS_EMPTY] [REMOVE] [REMOVE_VALUE]",
+ "defaultValue": "\"PUT\"",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.key": {
+ "name": "camel.sink.endpoint.key",
+ "description": "The key to use if none is set in the header or to listen for events for a specific key.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.lazyStartProducer": {
+ "name": "camel.sink.endpoint.lazyStartProducer",
+ "description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be 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 creating and starting the pr [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.nodes": {
+ "name": "camel.sink.endpoint.nodes",
+ "description": "The address of the nodes composing the cluster.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.resultHeader": {
+ "name": "camel.sink.endpoint.resultHeader",
+ "description": "The header that wil carry the result.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.transportClassName": {
+ "name": "camel.sink.endpoint.transportClassName",
+ "description": "The class name (fqn) of the Atomix transport",
+ "defaultValue": "\"io.atomix.catalyst.transport.netty.NettyTransport\"",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.ttl": {
+ "name": "camel.sink.endpoint.ttl",
+ "description": "The resource ttl.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.basicPropertyBinding": {
+ "name": "camel.sink.endpoint.basicPropertyBinding",
+ "description": "Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.defaultResourceConfig": {
+ "name": "camel.sink.endpoint.defaultResourceConfig",
+ "description": "The cluster wide default resource configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.defaultResourceOptions": {
+ "name": "camel.sink.endpoint.defaultResourceOptions",
+ "description": "The local default resource options.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.ephemeral": {
+ "name": "camel.sink.endpoint.ephemeral",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.readConsistency": {
+ "name": "camel.sink.endpoint.readConsistency",
+ "description": "The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.resourceConfigs": {
+ "name": "camel.sink.endpoint.resourceConfigs",
+ "description": "Cluster wide resources configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.resourceOptions": {
+ "name": "camel.sink.endpoint.resourceOptions",
+ "description": "Local resources configurations",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.synchronous": {
+ "name": "camel.sink.endpoint.synchronous",
+ "description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-multimap.atomix": {
+ "name": "camel.component.atomix-multimap.atomix",
+ "description": "The Atomix instance to use",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-multimap.configuration": {
+ "name": "camel.component.atomix-multimap.configuration",
+ "description": "The shared component configuration",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-multimap.configurationUri": {
+ "name": "camel.component.atomix-multimap.configurationUri",
+ "description": "The path to the AtomixClient configuration",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-multimap.defaultAction": {
+ "name": "camel.component.atomix-multimap.defaultAction",
+ "description": "The default action. One of: [PUT] [GET] [CLEAR] [SIZE] [CONTAINS_KEY] [IS_EMPTY] [REMOVE] [REMOVE_VALUE]",
+ "defaultValue": "\"PUT\"",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-multimap.key": {
+ "name": "camel.component.atomix-multimap.key",
+ "description": "The key to use if none is set in the header or to listen for events for a specific key.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-multimap.lazyStartProducer": {
+ "name": "camel.component.atomix-multimap.lazyStartProducer",
+ "description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be 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 creating and starting the pr [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-multimap.nodes": {
+ "name": "camel.component.atomix-multimap.nodes",
+ "description": "The nodes the AtomixClient should connect to",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-multimap.resultHeader": {
+ "name": "camel.component.atomix-multimap.resultHeader",
+ "description": "The header that wil carry the result.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-multimap.transportClassName": {
+ "name": "camel.component.atomix-multimap.transportClassName",
+ "description": "The class name (fqn) of the Atomix transport",
+ "defaultValue": "\"io.atomix.catalyst.transport.netty.NettyTransport\"",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-multimap.ttl": {
+ "name": "camel.component.atomix-multimap.ttl",
+ "description": "The resource ttl.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-multimap.basicPropertyBinding": {
+ "name": "camel.component.atomix-multimap.basicPropertyBinding",
+ "description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-multimap.defaultResourceConfig": {
+ "name": "camel.component.atomix-multimap.defaultResourceConfig",
+ "description": "The cluster wide default resource configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-multimap.defaultResourceOptions": {
+ "name": "camel.component.atomix-multimap.defaultResourceOptions",
+ "description": "The local default resource options.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-multimap.ephemeral": {
+ "name": "camel.component.atomix-multimap.ephemeral",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-multimap.readConsistency": {
+ "name": "camel.component.atomix-multimap.readConsistency",
+ "description": "The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-multimap.resourceConfigs": {
+ "name": "camel.component.atomix-multimap.resourceConfigs",
+ "description": "Cluster wide resources configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-multimap.resourceOptions": {
+ "name": "camel.component.atomix-multimap.resourceOptions",
+ "description": "Local resources configurations",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ }
+ }
+}
diff --git a/connectors/camel-atomix-queue-kafka-connector/src/generated/resources/camel-atomix-queue-kafka-sink-connector.json b/connectors/camel-atomix-queue-kafka-connector/src/generated/resources/camel-atomix-queue-kafka-sink-connector.json
new file mode 100644
index 0000000..010b523
--- /dev/null
+++ b/connectors/camel-atomix-queue-kafka-connector/src/generated/resources/camel-atomix-queue-kafka-sink-connector.json
@@ -0,0 +1,197 @@
+{
+ "connector": {
+ "class": "org.apache.camel.kafkaconnector.atomixqueue.CamelAtomixqueueSinkConnector",
+ "artifactId": "camel-atomix-queue",
+ "groupId": "org.apache.camel",
+ "title": "camel-atomix-queue",
+ "version": "0.6.0-SNAPSHOT"
+ },
+ "properties": {
+ "camel.sink.path.resourceName": {
+ "name": "camel.sink.path.resourceName",
+ "description": "The distributed resource name",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.sink.endpoint.atomix": {
+ "name": "camel.sink.endpoint.atomix",
+ "description": "The Atomix instance to use",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.configurationUri": {
+ "name": "camel.sink.endpoint.configurationUri",
+ "description": "The Atomix configuration uri.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.defaultAction": {
+ "name": "camel.sink.endpoint.defaultAction",
+ "description": "The default action. One of: [ADD] [OFFER] [PEEK] [POLL] [CLEAR] [CONTAINS] [IS_EMPTY] [REMOVE] [SIZE]",
+ "defaultValue": "\"ADD\"",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.nodes": {
+ "name": "camel.sink.endpoint.nodes",
+ "description": "The address of the nodes composing the cluster.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.resultHeader": {
+ "name": "camel.sink.endpoint.resultHeader",
+ "description": "The header that wil carry the result.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.transportClassName": {
+ "name": "camel.sink.endpoint.transportClassName",
+ "description": "The class name (fqn) of the Atomix transport",
+ "defaultValue": "\"io.atomix.catalyst.transport.netty.NettyTransport\"",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.lazyStartProducer": {
+ "name": "camel.sink.endpoint.lazyStartProducer",
+ "description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be 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 creating and starting the pr [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.basicPropertyBinding": {
+ "name": "camel.sink.endpoint.basicPropertyBinding",
+ "description": "Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.defaultResourceConfig": {
+ "name": "camel.sink.endpoint.defaultResourceConfig",
+ "description": "The cluster wide default resource configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.defaultResourceOptions": {
+ "name": "camel.sink.endpoint.defaultResourceOptions",
+ "description": "The local default resource options.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.ephemeral": {
+ "name": "camel.sink.endpoint.ephemeral",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.readConsistency": {
+ "name": "camel.sink.endpoint.readConsistency",
+ "description": "The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.resourceConfigs": {
+ "name": "camel.sink.endpoint.resourceConfigs",
+ "description": "Cluster wide resources configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.resourceOptions": {
+ "name": "camel.sink.endpoint.resourceOptions",
+ "description": "Local resources configurations",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.synchronous": {
+ "name": "camel.sink.endpoint.synchronous",
+ "description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-queue.atomix": {
+ "name": "camel.component.atomix-queue.atomix",
+ "description": "The Atomix instance to use",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-queue.configuration": {
+ "name": "camel.component.atomix-queue.configuration",
+ "description": "The shared component configuration",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-queue.configurationUri": {
+ "name": "camel.component.atomix-queue.configurationUri",
+ "description": "The path to the AtomixClient configuration",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-queue.defaultAction": {
+ "name": "camel.component.atomix-queue.defaultAction",
+ "description": "The default action. One of: [ADD] [OFFER] [PEEK] [POLL] [CLEAR] [CONTAINS] [IS_EMPTY] [REMOVE] [SIZE]",
+ "defaultValue": "\"ADD\"",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-queue.nodes": {
+ "name": "camel.component.atomix-queue.nodes",
+ "description": "The nodes the AtomixClient should connect to",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-queue.resultHeader": {
+ "name": "camel.component.atomix-queue.resultHeader",
+ "description": "The header that wil carry the result.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-queue.transportClassName": {
+ "name": "camel.component.atomix-queue.transportClassName",
+ "description": "The class name (fqn) of the Atomix transport",
+ "defaultValue": "\"io.atomix.catalyst.transport.netty.NettyTransport\"",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-queue.lazyStartProducer": {
+ "name": "camel.component.atomix-queue.lazyStartProducer",
+ "description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be 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 creating and starting the pr [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-queue.basicPropertyBinding": {
+ "name": "camel.component.atomix-queue.basicPropertyBinding",
+ "description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-queue.defaultResourceConfig": {
+ "name": "camel.component.atomix-queue.defaultResourceConfig",
+ "description": "The cluster wide default resource configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-queue.defaultResourceOptions": {
+ "name": "camel.component.atomix-queue.defaultResourceOptions",
+ "description": "The local default resource options.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-queue.ephemeral": {
+ "name": "camel.component.atomix-queue.ephemeral",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-queue.readConsistency": {
+ "name": "camel.component.atomix-queue.readConsistency",
+ "description": "The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-queue.resourceConfigs": {
+ "name": "camel.component.atomix-queue.resourceConfigs",
+ "description": "Cluster wide resources configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-queue.resourceOptions": {
+ "name": "camel.component.atomix-queue.resourceOptions",
+ "description": "Local resources configurations",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ }
+ }
+}
diff --git a/connectors/camel-atomix-queue-kafka-connector/src/generated/resources/camel-atomix-queue-kafka-source-connector.json b/connectors/camel-atomix-queue-kafka-connector/src/generated/resources/camel-atomix-queue-kafka-source-connector.json
new file mode 100644
index 0000000..7d91f2d
--- /dev/null
+++ b/connectors/camel-atomix-queue-kafka-connector/src/generated/resources/camel-atomix-queue-kafka-source-connector.json
@@ -0,0 +1,209 @@
+{
+ "connector": {
+ "class": "org.apache.camel.kafkaconnector.atomixqueue.CamelAtomixqueueSourceConnector",
+ "artifactId": "camel-atomix-queue",
+ "groupId": "org.apache.camel",
+ "title": "camel-atomix-queue",
+ "version": "0.6.0-SNAPSHOT"
+ },
+ "properties": {
+ "camel.source.path.resourceName": {
+ "name": "camel.source.path.resourceName",
+ "description": "The distributed resource name",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.source.endpoint.atomix": {
+ "name": "camel.source.endpoint.atomix",
+ "description": "The Atomix instance to use",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.configurationUri": {
+ "name": "camel.source.endpoint.configurationUri",
+ "description": "The Atomix configuration uri.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.defaultAction": {
+ "name": "camel.source.endpoint.defaultAction",
+ "description": "The default action. One of: [ADD] [OFFER] [PEEK] [POLL] [CLEAR] [CONTAINS] [IS_EMPTY] [REMOVE] [SIZE]",
+ "defaultValue": "\"ADD\"",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.nodes": {
+ "name": "camel.source.endpoint.nodes",
+ "description": "The address of the nodes composing the cluster.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.resultHeader": {
+ "name": "camel.source.endpoint.resultHeader",
+ "description": "The header that wil carry the result.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.transportClassName": {
+ "name": "camel.source.endpoint.transportClassName",
+ "description": "The class name (fqn) of the Atomix transport",
+ "defaultValue": "\"io.atomix.catalyst.transport.netty.NettyTransport\"",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.bridgeErrorHandler": {
+ "name": "camel.source.endpoint.bridgeErrorHandler",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.exceptionHandler": {
+ "name": "camel.source.endpoint.exceptionHandler",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.exchangePattern": {
+ "name": "camel.source.endpoint.exchangePattern",
+ "description": "Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.basicPropertyBinding": {
+ "name": "camel.source.endpoint.basicPropertyBinding",
+ "description": "Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.defaultResourceConfig": {
+ "name": "camel.source.endpoint.defaultResourceConfig",
+ "description": "The cluster wide default resource configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.defaultResourceOptions": {
+ "name": "camel.source.endpoint.defaultResourceOptions",
+ "description": "The local default resource options.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.ephemeral": {
+ "name": "camel.source.endpoint.ephemeral",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.readConsistency": {
+ "name": "camel.source.endpoint.readConsistency",
+ "description": "The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.resourceConfigs": {
+ "name": "camel.source.endpoint.resourceConfigs",
+ "description": "Cluster wide resources configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.resourceOptions": {
+ "name": "camel.source.endpoint.resourceOptions",
+ "description": "Local resources configurations",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.synchronous": {
+ "name": "camel.source.endpoint.synchronous",
+ "description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-queue.atomix": {
+ "name": "camel.component.atomix-queue.atomix",
+ "description": "The Atomix instance to use",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-queue.configuration": {
+ "name": "camel.component.atomix-queue.configuration",
+ "description": "The shared component configuration",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-queue.configurationUri": {
+ "name": "camel.component.atomix-queue.configurationUri",
+ "description": "The path to the AtomixClient configuration",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-queue.defaultAction": {
+ "name": "camel.component.atomix-queue.defaultAction",
+ "description": "The default action. One of: [ADD] [OFFER] [PEEK] [POLL] [CLEAR] [CONTAINS] [IS_EMPTY] [REMOVE] [SIZE]",
+ "defaultValue": "\"ADD\"",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-queue.nodes": {
+ "name": "camel.component.atomix-queue.nodes",
+ "description": "The nodes the AtomixClient should connect to",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-queue.resultHeader": {
+ "name": "camel.component.atomix-queue.resultHeader",
+ "description": "The header that wil carry the result.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-queue.transportClassName": {
+ "name": "camel.component.atomix-queue.transportClassName",
+ "description": "The class name (fqn) of the Atomix transport",
+ "defaultValue": "\"io.atomix.catalyst.transport.netty.NettyTransport\"",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-queue.bridgeErrorHandler": {
+ "name": "camel.component.atomix-queue.bridgeErrorHandler",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-queue.basicPropertyBinding": {
+ "name": "camel.component.atomix-queue.basicPropertyBinding",
+ "description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-queue.defaultResourceConfig": {
+ "name": "camel.component.atomix-queue.defaultResourceConfig",
+ "description": "The cluster wide default resource configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-queue.defaultResourceOptions": {
+ "name": "camel.component.atomix-queue.defaultResourceOptions",
+ "description": "The local default resource options.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-queue.ephemeral": {
+ "name": "camel.component.atomix-queue.ephemeral",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-queue.readConsistency": {
+ "name": "camel.component.atomix-queue.readConsistency",
+ "description": "The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-queue.resourceConfigs": {
+ "name": "camel.component.atomix-queue.resourceConfigs",
+ "description": "Cluster wide resources configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-queue.resourceOptions": {
+ "name": "camel.component.atomix-queue.resourceOptions",
+ "description": "Local resources configurations",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ }
+ }
+}
diff --git a/connectors/camel-atomix-set-kafka-connector/src/generated/resources/camel-atomix-set-kafka-sink-connector.json b/connectors/camel-atomix-set-kafka-connector/src/generated/resources/camel-atomix-set-kafka-sink-connector.json
new file mode 100644
index 0000000..2458e89
--- /dev/null
+++ b/connectors/camel-atomix-set-kafka-connector/src/generated/resources/camel-atomix-set-kafka-sink-connector.json
@@ -0,0 +1,209 @@
+{
+ "connector": {
+ "class": "org.apache.camel.kafkaconnector.atomixset.CamelAtomixsetSinkConnector",
+ "artifactId": "camel-atomix-set",
+ "groupId": "org.apache.camel",
+ "title": "camel-atomix-set",
+ "version": "0.6.0-SNAPSHOT"
+ },
+ "properties": {
+ "camel.sink.path.resourceName": {
+ "name": "camel.sink.path.resourceName",
+ "description": "The distributed resource name",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.sink.endpoint.atomix": {
+ "name": "camel.sink.endpoint.atomix",
+ "description": "The Atomix instance to use",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.configurationUri": {
+ "name": "camel.sink.endpoint.configurationUri",
+ "description": "The Atomix configuration uri.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.defaultAction": {
+ "name": "camel.sink.endpoint.defaultAction",
+ "description": "The default action. One of: [ADD] [CLEAR] [CONTAINS] [IS_EMPTY] [REMOVE] [SIZE]",
+ "defaultValue": "\"ADD\"",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.nodes": {
+ "name": "camel.sink.endpoint.nodes",
+ "description": "The address of the nodes composing the cluster.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.resultHeader": {
+ "name": "camel.sink.endpoint.resultHeader",
+ "description": "The header that wil carry the result.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.transportClassName": {
+ "name": "camel.sink.endpoint.transportClassName",
+ "description": "The class name (fqn) of the Atomix transport",
+ "defaultValue": "\"io.atomix.catalyst.transport.netty.NettyTransport\"",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.ttl": {
+ "name": "camel.sink.endpoint.ttl",
+ "description": "The resource ttl.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.lazyStartProducer": {
+ "name": "camel.sink.endpoint.lazyStartProducer",
+ "description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be 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 creating and starting the pr [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.basicPropertyBinding": {
+ "name": "camel.sink.endpoint.basicPropertyBinding",
+ "description": "Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.defaultResourceConfig": {
+ "name": "camel.sink.endpoint.defaultResourceConfig",
+ "description": "The cluster wide default resource configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.defaultResourceOptions": {
+ "name": "camel.sink.endpoint.defaultResourceOptions",
+ "description": "The local default resource options.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.ephemeral": {
+ "name": "camel.sink.endpoint.ephemeral",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.readConsistency": {
+ "name": "camel.sink.endpoint.readConsistency",
+ "description": "The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.resourceConfigs": {
+ "name": "camel.sink.endpoint.resourceConfigs",
+ "description": "Cluster wide resources configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.resourceOptions": {
+ "name": "camel.sink.endpoint.resourceOptions",
+ "description": "Local resources configurations",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.synchronous": {
+ "name": "camel.sink.endpoint.synchronous",
+ "description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-set.atomix": {
+ "name": "camel.component.atomix-set.atomix",
+ "description": "The Atomix instance to use",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-set.configuration": {
+ "name": "camel.component.atomix-set.configuration",
+ "description": "The shared component configuration",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-set.configurationUri": {
+ "name": "camel.component.atomix-set.configurationUri",
+ "description": "The path to the AtomixClient configuration",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-set.defaultAction": {
+ "name": "camel.component.atomix-set.defaultAction",
+ "description": "The default action. One of: [ADD] [CLEAR] [CONTAINS] [IS_EMPTY] [REMOVE] [SIZE]",
+ "defaultValue": "\"ADD\"",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-set.nodes": {
+ "name": "camel.component.atomix-set.nodes",
+ "description": "The nodes the AtomixClient should connect to",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-set.resultHeader": {
+ "name": "camel.component.atomix-set.resultHeader",
+ "description": "The header that wil carry the result.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-set.transportClassName": {
+ "name": "camel.component.atomix-set.transportClassName",
+ "description": "The class name (fqn) of the Atomix transport",
+ "defaultValue": "\"io.atomix.catalyst.transport.netty.NettyTransport\"",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-set.ttl": {
+ "name": "camel.component.atomix-set.ttl",
+ "description": "The resource ttl.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-set.lazyStartProducer": {
+ "name": "camel.component.atomix-set.lazyStartProducer",
+ "description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be 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 creating and starting the pr [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-set.basicPropertyBinding": {
+ "name": "camel.component.atomix-set.basicPropertyBinding",
+ "description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-set.defaultResourceConfig": {
+ "name": "camel.component.atomix-set.defaultResourceConfig",
+ "description": "The cluster wide default resource configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-set.defaultResourceOptions": {
+ "name": "camel.component.atomix-set.defaultResourceOptions",
+ "description": "The local default resource options.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-set.ephemeral": {
+ "name": "camel.component.atomix-set.ephemeral",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-set.readConsistency": {
+ "name": "camel.component.atomix-set.readConsistency",
+ "description": "The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-set.resourceConfigs": {
+ "name": "camel.component.atomix-set.resourceConfigs",
+ "description": "Cluster wide resources configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-set.resourceOptions": {
+ "name": "camel.component.atomix-set.resourceOptions",
+ "description": "Local resources configurations",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ }
+ }
+}
diff --git a/connectors/camel-atomix-set-kafka-connector/src/generated/resources/camel-atomix-set-kafka-source-connector.json b/connectors/camel-atomix-set-kafka-connector/src/generated/resources/camel-atomix-set-kafka-source-connector.json
new file mode 100644
index 0000000..402d2d9
--- /dev/null
+++ b/connectors/camel-atomix-set-kafka-connector/src/generated/resources/camel-atomix-set-kafka-source-connector.json
@@ -0,0 +1,221 @@
+{
+ "connector": {
+ "class": "org.apache.camel.kafkaconnector.atomixset.CamelAtomixsetSourceConnector",
+ "artifactId": "camel-atomix-set",
+ "groupId": "org.apache.camel",
+ "title": "camel-atomix-set",
+ "version": "0.6.0-SNAPSHOT"
+ },
+ "properties": {
+ "camel.source.path.resourceName": {
+ "name": "camel.source.path.resourceName",
+ "description": "The distributed resource name",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.source.endpoint.atomix": {
+ "name": "camel.source.endpoint.atomix",
+ "description": "The Atomix instance to use",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.configurationUri": {
+ "name": "camel.source.endpoint.configurationUri",
+ "description": "The Atomix configuration uri.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.defaultAction": {
+ "name": "camel.source.endpoint.defaultAction",
+ "description": "The default action. One of: [ADD] [CLEAR] [CONTAINS] [IS_EMPTY] [REMOVE] [SIZE]",
+ "defaultValue": "\"ADD\"",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.nodes": {
+ "name": "camel.source.endpoint.nodes",
+ "description": "The address of the nodes composing the cluster.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.resultHeader": {
+ "name": "camel.source.endpoint.resultHeader",
+ "description": "The header that wil carry the result.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.transportClassName": {
+ "name": "camel.source.endpoint.transportClassName",
+ "description": "The class name (fqn) of the Atomix transport",
+ "defaultValue": "\"io.atomix.catalyst.transport.netty.NettyTransport\"",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.ttl": {
+ "name": "camel.source.endpoint.ttl",
+ "description": "The resource ttl.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.bridgeErrorHandler": {
+ "name": "camel.source.endpoint.bridgeErrorHandler",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.exceptionHandler": {
+ "name": "camel.source.endpoint.exceptionHandler",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.exchangePattern": {
+ "name": "camel.source.endpoint.exchangePattern",
+ "description": "Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.basicPropertyBinding": {
+ "name": "camel.source.endpoint.basicPropertyBinding",
+ "description": "Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.defaultResourceConfig": {
+ "name": "camel.source.endpoint.defaultResourceConfig",
+ "description": "The cluster wide default resource configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.defaultResourceOptions": {
+ "name": "camel.source.endpoint.defaultResourceOptions",
+ "description": "The local default resource options.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.ephemeral": {
+ "name": "camel.source.endpoint.ephemeral",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.readConsistency": {
+ "name": "camel.source.endpoint.readConsistency",
+ "description": "The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.resourceConfigs": {
+ "name": "camel.source.endpoint.resourceConfigs",
+ "description": "Cluster wide resources configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.resourceOptions": {
+ "name": "camel.source.endpoint.resourceOptions",
+ "description": "Local resources configurations",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.synchronous": {
+ "name": "camel.source.endpoint.synchronous",
+ "description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-set.atomix": {
+ "name": "camel.component.atomix-set.atomix",
+ "description": "The Atomix instance to use",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-set.configuration": {
+ "name": "camel.component.atomix-set.configuration",
+ "description": "The shared component configuration",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-set.configurationUri": {
+ "name": "camel.component.atomix-set.configurationUri",
+ "description": "The path to the AtomixClient configuration",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-set.defaultAction": {
+ "name": "camel.component.atomix-set.defaultAction",
+ "description": "The default action. One of: [ADD] [CLEAR] [CONTAINS] [IS_EMPTY] [REMOVE] [SIZE]",
+ "defaultValue": "\"ADD\"",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-set.nodes": {
+ "name": "camel.component.atomix-set.nodes",
+ "description": "The nodes the AtomixClient should connect to",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-set.resultHeader": {
+ "name": "camel.component.atomix-set.resultHeader",
+ "description": "The header that wil carry the result.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-set.transportClassName": {
+ "name": "camel.component.atomix-set.transportClassName",
+ "description": "The class name (fqn) of the Atomix transport",
+ "defaultValue": "\"io.atomix.catalyst.transport.netty.NettyTransport\"",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-set.ttl": {
+ "name": "camel.component.atomix-set.ttl",
+ "description": "The resource ttl.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-set.bridgeErrorHandler": {
+ "name": "camel.component.atomix-set.bridgeErrorHandler",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-set.basicPropertyBinding": {
+ "name": "camel.component.atomix-set.basicPropertyBinding",
+ "description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-set.defaultResourceConfig": {
+ "name": "camel.component.atomix-set.defaultResourceConfig",
+ "description": "The cluster wide default resource configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-set.defaultResourceOptions": {
+ "name": "camel.component.atomix-set.defaultResourceOptions",
+ "description": "The local default resource options.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-set.ephemeral": {
+ "name": "camel.component.atomix-set.ephemeral",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-set.readConsistency": {
+ "name": "camel.component.atomix-set.readConsistency",
+ "description": "The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-set.resourceConfigs": {
+ "name": "camel.component.atomix-set.resourceConfigs",
+ "description": "Cluster wide resources configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-set.resourceOptions": {
+ "name": "camel.component.atomix-set.resourceOptions",
+ "description": "Local resources configurations",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ }
+ }
+}
diff --git a/connectors/camel-atomix-value-kafka-connector/src/generated/resources/camel-atomix-value-kafka-sink-connector.json b/connectors/camel-atomix-value-kafka-connector/src/generated/resources/camel-atomix-value-kafka-sink-connector.json
new file mode 100644
index 0000000..a185403
--- /dev/null
+++ b/connectors/camel-atomix-value-kafka-connector/src/generated/resources/camel-atomix-value-kafka-sink-connector.json
@@ -0,0 +1,209 @@
+{
+ "connector": {
+ "class": "org.apache.camel.kafkaconnector.atomixvalue.CamelAtomixvalueSinkConnector",
+ "artifactId": "camel-atomix-value",
+ "groupId": "org.apache.camel",
+ "title": "camel-atomix-value",
+ "version": "0.6.0-SNAPSHOT"
+ },
+ "properties": {
+ "camel.sink.path.resourceName": {
+ "name": "camel.sink.path.resourceName",
+ "description": "The distributed resource name",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.sink.endpoint.atomix": {
+ "name": "camel.sink.endpoint.atomix",
+ "description": "The Atomix instance to use",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.configurationUri": {
+ "name": "camel.sink.endpoint.configurationUri",
+ "description": "The Atomix configuration uri.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.defaultAction": {
+ "name": "camel.sink.endpoint.defaultAction",
+ "description": "The default action. One of: [SET] [GET] [GET_AND_SET] [COMPARE_AND_SET]",
+ "defaultValue": "\"SET\"",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.nodes": {
+ "name": "camel.sink.endpoint.nodes",
+ "description": "The address of the nodes composing the cluster.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.resultHeader": {
+ "name": "camel.sink.endpoint.resultHeader",
+ "description": "The header that wil carry the result.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.transportClassName": {
+ "name": "camel.sink.endpoint.transportClassName",
+ "description": "The class name (fqn) of the Atomix transport",
+ "defaultValue": "\"io.atomix.catalyst.transport.netty.NettyTransport\"",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.ttl": {
+ "name": "camel.sink.endpoint.ttl",
+ "description": "The resource ttl.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.lazyStartProducer": {
+ "name": "camel.sink.endpoint.lazyStartProducer",
+ "description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be 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 creating and starting the pr [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.basicPropertyBinding": {
+ "name": "camel.sink.endpoint.basicPropertyBinding",
+ "description": "Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.defaultResourceConfig": {
+ "name": "camel.sink.endpoint.defaultResourceConfig",
+ "description": "The cluster wide default resource configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.defaultResourceOptions": {
+ "name": "camel.sink.endpoint.defaultResourceOptions",
+ "description": "The local default resource options.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.ephemeral": {
+ "name": "camel.sink.endpoint.ephemeral",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.readConsistency": {
+ "name": "camel.sink.endpoint.readConsistency",
+ "description": "The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.resourceConfigs": {
+ "name": "camel.sink.endpoint.resourceConfigs",
+ "description": "Cluster wide resources configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.resourceOptions": {
+ "name": "camel.sink.endpoint.resourceOptions",
+ "description": "Local resources configurations",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.synchronous": {
+ "name": "camel.sink.endpoint.synchronous",
+ "description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-value.atomix": {
+ "name": "camel.component.atomix-value.atomix",
+ "description": "The Atomix instance to use",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-value.configuration": {
+ "name": "camel.component.atomix-value.configuration",
+ "description": "The shared component configuration",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-value.configurationUri": {
+ "name": "camel.component.atomix-value.configurationUri",
+ "description": "The path to the AtomixClient configuration",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-value.defaultAction": {
+ "name": "camel.component.atomix-value.defaultAction",
+ "description": "The default action. One of: [SET] [GET] [GET_AND_SET] [COMPARE_AND_SET]",
+ "defaultValue": "\"SET\"",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-value.nodes": {
+ "name": "camel.component.atomix-value.nodes",
+ "description": "The nodes the AtomixClient should connect to",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-value.resultHeader": {
+ "name": "camel.component.atomix-value.resultHeader",
+ "description": "The header that wil carry the result.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-value.transportClassName": {
+ "name": "camel.component.atomix-value.transportClassName",
+ "description": "The class name (fqn) of the Atomix transport",
+ "defaultValue": "\"io.atomix.catalyst.transport.netty.NettyTransport\"",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-value.ttl": {
+ "name": "camel.component.atomix-value.ttl",
+ "description": "The resource ttl.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-value.lazyStartProducer": {
+ "name": "camel.component.atomix-value.lazyStartProducer",
+ "description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be 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 creating and starting the pr [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-value.basicPropertyBinding": {
+ "name": "camel.component.atomix-value.basicPropertyBinding",
+ "description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-value.defaultResourceConfig": {
+ "name": "camel.component.atomix-value.defaultResourceConfig",
+ "description": "The cluster wide default resource configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-value.defaultResourceOptions": {
+ "name": "camel.component.atomix-value.defaultResourceOptions",
+ "description": "The local default resource options.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-value.ephemeral": {
+ "name": "camel.component.atomix-value.ephemeral",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-value.readConsistency": {
+ "name": "camel.component.atomix-value.readConsistency",
+ "description": "The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-value.resourceConfigs": {
+ "name": "camel.component.atomix-value.resourceConfigs",
+ "description": "Cluster wide resources configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-value.resourceOptions": {
+ "name": "camel.component.atomix-value.resourceOptions",
+ "description": "Local resources configurations",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ }
+ }
+}
diff --git a/connectors/camel-atomix-value-kafka-connector/src/generated/resources/camel-atomix-value-kafka-source-connector.json b/connectors/camel-atomix-value-kafka-connector/src/generated/resources/camel-atomix-value-kafka-source-connector.json
new file mode 100644
index 0000000..a2c2e94
--- /dev/null
+++ b/connectors/camel-atomix-value-kafka-connector/src/generated/resources/camel-atomix-value-kafka-source-connector.json
@@ -0,0 +1,221 @@
+{
+ "connector": {
+ "class": "org.apache.camel.kafkaconnector.atomixvalue.CamelAtomixvalueSourceConnector",
+ "artifactId": "camel-atomix-value",
+ "groupId": "org.apache.camel",
+ "title": "camel-atomix-value",
+ "version": "0.6.0-SNAPSHOT"
+ },
+ "properties": {
+ "camel.source.path.resourceName": {
+ "name": "camel.source.path.resourceName",
+ "description": "The distributed resource name",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.source.endpoint.atomix": {
+ "name": "camel.source.endpoint.atomix",
+ "description": "The Atomix instance to use",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.configurationUri": {
+ "name": "camel.source.endpoint.configurationUri",
+ "description": "The Atomix configuration uri.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.defaultAction": {
+ "name": "camel.source.endpoint.defaultAction",
+ "description": "The default action. One of: [SET] [GET] [GET_AND_SET] [COMPARE_AND_SET]",
+ "defaultValue": "\"SET\"",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.nodes": {
+ "name": "camel.source.endpoint.nodes",
+ "description": "The address of the nodes composing the cluster.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.resultHeader": {
+ "name": "camel.source.endpoint.resultHeader",
+ "description": "The header that wil carry the result.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.transportClassName": {
+ "name": "camel.source.endpoint.transportClassName",
+ "description": "The class name (fqn) of the Atomix transport",
+ "defaultValue": "\"io.atomix.catalyst.transport.netty.NettyTransport\"",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.ttl": {
+ "name": "camel.source.endpoint.ttl",
+ "description": "The resource ttl.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.bridgeErrorHandler": {
+ "name": "camel.source.endpoint.bridgeErrorHandler",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.exceptionHandler": {
+ "name": "camel.source.endpoint.exceptionHandler",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.exchangePattern": {
+ "name": "camel.source.endpoint.exchangePattern",
+ "description": "Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.basicPropertyBinding": {
+ "name": "camel.source.endpoint.basicPropertyBinding",
+ "description": "Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.defaultResourceConfig": {
+ "name": "camel.source.endpoint.defaultResourceConfig",
+ "description": "The cluster wide default resource configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.defaultResourceOptions": {
+ "name": "camel.source.endpoint.defaultResourceOptions",
+ "description": "The local default resource options.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.ephemeral": {
+ "name": "camel.source.endpoint.ephemeral",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.readConsistency": {
+ "name": "camel.source.endpoint.readConsistency",
+ "description": "The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.resourceConfigs": {
+ "name": "camel.source.endpoint.resourceConfigs",
+ "description": "Cluster wide resources configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.resourceOptions": {
+ "name": "camel.source.endpoint.resourceOptions",
+ "description": "Local resources configurations",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.synchronous": {
+ "name": "camel.source.endpoint.synchronous",
+ "description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-value.atomix": {
+ "name": "camel.component.atomix-value.atomix",
+ "description": "The Atomix instance to use",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-value.configuration": {
+ "name": "camel.component.atomix-value.configuration",
+ "description": "The shared component configuration",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-value.configurationUri": {
+ "name": "camel.component.atomix-value.configurationUri",
+ "description": "The path to the AtomixClient configuration",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-value.defaultAction": {
+ "name": "camel.component.atomix-value.defaultAction",
+ "description": "The default action. One of: [SET] [GET] [GET_AND_SET] [COMPARE_AND_SET]",
+ "defaultValue": "\"SET\"",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-value.nodes": {
+ "name": "camel.component.atomix-value.nodes",
+ "description": "The nodes the AtomixClient should connect to",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-value.resultHeader": {
+ "name": "camel.component.atomix-value.resultHeader",
+ "description": "The header that wil carry the result.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-value.transportClassName": {
+ "name": "camel.component.atomix-value.transportClassName",
+ "description": "The class name (fqn) of the Atomix transport",
+ "defaultValue": "\"io.atomix.catalyst.transport.netty.NettyTransport\"",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-value.ttl": {
+ "name": "camel.component.atomix-value.ttl",
+ "description": "The resource ttl.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-value.bridgeErrorHandler": {
+ "name": "camel.component.atomix-value.bridgeErrorHandler",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-value.basicPropertyBinding": {
+ "name": "camel.component.atomix-value.basicPropertyBinding",
+ "description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-value.defaultResourceConfig": {
+ "name": "camel.component.atomix-value.defaultResourceConfig",
+ "description": "The cluster wide default resource configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-value.defaultResourceOptions": {
+ "name": "camel.component.atomix-value.defaultResourceOptions",
+ "description": "The local default resource options.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-value.ephemeral": {
+ "name": "camel.component.atomix-value.ephemeral",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-value.readConsistency": {
+ "name": "camel.component.atomix-value.readConsistency",
+ "description": "The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-value.resourceConfigs": {
+ "name": "camel.component.atomix-value.resourceConfigs",
+ "description": "Cluster wide resources configuration.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.atomix-value.resourceOptions": {
+ "name": "camel.component.atomix-value.resourceOptions",
+ "description": "Local resources configurations",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ }
+ }
+}
diff --git a/connectors/camel-avro-kafka-connector/src/generated/resources/camel-avro-kafka-sink-connector.json b/connectors/camel-avro-kafka-connector/src/generated/resources/camel-avro-kafka-sink-connector.json
new file mode 100644
index 0000000..abb1230
--- /dev/null
+++ b/connectors/camel-avro-kafka-connector/src/generated/resources/camel-avro-kafka-sink-connector.json
@@ -0,0 +1,143 @@
+{
+ "connector": {
+ "class": "org.apache.camel.kafkaconnector.avro.CamelAvroSinkConnector",
+ "artifactId": "camel-avro",
+ "groupId": "org.apache.camel",
+ "title": "camel-avro",
+ "version": "0.6.0-SNAPSHOT"
+ },
+ "properties": {
+ "camel.sink.path.transport": {
+ "name": "camel.sink.path.transport",
+ "description": "Transport to use, can be either http or netty One of: [http] [netty]",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.sink.path.port": {
+ "name": "camel.sink.path.port",
+ "description": "Port number to use",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.sink.path.host": {
+ "name": "camel.sink.path.host",
+ "description": "Hostname to use",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.sink.path.messageName": {
+ "name": "camel.sink.path.messageName",
+ "description": "The name of the message to send.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.protocol": {
+ "name": "camel.sink.endpoint.protocol",
+ "description": "Avro protocol to use",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.protocolClassName": {
+ "name": "camel.sink.endpoint.protocolClassName",
+ "description": "Avro protocol to use defined by the FQN class name",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.protocolLocation": {
+ "name": "camel.sink.endpoint.protocolLocation",
+ "description": "Avro protocol location",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.reflectionProtocol": {
+ "name": "camel.sink.endpoint.reflectionProtocol",
+ "description": "If protocol object provided is reflection protocol. Should be used only with protocol parameter because for protocolClassName protocol type will be auto detected",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.singleParameter": {
+ "name": "camel.sink.endpoint.singleParameter",
+ "description": "If true, consumer parameter won't be wrapped into array. Will fail if protocol specifies more then 1 parameter for the message",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.uriAuthority": {
+ "name": "camel.sink.endpoint.uriAuthority",
+ "description": "Authority to use (username and password)",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.lazyStartProducer": {
+ "name": "camel.sink.endpoint.lazyStartProducer",
+ "description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be 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 creating and starting the pr [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.basicPropertyBinding": {
+ "name": "camel.sink.endpoint.basicPropertyBinding",
+ "description": "Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.synchronous": {
+ "name": "camel.sink.endpoint.synchronous",
+ "description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.avro.protocol": {
+ "name": "camel.component.avro.protocol",
+ "description": "Avro protocol to use",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.avro.protocolClassName": {
+ "name": "camel.component.avro.protocolClassName",
+ "description": "Avro protocol to use defined by the FQN class name",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.avro.protocolLocation": {
+ "name": "camel.component.avro.protocolLocation",
+ "description": "Avro protocol location",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.avro.reflectionProtocol": {
+ "name": "camel.component.avro.reflectionProtocol",
+ "description": "If protocol object provided is reflection protocol. Should be used only with protocol parameter because for protocolClassName protocol type will be auto detected",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.avro.singleParameter": {
+ "name": "camel.component.avro.singleParameter",
+ "description": "If true, consumer parameter won't be wrapped into array. Will fail if protocol specifies more then 1 parameter for the message",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.avro.uriAuthority": {
+ "name": "camel.component.avro.uriAuthority",
+ "description": "Authority to use (username and password)",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.avro.lazyStartProducer": {
+ "name": "camel.component.avro.lazyStartProducer",
+ "description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be 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 creating and starting the pr [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.avro.basicPropertyBinding": {
+ "name": "camel.component.avro.basicPropertyBinding",
+ "description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.avro.configuration": {
+ "name": "camel.component.avro.configuration",
+ "description": "To use a shared AvroConfiguration to configure options once",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ }
+ }
+}
diff --git a/connectors/camel-avro-kafka-connector/src/generated/resources/camel-avro-kafka-source-connector.json b/connectors/camel-avro-kafka-connector/src/generated/resources/camel-avro-kafka-source-connector.json
new file mode 100644
index 0000000..c5bad4a
--- /dev/null
+++ b/connectors/camel-avro-kafka-connector/src/generated/resources/camel-avro-kafka-source-connector.json
@@ -0,0 +1,155 @@
+{
+ "connector": {
+ "class": "org.apache.camel.kafkaconnector.avro.CamelAvroSourceConnector",
+ "artifactId": "camel-avro",
+ "groupId": "org.apache.camel",
+ "title": "camel-avro",
+ "version": "0.6.0-SNAPSHOT"
+ },
+ "properties": {
+ "camel.source.path.transport": {
+ "name": "camel.source.path.transport",
+ "description": "Transport to use, can be either http or netty One of: [http] [netty]",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.source.path.port": {
+ "name": "camel.source.path.port",
+ "description": "Port number to use",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.source.path.host": {
+ "name": "camel.source.path.host",
+ "description": "Hostname to use",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.source.path.messageName": {
+ "name": "camel.source.path.messageName",
+ "description": "The name of the message to send.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.protocol": {
+ "name": "camel.source.endpoint.protocol",
+ "description": "Avro protocol to use",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.protocolClassName": {
+ "name": "camel.source.endpoint.protocolClassName",
+ "description": "Avro protocol to use defined by the FQN class name",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.protocolLocation": {
+ "name": "camel.source.endpoint.protocolLocation",
+ "description": "Avro protocol location",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.reflectionProtocol": {
+ "name": "camel.source.endpoint.reflectionProtocol",
+ "description": "If protocol object provided is reflection protocol. Should be used only with protocol parameter because for protocolClassName protocol type will be auto detected",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.singleParameter": {
+ "name": "camel.source.endpoint.singleParameter",
+ "description": "If true, consumer parameter won't be wrapped into array. Will fail if protocol specifies more then 1 parameter for the message",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.uriAuthority": {
+ "name": "camel.source.endpoint.uriAuthority",
+ "description": "Authority to use (username and password)",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.bridgeErrorHandler": {
+ "name": "camel.source.endpoint.bridgeErrorHandler",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.exceptionHandler": {
+ "name": "camel.source.endpoint.exceptionHandler",
+ "description": "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.",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.exchangePattern": {
+ "name": "camel.source.endpoint.exchangePattern",
+ "description": "Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut]",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.basicPropertyBinding": {
+ "name": "camel.source.endpoint.basicPropertyBinding",
+ "description": "Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.source.endpoint.synchronous": {
+ "name": "camel.source.endpoint.synchronous",
+ "description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.avro.protocol": {
+ "name": "camel.component.avro.protocol",
+ "description": "Avro protocol to use",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.avro.protocolClassName": {
+ "name": "camel.component.avro.protocolClassName",
+ "description": "Avro protocol to use defined by the FQN class name",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.avro.protocolLocation": {
+ "name": "camel.component.avro.protocolLocation",
+ "description": "Avro protocol location",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.avro.reflectionProtocol": {
+ "name": "camel.component.avro.reflectionProtocol",
+ "description": "If protocol object provided is reflection protocol. Should be used only with protocol parameter because for protocolClassName protocol type will be auto detected",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.avro.singleParameter": {
+ "name": "camel.component.avro.singleParameter",
+ "description": "If true, consumer parameter won't be wrapped into array. Will fail if protocol specifies more then 1 parameter for the message",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.avro.uriAuthority": {
+ "name": "camel.component.avro.uriAuthority",
+ "description": "Authority to use (username and password)",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.avro.bridgeErrorHandler": {
+ "name": "camel.component.avro.bridgeErrorHandler",
+ "description": "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.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.avro.basicPropertyBinding": {
+ "name": "camel.component.avro.basicPropertyBinding",
+ "description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.avro.configuration": {
+ "name": "camel.component.avro.configuration",
+ "description": "To use a shared AvroConfiguration to configure options once",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ }
+ }
+}
diff --git a/connectors/camel-aws-cw-kafka-connector/src/generated/resources/camel-aws-cw-kafka-sink-connector.json b/connectors/camel-aws-cw-kafka-connector/src/generated/resources/camel-aws-cw-kafka-sink-connector.json
new file mode 100644
index 0000000..292b27b
--- /dev/null
+++ b/connectors/camel-aws-cw-kafka-connector/src/generated/resources/camel-aws-cw-kafka-sink-connector.json
@@ -0,0 +1,197 @@
+{
+ "connector": {
+ "class": "org.apache.camel.kafkaconnector.awscw.CamelAwscwSinkConnector",
+ "artifactId": "camel-aws-cw",
+ "groupId": "org.apache.camel",
+ "title": "camel-aws-cw",
+ "version": "0.6.0-SNAPSHOT"
+ },
+ "properties": {
+ "camel.sink.path.namespace": {
+ "name": "camel.sink.path.namespace",
+ "description": "The metric namespace",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.sink.endpoint.amazonCwClient": {
+ "name": "camel.sink.endpoint.amazonCwClient",
+ "description": "To use the AmazonCloudWatch as the client",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.autoDiscoverClient": {
+ "name": "camel.sink.endpoint.autoDiscoverClient",
+ "description": "Setting the autoDiscoverClient mechanism, if true, the component will look for a client instance in the registry automatically otherwise it will skip that checking.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.lazyStartProducer": {
+ "name": "camel.sink.endpoint.lazyStartProducer",
+ "description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be 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 creating and starting the pr [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.name": {
+ "name": "camel.sink.endpoint.name",
+ "description": "The metric name",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.proxyHost": {
+ "name": "camel.sink.endpoint.proxyHost",
+ "description": "To define a proxy host when instantiating the CW client",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.proxyPort": {
+ "name": "camel.sink.endpoint.proxyPort",
+ "description": "To define a proxy port when instantiating the CW client",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.proxyProtocol": {
+ "name": "camel.sink.endpoint.proxyProtocol",
+ "description": "To define a proxy protocol when instantiating the CW client One of: [HTTP] [HTTPS]",
+ "defaultValue": "\"HTTPS\"",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.region": {
+ "name": "camel.sink.endpoint.region",
+ "description": "The region in which CW client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name()",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.timestamp": {
+ "name": "camel.sink.endpoint.timestamp",
+ "description": "The metric timestamp",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.unit": {
+ "name": "camel.sink.endpoint.unit",
+ "description": "The metric unit",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.value": {
+ "name": "camel.sink.endpoint.value",
+ "description": "The metric value",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.basicPropertyBinding": {
+ "name": "camel.sink.endpoint.basicPropertyBinding",
+ "description": "Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.synchronous": {
+ "name": "camel.sink.endpoint.synchronous",
+ "description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.accessKey": {
+ "name": "camel.sink.endpoint.accessKey",
+ "description": "Amazon AWS Access Key",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.secretKey": {
+ "name": "camel.sink.endpoint.secretKey",
+ "description": "Amazon AWS Secret Key",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.aws-cw.amazonCwClient": {
+ "name": "camel.component.aws-cw.amazonCwClient",
+ "description": "To use the AmazonCloudWatch as the client",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.aws-cw.autoDiscoverClient": {
+ "name": "camel.component.aws-cw.autoDiscoverClient",
+ "description": "Setting the autoDiscoverClient mechanism, if true, the component will look for a client instance in the registry automatically otherwise it will skip that checking.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.component.aws-cw.configuration": {
+ "name": "camel.component.aws-cw.configuration",
+ "description": "The component configuration",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.aws-cw.lazyStartProducer": {
+ "name": "camel.component.aws-cw.lazyStartProducer",
+ "description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be 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 creating and starting the pr [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.aws-cw.name": {
+ "name": "camel.component.aws-cw.name",
+ "description": "The metric name",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.aws-cw.proxyHost": {
+ "name": "camel.component.aws-cw.proxyHost",
+ "description": "To define a proxy host when instantiating the CW client",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.aws-cw.proxyPort": {
+ "name": "camel.component.aws-cw.proxyPort",
+ "description": "To define a proxy port when instantiating the CW client",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.aws-cw.proxyProtocol": {
+ "name": "camel.component.aws-cw.proxyProtocol",
+ "description": "To define a proxy protocol when instantiating the CW client One of: [HTTP] [HTTPS]",
+ "defaultValue": "\"HTTPS\"",
+ "priority": "MEDIUM"
+ },
+ "camel.component.aws-cw.region": {
+ "name": "camel.component.aws-cw.region",
+ "description": "The region in which CW client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name()",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.aws-cw.timestamp": {
+ "name": "camel.component.aws-cw.timestamp",
+ "description": "The metric timestamp",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.aws-cw.unit": {
+ "name": "camel.component.aws-cw.unit",
+ "description": "The metric unit",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.aws-cw.value": {
+ "name": "camel.component.aws-cw.value",
+ "description": "The metric value",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.aws-cw.basicPropertyBinding": {
+ "name": "camel.component.aws-cw.basicPropertyBinding",
+ "description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.component.aws-cw.accessKey": {
+ "name": "camel.component.aws-cw.accessKey",
+ "description": "Amazon AWS Access Key",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.component.aws-cw.secretKey": {
+ "name": "camel.component.aws-cw.secretKey",
+ "description": "Amazon AWS Secret Key",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ }
+ }
+}
diff --git a/connectors/camel-aws-ddb-kafka-connector/src/generated/resources/camel-aws-ddb-kafka-sink-connector.json b/connectors/camel-aws-ddb-kafka-connector/src/generated/resources/camel-aws-ddb-kafka-sink-connector.json
new file mode 100644
index 0000000..faa2874
--- /dev/null
+++ b/connectors/camel-aws-ddb-kafka-connector/src/generated/resources/camel-aws-ddb-kafka-sink-connector.json
@@ -0,0 +1,221 @@
+{
+ "connector": {
+ "class": "org.apache.camel.kafkaconnector.awsddb.CamelAwsddbSinkConnector",
+ "artifactId": "camel-aws-ddb",
+ "groupId": "org.apache.camel",
+ "title": "camel-aws-ddb",
+ "version": "0.6.0-SNAPSHOT"
+ },
+ "properties": {
+ "camel.sink.path.tableName": {
+ "name": "camel.sink.path.tableName",
+ "description": "The name of the table currently worked with.",
+ "defaultValue": "null",
+ "priority": "HIGH"
+ },
+ "camel.sink.endpoint.amazonDDBClient": {
+ "name": "camel.sink.endpoint.amazonDDBClient",
+ "description": "To use the AmazonDynamoDB as the client",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.autoDiscoverClient": {
+ "name": "camel.sink.endpoint.autoDiscoverClient",
+ "description": "Setting the autoDiscoverClient mechanism, if true, the component will look for a client instance in the registry automatically otherwise it will skip that checking.",
+ "defaultValue": "true",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.consistentRead": {
+ "name": "camel.sink.endpoint.consistentRead",
+ "description": "Determines whether or not strong consistency should be enforced when data is read.",
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.keyAttributeName": {
+ "name": "camel.sink.endpoint.keyAttributeName",
+ "description": "Attribute name when creating table",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.keyAttributeType": {
+ "name": "camel.sink.endpoint.keyAttributeType",
+ "description": "Attribute type when creating table",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.lazyStartProducer": {
+ "name": "camel.sink.endpoint.lazyStartProducer",
+ "description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be 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 creating and starting the pr [...]
+ "defaultValue": "false",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.operation": {
+ "name": "camel.sink.endpoint.operation",
+ "description": "What operation to perform One of: [BatchGetItems] [DeleteItem] [DeleteTable] [DescribeTable] [GetItem] [PutItem] [Query] [Scan] [UpdateItem] [UpdateTable]",
+ "defaultValue": "\"PutItem\"",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.proxyHost": {
+ "name": "camel.sink.endpoint.proxyHost",
+ "description": "To define a proxy host when instantiating the DDB client",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
+ },
+ "camel.sink.endpoint.proxyPort": {
+ "name": "camel.sink.endpoint.proxyPort",
+ "description": "To define a proxy port when instantiating the DDB client. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name()",
+ "defaultValue": "null",
+ "priority": "MEDIUM"
... 95482 lines suppressed ...