You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by da...@apache.org on 2019/11/12 09:35:28 UTC
[camel] branch master updated (a5e4ab4 -> 80c1f9b)
This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git.
from a5e4ab4 Upgrade OWASP Maven Plugin to version 5.2.3
new 1e11348 CAMEL-14169: Make it easier to configure global endpoint options once
new 88ca334 Remove deprecated and not in use interface
new 80c1f9b CAMEL-14169: Regen options
The 3 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
.../src/main/docs/activemq-component.adoc | 8 +-
.../src/main/docs/ahc-ws-component.adoc | 8 +-
.../camel-ahc/src/main/docs/ahc-component.adoc | 8 +-
.../camel-amqp/src/main/docs/amqp-component.adoc | 8 +-
.../camel-apns/src/main/docs/apns-component.adoc | 8 +-
.../src/main/docs/as2-component.adoc | 8 +-
.../src/main/docs/asterisk-component.adoc | 8 +-
.../camel-atmos/src/main/docs/atmos-component.adoc | 8 +-
.../main/docs/atmosphere-websocket-component.adoc | 8 +-
.../camel-atom/src/main/docs/atom-component.adoc | 8 +-
.../src/main/docs/atomix-map-component.adoc | 8 +-
.../src/main/docs/atomix-messaging-component.adoc | 8 +-
.../src/main/docs/atomix-multimap-component.adoc | 8 +-
.../src/main/docs/atomix-queue-component.adoc | 8 +-
.../src/main/docs/atomix-set-component.adoc | 8 +-
.../src/main/docs/atomix-value-component.adoc | 8 +-
.../camel-avro/src/main/docs/avro-component.adoc | 8 +-
.../camel-avro/src/main/docs/avro-dataformat.adoc | 4 +-
.../src/main/docs/aws-cw-component.adoc | 8 +-
.../src/main/docs/aws-ddb-component.adoc | 8 +-
.../src/main/docs/aws-ddbstream-component.adoc | 8 +-
.../src/main/docs/aws-ec2-component.adoc | 8 +-
.../src/main/docs/aws-ecs-component.adoc | 8 +-
.../src/main/docs/aws-eks-component.adoc | 8 +-
.../src/main/docs/aws-iam-component.adoc | 8 +-
.../src/main/docs/aws-kinesis-component.adoc | 8 +-
.../main/docs/aws-kinesis-firehose-component.adoc | 8 +-
.../src/main/docs/aws-kms-component.adoc | 8 +-
.../src/main/docs/aws-lambda-component.adoc | 8 +-
.../src/main/docs/aws-mq-component.adoc | 8 +-
.../src/main/docs/aws-msk-component.adoc | 8 +-
.../src/main/docs/aws-s3-component.adoc | 8 +-
.../src/main/docs/aws-sdb-component.adoc | 8 +-
.../src/main/docs/aws-ses-component.adoc | 8 +-
.../src/main/docs/aws-sns-component.adoc | 8 +-
.../src/main/docs/aws-sqs-component.adoc | 8 +-
.../src/main/docs/aws-swf-component.adoc | 8 +-
.../src/main/docs/aws-translate-component.adoc | 8 +-
.../src/main/docs/azure-blob-component.adoc | 8 +-
.../src/main/docs/azure-queue-component.adoc | 8 +-
.../src/main/docs/bean-validator-component.adoc | 8 +-
.../camel-bean/src/main/docs/bean-component.adoc | 8 +-
.../camel-bean/src/main/docs/bean-language.adoc | 4 +-
.../camel-bean/src/main/docs/class-component.adoc | 4 +-
.../src/main/docs/beanstalk-component.adoc | 8 +-
.../src/main/docs/bonita-component.adoc | 8 +-
.../src/main/docs/box-component.adoc | 8 +-
.../src/main/docs/braintree-component.adoc | 8 +-
.../src/main/docs/browse-component.adoc | 8 +-
.../src/main/docs/caffeine-cache-component.adoc | 8 +-
.../main/docs/caffeine-loadcache-component.adoc | 8 +-
.../src/main/docs/cql-component.adoc | 8 +-
.../src/main/docs/chatscript-component.adoc | 8 +-
.../camel-chunk/src/main/docs/chunk-component.adoc | 8 +-
.../src/main/docs/cm-sms-component.adoc | 8 +-
.../camel-cmis/src/main/docs/cmis-component.adoc | 8 +-
.../camel-coap/src/main/docs/coap-component.adoc | 8 +-
.../src/main/docs/cometd-component.adoc | 8 +-
.../src/main/docs/consul-component.adoc | 8 +-
.../src/main/docs/controlbus-component.adoc | 8 +-
.../camel-corda/src/main/docs/corda-component.adoc | 8 +-
.../src/main/docs/couchbase-component.adoc | 8 +-
.../src/main/docs/couchdb-component.adoc | 8 +-
.../src/main/docs/crypto-cms-component.adoc | 8 +-
.../src/main/docs/crypto-component.adoc | 8 +-
.../src/main/docs/crypto-dataformat.adoc | 4 +-
.../camel-cxf/src/main/docs/cxf-component.adoc | 8 +-
.../camel-cxf/src/main/docs/cxfrs-component.adoc | 8 +-
.../src/main/docs/dataformat-component.adoc | 8 +-
.../src/main/docs/dataset-component.adoc | 8 +-
.../src/main/docs/dataset-test-component.adoc | 8 +-
.../src/main/docs/debezium-mongodb-component.adoc | 8 +-
.../src/main/docs/debezium-mysql-component.adoc | 8 +-
.../src/main/docs/debezium-postgres-component.adoc | 8 +-
.../main/docs/debezium-sqlserver-component.adoc | 8 +-
.../src/main/docs/digitalocean-component.adoc | 8 +-
.../src/main/docs/direct-component.adoc | 8 +-
.../src/main/docs/direct-vm-component.adoc | 4 +-
.../src/main/docs/disruptor-component.adoc | 10 ++-
.../camel-dns/src/main/docs/dns-component.adoc | 8 +-
.../src/main/docs/docker-component.adoc | 8 +-
.../camel-dozer/src/main/docs/dozer-component.adoc | 8 +-
.../camel-drill/src/main/docs/drill-component.adoc | 8 +-
.../src/main/docs/dropbox-component.adoc | 8 +-
.../src/main/docs/ehcache-component.adoc | 8 +-
.../main/docs/elasticsearch-rest-component.adoc | 8 +-
.../camel-elsql/src/main/docs/elsql-component.adoc | 8 +-
.../camel-etcd/src/main/docs/etcd-component.adoc | 8 +-
.../src/main/docs/eventadmin-component.adoc | 4 +-
.../camel-exec/src/main/docs/exec-component.adoc | 8 +-
.../src/main/docs/facebook-component.adoc | 8 +-
.../src/main/docs/fhir-component.adoc | 8 +-
.../src/main/docs/file-watch-component.adoc | 8 +-
.../camel-file/src/main/docs/file-component.adoc | 8 +-
.../src/main/docs/flatpack-component.adoc | 8 +-
.../src/main/docs/flatpack-dataformat.adoc | 4 +-
.../camel-flink/src/main/docs/flink-component.adoc | 8 +-
.../camel-fop/src/main/docs/fop-component.adoc | 8 +-
.../src/main/docs/freemarker-component.adoc | 8 +-
.../camel-ftp/src/main/docs/ftp-component.adoc | 8 +-
.../camel-ftp/src/main/docs/ftps-component.adoc | 8 +-
.../camel-ftp/src/main/docs/sftp-component.adoc | 4 +-
.../src/main/docs/ganglia-component.adoc | 8 +-
.../src/main/docs/geocoder-component.adoc | 8 +-
.../camel-git/src/main/docs/git-component.adoc | 8 +-
.../src/main/docs/github-component.adoc | 8 +-
.../src/main/docs/google-bigquery-component.adoc | 8 +-
.../main/docs/google-bigquery-sql-component.adoc | 8 +-
.../src/main/docs/google-calendar-component.adoc | 8 +-
.../docs/google-calendar-stream-component.adoc | 8 +-
.../src/main/docs/google-drive-component.adoc | 8 +-
.../src/main/docs/google-mail-component.adoc | 8 +-
.../main/docs/google-mail-stream-component.adoc | 8 +-
.../src/main/docs/google-pubsub-component.adoc | 8 +-
.../src/main/docs/google-sheets-component.adoc | 8 +-
.../main/docs/google-sheets-stream-component.adoc | 8 +-
.../camel-gora/src/main/docs/gora-component.adoc | 8 +-
.../camel-grape/src/main/docs/grape-component.adoc | 4 +-
.../src/main/docs/graphql-component.adoc | 8 +-
.../camel-grpc/src/main/docs/grpc-component.adoc | 8 +-
.../src/main/docs/guava-eventbus-component.adoc | 8 +-
.../main/docs/hazelcast-atomicvalue-component.adoc | 8 +-
.../main/docs/hazelcast-instance-component.adoc | 8 +-
.../src/main/docs/hazelcast-list-component.adoc | 8 +-
.../src/main/docs/hazelcast-map-component.adoc | 8 +-
.../main/docs/hazelcast-multimap-component.adoc | 8 +-
.../src/main/docs/hazelcast-queue-component.adoc | 8 +-
.../docs/hazelcast-replicatedmap-component.adoc | 8 +-
.../main/docs/hazelcast-ringbuffer-component.adoc | 8 +-
.../src/main/docs/hazelcast-seda-component.adoc | 8 +-
.../src/main/docs/hazelcast-set-component.adoc | 8 +-
.../src/main/docs/hazelcast-topic-component.adoc | 8 +-
.../camel-hbase/src/main/docs/hbase-component.adoc | 8 +-
.../camel-hdfs/src/main/docs/hdfs-component.adoc | 8 +-
.../src/main/docs/hipchat-component.adoc | 8 +-
.../camel-http/src/main/docs/http-component.adoc | 8 +-
.../src/main/docs/iec60870-client-component.adoc | 8 +-
.../src/main/docs/iec60870-server-component.adoc | 8 +-
.../src/main/docs/ignite-cache-component.adoc | 8 +-
.../src/main/docs/ignite-compute-component.adoc | 8 +-
.../src/main/docs/ignite-events-component.adoc | 8 +-
.../src/main/docs/ignite-idgen-component.adoc | 8 +-
.../src/main/docs/ignite-messaging-component.adoc | 8 +-
.../src/main/docs/ignite-queue-component.adoc | 8 +-
.../src/main/docs/ignite-set-component.adoc | 8 +-
.../src/main/docs/infinispan-component.adoc | 8 +-
.../src/main/docs/influxdb-component.adoc | 8 +-
.../camel-iota/src/main/docs/iota-component.adoc | 8 +-
.../camel-ipfs/src/main/docs/ipfs-component.adoc | 8 +-
.../camel-irc/src/main/docs/irc-component.adoc | 8 +-
.../src/main/docs/ironmq-component.adoc | 8 +-
.../camel-jbpm/src/main/docs/jbpm-component.adoc | 8 +-
.../src/main/docs/jcache-component.adoc | 8 +-
.../src/main/docs/jclouds-component.adoc | 8 +-
.../camel-jcr/src/main/docs/jcr-component.adoc | 8 +-
.../camel-jdbc/src/main/docs/jdbc-component.adoc | 8 +-
.../camel-jetty/src/main/docs/jetty-component.adoc | 8 +-
.../src/main/docs/jgroups-raft-component.adoc | 8 +-
.../src/main/docs/jgroups-component.adoc | 8 +-
.../camel-jing/src/main/docs/jing-component.adoc | 8 +-
.../camel-jira/src/main/docs/jira-component.adoc | 8 +-
.../camel-jms/src/main/docs/jms-component.adoc | 8 +-
.../camel-jmx/src/main/docs/jmx-component.adoc | 8 +-
.../camel-jolt/src/main/docs/jolt-component.adoc | 8 +-
.../camel-jooq/src/main/docs/jooq-component.adoc | 8 +-
.../camel-jpa/src/main/docs/jpa-component.adoc | 8 +-
.../camel-jsch/src/main/docs/scp-component.adoc | 8 +-
.../src/main/docs/json-validator-component.adoc | 8 +-
.../camel-jt400/src/main/docs/jt400-component.adoc | 8 +-
.../camel-kafka/src/main/docs/kafka-component.adoc | 8 +-
.../docs/kubernetes-config-maps-component.adoc | 8 +-
.../docs/kubernetes-deployments-component.adoc | 8 +-
.../src/main/docs/kubernetes-hpa-component.adoc | 8 +-
.../src/main/docs/kubernetes-job-component.adoc | 8 +-
.../main/docs/kubernetes-namespaces-component.adoc | 8 +-
.../src/main/docs/kubernetes-nodes-component.adoc | 8 +-
...rnetes-persistent-volumes-claims-component.adoc | 8 +-
.../kubernetes-persistent-volumes-component.adoc | 8 +-
.../src/main/docs/kubernetes-pods-component.adoc | 8 +-
...bernetes-replication-controllers-component.adoc | 8 +-
.../docs/kubernetes-resources-quota-component.adoc | 8 +-
.../main/docs/kubernetes-secrets-component.adoc | 8 +-
.../kubernetes-service-accounts-component.adoc | 8 +-
.../main/docs/kubernetes-services-component.adoc | 8 +-
.../docs/openshift-build-configs-component.adoc | 4 +-
.../src/main/docs/openshift-builds-component.adoc | 4 +-
.../camel-kudu/src/main/docs/kudu-component.adoc | 4 +-
.../src/main/docs/language-component.adoc | 8 +-
.../camel-ldap/src/main/docs/ldap-component.adoc | 8 +-
.../camel-ldif/src/main/docs/ldif-component.adoc | 8 +-
.../camel-log/src/main/docs/log-component.adoc | 8 +-
.../src/main/docs/lucene-component.adoc | 8 +-
.../src/main/docs/lumberjack-component.adoc | 8 +-
.../camel-mail/src/main/docs/mail-component.adoc | 8 +-
.../src/main/docs/master-component.adoc | 8 +-
.../src/main/docs/metrics-component.adoc | 8 +-
.../src/main/docs/micrometer-component.adoc | 8 +-
.../main/docs/microprofile-metrics-component.adoc | 4 +-
.../src/main/docs/milo-client-component.adoc | 8 +-
.../src/main/docs/milo-server-component.adoc | 8 +-
.../camel-mina/src/main/docs/mina-component.adoc | 8 +-
.../camel-mllp/src/main/docs/mllp-component.adoc | 8 +-
.../camel-mock/src/main/docs/mock-component.adoc | 8 +-
.../src/main/docs/mongodb-gridfs-component.adoc | 8 +-
.../src/main/docs/mongodb-component.adoc | 8 +-
.../camel-msv/src/main/docs/msv-component.adoc | 8 +-
.../src/main/docs/mustache-component.adoc | 8 +-
.../camel-mvel/src/main/docs/mvel-component.adoc | 8 +-
.../camel-mvel/src/main/docs/mvel-language.adoc | 4 +-
.../src/main/docs/mybatis-bean-component.adoc | 8 +-
.../src/main/docs/mybatis-component.adoc | 8 +-
.../src/main/docs/nagios-component.adoc | 8 +-
.../camel-nats/src/main/docs/nats-component.adoc | 8 +-
.../src/main/docs/netty-http-component.adoc | 8 +-
.../camel-netty/src/main/docs/netty-component.adoc | 8 +-
.../src/main/docs/nitrite-component.adoc | 8 +-
.../camel-nsq/src/main/docs/nsq-component.adoc | 8 +-
.../src/main/docs/olingo2-component.adoc | 8 +-
.../src/main/docs/olingo4-component.adoc | 8 +-
.../src/main/docs/openstack-cinder-component.adoc | 8 +-
.../src/main/docs/openstack-glance-component.adoc | 8 +-
.../main/docs/openstack-keystone-component.adoc | 8 +-
.../src/main/docs/openstack-neutron-component.adoc | 8 +-
.../src/main/docs/openstack-nova-component.adoc | 8 +-
.../src/main/docs/openstack-swift-component.adoc | 8 +-
.../src/main/docs/optaplanner-component.adoc | 8 +-
.../camel-paho/src/main/docs/paho-component.adoc | 8 +-
.../src/main/docs/paxlogging-component.adoc | 4 +-
.../camel-pdf/src/main/docs/pdf-component.adoc | 8 +-
.../main/docs/pg-replication-slot-component.adoc | 8 +-
.../src/main/docs/pgevent-component.adoc | 8 +-
.../camel-printer/src/main/docs/lpr-component.adoc | 8 +-
.../src/main/docs/pubnub-component.adoc | 8 +-
.../src/main/docs/pulsar-component.adoc | 8 +-
.../src/main/docs/quartz-component.adoc | 8 +-
.../src/main/docs/quickfix-component.adoc | 8 +-
.../src/main/docs/rabbitmq-component.adoc | 8 +-
.../src/main/docs/reactive-streams-component.adoc | 8 +-
.../camel-ref/src/main/docs/ref-component.adoc | 8 +-
.../src/main/docs/rest-swagger-component.adoc | 8 +-
.../src/main/docs/rest-api-component.adoc | 8 +-
.../camel-rest/src/main/docs/rest-component.adoc | 8 +-
.../src/main/docs/robotframework-component.adoc | 8 +-
.../camel-rss/src/main/docs/rss-component.adoc | 8 +-
.../camel-rss/src/main/docs/rss-dataformat.adoc | 4 +-
.../camel-saga/src/main/docs/saga-component.adoc | 8 +-
.../src/main/docs/salesforce-component.adoc | 8 +-
.../src/main/docs/sap-netweaver-component.adoc | 8 +-
.../src/main/docs/xquery-component.adoc | 8 +-
.../camel-saxon/src/main/docs/xquery-language.adoc | 4 +-
.../src/main/docs/scheduler-component.adoc | 8 +-
.../src/main/docs/schematron-component.adoc | 8 +-
.../camel-seda/src/main/docs/seda-component.adoc | 8 +-
.../src/main/docs/service-component.adoc | 8 +-
.../src/main/docs/servicenow-component.adoc | 8 +-
.../src/main/docs/servlet-component.adoc | 8 +-
.../camel-sip/src/main/docs/sip-component.adoc | 8 +-
.../src/main/docs/sjms-batch-component.adoc | 8 +-
.../camel-sjms/src/main/docs/sjms-component.adoc | 8 +-
.../camel-sjms2/src/main/docs/sjms2-component.adoc | 8 +-
.../camel-slack/src/main/docs/slack-component.adoc | 8 +-
.../camel-smpp/src/main/docs/smpp-component.adoc | 8 +-
.../camel-snmp/src/main/docs/snmp-component.adoc | 8 +-
.../camel-solr/src/main/docs/solr-component.adoc | 8 +-
.../src/main/docs/soroush-component.adoc | 8 +-
.../src/main/docs/spark-rest-component.adoc | 4 +-
.../camel-spark/src/main/docs/spark-component.adoc | 8 +-
.../src/main/docs/splunk-component.adoc | 8 +-
.../src/main/docs/spring-batch-component.adoc | 8 +-
.../src/main/docs/spring-boot.adoc | 5 +-
.../spring/boot/CamelConfigurationProperties.java | 29 +++++++
.../main/docs/spring-integration-component.adoc | 8 +-
.../src/main/docs/spring-ldap-component.adoc | 8 +-
.../src/main/docs/spring-redis-component.adoc | 8 +-
.../src/main/docs/spring-ws-component.adoc | 8 +-
.../src/main/docs/spring-event-component.adoc | 8 +-
.../camel-sql/src/main/docs/sql-component.adoc | 8 +-
.../src/main/docs/sql-stored-component.adoc | 8 +-
.../camel-ssh/src/main/docs/ssh-component.adoc | 8 +-
.../camel-stax/src/main/docs/stax-component.adoc | 8 +-
.../camel-stomp/src/main/docs/stomp-component.adoc | 8 +-
.../src/main/docs/stream-component.adoc | 8 +-
.../src/main/docs/string-template-component.adoc | 8 +-
.../camel-stub/src/main/docs/stub-component.adoc | 8 +-
.../src/main/docs/telegram-component.adoc | 8 +-
.../src/main/docs/thrift-component.adoc | 8 +-
.../src/main/docs/thrift-dataformat.adoc | 4 +-
.../camel-tika/src/main/docs/tika-component.adoc | 8 +-
.../camel-timer/src/main/docs/timer-component.adoc | 8 +-
.../src/main/docs/twilio-component.adoc | 8 +-
.../main/docs/twitter-directmessage-component.adoc | 8 +-
.../src/main/docs/twitter-search-component.adoc | 8 +-
.../src/main/docs/twitter-timeline-component.adoc | 8 +-
.../src/main/docs/undertow-component.adoc | 8 +-
.../src/main/docs/validator-component.adoc | 8 +-
.../src/main/docs/velocity-component.adoc | 8 +-
.../camel-vertx/src/main/docs/vertx-component.adoc | 8 +-
.../camel-vm/src/main/docs/vm-component.adoc | 8 +-
.../src/main/docs/weather-component.adoc | 8 +-
.../camel-web3j/src/main/docs/web3j-component.adoc | 8 +-
.../src/main/docs/webhook-component.adoc | 8 +-
.../src/main/docs/websocket-jsr356-component.adoc | 8 +-
.../src/main/docs/websocket-component.adoc | 8 +-
.../src/main/docs/wordpress-component.adoc | 8 +-
.../src/main/docs/xchange-component.adoc | 8 +-
.../camel-xj/src/main/docs/xj-component.adoc | 8 +-
.../src/main/docs/xmlsecurity-component.adoc | 8 +-
.../camel-xmpp/src/main/docs/xmpp-component.adoc | 8 +-
.../camel-xslt/src/main/docs/xslt-component.adoc | 8 +-
.../src/main/docs/yammer-component.adoc | 8 +-
.../src/main/docs/zendesk-component.adoc | 8 +-
.../src/main/docs/zookeeper-master-component.adoc | 8 +-
.../src/main/docs/zookeeper-component.adoc | 8 +-
.../main/java/org/apache/camel/CamelContext.java | 5 ++
.../apache/camel/GlobalEndpointConfiguration.java | 53 +++++++++++++
.../camel/spi/EndpointPropertyConfigurer.java | 35 ---------
.../camel/impl/engine/AbstractCamelContext.java | 7 ++
.../engine/DefaultGlobalEndpointConfiguration.java | 38 +++++-----
.../apache/camel/impl/LazyStartProducerTest.java | 31 ++++++++
.../camel/main/DefaultConfigurationConfigurer.java | 5 ++
.../camel/main/DefaultConfigurationProperties.java | 88 ++++++++++++++++++++++
.../camel-main-configuration-metadata.json | 18 +++++
.../org/apache/camel/support/DefaultComponent.java | 65 +++++++++++++++-
.../org/apache/camel/support/DefaultEndpoint.java | 6 +-
.../modules/ROOT/pages/activemq-component.adoc | 8 +-
.../modules/ROOT/pages/ahc-component.adoc | 8 +-
.../modules/ROOT/pages/ahc-ws-component.adoc | 8 +-
.../modules/ROOT/pages/amqp-component.adoc | 8 +-
.../modules/ROOT/pages/apns-component.adoc | 8 +-
.../modules/ROOT/pages/as2-component.adoc | 8 +-
.../modules/ROOT/pages/asterisk-component.adoc | 8 +-
.../modules/ROOT/pages/atmos-component.adoc | 8 +-
.../ROOT/pages/atmosphere-websocket-component.adoc | 8 +-
.../modules/ROOT/pages/atom-component.adoc | 8 +-
.../modules/ROOT/pages/atomix-map-component.adoc | 8 +-
.../ROOT/pages/atomix-messaging-component.adoc | 8 +-
.../ROOT/pages/atomix-multimap-component.adoc | 8 +-
.../modules/ROOT/pages/atomix-queue-component.adoc | 8 +-
.../modules/ROOT/pages/atomix-set-component.adoc | 8 +-
.../modules/ROOT/pages/atomix-value-component.adoc | 8 +-
.../modules/ROOT/pages/avro-component.adoc | 8 +-
.../modules/ROOT/pages/avro-dataformat.adoc | 4 +-
.../modules/ROOT/pages/aws-cw-component.adoc | 8 +-
.../modules/ROOT/pages/aws-ddb-component.adoc | 8 +-
.../ROOT/pages/aws-ddbstream-component.adoc | 8 +-
.../modules/ROOT/pages/aws-ec2-component.adoc | 8 +-
.../modules/ROOT/pages/aws-ecs-component.adoc | 8 +-
.../modules/ROOT/pages/aws-eks-component.adoc | 8 +-
.../modules/ROOT/pages/aws-iam-component.adoc | 8 +-
.../modules/ROOT/pages/aws-kinesis-component.adoc | 8 +-
.../ROOT/pages/aws-kinesis-firehose-component.adoc | 8 +-
.../modules/ROOT/pages/aws-kms-component.adoc | 8 +-
.../modules/ROOT/pages/aws-lambda-component.adoc | 8 +-
.../modules/ROOT/pages/aws-mq-component.adoc | 8 +-
.../modules/ROOT/pages/aws-msk-component.adoc | 8 +-
.../modules/ROOT/pages/aws-s3-component.adoc | 8 +-
.../modules/ROOT/pages/aws-sdb-component.adoc | 8 +-
.../modules/ROOT/pages/aws-ses-component.adoc | 8 +-
.../modules/ROOT/pages/aws-sns-component.adoc | 8 +-
.../modules/ROOT/pages/aws-sqs-component.adoc | 8 +-
.../modules/ROOT/pages/aws-swf-component.adoc | 8 +-
.../ROOT/pages/aws-translate-component.adoc | 8 +-
.../modules/ROOT/pages/azure-blob-component.adoc | 8 +-
.../modules/ROOT/pages/azure-queue-component.adoc | 8 +-
.../modules/ROOT/pages/bean-component.adoc | 8 +-
.../modules/ROOT/pages/bean-language.adoc | 4 +-
.../ROOT/pages/bean-validator-component.adoc | 8 +-
.../modules/ROOT/pages/beanstalk-component.adoc | 8 +-
.../modules/ROOT/pages/bonita-component.adoc | 8 +-
.../modules/ROOT/pages/box-component.adoc | 8 +-
.../modules/ROOT/pages/braintree-component.adoc | 8 +-
.../modules/ROOT/pages/browse-component.adoc | 8 +-
.../ROOT/pages/caffeine-cache-component.adoc | 8 +-
.../ROOT/pages/caffeine-loadcache-component.adoc | 8 +-
.../modules/ROOT/pages/chatscript-component.adoc | 8 +-
.../modules/ROOT/pages/chunk-component.adoc | 8 +-
.../modules/ROOT/pages/class-component.adoc | 4 +-
.../modules/ROOT/pages/cm-sms-component.adoc | 8 +-
.../modules/ROOT/pages/cmis-component.adoc | 8 +-
.../modules/ROOT/pages/coap-component.adoc | 8 +-
.../modules/ROOT/pages/cometd-component.adoc | 8 +-
.../modules/ROOT/pages/consul-component.adoc | 8 +-
.../modules/ROOT/pages/controlbus-component.adoc | 8 +-
.../modules/ROOT/pages/corda-component.adoc | 8 +-
.../modules/ROOT/pages/couchbase-component.adoc | 8 +-
.../modules/ROOT/pages/couchdb-component.adoc | 8 +-
.../modules/ROOT/pages/cql-component.adoc | 8 +-
.../modules/ROOT/pages/crypto-cms-component.adoc | 8 +-
.../modules/ROOT/pages/crypto-component.adoc | 8 +-
.../modules/ROOT/pages/crypto-dataformat.adoc | 4 +-
.../modules/ROOT/pages/cxf-component.adoc | 8 +-
.../modules/ROOT/pages/cxfrs-component.adoc | 8 +-
.../modules/ROOT/pages/dataformat-component.adoc | 8 +-
.../modules/ROOT/pages/dataset-component.adoc | 8 +-
.../modules/ROOT/pages/dataset-test-component.adoc | 8 +-
.../ROOT/pages/debezium-mongodb-component.adoc | 8 +-
.../ROOT/pages/debezium-mysql-component.adoc | 8 +-
.../ROOT/pages/debezium-postgres-component.adoc | 8 +-
.../ROOT/pages/debezium-sqlserver-component.adoc | 8 +-
.../modules/ROOT/pages/digitalocean-component.adoc | 8 +-
.../modules/ROOT/pages/direct-component.adoc | 8 +-
.../modules/ROOT/pages/direct-vm-component.adoc | 4 +-
.../modules/ROOT/pages/disruptor-component.adoc | 10 ++-
.../modules/ROOT/pages/dns-component.adoc | 8 +-
.../modules/ROOT/pages/docker-component.adoc | 8 +-
.../modules/ROOT/pages/dozer-component.adoc | 8 +-
.../modules/ROOT/pages/drill-component.adoc | 8 +-
.../modules/ROOT/pages/dropbox-component.adoc | 8 +-
.../modules/ROOT/pages/ehcache-component.adoc | 8 +-
.../ROOT/pages/elasticsearch-rest-component.adoc | 8 +-
.../modules/ROOT/pages/elsql-component.adoc | 8 +-
.../modules/ROOT/pages/etcd-component.adoc | 8 +-
.../modules/ROOT/pages/eventadmin-component.adoc | 4 +-
.../modules/ROOT/pages/exec-component.adoc | 8 +-
.../modules/ROOT/pages/facebook-component.adoc | 8 +-
.../modules/ROOT/pages/fhir-component.adoc | 8 +-
.../modules/ROOT/pages/file-component.adoc | 8 +-
.../modules/ROOT/pages/file-watch-component.adoc | 8 +-
.../modules/ROOT/pages/flatpack-component.adoc | 8 +-
.../modules/ROOT/pages/flatpack-dataformat.adoc | 4 +-
.../modules/ROOT/pages/flink-component.adoc | 8 +-
.../modules/ROOT/pages/fop-component.adoc | 8 +-
.../modules/ROOT/pages/freemarker-component.adoc | 8 +-
.../modules/ROOT/pages/ftp-component.adoc | 8 +-
.../modules/ROOT/pages/ftps-component.adoc | 8 +-
.../modules/ROOT/pages/ganglia-component.adoc | 8 +-
.../modules/ROOT/pages/geocoder-component.adoc | 8 +-
.../modules/ROOT/pages/git-component.adoc | 8 +-
.../modules/ROOT/pages/github-component.adoc | 8 +-
.../ROOT/pages/google-bigquery-component.adoc | 8 +-
.../ROOT/pages/google-bigquery-sql-component.adoc | 8 +-
.../ROOT/pages/google-calendar-component.adoc | 8 +-
.../pages/google-calendar-stream-component.adoc | 8 +-
.../modules/ROOT/pages/google-drive-component.adoc | 8 +-
.../modules/ROOT/pages/google-mail-component.adoc | 8 +-
.../ROOT/pages/google-mail-stream-component.adoc | 8 +-
.../ROOT/pages/google-pubsub-component.adoc | 8 +-
.../ROOT/pages/google-sheets-component.adoc | 8 +-
.../ROOT/pages/google-sheets-stream-component.adoc | 8 +-
.../modules/ROOT/pages/gora-component.adoc | 8 +-
.../modules/ROOT/pages/grape-component.adoc | 4 +-
.../modules/ROOT/pages/graphql-component.adoc | 8 +-
.../modules/ROOT/pages/grpc-component.adoc | 8 +-
.../ROOT/pages/guava-eventbus-component.adoc | 8 +-
.../pages/hazelcast-atomicvalue-component.adoc | 8 +-
.../ROOT/pages/hazelcast-instance-component.adoc | 8 +-
.../ROOT/pages/hazelcast-list-component.adoc | 8 +-
.../ROOT/pages/hazelcast-map-component.adoc | 8 +-
.../ROOT/pages/hazelcast-multimap-component.adoc | 8 +-
.../ROOT/pages/hazelcast-queue-component.adoc | 8 +-
.../pages/hazelcast-replicatedmap-component.adoc | 8 +-
.../ROOT/pages/hazelcast-ringbuffer-component.adoc | 8 +-
.../ROOT/pages/hazelcast-seda-component.adoc | 8 +-
.../ROOT/pages/hazelcast-set-component.adoc | 8 +-
.../ROOT/pages/hazelcast-topic-component.adoc | 8 +-
.../modules/ROOT/pages/hbase-component.adoc | 8 +-
.../modules/ROOT/pages/hdfs-component.adoc | 8 +-
.../modules/ROOT/pages/hipchat-component.adoc | 8 +-
.../modules/ROOT/pages/http-component.adoc | 8 +-
.../ROOT/pages/iec60870-client-component.adoc | 8 +-
.../ROOT/pages/iec60870-server-component.adoc | 8 +-
.../modules/ROOT/pages/ignite-cache-component.adoc | 8 +-
.../ROOT/pages/ignite-compute-component.adoc | 8 +-
.../ROOT/pages/ignite-events-component.adoc | 8 +-
.../modules/ROOT/pages/ignite-idgen-component.adoc | 8 +-
.../ROOT/pages/ignite-messaging-component.adoc | 8 +-
.../modules/ROOT/pages/ignite-queue-component.adoc | 8 +-
.../modules/ROOT/pages/ignite-set-component.adoc | 8 +-
.../modules/ROOT/pages/infinispan-component.adoc | 8 +-
.../modules/ROOT/pages/influxdb-component.adoc | 8 +-
.../modules/ROOT/pages/iota-component.adoc | 8 +-
.../modules/ROOT/pages/ipfs-component.adoc | 8 +-
.../modules/ROOT/pages/irc-component.adoc | 8 +-
.../modules/ROOT/pages/ironmq-component.adoc | 8 +-
.../modules/ROOT/pages/jbpm-component.adoc | 8 +-
.../modules/ROOT/pages/jcache-component.adoc | 8 +-
.../modules/ROOT/pages/jclouds-component.adoc | 8 +-
.../modules/ROOT/pages/jcr-component.adoc | 8 +-
.../modules/ROOT/pages/jdbc-component.adoc | 8 +-
.../modules/ROOT/pages/jetty-component.adoc | 8 +-
.../modules/ROOT/pages/jgroups-component.adoc | 8 +-
.../modules/ROOT/pages/jgroups-raft-component.adoc | 8 +-
.../modules/ROOT/pages/jing-component.adoc | 8 +-
.../modules/ROOT/pages/jira-component.adoc | 8 +-
.../modules/ROOT/pages/jms-component.adoc | 8 +-
.../modules/ROOT/pages/jmx-component.adoc | 8 +-
.../modules/ROOT/pages/jolt-component.adoc | 8 +-
.../modules/ROOT/pages/jooq-component.adoc | 8 +-
.../modules/ROOT/pages/jpa-component.adoc | 8 +-
.../ROOT/pages/json-validator-component.adoc | 8 +-
.../modules/ROOT/pages/jt400-component.adoc | 8 +-
.../modules/ROOT/pages/kafka-component.adoc | 8 +-
.../pages/kubernetes-config-maps-component.adoc | 8 +-
.../pages/kubernetes-deployments-component.adoc | 8 +-
.../ROOT/pages/kubernetes-hpa-component.adoc | 8 +-
.../ROOT/pages/kubernetes-job-component.adoc | 8 +-
.../pages/kubernetes-namespaces-component.adoc | 8 +-
.../ROOT/pages/kubernetes-nodes-component.adoc | 8 +-
...rnetes-persistent-volumes-claims-component.adoc | 8 +-
.../kubernetes-persistent-volumes-component.adoc | 8 +-
.../ROOT/pages/kubernetes-pods-component.adoc | 8 +-
...bernetes-replication-controllers-component.adoc | 8 +-
.../kubernetes-resources-quota-component.adoc | 8 +-
.../ROOT/pages/kubernetes-secrets-component.adoc | 8 +-
.../kubernetes-service-accounts-component.adoc | 8 +-
.../ROOT/pages/kubernetes-services-component.adoc | 8 +-
.../modules/ROOT/pages/kudu-component.adoc | 4 +-
.../modules/ROOT/pages/language-component.adoc | 8 +-
.../modules/ROOT/pages/ldap-component.adoc | 8 +-
.../modules/ROOT/pages/ldif-component.adoc | 8 +-
.../modules/ROOT/pages/log-component.adoc | 8 +-
.../modules/ROOT/pages/lpr-component.adoc | 8 +-
.../modules/ROOT/pages/lucene-component.adoc | 8 +-
.../modules/ROOT/pages/lumberjack-component.adoc | 8 +-
.../modules/ROOT/pages/mail-component.adoc | 8 +-
.../modules/ROOT/pages/master-component.adoc | 8 +-
.../modules/ROOT/pages/metrics-component.adoc | 8 +-
.../modules/ROOT/pages/micrometer-component.adoc | 8 +-
.../ROOT/pages/microprofile-metrics-component.adoc | 4 +-
.../modules/ROOT/pages/milo-client-component.adoc | 8 +-
.../modules/ROOT/pages/milo-server-component.adoc | 8 +-
.../modules/ROOT/pages/mina-component.adoc | 8 +-
.../modules/ROOT/pages/mllp-component.adoc | 8 +-
.../modules/ROOT/pages/mock-component.adoc | 8 +-
.../modules/ROOT/pages/mongodb-component.adoc | 8 +-
.../ROOT/pages/mongodb-gridfs-component.adoc | 8 +-
.../modules/ROOT/pages/msv-component.adoc | 8 +-
.../modules/ROOT/pages/mustache-component.adoc | 8 +-
.../modules/ROOT/pages/mvel-component.adoc | 8 +-
.../modules/ROOT/pages/mvel-language.adoc | 4 +-
.../modules/ROOT/pages/mybatis-bean-component.adoc | 8 +-
.../modules/ROOT/pages/mybatis-component.adoc | 8 +-
.../modules/ROOT/pages/nagios-component.adoc | 8 +-
.../modules/ROOT/pages/nats-component.adoc | 8 +-
.../modules/ROOT/pages/netty-component.adoc | 8 +-
.../modules/ROOT/pages/netty-http-component.adoc | 8 +-
.../modules/ROOT/pages/nitrite-component.adoc | 8 +-
.../modules/ROOT/pages/nsq-component.adoc | 8 +-
.../modules/ROOT/pages/olingo2-component.adoc | 8 +-
.../modules/ROOT/pages/olingo4-component.adoc | 8 +-
.../pages/openshift-build-configs-component.adoc | 4 +-
.../ROOT/pages/openshift-builds-component.adoc | 4 +-
.../ROOT/pages/openstack-cinder-component.adoc | 8 +-
.../ROOT/pages/openstack-glance-component.adoc | 8 +-
.../ROOT/pages/openstack-keystone-component.adoc | 8 +-
.../ROOT/pages/openstack-neutron-component.adoc | 8 +-
.../ROOT/pages/openstack-nova-component.adoc | 8 +-
.../ROOT/pages/openstack-swift-component.adoc | 8 +-
.../modules/ROOT/pages/optaplanner-component.adoc | 8 +-
.../modules/ROOT/pages/paho-component.adoc | 8 +-
.../modules/ROOT/pages/paxlogging-component.adoc | 4 +-
.../modules/ROOT/pages/pdf-component.adoc | 8 +-
.../ROOT/pages/pg-replication-slot-component.adoc | 8 +-
.../modules/ROOT/pages/pgevent-component.adoc | 8 +-
.../modules/ROOT/pages/pubnub-component.adoc | 8 +-
.../modules/ROOT/pages/pulsar-component.adoc | 8 +-
.../modules/ROOT/pages/quartz-component.adoc | 8 +-
.../modules/ROOT/pages/quickfix-component.adoc | 8 +-
.../modules/ROOT/pages/rabbitmq-component.adoc | 8 +-
.../ROOT/pages/reactive-streams-component.adoc | 8 +-
.../modules/ROOT/pages/ref-component.adoc | 8 +-
.../modules/ROOT/pages/rest-api-component.adoc | 8 +-
.../modules/ROOT/pages/rest-component.adoc | 8 +-
.../modules/ROOT/pages/rest-swagger-component.adoc | 8 +-
.../ROOT/pages/robotframework-component.adoc | 8 +-
.../modules/ROOT/pages/rss-component.adoc | 8 +-
.../modules/ROOT/pages/rss-dataformat.adoc | 4 +-
.../modules/ROOT/pages/saga-component.adoc | 8 +-
.../modules/ROOT/pages/salesforce-component.adoc | 8 +-
.../ROOT/pages/sap-netweaver-component.adoc | 8 +-
.../modules/ROOT/pages/scheduler-component.adoc | 8 +-
.../modules/ROOT/pages/schematron-component.adoc | 8 +-
.../modules/ROOT/pages/scp-component.adoc | 8 +-
.../modules/ROOT/pages/seda-component.adoc | 8 +-
.../modules/ROOT/pages/service-component.adoc | 8 +-
.../modules/ROOT/pages/servicenow-component.adoc | 8 +-
.../modules/ROOT/pages/servlet-component.adoc | 8 +-
.../modules/ROOT/pages/sftp-component.adoc | 4 +-
.../modules/ROOT/pages/sip-component.adoc | 8 +-
.../modules/ROOT/pages/sjms-batch-component.adoc | 8 +-
.../modules/ROOT/pages/sjms-component.adoc | 8 +-
.../modules/ROOT/pages/sjms2-component.adoc | 8 +-
.../modules/ROOT/pages/slack-component.adoc | 8 +-
.../modules/ROOT/pages/smpp-component.adoc | 8 +-
.../modules/ROOT/pages/snmp-component.adoc | 8 +-
.../modules/ROOT/pages/solr-component.adoc | 8 +-
.../modules/ROOT/pages/soroush-component.adoc | 8 +-
.../modules/ROOT/pages/spark-component.adoc | 8 +-
.../modules/ROOT/pages/spark-rest-component.adoc | 4 +-
.../modules/ROOT/pages/splunk-component.adoc | 8 +-
.../modules/ROOT/pages/spring-batch-component.adoc | 8 +-
.../components/modules/ROOT/pages/spring-boot.adoc | 5 +-
.../modules/ROOT/pages/spring-event-component.adoc | 8 +-
.../ROOT/pages/spring-integration-component.adoc | 8 +-
.../modules/ROOT/pages/spring-ldap-component.adoc | 8 +-
.../modules/ROOT/pages/spring-redis-component.adoc | 8 +-
.../modules/ROOT/pages/spring-ws-component.adoc | 8 +-
.../modules/ROOT/pages/sql-component.adoc | 8 +-
.../modules/ROOT/pages/sql-stored-component.adoc | 8 +-
.../modules/ROOT/pages/ssh-component.adoc | 8 +-
.../modules/ROOT/pages/stax-component.adoc | 8 +-
.../modules/ROOT/pages/stomp-component.adoc | 8 +-
.../modules/ROOT/pages/stream-component.adoc | 8 +-
.../ROOT/pages/string-template-component.adoc | 8 +-
.../modules/ROOT/pages/stub-component.adoc | 8 +-
.../modules/ROOT/pages/telegram-component.adoc | 8 +-
.../modules/ROOT/pages/thrift-component.adoc | 8 +-
.../modules/ROOT/pages/thrift-dataformat.adoc | 4 +-
.../modules/ROOT/pages/tika-component.adoc | 8 +-
.../modules/ROOT/pages/timer-component.adoc | 8 +-
.../modules/ROOT/pages/twilio-component.adoc | 8 +-
.../pages/twitter-directmessage-component.adoc | 8 +-
.../ROOT/pages/twitter-search-component.adoc | 8 +-
.../ROOT/pages/twitter-timeline-component.adoc | 8 +-
.../modules/ROOT/pages/undertow-component.adoc | 8 +-
.../modules/ROOT/pages/validator-component.adoc | 8 +-
.../modules/ROOT/pages/velocity-component.adoc | 8 +-
.../modules/ROOT/pages/vertx-component.adoc | 8 +-
.../modules/ROOT/pages/vm-component.adoc | 8 +-
.../modules/ROOT/pages/weather-component.adoc | 8 +-
.../modules/ROOT/pages/web3j-component.adoc | 8 +-
.../modules/ROOT/pages/webhook-component.adoc | 8 +-
.../modules/ROOT/pages/websocket-component.adoc | 8 +-
.../ROOT/pages/websocket-jsr356-component.adoc | 8 +-
.../modules/ROOT/pages/wordpress-component.adoc | 8 +-
.../modules/ROOT/pages/xchange-component.adoc | 8 +-
.../modules/ROOT/pages/xj-component.adoc | 8 +-
.../modules/ROOT/pages/xmlsecurity-component.adoc | 8 +-
.../modules/ROOT/pages/xmpp-component.adoc | 8 +-
.../modules/ROOT/pages/xquery-component.adoc | 8 +-
.../modules/ROOT/pages/xquery-language.adoc | 4 +-
.../modules/ROOT/pages/xslt-component.adoc | 8 +-
.../modules/ROOT/pages/yammer-component.adoc | 8 +-
.../modules/ROOT/pages/zendesk-component.adoc | 8 +-
.../modules/ROOT/pages/zookeeper-component.adoc | 8 +-
.../ROOT/pages/zookeeper-master-component.adoc | 8 +-
.../springboot/ActiveMQComponentConfiguration.java | 36 +++++++++
.../ahc/springboot/AhcComponentConfiguration.java | 36 +++++++++
.../ws/springboot/WsComponentConfiguration.java | 36 +++++++++
.../springboot/AMQPComponentConfiguration.java | 36 +++++++++
.../springboot/ApnsComponentConfiguration.java | 36 +++++++++
.../as2/springboot/AS2ComponentConfiguration.java | 36 +++++++++
.../springboot/AsteriskComponentConfiguration.java | 36 +++++++++
.../springboot/AtmosComponentConfiguration.java | 36 +++++++++
.../WebsocketComponentConfiguration.java | 36 +++++++++
.../springboot/AtomComponentConfiguration.java | 36 +++++++++
.../AtomixMapComponentConfiguration.java | 36 +++++++++
.../AtomixMessagingComponentConfiguration.java | 36 +++++++++
.../AtomixMultiMapComponentConfiguration.java | 36 +++++++++
.../AtomixQueueComponentConfiguration.java | 36 +++++++++
.../AtomixSetComponentConfiguration.java | 36 +++++++++
.../AtomixValueComponentConfiguration.java | 36 +++++++++
.../springboot/AvroComponentConfiguration.java | 36 +++++++++
.../cw/springboot/CwComponentConfiguration.java | 36 +++++++++
.../ddb/springboot/DdbComponentConfiguration.java | 36 +++++++++
.../DdbStreamComponentConfiguration.java | 36 +++++++++
.../ec2/springboot/EC2ComponentConfiguration.java | 36 +++++++++
.../ecs/springboot/ECSComponentConfiguration.java | 36 +++++++++
.../eks/springboot/EKSComponentConfiguration.java | 36 +++++++++
.../iam/springboot/IAMComponentConfiguration.java | 36 +++++++++
.../KinesisFirehoseComponentConfiguration.java | 36 +++++++++
.../springboot/KinesisComponentConfiguration.java | 36 +++++++++
.../kms/springboot/KMSComponentConfiguration.java | 36 +++++++++
.../springboot/LambdaComponentConfiguration.java | 36 +++++++++
.../mq/springboot/MQComponentConfiguration.java | 36 +++++++++
.../msk/springboot/MSKComponentConfiguration.java | 36 +++++++++
.../s3/springboot/S3ComponentConfiguration.java | 36 +++++++++
.../sdb/springboot/SdbComponentConfiguration.java | 36 +++++++++
.../ses/springboot/SesComponentConfiguration.java | 36 +++++++++
.../sns/springboot/SnsComponentConfiguration.java | 36 +++++++++
.../sqs/springboot/SqsComponentConfiguration.java | 36 +++++++++
.../swf/springboot/SWFComponentConfiguration.java | 36 +++++++++
.../TranslateComponentConfiguration.java | 36 +++++++++
.../BlobServiceComponentConfiguration.java | 36 +++++++++
.../QueueServiceComponentConfiguration.java | 36 +++++++++
.../springboot/BeanComponentConfiguration.java | 36 +++++++++
.../springboot/ClassComponentConfiguration.java | 36 +++++++++
.../BeanValidatorComponentConfiguration.java | 36 +++++++++
.../BeanstalkComponentConfiguration.java | 36 +++++++++
.../springboot/BonitaComponentConfiguration.java | 36 +++++++++
.../box/springboot/BoxComponentConfiguration.java | 36 +++++++++
.../BraintreeComponentConfiguration.java | 36 +++++++++
.../springboot/BrowseComponentConfiguration.java | 36 +++++++++
.../CaffeineCacheComponentConfiguration.java | 36 +++++++++
.../CaffeineLoadCacheComponentConfiguration.java | 36 +++++++++
.../CassandraComponentConfiguration.java | 36 +++++++++
.../ChatScriptComponentConfiguration.java | 36 +++++++++
.../springboot/ChunkComponentConfiguration.java | 36 +++++++++
.../cm/springboot/CMComponentConfiguration.java | 36 +++++++++
.../springboot/CMISComponentConfiguration.java | 36 +++++++++
.../springboot/CoAPComponentConfiguration.java | 36 +++++++++
.../springboot/CometdComponentConfiguration.java | 36 +++++++++
.../springboot/ConsulComponentConfiguration.java | 36 +++++++++
.../ControlBusComponentConfiguration.java | 36 +++++++++
.../springboot/CordaComponentConfiguration.java | 36 +++++++++
.../CouchbaseComponentConfiguration.java | 36 +++++++++
.../springboot/CouchDbComponentConfiguration.java | 36 +++++++++
.../CryptoCmsComponentConfiguration.java | 36 +++++++++
.../DigitalSignatureComponentConfiguration.java | 36 +++++++++
.../springboot/CxfRsComponentConfiguration.java | 36 +++++++++
.../cxf/springboot/CxfComponentConfiguration.java | 36 +++++++++
.../DataFormatComponentConfiguration.java | 36 +++++++++
.../springboot/DataSetComponentConfiguration.java | 36 +++++++++
.../DataSetTestComponentConfiguration.java | 36 +++++++++
.../DebeziumMongodbComponentConfiguration.java | 36 +++++++++
.../DebeziumMySqlComponentConfiguration.java | 36 +++++++++
.../DebeziumPostgresComponentConfiguration.java | 36 +++++++++
.../DebeziumSqlserverComponentConfiguration.java | 36 +++++++++
.../DigitalOceanComponentConfiguration.java | 36 +++++++++
.../springboot/DirectComponentConfiguration.java | 36 +++++++++
.../springboot/DirectVmComponentConfiguration.java | 36 +++++++++
.../DisruptorComponentConfiguration.java | 36 +++++++++
.../DisruptorVmComponentConfiguration.java | 36 +++++++++
.../dns/springboot/DnsComponentConfiguration.java | 36 +++++++++
.../springboot/DockerComponentConfiguration.java | 36 +++++++++
.../springboot/DozerComponentConfiguration.java | 36 +++++++++
.../springboot/DrillComponentConfiguration.java | 36 +++++++++
.../springboot/DropboxComponentConfiguration.java | 36 +++++++++
.../springboot/EhcacheComponentConfiguration.java | 36 +++++++++
.../ElasticsearchComponentConfiguration.java | 36 +++++++++
.../springboot/ElsqlComponentConfiguration.java | 36 +++++++++
.../springboot/EtcdComponentConfiguration.java | 36 +++++++++
.../springboot/ExecComponentConfiguration.java | 36 +++++++++
.../springboot/FacebookComponentConfiguration.java | 36 +++++++++
.../springboot/FhirComponentConfiguration.java | 36 +++++++++
.../springboot/FileComponentConfiguration.java | 36 +++++++++
.../FileWatchComponentConfiguration.java | 36 +++++++++
.../springboot/FlatpackComponentConfiguration.java | 36 +++++++++
.../springboot/FlinkComponentConfiguration.java | 36 +++++++++
.../fop/springboot/FopComponentConfiguration.java | 36 +++++++++
.../FreemarkerComponentConfiguration.java | 36 +++++++++
.../springboot/FtpComponentConfiguration.java | 36 +++++++++
.../springboot/FtpsComponentConfiguration.java | 36 +++++++++
.../springboot/SftpComponentConfiguration.java | 36 +++++++++
.../springboot/GangliaComponentConfiguration.java | 36 +++++++++
.../springboot/GeoCoderComponentConfiguration.java | 36 +++++++++
.../git/springboot/GitComponentConfiguration.java | 36 +++++++++
.../springboot/GitHubComponentConfiguration.java | 36 +++++++++
.../GoogleBigQueryComponentConfiguration.java | 36 +++++++++
.../GoogleBigQuerySQLComponentConfiguration.java | 36 +++++++++
.../GoogleCalendarComponentConfiguration.java | 36 +++++++++
...GoogleCalendarStreamComponentConfiguration.java | 36 +++++++++
.../GoogleDriveComponentConfiguration.java | 36 +++++++++
.../GoogleMailComponentConfiguration.java | 36 +++++++++
.../GoogleMailStreamComponentConfiguration.java | 36 +++++++++
.../GooglePubsubComponentConfiguration.java | 36 +++++++++
.../GoogleSheetsComponentConfiguration.java | 36 +++++++++
.../GoogleSheetsStreamComponentConfiguration.java | 36 +++++++++
.../springboot/GoraComponentConfiguration.java | 36 +++++++++
.../springboot/GraphqlComponentConfiguration.java | 36 +++++++++
.../springboot/GrpcComponentConfiguration.java | 36 +++++++++
.../GuavaEventBusComponentConfiguration.java | 36 +++++++++
...azelcastAtomicnumberComponentConfiguration.java | 36 +++++++++
.../HazelcastInstanceComponentConfiguration.java | 36 +++++++++
.../HazelcastListComponentConfiguration.java | 36 +++++++++
.../HazelcastMapComponentConfiguration.java | 36 +++++++++
.../HazelcastMultimapComponentConfiguration.java | 36 +++++++++
.../HazelcastQueueComponentConfiguration.java | 36 +++++++++
...zelcastReplicatedmapComponentConfiguration.java | 36 +++++++++
.../HazelcastRingbufferComponentConfiguration.java | 36 +++++++++
.../HazelcastSedaComponentConfiguration.java | 36 +++++++++
.../HazelcastSetComponentConfiguration.java | 36 +++++++++
.../HazelcastTopicComponentConfiguration.java | 36 +++++++++
.../springboot/HBaseComponentConfiguration.java | 36 +++++++++
.../springboot/HdfsComponentConfiguration.java | 36 +++++++++
.../springboot/HipchatComponentConfiguration.java | 36 +++++++++
.../springboot/HttpComponentConfiguration.java | 36 +++++++++
.../springboot/ClientComponentConfiguration.java | 36 +++++++++
.../springboot/ServerComponentConfiguration.java | 36 +++++++++
.../IgniteCacheComponentConfiguration.java | 36 +++++++++
.../IgniteComputeComponentConfiguration.java | 36 +++++++++
.../IgniteEventsComponentConfiguration.java | 36 +++++++++
.../IgniteIdGenComponentConfiguration.java | 36 +++++++++
.../IgniteMessagingComponentConfiguration.java | 36 +++++++++
.../IgniteQueueComponentConfiguration.java | 36 +++++++++
.../IgniteSetComponentConfiguration.java | 36 +++++++++
.../InfinispanComponentConfiguration.java | 36 +++++++++
.../springboot/InfluxDbComponentConfiguration.java | 36 +++++++++
.../springboot/IOTAComponentConfiguration.java | 36 +++++++++
.../springboot/IPFSComponentConfiguration.java | 36 +++++++++
.../irc/springboot/IrcComponentConfiguration.java | 36 +++++++++
.../springboot/IronMQComponentConfiguration.java | 36 +++++++++
.../springboot/JBPMComponentConfiguration.java | 36 +++++++++
.../springboot/JCacheComponentConfiguration.java | 36 +++++++++
.../springboot/JcloudsComponentConfiguration.java | 36 +++++++++
.../jcr/springboot/JcrComponentConfiguration.java | 36 +++++++++
.../springboot/JdbcComponentConfiguration.java | 36 +++++++++
.../JettyHttpComponentConfiguration9.java | 36 +++++++++
.../JGroupsRaftComponentConfiguration.java | 36 +++++++++
.../springboot/JGroupsComponentConfiguration.java | 36 +++++++++
.../springboot/JingComponentConfiguration.java | 36 +++++++++
.../springboot/JiraComponentConfiguration.java | 36 +++++++++
.../jms/springboot/JmsComponentConfiguration.java | 36 +++++++++
.../jmx/springboot/JMXComponentConfiguration.java | 36 +++++++++
.../springboot/JoltComponentConfiguration.java | 36 +++++++++
.../springboot/JooqComponentConfiguration.java | 36 +++++++++
.../jpa/springboot/JpaComponentConfiguration.java | 36 +++++++++
.../scp/springboot/ScpComponentConfiguration.java | 36 +++++++++
.../JsonValidatorComponentConfiguration.java | 36 +++++++++
.../springboot/Jt400ComponentConfiguration.java | 36 +++++++++
.../springboot/KafkaComponentConfiguration.java | 36 +++++++++
...KubernetesConfigMapsComponentConfiguration.java | 36 +++++++++
...ubernetesDeploymentsComponentConfiguration.java | 36 +++++++++
.../KubernetesHPAComponentConfiguration.java | 36 +++++++++
.../KubernetesJobComponentConfiguration.java | 36 +++++++++
...KubernetesNamespacesComponentConfiguration.java | 36 +++++++++
.../KubernetesNodesComponentConfiguration.java | 36 +++++++++
...tesPersistentVolumesComponentConfiguration.java | 36 +++++++++
...sistentVolumesClaimsComponentConfiguration.java | 36 +++++++++
.../KubernetesPodsComponentConfiguration.java | 36 +++++++++
...plicationControllersComponentConfiguration.java | 36 +++++++++
...rnetesResourcesQuotaComponentConfiguration.java | 36 +++++++++
.../KubernetesSecretsComponentConfiguration.java | 36 +++++++++
...netesServiceAccountsComponentConfiguration.java | 36 +++++++++
.../KubernetesServicesComponentConfiguration.java | 36 +++++++++
...penshiftBuildConfigsComponentConfiguration.java | 36 +++++++++
.../OpenshiftBuildsComponentConfiguration.java | 36 +++++++++
.../springboot/KuduComponentConfiguration.java | 36 +++++++++
.../springboot/LanguageComponentConfiguration.java | 36 +++++++++
.../springboot/LdapComponentConfiguration.java | 36 +++++++++
.../springboot/LdifComponentConfiguration.java | 36 +++++++++
.../log/springboot/LogComponentConfiguration.java | 36 +++++++++
.../springboot/LuceneComponentConfiguration.java | 36 +++++++++
.../LumberjackComponentConfiguration.java | 36 +++++++++
.../springboot/MailComponentConfiguration.java | 36 +++++++++
.../springboot/MasterComponentConfiguration.java | 36 +++++++++
.../springboot/MetricsComponentConfiguration.java | 36 +++++++++
.../MicrometerComponentConfiguration.java | 36 +++++++++
.../MiloClientComponentConfiguration.java | 36 +++++++++
.../MiloServerComponentConfiguration.java | 36 +++++++++
.../springboot/MinaComponentConfiguration.java | 36 +++++++++
.../springboot/MllpComponentConfiguration.java | 36 +++++++++
.../springboot/MockComponentConfiguration.java | 36 +++++++++
.../springboot/GridFsComponentConfiguration.java | 36 +++++++++
.../springboot/MongoDbComponentConfiguration.java | 36 +++++++++
.../msv/springboot/MsvComponentConfiguration.java | 36 +++++++++
.../springboot/MustacheComponentConfiguration.java | 36 +++++++++
.../springboot/MvelComponentConfiguration.java | 36 +++++++++
.../MyBatisBeanComponentConfiguration.java | 36 +++++++++
.../springboot/MyBatisComponentConfiguration.java | 36 +++++++++
.../springboot/NagiosComponentConfiguration.java | 36 +++++++++
.../springboot/NatsComponentConfiguration.java | 36 +++++++++
.../NettyHttpComponentConfiguration.java | 36 +++++++++
.../springboot/NettyComponentConfiguration.java | 36 +++++++++
.../springboot/NitriteComponentConfiguration.java | 36 +++++++++
.../nsq/springboot/NsqComponentConfiguration.java | 36 +++++++++
.../springboot/Olingo2ComponentConfiguration.java | 36 +++++++++
.../springboot/Olingo4ComponentConfiguration.java | 36 +++++++++
.../springboot/CinderComponentConfiguration.java | 36 +++++++++
.../springboot/GlanceComponentConfiguration.java | 36 +++++++++
.../springboot/KeystoneComponentConfiguration.java | 36 +++++++++
.../springboot/NeutronComponentConfiguration.java | 36 +++++++++
.../springboot/NovaComponentConfiguration.java | 36 +++++++++
.../springboot/SwiftComponentConfiguration.java | 36 +++++++++
.../OptaPlannerComponentConfiguration.java | 36 +++++++++
.../springboot/PahoComponentConfiguration.java | 36 +++++++++
.../pdf/springboot/PdfComponentConfiguration.java | 36 +++++++++
.../PgReplicationSlotComponentConfiguration.java | 36 +++++++++
.../springboot/PgEventComponentConfiguration.java | 36 +++++++++
.../springboot/PrinterComponentConfiguration.java | 36 +++++++++
.../springboot/PubNubComponentConfiguration.java | 36 +++++++++
.../springboot/PulsarComponentConfiguration.java | 36 +++++++++
.../springboot/QuartzComponentConfiguration.java | 36 +++++++++
.../QuickfixjComponentConfiguration.java | 36 +++++++++
.../springboot/RabbitMQComponentConfiguration.java | 36 +++++++++
.../ReactiveStreamsComponentConfiguration.java | 36 +++++++++
.../ref/springboot/RefComponentConfiguration.java | 36 +++++++++
.../springboot/RestApiComponentConfiguration.java | 36 +++++++++
.../springboot/RestComponentConfiguration.java | 36 +++++++++
.../RestSwaggerComponentConfiguration.java | 36 +++++++++
.../RobotFrameworkComponentConfiguration.java | 36 +++++++++
.../rss/springboot/RssComponentConfiguration.java | 36 +++++++++
.../springboot/SagaComponentConfiguration.java | 36 +++++++++
.../SalesforceComponentConfiguration.java | 36 +++++++++
.../NetWeaverComponentConfiguration.java | 36 +++++++++
.../springboot/XQueryComponentConfiguration.java | 36 +++++++++
.../SchedulerComponentConfiguration.java | 36 +++++++++
.../SchematronComponentConfiguration.java | 36 +++++++++
.../springboot/SedaComponentConfiguration.java | 36 +++++++++
.../springboot/ServiceComponentConfiguration.java | 36 +++++++++
.../ServiceNowComponentConfiguration.java | 36 +++++++++
.../springboot/ServletComponentConfiguration.java | 36 +++++++++
.../sip/springboot/SipComponentConfiguration.java | 36 +++++++++
.../SjmsBatchComponentConfiguration.java | 36 +++++++++
.../springboot/SjmsComponentConfiguration.java | 36 +++++++++
.../springboot/Sjms2ComponentConfiguration.java | 36 +++++++++
.../springboot/SlackComponentConfiguration.java | 36 +++++++++
.../springboot/SmppComponentConfiguration.java | 36 +++++++++
.../springboot/SnmpComponentConfiguration.java | 36 +++++++++
.../springboot/SolrComponentConfiguration.java | 36 +++++++++
.../SoroushBotComponentConfiguration.java | 36 +++++++++
.../springboot/SparkComponentConfiguration.java | 36 +++++++++
.../springboot/SplunkComponentConfiguration.java | 36 +++++++++
.../SpringBatchComponentConfiguration.java | 36 +++++++++
.../SpringIntegrationComponentConfiguration.java | 36 +++++++++
.../SpringLdapComponentConfiguration.java | 36 +++++++++
.../springboot/RedisComponentConfiguration.java | 36 +++++++++
.../springboot/EventComponentConfiguration.java | 36 +++++++++
.../SpringWebserviceComponentConfiguration.java | 36 +++++++++
.../sql/springboot/SqlComponentConfiguration.java | 36 +++++++++
.../SqlStoredComponentConfiguration.java | 36 +++++++++
.../ssh/springboot/SshComponentConfiguration.java | 36 +++++++++
.../springboot/StAXComponentConfiguration.java | 36 +++++++++
.../springboot/StompComponentConfiguration.java | 36 +++++++++
.../springboot/StreamComponentConfiguration.java | 36 +++++++++
.../StringTemplateComponentConfiguration.java | 36 +++++++++
.../springboot/StubComponentConfiguration.java | 36 +++++++++
.../springboot/TelegramComponentConfiguration.java | 36 +++++++++
.../springboot/ThriftComponentConfiguration.java | 36 +++++++++
.../springboot/TikaComponentConfiguration.java | 36 +++++++++
.../springboot/TimerComponentConfiguration.java | 36 +++++++++
.../springboot/TwilioComponentConfiguration.java | 36 +++++++++
...TwitterDirectMessageComponentConfiguration.java | 36 +++++++++
.../TwitterSearchComponentConfiguration.java | 36 +++++++++
.../TwitterTimelineComponentConfiguration.java | 36 +++++++++
.../springboot/UndertowComponentConfiguration.java | 36 +++++++++
.../ValidatorComponentConfiguration.java | 36 +++++++++
.../springboot/VelocityComponentConfiguration.java | 36 +++++++++
.../springboot/VertxComponentConfiguration.java | 36 +++++++++
.../vm/springboot/VmComponentConfiguration.java | 36 +++++++++
.../springboot/WeatherComponentConfiguration.java | 36 +++++++++
.../springboot/Web3jComponentConfiguration.java | 36 +++++++++
.../springboot/WebhookComponentConfiguration.java | 36 +++++++++
.../JSR356WebSocketComponentConfiguration.java | 36 +++++++++
.../WebsocketComponentConfiguration.java | 36 +++++++++
.../WordpressComponentConfiguration.java | 36 +++++++++
.../springboot/XChangeComponentConfiguration.java | 36 +++++++++
.../xj/springboot/XJComponentConfiguration.java | 36 +++++++++
.../XmlSignatureComponentConfiguration.java | 36 +++++++++
.../springboot/XmppComponentConfiguration.java | 36 +++++++++
.../springboot/XsltComponentConfiguration.java | 36 +++++++++
.../springboot/YammerComponentConfiguration.java | 36 +++++++++
.../springboot/ZendeskComponentConfiguration.java | 36 +++++++++
.../springboot/MasterComponentConfiguration.java | 36 +++++++++
.../ZooKeeperComponentConfiguration.java | 36 +++++++++
935 files changed, 14713 insertions(+), 1269 deletions(-)
create mode 100644 core/camel-api/src/main/java/org/apache/camel/GlobalEndpointConfiguration.java
delete mode 100644 core/camel-api/src/main/java/org/apache/camel/spi/EndpointPropertyConfigurer.java
copy components/camel-ftp/src/main/java/org/apache/camel/component/file/remote/SftpRemoteFileJCraft.java => core/camel-base/src/main/java/org/apache/camel/impl/engine/DefaultGlobalEndpointConfiguration.java (50%)
[camel] 03/03: CAMEL-14169: Regen options
Posted by da...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git
commit 80c1f9bc79b8ce3ef1cdaff4c2077e426eece6d4
Author: Claus Ibsen <cl...@gmail.com>
AuthorDate: Tue Nov 12 10:31:19 2019 +0100
CAMEL-14169: Regen options
---
.../src/main/docs/activemq-component.adoc | 8 +++--
.../src/main/docs/ahc-ws-component.adoc | 8 +++--
.../camel-ahc/src/main/docs/ahc-component.adoc | 8 +++--
.../camel-amqp/src/main/docs/amqp-component.adoc | 8 +++--
.../camel-apns/src/main/docs/apns-component.adoc | 8 +++--
.../src/main/docs/as2-component.adoc | 8 +++--
.../src/main/docs/asterisk-component.adoc | 8 +++--
.../camel-atmos/src/main/docs/atmos-component.adoc | 8 +++--
.../main/docs/atmosphere-websocket-component.adoc | 8 +++--
.../camel-atom/src/main/docs/atom-component.adoc | 8 +++--
.../src/main/docs/atomix-map-component.adoc | 8 +++--
.../src/main/docs/atomix-messaging-component.adoc | 8 +++--
.../src/main/docs/atomix-multimap-component.adoc | 8 +++--
.../src/main/docs/atomix-queue-component.adoc | 8 +++--
.../src/main/docs/atomix-set-component.adoc | 8 +++--
.../src/main/docs/atomix-value-component.adoc | 8 +++--
.../camel-avro/src/main/docs/avro-component.adoc | 8 +++--
.../camel-avro/src/main/docs/avro-dataformat.adoc | 4 ++-
.../src/main/docs/aws-cw-component.adoc | 8 +++--
.../src/main/docs/aws-ddb-component.adoc | 8 +++--
.../src/main/docs/aws-ddbstream-component.adoc | 8 +++--
.../src/main/docs/aws-ec2-component.adoc | 8 +++--
.../src/main/docs/aws-ecs-component.adoc | 8 +++--
.../src/main/docs/aws-eks-component.adoc | 8 +++--
.../src/main/docs/aws-iam-component.adoc | 8 +++--
.../src/main/docs/aws-kinesis-component.adoc | 8 +++--
.../main/docs/aws-kinesis-firehose-component.adoc | 8 +++--
.../src/main/docs/aws-kms-component.adoc | 8 +++--
.../src/main/docs/aws-lambda-component.adoc | 8 +++--
.../src/main/docs/aws-mq-component.adoc | 8 +++--
.../src/main/docs/aws-msk-component.adoc | 8 +++--
.../src/main/docs/aws-s3-component.adoc | 8 +++--
.../src/main/docs/aws-sdb-component.adoc | 8 +++--
.../src/main/docs/aws-ses-component.adoc | 8 +++--
.../src/main/docs/aws-sns-component.adoc | 8 +++--
.../src/main/docs/aws-sqs-component.adoc | 8 +++--
.../src/main/docs/aws-swf-component.adoc | 8 +++--
.../src/main/docs/aws-translate-component.adoc | 8 +++--
.../src/main/docs/azure-blob-component.adoc | 8 +++--
.../src/main/docs/azure-queue-component.adoc | 8 +++--
.../src/main/docs/bean-validator-component.adoc | 8 +++--
.../camel-bean/src/main/docs/bean-component.adoc | 8 +++--
.../camel-bean/src/main/docs/bean-language.adoc | 4 ++-
.../camel-bean/src/main/docs/class-component.adoc | 4 ++-
.../src/main/docs/beanstalk-component.adoc | 8 +++--
.../src/main/docs/bonita-component.adoc | 8 +++--
.../src/main/docs/box-component.adoc | 8 +++--
.../src/main/docs/braintree-component.adoc | 8 +++--
.../src/main/docs/browse-component.adoc | 8 +++--
.../src/main/docs/caffeine-cache-component.adoc | 8 +++--
.../main/docs/caffeine-loadcache-component.adoc | 8 +++--
.../src/main/docs/cql-component.adoc | 8 +++--
.../src/main/docs/chatscript-component.adoc | 8 +++--
.../camel-chunk/src/main/docs/chunk-component.adoc | 8 +++--
.../src/main/docs/cm-sms-component.adoc | 8 +++--
.../camel-cmis/src/main/docs/cmis-component.adoc | 8 +++--
.../camel-coap/src/main/docs/coap-component.adoc | 8 +++--
.../src/main/docs/cometd-component.adoc | 8 +++--
.../src/main/docs/consul-component.adoc | 8 +++--
.../src/main/docs/controlbus-component.adoc | 8 +++--
.../camel-corda/src/main/docs/corda-component.adoc | 8 +++--
.../src/main/docs/couchbase-component.adoc | 8 +++--
.../src/main/docs/couchdb-component.adoc | 8 +++--
.../src/main/docs/crypto-cms-component.adoc | 8 +++--
.../src/main/docs/crypto-component.adoc | 8 +++--
.../src/main/docs/crypto-dataformat.adoc | 4 ++-
.../camel-cxf/src/main/docs/cxf-component.adoc | 8 +++--
.../camel-cxf/src/main/docs/cxfrs-component.adoc | 8 +++--
.../src/main/docs/dataformat-component.adoc | 8 +++--
.../src/main/docs/dataset-component.adoc | 8 +++--
.../src/main/docs/dataset-test-component.adoc | 8 +++--
.../src/main/docs/debezium-mongodb-component.adoc | 8 +++--
.../src/main/docs/debezium-mysql-component.adoc | 8 +++--
.../src/main/docs/debezium-postgres-component.adoc | 8 +++--
.../main/docs/debezium-sqlserver-component.adoc | 8 +++--
.../src/main/docs/digitalocean-component.adoc | 8 +++--
.../src/main/docs/direct-component.adoc | 8 +++--
.../src/main/docs/direct-vm-component.adoc | 4 ++-
.../src/main/docs/disruptor-component.adoc | 10 ++++--
.../camel-dns/src/main/docs/dns-component.adoc | 8 +++--
.../src/main/docs/docker-component.adoc | 8 +++--
.../camel-dozer/src/main/docs/dozer-component.adoc | 8 +++--
.../camel-drill/src/main/docs/drill-component.adoc | 8 +++--
.../src/main/docs/dropbox-component.adoc | 8 +++--
.../src/main/docs/ehcache-component.adoc | 8 +++--
.../main/docs/elasticsearch-rest-component.adoc | 8 +++--
.../camel-elsql/src/main/docs/elsql-component.adoc | 8 +++--
.../camel-etcd/src/main/docs/etcd-component.adoc | 8 +++--
.../src/main/docs/eventadmin-component.adoc | 4 ++-
.../camel-exec/src/main/docs/exec-component.adoc | 8 +++--
.../src/main/docs/facebook-component.adoc | 8 +++--
.../src/main/docs/fhir-component.adoc | 8 +++--
.../src/main/docs/file-watch-component.adoc | 8 +++--
.../camel-file/src/main/docs/file-component.adoc | 8 +++--
.../src/main/docs/flatpack-component.adoc | 8 +++--
.../src/main/docs/flatpack-dataformat.adoc | 4 ++-
.../camel-flink/src/main/docs/flink-component.adoc | 8 +++--
.../camel-fop/src/main/docs/fop-component.adoc | 8 +++--
.../src/main/docs/freemarker-component.adoc | 8 +++--
.../camel-ftp/src/main/docs/ftp-component.adoc | 8 +++--
.../camel-ftp/src/main/docs/ftps-component.adoc | 8 +++--
.../camel-ftp/src/main/docs/sftp-component.adoc | 4 ++-
.../src/main/docs/ganglia-component.adoc | 8 +++--
.../src/main/docs/geocoder-component.adoc | 8 +++--
.../camel-git/src/main/docs/git-component.adoc | 8 +++--
.../src/main/docs/github-component.adoc | 8 +++--
.../src/main/docs/google-bigquery-component.adoc | 8 +++--
.../main/docs/google-bigquery-sql-component.adoc | 8 +++--
.../src/main/docs/google-calendar-component.adoc | 8 +++--
.../docs/google-calendar-stream-component.adoc | 8 +++--
.../src/main/docs/google-drive-component.adoc | 8 +++--
.../src/main/docs/google-mail-component.adoc | 8 +++--
.../main/docs/google-mail-stream-component.adoc | 8 +++--
.../src/main/docs/google-pubsub-component.adoc | 8 +++--
.../src/main/docs/google-sheets-component.adoc | 8 +++--
.../main/docs/google-sheets-stream-component.adoc | 8 +++--
.../camel-gora/src/main/docs/gora-component.adoc | 8 +++--
.../camel-grape/src/main/docs/grape-component.adoc | 4 ++-
.../src/main/docs/graphql-component.adoc | 8 +++--
.../camel-grpc/src/main/docs/grpc-component.adoc | 8 +++--
.../src/main/docs/guava-eventbus-component.adoc | 8 +++--
.../main/docs/hazelcast-atomicvalue-component.adoc | 8 +++--
.../main/docs/hazelcast-instance-component.adoc | 8 +++--
.../src/main/docs/hazelcast-list-component.adoc | 8 +++--
.../src/main/docs/hazelcast-map-component.adoc | 8 +++--
.../main/docs/hazelcast-multimap-component.adoc | 8 +++--
.../src/main/docs/hazelcast-queue-component.adoc | 8 +++--
.../docs/hazelcast-replicatedmap-component.adoc | 8 +++--
.../main/docs/hazelcast-ringbuffer-component.adoc | 8 +++--
.../src/main/docs/hazelcast-seda-component.adoc | 8 +++--
.../src/main/docs/hazelcast-set-component.adoc | 8 +++--
.../src/main/docs/hazelcast-topic-component.adoc | 8 +++--
.../camel-hbase/src/main/docs/hbase-component.adoc | 8 +++--
.../camel-hdfs/src/main/docs/hdfs-component.adoc | 8 +++--
.../src/main/docs/hipchat-component.adoc | 8 +++--
.../camel-http/src/main/docs/http-component.adoc | 8 +++--
.../src/main/docs/iec60870-client-component.adoc | 8 +++--
.../src/main/docs/iec60870-server-component.adoc | 8 +++--
.../src/main/docs/ignite-cache-component.adoc | 8 +++--
.../src/main/docs/ignite-compute-component.adoc | 8 +++--
.../src/main/docs/ignite-events-component.adoc | 8 +++--
.../src/main/docs/ignite-idgen-component.adoc | 8 +++--
.../src/main/docs/ignite-messaging-component.adoc | 8 +++--
.../src/main/docs/ignite-queue-component.adoc | 8 +++--
.../src/main/docs/ignite-set-component.adoc | 8 +++--
.../src/main/docs/infinispan-component.adoc | 8 +++--
.../src/main/docs/influxdb-component.adoc | 8 +++--
.../camel-iota/src/main/docs/iota-component.adoc | 8 +++--
.../camel-ipfs/src/main/docs/ipfs-component.adoc | 8 +++--
.../camel-irc/src/main/docs/irc-component.adoc | 8 +++--
.../src/main/docs/ironmq-component.adoc | 8 +++--
.../camel-jbpm/src/main/docs/jbpm-component.adoc | 8 +++--
.../src/main/docs/jcache-component.adoc | 8 +++--
.../src/main/docs/jclouds-component.adoc | 8 +++--
.../camel-jcr/src/main/docs/jcr-component.adoc | 8 +++--
.../camel-jdbc/src/main/docs/jdbc-component.adoc | 8 +++--
.../camel-jetty/src/main/docs/jetty-component.adoc | 8 +++--
.../src/main/docs/jgroups-raft-component.adoc | 8 +++--
.../src/main/docs/jgroups-component.adoc | 8 +++--
.../camel-jing/src/main/docs/jing-component.adoc | 8 +++--
.../camel-jira/src/main/docs/jira-component.adoc | 8 +++--
.../camel-jms/src/main/docs/jms-component.adoc | 8 +++--
.../camel-jmx/src/main/docs/jmx-component.adoc | 8 +++--
.../camel-jolt/src/main/docs/jolt-component.adoc | 8 +++--
.../camel-jooq/src/main/docs/jooq-component.adoc | 8 +++--
.../camel-jpa/src/main/docs/jpa-component.adoc | 8 +++--
.../camel-jsch/src/main/docs/scp-component.adoc | 8 +++--
.../src/main/docs/json-validator-component.adoc | 8 +++--
.../camel-jt400/src/main/docs/jt400-component.adoc | 8 +++--
.../camel-kafka/src/main/docs/kafka-component.adoc | 8 +++--
.../docs/kubernetes-config-maps-component.adoc | 8 +++--
.../docs/kubernetes-deployments-component.adoc | 8 +++--
.../src/main/docs/kubernetes-hpa-component.adoc | 8 +++--
.../src/main/docs/kubernetes-job-component.adoc | 8 +++--
.../main/docs/kubernetes-namespaces-component.adoc | 8 +++--
.../src/main/docs/kubernetes-nodes-component.adoc | 8 +++--
...rnetes-persistent-volumes-claims-component.adoc | 8 +++--
.../kubernetes-persistent-volumes-component.adoc | 8 +++--
.../src/main/docs/kubernetes-pods-component.adoc | 8 +++--
...bernetes-replication-controllers-component.adoc | 8 +++--
.../docs/kubernetes-resources-quota-component.adoc | 8 +++--
.../main/docs/kubernetes-secrets-component.adoc | 8 +++--
.../kubernetes-service-accounts-component.adoc | 8 +++--
.../main/docs/kubernetes-services-component.adoc | 8 +++--
.../docs/openshift-build-configs-component.adoc | 4 ++-
.../src/main/docs/openshift-builds-component.adoc | 4 ++-
.../camel-kudu/src/main/docs/kudu-component.adoc | 4 ++-
.../src/main/docs/language-component.adoc | 8 +++--
.../camel-ldap/src/main/docs/ldap-component.adoc | 8 +++--
.../camel-ldif/src/main/docs/ldif-component.adoc | 8 +++--
.../camel-log/src/main/docs/log-component.adoc | 8 +++--
.../src/main/docs/lucene-component.adoc | 8 +++--
.../src/main/docs/lumberjack-component.adoc | 8 +++--
.../camel-mail/src/main/docs/mail-component.adoc | 8 +++--
.../src/main/docs/master-component.adoc | 8 +++--
.../src/main/docs/metrics-component.adoc | 8 +++--
.../src/main/docs/micrometer-component.adoc | 8 +++--
.../main/docs/microprofile-metrics-component.adoc | 4 ++-
.../src/main/docs/milo-client-component.adoc | 8 +++--
.../src/main/docs/milo-server-component.adoc | 8 +++--
.../camel-mina/src/main/docs/mina-component.adoc | 8 +++--
.../camel-mllp/src/main/docs/mllp-component.adoc | 8 +++--
.../camel-mock/src/main/docs/mock-component.adoc | 8 +++--
.../src/main/docs/mongodb-gridfs-component.adoc | 8 +++--
.../src/main/docs/mongodb-component.adoc | 8 +++--
.../camel-msv/src/main/docs/msv-component.adoc | 8 +++--
.../src/main/docs/mustache-component.adoc | 8 +++--
.../camel-mvel/src/main/docs/mvel-component.adoc | 8 +++--
.../camel-mvel/src/main/docs/mvel-language.adoc | 4 ++-
.../src/main/docs/mybatis-bean-component.adoc | 8 +++--
.../src/main/docs/mybatis-component.adoc | 8 +++--
.../src/main/docs/nagios-component.adoc | 8 +++--
.../camel-nats/src/main/docs/nats-component.adoc | 8 +++--
.../src/main/docs/netty-http-component.adoc | 8 +++--
.../camel-netty/src/main/docs/netty-component.adoc | 8 +++--
.../src/main/docs/nitrite-component.adoc | 8 +++--
.../camel-nsq/src/main/docs/nsq-component.adoc | 8 +++--
.../src/main/docs/olingo2-component.adoc | 8 +++--
.../src/main/docs/olingo4-component.adoc | 8 +++--
.../src/main/docs/openstack-cinder-component.adoc | 8 +++--
.../src/main/docs/openstack-glance-component.adoc | 8 +++--
.../main/docs/openstack-keystone-component.adoc | 8 +++--
.../src/main/docs/openstack-neutron-component.adoc | 8 +++--
.../src/main/docs/openstack-nova-component.adoc | 8 +++--
.../src/main/docs/openstack-swift-component.adoc | 8 +++--
.../src/main/docs/optaplanner-component.adoc | 8 +++--
.../camel-paho/src/main/docs/paho-component.adoc | 8 +++--
.../src/main/docs/paxlogging-component.adoc | 4 ++-
.../camel-pdf/src/main/docs/pdf-component.adoc | 8 +++--
.../main/docs/pg-replication-slot-component.adoc | 8 +++--
.../src/main/docs/pgevent-component.adoc | 8 +++--
.../camel-printer/src/main/docs/lpr-component.adoc | 8 +++--
.../src/main/docs/pubnub-component.adoc | 8 +++--
.../src/main/docs/pulsar-component.adoc | 8 +++--
.../src/main/docs/quartz-component.adoc | 8 +++--
.../src/main/docs/quickfix-component.adoc | 8 +++--
.../src/main/docs/rabbitmq-component.adoc | 8 +++--
.../src/main/docs/reactive-streams-component.adoc | 8 +++--
.../camel-ref/src/main/docs/ref-component.adoc | 8 +++--
.../src/main/docs/rest-swagger-component.adoc | 8 +++--
.../src/main/docs/rest-api-component.adoc | 8 +++--
.../camel-rest/src/main/docs/rest-component.adoc | 8 +++--
.../src/main/docs/robotframework-component.adoc | 8 +++--
.../camel-rss/src/main/docs/rss-component.adoc | 8 +++--
.../camel-rss/src/main/docs/rss-dataformat.adoc | 4 ++-
.../camel-saga/src/main/docs/saga-component.adoc | 8 +++--
.../src/main/docs/salesforce-component.adoc | 8 +++--
.../src/main/docs/sap-netweaver-component.adoc | 8 +++--
.../src/main/docs/xquery-component.adoc | 8 +++--
.../camel-saxon/src/main/docs/xquery-language.adoc | 4 ++-
.../src/main/docs/scheduler-component.adoc | 8 +++--
.../src/main/docs/schematron-component.adoc | 8 +++--
.../camel-seda/src/main/docs/seda-component.adoc | 8 +++--
.../src/main/docs/service-component.adoc | 8 +++--
.../src/main/docs/servicenow-component.adoc | 8 +++--
.../src/main/docs/servlet-component.adoc | 8 +++--
.../camel-sip/src/main/docs/sip-component.adoc | 8 +++--
.../src/main/docs/sjms-batch-component.adoc | 8 +++--
.../camel-sjms/src/main/docs/sjms-component.adoc | 8 +++--
.../camel-sjms2/src/main/docs/sjms2-component.adoc | 8 +++--
.../camel-slack/src/main/docs/slack-component.adoc | 8 +++--
.../camel-smpp/src/main/docs/smpp-component.adoc | 8 +++--
.../camel-snmp/src/main/docs/snmp-component.adoc | 8 +++--
.../camel-solr/src/main/docs/solr-component.adoc | 8 +++--
.../src/main/docs/soroush-component.adoc | 8 +++--
.../src/main/docs/spark-rest-component.adoc | 4 ++-
.../camel-spark/src/main/docs/spark-component.adoc | 8 +++--
.../src/main/docs/splunk-component.adoc | 8 +++--
.../src/main/docs/spring-batch-component.adoc | 8 +++--
.../src/main/docs/spring-boot.adoc | 5 ++-
.../spring/boot/CamelConfigurationProperties.java | 29 +++++++++++++++++
.../main/docs/spring-integration-component.adoc | 8 +++--
.../src/main/docs/spring-ldap-component.adoc | 8 +++--
.../src/main/docs/spring-redis-component.adoc | 8 +++--
.../src/main/docs/spring-ws-component.adoc | 8 +++--
.../src/main/docs/spring-event-component.adoc | 8 +++--
.../camel-sql/src/main/docs/sql-component.adoc | 8 +++--
.../src/main/docs/sql-stored-component.adoc | 8 +++--
.../camel-ssh/src/main/docs/ssh-component.adoc | 8 +++--
.../camel-stax/src/main/docs/stax-component.adoc | 8 +++--
.../camel-stomp/src/main/docs/stomp-component.adoc | 8 +++--
.../src/main/docs/stream-component.adoc | 8 +++--
.../src/main/docs/string-template-component.adoc | 8 +++--
.../camel-stub/src/main/docs/stub-component.adoc | 8 +++--
.../src/main/docs/telegram-component.adoc | 8 +++--
.../src/main/docs/thrift-component.adoc | 8 +++--
.../src/main/docs/thrift-dataformat.adoc | 4 ++-
.../camel-tika/src/main/docs/tika-component.adoc | 8 +++--
.../camel-timer/src/main/docs/timer-component.adoc | 8 +++--
.../src/main/docs/twilio-component.adoc | 8 +++--
.../main/docs/twitter-directmessage-component.adoc | 8 +++--
.../src/main/docs/twitter-search-component.adoc | 8 +++--
.../src/main/docs/twitter-timeline-component.adoc | 8 +++--
.../src/main/docs/undertow-component.adoc | 8 +++--
.../src/main/docs/validator-component.adoc | 8 +++--
.../src/main/docs/velocity-component.adoc | 8 +++--
.../camel-vertx/src/main/docs/vertx-component.adoc | 8 +++--
.../camel-vm/src/main/docs/vm-component.adoc | 8 +++--
.../src/main/docs/weather-component.adoc | 8 +++--
.../camel-web3j/src/main/docs/web3j-component.adoc | 8 +++--
.../src/main/docs/webhook-component.adoc | 8 +++--
.../src/main/docs/websocket-jsr356-component.adoc | 8 +++--
.../src/main/docs/websocket-component.adoc | 8 +++--
.../src/main/docs/wordpress-component.adoc | 8 +++--
.../src/main/docs/xchange-component.adoc | 8 +++--
.../camel-xj/src/main/docs/xj-component.adoc | 8 +++--
.../src/main/docs/xmlsecurity-component.adoc | 8 +++--
.../camel-xmpp/src/main/docs/xmpp-component.adoc | 8 +++--
.../camel-xslt/src/main/docs/xslt-component.adoc | 8 +++--
.../src/main/docs/yammer-component.adoc | 8 +++--
.../src/main/docs/zendesk-component.adoc | 8 +++--
.../src/main/docs/zookeeper-master-component.adoc | 8 +++--
.../src/main/docs/zookeeper-component.adoc | 8 +++--
.../camel-main-configuration-metadata.json | 18 +++++++++++
.../modules/ROOT/pages/activemq-component.adoc | 8 +++--
.../modules/ROOT/pages/ahc-component.adoc | 8 +++--
.../modules/ROOT/pages/ahc-ws-component.adoc | 8 +++--
.../modules/ROOT/pages/amqp-component.adoc | 8 +++--
.../modules/ROOT/pages/apns-component.adoc | 8 +++--
.../modules/ROOT/pages/as2-component.adoc | 8 +++--
.../modules/ROOT/pages/asterisk-component.adoc | 8 +++--
.../modules/ROOT/pages/atmos-component.adoc | 8 +++--
.../ROOT/pages/atmosphere-websocket-component.adoc | 8 +++--
.../modules/ROOT/pages/atom-component.adoc | 8 +++--
.../modules/ROOT/pages/atomix-map-component.adoc | 8 +++--
.../ROOT/pages/atomix-messaging-component.adoc | 8 +++--
.../ROOT/pages/atomix-multimap-component.adoc | 8 +++--
.../modules/ROOT/pages/atomix-queue-component.adoc | 8 +++--
.../modules/ROOT/pages/atomix-set-component.adoc | 8 +++--
.../modules/ROOT/pages/atomix-value-component.adoc | 8 +++--
.../modules/ROOT/pages/avro-component.adoc | 8 +++--
.../modules/ROOT/pages/avro-dataformat.adoc | 4 ++-
.../modules/ROOT/pages/aws-cw-component.adoc | 8 +++--
.../modules/ROOT/pages/aws-ddb-component.adoc | 8 +++--
.../ROOT/pages/aws-ddbstream-component.adoc | 8 +++--
.../modules/ROOT/pages/aws-ec2-component.adoc | 8 +++--
.../modules/ROOT/pages/aws-ecs-component.adoc | 8 +++--
.../modules/ROOT/pages/aws-eks-component.adoc | 8 +++--
.../modules/ROOT/pages/aws-iam-component.adoc | 8 +++--
.../modules/ROOT/pages/aws-kinesis-component.adoc | 8 +++--
.../ROOT/pages/aws-kinesis-firehose-component.adoc | 8 +++--
.../modules/ROOT/pages/aws-kms-component.adoc | 8 +++--
.../modules/ROOT/pages/aws-lambda-component.adoc | 8 +++--
.../modules/ROOT/pages/aws-mq-component.adoc | 8 +++--
.../modules/ROOT/pages/aws-msk-component.adoc | 8 +++--
.../modules/ROOT/pages/aws-s3-component.adoc | 8 +++--
.../modules/ROOT/pages/aws-sdb-component.adoc | 8 +++--
.../modules/ROOT/pages/aws-ses-component.adoc | 8 +++--
.../modules/ROOT/pages/aws-sns-component.adoc | 8 +++--
.../modules/ROOT/pages/aws-sqs-component.adoc | 8 +++--
.../modules/ROOT/pages/aws-swf-component.adoc | 8 +++--
.../ROOT/pages/aws-translate-component.adoc | 8 +++--
.../modules/ROOT/pages/azure-blob-component.adoc | 8 +++--
.../modules/ROOT/pages/azure-queue-component.adoc | 8 +++--
.../modules/ROOT/pages/bean-component.adoc | 8 +++--
.../modules/ROOT/pages/bean-language.adoc | 4 ++-
.../ROOT/pages/bean-validator-component.adoc | 8 +++--
.../modules/ROOT/pages/beanstalk-component.adoc | 8 +++--
.../modules/ROOT/pages/bonita-component.adoc | 8 +++--
.../modules/ROOT/pages/box-component.adoc | 8 +++--
.../modules/ROOT/pages/braintree-component.adoc | 8 +++--
.../modules/ROOT/pages/browse-component.adoc | 8 +++--
.../ROOT/pages/caffeine-cache-component.adoc | 8 +++--
.../ROOT/pages/caffeine-loadcache-component.adoc | 8 +++--
.../modules/ROOT/pages/chatscript-component.adoc | 8 +++--
.../modules/ROOT/pages/chunk-component.adoc | 8 +++--
.../modules/ROOT/pages/class-component.adoc | 4 ++-
.../modules/ROOT/pages/cm-sms-component.adoc | 8 +++--
.../modules/ROOT/pages/cmis-component.adoc | 8 +++--
.../modules/ROOT/pages/coap-component.adoc | 8 +++--
.../modules/ROOT/pages/cometd-component.adoc | 8 +++--
.../modules/ROOT/pages/consul-component.adoc | 8 +++--
.../modules/ROOT/pages/controlbus-component.adoc | 8 +++--
.../modules/ROOT/pages/corda-component.adoc | 8 +++--
.../modules/ROOT/pages/couchbase-component.adoc | 8 +++--
.../modules/ROOT/pages/couchdb-component.adoc | 8 +++--
.../modules/ROOT/pages/cql-component.adoc | 8 +++--
.../modules/ROOT/pages/crypto-cms-component.adoc | 8 +++--
.../modules/ROOT/pages/crypto-component.adoc | 8 +++--
.../modules/ROOT/pages/crypto-dataformat.adoc | 4 ++-
.../modules/ROOT/pages/cxf-component.adoc | 8 +++--
.../modules/ROOT/pages/cxfrs-component.adoc | 8 +++--
.../modules/ROOT/pages/dataformat-component.adoc | 8 +++--
.../modules/ROOT/pages/dataset-component.adoc | 8 +++--
.../modules/ROOT/pages/dataset-test-component.adoc | 8 +++--
.../ROOT/pages/debezium-mongodb-component.adoc | 8 +++--
.../ROOT/pages/debezium-mysql-component.adoc | 8 +++--
.../ROOT/pages/debezium-postgres-component.adoc | 8 +++--
.../ROOT/pages/debezium-sqlserver-component.adoc | 8 +++--
.../modules/ROOT/pages/digitalocean-component.adoc | 8 +++--
.../modules/ROOT/pages/direct-component.adoc | 8 +++--
.../modules/ROOT/pages/direct-vm-component.adoc | 4 ++-
.../modules/ROOT/pages/disruptor-component.adoc | 10 ++++--
.../modules/ROOT/pages/dns-component.adoc | 8 +++--
.../modules/ROOT/pages/docker-component.adoc | 8 +++--
.../modules/ROOT/pages/dozer-component.adoc | 8 +++--
.../modules/ROOT/pages/drill-component.adoc | 8 +++--
.../modules/ROOT/pages/dropbox-component.adoc | 8 +++--
.../modules/ROOT/pages/ehcache-component.adoc | 8 +++--
.../ROOT/pages/elasticsearch-rest-component.adoc | 8 +++--
.../modules/ROOT/pages/elsql-component.adoc | 8 +++--
.../modules/ROOT/pages/etcd-component.adoc | 8 +++--
.../modules/ROOT/pages/eventadmin-component.adoc | 4 ++-
.../modules/ROOT/pages/exec-component.adoc | 8 +++--
.../modules/ROOT/pages/facebook-component.adoc | 8 +++--
.../modules/ROOT/pages/fhir-component.adoc | 8 +++--
.../modules/ROOT/pages/file-component.adoc | 8 +++--
.../modules/ROOT/pages/file-watch-component.adoc | 8 +++--
.../modules/ROOT/pages/flatpack-component.adoc | 8 +++--
.../modules/ROOT/pages/flatpack-dataformat.adoc | 4 ++-
.../modules/ROOT/pages/flink-component.adoc | 8 +++--
.../modules/ROOT/pages/fop-component.adoc | 8 +++--
.../modules/ROOT/pages/freemarker-component.adoc | 8 +++--
.../modules/ROOT/pages/ftp-component.adoc | 8 +++--
.../modules/ROOT/pages/ftps-component.adoc | 8 +++--
.../modules/ROOT/pages/ganglia-component.adoc | 8 +++--
.../modules/ROOT/pages/geocoder-component.adoc | 8 +++--
.../modules/ROOT/pages/git-component.adoc | 8 +++--
.../modules/ROOT/pages/github-component.adoc | 8 +++--
.../ROOT/pages/google-bigquery-component.adoc | 8 +++--
.../ROOT/pages/google-bigquery-sql-component.adoc | 8 +++--
.../ROOT/pages/google-calendar-component.adoc | 8 +++--
.../pages/google-calendar-stream-component.adoc | 8 +++--
.../modules/ROOT/pages/google-drive-component.adoc | 8 +++--
.../modules/ROOT/pages/google-mail-component.adoc | 8 +++--
.../ROOT/pages/google-mail-stream-component.adoc | 8 +++--
.../ROOT/pages/google-pubsub-component.adoc | 8 +++--
.../ROOT/pages/google-sheets-component.adoc | 8 +++--
.../ROOT/pages/google-sheets-stream-component.adoc | 8 +++--
.../modules/ROOT/pages/gora-component.adoc | 8 +++--
.../modules/ROOT/pages/grape-component.adoc | 4 ++-
.../modules/ROOT/pages/graphql-component.adoc | 8 +++--
.../modules/ROOT/pages/grpc-component.adoc | 8 +++--
.../ROOT/pages/guava-eventbus-component.adoc | 8 +++--
.../pages/hazelcast-atomicvalue-component.adoc | 8 +++--
.../ROOT/pages/hazelcast-instance-component.adoc | 8 +++--
.../ROOT/pages/hazelcast-list-component.adoc | 8 +++--
.../ROOT/pages/hazelcast-map-component.adoc | 8 +++--
.../ROOT/pages/hazelcast-multimap-component.adoc | 8 +++--
.../ROOT/pages/hazelcast-queue-component.adoc | 8 +++--
.../pages/hazelcast-replicatedmap-component.adoc | 8 +++--
.../ROOT/pages/hazelcast-ringbuffer-component.adoc | 8 +++--
.../ROOT/pages/hazelcast-seda-component.adoc | 8 +++--
.../ROOT/pages/hazelcast-set-component.adoc | 8 +++--
.../ROOT/pages/hazelcast-topic-component.adoc | 8 +++--
.../modules/ROOT/pages/hbase-component.adoc | 8 +++--
.../modules/ROOT/pages/hdfs-component.adoc | 8 +++--
.../modules/ROOT/pages/hipchat-component.adoc | 8 +++--
.../modules/ROOT/pages/http-component.adoc | 8 +++--
.../ROOT/pages/iec60870-client-component.adoc | 8 +++--
.../ROOT/pages/iec60870-server-component.adoc | 8 +++--
.../modules/ROOT/pages/ignite-cache-component.adoc | 8 +++--
.../ROOT/pages/ignite-compute-component.adoc | 8 +++--
.../ROOT/pages/ignite-events-component.adoc | 8 +++--
.../modules/ROOT/pages/ignite-idgen-component.adoc | 8 +++--
.../ROOT/pages/ignite-messaging-component.adoc | 8 +++--
.../modules/ROOT/pages/ignite-queue-component.adoc | 8 +++--
.../modules/ROOT/pages/ignite-set-component.adoc | 8 +++--
.../modules/ROOT/pages/infinispan-component.adoc | 8 +++--
.../modules/ROOT/pages/influxdb-component.adoc | 8 +++--
.../modules/ROOT/pages/iota-component.adoc | 8 +++--
.../modules/ROOT/pages/ipfs-component.adoc | 8 +++--
.../modules/ROOT/pages/irc-component.adoc | 8 +++--
.../modules/ROOT/pages/ironmq-component.adoc | 8 +++--
.../modules/ROOT/pages/jbpm-component.adoc | 8 +++--
.../modules/ROOT/pages/jcache-component.adoc | 8 +++--
.../modules/ROOT/pages/jclouds-component.adoc | 8 +++--
.../modules/ROOT/pages/jcr-component.adoc | 8 +++--
.../modules/ROOT/pages/jdbc-component.adoc | 8 +++--
.../modules/ROOT/pages/jetty-component.adoc | 8 +++--
.../modules/ROOT/pages/jgroups-component.adoc | 8 +++--
.../modules/ROOT/pages/jgroups-raft-component.adoc | 8 +++--
.../modules/ROOT/pages/jing-component.adoc | 8 +++--
.../modules/ROOT/pages/jira-component.adoc | 8 +++--
.../modules/ROOT/pages/jms-component.adoc | 8 +++--
.../modules/ROOT/pages/jmx-component.adoc | 8 +++--
.../modules/ROOT/pages/jolt-component.adoc | 8 +++--
.../modules/ROOT/pages/jooq-component.adoc | 8 +++--
.../modules/ROOT/pages/jpa-component.adoc | 8 +++--
.../ROOT/pages/json-validator-component.adoc | 8 +++--
.../modules/ROOT/pages/jt400-component.adoc | 8 +++--
.../modules/ROOT/pages/kafka-component.adoc | 8 +++--
.../pages/kubernetes-config-maps-component.adoc | 8 +++--
.../pages/kubernetes-deployments-component.adoc | 8 +++--
.../ROOT/pages/kubernetes-hpa-component.adoc | 8 +++--
.../ROOT/pages/kubernetes-job-component.adoc | 8 +++--
.../pages/kubernetes-namespaces-component.adoc | 8 +++--
.../ROOT/pages/kubernetes-nodes-component.adoc | 8 +++--
...rnetes-persistent-volumes-claims-component.adoc | 8 +++--
.../kubernetes-persistent-volumes-component.adoc | 8 +++--
.../ROOT/pages/kubernetes-pods-component.adoc | 8 +++--
...bernetes-replication-controllers-component.adoc | 8 +++--
.../kubernetes-resources-quota-component.adoc | 8 +++--
.../ROOT/pages/kubernetes-secrets-component.adoc | 8 +++--
.../kubernetes-service-accounts-component.adoc | 8 +++--
.../ROOT/pages/kubernetes-services-component.adoc | 8 +++--
.../modules/ROOT/pages/kudu-component.adoc | 4 ++-
.../modules/ROOT/pages/language-component.adoc | 8 +++--
.../modules/ROOT/pages/ldap-component.adoc | 8 +++--
.../modules/ROOT/pages/ldif-component.adoc | 8 +++--
.../modules/ROOT/pages/log-component.adoc | 8 +++--
.../modules/ROOT/pages/lpr-component.adoc | 8 +++--
.../modules/ROOT/pages/lucene-component.adoc | 8 +++--
.../modules/ROOT/pages/lumberjack-component.adoc | 8 +++--
.../modules/ROOT/pages/mail-component.adoc | 8 +++--
.../modules/ROOT/pages/master-component.adoc | 8 +++--
.../modules/ROOT/pages/metrics-component.adoc | 8 +++--
.../modules/ROOT/pages/micrometer-component.adoc | 8 +++--
.../ROOT/pages/microprofile-metrics-component.adoc | 4 ++-
.../modules/ROOT/pages/milo-client-component.adoc | 8 +++--
.../modules/ROOT/pages/milo-server-component.adoc | 8 +++--
.../modules/ROOT/pages/mina-component.adoc | 8 +++--
.../modules/ROOT/pages/mllp-component.adoc | 8 +++--
.../modules/ROOT/pages/mock-component.adoc | 8 +++--
.../modules/ROOT/pages/mongodb-component.adoc | 8 +++--
.../ROOT/pages/mongodb-gridfs-component.adoc | 8 +++--
.../modules/ROOT/pages/msv-component.adoc | 8 +++--
.../modules/ROOT/pages/mustache-component.adoc | 8 +++--
.../modules/ROOT/pages/mvel-component.adoc | 8 +++--
.../modules/ROOT/pages/mvel-language.adoc | 4 ++-
.../modules/ROOT/pages/mybatis-bean-component.adoc | 8 +++--
.../modules/ROOT/pages/mybatis-component.adoc | 8 +++--
.../modules/ROOT/pages/nagios-component.adoc | 8 +++--
.../modules/ROOT/pages/nats-component.adoc | 8 +++--
.../modules/ROOT/pages/netty-component.adoc | 8 +++--
.../modules/ROOT/pages/netty-http-component.adoc | 8 +++--
.../modules/ROOT/pages/nitrite-component.adoc | 8 +++--
.../modules/ROOT/pages/nsq-component.adoc | 8 +++--
.../modules/ROOT/pages/olingo2-component.adoc | 8 +++--
.../modules/ROOT/pages/olingo4-component.adoc | 8 +++--
.../pages/openshift-build-configs-component.adoc | 4 ++-
.../ROOT/pages/openshift-builds-component.adoc | 4 ++-
.../ROOT/pages/openstack-cinder-component.adoc | 8 +++--
.../ROOT/pages/openstack-glance-component.adoc | 8 +++--
.../ROOT/pages/openstack-keystone-component.adoc | 8 +++--
.../ROOT/pages/openstack-neutron-component.adoc | 8 +++--
.../ROOT/pages/openstack-nova-component.adoc | 8 +++--
.../ROOT/pages/openstack-swift-component.adoc | 8 +++--
.../modules/ROOT/pages/optaplanner-component.adoc | 8 +++--
.../modules/ROOT/pages/paho-component.adoc | 8 +++--
.../modules/ROOT/pages/paxlogging-component.adoc | 4 ++-
.../modules/ROOT/pages/pdf-component.adoc | 8 +++--
.../ROOT/pages/pg-replication-slot-component.adoc | 8 +++--
.../modules/ROOT/pages/pgevent-component.adoc | 8 +++--
.../modules/ROOT/pages/pubnub-component.adoc | 8 +++--
.../modules/ROOT/pages/pulsar-component.adoc | 8 +++--
.../modules/ROOT/pages/quartz-component.adoc | 8 +++--
.../modules/ROOT/pages/quickfix-component.adoc | 8 +++--
.../modules/ROOT/pages/rabbitmq-component.adoc | 8 +++--
.../ROOT/pages/reactive-streams-component.adoc | 8 +++--
.../modules/ROOT/pages/ref-component.adoc | 8 +++--
.../modules/ROOT/pages/rest-api-component.adoc | 8 +++--
.../modules/ROOT/pages/rest-component.adoc | 8 +++--
.../modules/ROOT/pages/rest-swagger-component.adoc | 8 +++--
.../ROOT/pages/robotframework-component.adoc | 8 +++--
.../modules/ROOT/pages/rss-component.adoc | 8 +++--
.../modules/ROOT/pages/rss-dataformat.adoc | 4 ++-
.../modules/ROOT/pages/saga-component.adoc | 8 +++--
.../modules/ROOT/pages/salesforce-component.adoc | 8 +++--
.../ROOT/pages/sap-netweaver-component.adoc | 8 +++--
.../modules/ROOT/pages/scheduler-component.adoc | 8 +++--
.../modules/ROOT/pages/schematron-component.adoc | 8 +++--
.../modules/ROOT/pages/scp-component.adoc | 8 +++--
.../modules/ROOT/pages/seda-component.adoc | 8 +++--
.../modules/ROOT/pages/service-component.adoc | 8 +++--
.../modules/ROOT/pages/servicenow-component.adoc | 8 +++--
.../modules/ROOT/pages/servlet-component.adoc | 8 +++--
.../modules/ROOT/pages/sftp-component.adoc | 4 ++-
.../modules/ROOT/pages/sip-component.adoc | 8 +++--
.../modules/ROOT/pages/sjms-batch-component.adoc | 8 +++--
.../modules/ROOT/pages/sjms-component.adoc | 8 +++--
.../modules/ROOT/pages/sjms2-component.adoc | 8 +++--
.../modules/ROOT/pages/slack-component.adoc | 8 +++--
.../modules/ROOT/pages/smpp-component.adoc | 8 +++--
.../modules/ROOT/pages/snmp-component.adoc | 8 +++--
.../modules/ROOT/pages/solr-component.adoc | 8 +++--
.../modules/ROOT/pages/soroush-component.adoc | 8 +++--
.../modules/ROOT/pages/spark-component.adoc | 8 +++--
.../modules/ROOT/pages/spark-rest-component.adoc | 4 ++-
.../modules/ROOT/pages/splunk-component.adoc | 8 +++--
.../modules/ROOT/pages/spring-batch-component.adoc | 8 +++--
.../components/modules/ROOT/pages/spring-boot.adoc | 5 ++-
.../modules/ROOT/pages/spring-event-component.adoc | 8 +++--
.../ROOT/pages/spring-integration-component.adoc | 8 +++--
.../modules/ROOT/pages/spring-ldap-component.adoc | 8 +++--
.../modules/ROOT/pages/spring-redis-component.adoc | 8 +++--
.../modules/ROOT/pages/spring-ws-component.adoc | 8 +++--
.../modules/ROOT/pages/sql-component.adoc | 8 +++--
.../modules/ROOT/pages/sql-stored-component.adoc | 8 +++--
.../modules/ROOT/pages/ssh-component.adoc | 8 +++--
.../modules/ROOT/pages/stax-component.adoc | 8 +++--
.../modules/ROOT/pages/stomp-component.adoc | 8 +++--
.../modules/ROOT/pages/stream-component.adoc | 8 +++--
.../ROOT/pages/string-template-component.adoc | 8 +++--
.../modules/ROOT/pages/stub-component.adoc | 8 +++--
.../modules/ROOT/pages/telegram-component.adoc | 8 +++--
.../modules/ROOT/pages/thrift-component.adoc | 8 +++--
.../modules/ROOT/pages/thrift-dataformat.adoc | 4 ++-
.../modules/ROOT/pages/tika-component.adoc | 8 +++--
.../modules/ROOT/pages/timer-component.adoc | 8 +++--
.../modules/ROOT/pages/twilio-component.adoc | 8 +++--
.../pages/twitter-directmessage-component.adoc | 8 +++--
.../ROOT/pages/twitter-search-component.adoc | 8 +++--
.../ROOT/pages/twitter-timeline-component.adoc | 8 +++--
.../modules/ROOT/pages/undertow-component.adoc | 8 +++--
.../modules/ROOT/pages/validator-component.adoc | 8 +++--
.../modules/ROOT/pages/velocity-component.adoc | 8 +++--
.../modules/ROOT/pages/vertx-component.adoc | 8 +++--
.../modules/ROOT/pages/vm-component.adoc | 8 +++--
.../modules/ROOT/pages/weather-component.adoc | 8 +++--
.../modules/ROOT/pages/web3j-component.adoc | 8 +++--
.../modules/ROOT/pages/webhook-component.adoc | 8 +++--
.../modules/ROOT/pages/websocket-component.adoc | 8 +++--
.../ROOT/pages/websocket-jsr356-component.adoc | 8 +++--
.../modules/ROOT/pages/wordpress-component.adoc | 8 +++--
.../modules/ROOT/pages/xchange-component.adoc | 8 +++--
.../modules/ROOT/pages/xj-component.adoc | 8 +++--
.../modules/ROOT/pages/xmlsecurity-component.adoc | 8 +++--
.../modules/ROOT/pages/xmpp-component.adoc | 8 +++--
.../modules/ROOT/pages/xquery-component.adoc | 8 +++--
.../modules/ROOT/pages/xquery-language.adoc | 4 ++-
.../modules/ROOT/pages/xslt-component.adoc | 8 +++--
.../modules/ROOT/pages/yammer-component.adoc | 8 +++--
.../modules/ROOT/pages/zendesk-component.adoc | 8 +++--
.../modules/ROOT/pages/zookeeper-component.adoc | 8 +++--
.../ROOT/pages/zookeeper-master-component.adoc | 8 +++--
.../springboot/ActiveMQComponentConfiguration.java | 36 ++++++++++++++++++++++
.../ahc/springboot/AhcComponentConfiguration.java | 36 ++++++++++++++++++++++
.../ws/springboot/WsComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/AMQPComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/ApnsComponentConfiguration.java | 36 ++++++++++++++++++++++
.../as2/springboot/AS2ComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/AsteriskComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/AtmosComponentConfiguration.java | 36 ++++++++++++++++++++++
.../WebsocketComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/AtomComponentConfiguration.java | 36 ++++++++++++++++++++++
.../AtomixMapComponentConfiguration.java | 36 ++++++++++++++++++++++
.../AtomixMessagingComponentConfiguration.java | 36 ++++++++++++++++++++++
.../AtomixMultiMapComponentConfiguration.java | 36 ++++++++++++++++++++++
.../AtomixQueueComponentConfiguration.java | 36 ++++++++++++++++++++++
.../AtomixSetComponentConfiguration.java | 36 ++++++++++++++++++++++
.../AtomixValueComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/AvroComponentConfiguration.java | 36 ++++++++++++++++++++++
.../cw/springboot/CwComponentConfiguration.java | 36 ++++++++++++++++++++++
.../ddb/springboot/DdbComponentConfiguration.java | 36 ++++++++++++++++++++++
.../DdbStreamComponentConfiguration.java | 36 ++++++++++++++++++++++
.../ec2/springboot/EC2ComponentConfiguration.java | 36 ++++++++++++++++++++++
.../ecs/springboot/ECSComponentConfiguration.java | 36 ++++++++++++++++++++++
.../eks/springboot/EKSComponentConfiguration.java | 36 ++++++++++++++++++++++
.../iam/springboot/IAMComponentConfiguration.java | 36 ++++++++++++++++++++++
.../KinesisFirehoseComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/KinesisComponentConfiguration.java | 36 ++++++++++++++++++++++
.../kms/springboot/KMSComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/LambdaComponentConfiguration.java | 36 ++++++++++++++++++++++
.../mq/springboot/MQComponentConfiguration.java | 36 ++++++++++++++++++++++
.../msk/springboot/MSKComponentConfiguration.java | 36 ++++++++++++++++++++++
.../s3/springboot/S3ComponentConfiguration.java | 36 ++++++++++++++++++++++
.../sdb/springboot/SdbComponentConfiguration.java | 36 ++++++++++++++++++++++
.../ses/springboot/SesComponentConfiguration.java | 36 ++++++++++++++++++++++
.../sns/springboot/SnsComponentConfiguration.java | 36 ++++++++++++++++++++++
.../sqs/springboot/SqsComponentConfiguration.java | 36 ++++++++++++++++++++++
.../swf/springboot/SWFComponentConfiguration.java | 36 ++++++++++++++++++++++
.../TranslateComponentConfiguration.java | 36 ++++++++++++++++++++++
.../BlobServiceComponentConfiguration.java | 36 ++++++++++++++++++++++
.../QueueServiceComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/BeanComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/ClassComponentConfiguration.java | 36 ++++++++++++++++++++++
.../BeanValidatorComponentConfiguration.java | 36 ++++++++++++++++++++++
.../BeanstalkComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/BonitaComponentConfiguration.java | 36 ++++++++++++++++++++++
.../box/springboot/BoxComponentConfiguration.java | 36 ++++++++++++++++++++++
.../BraintreeComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/BrowseComponentConfiguration.java | 36 ++++++++++++++++++++++
.../CaffeineCacheComponentConfiguration.java | 36 ++++++++++++++++++++++
.../CaffeineLoadCacheComponentConfiguration.java | 36 ++++++++++++++++++++++
.../CassandraComponentConfiguration.java | 36 ++++++++++++++++++++++
.../ChatScriptComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/ChunkComponentConfiguration.java | 36 ++++++++++++++++++++++
.../cm/springboot/CMComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/CMISComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/CoAPComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/CometdComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/ConsulComponentConfiguration.java | 36 ++++++++++++++++++++++
.../ControlBusComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/CordaComponentConfiguration.java | 36 ++++++++++++++++++++++
.../CouchbaseComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/CouchDbComponentConfiguration.java | 36 ++++++++++++++++++++++
.../CryptoCmsComponentConfiguration.java | 36 ++++++++++++++++++++++
.../DigitalSignatureComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/CxfRsComponentConfiguration.java | 36 ++++++++++++++++++++++
.../cxf/springboot/CxfComponentConfiguration.java | 36 ++++++++++++++++++++++
.../DataFormatComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/DataSetComponentConfiguration.java | 36 ++++++++++++++++++++++
.../DataSetTestComponentConfiguration.java | 36 ++++++++++++++++++++++
.../DebeziumMongodbComponentConfiguration.java | 36 ++++++++++++++++++++++
.../DebeziumMySqlComponentConfiguration.java | 36 ++++++++++++++++++++++
.../DebeziumPostgresComponentConfiguration.java | 36 ++++++++++++++++++++++
.../DebeziumSqlserverComponentConfiguration.java | 36 ++++++++++++++++++++++
.../DigitalOceanComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/DirectComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/DirectVmComponentConfiguration.java | 36 ++++++++++++++++++++++
.../DisruptorComponentConfiguration.java | 36 ++++++++++++++++++++++
.../DisruptorVmComponentConfiguration.java | 36 ++++++++++++++++++++++
.../dns/springboot/DnsComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/DockerComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/DozerComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/DrillComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/DropboxComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/EhcacheComponentConfiguration.java | 36 ++++++++++++++++++++++
.../ElasticsearchComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/ElsqlComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/EtcdComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/ExecComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/FacebookComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/FhirComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/FileComponentConfiguration.java | 36 ++++++++++++++++++++++
.../FileWatchComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/FlatpackComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/FlinkComponentConfiguration.java | 36 ++++++++++++++++++++++
.../fop/springboot/FopComponentConfiguration.java | 36 ++++++++++++++++++++++
.../FreemarkerComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/FtpComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/FtpsComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/SftpComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/GangliaComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/GeoCoderComponentConfiguration.java | 36 ++++++++++++++++++++++
.../git/springboot/GitComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/GitHubComponentConfiguration.java | 36 ++++++++++++++++++++++
.../GoogleBigQueryComponentConfiguration.java | 36 ++++++++++++++++++++++
.../GoogleBigQuerySQLComponentConfiguration.java | 36 ++++++++++++++++++++++
.../GoogleCalendarComponentConfiguration.java | 36 ++++++++++++++++++++++
...GoogleCalendarStreamComponentConfiguration.java | 36 ++++++++++++++++++++++
.../GoogleDriveComponentConfiguration.java | 36 ++++++++++++++++++++++
.../GoogleMailComponentConfiguration.java | 36 ++++++++++++++++++++++
.../GoogleMailStreamComponentConfiguration.java | 36 ++++++++++++++++++++++
.../GooglePubsubComponentConfiguration.java | 36 ++++++++++++++++++++++
.../GoogleSheetsComponentConfiguration.java | 36 ++++++++++++++++++++++
.../GoogleSheetsStreamComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/GoraComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/GraphqlComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/GrpcComponentConfiguration.java | 36 ++++++++++++++++++++++
.../GuavaEventBusComponentConfiguration.java | 36 ++++++++++++++++++++++
...azelcastAtomicnumberComponentConfiguration.java | 36 ++++++++++++++++++++++
.../HazelcastInstanceComponentConfiguration.java | 36 ++++++++++++++++++++++
.../HazelcastListComponentConfiguration.java | 36 ++++++++++++++++++++++
.../HazelcastMapComponentConfiguration.java | 36 ++++++++++++++++++++++
.../HazelcastMultimapComponentConfiguration.java | 36 ++++++++++++++++++++++
.../HazelcastQueueComponentConfiguration.java | 36 ++++++++++++++++++++++
...zelcastReplicatedmapComponentConfiguration.java | 36 ++++++++++++++++++++++
.../HazelcastRingbufferComponentConfiguration.java | 36 ++++++++++++++++++++++
.../HazelcastSedaComponentConfiguration.java | 36 ++++++++++++++++++++++
.../HazelcastSetComponentConfiguration.java | 36 ++++++++++++++++++++++
.../HazelcastTopicComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/HBaseComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/HdfsComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/HipchatComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/HttpComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/ClientComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/ServerComponentConfiguration.java | 36 ++++++++++++++++++++++
.../IgniteCacheComponentConfiguration.java | 36 ++++++++++++++++++++++
.../IgniteComputeComponentConfiguration.java | 36 ++++++++++++++++++++++
.../IgniteEventsComponentConfiguration.java | 36 ++++++++++++++++++++++
.../IgniteIdGenComponentConfiguration.java | 36 ++++++++++++++++++++++
.../IgniteMessagingComponentConfiguration.java | 36 ++++++++++++++++++++++
.../IgniteQueueComponentConfiguration.java | 36 ++++++++++++++++++++++
.../IgniteSetComponentConfiguration.java | 36 ++++++++++++++++++++++
.../InfinispanComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/InfluxDbComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/IOTAComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/IPFSComponentConfiguration.java | 36 ++++++++++++++++++++++
.../irc/springboot/IrcComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/IronMQComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/JBPMComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/JCacheComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/JcloudsComponentConfiguration.java | 36 ++++++++++++++++++++++
.../jcr/springboot/JcrComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/JdbcComponentConfiguration.java | 36 ++++++++++++++++++++++
.../JettyHttpComponentConfiguration9.java | 36 ++++++++++++++++++++++
.../JGroupsRaftComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/JGroupsComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/JingComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/JiraComponentConfiguration.java | 36 ++++++++++++++++++++++
.../jms/springboot/JmsComponentConfiguration.java | 36 ++++++++++++++++++++++
.../jmx/springboot/JMXComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/JoltComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/JooqComponentConfiguration.java | 36 ++++++++++++++++++++++
.../jpa/springboot/JpaComponentConfiguration.java | 36 ++++++++++++++++++++++
.../scp/springboot/ScpComponentConfiguration.java | 36 ++++++++++++++++++++++
.../JsonValidatorComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/Jt400ComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/KafkaComponentConfiguration.java | 36 ++++++++++++++++++++++
...KubernetesConfigMapsComponentConfiguration.java | 36 ++++++++++++++++++++++
...ubernetesDeploymentsComponentConfiguration.java | 36 ++++++++++++++++++++++
.../KubernetesHPAComponentConfiguration.java | 36 ++++++++++++++++++++++
.../KubernetesJobComponentConfiguration.java | 36 ++++++++++++++++++++++
...KubernetesNamespacesComponentConfiguration.java | 36 ++++++++++++++++++++++
.../KubernetesNodesComponentConfiguration.java | 36 ++++++++++++++++++++++
...tesPersistentVolumesComponentConfiguration.java | 36 ++++++++++++++++++++++
...sistentVolumesClaimsComponentConfiguration.java | 36 ++++++++++++++++++++++
.../KubernetesPodsComponentConfiguration.java | 36 ++++++++++++++++++++++
...plicationControllersComponentConfiguration.java | 36 ++++++++++++++++++++++
...rnetesResourcesQuotaComponentConfiguration.java | 36 ++++++++++++++++++++++
.../KubernetesSecretsComponentConfiguration.java | 36 ++++++++++++++++++++++
...netesServiceAccountsComponentConfiguration.java | 36 ++++++++++++++++++++++
.../KubernetesServicesComponentConfiguration.java | 36 ++++++++++++++++++++++
...penshiftBuildConfigsComponentConfiguration.java | 36 ++++++++++++++++++++++
.../OpenshiftBuildsComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/KuduComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/LanguageComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/LdapComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/LdifComponentConfiguration.java | 36 ++++++++++++++++++++++
.../log/springboot/LogComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/LuceneComponentConfiguration.java | 36 ++++++++++++++++++++++
.../LumberjackComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/MailComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/MasterComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/MetricsComponentConfiguration.java | 36 ++++++++++++++++++++++
.../MicrometerComponentConfiguration.java | 36 ++++++++++++++++++++++
.../MiloClientComponentConfiguration.java | 36 ++++++++++++++++++++++
.../MiloServerComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/MinaComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/MllpComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/MockComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/GridFsComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/MongoDbComponentConfiguration.java | 36 ++++++++++++++++++++++
.../msv/springboot/MsvComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/MustacheComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/MvelComponentConfiguration.java | 36 ++++++++++++++++++++++
.../MyBatisBeanComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/MyBatisComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/NagiosComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/NatsComponentConfiguration.java | 36 ++++++++++++++++++++++
.../NettyHttpComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/NettyComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/NitriteComponentConfiguration.java | 36 ++++++++++++++++++++++
.../nsq/springboot/NsqComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/Olingo2ComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/Olingo4ComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/CinderComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/GlanceComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/KeystoneComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/NeutronComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/NovaComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/SwiftComponentConfiguration.java | 36 ++++++++++++++++++++++
.../OptaPlannerComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/PahoComponentConfiguration.java | 36 ++++++++++++++++++++++
.../pdf/springboot/PdfComponentConfiguration.java | 36 ++++++++++++++++++++++
.../PgReplicationSlotComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/PgEventComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/PrinterComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/PubNubComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/PulsarComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/QuartzComponentConfiguration.java | 36 ++++++++++++++++++++++
.../QuickfixjComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/RabbitMQComponentConfiguration.java | 36 ++++++++++++++++++++++
.../ReactiveStreamsComponentConfiguration.java | 36 ++++++++++++++++++++++
.../ref/springboot/RefComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/RestApiComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/RestComponentConfiguration.java | 36 ++++++++++++++++++++++
.../RestSwaggerComponentConfiguration.java | 36 ++++++++++++++++++++++
.../RobotFrameworkComponentConfiguration.java | 36 ++++++++++++++++++++++
.../rss/springboot/RssComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/SagaComponentConfiguration.java | 36 ++++++++++++++++++++++
.../SalesforceComponentConfiguration.java | 36 ++++++++++++++++++++++
.../NetWeaverComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/XQueryComponentConfiguration.java | 36 ++++++++++++++++++++++
.../SchedulerComponentConfiguration.java | 36 ++++++++++++++++++++++
.../SchematronComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/SedaComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/ServiceComponentConfiguration.java | 36 ++++++++++++++++++++++
.../ServiceNowComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/ServletComponentConfiguration.java | 36 ++++++++++++++++++++++
.../sip/springboot/SipComponentConfiguration.java | 36 ++++++++++++++++++++++
.../SjmsBatchComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/SjmsComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/Sjms2ComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/SlackComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/SmppComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/SnmpComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/SolrComponentConfiguration.java | 36 ++++++++++++++++++++++
.../SoroushBotComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/SparkComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/SplunkComponentConfiguration.java | 36 ++++++++++++++++++++++
.../SpringBatchComponentConfiguration.java | 36 ++++++++++++++++++++++
.../SpringIntegrationComponentConfiguration.java | 36 ++++++++++++++++++++++
.../SpringLdapComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/RedisComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/EventComponentConfiguration.java | 36 ++++++++++++++++++++++
.../SpringWebserviceComponentConfiguration.java | 36 ++++++++++++++++++++++
.../sql/springboot/SqlComponentConfiguration.java | 36 ++++++++++++++++++++++
.../SqlStoredComponentConfiguration.java | 36 ++++++++++++++++++++++
.../ssh/springboot/SshComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/StAXComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/StompComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/StreamComponentConfiguration.java | 36 ++++++++++++++++++++++
.../StringTemplateComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/StubComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/TelegramComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/ThriftComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/TikaComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/TimerComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/TwilioComponentConfiguration.java | 36 ++++++++++++++++++++++
...TwitterDirectMessageComponentConfiguration.java | 36 ++++++++++++++++++++++
.../TwitterSearchComponentConfiguration.java | 36 ++++++++++++++++++++++
.../TwitterTimelineComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/UndertowComponentConfiguration.java | 36 ++++++++++++++++++++++
.../ValidatorComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/VelocityComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/VertxComponentConfiguration.java | 36 ++++++++++++++++++++++
.../vm/springboot/VmComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/WeatherComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/Web3jComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/WebhookComponentConfiguration.java | 36 ++++++++++++++++++++++
.../JSR356WebSocketComponentConfiguration.java | 36 ++++++++++++++++++++++
.../WebsocketComponentConfiguration.java | 36 ++++++++++++++++++++++
.../WordpressComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/XChangeComponentConfiguration.java | 36 ++++++++++++++++++++++
.../xj/springboot/XJComponentConfiguration.java | 36 ++++++++++++++++++++++
.../XmlSignatureComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/XmppComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/XsltComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/YammerComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/ZendeskComponentConfiguration.java | 36 ++++++++++++++++++++++
.../springboot/MasterComponentConfiguration.java | 36 ++++++++++++++++++++++
.../ZooKeeperComponentConfiguration.java | 36 ++++++++++++++++++++++
925 files changed, 14441 insertions(+), 1208 deletions(-)
diff --git a/components/camel-activemq/src/main/docs/activemq-component.adoc b/components/camel-activemq/src/main/docs/activemq-component.adoc
index dc42c4f..1ebed7b 100644
--- a/components/camel-activemq/src/main/docs/activemq-component.adoc
+++ b/components/camel-activemq/src/main/docs/activemq-component.adoc
@@ -48,7 +48,7 @@ activemq:foo
== Component options
// component options: START
-The ActiveMQ component supports 85 options, which are listed below.
+The ActiveMQ component supports 87 options, which are listed below.
@@ -140,6 +140,8 @@ The ActiveMQ component supports 85 options, which are listed below.
| *formatDateHeadersTo Iso8601* (producer) | Sets whether date headers should be formatted according to the ISO 8601 standard. | false | boolean
| *headerFilterStrategy* (filter) | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. | | HeaderFilterStrategy
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -284,7 +286,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 86 options, which are listed below.
+The component supports 88 options, which are listed below.
@@ -303,6 +305,7 @@ The component supports 86 options, which are listed below.
| *camel.component.activemq.async-stop-listener* | Whether to stop the JmsConsumer message listener asynchronously, when stopping a route. | false | Boolean
| *camel.component.activemq.auto-startup* | Specifies whether the consumer container should auto-startup. | true | Boolean
| *camel.component.activemq.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.activemq.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.activemq.broker-u-r-l* | Sets the broker URL to use to connect to ActiveMQ using the ActiveMQ URI format | | String
| *camel.component.activemq.cache-level* | Sets the cache level by ID for the underlying JMS resources. See cacheLevelName option for more details. | | Integer
| *camel.component.activemq.cache-level-name* | Sets the cache level by name for the underlying JMS resources. Possible values are: CACHE_AUTO, CACHE_CONNECTION, CACHE_CONSUMER, CACHE_NONE, and CACHE_SESSION. The default setting is CACHE_AUTO. See the Spring documentation and Transactions Cache Levels for more information. | CACHE_AUTO | String
@@ -336,6 +339,7 @@ The component supports 86 options, which are listed below.
| *camel.component.activemq.jms-key-format-strategy* | Pluggable strategy for encoding and decoding JMS keys so they can be compliant with the JMS specification. Camel provides two implementations out of the box: default and passthrough. The default strategy will safely marshal dots and hyphens (. and -). The passthrough strategy leaves the key as is. Can be used for JMS brokers which do not care whether JMS header keys contain illegal characters. You can provide your own implementation [...]
| *camel.component.activemq.jms-operations* | Allows you to use your own implementation of the org.springframework.jms.core.JmsOperations interface. Camel uses JmsTemplate as default. Can be used for testing purpose, but not used much as stated in the spring API docs. The option is a org.springframework.jms.core.JmsOperations type. | | String
| *camel.component.activemq.lazy-create-transaction-manager* | If true, Camel will create a JmsTransactionManager, if there is no transactionManager injected when option transacted=true. | true | Boolean
+| *camel.component.activemq.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed t [...]
| *camel.component.activemq.map-jms-message* | Specifies whether Camel should auto map the received JMS message to a suited payload type, such as javax.jms.TextMessage to a String etc. See section about how mapping works below for more details. | true | Boolean
| *camel.component.activemq.max-concurrent-consumers* | Specifies the maximum number of concurrent consumers when consuming from JMS (not for request/reply over JMS). See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. When doing request/reply over JMS then the option replyToMaxConcurrentConsumers is used to control number of concurrent consumers on the reply message listener. | | Integer
| *camel.component.activemq.max-messages-per-task* | The number of messages per task. -1 is unlimited. If you use a range for concurrent consumers (eg min max), then this option can be used to set a value to eg 100 to control how fast the consumers will shrink when less work is required. | -1 | Integer
diff --git a/components/camel-ahc-ws/src/main/docs/ahc-ws-component.adoc b/components/camel-ahc-ws/src/main/docs/ahc-ws-component.adoc
index 5be9d7e..a23466d 100644
--- a/components/camel-ahc-ws/src/main/docs/ahc-ws-component.adoc
+++ b/components/camel-ahc-ws/src/main/docs/ahc-ws-component.adoc
@@ -47,7 +47,7 @@ various configuration options of the AHC component.
// component options: START
-The AHC Websocket component supports 8 options, which are listed below.
+The AHC Websocket component supports 10 options, which are listed below.
@@ -62,6 +62,8 @@ The AHC Websocket component supports 8 options, which are listed below.
| *useGlobalSslContext Parameters* (security) | Enable usage of global SSL context parameters. | false | boolean
| *headerFilterStrategy* (filter) | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. | | HeaderFilterStrategy
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -128,7 +130,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 9 options, which are listed below.
+The component supports 11 options, which are listed below.
@@ -138,10 +140,12 @@ The component supports 9 options, which are listed below.
| *camel.component.ahc-ws.allow-java-serialized-object* | Whether to allow java serialization when a request uses context-type=application/x-java-serialized-object This is by default turned off. If you enable this then be aware that Java will deserialize the incoming data from the request to Java and that can be a potential security risk. | false | Boolean
| *camel.component.ahc-ws.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
| *camel.component.ahc-ws.binding* | To use a custom AhcBinding which allows to control how to bind between AHC and Camel. The option is a org.apache.camel.component.ahc.AhcBinding type. | | String
+| *camel.component.ahc-ws.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.ahc-ws.client* | To use a custom AsyncHttpClient. The option is a org.asynchttpclient.AsyncHttpClient type. | | String
| *camel.component.ahc-ws.client-config* | To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance. The option is a org.asynchttpclient.AsyncHttpClientConfig type. | | String
| *camel.component.ahc-ws.enabled* | Enable ahc-ws component | true | Boolean
| *camel.component.ahc-ws.header-filter-strategy* | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. The option is a org.apache.camel.spi.HeaderFilterStrategy type. | | String
+| *camel.component.ahc-ws.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed the [...]
| *camel.component.ahc-ws.ssl-context-parameters* | Reference to a org.apache.camel.support.jsse.SSLContextParameters in the Registry. Note that configuring this option will override any SSL/TLS configuration options provided through the clientConfig option at the endpoint or component level. The option is a org.apache.camel.support.jsse.SSLContextParameters type. | | String
| *camel.component.ahc-ws.use-global-ssl-context-parameters* | Enable usage of global SSL context parameters. | false | Boolean
|===
diff --git a/components/camel-ahc/src/main/docs/ahc-component.adoc b/components/camel-ahc/src/main/docs/ahc-component.adoc
index 59b4b25..5b0fdef 100644
--- a/components/camel-ahc/src/main/docs/ahc-component.adoc
+++ b/components/camel-ahc/src/main/docs/ahc-component.adoc
@@ -106,7 +106,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 9 options, which are listed below.
+The component supports 11 options, which are listed below.
@@ -116,10 +116,12 @@ The component supports 9 options, which are listed below.
| *camel.component.ahc.allow-java-serialized-object* | Whether to allow java serialization when a request uses context-type=application/x-java-serialized-object This is by default turned off. If you enable this then be aware that Java will deserialize the incoming data from the request to Java and that can be a potential security risk. | false | Boolean
| *camel.component.ahc.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
| *camel.component.ahc.binding* | To use a custom AhcBinding which allows to control how to bind between AHC and Camel. The option is a org.apache.camel.component.ahc.AhcBinding type. | | String
+| *camel.component.ahc.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.ahc.client* | To use a custom AsyncHttpClient. The option is a org.asynchttpclient.AsyncHttpClient type. | | String
| *camel.component.ahc.client-config* | To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance. The option is a org.asynchttpclient.AsyncHttpClientConfig type. | | String
| *camel.component.ahc.enabled* | Enable ahc component | true | Boolean
| *camel.component.ahc.header-filter-strategy* | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. The option is a org.apache.camel.spi.HeaderFilterStrategy type. | | String
+| *camel.component.ahc.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then c [...]
| *camel.component.ahc.ssl-context-parameters* | Reference to a org.apache.camel.support.jsse.SSLContextParameters in the Registry. Note that configuring this option will override any SSL/TLS configuration options provided through the clientConfig option at the endpoint or component level. The option is a org.apache.camel.support.jsse.SSLContextParameters type. | | String
| *camel.component.ahc.use-global-ssl-context-parameters* | Enable usage of global SSL context parameters. | false | Boolean
|===
@@ -144,7 +146,7 @@ The component supports 9 options, which are listed below.
// component options: START
-The AHC component supports 8 options, which are listed below.
+The AHC component supports 10 options, which are listed below.
@@ -159,6 +161,8 @@ The AHC component supports 8 options, which are listed below.
| *useGlobalSslContext Parameters* (security) | Enable usage of global SSL context parameters. | false | boolean
| *headerFilterStrategy* (filter) | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. | | HeaderFilterStrategy
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
diff --git a/components/camel-amqp/src/main/docs/amqp-component.adoc b/components/camel-amqp/src/main/docs/amqp-component.adoc
index 452be1c..8aeb96f 100644
--- a/components/camel-amqp/src/main/docs/amqp-component.adoc
+++ b/components/camel-amqp/src/main/docs/amqp-component.adoc
@@ -40,7 +40,7 @@ xref:jms-component.adoc[JMS] component after the destination name.
// component options: START
-The AMQP component supports 80 options, which are listed below.
+The AMQP component supports 82 options, which are listed below.
@@ -127,6 +127,8 @@ The AMQP component supports 80 options, which are listed below.
| *formatDateHeadersTo Iso8601* (producer) | Sets whether date headers should be formatted according to the ISO 8601 standard. | false | boolean
| *headerFilterStrategy* (filter) | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. | | HeaderFilterStrategy
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -273,7 +275,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 81 options, which are listed below.
+The component supports 83 options, which are listed below.
@@ -292,6 +294,7 @@ The component supports 81 options, which are listed below.
| *camel.component.amqp.async-stop-listener* | Whether to stop the JmsConsumer message listener asynchronously, when stopping a route. | false | Boolean
| *camel.component.amqp.auto-startup* | Specifies whether the consumer container should auto-startup. | true | Boolean
| *camel.component.amqp.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.amqp.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.amqp.cache-level* | Sets the cache level by ID for the underlying JMS resources. See cacheLevelName option for more details. | | Integer
| *camel.component.amqp.cache-level-name* | Sets the cache level by name for the underlying JMS resources. Possible values are: CACHE_AUTO, CACHE_CONNECTION, CACHE_CONSUMER, CACHE_NONE, and CACHE_SESSION. The default setting is CACHE_AUTO. See the Spring documentation and Transactions Cache Levels for more information. | CACHE_AUTO | String
| *camel.component.amqp.client-id* | Sets the JMS client ID to use. Note that this value, if specified, must be unique and can only be used by a single JMS connection instance. It is typically only required for durable topic subscriptions. If using Apache ActiveMQ you may prefer to use Virtual Topics instead. | | String
@@ -323,6 +326,7 @@ The component supports 81 options, which are listed below.
| *camel.component.amqp.jms-key-format-strategy* | Pluggable strategy for encoding and decoding JMS keys so they can be compliant with the JMS specification. Camel provides two implementations out of the box: default and passthrough. The default strategy will safely marshal dots and hyphens (. and -). The passthrough strategy leaves the key as is. Can be used for JMS brokers which do not care whether JMS header keys contain illegal characters. You can provide your own implementation of t [...]
| *camel.component.amqp.jms-operations* | Allows you to use your own implementation of the org.springframework.jms.core.JmsOperations interface. Camel uses JmsTemplate as default. Can be used for testing purpose, but not used much as stated in the spring API docs. The option is a org.springframework.jms.core.JmsOperations type. | | String
| *camel.component.amqp.lazy-create-transaction-manager* | If true, Camel will create a JmsTransactionManager, if there is no transactionManager injected when option transacted=true. | true | Boolean
+| *camel.component.amqp.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
| *camel.component.amqp.map-jms-message* | Specifies whether Camel should auto map the received JMS message to a suited payload type, such as javax.jms.TextMessage to a String etc. See section about how mapping works below for more details. | true | Boolean
| *camel.component.amqp.max-concurrent-consumers* | Specifies the maximum number of concurrent consumers when consuming from JMS (not for request/reply over JMS). See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. When doing request/reply over JMS then the option replyToMaxConcurrentConsumers is used to control number of concurrent consumers on the reply message listener. | | Integer
| *camel.component.amqp.max-messages-per-task* | The number of messages per task. -1 is unlimited. If you use a range for concurrent consumers (eg min max), then this option can be used to set a value to eg 100 to control how fast the consumers will shrink when less work is required. | -1 | Integer
diff --git a/components/camel-apns/src/main/docs/apns-component.adoc b/components/camel-apns/src/main/docs/apns-component.adoc
index 30f3907..2c3eff9 100644
--- a/components/camel-apns/src/main/docs/apns-component.adoc
+++ b/components/camel-apns/src/main/docs/apns-component.adoc
@@ -56,7 +56,7 @@ apns:consumer[?options]
// component options: START
-The APNS component supports 2 options, which are listed below.
+The APNS component supports 4 options, which are listed below.
@@ -65,6 +65,8 @@ The APNS component supports 2 options, which are listed below.
| Name | Description | Default | Type
| *apnsService* (common) | *Required* The ApnsService to use. The org.apache.camel.component.apns.factory.ApnsServiceFactory can be used to build a ApnsService | | ApnsService
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -137,7 +139,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 3 options, which are listed below.
+The component supports 5 options, which are listed below.
@@ -146,7 +148,9 @@ The component supports 3 options, which are listed below.
| Name | Description | Default | Type
| *camel.component.apns.apns-service* | The ApnsService to use. The org.apache.camel.component.apns.factory.ApnsServiceFactory can be used to build a ApnsService. The option is a com.notnoop.apns.ApnsService type. | | String
| *camel.component.apns.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.apns.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.apns.enabled* | Enable apns component | true | Boolean
+| *camel.component.apns.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-as2/camel-as2-component/src/main/docs/as2-component.adoc b/components/camel-as2/camel-as2-component/src/main/docs/as2-component.adoc
index dfa0842..c849e57 100644
--- a/components/camel-as2/camel-as2-component/src/main/docs/as2-component.adoc
+++ b/components/camel-as2/camel-as2-component/src/main/docs/as2-component.adoc
@@ -42,7 +42,7 @@ apiName can be one of:
// component options: START
-The AS2 component supports 2 options, which are listed below.
+The AS2 component supports 4 options, which are listed below.
@@ -51,6 +51,8 @@ The AS2 component supports 2 options, which are listed below.
| Name | Description | Default | Type
| *configuration* (common) | To use the shared configuration | | AS2Configuration
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -148,7 +150,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 30 options, which are listed below.
+The component supports 32 options, which are listed below.
@@ -156,6 +158,7 @@ The component supports 30 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.as2.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.as2.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.as2.configuration.api-name* | What kind of operation to perform | | AS2ApiName
| *camel.component.as2.configuration.as2-from* | The value of the AS2From header of AS2 message. | | String
| *camel.component.as2.configuration.as2-message-structure* | The structure of AS2 Message. One of: PLAIN - No encryption, no signature, SIGNED - No encryption, signature, ENCRYPTED - Encryption, no signature, ENCRYPTED_SIGNED - Encryption, signature | | AS2MessageStructure
@@ -185,6 +188,7 @@ The component supports 30 options, which are listed below.
| *camel.component.as2.configuration.target-port-number* | The port number of target host. -1 indicates the scheme default port. | | Integer
| *camel.component.as2.configuration.user-agent* | The value included in the User-Agent message header identifying the AS2 user agent. | Camel AS2 Client Endpoint | String
| *camel.component.as2.enabled* | Whether to enable auto configuration of the as2 component. This is enabled by default. | | Boolean
+| *camel.component.as2.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then c [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-asterisk/src/main/docs/asterisk-component.adoc b/components/camel-asterisk/src/main/docs/asterisk-component.adoc
index 63bd895..d6d8aeb 100644
--- a/components/camel-asterisk/src/main/docs/asterisk-component.adoc
+++ b/components/camel-asterisk/src/main/docs/asterisk-component.adoc
@@ -34,7 +34,7 @@ asterisk:name[?options]
== Options
// component options: START
-The Asterisk component supports 1 options, which are listed below.
+The Asterisk component supports 3 options, which are listed below.
@@ -42,6 +42,8 @@ The Asterisk component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -98,7 +100,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -106,7 +108,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.asterisk.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.asterisk.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.asterisk.enabled* | Enable asterisk component | true | Boolean
+| *camel.component.asterisk.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed t [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-atmos/src/main/docs/atmos-component.adoc b/components/camel-atmos/src/main/docs/atmos-component.adoc
index ebd22ac..c0c03ef 100644
--- a/components/camel-atmos/src/main/docs/atmos-component.adoc
+++ b/components/camel-atmos/src/main/docs/atmos-component.adoc
@@ -20,7 +20,7 @@ from("atmos:foo/get?remotePath=/path").to("mock:test");
// component options: START
-The Atmos component supports 5 options, which are listed below.
+The Atmos component supports 7 options, which are listed below.
@@ -32,6 +32,8 @@ The Atmos component supports 5 options, which are listed below.
| *uri* (advanced) | The URI of the server for the Atmos client to connect to | | String
| *sslValidation* (security) | Whether the Atmos client should perform SSL validation | false | boolean
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -95,7 +97,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 6 options, which are listed below.
+The component supports 8 options, which are listed below.
@@ -103,8 +105,10 @@ The component supports 6 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.atmos.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.atmos.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.atmos.enabled* | Enable atmos component | true | Boolean
| *camel.component.atmos.full-token-id* | The token id to pass to the Atmos client | | String
+| *camel.component.atmos.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
| *camel.component.atmos.secret-key* | The secret key to pass to the Atmos client (should be base64 encoded) | | String
| *camel.component.atmos.ssl-validation* | Whether the Atmos client should perform SSL validation | false | Boolean
| *camel.component.atmos.uri* | The URI of the server for the Atmos client to connect to | | String
diff --git a/components/camel-atmosphere-websocket/src/main/docs/atmosphere-websocket-component.adoc b/components/camel-atmosphere-websocket/src/main/docs/atmosphere-websocket-component.adoc
index 9368f25..c42a277 100644
--- a/components/camel-atmosphere-websocket/src/main/docs/atmosphere-websocket-component.adoc
+++ b/components/camel-atmosphere-websocket/src/main/docs/atmosphere-websocket-component.adoc
@@ -39,7 +39,7 @@ their `pom.xml` for this component:
// component options: START
-The Atmosphere Websocket component supports 9 options, which are listed below.
+The Atmosphere Websocket component supports 11 options, which are listed below.
@@ -55,6 +55,8 @@ The Atmosphere Websocket component supports 9 options, which are listed below.
| *allowJavaSerialized Object* (advanced) | Whether to allow java serialization when a request uses context-type=application/x-java-serialized-object. This is by default turned off. If you enable this then be aware that Java will deserialize the incoming data from the request to Java and that can be a potential security risk. | false | boolean
| *headerFilterStrategy* (filter) | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. | | HeaderFilterStrategy
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -130,7 +132,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 10 options, which are listed below.
+The component supports 12 options, which are listed below.
@@ -140,12 +142,14 @@ The component supports 10 options, which are listed below.
| *camel.component.atmosphere-websocket.allow-java-serialized-object* | Whether to allow java serialization when a request uses context-type=application/x-java-serialized-object. This is by default turned off. If you enable this then be aware that Java will deserialize the incoming data from the request to Java and that can be a potential security risk. | false | Boolean
| *camel.component.atmosphere-websocket.attachment-multipart-binding* | Whether to automatic bind multipart/form-data as attachments on the Camel Exchange. The options attachmentMultipartBinding=true and disableStreamCache=false cannot work together. Remove disableStreamCache to use AttachmentMultipartBinding. This is turn off by default as this may require servlet specific configuration to enable this when using Servlet's. | false | Boolean
| *camel.component.atmosphere-websocket.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.atmosphere-websocket.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.atmosphere-websocket.enabled* | Enable atmosphere-websocket component | true | Boolean
| *camel.component.atmosphere-websocket.file-name-ext-whitelist* | Whitelist of accepted filename extensions for accepting uploaded files. Multiple extensions can be separated by comma, such as txt,xml. | | String
| *camel.component.atmosphere-websocket.header-filter-strategy* | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. The option is a org.apache.camel.spi.HeaderFilterStrategy type. | | String
| *camel.component.atmosphere-websocket.http-binding* | To use a custom HttpBinding to control the mapping between Camel message and HttpClient. The option is a org.apache.camel.http.common.HttpBinding type. | | String
| *camel.component.atmosphere-websocket.http-configuration* | To use the shared HttpConfiguration as base configuration. The option is a org.apache.camel.http.common.HttpConfiguration type. | | String
| *camel.component.atmosphere-websocket.http-registry* | To use a custom org.apache.camel.component.servlet.HttpRegistry. The option is a org.apache.camel.component.servlet.HttpRegistry type. | | String
+| *camel.component.atmosphere-websocket.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is [...]
| *camel.component.atmosphere-websocket.servlet-name* | Default name of servlet to use. The default name is CamelServlet. | CamelServlet | String
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-atom/src/main/docs/atom-component.adoc b/components/camel-atom/src/main/docs/atom-component.adoc
index 7401785..26e78a7 100644
--- a/components/camel-atom/src/main/docs/atom-component.adoc
+++ b/components/camel-atom/src/main/docs/atom-component.adoc
@@ -39,7 +39,7 @@ Where *atomUri* is the URI to the Atom feed to poll.
// component options: START
-The Atom component supports 1 options, which are listed below.
+The Atom component supports 3 options, which are listed below.
@@ -47,6 +47,8 @@ The Atom component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -124,7 +126,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -132,7 +134,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.atom.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.atom.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.atom.enabled* | Enable atom component | true | Boolean
+| *camel.component.atom.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-atomix/src/main/docs/atomix-map-component.adoc b/components/camel-atomix/src/main/docs/atomix-map-component.adoc
index e93cf04..61d232b 100644
--- a/components/camel-atomix/src/main/docs/atomix-map-component.adoc
+++ b/components/camel-atomix/src/main/docs/atomix-map-component.adoc
@@ -30,7 +30,7 @@ Maven users will need to add the following dependency to their pom.xml for this
== Options
// component options: START
-The Atomix Map component supports 5 options, which are listed below.
+The Atomix Map component supports 7 options, which are listed below.
@@ -42,6 +42,8 @@ The Atomix Map component supports 5 options, which are listed below.
| *nodes* (common) | The nodes the AtomixClient should connect to | | List
| *configurationUri* (common) | The path to the AtomixClient configuration | | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -108,7 +110,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 9 options, which are listed below.
+The component supports 11 options, which are listed below.
@@ -117,12 +119,14 @@ The component supports 9 options, which are listed below.
| Name | Description | Default | Type
| *camel.component.atomix-map.atomix* | The shared AtomixClient instance. The option is a io.atomix.AtomixClient type. | | String
| *camel.component.atomix-map.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.atomix-map.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.atomix-map.configuration-uri* | The path to the AtomixClient configuration | | String
| *camel.component.atomix-map.configuration.default-action* | The default action. | | AtomixMap$Action
| *camel.component.atomix-map.configuration.key* | The key to use if none is set in the header or to listen for events for a specific key. | | Object
| *camel.component.atomix-map.configuration.result-header* | The header that wil carry the result. | | String
| *camel.component.atomix-map.configuration.ttl* | The resource ttl. | | Long
| *camel.component.atomix-map.enabled* | Whether to enable auto configuration of the atomix-map component. This is enabled by default. | | Boolean
+| *camel.component.atomix-map.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed [...]
| *camel.component.atomix-map.nodes* | The nodes the AtomixClient should connect to | | List
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-atomix/src/main/docs/atomix-messaging-component.adoc b/components/camel-atomix/src/main/docs/atomix-messaging-component.adoc
index 33ab9c0..e20f612 100644
--- a/components/camel-atomix/src/main/docs/atomix-messaging-component.adoc
+++ b/components/camel-atomix/src/main/docs/atomix-messaging-component.adoc
@@ -29,7 +29,7 @@ for this component:
----
// component options: START
-The Atomix Messaging component supports 5 options, which are listed below.
+The Atomix Messaging component supports 7 options, which are listed below.
@@ -41,6 +41,8 @@ The Atomix Messaging component supports 5 options, which are listed below.
| *nodes* (common) | The nodes the AtomixClient should connect to | | List
| *configurationUri* (common) | The path to the AtomixClient configuration | | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -108,7 +110,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 10 options, which are listed below.
+The component supports 12 options, which are listed below.
@@ -117,6 +119,7 @@ The component supports 10 options, which are listed below.
| Name | Description | Default | Type
| *camel.component.atomix-messaging.atomix* | The shared AtomixClient instance. The option is a io.atomix.AtomixClient type. | | String
| *camel.component.atomix-messaging.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.atomix-messaging.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.atomix-messaging.configuration-uri* | The path to the AtomixClient configuration | | String
| *camel.component.atomix-messaging.configuration.broadcast-type* | The broadcast type. | | AtomixMessaging$BroadcastType
| *camel.component.atomix-messaging.configuration.channel-name* | The messaging channel name | | String
@@ -124,6 +127,7 @@ The component supports 10 options, which are listed below.
| *camel.component.atomix-messaging.configuration.member-name* | The Atomix Group member name | | String
| *camel.component.atomix-messaging.configuration.result-header* | The header that wil carry the result. | | String
| *camel.component.atomix-messaging.enabled* | Whether to enable auto configuration of the atomix-messaging component. This is enabled by default. | | Boolean
+| *camel.component.atomix-messaging.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is pro [...]
| *camel.component.atomix-messaging.nodes* | The nodes the AtomixClient should connect to | | List
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-atomix/src/main/docs/atomix-multimap-component.adoc b/components/camel-atomix/src/main/docs/atomix-multimap-component.adoc
index ade5e52..eb5c607 100644
--- a/components/camel-atomix/src/main/docs/atomix-multimap-component.adoc
+++ b/components/camel-atomix/src/main/docs/atomix-multimap-component.adoc
@@ -29,7 +29,7 @@ for this component:
----
// component options: START
-The Atomix MultiMap component supports 5 options, which are listed below.
+The Atomix MultiMap component supports 7 options, which are listed below.
@@ -41,6 +41,8 @@ The Atomix MultiMap component supports 5 options, which are listed below.
| *nodes* (consumer) | The nodes the AtomixClient should connect to | | List
| *configurationUri* (consumer) | The path to the AtomixClient configuration | | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -106,7 +108,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 9 options, which are listed below.
+The component supports 11 options, which are listed below.
@@ -115,12 +117,14 @@ The component supports 9 options, which are listed below.
| Name | Description | Default | Type
| *camel.component.atomix-multimap.atomix* | The shared AtomixClient instance. The option is a io.atomix.AtomixClient type. | | String
| *camel.component.atomix-multimap.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.atomix-multimap.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.atomix-multimap.configuration-uri* | The path to the AtomixClient configuration | | String
| *camel.component.atomix-multimap.configuration.default-action* | The default action. | | AtomixMultiMap$Action
| *camel.component.atomix-multimap.configuration.key* | The key to use if none is set in the header or to listen for events for a specific key. | | Object
| *camel.component.atomix-multimap.configuration.result-header* | The header that wil carry the result. | | String
| *camel.component.atomix-multimap.configuration.ttl* | The resource ttl. | | Long
| *camel.component.atomix-multimap.enabled* | Whether to enable auto configuration of the atomix-multimap component. This is enabled by default. | | Boolean
+| *camel.component.atomix-multimap.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proc [...]
| *camel.component.atomix-multimap.nodes* | The nodes the AtomixClient should connect to | | List
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-atomix/src/main/docs/atomix-queue-component.adoc b/components/camel-atomix/src/main/docs/atomix-queue-component.adoc
index 3f5f5ed..4b0bd4a 100644
--- a/components/camel-atomix/src/main/docs/atomix-queue-component.adoc
+++ b/components/camel-atomix/src/main/docs/atomix-queue-component.adoc
@@ -29,7 +29,7 @@ for this component:
----
// component options: START
-The Atomix Queue component supports 5 options, which are listed below.
+The Atomix Queue component supports 7 options, which are listed below.
@@ -41,6 +41,8 @@ The Atomix Queue component supports 5 options, which are listed below.
| *nodes* (common) | The nodes the AtomixClient should connect to | | List
| *configurationUri* (common) | The path to the AtomixClient configuration | | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -105,7 +107,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 7 options, which are listed below.
+The component supports 9 options, which are listed below.
@@ -114,10 +116,12 @@ The component supports 7 options, which are listed below.
| Name | Description | Default | Type
| *camel.component.atomix-queue.atomix* | The shared AtomixClient instance. The option is a io.atomix.AtomixClient type. | | String
| *camel.component.atomix-queue.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.atomix-queue.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.atomix-queue.configuration-uri* | The path to the AtomixClient configuration | | String
| *camel.component.atomix-queue.configuration.default-action* | The default action. | | AtomixQueue$Action
| *camel.component.atomix-queue.configuration.result-header* | The header that wil carry the result. | | String
| *camel.component.atomix-queue.enabled* | Whether to enable auto configuration of the atomix-queue component. This is enabled by default. | | Boolean
+| *camel.component.atomix-queue.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is process [...]
| *camel.component.atomix-queue.nodes* | The nodes the AtomixClient should connect to | | List
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-atomix/src/main/docs/atomix-set-component.adoc b/components/camel-atomix/src/main/docs/atomix-set-component.adoc
index 756da44..b7cba65 100644
--- a/components/camel-atomix/src/main/docs/atomix-set-component.adoc
+++ b/components/camel-atomix/src/main/docs/atomix-set-component.adoc
@@ -29,7 +29,7 @@ for this component:
----
// component options: START
-The Atomix Set component supports 5 options, which are listed below.
+The Atomix Set component supports 7 options, which are listed below.
@@ -41,6 +41,8 @@ The Atomix Set component supports 5 options, which are listed below.
| *nodes* (common) | The nodes the AtomixClient should connect to | | List
| *configurationUri* (common) | The path to the AtomixClient configuration | | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -106,7 +108,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 8 options, which are listed below.
+The component supports 10 options, which are listed below.
@@ -115,11 +117,13 @@ The component supports 8 options, which are listed below.
| Name | Description | Default | Type
| *camel.component.atomix-set.atomix* | The shared AtomixClient instance. The option is a io.atomix.AtomixClient type. | | String
| *camel.component.atomix-set.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.atomix-set.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.atomix-set.configuration-uri* | The path to the AtomixClient configuration | | String
| *camel.component.atomix-set.configuration.default-action* | The default action. | | AtomixSet$Action
| *camel.component.atomix-set.configuration.result-header* | The header that wil carry the result. | | String
| *camel.component.atomix-set.configuration.ttl* | The resource ttl. | | Long
| *camel.component.atomix-set.enabled* | Whether to enable auto configuration of the atomix-set component. This is enabled by default. | | Boolean
+| *camel.component.atomix-set.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed [...]
| *camel.component.atomix-set.nodes* | The nodes the AtomixClient should connect to | | List
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-atomix/src/main/docs/atomix-value-component.adoc b/components/camel-atomix/src/main/docs/atomix-value-component.adoc
index d263404..1c1ffba 100644
--- a/components/camel-atomix/src/main/docs/atomix-value-component.adoc
+++ b/components/camel-atomix/src/main/docs/atomix-value-component.adoc
@@ -29,7 +29,7 @@ for this component:
----
// component options: START
-The Atomix Value component supports 5 options, which are listed below.
+The Atomix Value component supports 7 options, which are listed below.
@@ -41,6 +41,8 @@ The Atomix Value component supports 5 options, which are listed below.
| *nodes* (common) | The nodes the AtomixClient should connect to | | List
| *configurationUri* (common) | The path to the AtomixClient configuration | | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -106,7 +108,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 8 options, which are listed below.
+The component supports 10 options, which are listed below.
@@ -115,11 +117,13 @@ The component supports 8 options, which are listed below.
| Name | Description | Default | Type
| *camel.component.atomix-value.atomix* | The shared AtomixClient instance. The option is a io.atomix.AtomixClient type. | | String
| *camel.component.atomix-value.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.atomix-value.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.atomix-value.configuration-uri* | The path to the AtomixClient configuration | | String
| *camel.component.atomix-value.configuration.default-action* | The default action. | | AtomixValue$Action
| *camel.component.atomix-value.configuration.result-header* | The header that wil carry the result. | | String
| *camel.component.atomix-value.configuration.ttl* | The resource ttl. | | Long
| *camel.component.atomix-value.enabled* | Whether to enable auto configuration of the atomix-value component. This is enabled by default. | | Boolean
+| *camel.component.atomix-value.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is process [...]
| *camel.component.atomix-value.nodes* | The nodes the AtomixClient should connect to | | List
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-avro/src/main/docs/avro-component.adoc b/components/camel-avro/src/main/docs/avro-component.adoc
index 76683ca..b1330ac 100644
--- a/components/camel-avro/src/main/docs/avro-component.adoc
+++ b/components/camel-avro/src/main/docs/avro-component.adoc
@@ -176,7 +176,7 @@ wrapping.
// component options: START
-The Avro component supports 2 options, which are listed below.
+The Avro component supports 4 options, which are listed below.
@@ -185,6 +185,8 @@ The Avro component supports 2 options, which are listed below.
| Name | Description | Default | Type
| *configuration* (advanced) | To use a shared AvroConfiguration to configure options once | | AvroConfiguration
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -251,7 +253,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 15 options, which are listed below.
+The component supports 17 options, which are listed below.
@@ -259,6 +261,7 @@ The component supports 15 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.avro.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.avro.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.avro.configuration.host* | Hostname to use | | String
| *camel.component.avro.configuration.message-name* | The name of the message to send. | | String
| *camel.component.avro.configuration.port* | Port number to use | | Integer
@@ -270,6 +273,7 @@ The component supports 15 options, which are listed below.
| *camel.component.avro.configuration.transport* | Transport to use, can be either http or netty | | AvroTransport
| *camel.component.avro.configuration.uri-authority* | Authority to use (username and password) | | String
| *camel.component.avro.enabled* | Enable avro component | true | Boolean
+| *camel.component.avro.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
| *camel.dataformat.avro.content-type-header* | Whether the data format should set the Content-Type header with the type from the data format if the data format is capable of doing so. For example application/xml for data formats marshalling to XML, or application/json for data formats marshalling to JSon etc. | false | Boolean
| *camel.dataformat.avro.enabled* | Enable avro dataformat | true | Boolean
| *camel.dataformat.avro.instance-class-name* | Class name to use for marshal and unmarshalling | | String
diff --git a/components/camel-avro/src/main/docs/avro-dataformat.adoc b/components/camel-avro/src/main/docs/avro-dataformat.adoc
index 3765a51..e785935 100644
--- a/components/camel-avro/src/main/docs/avro-dataformat.adoc
+++ b/components/camel-avro/src/main/docs/avro-dataformat.adoc
@@ -157,7 +157,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 15 options, which are listed below.
+The component supports 17 options, which are listed below.
@@ -165,6 +165,7 @@ The component supports 15 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.avro.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.avro.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.avro.configuration.host* | Hostname to use | | String
| *camel.component.avro.configuration.message-name* | The name of the message to send. | | String
| *camel.component.avro.configuration.port* | Port number to use | | Integer
@@ -176,6 +177,7 @@ The component supports 15 options, which are listed below.
| *camel.component.avro.configuration.transport* | Transport to use, can be either http or netty | | AvroTransport
| *camel.component.avro.configuration.uri-authority* | Authority to use (username and password) | | String
| *camel.component.avro.enabled* | Enable avro component | true | Boolean
+| *camel.component.avro.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
| *camel.dataformat.avro.content-type-header* | Whether the data format should set the Content-Type header with the type from the data format if the data format is capable of doing so. For example application/xml for data formats marshalling to XML, or application/json for data formats marshalling to JSon etc. | false | Boolean
| *camel.dataformat.avro.enabled* | Enable avro dataformat | true | Boolean
| *camel.dataformat.avro.instance-class-name* | Class name to use for marshal and unmarshalling | | String
diff --git a/components/camel-aws-cw/src/main/docs/aws-cw-component.adoc b/components/camel-aws-cw/src/main/docs/aws-cw-component.adoc
index c42da98..8b3abb4 100644
--- a/components/camel-aws-cw/src/main/docs/aws-cw-component.adoc
+++ b/components/camel-aws-cw/src/main/docs/aws-cw-component.adoc
@@ -33,7 +33,7 @@ The metrics will be created if they don't already exists. +
// component options: START
-The AWS CloudWatch component supports 5 options, which are listed below.
+The AWS CloudWatch component supports 7 options, which are listed below.
@@ -45,6 +45,8 @@ The AWS CloudWatch component supports 5 options, which are listed below.
| *secretKey* (producer) | Amazon AWS Secret Key | | String
| *region* (producer) | The region in which CW client needs to work | | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -108,7 +110,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 17 options, which are listed below.
+The component supports 19 options, which are listed below.
@@ -117,6 +119,7 @@ The component supports 17 options, which are listed below.
| Name | Description | Default | Type
| *camel.component.aws-cw.access-key* | Amazon AWS Access Key | | String
| *camel.component.aws-cw.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.aws-cw.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.aws-cw.configuration.access-key* | Amazon AWS Access Key | | String
| *camel.component.aws-cw.configuration.amazon-cw-client* | To use the AmazonCloudWatch as the client | | AmazonCloudWatch
| *camel.component.aws-cw.configuration.name* | The metric name | | String
@@ -130,6 +133,7 @@ The component supports 17 options, which are listed below.
| *camel.component.aws-cw.configuration.unit* | The metric unit | | String
| *camel.component.aws-cw.configuration.value* | The metric value | | Double
| *camel.component.aws-cw.enabled* | Whether to enable auto configuration of the aws-cw component. This is enabled by default. | | Boolean
+| *camel.component.aws-cw.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed the [...]
| *camel.component.aws-cw.region* | The region in which CW client needs to work | | String
| *camel.component.aws-cw.secret-key* | Amazon AWS Secret Key | | String
|===
diff --git a/components/camel-aws-ddb/src/main/docs/aws-ddb-component.adoc b/components/camel-aws-ddb/src/main/docs/aws-ddb-component.adoc
index 34712a1..d91cd35 100644
--- a/components/camel-aws-ddb/src/main/docs/aws-ddb-component.adoc
+++ b/components/camel-aws-ddb/src/main/docs/aws-ddb-component.adoc
@@ -30,7 +30,7 @@ You can append query options to the URI in the following format,
// component options: START
-The AWS DynamoDB component supports 5 options, which are listed below.
+The AWS DynamoDB component supports 7 options, which are listed below.
@@ -42,6 +42,8 @@ The AWS DynamoDB component supports 5 options, which are listed below.
| *secretKey* (producer) | Amazon AWS Secret Key | | String
| *region* (producer) | The region in which DDB client needs to work | | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -107,7 +109,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 19 options, which are listed below.
+The component supports 21 options, which are listed below.
@@ -116,6 +118,7 @@ The component supports 19 options, which are listed below.
| Name | Description | Default | Type
| *camel.component.aws-ddb.access-key* | Amazon AWS Access Key | | String
| *camel.component.aws-ddb.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.aws-ddb.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.aws-ddb.configuration.access-key* | Amazon AWS Access Key | | String
| *camel.component.aws-ddb.configuration.amazon-d-d-b-client* | To use the AmazonDynamoDB as the client | | AmazonDynamoDB
| *camel.component.aws-ddb.configuration.consistent-read* | Determines whether or not strong consistency should be enforced when data is read. | false | Boolean
@@ -131,6 +134,7 @@ The component supports 19 options, which are listed below.
| *camel.component.aws-ddb.configuration.table-name* | The name of the table currently worked with. | | String
| *camel.component.aws-ddb.configuration.write-capacity* | The provisioned throughput to reserved for writing resources to your table | | Long
| *camel.component.aws-ddb.enabled* | Whether to enable auto configuration of the aws-ddb component. This is enabled by default. | | Boolean
+| *camel.component.aws-ddb.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
| *camel.component.aws-ddb.region* | The region in which DDB client needs to work | | String
| *camel.component.aws-ddb.secret-key* | Amazon AWS Secret Key | | String
|===
diff --git a/components/camel-aws-ddb/src/main/docs/aws-ddbstream-component.adoc b/components/camel-aws-ddb/src/main/docs/aws-ddbstream-component.adoc
index 9e9e0c2..8095555 100644
--- a/components/camel-aws-ddb/src/main/docs/aws-ddbstream-component.adoc
+++ b/components/camel-aws-ddb/src/main/docs/aws-ddbstream-component.adoc
@@ -31,7 +31,7 @@ The stream needs to be created prior to it being used. +
// component options: START
-The AWS DynamoDB Streams component supports 5 options, which are listed below.
+The AWS DynamoDB Streams component supports 7 options, which are listed below.
@@ -43,6 +43,8 @@ The AWS DynamoDB Streams component supports 5 options, which are listed below.
| *secretKey* (consumer) | Amazon AWS Secret Key | | String
| *region* (consumer) | Amazon AWS Region | | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -125,7 +127,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 16 options, which are listed below.
+The component supports 18 options, which are listed below.
@@ -134,6 +136,7 @@ The component supports 16 options, which are listed below.
| Name | Description | Default | Type
| *camel.component.aws-ddbstream.access-key* | Amazon AWS Access Key | | String
| *camel.component.aws-ddbstream.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.aws-ddbstream.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.aws-ddbstream.configuration.access-key* | Amazon AWS Access Key | | String
| *camel.component.aws-ddbstream.configuration.amazon-dynamo-db-streams-client* | Amazon DynamoDB client to use for all requests for this endpoint | | AmazonDynamoDBStreams
| *camel.component.aws-ddbstream.configuration.iterator-type* | Defines where in the DynaboDB stream to start getting records. Note that using TRIM_HORIZON can cause a significant delay before the stream has caught up to real-time. if {AT,AFTER}_SEQUENCE_NUMBER are used, then a sequenceNumberProvider MUST be supplied. | | ShardIteratorType
@@ -146,6 +149,7 @@ The component supports 16 options, which are listed below.
| *camel.component.aws-ddbstream.configuration.sequence-number-provider* | Provider for the sequence number when using one of the two ShardIteratorType.{AT,AFTER}_SEQUENCE_NUMBER iterator types. Can be a registry reference or a literal sequence number. | | SequenceNumberProvider
| *camel.component.aws-ddbstream.configuration.table-name* | Name of the dynamodb table | | String
| *camel.component.aws-ddbstream.enabled* | Whether to enable auto configuration of the aws-ddbstream component. This is enabled by default. | | Boolean
+| *camel.component.aws-ddbstream.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proces [...]
| *camel.component.aws-ddbstream.region* | Amazon AWS Region | | String
| *camel.component.aws-ddbstream.secret-key* | Amazon AWS Secret Key | | String
|===
diff --git a/components/camel-aws-ec2/src/main/docs/aws-ec2-component.adoc b/components/camel-aws-ec2/src/main/docs/aws-ec2-component.adoc
index 87cd0ce..3a90a5c 100644
--- a/components/camel-aws-ec2/src/main/docs/aws-ec2-component.adoc
+++ b/components/camel-aws-ec2/src/main/docs/aws-ec2-component.adoc
@@ -30,7 +30,7 @@ You can append query options to the URI in the following format,
// component options: START
-The AWS EC2 component supports 5 options, which are listed below.
+The AWS EC2 component supports 7 options, which are listed below.
@@ -42,6 +42,8 @@ The AWS EC2 component supports 5 options, which are listed below.
| *accessKey* (producer) | Amazon AWS Access Key | | String
| *secretKey* (producer) | Amazon AWS Secret Key | | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -102,7 +104,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 13 options, which are listed below.
+The component supports 15 options, which are listed below.
@@ -111,6 +113,7 @@ The component supports 13 options, which are listed below.
| Name | Description | Default | Type
| *camel.component.aws-ec2.access-key* | Amazon AWS Access Key | | String
| *camel.component.aws-ec2.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.aws-ec2.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.aws-ec2.configuration.access-key* | Amazon AWS Access Key | | String
| *camel.component.aws-ec2.configuration.amazon-ec2-client* | To use a existing configured AmazonEC2Client as client | | AmazonEC2
| *camel.component.aws-ec2.configuration.operation* | The operation to perform. It can be createAndRunInstances, startInstances, stopInstances, terminateInstances, describeInstances, describeInstancesStatus, rebootInstances, monitorInstances, unmonitorInstances, createTags or deleteTags | | EC2Operations
@@ -120,6 +123,7 @@ The component supports 13 options, which are listed below.
| *camel.component.aws-ec2.configuration.region* | The region in which EC2 client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | | String
| *camel.component.aws-ec2.configuration.secret-key* | Amazon AWS Secret Key | | String
| *camel.component.aws-ec2.enabled* | Whether to enable auto configuration of the aws-ec2 component. This is enabled by default. | | Boolean
+| *camel.component.aws-ec2.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
| *camel.component.aws-ec2.region* | The region in which EC2 client needs to work | | String
| *camel.component.aws-ec2.secret-key* | Amazon AWS Secret Key | | String
|===
diff --git a/components/camel-aws-ecs/src/main/docs/aws-ecs-component.adoc b/components/camel-aws-ecs/src/main/docs/aws-ecs-component.adoc
index 39d628f..796241c 100644
--- a/components/camel-aws-ecs/src/main/docs/aws-ecs-component.adoc
+++ b/components/camel-aws-ecs/src/main/docs/aws-ecs-component.adoc
@@ -30,7 +30,7 @@ You can append query options to the URI in the following format,
// component options: START
-The AWS ECS component supports 5 options, which are listed below.
+The AWS ECS component supports 7 options, which are listed below.
@@ -42,6 +42,8 @@ The AWS ECS component supports 5 options, which are listed below.
| *secretKey* (producer) | Amazon AWS Secret Key | | String
| *region* (producer) | The region in which ECS client needs to work | | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -102,7 +104,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 13 options, which are listed below.
+The component supports 15 options, which are listed below.
@@ -111,6 +113,7 @@ The component supports 13 options, which are listed below.
| Name | Description | Default | Type
| *camel.component.aws-ecs.access-key* | Amazon AWS Access Key | | String
| *camel.component.aws-ecs.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.aws-ecs.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.aws-ecs.configuration.access-key* | Amazon AWS Access Key | | String
| *camel.component.aws-ecs.configuration.ecs-client* | To use a existing configured AWS ECS as client | | AmazonECS
| *camel.component.aws-ecs.configuration.operation* | The operation to perform | | ECSOperations
@@ -120,6 +123,7 @@ The component supports 13 options, which are listed below.
| *camel.component.aws-ecs.configuration.region* | The region in which ECS client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | | String
| *camel.component.aws-ecs.configuration.secret-key* | Amazon AWS Secret Key | | String
| *camel.component.aws-ecs.enabled* | Whether to enable auto configuration of the aws-ecs component. This is enabled by default. | | Boolean
+| *camel.component.aws-ecs.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
| *camel.component.aws-ecs.region* | The region in which ECS client needs to work | | String
| *camel.component.aws-ecs.secret-key* | Amazon AWS Secret Key | | String
|===
diff --git a/components/camel-aws-eks/src/main/docs/aws-eks-component.adoc b/components/camel-aws-eks/src/main/docs/aws-eks-component.adoc
index 94c503c..5284237 100644
--- a/components/camel-aws-eks/src/main/docs/aws-eks-component.adoc
+++ b/components/camel-aws-eks/src/main/docs/aws-eks-component.adoc
@@ -30,7 +30,7 @@ You can append query options to the URI in the following format,
// component options: START
-The AWS EKS component supports 5 options, which are listed below.
+The AWS EKS component supports 7 options, which are listed below.
@@ -42,6 +42,8 @@ The AWS EKS component supports 5 options, which are listed below.
| *secretKey* (producer) | Amazon AWS Secret Key | | String
| *region* (producer) | The region in which EKS client needs to work | | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -102,7 +104,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 13 options, which are listed below.
+The component supports 15 options, which are listed below.
@@ -111,6 +113,7 @@ The component supports 13 options, which are listed below.
| Name | Description | Default | Type
| *camel.component.aws-eks.access-key* | Amazon AWS Access Key | | String
| *camel.component.aws-eks.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.aws-eks.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.aws-eks.configuration.access-key* | Amazon AWS Access Key | | String
| *camel.component.aws-eks.configuration.eks-client* | To use a existing configured AWS EKS as client | | AmazonEKS
| *camel.component.aws-eks.configuration.operation* | The operation to perform | | EKSOperations
@@ -120,6 +123,7 @@ The component supports 13 options, which are listed below.
| *camel.component.aws-eks.configuration.region* | The region in which EKS client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | | String
| *camel.component.aws-eks.configuration.secret-key* | Amazon AWS Secret Key | | String
| *camel.component.aws-eks.enabled* | Whether to enable auto configuration of the aws-eks component. This is enabled by default. | | Boolean
+| *camel.component.aws-eks.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
| *camel.component.aws-eks.region* | The region in which EKS client needs to work | | String
| *camel.component.aws-eks.secret-key* | Amazon AWS Secret Key | | String
|===
diff --git a/components/camel-aws-iam/src/main/docs/aws-iam-component.adoc b/components/camel-aws-iam/src/main/docs/aws-iam-component.adoc
index 71d11dc..127e685 100644
--- a/components/camel-aws-iam/src/main/docs/aws-iam-component.adoc
+++ b/components/camel-aws-iam/src/main/docs/aws-iam-component.adoc
@@ -30,7 +30,7 @@ You can append query options to the URI in the following format,
// component options: START
-The AWS IAM component supports 5 options, which are listed below.
+The AWS IAM component supports 7 options, which are listed below.
@@ -42,6 +42,8 @@ The AWS IAM component supports 5 options, which are listed below.
| *secretKey* (producer) | Amazon AWS Secret Key | | String
| *region* (producer) | The region in which IAM client needs to work | | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -102,7 +104,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 13 options, which are listed below.
+The component supports 15 options, which are listed below.
@@ -111,6 +113,7 @@ The component supports 13 options, which are listed below.
| Name | Description | Default | Type
| *camel.component.aws-iam.access-key* | Amazon AWS Access Key | | String
| *camel.component.aws-iam.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.aws-iam.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.aws-iam.configuration.access-key* | Amazon AWS Access Key | | String
| *camel.component.aws-iam.configuration.iam-client* | To use a existing configured AWS IAM as client | | AmazonIdentityManagement
| *camel.component.aws-iam.configuration.operation* | The operation to perform | | IAMOperations
@@ -120,6 +123,7 @@ The component supports 13 options, which are listed below.
| *camel.component.aws-iam.configuration.region* | The region in which IAM client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | | String
| *camel.component.aws-iam.configuration.secret-key* | Amazon AWS Secret Key | | String
| *camel.component.aws-iam.enabled* | Whether to enable auto configuration of the aws-iam component. This is enabled by default. | | Boolean
+| *camel.component.aws-iam.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
| *camel.component.aws-iam.region* | The region in which IAM client needs to work | | String
| *camel.component.aws-iam.secret-key* | Amazon AWS Secret Key | | String
|===
diff --git a/components/camel-aws-kinesis/src/main/docs/aws-kinesis-component.adoc b/components/camel-aws-kinesis/src/main/docs/aws-kinesis-component.adoc
index b78af1c..03054bd 100644
--- a/components/camel-aws-kinesis/src/main/docs/aws-kinesis-component.adoc
+++ b/components/camel-aws-kinesis/src/main/docs/aws-kinesis-component.adoc
@@ -31,7 +31,7 @@ The stream needs to be created prior to it being used. +
// component options: START
-The AWS Kinesis component supports 5 options, which are listed below.
+The AWS Kinesis component supports 7 options, which are listed below.
@@ -43,6 +43,8 @@ The AWS Kinesis component supports 5 options, which are listed below.
| *secretKey* (common) | Amazon AWS Secret Key | | String
| *region* (common) | Amazon AWS Region | | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -129,7 +131,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 18 options, which are listed below.
+The component supports 20 options, which are listed below.
@@ -138,6 +140,7 @@ The component supports 18 options, which are listed below.
| Name | Description | Default | Type
| *camel.component.aws-kinesis.access-key* | Amazon AWS Access Key | | String
| *camel.component.aws-kinesis.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.aws-kinesis.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.aws-kinesis.configuration.access-key* | Amazon AWS Access Key | | String
| *camel.component.aws-kinesis.configuration.amazon-kinesis-client* | Amazon Kinesis client to use for all requests for this endpoint | | AmazonKinesis
| *camel.component.aws-kinesis.configuration.iterator-type* | Defines where in the Kinesis stream to start getting records | | ShardIteratorType
@@ -152,6 +155,7 @@ The component supports 18 options, which are listed below.
| *camel.component.aws-kinesis.configuration.shard-id* | Defines which shardId in the Kinesis stream to get records from | | String
| *camel.component.aws-kinesis.configuration.stream-name* | Name of the stream | | String
| *camel.component.aws-kinesis.enabled* | Whether to enable auto configuration of the aws-kinesis component. This is enabled by default. | | Boolean
+| *camel.component.aws-kinesis.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processe [...]
| *camel.component.aws-kinesis.region* | Amazon AWS Region | | String
| *camel.component.aws-kinesis.secret-key* | Amazon AWS Secret Key | | String
|===
diff --git a/components/camel-aws-kinesis/src/main/docs/aws-kinesis-firehose-component.adoc b/components/camel-aws-kinesis/src/main/docs/aws-kinesis-firehose-component.adoc
index 30efd2b..f922959 100644
--- a/components/camel-aws-kinesis/src/main/docs/aws-kinesis-firehose-component.adoc
+++ b/components/camel-aws-kinesis/src/main/docs/aws-kinesis-firehose-component.adoc
@@ -30,7 +30,7 @@ The stream needs to be created prior to it being used. +
// component options: START
-The AWS Kinesis Firehose component supports 5 options, which are listed below.
+The AWS Kinesis Firehose component supports 7 options, which are listed below.
@@ -42,6 +42,8 @@ The AWS Kinesis Firehose component supports 5 options, which are listed below.
| *secretKey* (producer) | Amazon AWS Secret Key | | String
| *region* (producer) | Amazon AWS Region | | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -104,7 +106,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 13 options, which are listed below.
+The component supports 15 options, which are listed below.
@@ -113,6 +115,7 @@ The component supports 13 options, which are listed below.
| Name | Description | Default | Type
| *camel.component.aws-kinesis-firehose.access-key* | Amazon AWS Access Key | | String
| *camel.component.aws-kinesis-firehose.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.aws-kinesis-firehose.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.aws-kinesis-firehose.configuration.access-key* | Amazon AWS Access Key | | String
| *camel.component.aws-kinesis-firehose.configuration.amazon-kinesis-firehose-client* | Amazon Kinesis Firehose client to use for all requests for this endpoint | | AmazonKinesisFirehose
| *camel.component.aws-kinesis-firehose.configuration.proxy-host* | To define a proxy host when instantiating the Kinesis Firehose client | | String
@@ -122,6 +125,7 @@ The component supports 13 options, which are listed below.
| *camel.component.aws-kinesis-firehose.configuration.secret-key* | Amazon AWS Secret Key | | String
| *camel.component.aws-kinesis-firehose.configuration.stream-name* | Name of the stream | | String
| *camel.component.aws-kinesis-firehose.enabled* | Whether to enable auto configuration of the aws-kinesis-firehose component. This is enabled by default. | | Boolean
+| *camel.component.aws-kinesis-firehose.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is [...]
| *camel.component.aws-kinesis-firehose.region* | Amazon AWS Region | | String
| *camel.component.aws-kinesis-firehose.secret-key* | Amazon AWS Secret Key | | String
|===
diff --git a/components/camel-aws-kms/src/main/docs/aws-kms-component.adoc b/components/camel-aws-kms/src/main/docs/aws-kms-component.adoc
index 08777ce..f1df25e 100644
--- a/components/camel-aws-kms/src/main/docs/aws-kms-component.adoc
+++ b/components/camel-aws-kms/src/main/docs/aws-kms-component.adoc
@@ -30,7 +30,7 @@ You can append query options to the URI in the following format,
// component options: START
-The AWS KMS component supports 5 options, which are listed below.
+The AWS KMS component supports 7 options, which are listed below.
@@ -42,6 +42,8 @@ The AWS KMS component supports 5 options, which are listed below.
| *secretKey* (producer) | Amazon AWS Secret Key | | String
| *region* (producer) | The region in which KMS client needs to work | | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -102,7 +104,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 13 options, which are listed below.
+The component supports 15 options, which are listed below.
@@ -111,6 +113,7 @@ The component supports 13 options, which are listed below.
| Name | Description | Default | Type
| *camel.component.aws-kms.access-key* | Amazon AWS Access Key | | String
| *camel.component.aws-kms.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.aws-kms.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.aws-kms.configuration.access-key* | Amazon AWS Access Key | | String
| *camel.component.aws-kms.configuration.kms-client* | To use a existing configured AWS KMS as client | | AWSKMS
| *camel.component.aws-kms.configuration.operation* | The operation to perform | | KMSOperations
@@ -120,6 +123,7 @@ The component supports 13 options, which are listed below.
| *camel.component.aws-kms.configuration.region* | The region in which KMS client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | | String
| *camel.component.aws-kms.configuration.secret-key* | Amazon AWS Secret Key | | String
| *camel.component.aws-kms.enabled* | Whether to enable auto configuration of the aws-kms component. This is enabled by default. | | Boolean
+| *camel.component.aws-kms.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
| *camel.component.aws-kms.region* | The region in which KMS client needs to work | | String
| *camel.component.aws-kms.secret-key* | Amazon AWS Secret Key | | String
|===
diff --git a/components/camel-aws-lambda/src/main/docs/aws-lambda-component.adoc b/components/camel-aws-lambda/src/main/docs/aws-lambda-component.adoc
index 9d12867..abe334e 100644
--- a/components/camel-aws-lambda/src/main/docs/aws-lambda-component.adoc
+++ b/components/camel-aws-lambda/src/main/docs/aws-lambda-component.adoc
@@ -36,7 +36,7 @@ You can append query options to the URI in the following format,
// component options: START
-The AWS Lambda component supports 5 options, which are listed below.
+The AWS Lambda component supports 7 options, which are listed below.
@@ -48,6 +48,8 @@ The AWS Lambda component supports 5 options, which are listed below.
| *secretKey* (producer) | Amazon AWS Secret Key | | String
| *region* (producer) | Amazon AWS Region | | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -108,7 +110,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 14 options, which are listed below.
+The component supports 16 options, which are listed below.
@@ -117,6 +119,7 @@ The component supports 14 options, which are listed below.
| Name | Description | Default | Type
| *camel.component.aws-lambda.access-key* | Amazon AWS Access Key | | String
| *camel.component.aws-lambda.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.aws-lambda.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.aws-lambda.configuration.access-key* | Amazon AWS Access Key | | String
| *camel.component.aws-lambda.configuration.aws-lambda-client* | To use a existing configured AwsLambdaClient as client | | AWSLambda
| *camel.component.aws-lambda.configuration.function* | Name of the Lambda function. | | String
@@ -127,6 +130,7 @@ The component supports 14 options, which are listed below.
| *camel.component.aws-lambda.configuration.region* | Amazon AWS Region. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | | String
| *camel.component.aws-lambda.configuration.secret-key* | Amazon AWS Secret Key | | String
| *camel.component.aws-lambda.enabled* | Whether to enable auto configuration of the aws-lambda component. This is enabled by default. | | Boolean
+| *camel.component.aws-lambda.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed [...]
| *camel.component.aws-lambda.region* | Amazon AWS Region | | String
| *camel.component.aws-lambda.secret-key* | Amazon AWS Secret Key | | String
|===
diff --git a/components/camel-aws-mq/src/main/docs/aws-mq-component.adoc b/components/camel-aws-mq/src/main/docs/aws-mq-component.adoc
index 8069c0f..c7fb18f 100644
--- a/components/camel-aws-mq/src/main/docs/aws-mq-component.adoc
+++ b/components/camel-aws-mq/src/main/docs/aws-mq-component.adoc
@@ -30,7 +30,7 @@ You can append query options to the URI in the following format,
// component options: START
-The AWS MQ component supports 5 options, which are listed below.
+The AWS MQ component supports 7 options, which are listed below.
@@ -42,6 +42,8 @@ The AWS MQ component supports 5 options, which are listed below.
| *secretKey* (producer) | Amazon AWS Secret Key | | String
| *region* (producer) | The region in which MQ client needs to work | | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -102,7 +104,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 13 options, which are listed below.
+The component supports 15 options, which are listed below.
@@ -111,6 +113,7 @@ The component supports 13 options, which are listed below.
| Name | Description | Default | Type
| *camel.component.aws-mq.access-key* | Amazon AWS Access Key | | String
| *camel.component.aws-mq.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.aws-mq.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.aws-mq.configuration.access-key* | Amazon AWS Access Key | | String
| *camel.component.aws-mq.configuration.amazon-mq-client* | To use a existing configured AmazonMQClient as client | | AmazonMQ
| *camel.component.aws-mq.configuration.operation* | The operation to perform. It can be listBrokers,createBroker,deleteBroker | | MQOperations
@@ -120,6 +123,7 @@ The component supports 13 options, which are listed below.
| *camel.component.aws-mq.configuration.region* | The region in which MQ client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | | String
| *camel.component.aws-mq.configuration.secret-key* | Amazon AWS Secret Key | | String
| *camel.component.aws-mq.enabled* | Whether to enable auto configuration of the aws-mq component. This is enabled by default. | | Boolean
+| *camel.component.aws-mq.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed the [...]
| *camel.component.aws-mq.region* | The region in which MQ client needs to work | | String
| *camel.component.aws-mq.secret-key* | Amazon AWS Secret Key | | String
|===
diff --git a/components/camel-aws-msk/src/main/docs/aws-msk-component.adoc b/components/camel-aws-msk/src/main/docs/aws-msk-component.adoc
index e05cfff..4d16d1d 100644
--- a/components/camel-aws-msk/src/main/docs/aws-msk-component.adoc
+++ b/components/camel-aws-msk/src/main/docs/aws-msk-component.adoc
@@ -30,7 +30,7 @@ You can append query options to the URI in the following format,
// component options: START
-The AWS MSK component supports 5 options, which are listed below.
+The AWS MSK component supports 7 options, which are listed below.
@@ -42,6 +42,8 @@ The AWS MSK component supports 5 options, which are listed below.
| *secretKey* (producer) | Amazon AWS Secret Key | | String
| *region* (producer) | The region in which MSK client needs to work | | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -103,7 +105,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 13 options, which are listed below.
+The component supports 15 options, which are listed below.
@@ -112,6 +114,7 @@ The component supports 13 options, which are listed below.
| Name | Description | Default | Type
| *camel.component.aws-msk.access-key* | Amazon AWS Access Key | | String
| *camel.component.aws-msk.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.aws-msk.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.aws-msk.configuration.access-key* | Amazon AWS Access Key | | String
| *camel.component.aws-msk.configuration.msk-client* | To use a existing configured AWS MSK as client | | AWSKafka
| *camel.component.aws-msk.configuration.operation* | The operation to perform | | MSKOperations
@@ -121,6 +124,7 @@ The component supports 13 options, which are listed below.
| *camel.component.aws-msk.configuration.region* | The region in which MSK client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | | String
| *camel.component.aws-msk.configuration.secret-key* | Amazon AWS Secret Key | | String
| *camel.component.aws-msk.enabled* | Whether to enable auto configuration of the aws-msk component. This is enabled by default. | | Boolean
+| *camel.component.aws-msk.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
| *camel.component.aws-msk.region* | The region in which MSK client needs to work | | String
| *camel.component.aws-msk.secret-key* | Amazon AWS Secret Key | | String
|===
diff --git a/components/camel-aws-s3/src/main/docs/aws-s3-component.adoc b/components/camel-aws-s3/src/main/docs/aws-s3-component.adoc
index 834f770..19b081d 100644
--- a/components/camel-aws-s3/src/main/docs/aws-s3-component.adoc
+++ b/components/camel-aws-s3/src/main/docs/aws-s3-component.adoc
@@ -40,7 +40,7 @@ from("aws-s3://helloBucket?accessKey=yourAccessKey&secretKey=yourSecretKey&prefi
// component options: START
-The AWS S3 Storage Service component supports 5 options, which are listed below.
+The AWS S3 Storage Service component supports 7 options, which are listed below.
@@ -52,6 +52,8 @@ The AWS S3 Storage Service component supports 5 options, which are listed below.
| *secretKey* (common) | Amazon AWS Secret Key | | String
| *region* (common) | The region where the bucket is located. This option is used in the com.amazonaws.services.s3.model.CreateBucketRequest. | | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -165,7 +167,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 39 options, which are listed below.
+The component supports 41 options, which are listed below.
@@ -174,6 +176,7 @@ The component supports 39 options, which are listed below.
| Name | Description | Default | Type
| *camel.component.aws-s3.access-key* | Amazon AWS Access Key | | String
| *camel.component.aws-s3.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.aws-s3.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.aws-s3.configuration.accelerate-mode-enabled* | Define if Accelerate Mode enabled is true or false | false | Boolean
| *camel.component.aws-s3.configuration.access-key* | Amazon AWS Access Key | | String
| *camel.component.aws-s3.configuration.amazon-s3-client* | Reference to a `com.amazonaws.services.s3.AmazonS3` in the registry. | | AmazonS3
@@ -209,6 +212,7 @@ The component supports 39 options, which are listed below.
| *camel.component.aws-s3.configuration.use-encryption* | Define if encryption must be used or not | false | Boolean
| *camel.component.aws-s3.configuration.use-i-a-m-credentials* | Set whether the S3 client should expect to load credentials on an EC2 instance or to expect static credentials to be passed in. | false | Boolean
| *camel.component.aws-s3.enabled* | Whether to enable auto configuration of the aws-s3 component. This is enabled by default. | | Boolean
+| *camel.component.aws-s3.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed the [...]
| *camel.component.aws-s3.region* | The region where the bucket is located. This option is used in the com.amazonaws.services.s3.model.CreateBucketRequest. | | String
| *camel.component.aws-s3.secret-key* | Amazon AWS Secret Key | | String
|===
diff --git a/components/camel-aws-sdb/src/main/docs/aws-sdb-component.adoc b/components/camel-aws-sdb/src/main/docs/aws-sdb-component.adoc
index faa2eb8..1c56304 100644
--- a/components/camel-aws-sdb/src/main/docs/aws-sdb-component.adoc
+++ b/components/camel-aws-sdb/src/main/docs/aws-sdb-component.adoc
@@ -30,7 +30,7 @@ You can append query options to the URI in the following format,
// component options: START
-The AWS SimpleDB component supports 1 options, which are listed below.
+The AWS SimpleDB component supports 3 options, which are listed below.
@@ -38,6 +38,8 @@ The AWS SimpleDB component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -100,7 +102,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -108,7 +110,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.aws-sdb.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.aws-sdb.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.aws-sdb.enabled* | Whether to enable auto configuration of the aws-sdb component. This is enabled by default. | | Boolean
+| *camel.component.aws-sdb.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-aws-ses/src/main/docs/aws-ses-component.adoc b/components/camel-aws-ses/src/main/docs/aws-ses-component.adoc
index ecc6e97..12a9e3e 100644
--- a/components/camel-aws-ses/src/main/docs/aws-ses-component.adoc
+++ b/components/camel-aws-ses/src/main/docs/aws-ses-component.adoc
@@ -30,7 +30,7 @@ You can append query options to the URI in the following format,
// component options: START
-The AWS Simple Email Service component supports 5 options, which are listed below.
+The AWS Simple Email Service component supports 7 options, which are listed below.
@@ -42,6 +42,8 @@ The AWS Simple Email Service component supports 5 options, which are listed belo
| *secretKey* (producer) | Amazon AWS Secret Key | | String
| *region* (producer) | The region in which SES client needs to work | | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -105,7 +107,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 17 options, which are listed below.
+The component supports 19 options, which are listed below.
@@ -114,6 +116,7 @@ The component supports 17 options, which are listed below.
| Name | Description | Default | Type
| *camel.component.aws-ses.access-key* | Amazon AWS Access Key | | String
| *camel.component.aws-ses.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.aws-ses.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.aws-ses.configuration.access-key* | Amazon AWS Access Key | | String
| *camel.component.aws-ses.configuration.amazon-s-e-s-client* | To use the AmazonSimpleEmailService as the client | | AmazonSimpleEmailService
| *camel.component.aws-ses.configuration.from* | The sender's email address. | | String
@@ -127,6 +130,7 @@ The component supports 17 options, which are listed below.
| *camel.component.aws-ses.configuration.subject* | The subject which is used if the message header 'CamelAwsSesSubject' is not present. | | String
| *camel.component.aws-ses.configuration.to* | List of destination email address. Can be overriden with 'CamelAwsSesTo' header. | | List
| *camel.component.aws-ses.enabled* | Whether to enable auto configuration of the aws-ses component. This is enabled by default. | | Boolean
+| *camel.component.aws-ses.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
| *camel.component.aws-ses.region* | The region in which SES client needs to work | | String
| *camel.component.aws-ses.secret-key* | Amazon AWS Secret Key | | String
|===
diff --git a/components/camel-aws-sns/src/main/docs/aws-sns-component.adoc b/components/camel-aws-sns/src/main/docs/aws-sns-component.adoc
index 8cf6fd9..8d7fe70 100644
--- a/components/camel-aws-sns/src/main/docs/aws-sns-component.adoc
+++ b/components/camel-aws-sns/src/main/docs/aws-sns-component.adoc
@@ -33,7 +33,7 @@ The topic will be created if they don't already exists. +
// component options: START
-The AWS Simple Notification System component supports 5 options, which are listed below.
+The AWS Simple Notification System component supports 7 options, which are listed below.
@@ -45,6 +45,8 @@ The AWS Simple Notification System component supports 5 options, which are liste
| *secretKey* (producer) | Amazon AWS Secret Key | | String
| *region* (producer) | The region in which SNS client needs to work | | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -115,7 +117,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 23 options, which are listed below.
+The component supports 25 options, which are listed below.
@@ -124,6 +126,7 @@ The component supports 23 options, which are listed below.
| Name | Description | Default | Type
| *camel.component.aws-sns.access-key* | Amazon AWS Access Key | | String
| *camel.component.aws-sns.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.aws-sns.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.aws-sns.configuration.access-key* | Amazon AWS Access Key | | String
| *camel.component.aws-sns.configuration.amazon-s-n-s-client* | To use the AmazonSNS as the client | | AmazonSNS
| *camel.component.aws-sns.configuration.amazon-s-q-s-client* | An SQS Client to use as bridge between SNS and SQS | | AmazonSQS
@@ -143,6 +146,7 @@ The component supports 23 options, which are listed below.
| *camel.component.aws-sns.configuration.topic-arn* | The Amazon Resource Name (ARN) assigned to the created topic. | | String
| *camel.component.aws-sns.configuration.topic-name* | The name of the topic | | String
| *camel.component.aws-sns.enabled* | Whether to enable auto configuration of the aws-sns component. This is enabled by default. | | Boolean
+| *camel.component.aws-sns.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
| *camel.component.aws-sns.region* | The region in which SNS client needs to work | | String
| *camel.component.aws-sns.secret-key* | Amazon AWS Secret Key | | String
|===
diff --git a/components/camel-aws-sqs/src/main/docs/aws-sqs-component.adoc b/components/camel-aws-sqs/src/main/docs/aws-sqs-component.adoc
index f31d2c0..832cf7b 100644
--- a/components/camel-aws-sqs/src/main/docs/aws-sqs-component.adoc
+++ b/components/camel-aws-sqs/src/main/docs/aws-sqs-component.adoc
@@ -31,7 +31,7 @@ The queue will be created if they don't already exists. +
// component options: START
-The AWS Simple Queue Service component supports 5 options, which are listed below.
+The AWS Simple Queue Service component supports 7 options, which are listed below.
@@ -43,6 +43,8 @@ The AWS Simple Queue Service component supports 5 options, which are listed belo
| *secretKey* (common) | Amazon AWS Secret Key | | String
| *region* (common) | Specify the queue region which could be used with queueOwnerAWSAccountId to build the service URL. | | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -154,7 +156,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 40 options, which are listed below.
+The component supports 42 options, which are listed below.
@@ -163,6 +165,7 @@ The component supports 40 options, which are listed below.
| Name | Description | Default | Type
| *camel.component.aws-sqs.access-key* | Amazon AWS Access Key | | String
| *camel.component.aws-sqs.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.aws-sqs.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.aws-sqs.configuration.access-key* | Amazon AWS Access Key | | String
| *camel.component.aws-sqs.configuration.amazon-a-w-s-host* | The hostname of the Amazon AWS cloud. | amazonaws.com | String
| *camel.component.aws-sqs.configuration.amazon-s-q-s-client* | To use the AmazonSQS as client | | AmazonSQS
@@ -199,6 +202,7 @@ The component supports 40 options, which are listed below.
| *camel.component.aws-sqs.configuration.visibility-timeout* | The duration (in seconds) that the received messages are hidden from subsequent retrieve requests after being retrieved by a ReceiveMessage request to set in the com.amazonaws.services.sqs.model.SetQueueAttributesRequest. This only make sense if its different from defaultVisibilityTimeout. It changes the queue visibility timeout attribute permanently. | | Integer
| *camel.component.aws-sqs.configuration.wait-time-seconds* | Duration in seconds (0 to 20) that the ReceiveMessage action call will wait until a message is in the queue to include in the response. | | Integer
| *camel.component.aws-sqs.enabled* | Whether to enable auto configuration of the aws-sqs component. This is enabled by default. | | Boolean
+| *camel.component.aws-sqs.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
| *camel.component.aws-sqs.region* | Specify the queue region which could be used with queueOwnerAWSAccountId to build the service URL. | | String
| *camel.component.aws-sqs.secret-key* | Amazon AWS Secret Key | | String
|===
diff --git a/components/camel-aws-swf/src/main/docs/aws-swf-component.adoc b/components/camel-aws-swf/src/main/docs/aws-swf-component.adoc
index 7a75e24..772ea49 100644
--- a/components/camel-aws-swf/src/main/docs/aws-swf-component.adoc
+++ b/components/camel-aws-swf/src/main/docs/aws-swf-component.adoc
@@ -30,7 +30,7 @@ You can append query options to the URI in the following format,
// component options: START
-The AWS Simple Workflow component supports 5 options, which are listed below.
+The AWS Simple Workflow component supports 7 options, which are listed below.
@@ -42,6 +42,8 @@ The AWS Simple Workflow component supports 5 options, which are listed below.
| *secretKey* (common) | Amazon AWS Secret Key. | | String
| *region* (common) | Amazon AWS Region. | | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -123,7 +125,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 32 options, which are listed below.
+The component supports 34 options, which are listed below.
@@ -132,6 +134,7 @@ The component supports 32 options, which are listed below.
| Name | Description | Default | Type
| *camel.component.aws-swf.access-key* | Amazon AWS Access Key. | | String
| *camel.component.aws-swf.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.aws-swf.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.aws-swf.configuration.access-key* | Amazon AWS Access Key. | | String
| *camel.component.aws-swf.configuration.activity-list* | The list name to consume activities from. | | String
| *camel.component.aws-swf.configuration.activity-scheduling-options* | Activity scheduling options | | ActivitySchedulingOptions
@@ -160,6 +163,7 @@ The component supports 32 options, which are listed below.
| *camel.component.aws-swf.configuration.workflow-list* | The list name to consume workflows from. | | String
| *camel.component.aws-swf.configuration.workflow-type-registration-options* | Workflow registration options | | WorkflowTypeRegistrationOptions
| *camel.component.aws-swf.enabled* | Whether to enable auto configuration of the aws-swf component. This is enabled by default. | | Boolean
+| *camel.component.aws-swf.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
| *camel.component.aws-swf.region* | Amazon AWS Region. | | String
| *camel.component.aws-swf.secret-key* | Amazon AWS Secret Key. | | String
|===
diff --git a/components/camel-aws-translate/src/main/docs/aws-translate-component.adoc b/components/camel-aws-translate/src/main/docs/aws-translate-component.adoc
index aa948dc..c47a7cc 100644
--- a/components/camel-aws-translate/src/main/docs/aws-translate-component.adoc
+++ b/components/camel-aws-translate/src/main/docs/aws-translate-component.adoc
@@ -30,7 +30,7 @@ You can append query options to the URI in the following format,
// component options: START
-The AWS Translate component supports 5 options, which are listed below.
+The AWS Translate component supports 7 options, which are listed below.
@@ -42,6 +42,8 @@ The AWS Translate component supports 5 options, which are listed below.
| *secretKey* (producer) | Amazon AWS Secret Key | | String
| *region* (producer) | The region in which Translate client needs to work | | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -103,7 +105,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 14 options, which are listed below.
+The component supports 16 options, which are listed below.
@@ -112,6 +114,7 @@ The component supports 14 options, which are listed below.
| Name | Description | Default | Type
| *camel.component.aws-translate.access-key* | Amazon AWS Access Key | | String
| *camel.component.aws-translate.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.aws-translate.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.aws-translate.configuration.access-key* | Amazon AWS Access Key | | String
| *camel.component.aws-translate.configuration.autodetect-source-language* | Being able to autodetect the source language | false | Boolean
| *camel.component.aws-translate.configuration.operation* | The operation to perform | | TranslateOperations
@@ -122,6 +125,7 @@ The component supports 14 options, which are listed below.
| *camel.component.aws-translate.configuration.secret-key* | Amazon AWS Secret Key | | String
| *camel.component.aws-translate.configuration.translate-client* | To use a existing configured AWS Translate as client | | AmazonTranslate
| *camel.component.aws-translate.enabled* | Whether to enable auto configuration of the aws-translate component. This is enabled by default. | | Boolean
+| *camel.component.aws-translate.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proces [...]
| *camel.component.aws-translate.region* | The region in which Translate client needs to work | | String
| *camel.component.aws-translate.secret-key* | Amazon AWS Secret Key | | String
|===
diff --git a/components/camel-azure/src/main/docs/azure-blob-component.adoc b/components/camel-azure/src/main/docs/azure-blob-component.adoc
index 40ed706..a2aea3a 100644
--- a/components/camel-azure/src/main/docs/azure-blob-component.adoc
+++ b/components/camel-azure/src/main/docs/azure-blob-component.adoc
@@ -39,7 +39,7 @@ to("file://blobdirectory");
// component options: START
-The Azure Storage Blob Service component supports 2 options, which are listed below.
+The Azure Storage Blob Service component supports 4 options, which are listed below.
@@ -48,6 +48,8 @@ The Azure Storage Blob Service component supports 2 options, which are listed be
| Name | Description | Default | Type
| *configuration* (advanced) | The Blob Service configuration | | BlobServiceConfiguration
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -125,7 +127,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 20 options, which are listed below.
+The component supports 22 options, which are listed below.
@@ -133,6 +135,7 @@ The component supports 20 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.azure-blob.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.azure-blob.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.azure-blob.configuration.account-name* | Set the Azure account name | | String
| *camel.component.azure-blob.configuration.azure-blob-client* | The blob service client | | CloudBlob
| *camel.component.azure-blob.configuration.blob-metadata* | Set the blob meta-data | | Map
@@ -152,6 +155,7 @@ The component supports 20 options, which are listed below.
| *camel.component.azure-blob.configuration.stream-write-size* | Set the size of the buffer for writing block and page blocks | | Integer
| *camel.component.azure-blob.configuration.use-flat-listing* | Specify if the flat or hierarchical blob listing should be used | true | Boolean
| *camel.component.azure-blob.enabled* | Enable azure-blob component | true | Boolean
+| *camel.component.azure-blob.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-azure/src/main/docs/azure-queue-component.adoc b/components/camel-azure/src/main/docs/azure-queue-component.adoc
index 09cef60..933e32a 100644
--- a/components/camel-azure/src/main/docs/azure-queue-component.adoc
+++ b/components/camel-azure/src/main/docs/azure-queue-component.adoc
@@ -39,7 +39,7 @@ to("file://queuedirectory");
// component options: START
-The Azure Storage Queue Service component supports 2 options, which are listed below.
+The Azure Storage Queue Service component supports 4 options, which are listed below.
@@ -48,6 +48,8 @@ The Azure Storage Queue Service component supports 2 options, which are listed b
| Name | Description | Default | Type
| *configuration* (advanced) | The Queue Service configuration | | QueueServiceConfiguration
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -116,7 +118,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 10 options, which are listed below.
+The component supports 12 options, which are listed below.
@@ -124,6 +126,7 @@ The component supports 10 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.azure-queue.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.azure-queue.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.azure-queue.configuration.account-name* | Set the Azure account name | | String
| *camel.component.azure-queue.configuration.azure-queue-client* | The queue service client | | CloudQueue
| *camel.component.azure-queue.configuration.credentials* | Set the storage credentials, required in most cases | | StorageCredentials
@@ -133,6 +136,7 @@ The component supports 10 options, which are listed below.
| *camel.component.azure-queue.configuration.queue-name* | The queue resource name | | String
| *camel.component.azure-queue.configuration.queue-prefix* | Set a prefix which can be used for listing the queues | | String
| *camel.component.azure-queue.enabled* | Enable azure-queue component | true | Boolean
+| *camel.component.azure-queue.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processe [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-bean-validator/src/main/docs/bean-validator-component.adoc b/components/camel-bean-validator/src/main/docs/bean-validator-component.adoc
index 449b2e1..645923ce 100644
--- a/components/camel-bean-validator/src/main/docs/bean-validator-component.adoc
+++ b/components/camel-bean-validator/src/main/docs/bean-validator-component.adoc
@@ -49,7 +49,7 @@ Where *label* is an arbitrary text value describing the endpoint. +
// component options: START
-The Bean Validator component supports 1 options, which are listed below.
+The Bean Validator component supports 3 options, which are listed below.
@@ -57,6 +57,8 @@ The Bean Validator component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -113,7 +115,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -121,7 +123,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.bean-validator.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.bean-validator.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.bean-validator.enabled* | Enable bean-validator component | true | Boolean
+| *camel.component.bean-validator.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proce [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-bean/src/main/docs/bean-component.adoc b/components/camel-bean/src/main/docs/bean-component.adoc
index 04c3338..0f3f4b8 100644
--- a/components/camel-bean/src/main/docs/bean-component.adoc
+++ b/components/camel-bean/src/main/docs/bean-component.adoc
@@ -23,7 +23,7 @@ the Registry
// component options: START
-The Bean component supports 2 options, which are listed below.
+The Bean component supports 4 options, which are listed below.
@@ -32,6 +32,8 @@ The Bean component supports 2 options, which are listed below.
| Name | Description | Default | Type
| *cache* (advanced) | If enabled, Camel will cache the result of the first Registry look-up. Cache can be enabled if the bean in the Registry is defined as a singleton scope. | | Boolean
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -88,7 +90,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 5 options, which are listed below.
+The component supports 7 options, which are listed below.
@@ -96,8 +98,10 @@ The component supports 5 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.bean.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.bean.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.bean.cache* | If enabled, Camel will cache the result of the first Registry look-up. Cache can be enabled if the bean in the Registry is defined as a singleton scope. | | Boolean
| *camel.component.bean.enabled* | Whether to enable auto configuration of the bean component. This is enabled by default. | | Boolean
+| *camel.component.bean.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
| *camel.language.bean.enabled* | Whether to enable auto configuration of the bean language. This is enabled by default. | | Boolean
| *camel.language.bean.trim* | Whether to trim the value to remove leading and trailing whitespaces and line breaks | true | Boolean
|===
diff --git a/components/camel-bean/src/main/docs/bean-language.adoc b/components/camel-bean/src/main/docs/bean-language.adoc
index 823f8f1..96e9bc3 100644
--- a/components/camel-bean/src/main/docs/bean-language.adoc
+++ b/components/camel-bean/src/main/docs/bean-language.adoc
@@ -51,7 +51,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 5 options, which are listed below.
+The component supports 7 options, which are listed below.
@@ -59,8 +59,10 @@ The component supports 5 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.bean.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.bean.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.bean.cache* | If enabled, Camel will cache the result of the first Registry look-up. Cache can be enabled if the bean in the Registry is defined as a singleton scope. | | Boolean
| *camel.component.bean.enabled* | Whether to enable auto configuration of the bean component. This is enabled by default. | | Boolean
+| *camel.component.bean.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
| *camel.language.bean.enabled* | Whether to enable auto configuration of the bean language. This is enabled by default. | | Boolean
| *camel.language.bean.trim* | Whether to trim the value to remove leading and trailing whitespaces and line breaks | true | Boolean
|===
diff --git a/components/camel-bean/src/main/docs/class-component.adoc b/components/camel-bean/src/main/docs/class-component.adoc
index c18f1f4..23b24d2 100644
--- a/components/camel-bean/src/main/docs/class-component.adoc
+++ b/components/camel-bean/src/main/docs/class-component.adoc
@@ -26,7 +26,7 @@ bean.
// component options: START
-The Class component supports 2 options, which are listed below.
+The Class component supports 4 options, which are listed below.
@@ -35,6 +35,8 @@ The Class component supports 2 options, which are listed below.
| Name | Description | Default | Type
| *cache* (advanced) | If enabled, Camel will cache the result of the first Registry look-up. Cache can be enabled if the bean in the Registry is defined as a singleton scope. | | Boolean
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
diff --git a/components/camel-beanstalk/src/main/docs/beanstalk-component.adoc b/components/camel-beanstalk/src/main/docs/beanstalk-component.adoc
index 36250a5..b5faa51 100644
--- a/components/camel-beanstalk/src/main/docs/beanstalk-component.adoc
+++ b/components/camel-beanstalk/src/main/docs/beanstalk-component.adoc
@@ -61,7 +61,7 @@ into Beanstalk.
// component options: START
-The Beanstalk component supports 2 options, which are listed below.
+The Beanstalk component supports 4 options, which are listed below.
@@ -70,6 +70,8 @@ The Beanstalk component supports 2 options, which are listed below.
| Name | Description | Default | Type
| *connectionSettings Factory* (common) | Custom ConnectionSettingsFactory. Specify which ConnectionSettingsFactory to use to make connections to Beanstalkd. Especially useful for unit testing without beanstalkd daemon (you can mock ConnectionSettings) | | ConnectionSettingsFactory
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -148,7 +150,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 3 options, which are listed below.
+The component supports 5 options, which are listed below.
@@ -156,8 +158,10 @@ The component supports 3 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.beanstalk.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.beanstalk.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.beanstalk.connection-settings-factory* | Custom ConnectionSettingsFactory. Specify which ConnectionSettingsFactory to use to make connections to Beanstalkd. Especially useful for unit testing without beanstalkd daemon (you can mock ConnectionSettings). The option is a org.apache.camel.component.beanstalk.ConnectionSettingsFactory type. | | String
| *camel.component.beanstalk.enabled* | Enable beanstalk component | true | Boolean
+| *camel.component.beanstalk.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-bonita/src/main/docs/bonita-component.adoc b/components/camel-bonita/src/main/docs/bonita-component.adoc
index 4fd86fd..c46e24a 100644
--- a/components/camel-bonita/src/main/docs/bonita-component.adoc
+++ b/components/camel-bonita/src/main/docs/bonita-component.adoc
@@ -21,7 +21,7 @@ Where *operation* is the specific action to perform on Bonita.
== General Options
// component options: START
-The Bonita component supports 1 options, which are listed below.
+The Bonita component supports 3 options, which are listed below.
@@ -29,6 +29,8 @@ The Bonita component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -86,7 +88,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -94,7 +96,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.bonita.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.bonita.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.bonita.enabled* | Enable bonita component | true | Boolean
+| *camel.component.bonita.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed the [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-box/camel-box-component/src/main/docs/box-component.adoc b/components/camel-box/camel-box-component/src/main/docs/box-component.adoc
index 14637ee..27b0a76 100644
--- a/components/camel-box/camel-box-component/src/main/docs/box-component.adoc
+++ b/components/camel-box/camel-box-component/src/main/docs/box-component.adoc
@@ -52,7 +52,7 @@ The Box component supports three different types of authenticated connections.
== Box Options
// component options: START
-The Box component supports 2 options, which are listed below.
+The Box component supports 4 options, which are listed below.
@@ -61,6 +61,8 @@ The Box component supports 2 options, which are listed below.
| Name | Description | Default | Type
| *configuration* (common) | To use the shared configuration | | BoxConfiguration
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -146,7 +148,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 19 options, which are listed below.
+The component supports 21 options, which are listed below.
@@ -154,6 +156,7 @@ The component supports 19 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.box.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.box.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.box.configuration.access-token-cache* | Custom Access Token Cache for storing and retrieving access tokens. | | IAccessTokenCache
| *camel.component.box.configuration.api-name* | What kind of operation to perform | | BoxApiName
| *camel.component.box.configuration.authentication-type* | The type of authentication for connection. <p> Types of Authentication: <ul> <li>STANDARD_AUTHENTICATION - OAuth 2.0 (3-legged)</li> <li>SERVER_AUTHENTICATION - OAuth 2.0 with JSON Web Tokens</li> </ul> | APP_USER_AUTHENTICATION | String
@@ -172,6 +175,7 @@ The component supports 19 options, which are listed below.
| *camel.component.box.configuration.user-name* | Box user name, MUST be provided | | String
| *camel.component.box.configuration.user-password* | Box user password, MUST be provided if authSecureStorage is not set, or returns null on first call | | String
| *camel.component.box.enabled* | Enable box component | true | Boolean
+| *camel.component.box.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then c [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-braintree/src/main/docs/braintree-component.adoc b/components/camel-braintree/src/main/docs/braintree-component.adoc
index c5062fd..e59757b 100644
--- a/components/camel-braintree/src/main/docs/braintree-component.adoc
+++ b/components/camel-braintree/src/main/docs/braintree-component.adoc
@@ -40,7 +40,7 @@ for this component:
// component options: START
-The Braintree component supports 2 options, which are listed below.
+The Braintree component supports 4 options, which are listed below.
@@ -49,6 +49,8 @@ The Braintree component supports 2 options, which are listed below.
| Name | Description | Default | Type
| *configuration* (common) | To use the shared configuration | | BraintreeConfiguration
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -132,7 +134,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 14 options, which are listed below.
+The component supports 16 options, which are listed below.
@@ -140,6 +142,7 @@ The component supports 14 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.braintree.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.braintree.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.braintree.configuration.access-token* | The access token granted by a merchant to another in order to process transactions on their behalf. Used in place of environment, merchant id, public key and private key fields. | | String
| *camel.component.braintree.configuration.api-name* | What kind of operation to perform | | BraintreeApiName
| *camel.component.braintree.configuration.environment* | The environment Either SANDBOX or PRODUCTION | | String
@@ -153,6 +156,7 @@ The component supports 14 options, which are listed below.
| *camel.component.braintree.configuration.proxy-port* | The proxy port | | Integer
| *camel.component.braintree.configuration.public-key* | The public key provided by Braintree. | | String
| *camel.component.braintree.enabled* | Enable braintree component | true | Boolean
+| *camel.component.braintree.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-browse/src/main/docs/browse-component.adoc b/components/camel-browse/src/main/docs/browse-component.adoc
index df7fabe..797dfdd 100644
--- a/components/camel-browse/src/main/docs/browse-component.adoc
+++ b/components/camel-browse/src/main/docs/browse-component.adoc
@@ -26,7 +26,7 @@ Where *someName* can be any string to uniquely identify the endpoint.
// component options: START
-The Browse component supports 1 options, which are listed below.
+The Browse component supports 3 options, which are listed below.
@@ -34,6 +34,8 @@ The Browse component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -89,7 +91,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -97,7 +99,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.browse.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.browse.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.browse.enabled* | Whether to enable auto configuration of the browse component. This is enabled by default. | | Boolean
+| *camel.component.browse.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed the [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-caffeine/src/main/docs/caffeine-cache-component.adoc b/components/camel-caffeine/src/main/docs/caffeine-cache-component.adoc
index 781d45d..92c49c0 100644
--- a/components/camel-caffeine/src/main/docs/caffeine-cache-component.adoc
+++ b/components/camel-caffeine/src/main/docs/caffeine-cache-component.adoc
@@ -37,7 +37,7 @@ format, `?option=value&option=#beanRef&...`
// component options: START
-The Caffeine Cache component supports 2 options, which are listed below.
+The Caffeine Cache component supports 4 options, which are listed below.
@@ -46,6 +46,8 @@ The Caffeine Cache component supports 2 options, which are listed below.
| Name | Description | Default | Type
| *configuration* (advanced) | Sets the global component configuration | | CaffeineConfiguration
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -115,7 +117,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 17 options, which are listed below.
+The component supports 19 options, which are listed below.
@@ -123,6 +125,7 @@ The component supports 17 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.caffeine-cache.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.caffeine-cache.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.caffeine-cache.configuration.action* | To configure the default cache action. If an action is set in the message header, then the operation from the header takes precedence. | | String
| *camel.component.caffeine-cache.configuration.cache* | To configure an already instantiated cache to be used | | Cache
| *camel.component.caffeine-cache.configuration.cache-loader* | To configure a CacheLoader in case of a LoadCache use | | CacheLoader
@@ -139,6 +142,7 @@ The component supports 17 options, which are listed below.
| *camel.component.caffeine-cache.configuration.stats-enabled* | To enable stats on the cache | false | Boolean
| *camel.component.caffeine-cache.configuration.value-type* | The cache value type, default "java.lang.Object" | | String
| *camel.component.caffeine-cache.enabled* | Whether to enable auto configuration of the caffeine-cache component. This is enabled by default. | | Boolean
+| *camel.component.caffeine-cache.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proce [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-caffeine/src/main/docs/caffeine-loadcache-component.adoc b/components/camel-caffeine/src/main/docs/caffeine-loadcache-component.adoc
index 17b774e..0a27d8f 100644
--- a/components/camel-caffeine/src/main/docs/caffeine-loadcache-component.adoc
+++ b/components/camel-caffeine/src/main/docs/caffeine-loadcache-component.adoc
@@ -37,7 +37,7 @@ format, `?option=value&option=#beanRef&...`
// component options: START
-The Caffeine LoadCache component supports 2 options, which are listed below.
+The Caffeine LoadCache component supports 4 options, which are listed below.
@@ -46,6 +46,8 @@ The Caffeine LoadCache component supports 2 options, which are listed below.
| Name | Description | Default | Type
| *configuration* (advanced) | Sets the global component configuration | | CaffeineConfiguration
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -115,7 +117,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 17 options, which are listed below.
+The component supports 19 options, which are listed below.
@@ -123,6 +125,7 @@ The component supports 17 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.caffeine-loadcache.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.caffeine-loadcache.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.caffeine-loadcache.configuration.action* | To configure the default cache action. If an action is set in the message header, then the operation from the header takes precedence. | | String
| *camel.component.caffeine-loadcache.configuration.cache* | To configure an already instantiated cache to be used | | Cache
| *camel.component.caffeine-loadcache.configuration.cache-loader* | To configure a CacheLoader in case of a LoadCache use | | CacheLoader
@@ -139,6 +142,7 @@ The component supports 17 options, which are listed below.
| *camel.component.caffeine-loadcache.configuration.stats-enabled* | To enable stats on the cache | false | Boolean
| *camel.component.caffeine-loadcache.configuration.value-type* | The cache value type, default "java.lang.Object" | | String
| *camel.component.caffeine-loadcache.enabled* | Whether to enable auto configuration of the caffeine-loadcache component. This is enabled by default. | | Boolean
+| *camel.component.caffeine-loadcache.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is p [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-cassandraql/src/main/docs/cql-component.adoc b/components/camel-cassandraql/src/main/docs/cql-component.adoc
index 400dcf6..8329ef0 100644
--- a/components/camel-cassandraql/src/main/docs/cql-component.adoc
+++ b/components/camel-cassandraql/src/main/docs/cql-component.adoc
@@ -59,7 +59,7 @@ your own Cluster instance and give it to the Camel endpoint.
// component options: START
-The Cassandra CQL component supports 1 options, which are listed below.
+The Cassandra CQL component supports 3 options, which are listed below.
@@ -67,6 +67,8 @@ The Cassandra CQL component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -150,7 +152,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -158,7 +160,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.cql.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.cql.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.cql.enabled* | Enable cql component | true | Boolean
+| *camel.component.cql.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then c [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-chatscript/src/main/docs/chatscript-component.adoc b/components/camel-chatscript/src/main/docs/chatscript-component.adoc
index 9ec9c88..04cbf56 100644
--- a/components/camel-chatscript/src/main/docs/chatscript-component.adoc
+++ b/components/camel-chatscript/src/main/docs/chatscript-component.adoc
@@ -42,7 +42,7 @@ ChatScript:host:[port]/botName[?options]
== Options
// component options: START
-The ChatScript component supports 1 options, which are listed below.
+The ChatScript component supports 3 options, which are listed below.
@@ -50,6 +50,8 @@ The ChatScript component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -104,7 +106,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -112,6 +114,8 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.chatscript.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.chatscript.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.chatscript.enabled* | Whether to enable auto configuration of the chatscript component. This is enabled by default. | | Boolean
+| *camel.component.chatscript.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-chunk/src/main/docs/chunk-component.adoc b/components/camel-chunk/src/main/docs/chunk-component.adoc
index 482c915..7cb2a9b 100644
--- a/components/camel-chunk/src/main/docs/chunk-component.adoc
+++ b/components/camel-chunk/src/main/docs/chunk-component.adoc
@@ -41,7 +41,7 @@ format, `?option=value&option=value&...`
// component options: START
-The Chunk component supports 1 options, which are listed below.
+The Chunk component supports 3 options, which are listed below.
@@ -49,6 +49,8 @@ The Chunk component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -106,7 +108,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -114,7 +116,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.chunk.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.chunk.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.chunk.enabled* | Enable chunk component | true | Boolean
+| *camel.component.chunk.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-cm-sms/src/main/docs/cm-sms-component.adoc b/components/camel-cm-sms/src/main/docs/cm-sms-component.adoc
index 9570d97..eb85807 100644
--- a/components/camel-cm-sms/src/main/docs/cm-sms-component.adoc
+++ b/components/camel-cm-sms/src/main/docs/cm-sms-component.adoc
@@ -36,7 +36,7 @@ for this component:
// component options: START
-The CM SMS Gateway component supports 1 options, which are listed below.
+The CM SMS Gateway component supports 3 options, which are listed below.
@@ -44,6 +44,8 @@ The CM SMS Gateway component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -99,7 +101,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -107,7 +109,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.cm-sms.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.cm-sms.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.cm-sms.enabled* | Enable cm-sms component | true | Boolean
+| *camel.component.cm-sms.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed the [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-cmis/src/main/docs/cmis-component.adoc b/components/camel-cmis/src/main/docs/cmis-component.adoc
index 5ca8e1a..7322487 100644
--- a/components/camel-cmis/src/main/docs/cmis-component.adoc
+++ b/components/camel-cmis/src/main/docs/cmis-component.adoc
@@ -26,7 +26,7 @@ You can append query options to the URI in the following format,
// component options: START
-The CMIS component supports 2 options, which are listed below.
+The CMIS component supports 4 options, which are listed below.
@@ -35,6 +35,8 @@ The CMIS component supports 2 options, which are listed below.
| Name | Description | Default | Type
| *sessionFacadeFactory* (common) | To use a custom CMISSessionFacadeFactory to create the CMISSessionFacade instances | | CMISSessionFacadeFactory
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -98,7 +100,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 3 options, which are listed below.
+The component supports 5 options, which are listed below.
@@ -106,7 +108,9 @@ The component supports 3 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.cmis.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.cmis.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.cmis.enabled* | Enable cmis component | true | Boolean
+| *camel.component.cmis.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
| *camel.component.cmis.session-facade-factory* | To use a custom CMISSessionFacadeFactory to create the CMISSessionFacade instances. The option is a org.apache.camel.component.cmis.CMISSessionFacadeFactory type. | | String
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-coap/src/main/docs/coap-component.adoc b/components/camel-coap/src/main/docs/coap-component.adoc
index aca9866..8533868 100644
--- a/components/camel-coap/src/main/docs/coap-component.adoc
+++ b/components/camel-coap/src/main/docs/coap-component.adoc
@@ -46,7 +46,7 @@ for this component:
// component options: START
-The CoAP component supports 1 options, which are listed below.
+The CoAP component supports 3 options, which are listed below.
@@ -54,6 +54,8 @@ The CoAP component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -118,7 +120,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -126,7 +128,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.coap.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.coap.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.coap.enabled* | Enable coap component | true | Boolean
+| *camel.component.coap.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-cometd/src/main/docs/cometd-component.adoc b/components/camel-cometd/src/main/docs/cometd-component.adoc
index 1172ada..9da94b6 100644
--- a/components/camel-cometd/src/main/docs/cometd-component.adoc
+++ b/components/camel-cometd/src/main/docs/cometd-component.adoc
@@ -53,7 +53,7 @@ where `cometds:` represents an SSL configured endpoint.
// component options: START
-The CometD component supports 8 options, which are listed below.
+The CometD component supports 10 options, which are listed below.
@@ -68,6 +68,8 @@ The CometD component supports 8 options, which are listed below.
| *sslContextParameters* (security) | To configure security using SSLContextParameters | | SSLContextParameters
| *useGlobalSslContext Parameters* (security) | Enable usage of global SSL context parameters. | false | boolean
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -139,7 +141,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 9 options, which are listed below.
+The component supports 11 options, which are listed below.
@@ -147,8 +149,10 @@ The component supports 9 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.cometd.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.cometd.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.cometd.enabled* | Enable cometd component | true | Boolean
| *camel.component.cometd.extensions* | To use a list of custom BayeuxServer.Extension that allows modifying incoming and outgoing requests. | | List
+| *camel.component.cometd.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed the [...]
| *camel.component.cometd.security-policy* | To use a custom configured SecurityPolicy to control authorization. The option is a org.cometd.bayeux.server.SecurityPolicy type. | | String
| *camel.component.cometd.ssl-context-parameters* | To configure security using SSLContextParameters. The option is a org.apache.camel.support.jsse.SSLContextParameters type. | | String
| *camel.component.cometd.ssl-key-password* | The password for the keystore when using SSL. | | String
diff --git a/components/camel-consul/src/main/docs/consul-component.adoc b/components/camel-consul/src/main/docs/consul-component.adoc
index abee07e..1f07289 100644
--- a/components/camel-consul/src/main/docs/consul-component.adoc
+++ b/components/camel-consul/src/main/docs/consul-component.adoc
@@ -40,7 +40,7 @@ You can append query options to the URI in the following format:
// component options: START
-The Consul component supports 9 options, which are listed below.
+The Consul component supports 11 options, which are listed below.
@@ -56,6 +56,8 @@ The Consul component supports 9 options, which are listed below.
| *password* (common) | Sets the password to be used for basic authentication | | String
| *configuration* (advanced) | Sets the common configuration shared among endpoints | | ConsulConfiguration
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -113,7 +115,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 90 options, which are listed below.
+The component supports 92 options, which are listed below.
@@ -122,6 +124,7 @@ The component supports 90 options, which are listed below.
| Name | Description | Default | Type
| *camel.component.consul.acl-token* | Sets the ACL token to be used with Consul | | String
| *camel.component.consul.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.consul.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.consul.cluster.service.acl-token* | | | String
| *camel.component.consul.cluster.service.attributes* | Custom service attributes. | | Map
| *camel.component.consul.cluster.service.block-seconds* | | | Integer
@@ -175,6 +178,7 @@ The component supports 90 options, which are listed below.
| *camel.component.consul.health.check.repository.enabled* | | | Boolean
| *camel.component.consul.health.check.repository.failure-threshold* | | | Integer
| *camel.component.consul.health.check.repository.interval* | | | String
+| *camel.component.consul.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed the [...]
| *camel.component.consul.password* | Sets the password to be used for basic authentication | | String
| *camel.component.consul.service-registry.acl-token* | | | String
| *camel.component.consul.service-registry.attributes* | Custom service attributes. | | Map
diff --git a/components/camel-controlbus/src/main/docs/controlbus-component.adoc b/components/camel-controlbus/src/main/docs/controlbus-component.adoc
index 43f6500..d14145a 100644
--- a/components/camel-controlbus/src/main/docs/controlbus-component.adoc
+++ b/components/camel-controlbus/src/main/docs/controlbus-component.adoc
@@ -57,7 +57,7 @@ then the result is put in the message body.
// component options: START
-The Control Bus component supports 1 options, which are listed below.
+The Control Bus component supports 3 options, which are listed below.
@@ -65,6 +65,8 @@ The Control Bus component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -127,7 +129,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -135,7 +137,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.controlbus.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.controlbus.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.controlbus.enabled* | Whether to enable auto configuration of the controlbus component. This is enabled by default. | | Boolean
+| *camel.component.controlbus.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-corda/src/main/docs/corda-component.adoc b/components/camel-corda/src/main/docs/corda-component.adoc
index 558b775..3231442 100644
--- a/components/camel-corda/src/main/docs/corda-component.adoc
+++ b/components/camel-corda/src/main/docs/corda-component.adoc
@@ -37,7 +37,7 @@ corda://<host:port>[?options]
// component options: START
-The Corda component supports 2 options, which are listed below.
+The Corda component supports 4 options, which are listed below.
@@ -46,6 +46,8 @@ The Corda component supports 2 options, which are listed below.
| Name | Description | Default | Type
| *configuration* (common) | Default configuration | | CordaConfiguration
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -99,7 +101,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 14 options, which are listed below.
+The component supports 16 options, which are listed below.
@@ -107,6 +109,7 @@ The component supports 14 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.corda.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.corda.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.corda.configuration.arguments* | | | Object[]
| *camel.component.corda.configuration.contract-state-class* | | | Class
| *camel.component.corda.configuration.flow-loci-class* | | | Class
@@ -120,6 +123,7 @@ The component supports 14 options, which are listed below.
| *camel.component.corda.configuration.sort* | | | Sort
| *camel.component.corda.configuration.username* | | | String
| *camel.component.corda.enabled* | Enable corda component | true | Boolean
+| *camel.component.corda.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-couchbase/src/main/docs/couchbase-component.adoc b/components/camel-couchbase/src/main/docs/couchbase-component.adoc
index 9ffe955..276997d 100644
--- a/components/camel-couchbase/src/main/docs/couchbase-component.adoc
+++ b/components/camel-couchbase/src/main/docs/couchbase-component.adoc
@@ -34,7 +34,7 @@ couchbase:url
== Options
// component options: START
-The Couchbase component supports 1 options, which are listed below.
+The Couchbase component supports 3 options, which are listed below.
@@ -42,6 +42,8 @@ The Couchbase component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -140,7 +142,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -148,7 +150,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.couchbase.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.couchbase.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.couchbase.enabled* | Enable couchbase component | true | Boolean
+| *camel.component.couchbase.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-couchdb/src/main/docs/couchdb-component.adoc b/components/camel-couchdb/src/main/docs/couchdb-component.adoc
index 5f966fd..23a9c50 100644
--- a/components/camel-couchdb/src/main/docs/couchdb-component.adoc
+++ b/components/camel-couchdb/src/main/docs/couchdb-component.adoc
@@ -49,7 +49,7 @@ is optional and if not specified then defaults to 5984.
== Options
// component options: START
-The CouchDB component supports 1 options, which are listed below.
+The CouchDB component supports 3 options, which are listed below.
@@ -57,6 +57,8 @@ The CouchDB component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -120,7 +122,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -128,7 +130,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.couchdb.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.couchdb.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.couchdb.enabled* | Enable couchdb component | true | Boolean
+| *camel.component.couchdb.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-crypto-cms/src/main/docs/crypto-cms-component.adoc b/components/camel-crypto-cms/src/main/docs/crypto-cms-component.adoc
index aba756f..f938340 100644
--- a/components/camel-crypto-cms/src/main/docs/crypto-cms-component.adoc
+++ b/components/camel-crypto-cms/src/main/docs/crypto-cms-component.adoc
@@ -38,7 +38,7 @@ If the Bouncy Castle security provider is not registered then the Crypto CMS com
== Options
// component options: START
-The Crypto CMS component supports 3 options, which are listed below.
+The Crypto CMS component supports 5 options, which are listed below.
@@ -48,6 +48,8 @@ The Crypto CMS component supports 3 options, which are listed below.
| *signedDataVerifier Configuration* (advanced) | To configure the shared SignedDataVerifierConfiguration, which determines the uri parameters for the verify operation. | | SignedDataVerifierConfiguration
| *envelopedDataDecryptor Configuration* (advanced) | To configure the shared EnvelopedDataDecryptorConfiguration, which determines the uri parameters for the decrypt operation. | | EnvelopedDataDecryptorConfiguration
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -112,7 +114,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 4 options, which are listed below.
+The component supports 6 options, which are listed below.
@@ -120,8 +122,10 @@ The component supports 4 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.crypto-cms.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.crypto-cms.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.crypto-cms.enabled* | Whether to enable auto configuration of the crypto-cms component. This is enabled by default. | | Boolean
| *camel.component.crypto-cms.enveloped-data-decryptor-configuration* | To configure the shared EnvelopedDataDecryptorConfiguration, which determines the uri parameters for the decrypt operation. The option is a org.apache.camel.component.crypto.cms.crypt.EnvelopedDataDecryptorConfiguration type. | | String
+| *camel.component.crypto-cms.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed [...]
| *camel.component.crypto-cms.signed-data-verifier-configuration* | To configure the shared SignedDataVerifierConfiguration, which determines the uri parameters for the verify operation. The option is a org.apache.camel.component.crypto.cms.sig.SignedDataVerifierConfiguration type. | | String
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-crypto/src/main/docs/crypto-component.adoc b/components/camel-crypto/src/main/docs/crypto-component.adoc
index b426442..56b9ef4 100644
--- a/components/camel-crypto/src/main/docs/crypto-component.adoc
+++ b/components/camel-crypto/src/main/docs/crypto-component.adoc
@@ -85,7 +85,7 @@ both signing and verifying should be configured identically.
== Options
// component options: START
-The Crypto (JCE) component supports 2 options, which are listed below.
+The Crypto (JCE) component supports 4 options, which are listed below.
@@ -94,6 +94,8 @@ The Crypto (JCE) component supports 2 options, which are listed below.
| Name | Description | Default | Type
| *configuration* (advanced) | To use the shared DigitalSignatureConfiguration as configuration | | DigitalSignatureConfiguration
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -162,7 +164,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 33 options, which are listed below.
+The component supports 35 options, which are listed below.
@@ -170,6 +172,7 @@ The component supports 33 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.crypto.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.crypto.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.crypto.configuration.algorithm* | Sets the JCE name of the Algorithm that should be used for the signer. | SHA256withRSA | String
| *camel.component.crypto.configuration.alias* | Sets the alias used to query the KeyStore for keys and {@link java.security.cert.Certificate Certificates} to be used in signing and verifying exchanges. This value can be provided at runtime via the message header {@link org.apache.camel.component.crypto.DigitalSignatureConstants#KEYSTORE_ALIAS} | | String
| *camel.component.crypto.configuration.buffer-size* | Set the size of the buffer used to read in the Exchange payload data. | 2048 | Integer
@@ -191,6 +194,7 @@ The component supports 33 options, which are listed below.
| *camel.component.crypto.configuration.secure-random-name* | Sets the reference name for a SecureRandom that can be found in the registry. | | String
| *camel.component.crypto.configuration.signature-header-name* | Set the name of the message header that should be used to store the base64 encoded signature. This defaults to 'CamelDigitalSignature' | | String
| *camel.component.crypto.enabled* | Enable crypto component | true | Boolean
+| *camel.component.crypto.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed the [...]
| *camel.dataformat.crypto.algorithm* | The JCE algorithm name indicating the cryptographic algorithm that will be used. | | String
| *camel.dataformat.crypto.algorithm-parameter-ref* | A JCE AlgorithmParameterSpec used to initialize the Cipher. Will lookup the type using the given name as a java.security.spec.AlgorithmParameterSpec type. | | String
| *camel.dataformat.crypto.buffersize* | The size of the buffer used in the signature process. | | Integer
diff --git a/components/camel-crypto/src/main/docs/crypto-dataformat.adoc b/components/camel-crypto/src/main/docs/crypto-dataformat.adoc
index 29705ac..1f26f3d 100644
--- a/components/camel-crypto/src/main/docs/crypto-dataformat.adoc
+++ b/components/camel-crypto/src/main/docs/crypto-dataformat.adoc
@@ -49,7 +49,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 33 options, which are listed below.
+The component supports 35 options, which are listed below.
@@ -57,6 +57,7 @@ The component supports 33 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.crypto.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.crypto.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.crypto.configuration.algorithm* | Sets the JCE name of the Algorithm that should be used for the signer. | SHA256withRSA | String
| *camel.component.crypto.configuration.alias* | Sets the alias used to query the KeyStore for keys and {@link java.security.cert.Certificate Certificates} to be used in signing and verifying exchanges. This value can be provided at runtime via the message header {@link org.apache.camel.component.crypto.DigitalSignatureConstants#KEYSTORE_ALIAS} | | String
| *camel.component.crypto.configuration.buffer-size* | Set the size of the buffer used to read in the Exchange payload data. | 2048 | Integer
@@ -78,6 +79,7 @@ The component supports 33 options, which are listed below.
| *camel.component.crypto.configuration.secure-random-name* | Sets the reference name for a SecureRandom that can be found in the registry. | | String
| *camel.component.crypto.configuration.signature-header-name* | Set the name of the message header that should be used to store the base64 encoded signature. This defaults to 'CamelDigitalSignature' | | String
| *camel.component.crypto.enabled* | Enable crypto component | true | Boolean
+| *camel.component.crypto.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed the [...]
| *camel.dataformat.crypto.algorithm* | The JCE algorithm name indicating the cryptographic algorithm that will be used. | | String
| *camel.dataformat.crypto.algorithm-parameter-ref* | A JCE AlgorithmParameterSpec used to initialize the Cipher. Will lookup the type using the given name as a java.security.spec.AlgorithmParameterSpec type. | | String
| *camel.dataformat.crypto.buffersize* | The size of the buffer used in the signature process. | | Integer
diff --git a/components/camel-cxf/src/main/docs/cxf-component.adoc b/components/camel-cxf/src/main/docs/cxf-component.adoc
index 84994af..df72593 100644
--- a/components/camel-cxf/src/main/docs/cxf-component.adoc
+++ b/components/camel-cxf/src/main/docs/cxf-component.adoc
@@ -85,7 +85,7 @@ cxf:bean:cxfEndpoint?wsdlURL=wsdl/hello_world.wsdl&dataFormat=PAYLOAD
// component options: START
-The CXF component supports 4 options, which are listed below.
+The CXF component supports 6 options, which are listed below.
@@ -96,6 +96,8 @@ The CXF component supports 4 options, which are listed below.
| *useGlobalSslContext Parameters* (security) | Enable usage of global SSL context parameters. | false | boolean
| *headerFilterStrategy* (filter) | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. | | HeaderFilterStrategy
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -183,7 +185,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 5 options, which are listed below.
+The component supports 7 options, which are listed below.
@@ -192,8 +194,10 @@ The component supports 5 options, which are listed below.
| Name | Description | Default | Type
| *camel.component.cxf.allow-streaming* | This option controls whether the CXF component, when running in PAYLOAD mode, will DOM parse the incoming messages into DOM Elements or keep the payload as a javax.xml.transform.Source object that would allow streaming in some cases. | | Boolean
| *camel.component.cxf.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.cxf.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.cxf.enabled* | Enable cxf component | true | Boolean
| *camel.component.cxf.header-filter-strategy* | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. The option is a org.apache.camel.spi.HeaderFilterStrategy type. | | String
+| *camel.component.cxf.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then c [...]
| *camel.component.cxf.use-global-ssl-context-parameters* | Enable usage of global SSL context parameters. | false | Boolean
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-cxf/src/main/docs/cxfrs-component.adoc b/components/camel-cxf/src/main/docs/cxfrs-component.adoc
index 559a939..f607f1d 100644
--- a/components/camel-cxf/src/main/docs/cxfrs-component.adoc
+++ b/components/camel-cxf/src/main/docs/cxfrs-component.adoc
@@ -52,7 +52,7 @@ cxfrs:bean:cxfEndpoint?resourceClasses=org.apache.camel.rs.Example
// component options: START
-The CXF-RS component supports 3 options, which are listed below.
+The CXF-RS component supports 5 options, which are listed below.
@@ -62,6 +62,8 @@ The CXF-RS component supports 3 options, which are listed below.
| *useGlobalSslContext Parameters* (security) | Enable usage of global SSL context parameters. | false | boolean
| *headerFilterStrategy* (filter) | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. | | HeaderFilterStrategy
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -144,7 +146,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 4 options, which are listed below.
+The component supports 6 options, which are listed below.
@@ -152,8 +154,10 @@ The component supports 4 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.cxfrs.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.cxfrs.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.cxfrs.enabled* | Enable cxfrs component | true | Boolean
| *camel.component.cxfrs.header-filter-strategy* | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. The option is a org.apache.camel.spi.HeaderFilterStrategy type. | | String
+| *camel.component.cxfrs.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
| *camel.component.cxfrs.use-global-ssl-context-parameters* | Enable usage of global SSL context parameters. | false | Boolean
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-dataformat/src/main/docs/dataformat-component.adoc b/components/camel-dataformat/src/main/docs/dataformat-component.adoc
index c0a0dde..67bfea2 100644
--- a/components/camel-dataformat/src/main/docs/dataformat-component.adoc
+++ b/components/camel-dataformat/src/main/docs/dataformat-component.adoc
@@ -27,7 +27,7 @@ for which options it support.
// component options: START
-The Data Format component supports 1 options, which are listed below.
+The Data Format component supports 3 options, which are listed below.
@@ -35,6 +35,8 @@ The Data Format component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -88,7 +90,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -96,7 +98,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.dataformat.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.dataformat.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.dataformat.enabled* | Whether to enable auto configuration of the dataformat component. This is enabled by default. | | Boolean
+| *camel.component.dataformat.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-dataset/src/main/docs/dataset-component.adoc b/components/camel-dataset/src/main/docs/dataset-component.adoc
index 9957d2d..ca4afaf 100644
--- a/components/camel-dataset/src/main/docs/dataset-component.adoc
+++ b/components/camel-dataset/src/main/docs/dataset-component.adoc
@@ -49,7 +49,7 @@ extend `DataSetSupport`.
// component options: START
-The Dataset component supports 1 options, which are listed below.
+The Dataset component supports 3 options, which are listed below.
@@ -57,6 +57,8 @@ The Dataset component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -124,7 +126,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -132,7 +134,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.dataset.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.dataset.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.dataset.enabled* | Whether to enable auto configuration of the dataset component. This is enabled by default. | | Boolean
+| *camel.component.dataset.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-dataset/src/main/docs/dataset-test-component.adoc b/components/camel-dataset/src/main/docs/dataset-test-component.adoc
index 5ec1df0..72a9cf3 100644
--- a/components/camel-dataset/src/main/docs/dataset-test-component.adoc
+++ b/components/camel-dataset/src/main/docs/dataset-test-component.adoc
@@ -45,7 +45,7 @@ pulled from before starting the test.
== URI Options
// component options: START
-The DataSet Test component supports 1 options, which are listed below.
+The DataSet Test component supports 3 options, which are listed below.
@@ -53,6 +53,8 @@ The DataSet Test component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -117,7 +119,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -125,7 +127,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.dataset-test.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.dataset-test.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.dataset-test.enabled* | Whether to enable auto configuration of the dataset-test component. This is enabled by default. | | Boolean
+| *camel.component.dataset-test.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is process [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-debezium-mongodb/src/main/docs/debezium-mongodb-component.adoc b/components/camel-debezium-mongodb/src/main/docs/debezium-mongodb-component.adoc
index 6bb7aa9..019e230 100644
--- a/components/camel-debezium-mongodb/src/main/docs/debezium-mongodb-component.adoc
+++ b/components/camel-debezium-mongodb/src/main/docs/debezium-mongodb-component.adoc
@@ -42,7 +42,7 @@ debezium-mongodb:name[?options]
// component options: START
-The Debezium MongoDB Connector component supports 2 options, which are listed below.
+The Debezium MongoDB Connector component supports 4 options, which are listed below.
@@ -51,6 +51,8 @@ The Debezium MongoDB Connector component supports 2 options, which are listed be
| Name | Description | Default | Type
| *configuration* (consumer) | Allow pre-configured Configurations to be set. | | MongoDbConnectorEmbeddedDebeziumConfiguration
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -141,7 +143,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 42 options, which are listed below.
+The component supports 44 options, which are listed below.
@@ -149,6 +151,7 @@ The component supports 42 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.debezium-mongodb.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.debezium-mongodb.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.debezium-mongodb.configuration.collection-blacklist* | Description is not available here, please check Debezium website for corresponding key 'collection.blacklist' description. | | String
| *camel.component.debezium-mongodb.configuration.collection-whitelist* | The collections for which changes are to be captured | | String
| *camel.component.debezium-mongodb.configuration.connect-backoff-initial-delay-ms* | The initial delay when trying to reconnect to a primary after a connection cannot be made or when no primary is available. Defaults to 1 second (1000 ms). | 1000 | Long
@@ -190,6 +193,7 @@ The component supports 42 options, which are listed below.
| *camel.component.debezium-mongodb.configuration.source-struct-version* | A version of the format of the publicly visible source part in the message | v2 | String
| *camel.component.debezium-mongodb.configuration.tombstones-on-delete* | Whether delete operations should be represented by a delete event and a subsquenttombstone event (true) or only by a delete event (false). Emitting the tombstone event (the default behavior) allows Kafka to completely delete all events pertaining to the given key once the source record got deleted. | false | Boolean
| *camel.component.debezium-mongodb.enabled* | Whether to enable auto configuration of the debezium-mongodb component. This is enabled by default. | | Boolean
+| *camel.component.debezium-mongodb.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is pro [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-debezium-mysql/src/main/docs/debezium-mysql-component.adoc b/components/camel-debezium-mysql/src/main/docs/debezium-mysql-component.adoc
index 804ff5e..243e947 100644
--- a/components/camel-debezium-mysql/src/main/docs/debezium-mysql-component.adoc
+++ b/components/camel-debezium-mysql/src/main/docs/debezium-mysql-component.adoc
@@ -52,7 +52,7 @@ debezium-mysql:name[?options]
// component options: START
-The Debezium MySQL Connector component supports 2 options, which are listed below.
+The Debezium MySQL Connector component supports 4 options, which are listed below.
@@ -61,6 +61,8 @@ The Debezium MySQL Connector component supports 2 options, which are listed belo
| Name | Description | Default | Type
| *configuration* (consumer) | Allow pre-configured Configurations to be set. | | MySqlConnectorEmbeddedDebeziumConfiguration
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -181,7 +183,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 72 options, which are listed below.
+The component supports 74 options, which are listed below.
@@ -189,6 +191,7 @@ The component supports 72 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.debezium-mysql.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.debezium-mysql.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.debezium-mysql.configuration.bigint-unsigned-handling-mode* | Specify how BIGINT UNSIGNED columns should be represented in change events, including:'precise' uses java.math.BigDecimal to represent values, which are encoded in the change events using a binary representation and Kafka Connect's 'org.apache.kafka.connect.data.Decimal' type; 'long' (the default) represents values using Java's 'long', which may not offer the precision but will be far easier to use in consum [...]
| *camel.component.debezium-mysql.configuration.binlog-buffer-size* | The size of a look-ahead buffer used by the binlog reader to decide whether the transaction in progress is going to be committed or rolled back. Use 0 to disable look-ahead buffering. Defaults to 0 (i.e. buffering is disabled). | 0 | Integer
| *camel.component.debezium-mysql.configuration.column-blacklist* | Description is not available here, please check Debezium website for corresponding key 'column.blacklist' description. | | String
@@ -260,6 +263,7 @@ The component supports 72 options, which are listed below.
| *camel.component.debezium-mysql.configuration.time-precision-mode* | Time, date and timestamps can be represented with different kinds of precisions, including:'adaptive_time_microseconds': the precision of date and timestamp values is based the database column's precision; but time fields always use microseconds precision;'connect': always represents time, date and timestamp values using Kafka Connect's built-in representations for Time, Date, and Timestamp, which uses millisecond pre [...]
| *camel.component.debezium-mysql.configuration.tombstones-on-delete* | Whether delete operations should be represented by a delete event and a subsquenttombstone event (true) or only by a delete event (false). Emitting the tombstone event (the default behavior) allows Kafka to completely delete all events pertaining to the given key once the source record got deleted. | false | Boolean
| *camel.component.debezium-mysql.enabled* | Whether to enable auto configuration of the debezium-mysql component. This is enabled by default. | | Boolean
+| *camel.component.debezium-mysql.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proce [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-debezium-postgres/src/main/docs/debezium-postgres-component.adoc b/components/camel-debezium-postgres/src/main/docs/debezium-postgres-component.adoc
index e590138..051af56 100644
--- a/components/camel-debezium-postgres/src/main/docs/debezium-postgres-component.adoc
+++ b/components/camel-debezium-postgres/src/main/docs/debezium-postgres-component.adoc
@@ -42,7 +42,7 @@ debezium-postgres:name[?options]
// component options: START
-The Debezium PostgresSQL Connector component supports 2 options, which are listed below.
+The Debezium PostgresSQL Connector component supports 4 options, which are listed below.
@@ -51,6 +51,8 @@ The Debezium PostgresSQL Connector component supports 2 options, which are liste
| Name | Description | Default | Type
| *configuration* (consumer) | Allow pre-configured Configurations to be set. | | PostgresConnectorEmbeddedDebeziumConfiguration
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -162,7 +164,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 63 options, which are listed below.
+The component supports 65 options, which are listed below.
@@ -170,6 +172,7 @@ The component supports 63 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.debezium-postgres.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.debezium-postgres.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.debezium-postgres.configuration.column-blacklist* | Description is not available here, please check Debezium website for corresponding key 'column.blacklist' description. | | String
| *camel.component.debezium-postgres.configuration.connector-class* | The name of the Java class for the connector | | Class
| *camel.component.debezium-postgres.configuration.database-dbname* | The name of the database the connector should be monitoring | | String
@@ -232,6 +235,7 @@ The component supports 63 options, which are listed below.
| *camel.component.debezium-postgres.configuration.tombstones-on-delete* | Whether delete operations should be represented by a delete event and a subsquenttombstone event (true) or only by a delete event (false). Emitting the tombstone event (the default behavior) allows Kafka to completely delete all events pertaining to the given key once the source record got deleted. | false | Boolean
| *camel.component.debezium-postgres.configuration.xmin-fetch-interval-ms* | Specify how often (in ms) the xmin will be fetched from the replication slot. This xmin value is exposed by the slot which gives a lower bound of where a new replication slot could start from. The lower the value, the more likely this value is to be the current 'true' value, but the bigger the performance cost. The bigger the value, the less likely this value is to be the current 'true' value, but the lower the [...]
| *camel.component.debezium-postgres.enabled* | Whether to enable auto configuration of the debezium-postgres component. This is enabled by default. | | Boolean
+| *camel.component.debezium-postgres.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is pr [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-debezium-sqlserver/src/main/docs/debezium-sqlserver-component.adoc b/components/camel-debezium-sqlserver/src/main/docs/debezium-sqlserver-component.adoc
index 1dc1cc1..9015bac 100644
--- a/components/camel-debezium-sqlserver/src/main/docs/debezium-sqlserver-component.adoc
+++ b/components/camel-debezium-sqlserver/src/main/docs/debezium-sqlserver-component.adoc
@@ -39,7 +39,7 @@ debezium-sqlserver:name[?options]
// component options: START
-The Debezium SQL Server Connector component supports 2 options, which are listed below.
+The Debezium SQL Server Connector component supports 4 options, which are listed below.
@@ -48,6 +48,8 @@ The Debezium SQL Server Connector component supports 2 options, which are listed
| Name | Description | Default | Type
| *configuration* (consumer) | Allow pre-configured Configurations to be set. | | SqlServerConnectorEmbeddedDebeziumConfiguration
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -140,7 +142,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 44 options, which are listed below.
+The component supports 46 options, which are listed below.
@@ -148,6 +150,7 @@ The component supports 44 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.debezium-sqlserver.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.debezium-sqlserver.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.debezium-sqlserver.configuration.column-blacklist* | Description is not available here, please check Debezium website for corresponding key 'column.blacklist' description. | | String
| *camel.component.debezium-sqlserver.configuration.connector-class* | The name of the Java class for the connector | | Class
| *camel.component.debezium-sqlserver.configuration.database-dbname* | The name of the database the connector should be monitoring. When working with a multi-tenant set-up, must be set to the CDB name. | | String
@@ -191,6 +194,7 @@ The component supports 44 options, which are listed below.
| *camel.component.debezium-sqlserver.configuration.table-whitelist* | The tables for which changes are to be captured | | String
| *camel.component.debezium-sqlserver.configuration.time-precision-mode* | Time, date, and timestamps can be represented with different kinds of precisions, including:'adaptive' (the default) bases the precision of time, date, and timestamp values on the database column's precision; 'adaptive_time_microseconds' like 'adaptive' mode, but TIME fields always use microseconds precision;'connect' always represents time, date, and timestamp values using Kafka Connect's built-in representations [...]
| *camel.component.debezium-sqlserver.enabled* | Whether to enable auto configuration of the debezium-sqlserver component. This is enabled by default. | | Boolean
+| *camel.component.debezium-sqlserver.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is p [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-digitalocean/src/main/docs/digitalocean-component.adoc b/components/camel-digitalocean/src/main/docs/digitalocean-component.adoc
index 441e8d1..56dad3d 100644
--- a/components/camel-digitalocean/src/main/docs/digitalocean-component.adoc
+++ b/components/camel-digitalocean/src/main/docs/digitalocean-component.adoc
@@ -35,7 +35,7 @@ The DigitalOcean component only supports producer endpoints so you cannot use th
// component options: START
-The DigitalOcean component supports 1 options, which are listed below.
+The DigitalOcean component supports 3 options, which are listed below.
@@ -43,6 +43,8 @@ The DigitalOcean component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -101,7 +103,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -109,7 +111,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.digitalocean.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.digitalocean.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.digitalocean.enabled* | Enable digitalocean component | true | Boolean
+| *camel.component.digitalocean.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is process [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-direct/src/main/docs/direct-component.adoc b/components/camel-direct/src/main/docs/direct-component.adoc
index b960ef9..56ff816 100644
--- a/components/camel-direct/src/main/docs/direct-component.adoc
+++ b/components/camel-direct/src/main/docs/direct-component.adoc
@@ -34,7 +34,7 @@ Where *someName* can be any string to uniquely identify the endpoint
// component options: START
-The Direct component supports 3 options, which are listed below.
+The Direct component supports 5 options, which are listed below.
@@ -44,6 +44,8 @@ The Direct component supports 3 options, which are listed below.
| *block* (producer) | If sending a message to a direct endpoint which has no active consumer, then we can tell the producer to block and wait for the consumer to become active. | true | boolean
| *timeout* (producer) | The timeout value to use if block is enabled. | 30000 | long
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -103,7 +105,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 4 options, which are listed below.
+The component supports 6 options, which are listed below.
@@ -112,7 +114,9 @@ The component supports 4 options, which are listed below.
| Name | Description | Default | Type
| *camel.component.direct.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
| *camel.component.direct.block* | If sending a message to a direct endpoint which has no active consumer, then we can tell the producer to block and wait for the consumer to become active. | true | Boolean
+| *camel.component.direct.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.direct.enabled* | Whether to enable auto configuration of the direct component. This is enabled by default. | | Boolean
+| *camel.component.direct.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed the [...]
| *camel.component.direct.timeout* | The timeout value to use if block is enabled. | 30000 | Long
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-directvm/src/main/docs/direct-vm-component.adoc b/components/camel-directvm/src/main/docs/direct-vm-component.adoc
index 06ae51a..21bd053 100644
--- a/components/camel-directvm/src/main/docs/direct-vm-component.adoc
+++ b/components/camel-directvm/src/main/docs/direct-vm-component.adoc
@@ -45,7 +45,7 @@ Where *someName* can be any string to uniquely identify the endpoint
// component options: START
-The Direct VM component supports 5 options, which are listed below.
+The Direct VM component supports 7 options, which are listed below.
@@ -57,6 +57,8 @@ The Direct VM component supports 5 options, which are listed below.
| *headerFilterStrategy* (advanced) | Sets a HeaderFilterStrategy that will only be applied on producer endpoints (on both directions: request and response). Default value: none. | | HeaderFilterStrategy
| *propagateProperties* (advanced) | Whether to propagate or not properties from the producer side to the consumer side, and vice versa. Default value: true. | true | boolean
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
diff --git a/components/camel-disruptor/src/main/docs/disruptor-component.adoc b/components/camel-disruptor/src/main/docs/disruptor-component.adoc
index 6b6b47a..4f1035e 100644
--- a/components/camel-disruptor/src/main/docs/disruptor-component.adoc
+++ b/components/camel-disruptor/src/main/docs/disruptor-component.adoc
@@ -99,7 +99,7 @@ All the following options are valid for both the **disruptor:** and
// component options: START
-The Disruptor component supports 8 options, which are listed below.
+The Disruptor component supports 10 options, which are listed below.
@@ -114,6 +114,8 @@ The Disruptor component supports 8 options, which are listed below.
| *queueSize* (common) | *Deprecated* To configure the ring buffer size | | int
| *bufferSize* (common) | To configure the ring buffer size | 1024 | int
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -177,7 +179,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 18 options, which are listed below.
+The component supports 22 options, which are listed below.
@@ -185,6 +187,7 @@ The component supports 18 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.disruptor-vm.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.disruptor-vm.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.disruptor-vm.buffer-size* | To configure the ring buffer size | 1024 | Integer
| *camel.component.disruptor-vm.default-block-when-full* | To configure the default value for block when full The default value is true. | true | Boolean
| *camel.component.disruptor-vm.default-concurrent-consumers* | To configure the default number of concurrent consumers | 1 | Integer
@@ -192,7 +195,9 @@ The component supports 18 options, which are listed below.
| *camel.component.disruptor-vm.default-producer-type* | To configure the default value for DisruptorProducerType The default value is Multi. | | DisruptorProducerType
| *camel.component.disruptor-vm.default-wait-strategy* | To configure the default value for DisruptorWaitStrategy The default value is Blocking. | | DisruptorWaitStrategy
| *camel.component.disruptor-vm.enabled* | Enable disruptor-vm component | true | Boolean
+| *camel.component.disruptor-vm.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is process [...]
| *camel.component.disruptor.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.disruptor.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.disruptor.buffer-size* | To configure the ring buffer size | 1024 | Integer
| *camel.component.disruptor.default-block-when-full* | To configure the default value for block when full The default value is true. | true | Boolean
| *camel.component.disruptor.default-concurrent-consumers* | To configure the default number of concurrent consumers | 1 | Integer
@@ -200,6 +205,7 @@ The component supports 18 options, which are listed below.
| *camel.component.disruptor.default-producer-type* | To configure the default value for DisruptorProducerType The default value is Multi. | | DisruptorProducerType
| *camel.component.disruptor.default-wait-strategy* | To configure the default value for DisruptorWaitStrategy The default value is Blocking. | | DisruptorWaitStrategy
| *camel.component.disruptor.enabled* | Enable disruptor component | true | Boolean
+| *camel.component.disruptor.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed [...]
| *camel.component.disruptor-vm.queue-size* | *Deprecated* To configure the ring buffer size | | Integer
| *camel.component.disruptor.queue-size* | *Deprecated* To configure the ring buffer size | | Integer
|===
diff --git a/components/camel-dns/src/main/docs/dns-component.adoc b/components/camel-dns/src/main/docs/dns-component.adoc
index 381f1ef..87d18d1 100644
--- a/components/camel-dns/src/main/docs/dns-component.adoc
+++ b/components/camel-dns/src/main/docs/dns-component.adoc
@@ -55,7 +55,7 @@ This component only supports producers.
// component options: START
-The DNS component supports 1 options, which are listed below.
+The DNS component supports 3 options, which are listed below.
@@ -63,6 +63,8 @@ The DNS component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -114,7 +116,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -122,7 +124,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.dns.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.dns.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.dns.enabled* | Enable dns component | true | Boolean
+| *camel.component.dns.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then c [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-docker/src/main/docs/docker-component.adoc b/components/camel-docker/src/main/docs/docker-component.adoc
index 0eaa5bc..119fe3a 100644
--- a/components/camel-docker/src/main/docs/docker-component.adoc
+++ b/components/camel-docker/src/main/docs/docker-component.adoc
@@ -27,7 +27,7 @@ Where *operation* is the specific action to perform on Docker.
== General Options
// component options: START
-The Docker component supports 2 options, which are listed below.
+The Docker component supports 4 options, which are listed below.
@@ -36,6 +36,8 @@ The Docker component supports 2 options, which are listed below.
| Name | Description | Default | Type
| *configuration* (advanced) | To use the shared docker configuration | | DockerConfiguration
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -105,7 +107,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 20 options, which are listed below.
+The component supports 22 options, which are listed below.
@@ -113,6 +115,7 @@ The component supports 20 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.docker.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.docker.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.docker.configuration.cert-path* | Location containing the SSL certificate chain | | String
| *camel.component.docker.configuration.cmd-exec-factory* | The fully qualified class name of the DockerCmdExecFactory implementation to use | com.github.dockerjava.netty.NettyDockerCmdExecFactory | String
| *camel.component.docker.configuration.email* | Email address associated with the user | | String
@@ -132,6 +135,7 @@ The component supports 20 options, which are listed below.
| *camel.component.docker.configuration.tls-verify* | Check TLS | false | Boolean
| *camel.component.docker.configuration.username* | User name to authenticate with | | String
| *camel.component.docker.enabled* | Enable docker component | true | Boolean
+| *camel.component.docker.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed the [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-dozer/src/main/docs/dozer-component.adoc b/components/camel-dozer/src/main/docs/dozer-component.adoc
index 77bd4d2..f640988 100644
--- a/components/camel-dozer/src/main/docs/dozer-component.adoc
+++ b/components/camel-dozer/src/main/docs/dozer-component.adoc
@@ -61,7 +61,7 @@ from("direct:orderInput").
== Options
// component options: START
-The Dozer component supports 1 options, which are listed below.
+The Dozer component supports 3 options, which are listed below.
@@ -69,6 +69,8 @@ The Dozer component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -124,7 +126,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -132,7 +134,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.dozer.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.dozer.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.dozer.enabled* | Enable dozer component | true | Boolean
+| *camel.component.dozer.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-drill/src/main/docs/drill-component.adoc b/components/camel-drill/src/main/docs/drill-component.adoc
index ce9bd8e..40b4565 100644
--- a/components/camel-drill/src/main/docs/drill-component.adoc
+++ b/components/camel-drill/src/main/docs/drill-component.adoc
@@ -41,7 +41,7 @@ The producer executes a query using the *CamelDrillQuery* header and puts the re
== Options
// component options: START
-The Drill component supports 1 options, which are listed below.
+The Drill component supports 3 options, which are listed below.
@@ -49,6 +49,8 @@ The Drill component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -104,7 +106,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -112,7 +114,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.drill.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.drill.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.drill.enabled* | Enable drill component | true | Boolean
+| *camel.component.drill.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-dropbox/src/main/docs/dropbox-component.adoc b/components/camel-dropbox/src/main/docs/dropbox-component.adoc
index 3a29e27..e901201 100644
--- a/components/camel-dropbox/src/main/docs/dropbox-component.adoc
+++ b/components/camel-dropbox/src/main/docs/dropbox-component.adoc
@@ -70,7 +70,7 @@ https://www.dropbox.com/developers/core/start/java[Dropbox
documentation] that explains how to get them.
// component options: START
-The Dropbox component supports 1 options, which are listed below.
+The Dropbox component supports 3 options, which are listed below.
@@ -78,6 +78,8 @@ The Dropbox component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -138,7 +140,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -146,7 +148,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.dropbox.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.dropbox.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.dropbox.enabled* | Enable dropbox component | true | Boolean
+| *camel.component.dropbox.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-ehcache/src/main/docs/ehcache-component.adoc b/components/camel-ehcache/src/main/docs/ehcache-component.adoc
index b1faec4..154c6c1 100644
--- a/components/camel-ehcache/src/main/docs/ehcache-component.adoc
+++ b/components/camel-ehcache/src/main/docs/ehcache-component.adoc
@@ -42,7 +42,7 @@ format, `?option=value&option=#beanRef&...`
// component options: START
-The Ehcache component supports 7 options, which are listed below.
+The Ehcache component supports 9 options, which are listed below.
@@ -56,6 +56,8 @@ The Ehcache component supports 7 options, which are listed below.
| *cachesConfigurations* (common) | A map of caches configurations to be used to create caches. | | Map
| *cacheConfigurationUri* (common) | URI pointing to the Ehcache XML configuration file's location | | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -123,7 +125,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 25 options, which are listed below.
+The component supports 27 options, which are listed below.
@@ -131,6 +133,7 @@ The component supports 25 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.ehcache.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.ehcache.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.ehcache.cache-configuration* | The default cache configuration to be used to create caches. The option is a org.ehcache.config.CacheConfiguration type. | | String
| *camel.component.ehcache.cache-configuration-uri* | URI pointing to the Ehcache XML configuration file's location | | String
| *camel.component.ehcache.cache-manager* | The cache manager. The option is a org.ehcache.CacheManager type. | | String
@@ -154,6 +157,7 @@ The component supports 25 options, which are listed below.
| *camel.component.ehcache.customizer.cache-manager.enabled* | Enable or disable the cache-manager customizer. | true | Boolean
| *camel.component.ehcache.customizer.cache-manager.override* | Configure if the cache manager eventually set on the component should be overridden by the customizer. | false | Boolean
| *camel.component.ehcache.enabled* | Enable ehcache component | true | Boolean
+| *camel.component.ehcache.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
| *camel.component.ehcache.configuration.config-uri* | *Deprecated* URI pointing to the Ehcache XML configuration file's location | | String
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-elasticsearch-rest/src/main/docs/elasticsearch-rest-component.adoc b/components/camel-elasticsearch-rest/src/main/docs/elasticsearch-rest-component.adoc
index fb8db17..58b9fe2 100644
--- a/components/camel-elasticsearch-rest/src/main/docs/elasticsearch-rest-component.adoc
+++ b/components/camel-elasticsearch-rest/src/main/docs/elasticsearch-rest-component.adoc
@@ -38,7 +38,7 @@ elasticsearch-rest://clusterName[?options]
== Endpoint Options
// component options: START
-The Elastichsearch Rest component supports 12 options, which are listed below.
+The Elastichsearch Rest component supports 14 options, which are listed below.
@@ -57,6 +57,8 @@ The Elastichsearch Rest component supports 12 options, which are listed below.
| *snifferInterval* (advanced) | The interval between consecutive ordinary sniff executions in milliseconds. Will be honoured when sniffOnFailure is disabled or when there are no failures between consecutive sniff executions | 300000 | int
| *sniffAfterFailureDelay* (advanced) | The delay of a sniff execution scheduled after a failure (in milliseconds) | 60000 | int
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -118,7 +120,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 13 options, which are listed below.
+The component supports 15 options, which are listed below.
@@ -126,12 +128,14 @@ The component supports 13 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.elasticsearch-rest.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.elasticsearch-rest.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.elasticsearch-rest.client* | To use an existing configured Elasticsearch client, instead of creating a client per endpoint. This allow to customize the client with specific settings. The option is a org.elasticsearch.client.RestClient type. | | String
| *camel.component.elasticsearch-rest.connection-timeout* | The time in ms to wait before connection will timeout. | 30000 | Integer
| *camel.component.elasticsearch-rest.enable-s-s-l* | Enable SSL | false | Boolean
| *camel.component.elasticsearch-rest.enable-sniffer* | Enable automatically discover nodes from a running Elasticsearch cluster | false | Boolean
| *camel.component.elasticsearch-rest.enabled* | Whether to enable auto configuration of the elasticsearch-rest component. This is enabled by default. | | Boolean
| *camel.component.elasticsearch-rest.host-addresses* | Comma separated list with ip:port formatted remote transport addresses to use. The ip and port options must be left blank for hostAddresses to be considered instead. | | String
+| *camel.component.elasticsearch-rest.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is p [...]
| *camel.component.elasticsearch-rest.max-retry-timeout* | The time in ms before retry | 30000 | Integer
| *camel.component.elasticsearch-rest.password* | Password for authenticate | | String
| *camel.component.elasticsearch-rest.sniff-after-failure-delay* | The delay of a sniff execution scheduled after a failure (in milliseconds) | 60000 | Integer
diff --git a/components/camel-elsql/src/main/docs/elsql-component.adoc b/components/camel-elsql/src/main/docs/elsql-component.adoc
index ed361e5..1561f48 100644
--- a/components/camel-elsql/src/main/docs/elsql-component.adoc
+++ b/components/camel-elsql/src/main/docs/elsql-component.adoc
@@ -56,7 +56,7 @@ If a named parameter cannot be resolved, then an exception is thrown.
== Options
// component options: START
-The ElSQL component supports 5 options, which are listed below.
+The ElSQL component supports 7 options, which are listed below.
@@ -68,6 +68,8 @@ The ElSQL component supports 5 options, which are listed below.
| *elSqlConfig* (advanced) | To use a specific configured ElSqlConfig. It may be better to use the databaseVendor option instead. | | ElSqlConfig
| *resourceUri* (common) | The resource file which contains the elsql SQL statements to use. You can specify multiple resources separated by comma. The resources are loaded on the classpath by default, you can prefix with file: to load from file system. Notice you can set this option on the component and then you do not have to configure this on the endpoint. | | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -165,7 +167,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 6 options, which are listed below.
+The component supports 8 options, which are listed below.
@@ -173,10 +175,12 @@ The component supports 6 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.elsql.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.elsql.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.elsql.data-source* | Sets the DataSource to use to communicate with the database. The option is a javax.sql.DataSource type. | | String
| *camel.component.elsql.database-vendor* | To use a vendor specific com.opengamma.elsql.ElSqlConfig | | ElSqlDatabaseVendor
| *camel.component.elsql.el-sql-config* | To use a specific configured ElSqlConfig. It may be better to use the databaseVendor option instead. The option is a com.opengamma.elsql.ElSqlConfig type. | | String
| *camel.component.elsql.enabled* | Enable elsql component | true | Boolean
+| *camel.component.elsql.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
| *camel.component.elsql.resource-uri* | The resource file which contains the elsql SQL statements to use. You can specify multiple resources separated by comma. The resources are loaded on the classpath by default, you can prefix with file: to load from file system. Notice you can set this option on the component and then you do not have to configure this on the endpoint. | | String
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-etcd/src/main/docs/etcd-component.adoc b/components/camel-etcd/src/main/docs/etcd-component.adoc
index 809e320..d574d51 100644
--- a/components/camel-etcd/src/main/docs/etcd-component.adoc
+++ b/components/camel-etcd/src/main/docs/etcd-component.adoc
@@ -22,7 +22,7 @@ etcd:namespace/path[?options]
== URI Options
// component options: START
-The Etcd component supports 7 options, which are listed below.
+The Etcd component supports 9 options, which are listed below.
@@ -36,6 +36,8 @@ The Etcd component supports 7 options, which are listed below.
| *configuration* (advanced) | Sets the common configuration shared among endpoints | | EtcdConfiguration
| *useGlobalSslContext Parameters* (security) | Enable usage of global SSL context parameters. | false | boolean
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -115,7 +117,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 17 options, which are listed below.
+The component supports 19 options, which are listed below.
@@ -123,6 +125,7 @@ The component supports 17 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.etcd.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.etcd.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.etcd.configuration.from-index* | The index to watch from | 0 | Long
| *camel.component.etcd.configuration.password* | The password to use for basic authentication. | | String
| *camel.component.etcd.configuration.recursive* | To apply an action recursively. | false | Boolean
@@ -134,6 +137,7 @@ The component supports 17 options, which are listed below.
| *camel.component.etcd.configuration.uris* | To set the URIs the client connects. | http://localhost:2379,http://localhost:4001 | String
| *camel.component.etcd.configuration.user-name* | The user name to use for basic authentication. | | String
| *camel.component.etcd.enabled* | Enable etcd component | true | Boolean
+| *camel.component.etcd.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
| *camel.component.etcd.password* | The password to use for basic authentication. | | String
| *camel.component.etcd.ssl-context-parameters* | To configure security using SSLContextParameters. The option is a org.apache.camel.support.jsse.SSLContextParameters type. | | String
| *camel.component.etcd.uris* | To set the URIs the client connects. | | String
diff --git a/components/camel-eventadmin/src/main/docs/eventadmin-component.adoc b/components/camel-eventadmin/src/main/docs/eventadmin-component.adoc
index 0a7a863..b9269dd 100644
--- a/components/camel-eventadmin/src/main/docs/eventadmin-component.adoc
+++ b/components/camel-eventadmin/src/main/docs/eventadmin-component.adoc
@@ -37,7 +37,7 @@ where `topic` is the name of the topic to listen too.
== URI options
// component options: START
-The OSGi EventAdmin component supports 2 options, which are listed below.
+The OSGi EventAdmin component supports 4 options, which are listed below.
@@ -46,6 +46,8 @@ The OSGi EventAdmin component supports 2 options, which are listed below.
| Name | Description | Default | Type
| *bundleContext* (common) | The OSGi BundleContext is automatic injected by Camel | | BundleContext
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
diff --git a/components/camel-exec/src/main/docs/exec-component.adoc b/components/camel-exec/src/main/docs/exec-component.adoc
index 50ca4b5..2bd4c88 100644
--- a/components/camel-exec/src/main/docs/exec-component.adoc
+++ b/components/camel-exec/src/main/docs/exec-component.adoc
@@ -38,7 +38,7 @@ executable must in the system path.
== URI options
// component options: START
-The Exec component supports 1 options, which are listed below.
+The Exec component supports 3 options, which are listed below.
@@ -46,6 +46,8 @@ The Exec component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -103,7 +105,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -111,7 +113,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.exec.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.exec.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.exec.enabled* | Enable exec component | true | Boolean
+| *camel.component.exec.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-facebook/src/main/docs/facebook-component.adoc b/components/camel-facebook/src/main/docs/facebook-component.adoc
index 9436ec9..dfad768 100644
--- a/components/camel-facebook/src/main/docs/facebook-component.adoc
+++ b/components/camel-facebook/src/main/docs/facebook-component.adoc
@@ -57,7 +57,7 @@ to application APIs.
// component options: START
-The Facebook component supports 2 options, which are listed below.
+The Facebook component supports 4 options, which are listed below.
@@ -66,6 +66,8 @@ The Facebook component supports 2 options, which are listed below.
| Name | Description | Default | Type
| *configuration* (advanced) | To use the shared configuration | | FacebookConfiguration
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -220,7 +222,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 29 options, which are listed below.
+The component supports 31 options, which are listed below.
@@ -228,6 +230,7 @@ The component supports 29 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.facebook.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.facebook.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.facebook.configuration.client-u-r-l* | Facebook4J API client URL | | String
| *camel.component.facebook.configuration.client-version* | Facebook4J client API version | | String
| *camel.component.facebook.configuration.debug-enabled* | Enables deubg output. Effective only with the embedded logger | false | Boolean
@@ -256,6 +259,7 @@ The component supports 29 options, which are listed below.
| *camel.component.facebook.configuration.use-s-s-l* | Use SSL | true | Boolean
| *camel.component.facebook.configuration.video-base-u-r-l* | Video API base URL | https://graph-video.facebook.com/ | String
| *camel.component.facebook.enabled* | Enable facebook component | true | Boolean
+| *camel.component.facebook.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed t [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-fhir/camel-fhir-component/src/main/docs/fhir-component.adoc b/components/camel-fhir/camel-fhir-component/src/main/docs/fhir-component.adoc
index cec2978..51fbcbb 100644
--- a/components/camel-fhir/camel-fhir-component/src/main/docs/fhir-component.adoc
+++ b/components/camel-fhir/camel-fhir-component/src/main/docs/fhir-component.adoc
@@ -51,7 +51,7 @@ Endpoint prefix can be one of:
// component options: START
-The FHIR component supports 2 options, which are listed below.
+The FHIR component supports 4 options, which are listed below.
@@ -60,6 +60,8 @@ The FHIR component supports 2 options, which are listed below.
| Name | Description | Default | Type
| *configuration* (common) | To use the shared configuration | | FhirConfiguration
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -154,7 +156,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 27 options, which are listed below.
+The component supports 29 options, which are listed below.
@@ -162,6 +164,7 @@ The component supports 27 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.fhir.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.fhir.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.fhir.configuration.access-token* | What sub operation to use for the selected operation | | String
| *camel.component.fhir.configuration.api-name* | What kind of operation to perform | | FhirApiName
| *camel.component.fhir.configuration.client* | What sub operation to use for the selected operation | | IGenericClient
@@ -188,5 +191,6 @@ The component supports 27 options, which are listed below.
| *camel.component.fhir.configuration.username* | What sub operation to use for the selected operation | | String
| *camel.component.fhir.configuration.validation-mode* | What sub operation to use for the selected operation | ONCE | String
| *camel.component.fhir.enabled* | Whether to enable auto configuration of the fhir component. This is enabled by default. | | Boolean
+| *camel.component.fhir.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-file-watch/src/main/docs/file-watch-component.adoc b/components/camel-file-watch/src/main/docs/file-watch-component.adoc
index a7e126f..938f0ea 100644
--- a/components/camel-file-watch/src/main/docs/file-watch-component.adoc
+++ b/components/camel-file-watch/src/main/docs/file-watch-component.adoc
@@ -12,7 +12,7 @@ This component can be used to watch file modification events in folder. It is ba
== URI Options
// component options: START
-The file-watch component supports 6 options, which are listed below.
+The file-watch component supports 8 options, which are listed below.
@@ -25,6 +25,8 @@ The file-watch component supports 6 options, which are listed below.
| *fileHasher* (consumer) | Reference to io.methvin.watcher.hashing.FileHasher. This prevents emitting duplicate events on some platforms. For working with large files and if you dont need detect multiple modifications per second per file, use #lastModifiedTimeFileHasher. You can also provide custom implementation in registry. | #murmur3FFileHasher | FileHasher
| *useFileHashing* (consumer) | Enables or disables file hashing to detect duplicate events. If you disable this, you can get some events multiple times on some platforms and JDKs. Check java.nio.file.WatchService limitations for your target platform. | true | boolean
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -87,7 +89,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 7 options, which are listed below.
+The component supports 9 options, which are listed below.
@@ -95,9 +97,11 @@ The component supports 7 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.file-watch.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.file-watch.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.file-watch.concurrent-consumers* | The number of concurrent consumers. Increase this value, if your route is slow to prevent buffering in queue. | 1 | Integer
| *camel.component.file-watch.enabled* | Whether to enable auto configuration of the file-watch component. This is enabled by default. | | Boolean
| *camel.component.file-watch.file-hasher* | Reference to io.methvin.watcher.hashing.FileHasher. This prevents emitting duplicate events on some platforms. For working with large files and if you dont need detect multiple modifications per second per file, use #lastModifiedTimeFileHasher. You can also provide custom implementation in registry. The option is a io.methvin.watcher.hashing.FileHasher type. | | String
+| *camel.component.file-watch.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed [...]
| *camel.component.file-watch.poll-threads* | The number of threads polling WatchService. Increase this value, if you see OVERFLOW messages in log. | 1 | Integer
| *camel.component.file-watch.queue-size* | Maximum size of queue between WatchService and consumer. Unbounded by default. | 2147483647 | Integer
| *camel.component.file-watch.use-file-hashing* | Enables or disables file hashing to detect duplicate events. If you disable this, you can get some events multiple times on some platforms and JDKs. Check java.nio.file.WatchService limitations for your target platform. | true | Boolean
diff --git a/components/camel-file/src/main/docs/file-component.adoc b/components/camel-file/src/main/docs/file-component.adoc
index 346d51a..43efa3b 100644
--- a/components/camel-file/src/main/docs/file-component.adoc
+++ b/components/camel-file/src/main/docs/file-component.adoc
@@ -57,7 +57,7 @@ options and `doneFileName` option that you can use. See also the section
== URI Options
// component options: START
-The File component supports 1 options, which are listed below.
+The File component supports 3 options, which are listed below.
@@ -65,6 +65,8 @@ The File component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -225,7 +227,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -233,7 +235,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.file.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.file.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.file.enabled* | Whether to enable auto configuration of the file component. This is enabled by default. | | Boolean
+| *camel.component.file.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-flatpack/src/main/docs/flatpack-component.adoc b/components/camel-flatpack/src/main/docs/flatpack-component.adoc
index a991453..ea8470d 100644
--- a/components/camel-flatpack/src/main/docs/flatpack-component.adoc
+++ b/components/camel-flatpack/src/main/docs/flatpack-component.adoc
@@ -46,7 +46,7 @@ You can append query options to the URI in the following format,
== URI Options
// component options: START
-The Flatpack component supports 1 options, which are listed below.
+The Flatpack component supports 3 options, which are listed below.
@@ -54,6 +54,8 @@ The Flatpack component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -129,7 +131,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 12 options, which are listed below.
+The component supports 14 options, which are listed below.
@@ -137,7 +139,9 @@ The component supports 12 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.flatpack.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.flatpack.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.flatpack.enabled* | Enable flatpack component | true | Boolean
+| *camel.component.flatpack.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed t [...]
| *camel.dataformat.flatpack.allow-short-lines* | Allows for lines to be shorter than expected and ignores the extra characters | false | Boolean
| *camel.dataformat.flatpack.content-type-header* | Whether the data format should set the Content-Type header with the type from the data format if the data format is capable of doing so. For example application/xml for data formats marshalling to XML, or application/json for data formats marshalling to JSon etc. | false | Boolean
| *camel.dataformat.flatpack.definition* | The flatpack pzmap configuration file. Can be omitted in simpler situations, but its preferred to use the pzmap. | | String
diff --git a/components/camel-flatpack/src/main/docs/flatpack-dataformat.adoc b/components/camel-flatpack/src/main/docs/flatpack-dataformat.adoc
index e8b4a50..e0bb2a4 100644
--- a/components/camel-flatpack/src/main/docs/flatpack-dataformat.adoc
+++ b/components/camel-flatpack/src/main/docs/flatpack-dataformat.adoc
@@ -56,7 +56,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 12 options, which are listed below.
+The component supports 14 options, which are listed below.
@@ -64,7 +64,9 @@ The component supports 12 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.flatpack.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.flatpack.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.flatpack.enabled* | Enable flatpack component | true | Boolean
+| *camel.component.flatpack.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed t [...]
| *camel.dataformat.flatpack.allow-short-lines* | Allows for lines to be shorter than expected and ignores the extra characters | false | Boolean
| *camel.dataformat.flatpack.content-type-header* | Whether the data format should set the Content-Type header with the type from the data format if the data format is capable of doing so. For example application/xml for data formats marshalling to XML, or application/json for data formats marshalling to JSon etc. | false | Boolean
| *camel.dataformat.flatpack.definition* | The flatpack pzmap configuration file. Can be omitted in simpler situations, but its preferred to use the pzmap. | | String
diff --git a/components/camel-flink/src/main/docs/flink-component.adoc b/components/camel-flink/src/main/docs/flink-component.adoc
index bc98ecf..2883e89 100644
--- a/components/camel-flink/src/main/docs/flink-component.adoc
+++ b/components/camel-flink/src/main/docs/flink-component.adoc
@@ -97,7 +97,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 6 options, which are listed below.
+The component supports 8 options, which are listed below.
@@ -105,11 +105,13 @@ The component supports 6 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.flink.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.flink.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.flink.data-set* | DataSet to compute against. The option is a org.apache.flink.api.java.DataSet type. | | String
| *camel.component.flink.data-set-callback* | Function performing action against a DataSet. The option is a org.apache.camel.component.flink.DataSetCallback type. | | String
| *camel.component.flink.data-stream* | DataStream to compute against. The option is a org.apache.flink.streaming.api.datastream.DataStream type. | | String
| *camel.component.flink.data-stream-callback* | Function performing action against a DataStream. The option is a org.apache.camel.component.flink.DataStreamCallback type. | | String
| *camel.component.flink.enabled* | Enable flink component | true | Boolean
+| *camel.component.flink.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
|===
// spring-boot-auto-configure options: END
@@ -122,7 +124,7 @@ The component supports 6 options, which are listed below.
// component options: START
-The Flink component supports 5 options, which are listed below.
+The Flink component supports 7 options, which are listed below.
@@ -134,6 +136,8 @@ The Flink component supports 5 options, which are listed below.
| *dataSetCallback* (producer) | Function performing action against a DataSet. | | DataSetCallback
| *dataStreamCallback* (producer) | Function performing action against a DataStream. | | DataStreamCallback
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
diff --git a/components/camel-fop/src/main/docs/fop-component.adoc b/components/camel-fop/src/main/docs/fop-component.adoc
index 98b079c..d479f3c 100644
--- a/components/camel-fop/src/main/docs/fop-component.adoc
+++ b/components/camel-fop/src/main/docs/fop-component.adoc
@@ -66,7 +66,7 @@ The complete list of valid output formats can be found in the `MimeConstants.jav
== Endpoint Options
// component options: START
-The FOP component supports 1 options, which are listed below.
+The FOP component supports 3 options, which are listed below.
@@ -74,6 +74,8 @@ The FOP component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -127,7 +129,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -135,7 +137,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.fop.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.fop.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.fop.enabled* | Enable fop component | true | Boolean
+| *camel.component.fop.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then c [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-freemarker/src/main/docs/freemarker-component.adoc b/components/camel-freemarker/src/main/docs/freemarker-component.adoc
index 30ebe48..7501440 100644
--- a/components/camel-freemarker/src/main/docs/freemarker-component.adoc
+++ b/components/camel-freemarker/src/main/docs/freemarker-component.adoc
@@ -44,7 +44,7 @@ You can append query options to the URI in the following format,
// component options: START
-The Freemarker component supports 2 options, which are listed below.
+The Freemarker component supports 4 options, which are listed below.
@@ -53,6 +53,8 @@ The Freemarker component supports 2 options, which are listed below.
| Name | Description | Default | Type
| *configuration* (advanced) | To use an existing freemarker.template.Configuration instance as the configuration. | | Configuration
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -110,7 +112,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 3 options, which are listed below.
+The component supports 5 options, which are listed below.
@@ -118,8 +120,10 @@ The component supports 3 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.freemarker.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.freemarker.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.freemarker.configuration* | To use an existing freemarker.template.Configuration instance as the configuration. The option is a freemarker.template.Configuration type. | | String
| *camel.component.freemarker.enabled* | Enable freemarker component | true | Boolean
+| *camel.component.freemarker.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-ftp/src/main/docs/ftp-component.adoc b/components/camel-ftp/src/main/docs/ftp-component.adoc
index a349767..f61069f 100644
--- a/components/camel-ftp/src/main/docs/ftp-component.adoc
+++ b/components/camel-ftp/src/main/docs/ftp-component.adoc
@@ -71,7 +71,7 @@ The options below are exclusive for the FTP component.
// component options: START
-The FTP component supports 1 options, which are listed below.
+The FTP component supports 3 options, which are listed below.
@@ -79,6 +79,8 @@ The FTP component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -239,7 +241,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -247,7 +249,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.ftp.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.ftp.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.ftp.enabled* | Enable \ftp component | true | Boolean
+| *camel.component.ftp.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then c [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-ftp/src/main/docs/ftps-component.adoc b/components/camel-ftp/src/main/docs/ftps-component.adoc
index f3a33c0..8b1f1c1 100644
--- a/components/camel-ftp/src/main/docs/ftps-component.adoc
+++ b/components/camel-ftp/src/main/docs/ftps-component.adoc
@@ -30,7 +30,7 @@ For more information you can look at xref:ftp-component.adoc[FTP component]
The options below are exclusive for the FTPS component.
// component options: START
-The FTPS component supports 2 options, which are listed below.
+The FTPS component supports 4 options, which are listed below.
@@ -39,6 +39,8 @@ The FTPS component supports 2 options, which are listed below.
| Name | Description | Default | Type
| *useGlobalSslContext Parameters* (security) | Enable usage of global SSL context parameters. | false | boolean
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -206,7 +208,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 3 options, which are listed below.
+The component supports 5 options, which are listed below.
@@ -214,7 +216,9 @@ The component supports 3 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.ftps.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.ftps.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.ftps.enabled* | Enable \ftps component | true | Boolean
+| *camel.component.ftps.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
| *camel.component.ftps.use-global-ssl-context-parameters* | Enable usage of global SSL context parameters. | false | Boolean
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-ftp/src/main/docs/sftp-component.adoc b/components/camel-ftp/src/main/docs/sftp-component.adoc
index 34c2177..f814ed9 100644
--- a/components/camel-ftp/src/main/docs/sftp-component.adoc
+++ b/components/camel-ftp/src/main/docs/sftp-component.adoc
@@ -30,7 +30,7 @@ For more information you can look at xref:ftp-component.adoc[FTP component]
The options below are exclusive for the FTPS component.
// component options: START
-The SFTP component supports 1 options, which are listed below.
+The SFTP component supports 3 options, which are listed below.
@@ -38,6 +38,8 @@ The SFTP component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
diff --git a/components/camel-ganglia/src/main/docs/ganglia-component.adoc b/components/camel-ganglia/src/main/docs/ganglia-component.adoc
index f3de54a..1b67eba 100644
--- a/components/camel-ganglia/src/main/docs/ganglia-component.adoc
+++ b/components/camel-ganglia/src/main/docs/ganglia-component.adoc
@@ -55,7 +55,7 @@ You can append query options to the URI in the following format,
// component options: START
-The Ganglia component supports 2 options, which are listed below.
+The Ganglia component supports 4 options, which are listed below.
@@ -64,6 +64,8 @@ The Ganglia component supports 2 options, which are listed below.
| Name | Description | Default | Type
| *configuration* (advanced) | To use the shared configuration | | GangliaConfiguration
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -131,7 +133,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 16 options, which are listed below.
+The component supports 18 options, which are listed below.
@@ -139,6 +141,7 @@ The component supports 16 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.ganglia.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.ganglia.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.ganglia.configuration.dmax* | Minumum time in seconds before Ganglia will purge the metric value if it expires. Set to 0 and the value will remain in Ganglia indefinitely until a gmond agent restart. | 0 | Integer
| *camel.component.ganglia.configuration.group-name* | The group that the metric belongs to. | java | String
| *camel.component.ganglia.configuration.host* | Host name for Ganglia server | 239.2.11.71 | String
@@ -154,6 +157,7 @@ The component supports 16 options, which are listed below.
| *camel.component.ganglia.configuration.units* | Any unit of measurement that qualifies the metric, e.g. widgets, litres, bytes. Do not include a prefix such as k (kilo) or m (milli), other tools may scale the units later. The value should be unscaled. | | String
| *camel.component.ganglia.configuration.wire-format31x* | Use the wire format of Ganglia 3.1.0 and later versions. Set this to false to use Ganglia 3.0.x or earlier. | true | Boolean
| *camel.component.ganglia.enabled* | Enable ganglia component | true | Boolean
+| *camel.component.ganglia.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-geocoder/src/main/docs/geocoder-component.adoc b/components/camel-geocoder/src/main/docs/geocoder-component.adoc
index caca77a..89211ea 100644
--- a/components/camel-geocoder/src/main/docs/geocoder-component.adoc
+++ b/components/camel-geocoder/src/main/docs/geocoder-component.adoc
@@ -37,7 +37,7 @@ geocoder:latlng:latitude,longitude[?options]
// component options: START
-The Geocoder component supports 1 options, which are listed below.
+The Geocoder component supports 3 options, which are listed below.
@@ -45,6 +45,8 @@ The Geocoder component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -110,7 +112,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -118,7 +120,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.geocoder.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.geocoder.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.geocoder.enabled* | Enable geocoder component | true | Boolean
+| *camel.component.geocoder.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed t [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-git/src/main/docs/git-component.adoc b/components/camel-git/src/main/docs/git-component.adoc
index 3d1163d..20e493c 100644
--- a/components/camel-git/src/main/docs/git-component.adoc
+++ b/components/camel-git/src/main/docs/git-component.adoc
@@ -34,7 +34,7 @@ repository.
// component options: START
-The Git component supports 1 options, which are listed below.
+The Git component supports 3 options, which are listed below.
@@ -42,6 +42,8 @@ The Git component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -106,7 +108,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -114,7 +116,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.git.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.git.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.git.enabled* | Enable git component | true | Boolean
+| *camel.component.git.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then c [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-github/src/main/docs/github-component.adoc b/components/camel-github/src/main/docs/github-component.adoc
index 3e81273..01ca333 100644
--- a/components/camel-github/src/main/docs/github-component.adoc
+++ b/components/camel-github/src/main/docs/github-component.adoc
@@ -50,7 +50,7 @@ Note that these can be configured directly through the endpoint.
// component options: START
-The GitHub component supports 1 options, which are listed below.
+The GitHub component supports 3 options, which are listed below.
@@ -58,6 +58,8 @@ The GitHub component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -121,7 +123,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -129,7 +131,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.github.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.github.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.github.enabled* | Enable github component | true | Boolean
+| *camel.component.github.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed the [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-google-bigquery/src/main/docs/google-bigquery-component.adoc b/components/camel-google-bigquery/src/main/docs/google-bigquery-component.adoc
index 8d73565..97b6f34 100644
--- a/components/camel-google-bigquery/src/main/docs/google-bigquery-component.adoc
+++ b/components/camel-google-bigquery/src/main/docs/google-bigquery-component.adoc
@@ -61,7 +61,7 @@ Service Account Email and Service Account Key can be found in the GCP JSON crede
== Options
// component options: START
-The Google BigQuery component supports 4 options, which are listed below.
+The Google BigQuery component supports 6 options, which are listed below.
@@ -72,6 +72,8 @@ The Google BigQuery component supports 4 options, which are listed below.
| *datasetId* (producer) | BigQuery Dataset Id | | String
| *connectionFactory* (producer) | ConnectionFactory to obtain connection to Bigquery Service. If non provided the default one will be used | | GoogleBigQueryConnectionFactory
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -125,7 +127,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 8 options, which are listed below.
+The component supports 10 options, which are listed below.
@@ -133,12 +135,14 @@ The component supports 8 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.google-bigquery.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.google-bigquery.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.google-bigquery.connection-factory.credentials-file-location* | | | String
| *camel.component.google-bigquery.connection-factory.service-account* | | | String
| *camel.component.google-bigquery.connection-factory.service-account-key* | | | String
| *camel.component.google-bigquery.connection-factory.service-u-r-l* | | | String
| *camel.component.google-bigquery.dataset-id* | BigQuery Dataset Id | | String
| *camel.component.google-bigquery.enabled* | Whether to enable auto configuration of the google-bigquery component. This is enabled by default. | | Boolean
+| *camel.component.google-bigquery.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proc [...]
| *camel.component.google-bigquery.project-id* | Google Cloud Project Id | | String
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-google-bigquery/src/main/docs/google-bigquery-sql-component.adoc b/components/camel-google-bigquery/src/main/docs/google-bigquery-sql-component.adoc
index c601927..38c9c04 100644
--- a/components/camel-google-bigquery/src/main/docs/google-bigquery-sql-component.adoc
+++ b/components/camel-google-bigquery/src/main/docs/google-bigquery-sql-component.adoc
@@ -78,7 +78,7 @@ You can externalize your SQL queries to files in the classpath or file system as
== Options
// component options: START
-The Google BigQuery Standard SQL component supports 3 options, which are listed below.
+The Google BigQuery Standard SQL component supports 5 options, which are listed below.
@@ -88,6 +88,8 @@ The Google BigQuery Standard SQL component supports 3 options, which are listed
| *projectId* (producer) | Google Cloud Project Id | | String
| *connectionFactory* (producer) | ConnectionFactory to obtain connection to Bigquery Service. If non provided the default one will be used | | GoogleBigQueryConnectionFactory
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -139,7 +141,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 7 options, which are listed below.
+The component supports 9 options, which are listed below.
@@ -147,11 +149,13 @@ The component supports 7 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.google-bigquery-sql.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.google-bigquery-sql.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.google-bigquery-sql.connection-factory.credentials-file-location* | | | String
| *camel.component.google-bigquery-sql.connection-factory.service-account* | | | String
| *camel.component.google-bigquery-sql.connection-factory.service-account-key* | | | String
| *camel.component.google-bigquery-sql.connection-factory.service-u-r-l* | | | String
| *camel.component.google-bigquery-sql.enabled* | Whether to enable auto configuration of the google-bigquery-sql component. This is enabled by default. | | Boolean
+| *camel.component.google-bigquery-sql.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is [...]
| *camel.component.google-bigquery-sql.project-id* | Google Cloud Project Id | | String
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-google-calendar/src/main/docs/google-calendar-component.adoc b/components/camel-google-calendar/src/main/docs/google-calendar-component.adoc
index 877dcb9..67d5e1c 100644
--- a/components/camel-google-calendar/src/main/docs/google-calendar-component.adoc
+++ b/components/camel-google-calendar/src/main/docs/google-calendar-component.adoc
@@ -41,7 +41,7 @@ for this component:
// component options: START
-The Google Calendar component supports 3 options, which are listed below.
+The Google Calendar component supports 5 options, which are listed below.
@@ -51,6 +51,8 @@ The Google Calendar component supports 3 options, which are listed below.
| *configuration* (common) | To use the shared configuration | | GoogleCalendarConfiguration
| *clientFactory* (advanced) | To use the GoogleCalendarClientFactory as factory for creating the client. Will by default use BatchGoogleCalendarClientFactory | | GoogleCalendarClientFactory
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -137,7 +139,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 14 options, which are listed below.
+The component supports 16 options, which are listed below.
@@ -145,6 +147,7 @@ The component supports 14 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.google-calendar.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.google-calendar.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.google-calendar.client-factory* | To use the GoogleCalendarClientFactory as factory for creating the client. Will by default use BatchGoogleCalendarClientFactory. The option is a org.apache.camel.component.google.calendar.GoogleCalendarClientFactory type. | | String
| *camel.component.google-calendar.configuration.access-token* | OAuth 2 access token. This typically expires after an hour so refreshToken is recommended for long term usage. | | String
| *camel.component.google-calendar.configuration.api-name* | What kind of operation to perform | | GoogleCalendarApiName
@@ -158,6 +161,7 @@ The component supports 14 options, which are listed below.
| *camel.component.google-calendar.configuration.scopes* | Specifies the level of permissions you want a calendar application to have to a user account. You can separate multiple scopes by comma. See \https://developers.google.com/google-apps/calendar/auth for more info. | https://www.googleapis.com/auth/calendar | String
| *camel.component.google-calendar.configuration.user* | The email address of the user the application is trying to impersonate in the service account flow | | String
| *camel.component.google-calendar.enabled* | Enable google-calendar component | true | Boolean
+| *camel.component.google-calendar.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proc [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-google-calendar/src/main/docs/google-calendar-stream-component.adoc b/components/camel-google-calendar/src/main/docs/google-calendar-stream-component.adoc
index b65ff0d..0c64a07 100644
--- a/components/camel-google-calendar/src/main/docs/google-calendar-stream-component.adoc
+++ b/components/camel-google-calendar/src/main/docs/google-calendar-stream-component.adoc
@@ -48,7 +48,7 @@ The Google Calendar Component uses the following URI format:
// component options: START
-The Google Calendar Stream component supports 3 options, which are listed below.
+The Google Calendar Stream component supports 5 options, which are listed below.
@@ -58,6 +58,8 @@ The Google Calendar Stream component supports 3 options, which are listed below.
| *configuration* (advanced) | The configuration | | GoogleCalendarStreamConfiguration
| *clientFactory* (advanced) | The client Factory | | GoogleCalendarClientFactory
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -139,7 +141,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 15 options, which are listed below.
+The component supports 17 options, which are listed below.
@@ -147,6 +149,7 @@ The component supports 15 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.google-calendar-stream.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.google-calendar-stream.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.google-calendar-stream.client-factory* | The client Factory. The option is a org.apache.camel.component.google.calendar.GoogleCalendarClientFactory type. | | String
| *camel.component.google-calendar-stream.configuration.access-token* | OAuth 2 access token. This typically expires after an hour so refreshToken is recommended for long term usage. | | String
| *camel.component.google-calendar-stream.configuration.application-name* | Google Calendar application name. Example would be "camel-google-calendar/1.0" | | String
@@ -161,6 +164,7 @@ The component supports 15 options, which are listed below.
| *camel.component.google-calendar-stream.configuration.refresh-token* | OAuth 2 refresh token. Using this, the Google Calendar component can obtain a new accessToken whenever the current one expires - a necessity if the application is long-lived. | | String
| *camel.component.google-calendar-stream.configuration.scopes* | Specifies the level of permissions you want a calendar application to have to a user account. See \https://developers.google.com/calendar/auth for more info. | | List
| *camel.component.google-calendar-stream.enabled* | Whether to enable auto configuration of the google-calendar-stream component. This is enabled by default. | | Boolean
+| *camel.component.google-calendar-stream.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-google-drive/src/main/docs/google-drive-component.adoc b/components/camel-google-drive/src/main/docs/google-drive-component.adoc
index 578e3d1..c88481a 100644
--- a/components/camel-google-drive/src/main/docs/google-drive-component.adoc
+++ b/components/camel-google-drive/src/main/docs/google-drive-component.adoc
@@ -68,7 +68,7 @@ Endpoint prefix can be one of:
// component options: START
-The Google Drive component supports 3 options, which are listed below.
+The Google Drive component supports 5 options, which are listed below.
@@ -78,6 +78,8 @@ The Google Drive component supports 3 options, which are listed below.
| *configuration* (common) | To use the shared configuration | | GoogleDriveConfiguration
| *clientFactory* (advanced) | To use the GoogleCalendarClientFactory as factory for creating the client. Will by default use BatchGoogleDriveClientFactory | | GoogleDriveClientFactory
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -162,7 +164,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 11 options, which are listed below.
+The component supports 13 options, which are listed below.
@@ -170,6 +172,7 @@ The component supports 11 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.google-drive.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.google-drive.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.google-drive.client-factory* | To use the GoogleCalendarClientFactory as factory for creating the client. Will by default use BatchGoogleDriveClientFactory. The option is a org.apache.camel.component.google.drive.GoogleDriveClientFactory type. | | String
| *camel.component.google-drive.configuration.access-token* | OAuth 2 access token. This typically expires after an hour so refreshToken is recommended for long term usage. | | String
| *camel.component.google-drive.configuration.api-name* | What kind of operation to perform | | GoogleDriveApiName
@@ -180,6 +183,7 @@ The component supports 11 options, which are listed below.
| *camel.component.google-drive.configuration.refresh-token* | OAuth 2 refresh token. Using this, the Google Calendar component can obtain a new accessToken whenever the current one expires - a necessity if the application is long-lived. | | String
| *camel.component.google-drive.configuration.scopes* | Specifies the level of permissions you want a drive application to have to a user account. See \https://developers.google.com/drive/web/scopes for more info. | | List
| *camel.component.google-drive.enabled* | Enable google-drive component | true | Boolean
+| *camel.component.google-drive.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is process [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-google-mail/src/main/docs/google-mail-component.adoc b/components/camel-google-mail/src/main/docs/google-mail-component.adoc
index 4634d73..a18223a 100644
--- a/components/camel-google-mail/src/main/docs/google-mail-component.adoc
+++ b/components/camel-google-mail/src/main/docs/google-mail-component.adoc
@@ -60,7 +60,7 @@ Endpoint prefix can be one of:
// component options: START
-The Google Mail component supports 3 options, which are listed below.
+The Google Mail component supports 5 options, which are listed below.
@@ -70,6 +70,8 @@ The Google Mail component supports 3 options, which are listed below.
| *configuration* (common) | To use the shared configuration | | GoogleMailConfiguration
| *clientFactory* (advanced) | To use the GoogleCalendarClientFactory as factory for creating the client. Will by default use BatchGoogleMailClientFactory | | GoogleMailClientFactory
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -151,7 +153,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 10 options, which are listed below.
+The component supports 12 options, which are listed below.
@@ -159,6 +161,7 @@ The component supports 10 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.google-mail.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.google-mail.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.google-mail.client-factory* | To use the GoogleCalendarClientFactory as factory for creating the client. Will by default use BatchGoogleMailClientFactory. The option is a org.apache.camel.component.google.mail.GoogleMailClientFactory type. | | String
| *camel.component.google-mail.configuration.access-token* | OAuth 2 access token. This typically expires after an hour so refreshToken is recommended for long term usage. | | String
| *camel.component.google-mail.configuration.api-name* | What kind of operation to perform | | GoogleMailApiName
@@ -168,6 +171,7 @@ The component supports 10 options, which are listed below.
| *camel.component.google-mail.configuration.method-name* | What sub operation to use for the selected operation | | String
| *camel.component.google-mail.configuration.refresh-token* | OAuth 2 refresh token. Using this, the Google Calendar component can obtain a new accessToken whenever the current one expires - a necessity if the application is long-lived. | | String
| *camel.component.google-mail.enabled* | Enable google-mail component | true | Boolean
+| *camel.component.google-mail.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processe [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-google-mail/src/main/docs/google-mail-stream-component.adoc b/components/camel-google-mail/src/main/docs/google-mail-stream-component.adoc
index c3a393d..7883a15 100644
--- a/components/camel-google-mail/src/main/docs/google-mail-stream-component.adoc
+++ b/components/camel-google-mail/src/main/docs/google-mail-stream-component.adoc
@@ -46,7 +46,7 @@ The GoogleMail Component uses the following URI format:
// component options: START
-The Google Mail Stream component supports 3 options, which are listed below.
+The Google Mail Stream component supports 5 options, which are listed below.
@@ -56,6 +56,8 @@ The Google Mail Stream component supports 3 options, which are listed below.
| *configuration* (advanced) | The configuration | | GoogleMailStreamConfiguration
| *clientFactory* (advanced) | The client Factory | | GoogleMailClientFactory
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -135,7 +137,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 13 options, which are listed below.
+The component supports 15 options, which are listed below.
@@ -143,6 +145,7 @@ The component supports 13 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.google-mail-stream.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.google-mail-stream.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.google-mail-stream.client-factory* | The client Factory. The option is a org.apache.camel.component.google.mail.GoogleMailClientFactory type. | | String
| *camel.component.google-mail-stream.configuration.access-token* | OAuth 2 access token. This typically expires after an hour so refreshToken is recommended for long term usage. | | String
| *camel.component.google-mail-stream.configuration.application-name* | Google mail application name. Example would be "camel-google-mail/1.0" | | String
@@ -155,6 +158,7 @@ The component supports 13 options, which are listed below.
| *camel.component.google-mail-stream.configuration.query* | The query to execute on gmail box | is:unread | String
| *camel.component.google-mail-stream.configuration.refresh-token* | OAuth 2 refresh token. Using this, the Google Calendar component can obtain a new accessToken whenever the current one expires - a necessity if the application is long-lived. | | String
| *camel.component.google-mail-stream.enabled* | Whether to enable auto configuration of the google-mail-stream component. This is enabled by default. | | Boolean
+| *camel.component.google-mail-stream.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is p [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-google-pubsub/src/main/docs/google-pubsub-component.adoc b/components/camel-google-pubsub/src/main/docs/google-pubsub-component.adoc
index 5e462b7..aecb344 100644
--- a/components/camel-google-pubsub/src/main/docs/google-pubsub-component.adoc
+++ b/components/camel-google-pubsub/src/main/docs/google-pubsub-component.adoc
@@ -39,7 +39,7 @@ Destination Name can be either a topic or a subscription name.
== Options
// component options: START
-The Google Pubsub component supports 2 options, which are listed below.
+The Google Pubsub component supports 4 options, which are listed below.
@@ -48,6 +48,8 @@ The Google Pubsub component supports 2 options, which are listed below.
| Name | Description | Default | Type
| *connectionFactory* (common) | Sets the connection factory to use: provides the ability to explicitly manage connection credentials: - the path to the key file - the Service Account Key / Email pair | | GooglePubsubConnectionFactory
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -106,7 +108,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 6 options, which are listed below.
+The component supports 8 options, which are listed below.
@@ -114,11 +116,13 @@ The component supports 6 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.google-pubsub.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.google-pubsub.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.google-pubsub.connection-factory.credentials-file-location* | | | String
| *camel.component.google-pubsub.connection-factory.service-account* | | | String
| *camel.component.google-pubsub.connection-factory.service-account-key* | | | String
| *camel.component.google-pubsub.connection-factory.service-u-r-l* | | | String
| *camel.component.google-pubsub.enabled* | Enable google-pubsub component | true | Boolean
+| *camel.component.google-pubsub.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proces [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-google-sheets/src/main/docs/google-sheets-component.adoc b/components/camel-google-sheets/src/main/docs/google-sheets-component.adoc
index c48a387..94d8438 100644
--- a/components/camel-google-sheets/src/main/docs/google-sheets-component.adoc
+++ b/components/camel-google-sheets/src/main/docs/google-sheets-component.adoc
@@ -56,7 +56,7 @@ Endpoint prefix can be one of:
// component options: START
-The Google Sheets component supports 3 options, which are listed below.
+The Google Sheets component supports 5 options, which are listed below.
@@ -66,6 +66,8 @@ The Google Sheets component supports 3 options, which are listed below.
| *configuration* (common) | To use the shared configuration | | GoogleSheetsConfiguration
| *clientFactory* (advanced) | To use the GoogleSheetsClientFactory as factory for creating the client. Will by default use BatchGoogleSheetsClientFactory | | GoogleSheetsClientFactory
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -147,7 +149,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 10 options, which are listed below.
+The component supports 12 options, which are listed below.
@@ -155,6 +157,7 @@ The component supports 10 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.google-sheets.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.google-sheets.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.google-sheets.client-factory* | To use the GoogleSheetsClientFactory as factory for creating the client. Will by default use BatchGoogleSheetsClientFactory. The option is a org.apache.camel.component.google.sheets.GoogleSheetsClientFactory type. | | String
| *camel.component.google-sheets.configuration.access-token* | OAuth 2 access token. This typically expires after an hour so refreshToken is recommended for long term usage. | | String
| *camel.component.google-sheets.configuration.api-name* | What kind of operation to perform | | GoogleSheetsApiName
@@ -164,6 +167,7 @@ The component supports 10 options, which are listed below.
| *camel.component.google-sheets.configuration.method-name* | What sub operation to use for the selected operation | | String
| *camel.component.google-sheets.configuration.refresh-token* | OAuth 2 refresh token. Using this, the Google Sheets component can obtain a new accessToken whenever the current one expires - a necessity if the application is long-lived. | | String
| *camel.component.google-sheets.enabled* | Whether to enable auto configuration of the google-sheets component. This is enabled by default. | | Boolean
+| *camel.component.google-sheets.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proces [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-google-sheets/src/main/docs/google-sheets-stream-component.adoc b/components/camel-google-sheets/src/main/docs/google-sheets-stream-component.adoc
index 9db7667..f9f49b1 100644
--- a/components/camel-google-sheets/src/main/docs/google-sheets-stream-component.adoc
+++ b/components/camel-google-sheets/src/main/docs/google-sheets-stream-component.adoc
@@ -48,7 +48,7 @@ The Google Sheets Component uses the following URI format:
// component options: START
-The Google Sheets Stream component supports 3 options, which are listed below.
+The Google Sheets Stream component supports 5 options, which are listed below.
@@ -58,6 +58,8 @@ The Google Sheets Stream component supports 3 options, which are listed below.
| *configuration* (consumer) | To use the shared configuration | | GoogleSheetsStreamConfiguration
| *clientFactory* (advanced) | To use the GoogleSheetsClientFactory as factory for creating the client. Will by default use BatchGoogleSheetsClientFactory | | GoogleSheetsClientFactory
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -141,7 +143,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 17 options, which are listed below.
+The component supports 19 options, which are listed below.
@@ -149,6 +151,7 @@ The component supports 17 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.google-sheets-stream.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.google-sheets-stream.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.google-sheets-stream.client-factory* | To use the GoogleSheetsClientFactory as factory for creating the client. Will by default use BatchGoogleSheetsClientFactory. The option is a org.apache.camel.component.google.sheets.GoogleSheetsClientFactory type. | | String
| *camel.component.google-sheets-stream.configuration.access-token* | OAuth 2 access token. This typically expires after an hour so refreshToken is recommended for long term usage. | | String
| *camel.component.google-sheets-stream.configuration.api-name* | Sets the apiName. | | String
@@ -165,6 +168,7 @@ The component supports 17 options, which are listed below.
| *camel.component.google-sheets-stream.configuration.spreadsheet-id* | Specifies the spreadsheet identifier that is used to identify the target to obtain. | | String
| *camel.component.google-sheets-stream.configuration.value-render-option* | Determines how values should be rendered in the output. | FORMATTED_VALUE | String
| *camel.component.google-sheets-stream.enabled* | Whether to enable auto configuration of the google-sheets-stream component. This is enabled by default. | | Boolean
+| *camel.component.google-sheets-stream.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-gora/src/main/docs/gora-component.adoc b/components/camel-gora/src/main/docs/gora-component.adoc
index 8a8a916..8a14840 100644
--- a/components/camel-gora/src/main/docs/gora-component.adoc
+++ b/components/camel-gora/src/main/docs/gora-component.adoc
@@ -80,7 +80,7 @@ http://gora.apache.org/current/gora-conf.html[gora-conf] page.
// component options: START
-The Gora component supports 1 options, which are listed below.
+The Gora component supports 3 options, which are listed below.
@@ -88,6 +88,8 @@ The Gora component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -161,7 +163,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -169,7 +171,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.gora.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.gora.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.gora.enabled* | Enable gora component | true | Boolean
+| *camel.component.gora.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-grape/src/main/docs/grape-component.adoc b/components/camel-grape/src/main/docs/grape-component.adoc
index f7ca5c0..8c86b83 100644
--- a/components/camel-grape/src/main/docs/grape-component.adoc
+++ b/components/camel-grape/src/main/docs/grape-component.adoc
@@ -17,7 +17,7 @@ without the restart of the router.
== Grape options
// component options: START
-The Grape component supports 2 options, which are listed below.
+The Grape component supports 4 options, which are listed below.
@@ -26,6 +26,8 @@ The Grape component supports 2 options, which are listed below.
| Name | Description | Default | Type
| *patchesRepository* (advanced) | Implementation of org.apache.camel.component.grape.PatchesRepository, by default: FilePatchesRepository | | PatchesRepository
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
diff --git a/components/camel-graphql/src/main/docs/graphql-component.adoc b/components/camel-graphql/src/main/docs/graphql-component.adoc
index 7cabec1..eb00de9 100644
--- a/components/camel-graphql/src/main/docs/graphql-component.adoc
+++ b/components/camel-graphql/src/main/docs/graphql-component.adoc
@@ -66,7 +66,7 @@ with the following path and query parameters:
== GraphQL Component Options
// component options: START
-The GraphQL component supports 1 options, which are listed below.
+The GraphQL component supports 3 options, which are listed below.
@@ -74,6 +74,8 @@ The GraphQL component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -93,7 +95,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -101,7 +103,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.graphql.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.graphql.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.graphql.enabled* | Whether to enable auto configuration of the graphql component. This is enabled by default. | | Boolean
+| *camel.component.graphql.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-grpc/src/main/docs/grpc-component.adoc b/components/camel-grpc/src/main/docs/grpc-component.adoc
index 3ebfc7b..fe4cad9 100644
--- a/components/camel-grpc/src/main/docs/grpc-component.adoc
+++ b/components/camel-grpc/src/main/docs/grpc-component.adoc
@@ -44,7 +44,7 @@ grpc://service[?options]
== Endpoint Options
// component options: START
-The gRPC component supports 1 options, which are listed below.
+The gRPC component supports 3 options, which are listed below.
@@ -52,6 +52,8 @@ The gRPC component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -127,7 +129,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -135,7 +137,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.grpc.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.grpc.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.grpc.enabled* | Enable grpc component | true | Boolean
+| *camel.component.grpc.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-guava-eventbus/src/main/docs/guava-eventbus-component.adoc b/components/camel-guava-eventbus/src/main/docs/guava-eventbus-component.adoc
index f37f275..6c339b8 100644
--- a/components/camel-guava-eventbus/src/main/docs/guava-eventbus-component.adoc
+++ b/components/camel-guava-eventbus/src/main/docs/guava-eventbus-component.adoc
@@ -50,7 +50,7 @@ registry.
// component options: START
-The Guava EventBus component supports 3 options, which are listed below.
+The Guava EventBus component supports 5 options, which are listed below.
@@ -60,6 +60,8 @@ The Guava EventBus component supports 3 options, which are listed below.
| *eventBus* (common) | To use the given Guava EventBus instance | | EventBus
| *listenerInterface* (common) | The interface with method(s) marked with the Subscribe annotation. Dynamic proxy will be created over the interface so it could be registered as the EventBus listener. Particularly useful when creating multi-event listeners and for handling DeadEvent properly. This option cannot be used together with eventClass option. | | Class
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -118,7 +120,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 4 options, which are listed below.
+The component supports 6 options, which are listed below.
@@ -126,8 +128,10 @@ The component supports 4 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.guava-eventbus.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.guava-eventbus.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.guava-eventbus.enabled* | Enable guava-eventbus component | true | Boolean
| *camel.component.guava-eventbus.event-bus* | To use the given Guava EventBus instance. The option is a com.google.common.eventbus.EventBus type. | | String
+| *camel.component.guava-eventbus.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proce [...]
| *camel.component.guava-eventbus.listener-interface* | The interface with method(s) marked with the Subscribe annotation. Dynamic proxy will be created over the interface so it could be registered as the EventBus listener. Particularly useful when creating multi-event listeners and for handling DeadEvent properly. This option cannot be used together with eventClass option. | | Class
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-hazelcast/src/main/docs/hazelcast-atomicvalue-component.adoc b/components/camel-hazelcast/src/main/docs/hazelcast-atomicvalue-component.adoc
index 007baa4..dc64e71 100644
--- a/components/camel-hazelcast/src/main/docs/hazelcast-atomicvalue-component.adoc
+++ b/components/camel-hazelcast/src/main/docs/hazelcast-atomicvalue-component.adoc
@@ -16,7 +16,7 @@ An atomic number is an object that simply provides a grid wide number (long).
== Options
// component options: START
-The Hazelcast Atomic Number component supports 3 options, which are listed below.
+The Hazelcast Atomic Number component supports 5 options, which are listed below.
@@ -26,6 +26,8 @@ The Hazelcast Atomic Number component supports 3 options, which are listed below
| *hazelcastInstance* (advanced) | The hazelcast instance reference which can be used for hazelcast endpoint. If you don't specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. | | HazelcastInstance
| *hazelcastMode* (advanced) | The hazelcast mode reference which kind of instance should be used. If you don't specify the mode, then the node mode will be the default. | node | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -78,7 +80,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 6 options, which are listed below.
+The component supports 8 options, which are listed below.
@@ -86,11 +88,13 @@ The component supports 6 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.hazelcast-atomicvalue.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.hazelcast-atomicvalue.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.hazelcast-atomicvalue.customizer.hazelcast-instance.enabled* | Enable or disable the cache-manager customizer. | true | Boolean
| *camel.component.hazelcast-atomicvalue.customizer.hazelcast-instance.override* | Configure if the cache manager eventually set on the component should be overridden by the customizer. | false | Boolean
| *camel.component.hazelcast-atomicvalue.enabled* | Enable hazelcast-atomicvalue component | true | Boolean
| *camel.component.hazelcast-atomicvalue.hazelcast-instance* | The hazelcast instance reference which can be used for hazelcast endpoint. If you don't specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. The option is a com.hazelcast.core.HazelcastInstance type. | | String
| *camel.component.hazelcast-atomicvalue.hazelcast-mode* | The hazelcast mode reference which kind of instance should be used. If you don't specify the mode, then the node mode will be the default. | node | String
+| *camel.component.hazelcast-atomicvalue.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message i [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-hazelcast/src/main/docs/hazelcast-instance-component.adoc b/components/camel-hazelcast/src/main/docs/hazelcast-instance-component.adoc
index dccce33..e2aba66 100644
--- a/components/camel-hazelcast/src/main/docs/hazelcast-instance-component.adoc
+++ b/components/camel-hazelcast/src/main/docs/hazelcast-instance-component.adoc
@@ -16,7 +16,7 @@ Hazelcast makes sense in one single "server node", but it's extremly powerful in
== Options
// component options: START
-The Hazelcast Instance component supports 3 options, which are listed below.
+The Hazelcast Instance component supports 5 options, which are listed below.
@@ -26,6 +26,8 @@ The Hazelcast Instance component supports 3 options, which are listed below.
| *hazelcastInstance* (advanced) | The hazelcast instance reference which can be used for hazelcast endpoint. If you don't specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. | | HazelcastInstance
| *hazelcastMode* (advanced) | The hazelcast mode reference which kind of instance should be used. If you don't specify the mode, then the node mode will be the default. | node | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
// endpoint options: START
@@ -79,7 +81,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 26 options, which are listed below.
+The component supports 28 options, which are listed below.
@@ -89,9 +91,11 @@ The component supports 26 options, which are listed below.
| *camel.component.hazelcast-atomicvalue.customizer.hazelcast-instance.enabled* | Enable or disable the cache-manager customizer. | true | Boolean
| *camel.component.hazelcast-atomicvalue.customizer.hazelcast-instance.override* | Configure if the cache manager eventually set on the component should be overridden by the customizer. | false | Boolean
| *camel.component.hazelcast-instance.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.hazelcast-instance.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.hazelcast-instance.enabled* | Enable hazelcast-instance component | true | Boolean
| *camel.component.hazelcast-instance.hazelcast-instance* | The hazelcast instance reference which can be used for hazelcast endpoint. If you don't specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. The option is a com.hazelcast.core.HazelcastInstance type. | | String
| *camel.component.hazelcast-instance.hazelcast-mode* | The hazelcast mode reference which kind of instance should be used. If you don't specify the mode, then the node mode will be the default. | node | String
+| *camel.component.hazelcast-instance.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is p [...]
| *camel.component.hazelcast-list.customizer.hazelcast-instance.enabled* | Enable or disable the cache-manager customizer. | true | Boolean
| *camel.component.hazelcast-list.customizer.hazelcast-instance.override* | Configure if the cache manager eventually set on the component should be overridden by the customizer. | false | Boolean
| *camel.component.hazelcast-map.customizer.hazelcast-instance.enabled* | Enable or disable the cache-manager customizer. | true | Boolean
diff --git a/components/camel-hazelcast/src/main/docs/hazelcast-list-component.adoc b/components/camel-hazelcast/src/main/docs/hazelcast-list-component.adoc
index cde6995..5ed798a 100644
--- a/components/camel-hazelcast/src/main/docs/hazelcast-list-component.adoc
+++ b/components/camel-hazelcast/src/main/docs/hazelcast-list-component.adoc
@@ -12,7 +12,7 @@ The http://www.hazelcast.com/[Hazelcast] List component is one of Camel Hazelcas
== Options
// component options: START
-The Hazelcast List component supports 3 options, which are listed below.
+The Hazelcast List component supports 5 options, which are listed below.
@@ -22,6 +22,8 @@ The Hazelcast List component supports 3 options, which are listed below.
| *hazelcastInstance* (advanced) | The hazelcast instance reference which can be used for hazelcast endpoint. If you don't specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. | | HazelcastInstance
| *hazelcastMode* (advanced) | The hazelcast mode reference which kind of instance should be used. If you don't specify the mode, then the node mode will be the default. | node | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
// endpoint options: START
@@ -76,7 +78,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 6 options, which are listed below.
+The component supports 8 options, which are listed below.
@@ -84,11 +86,13 @@ The component supports 6 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.hazelcast-list.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.hazelcast-list.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.hazelcast-list.customizer.hazelcast-instance.enabled* | Enable or disable the cache-manager customizer. | true | Boolean
| *camel.component.hazelcast-list.customizer.hazelcast-instance.override* | Configure if the cache manager eventually set on the component should be overridden by the customizer. | false | Boolean
| *camel.component.hazelcast-list.enabled* | Enable hazelcast-list component | true | Boolean
| *camel.component.hazelcast-list.hazelcast-instance* | The hazelcast instance reference which can be used for hazelcast endpoint. If you don't specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. The option is a com.hazelcast.core.HazelcastInstance type. | | String
| *camel.component.hazelcast-list.hazelcast-mode* | The hazelcast mode reference which kind of instance should be used. If you don't specify the mode, then the node mode will be the default. | node | String
+| *camel.component.hazelcast-list.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proce [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-hazelcast/src/main/docs/hazelcast-map-component.adoc b/components/camel-hazelcast/src/main/docs/hazelcast-map-component.adoc
index e1f800a..69bb266 100644
--- a/components/camel-hazelcast/src/main/docs/hazelcast-map-component.adoc
+++ b/components/camel-hazelcast/src/main/docs/hazelcast-map-component.adoc
@@ -13,7 +13,7 @@ The http://www.hazelcast.com/[Hazelcast] Map component is one of Camel Hazelcast
== Options
// component options: START
-The Hazelcast Map component supports 3 options, which are listed below.
+The Hazelcast Map component supports 5 options, which are listed below.
@@ -23,6 +23,8 @@ The Hazelcast Map component supports 3 options, which are listed below.
| *hazelcastInstance* (advanced) | The hazelcast instance reference which can be used for hazelcast endpoint. If you don't specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. | | HazelcastInstance
| *hazelcastMode* (advanced) | The hazelcast mode reference which kind of instance should be used. If you don't specify the mode, then the node mode will be the default. | node | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
// endpoint options: START
@@ -77,7 +79,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 6 options, which are listed below.
+The component supports 8 options, which are listed below.
@@ -85,11 +87,13 @@ The component supports 6 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.hazelcast-map.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.hazelcast-map.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.hazelcast-map.customizer.hazelcast-instance.enabled* | Enable or disable the cache-manager customizer. | true | Boolean
| *camel.component.hazelcast-map.customizer.hazelcast-instance.override* | Configure if the cache manager eventually set on the component should be overridden by the customizer. | false | Boolean
| *camel.component.hazelcast-map.enabled* | Enable hazelcast-map component | true | Boolean
| *camel.component.hazelcast-map.hazelcast-instance* | The hazelcast instance reference which can be used for hazelcast endpoint. If you don't specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. The option is a com.hazelcast.core.HazelcastInstance type. | | String
| *camel.component.hazelcast-map.hazelcast-mode* | The hazelcast mode reference which kind of instance should be used. If you don't specify the mode, then the node mode will be the default. | node | String
+| *camel.component.hazelcast-map.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proces [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-hazelcast/src/main/docs/hazelcast-multimap-component.adoc b/components/camel-hazelcast/src/main/docs/hazelcast-multimap-component.adoc
index 9b94b1e..b767756 100644
--- a/components/camel-hazelcast/src/main/docs/hazelcast-multimap-component.adoc
+++ b/components/camel-hazelcast/src/main/docs/hazelcast-multimap-component.adoc
@@ -13,7 +13,7 @@ The http://www.hazelcast.com/[Hazelcast] Multimap component is one of Camel Haze
== Options
// component options: START
-The Hazelcast Multimap component supports 3 options, which are listed below.
+The Hazelcast Multimap component supports 5 options, which are listed below.
@@ -23,6 +23,8 @@ The Hazelcast Multimap component supports 3 options, which are listed below.
| *hazelcastInstance* (advanced) | The hazelcast instance reference which can be used for hazelcast endpoint. If you don't specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. | | HazelcastInstance
| *hazelcastMode* (advanced) | The hazelcast mode reference which kind of instance should be used. If you don't specify the mode, then the node mode will be the default. | node | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -78,7 +80,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 6 options, which are listed below.
+The component supports 8 options, which are listed below.
@@ -86,11 +88,13 @@ The component supports 6 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.hazelcast-multimap.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.hazelcast-multimap.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.hazelcast-multimap.customizer.hazelcast-instance.enabled* | Enable or disable the cache-manager customizer. | true | Boolean
| *camel.component.hazelcast-multimap.customizer.hazelcast-instance.override* | Configure if the cache manager eventually set on the component should be overridden by the customizer. | false | Boolean
| *camel.component.hazelcast-multimap.enabled* | Enable hazelcast-multimap component | true | Boolean
| *camel.component.hazelcast-multimap.hazelcast-instance* | The hazelcast instance reference which can be used for hazelcast endpoint. If you don't specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. The option is a com.hazelcast.core.HazelcastInstance type. | | String
| *camel.component.hazelcast-multimap.hazelcast-mode* | The hazelcast mode reference which kind of instance should be used. If you don't specify the mode, then the node mode will be the default. | node | String
+| *camel.component.hazelcast-multimap.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is p [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-hazelcast/src/main/docs/hazelcast-queue-component.adoc b/components/camel-hazelcast/src/main/docs/hazelcast-queue-component.adoc
index 20671e2..972b974 100644
--- a/components/camel-hazelcast/src/main/docs/hazelcast-queue-component.adoc
+++ b/components/camel-hazelcast/src/main/docs/hazelcast-queue-component.adoc
@@ -13,7 +13,7 @@ The http://www.hazelcast.com/[Hazelcast] Queue component is one of Camel Hazelca
== Options
// component options: START
-The Hazelcast Queue component supports 3 options, which are listed below.
+The Hazelcast Queue component supports 5 options, which are listed below.
@@ -23,6 +23,8 @@ The Hazelcast Queue component supports 3 options, which are listed below.
| *hazelcastInstance* (advanced) | The hazelcast instance reference which can be used for hazelcast endpoint. If you don't specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. | | HazelcastInstance
| *hazelcastMode* (advanced) | The hazelcast mode reference which kind of instance should be used. If you don't specify the mode, then the node mode will be the default. | node | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
// endpoint options: START
@@ -80,7 +82,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 6 options, which are listed below.
+The component supports 8 options, which are listed below.
@@ -88,11 +90,13 @@ The component supports 6 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.hazelcast-queue.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.hazelcast-queue.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.hazelcast-queue.customizer.hazelcast-instance.enabled* | Enable or disable the cache-manager customizer. | true | Boolean
| *camel.component.hazelcast-queue.customizer.hazelcast-instance.override* | Configure if the cache manager eventually set on the component should be overridden by the customizer. | false | Boolean
| *camel.component.hazelcast-queue.enabled* | Enable hazelcast-queue component | true | Boolean
| *camel.component.hazelcast-queue.hazelcast-instance* | The hazelcast instance reference which can be used for hazelcast endpoint. If you don't specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. The option is a com.hazelcast.core.HazelcastInstance type. | | String
| *camel.component.hazelcast-queue.hazelcast-mode* | The hazelcast mode reference which kind of instance should be used. If you don't specify the mode, then the node mode will be the default. | node | String
+| *camel.component.hazelcast-queue.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proc [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-hazelcast/src/main/docs/hazelcast-replicatedmap-component.adoc b/components/camel-hazelcast/src/main/docs/hazelcast-replicatedmap-component.adoc
index e882a94..e5d695d 100644
--- a/components/camel-hazelcast/src/main/docs/hazelcast-replicatedmap-component.adoc
+++ b/components/camel-hazelcast/src/main/docs/hazelcast-replicatedmap-component.adoc
@@ -14,7 +14,7 @@ A replicated map is a weakly consistent, distributed key-value data structure wi
== Options
// component options: START
-The Hazelcast Replicated Map component supports 3 options, which are listed below.
+The Hazelcast Replicated Map component supports 5 options, which are listed below.
@@ -24,6 +24,8 @@ The Hazelcast Replicated Map component supports 3 options, which are listed belo
| *hazelcastInstance* (advanced) | The hazelcast instance reference which can be used for hazelcast endpoint. If you don't specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. | | HazelcastInstance
| *hazelcastMode* (advanced) | The hazelcast mode reference which kind of instance should be used. If you don't specify the mode, then the node mode will be the default. | node | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
// endpoint options: START
@@ -78,7 +80,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 6 options, which are listed below.
+The component supports 8 options, which are listed below.
@@ -86,11 +88,13 @@ The component supports 6 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.hazelcast-replicatedmap.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.hazelcast-replicatedmap.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.hazelcast-replicatedmap.customizer.hazelcast-instance.enabled* | Enable or disable the cache-manager customizer. | true | Boolean
| *camel.component.hazelcast-replicatedmap.customizer.hazelcast-instance.override* | Configure if the cache manager eventually set on the component should be overridden by the customizer. | false | Boolean
| *camel.component.hazelcast-replicatedmap.enabled* | Enable hazelcast-replicatedmap component | true | Boolean
| *camel.component.hazelcast-replicatedmap.hazelcast-instance* | The hazelcast instance reference which can be used for hazelcast endpoint. If you don't specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. The option is a com.hazelcast.core.HazelcastInstance type. | | String
| *camel.component.hazelcast-replicatedmap.hazelcast-mode* | The hazelcast mode reference which kind of instance should be used. If you don't specify the mode, then the node mode will be the default. | node | String
+| *camel.component.hazelcast-replicatedmap.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-hazelcast/src/main/docs/hazelcast-ringbuffer-component.adoc b/components/camel-hazelcast/src/main/docs/hazelcast-ringbuffer-component.adoc
index a80fd5e..0ec9de7 100644
--- a/components/camel-hazelcast/src/main/docs/hazelcast-ringbuffer-component.adoc
+++ b/components/camel-hazelcast/src/main/docs/hazelcast-ringbuffer-component.adoc
@@ -13,7 +13,7 @@ Ringbuffer is a distributed data structure where the data is stored in a ring-li
== Options
// component options: START
-The Hazelcast Ringbuffer component supports 3 options, which are listed below.
+The Hazelcast Ringbuffer component supports 5 options, which are listed below.
@@ -23,6 +23,8 @@ The Hazelcast Ringbuffer component supports 3 options, which are listed below.
| *hazelcastInstance* (advanced) | The hazelcast instance reference which can be used for hazelcast endpoint. If you don't specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. | | HazelcastInstance
| *hazelcastMode* (advanced) | The hazelcast mode reference which kind of instance should be used. If you don't specify the mode, then the node mode will be the default. | node | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -75,7 +77,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 6 options, which are listed below.
+The component supports 8 options, which are listed below.
@@ -83,11 +85,13 @@ The component supports 6 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.hazelcast-ringbuffer.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.hazelcast-ringbuffer.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.hazelcast-ringbuffer.customizer.hazelcast-instance.enabled* | Enable or disable the cache-manager customizer. | true | Boolean
| *camel.component.hazelcast-ringbuffer.customizer.hazelcast-instance.override* | Configure if the cache manager eventually set on the component should be overridden by the customizer. | false | Boolean
| *camel.component.hazelcast-ringbuffer.enabled* | Enable hazelcast-ringbuffer component | true | Boolean
| *camel.component.hazelcast-ringbuffer.hazelcast-instance* | The hazelcast instance reference which can be used for hazelcast endpoint. If you don't specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. The option is a com.hazelcast.core.HazelcastInstance type. | | String
| *camel.component.hazelcast-ringbuffer.hazelcast-mode* | The hazelcast mode reference which kind of instance should be used. If you don't specify the mode, then the node mode will be the default. | node | String
+| *camel.component.hazelcast-ringbuffer.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-hazelcast/src/main/docs/hazelcast-seda-component.adoc b/components/camel-hazelcast/src/main/docs/hazelcast-seda-component.adoc
index 9398267..41430de 100644
--- a/components/camel-hazelcast/src/main/docs/hazelcast-seda-component.adoc
+++ b/components/camel-hazelcast/src/main/docs/hazelcast-seda-component.adoc
@@ -14,7 +14,7 @@ SEDA component differs from the rest components provided. It implements a work-q
== Options
// component options: START
-The Hazelcast SEDA component supports 3 options, which are listed below.
+The Hazelcast SEDA component supports 5 options, which are listed below.
@@ -24,6 +24,8 @@ The Hazelcast SEDA component supports 3 options, which are listed below.
| *hazelcastInstance* (advanced) | The hazelcast instance reference which can be used for hazelcast endpoint. If you don't specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. | | HazelcastInstance
| *hazelcastMode* (advanced) | The hazelcast mode reference which kind of instance should be used. If you don't specify the mode, then the node mode will be the default. | node | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
// endpoint options: START
@@ -83,7 +85,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 6 options, which are listed below.
+The component supports 8 options, which are listed below.
@@ -91,11 +93,13 @@ The component supports 6 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.hazelcast-seda.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.hazelcast-seda.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.hazelcast-seda.customizer.hazelcast-instance.enabled* | Enable or disable the cache-manager customizer. | true | Boolean
| *camel.component.hazelcast-seda.customizer.hazelcast-instance.override* | Configure if the cache manager eventually set on the component should be overridden by the customizer. | false | Boolean
| *camel.component.hazelcast-seda.enabled* | Enable hazelcast-seda component | true | Boolean
| *camel.component.hazelcast-seda.hazelcast-instance* | The hazelcast instance reference which can be used for hazelcast endpoint. If you don't specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. The option is a com.hazelcast.core.HazelcastInstance type. | | String
| *camel.component.hazelcast-seda.hazelcast-mode* | The hazelcast mode reference which kind of instance should be used. If you don't specify the mode, then the node mode will be the default. | node | String
+| *camel.component.hazelcast-seda.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proce [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-hazelcast/src/main/docs/hazelcast-set-component.adoc b/components/camel-hazelcast/src/main/docs/hazelcast-set-component.adoc
index d5bc970..fbaddbf 100644
--- a/components/camel-hazelcast/src/main/docs/hazelcast-set-component.adoc
+++ b/components/camel-hazelcast/src/main/docs/hazelcast-set-component.adoc
@@ -13,7 +13,7 @@ The http://www.hazelcast.com/[Hazelcast] Set component is one of Camel Hazelcast
== Options
// component options: START
-The Hazelcast Set component supports 3 options, which are listed below.
+The Hazelcast Set component supports 5 options, which are listed below.
@@ -23,6 +23,8 @@ The Hazelcast Set component supports 3 options, which are listed below.
| *hazelcastInstance* (advanced) | The hazelcast instance reference which can be used for hazelcast endpoint. If you don't specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. | | HazelcastInstance
| *hazelcastMode* (advanced) | The hazelcast mode reference which kind of instance should be used. If you don't specify the mode, then the node mode will be the default. | node | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
// endpoint options: START
@@ -77,7 +79,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 6 options, which are listed below.
+The component supports 8 options, which are listed below.
@@ -85,11 +87,13 @@ The component supports 6 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.hazelcast-set.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.hazelcast-set.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.hazelcast-set.customizer.hazelcast-instance.enabled* | Enable or disable the cache-manager customizer. | true | Boolean
| *camel.component.hazelcast-set.customizer.hazelcast-instance.override* | Configure if the cache manager eventually set on the component should be overridden by the customizer. | false | Boolean
| *camel.component.hazelcast-set.enabled* | Enable hazelcast-set component | true | Boolean
| *camel.component.hazelcast-set.hazelcast-instance* | The hazelcast instance reference which can be used for hazelcast endpoint. If you don't specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. The option is a com.hazelcast.core.HazelcastInstance type. | | String
| *camel.component.hazelcast-set.hazelcast-mode* | The hazelcast mode reference which kind of instance should be used. If you don't specify the mode, then the node mode will be the default. | node | String
+| *camel.component.hazelcast-set.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proces [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-hazelcast/src/main/docs/hazelcast-topic-component.adoc b/components/camel-hazelcast/src/main/docs/hazelcast-topic-component.adoc
index 116646d..7e5203e 100644
--- a/components/camel-hazelcast/src/main/docs/hazelcast-topic-component.adoc
+++ b/components/camel-hazelcast/src/main/docs/hazelcast-topic-component.adoc
@@ -13,7 +13,7 @@ The http://www.hazelcast.com/[Hazelcast] Topic component is one of Camel Hazelca
== Options
// component options: START
-The Hazelcast Topic component supports 3 options, which are listed below.
+The Hazelcast Topic component supports 5 options, which are listed below.
@@ -23,6 +23,8 @@ The Hazelcast Topic component supports 3 options, which are listed below.
| *hazelcastInstance* (advanced) | The hazelcast instance reference which can be used for hazelcast endpoint. If you don't specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. | | HazelcastInstance
| *hazelcastMode* (advanced) | The hazelcast mode reference which kind of instance should be used. If you don't specify the mode, then the node mode will be the default. | node | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
// endpoint options: START
@@ -78,7 +80,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 8 options, which are listed below.
+The component supports 10 options, which are listed below.
@@ -86,6 +88,7 @@ The component supports 8 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.hazelcast-topic.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.hazelcast-topic.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.hazelcast-topic.customizer.hazelcast-instance.enabled* | Enable or disable the cache-manager customizer. | true | Boolean
| *camel.component.hazelcast-topic.customizer.hazelcast-instance.enabled* | Enable or disable the cache-manager customizer. | true | Boolean
| *camel.component.hazelcast-topic.customizer.hazelcast-instance.override* | Configure if the cache manager eventually set on the component should be overridden by the customizer. | false | Boolean
@@ -93,6 +96,7 @@ The component supports 8 options, which are listed below.
| *camel.component.hazelcast-topic.enabled* | Enable hazelcast-topic component | true | Boolean
| *camel.component.hazelcast-topic.hazelcast-instance* | The hazelcast instance reference which can be used for hazelcast endpoint. If you don't specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. The option is a com.hazelcast.core.HazelcastInstance type. | | String
| *camel.component.hazelcast-topic.hazelcast-mode* | The hazelcast mode reference which kind of instance should be used. If you don't specify the mode, then the node mode will be the default. | node | String
+| *camel.component.hazelcast-topic.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proc [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-hbase/src/main/docs/hbase-component.adoc b/components/camel-hbase/src/main/docs/hbase-component.adoc
index 53c4741..dde5956 100644
--- a/components/camel-hbase/src/main/docs/hbase-component.adoc
+++ b/components/camel-hbase/src/main/docs/hbase-component.adoc
@@ -106,7 +106,7 @@ The supported operations are:
// component options: START
-The HBase component supports 3 options, which are listed below.
+The HBase component supports 5 options, which are listed below.
@@ -116,6 +116,8 @@ The HBase component supports 3 options, which are listed below.
| *configuration* (advanced) | To use the shared configuration | | Configuration
| *poolMaxSize* (common) | Maximum number of references to keep for each table in the HTable pool. The default value is 10. | 10 | int
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -185,7 +187,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 4 options, which are listed below.
+The component supports 6 options, which are listed below.
@@ -193,8 +195,10 @@ The component supports 4 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.hbase.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.hbase.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.hbase.configuration* | To use the shared configuration. The option is a org.apache.hadoop.conf.Configuration type. | | String
| *camel.component.hbase.enabled* | Enable hbase component | true | Boolean
+| *camel.component.hbase.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
| *camel.component.hbase.pool-max-size* | Maximum number of references to keep for each table in the HTable pool. The default value is 10. | 10 | Integer
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-hdfs/src/main/docs/hdfs-component.adoc b/components/camel-hdfs/src/main/docs/hdfs-component.adoc
index 60eea93..cf41043 100644
--- a/components/camel-hdfs/src/main/docs/hdfs-component.adoc
+++ b/components/camel-hdfs/src/main/docs/hdfs-component.adoc
@@ -58,7 +58,7 @@ fileMode=Append to append each of the chunks together.
// component options: START
-The HDFS component supports 3 options, which are listed below.
+The HDFS component supports 5 options, which are listed below.
@@ -68,6 +68,8 @@ The HDFS component supports 3 options, which are listed below.
| *jAASConfiguration* (common) | To use the given configuration for security with JAAS. | | Configuration
| *kerberosConfigFile* (common) | To use kerberos authentication, set the value of the 'java.security.krb5.conf' environment variable to an existing file. If the environment variable is already set, warn if different than the specified parameter | | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -167,7 +169,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 4 options, which are listed below.
+The component supports 6 options, which are listed below.
@@ -175,9 +177,11 @@ The component supports 4 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.hdfs.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.hdfs.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.hdfs.enabled* | Whether to enable auto configuration of the hdfs component. This is enabled by default. | | Boolean
| *camel.component.hdfs.j-a-a-s-configuration* | To use the given configuration for security with JAAS. The option is a javax.security.auth.login.Configuration type. | | String
| *camel.component.hdfs.kerberos-config-file* | To use kerberos authentication, set the value of the 'java.security.krb5.conf' environment variable to an existing file. If the environment variable is already set, warn if different than the specified parameter | | String
+| *camel.component.hdfs.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-hipchat/src/main/docs/hipchat-component.adoc b/components/camel-hipchat/src/main/docs/hipchat-component.adoc
index 8ff3247..d79d707 100644
--- a/components/camel-hipchat/src/main/docs/hipchat-component.adoc
+++ b/components/camel-hipchat/src/main/docs/hipchat-component.adoc
@@ -31,7 +31,7 @@ You can append query options to the URI in the following format,
// component options: START
-The Hipchat component supports 1 options, which are listed below.
+The Hipchat component supports 3 options, which are listed below.
@@ -39,6 +39,8 @@ The Hipchat component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -117,7 +119,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -125,7 +127,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.hipchat.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.hipchat.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.hipchat.enabled* | Enable hipchat component | true | Boolean
+| *camel.component.hipchat.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-http/src/main/docs/http-component.adoc b/components/camel-http/src/main/docs/http-component.adoc
index 7c9c9ec..4a7c51d 100644
--- a/components/camel-http/src/main/docs/http-component.adoc
+++ b/components/camel-http/src/main/docs/http-component.adoc
@@ -49,7 +49,7 @@ route, use the xref:jetty-component.adoc[Jetty Component] instead.
// component options: START
-The HTTP component supports 18 options, which are listed below.
+The HTTP component supports 20 options, which are listed below.
@@ -74,6 +74,8 @@ The HTTP component supports 18 options, which are listed below.
| *allowJavaSerialized Object* (advanced) | Whether to allow java serialization when a request uses context-type=application/x-java-serialized-object. This is by default turned off. If you enable this then be aware that Java will deserialize the incoming data from the request to Java and that can be a potential security risk. | false | boolean
| *headerFilterStrategy* (filter) | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. | | HeaderFilterStrategy
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -180,7 +182,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 19 options, which are listed below.
+The component supports 21 options, which are listed below.
@@ -189,6 +191,7 @@ The component supports 19 options, which are listed below.
| Name | Description | Default | Type
| *camel.component.http.allow-java-serialized-object* | Whether to allow java serialization when a request uses context-type=application/x-java-serialized-object. This is by default turned off. If you enable this then be aware that Java will deserialize the incoming data from the request to Java and that can be a potential security risk. | false | Boolean
| *camel.component.http.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.http.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.http.client-connection-manager* | To use a custom and shared HttpClientConnectionManager to manage connections. If this has been configured then this is always used for all endpoints created by this component. The option is a org.apache.http.conn.HttpClientConnectionManager type. | | String
| *camel.component.http.connect-timeout* | Determines the timeout in milliseconds until a connection is established. A timeout value of zero is interpreted as an infinite timeout. A timeout value of zero is interpreted as an infinite timeout. A negative value is interpreted as undefined (system default). Default: -1 | -1 | Integer
| *camel.component.http.connection-request-timeout* | The timeout in milliseconds used when requesting a connection from the connection manager. A timeout value of zero is interpreted as an infinite timeout. A timeout value of zero is interpreted as an infinite timeout. A negative value is interpreted as undefined (system default). Default: -1 | -1 | Integer
@@ -201,6 +204,7 @@ The component supports 19 options, which are listed below.
| *camel.component.http.http-client-configurer* | To use the custom HttpClientConfigurer to perform configuration of the HttpClient that will be used. The option is a org.apache.camel.component.http.HttpClientConfigurer type. | | String
| *camel.component.http.http-configuration* | To use the shared HttpConfiguration as base configuration. The option is a org.apache.camel.http.common.HttpConfiguration type. | | String
| *camel.component.http.http-context* | To use a custom org.apache.http.protocol.HttpContext when executing requests. The option is a org.apache.http.protocol.HttpContext type. | | String
+| *camel.component.http.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
| *camel.component.http.max-total-connections* | The maximum number of connections. | 200 | Integer
| *camel.component.http.socket-timeout* | Defines the socket timeout (SO_TIMEOUT) in milliseconds, which is the timeout for waiting for data or, put differently, a maximum period inactivity between two consecutive data packets). A timeout value of zero is interpreted as an infinite timeout. A negative value is interpreted as undefined (system default). Default: -1 | -1 | Integer
| *camel.component.http.ssl-context-parameters* | To configure security using SSLContextParameters. Important: Only one instance of org.apache.camel.support.jsse.SSLContextParameters is supported per HttpComponent. If you need to use 2 or more different instances, you need to define a new HttpComponent per instance you need. The option is a org.apache.camel.support.jsse.SSLContextParameters type. | | String
diff --git a/components/camel-iec60870/src/main/docs/iec60870-client-component.adoc b/components/camel-iec60870/src/main/docs/iec60870-client-component.adoc
index 962058b..04af90b 100644
--- a/components/camel-iec60870/src/main/docs/iec60870-client-component.adoc
+++ b/components/camel-iec60870/src/main/docs/iec60870-client-component.adoc
@@ -24,7 +24,7 @@ for this component:
----
// component options: START
-The IEC 60870 Client component supports 2 options, which are listed below.
+The IEC 60870 Client component supports 4 options, which are listed below.
@@ -33,6 +33,8 @@ The IEC 60870 Client component supports 2 options, which are listed below.
| Name | Description | Default | Type
| *defaultConnection Options* (common) | Default connection options | | ClientOptions
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -120,7 +122,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 5 options, which are listed below.
+The component supports 7 options, which are listed below.
@@ -128,10 +130,12 @@ The component supports 5 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.iec60870-client.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.iec60870-client.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.iec60870-client.default-connection-options.cause-source-address* | Whether to include the source address | | Byte
| *camel.component.iec60870-client.default-connection-options.data-module-options* | Whether to include the source address | | DataModuleOptions
| *camel.component.iec60870-client.default-connection-options.ignore-background-scan* | Whether to include the source address | true | Boolean
| *camel.component.iec60870-client.enabled* | Whether to enable auto configuration of the iec60870-client component. This is enabled by default. | | Boolean
+| *camel.component.iec60870-client.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proc [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-iec60870/src/main/docs/iec60870-server-component.adoc b/components/camel-iec60870/src/main/docs/iec60870-server-component.adoc
index ef2883a..63f915e 100644
--- a/components/camel-iec60870/src/main/docs/iec60870-server-component.adoc
+++ b/components/camel-iec60870/src/main/docs/iec60870-server-component.adoc
@@ -25,7 +25,7 @@ for this component:
// component options: START
-The IEC 60870 Server component supports 2 options, which are listed below.
+The IEC 60870 Server component supports 4 options, which are listed below.
@@ -34,6 +34,8 @@ The IEC 60870 Server component supports 2 options, which are listed below.
| Name | Description | Default | Type
| *defaultConnection Options* (common) | Default connection options | | ServerOptions
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -124,7 +126,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 8 options, which are listed below.
+The component supports 10 options, which are listed below.
@@ -132,6 +134,7 @@ The component supports 8 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.iec60870-server.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.iec60870-server.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.iec60870-server.default-connection-options.background-scan-period* | The period in "ms" between background transmission cycles. <p> If this is set to zero or less, background transmissions will be disabled. </p> | | Integer
| *camel.component.iec60870-server.default-connection-options.booleans-with-timestamp* | The period in "ms" between background transmission cycles. <p> If this is set to zero or less, background transmissions will be disabled. </p> | | Boolean
| *camel.component.iec60870-server.default-connection-options.buffering-period* | The period in "ms" between background transmission cycles. <p> If this is set to zero or less, background transmissions will be disabled. </p> | | Integer
@@ -139,6 +142,7 @@ The component supports 8 options, which are listed below.
| *camel.component.iec60870-server.default-connection-options.floats-with-timestamp* | The period in "ms" between background transmission cycles. <p> If this is set to zero or less, background transmissions will be disabled. </p> | | Boolean
| *camel.component.iec60870-server.default-connection-options.spontaneous-duplicates* | The period in "ms" between background transmission cycles. <p> If this is set to zero or less, background transmissions will be disabled. </p> | | Integer
| *camel.component.iec60870-server.enabled* | Whether to enable auto configuration of the iec60870-server component. This is enabled by default. | | Boolean
+| *camel.component.iec60870-server.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proc [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-ignite/src/main/docs/ignite-cache-component.adoc b/components/camel-ignite/src/main/docs/ignite-cache-component.adoc
index 7c6f04d..7eabb26 100644
--- a/components/camel-ignite/src/main/docs/ignite-cache-component.adoc
+++ b/components/camel-ignite/src/main/docs/ignite-cache-component.adoc
@@ -17,7 +17,7 @@ Even if you configure a fixed operation in the endpoint URI, you can vary it per
== Options
// component options: START
-The Ignite Cache component supports 4 options, which are listed below.
+The Ignite Cache component supports 6 options, which are listed below.
@@ -28,6 +28,8 @@ The Ignite Cache component supports 4 options, which are listed below.
| *configurationResource* (common) | Sets the resource from where to load the configuration. It can be a: URI, String (URI) or an InputStream. | | Object
| *igniteConfiguration* (common) | Allows the user to set a programmatic IgniteConfiguration. | | IgniteConfiguration
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -92,7 +94,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 5 options, which are listed below.
+The component supports 7 options, which are listed below.
@@ -100,10 +102,12 @@ The component supports 5 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.ignite-cache.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.ignite-cache.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.ignite-cache.configuration-resource* | Sets the resource from where to load the configuration. It can be a: URI, String (URI) or an InputStream. The option is a java.lang.Object type. | | String
| *camel.component.ignite-cache.enabled* | Enable ignite-cache component | true | Boolean
| *camel.component.ignite-cache.ignite* | Sets the Ignite instance. The option is a org.apache.ignite.Ignite type. | | String
| *camel.component.ignite-cache.ignite-configuration* | Allows the user to set a programmatic IgniteConfiguration. The option is a org.apache.ignite.configuration.IgniteConfiguration type. | | String
+| *camel.component.ignite-cache.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is process [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-ignite/src/main/docs/ignite-compute-component.adoc b/components/camel-ignite/src/main/docs/ignite-compute-component.adoc
index b3f6ce7..ebc56af 100644
--- a/components/camel-ignite/src/main/docs/ignite-compute-component.adoc
+++ b/components/camel-ignite/src/main/docs/ignite-compute-component.adoc
@@ -18,7 +18,7 @@ The endpoint tries to run the object passed in the body of the IN message as the
== Options
// component options: START
-The Ignite Compute component supports 4 options, which are listed below.
+The Ignite Compute component supports 6 options, which are listed below.
@@ -29,6 +29,8 @@ The Ignite Compute component supports 4 options, which are listed below.
| *configurationResource* (producer) | Sets the resource from where to load the configuration. It can be a: URI, String (URI) or an InputStream. | | Object
| *igniteConfiguration* (producer) | Allows the user to set a programmatic IgniteConfiguration. | | IgniteConfiguration
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -85,7 +87,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 5 options, which are listed below.
+The component supports 7 options, which are listed below.
@@ -93,10 +95,12 @@ The component supports 5 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.ignite-compute.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.ignite-compute.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.ignite-compute.configuration-resource* | Sets the resource from where to load the configuration. It can be a: URI, String (URI) or an InputStream. The option is a java.lang.Object type. | | String
| *camel.component.ignite-compute.enabled* | Enable ignite-compute component | true | Boolean
| *camel.component.ignite-compute.ignite* | Sets the Ignite instance. The option is a org.apache.ignite.Ignite type. | | String
| *camel.component.ignite-compute.ignite-configuration* | Allows the user to set a programmatic IgniteConfiguration. The option is a org.apache.ignite.configuration.IgniteConfiguration type. | | String
+| *camel.component.ignite-compute.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proce [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-ignite/src/main/docs/ignite-events-component.adoc b/components/camel-ignite/src/main/docs/ignite-events-component.adoc
index 89ca123..1e20341 100644
--- a/components/camel-ignite/src/main/docs/ignite-events-component.adoc
+++ b/components/camel-ignite/src/main/docs/ignite-events-component.adoc
@@ -15,7 +15,7 @@ The Exchanges created by this consumer put the received Event object into the bo
== Options
// component options: START
-The Ignite Events component supports 4 options, which are listed below.
+The Ignite Events component supports 6 options, which are listed below.
@@ -26,6 +26,8 @@ The Ignite Events component supports 4 options, which are listed below.
| *configurationResource* (consumer) | Sets the resource from where to load the configuration. It can be a: URI, String (URI) or an InputStream. | | Object
| *igniteConfiguration* (consumer) | Allows the user to set a programmatic IgniteConfiguration. | | IgniteConfiguration
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -81,7 +83,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 5 options, which are listed below.
+The component supports 7 options, which are listed below.
@@ -89,10 +91,12 @@ The component supports 5 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.ignite-events.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.ignite-events.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.ignite-events.configuration-resource* | Sets the resource from where to load the configuration. It can be a: URI, String (URI) or an InputStream. The option is a java.lang.Object type. | | String
| *camel.component.ignite-events.enabled* | Enable ignite-events component | true | Boolean
| *camel.component.ignite-events.ignite* | Sets the Ignite instance. The option is a org.apache.ignite.Ignite type. | | String
| *camel.component.ignite-events.ignite-configuration* | Allows the user to set a programmatic IgniteConfiguration. The option is a org.apache.ignite.configuration.IgniteConfiguration type. | | String
+| *camel.component.ignite-events.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proces [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-ignite/src/main/docs/ignite-idgen-component.adoc b/components/camel-ignite/src/main/docs/ignite-idgen-component.adoc
index 722b68e..b540419 100644
--- a/components/camel-ignite/src/main/docs/ignite-idgen-component.adoc
+++ b/components/camel-ignite/src/main/docs/ignite-idgen-component.adoc
@@ -14,7 +14,7 @@ This endpoint only supports producers.
== Options
// component options: START
-The Ignite ID Generator component supports 4 options, which are listed below.
+The Ignite ID Generator component supports 6 options, which are listed below.
@@ -25,6 +25,8 @@ The Ignite ID Generator component supports 4 options, which are listed below.
| *configurationResource* (producer) | Sets the resource from where to load the configuration. It can be a: URI, String (URI) or an InputStream. | | Object
| *igniteConfiguration* (producer) | Allows the user to set a programmatic IgniteConfiguration. | | IgniteConfiguration
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -79,7 +81,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 5 options, which are listed below.
+The component supports 7 options, which are listed below.
@@ -87,10 +89,12 @@ The component supports 5 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.ignite-idgen.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.ignite-idgen.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.ignite-idgen.configuration-resource* | Sets the resource from where to load the configuration. It can be a: URI, String (URI) or an InputStream. The option is a java.lang.Object type. | | String
| *camel.component.ignite-idgen.enabled* | Enable ignite-idgen component | true | Boolean
| *camel.component.ignite-idgen.ignite* | Sets the Ignite instance. The option is a org.apache.ignite.Ignite type. | | String
| *camel.component.ignite-idgen.ignite-configuration* | Allows the user to set a programmatic IgniteConfiguration. The option is a org.apache.ignite.configuration.IgniteConfiguration type. | | String
+| *camel.component.ignite-idgen.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is process [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-ignite/src/main/docs/ignite-messaging-component.adoc b/components/camel-ignite/src/main/docs/ignite-messaging-component.adoc
index cb69e39..74a1477 100644
--- a/components/camel-ignite/src/main/docs/ignite-messaging-component.adoc
+++ b/components/camel-ignite/src/main/docs/ignite-messaging-component.adoc
@@ -14,7 +14,7 @@ This endpoint supports producers (to send messages) and consumers (to receive me
== Options
// component options: START
-The Ignite Messaging component supports 4 options, which are listed below.
+The Ignite Messaging component supports 6 options, which are listed below.
@@ -25,6 +25,8 @@ The Ignite Messaging component supports 4 options, which are listed below.
| *configurationResource* (common) | Sets the resource from where to load the configuration. It can be a: URI, String (URI) or an InputStream. | | Object
| *igniteConfiguration* (common) | Allows the user to set a programmatic IgniteConfiguration. | | IgniteConfiguration
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -82,7 +84,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 5 options, which are listed below.
+The component supports 7 options, which are listed below.
@@ -90,10 +92,12 @@ The component supports 5 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.ignite-messaging.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.ignite-messaging.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.ignite-messaging.configuration-resource* | Sets the resource from where to load the configuration. It can be a: URI, String (URI) or an InputStream. The option is a java.lang.Object type. | | String
| *camel.component.ignite-messaging.enabled* | Enable ignite-messaging component | true | Boolean
| *camel.component.ignite-messaging.ignite* | Sets the Ignite instance. The option is a org.apache.ignite.Ignite type. | | String
| *camel.component.ignite-messaging.ignite-configuration* | Allows the user to set a programmatic IgniteConfiguration. The option is a org.apache.ignite.configuration.IgniteConfiguration type. | | String
+| *camel.component.ignite-messaging.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is pro [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-ignite/src/main/docs/ignite-queue-component.adoc b/components/camel-ignite/src/main/docs/ignite-queue-component.adoc
index 76356da..83cb819 100644
--- a/components/camel-ignite/src/main/docs/ignite-queue-component.adoc
+++ b/components/camel-ignite/src/main/docs/ignite-queue-component.adoc
@@ -14,7 +14,7 @@ This endpoint only supports producers.
== Options
// component options: START
-The Ignite Queues component supports 4 options, which are listed below.
+The Ignite Queues component supports 6 options, which are listed below.
@@ -25,6 +25,8 @@ The Ignite Queues component supports 4 options, which are listed below.
| *configurationResource* (producer) | Sets the resource from where to load the configuration. It can be a: URI, String (URI) or an InputStream. | | Object
| *igniteConfiguration* (producer) | Allows the user to set a programmatic IgniteConfiguration. | | IgniteConfiguration
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -80,7 +82,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 5 options, which are listed below.
+The component supports 7 options, which are listed below.
@@ -88,10 +90,12 @@ The component supports 5 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.ignite-queue.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.ignite-queue.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.ignite-queue.configuration-resource* | Sets the resource from where to load the configuration. It can be a: URI, String (URI) or an InputStream. The option is a java.lang.Object type. | | String
| *camel.component.ignite-queue.enabled* | Enable ignite-queue component | true | Boolean
| *camel.component.ignite-queue.ignite* | Sets the Ignite instance. The option is a org.apache.ignite.Ignite type. | | String
| *camel.component.ignite-queue.ignite-configuration* | Allows the user to set a programmatic IgniteConfiguration. The option is a org.apache.ignite.configuration.IgniteConfiguration type. | | String
+| *camel.component.ignite-queue.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is process [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-ignite/src/main/docs/ignite-set-component.adoc b/components/camel-ignite/src/main/docs/ignite-set-component.adoc
index 1819a33..a07f929 100644
--- a/components/camel-ignite/src/main/docs/ignite-set-component.adoc
+++ b/components/camel-ignite/src/main/docs/ignite-set-component.adoc
@@ -14,7 +14,7 @@ This endpoint only supports producers.
== Options
// component options: START
-The Ignite Sets component supports 4 options, which are listed below.
+The Ignite Sets component supports 6 options, which are listed below.
@@ -25,6 +25,8 @@ The Ignite Sets component supports 4 options, which are listed below.
| *configurationResource* (producer) | Sets the resource from where to load the configuration. It can be a: URI, String (URI) or an InputStream. | | Object
| *igniteConfiguration* (producer) | Allows the user to set a programmatic IgniteConfiguration. | | IgniteConfiguration
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -78,7 +80,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 5 options, which are listed below.
+The component supports 7 options, which are listed below.
@@ -86,10 +88,12 @@ The component supports 5 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.ignite-set.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.ignite-set.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.ignite-set.configuration-resource* | Sets the resource from where to load the configuration. It can be a: URI, String (URI) or an InputStream. The option is a java.lang.Object type. | | String
| *camel.component.ignite-set.enabled* | Enable ignite-set component | true | Boolean
| *camel.component.ignite-set.ignite* | Sets the Ignite instance. The option is a org.apache.ignite.Ignite type. | | String
| *camel.component.ignite-set.ignite-configuration* | Allows the user to set a programmatic IgniteConfiguration. The option is a org.apache.ignite.configuration.IgniteConfiguration type. | | String
+| *camel.component.ignite-set.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-infinispan/src/main/docs/infinispan-component.adoc b/components/camel-infinispan/src/main/docs/infinispan-component.adoc
index 34e9842..f2c4ee7 100644
--- a/components/camel-infinispan/src/main/docs/infinispan-component.adoc
+++ b/components/camel-infinispan/src/main/docs/infinispan-component.adoc
@@ -56,7 +56,7 @@ accessible from the registry.
// component options: START
-The Infinispan component supports 3 options, which are listed below.
+The Infinispan component supports 5 options, which are listed below.
@@ -66,6 +66,8 @@ The Infinispan component supports 3 options, which are listed below.
| *configuration* (common) | The default configuration shared among endpoints. | | InfinispanConfiguration
| *cacheContainer* (common) | The default cache container. | | BasicCacheContainer
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -136,7 +138,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 22 options, which are listed below.
+The component supports 24 options, which are listed below.
@@ -144,6 +146,7 @@ The component supports 22 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.infinispan.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.infinispan.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.infinispan.cache-container* | The default cache container. The option is a org.infinispan.commons.api.BasicCacheContainer type. | | String
| *camel.component.infinispan.configuration.cache-container* | Specifies the cache Container to connect | | BasicCacheContainer
| *camel.component.infinispan.configuration.cache-container-configuration* | The CacheContainer configuration. Uses if the cacheContainer is not defined. Must be the following types: org.infinispan.client.hotrod.configuration.Configuration - for remote cache interaction configuration; org.infinispan.configuration.cache.Configuration - for embedded cache interaction configuration; | | Object
@@ -164,6 +167,7 @@ The component supports 22 options, which are listed below.
| *camel.component.infinispan.customizer.remote-cache-manager.enabled* | Enable or disable the cache-manager customizer. | true | Boolean
| *camel.component.infinispan.customizer.remote-cache-manager.override* | Configure if the cache manager eventually set on the component should be overridden by the customizer. | false | Boolean
| *camel.component.infinispan.enabled* | Enable infinispan component | true | Boolean
+| *camel.component.infinispan.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed [...]
| *camel.component.infinispan.configuration.command* | *Deprecated* The operation to perform. | PUT | String
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-influxdb/src/main/docs/influxdb-component.adoc b/components/camel-influxdb/src/main/docs/influxdb-component.adoc
index 850b942..a1f6b7b 100644
--- a/components/camel-influxdb/src/main/docs/influxdb-component.adoc
+++ b/components/camel-influxdb/src/main/docs/influxdb-component.adoc
@@ -46,7 +46,7 @@ configured in the registry, using the native java driver.
// component options: START
-The InfluxDB component supports 1 options, which are listed below.
+The InfluxDB component supports 3 options, which are listed below.
@@ -54,6 +54,8 @@ The InfluxDB component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -111,7 +113,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -119,7 +121,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.influxdb.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.influxdb.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.influxdb.enabled* | Enable influxdb component | true | Boolean
+| *camel.component.influxdb.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed t [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-iota/src/main/docs/iota-component.adoc b/components/camel-iota/src/main/docs/iota-component.adoc
index 9e4e3a1..4cec6c5 100644
--- a/components/camel-iota/src/main/docs/iota-component.adoc
+++ b/components/camel-iota/src/main/docs/iota-component.adoc
@@ -32,7 +32,7 @@ iota:name?url=nodeurl[&moreOptions...]
== Options
// component options: START
-The IOTA component supports 1 options, which are listed below.
+The IOTA component supports 3 options, which are listed below.
@@ -40,6 +40,8 @@ The IOTA component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -99,7 +101,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -107,7 +109,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.iota.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.iota.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.iota.enabled* | Whether to enable auto configuration of the iota component. This is enabled by default. | | Boolean
+| *camel.component.iota.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-ipfs/src/main/docs/ipfs-component.adoc b/components/camel-ipfs/src/main/docs/ipfs-component.adoc
index 338d39b..64f0cab 100644
--- a/components/camel-ipfs/src/main/docs/ipfs-component.adoc
+++ b/components/camel-ipfs/src/main/docs/ipfs-component.adoc
@@ -32,7 +32,7 @@ ipfs://cmd?options
== Options
// component options: START
-The IPFS component supports 1 options, which are listed below.
+The IPFS component supports 3 options, which are listed below.
@@ -40,6 +40,8 @@ The IPFS component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -92,7 +94,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -100,7 +102,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.ipfs.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.ipfs.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.ipfs.enabled* | Whether to enable auto configuration of the ipfs component. This is enabled by default. | | Boolean
+| *camel.component.ipfs.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-irc/src/main/docs/irc-component.adoc b/components/camel-irc/src/main/docs/irc-component.adoc
index a32ab07..5c9b03c 100644
--- a/components/camel-irc/src/main/docs/irc-component.adoc
+++ b/components/camel-irc/src/main/docs/irc-component.adoc
@@ -39,7 +39,7 @@ You can append query options to the URI in the following format,
// component options: START
-The IRC component supports 2 options, which are listed below.
+The IRC component supports 4 options, which are listed below.
@@ -48,6 +48,8 @@ The IRC component supports 2 options, which are listed below.
| Name | Description | Default | Type
| *useGlobalSslContext Parameters* (security) | Enable usage of global SSL context parameters. | false | boolean
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -128,7 +130,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 3 options, which are listed below.
+The component supports 5 options, which are listed below.
@@ -136,7 +138,9 @@ The component supports 3 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.irc.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.irc.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.irc.enabled* | Enable irc component | true | Boolean
+| *camel.component.irc.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then c [...]
| *camel.component.irc.use-global-ssl-context-parameters* | Enable usage of global SSL context parameters. | false | Boolean
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-ironmq/src/main/docs/ironmq-component.adoc b/components/camel-ironmq/src/main/docs/ironmq-component.adoc
index 89de114..91a7d83 100644
--- a/components/camel-ironmq/src/main/docs/ironmq-component.adoc
+++ b/components/camel-ironmq/src/main/docs/ironmq-component.adoc
@@ -120,7 +120,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -128,7 +128,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.ironmq.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.ironmq.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.ironmq.enabled* | Enable ironmq component | true | Boolean
+| *camel.component.ironmq.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed the [...]
|===
// spring-boot-auto-configure options: END
@@ -144,7 +146,7 @@ The component supports 2 options, which are listed below.
// component options: START
-The IronMQ component supports 1 options, which are listed below.
+The IronMQ component supports 3 options, which are listed below.
@@ -152,6 +154,8 @@ The IronMQ component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
diff --git a/components/camel-jbpm/src/main/docs/jbpm-component.adoc b/components/camel-jbpm/src/main/docs/jbpm-component.adoc
index 2605737..13a36a9 100644
--- a/components/camel-jbpm/src/main/docs/jbpm-component.adoc
+++ b/components/camel-jbpm/src/main/docs/jbpm-component.adoc
@@ -140,7 +140,7 @@ jbpm::hostName[:port][/resourceUri][?options]
// component options: START
-The JBPM component supports 1 options, which are listed below.
+The JBPM component supports 3 options, which are listed below.
@@ -148,6 +148,8 @@ The JBPM component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -231,7 +233,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -239,7 +241,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.jbpm.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.jbpm.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.jbpm.enabled* | Enable jbpm component | true | Boolean
+| *camel.component.jbpm.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-jcache/src/main/docs/jcache-component.adoc b/components/camel-jcache/src/main/docs/jcache-component.adoc
index 3bcec50..a5cf2f2 100644
--- a/components/camel-jcache/src/main/docs/jcache-component.adoc
+++ b/components/camel-jcache/src/main/docs/jcache-component.adoc
@@ -85,7 +85,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 6 options, which are listed below.
+The component supports 8 options, which are listed below.
@@ -93,11 +93,13 @@ The component supports 6 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.jcache.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.jcache.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.jcache.cache-configuration* | A Configuration for the Cache. The option is a javax.cache.configuration.Configuration type. | | String
| *camel.component.jcache.cache-configuration-properties* | The Properties for the javax.cache.spi.CachingProvider to create the CacheManager. The option is a java.util.Properties type. | | String
| *camel.component.jcache.caching-provider* | The fully qualified class name of the javax.cache.spi.CachingProvider | | String
| *camel.component.jcache.configuration-uri* | An implementation specific URI for the CacheManager | | String
| *camel.component.jcache.enabled* | Enable jcache component | true | Boolean
+| *camel.component.jcache.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed the [...]
|===
// spring-boot-auto-configure options: END
@@ -110,7 +112,7 @@ The component supports 6 options, which are listed below.
// component options: START
-The JCache component supports 5 options, which are listed below.
+The JCache component supports 7 options, which are listed below.
@@ -122,6 +124,8 @@ The JCache component supports 5 options, which are listed below.
| *cacheConfiguration Properties* (common) | The Properties for the javax.cache.spi.CachingProvider to create the CacheManager | | Properties
| *configurationUri* (common) | An implementation specific URI for the CacheManager | | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
diff --git a/components/camel-jclouds/src/main/docs/jclouds-component.adoc b/components/camel-jclouds/src/main/docs/jclouds-component.adoc
index 53d654a..edf75d7 100644
--- a/components/camel-jclouds/src/main/docs/jclouds-component.adoc
+++ b/components/camel-jclouds/src/main/docs/jclouds-component.adoc
@@ -107,7 +107,7 @@ You can append query options to the URI in the following format,
// component options: START
-The JClouds component supports 3 options, which are listed below.
+The JClouds component supports 5 options, which are listed below.
@@ -117,6 +117,8 @@ The JClouds component supports 3 options, which are listed below.
| *blobStores* (common) | To use the given BlobStore which must be configured when using blobstore. | | List
| *computeServices* (common) | To use the given ComputeService which must be configured when use compute. | | List
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -200,7 +202,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 4 options, which are listed below.
+The component supports 6 options, which are listed below.
@@ -209,8 +211,10 @@ The component supports 4 options, which are listed below.
| Name | Description | Default | Type
| *camel.component.jclouds.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
| *camel.component.jclouds.blob-stores* | To use the given BlobStore which must be configured when using blobstore. | | List
+| *camel.component.jclouds.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.jclouds.compute-services* | To use the given ComputeService which must be configured when use compute. | | List
| *camel.component.jclouds.enabled* | Whether to enable auto configuration of the jclouds component. This is enabled by default. | | Boolean
+| *camel.component.jclouds.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-jcr/src/main/docs/jcr-component.adoc b/components/camel-jcr/src/main/docs/jcr-component.adoc
index 1c7bea9..c09a11c 100644
--- a/components/camel-jcr/src/main/docs/jcr-component.adoc
+++ b/components/camel-jcr/src/main/docs/jcr-component.adoc
@@ -46,7 +46,7 @@ The `repository` element of the URI is used to look up the JCR
// component options: START
-The JCR component supports 1 options, which are listed below.
+The JCR component supports 3 options, which are listed below.
@@ -54,6 +54,8 @@ The JCR component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -120,7 +122,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -128,7 +130,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.jcr.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.jcr.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.jcr.enabled* | Enable jcr component | true | Boolean
+| *camel.component.jcr.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then c [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-jdbc/src/main/docs/jdbc-component.adoc b/components/camel-jdbc/src/main/docs/jdbc-component.adoc
index 5cd9846..4043ae5 100644
--- a/components/camel-jdbc/src/main/docs/jdbc-component.adoc
+++ b/components/camel-jdbc/src/main/docs/jdbc-component.adoc
@@ -44,7 +44,7 @@ You can append query options to the URI in the following format,
== Options
// component options: START
-The JDBC component supports 2 options, which are listed below.
+The JDBC component supports 4 options, which are listed below.
@@ -53,6 +53,8 @@ The JDBC component supports 2 options, which are listed below.
| Name | Description | Default | Type
| *dataSource* (producer) | To use the DataSource instance instead of looking up the data source by name from the registry. | | DataSource
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -120,7 +122,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 3 options, which are listed below.
+The component supports 5 options, which are listed below.
@@ -128,8 +130,10 @@ The component supports 3 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.jdbc.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.jdbc.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.jdbc.data-source* | To use the DataSource instance instead of looking up the data source by name from the registry. The option is a javax.sql.DataSource type. | | String
| *camel.component.jdbc.enabled* | Enable jdbc component | true | Boolean
+| *camel.component.jdbc.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-jetty/src/main/docs/jetty-component.adoc b/components/camel-jetty/src/main/docs/jetty-component.adoc
index 4c44ba8..d3b040a 100644
--- a/components/camel-jetty/src/main/docs/jetty-component.adoc
+++ b/components/camel-jetty/src/main/docs/jetty-component.adoc
@@ -53,7 +53,7 @@ You can append query options to the URI in the following format,
// component options: START
-The Jetty component supports 31 options, which are listed below.
+The Jetty component supports 33 options, which are listed below.
@@ -91,6 +91,8 @@ The Jetty component supports 31 options, which are listed below.
| *allowJavaSerialized Object* (advanced) | Whether to allow java serialization when a request uses context-type=application/x-java-serialized-object. This is by default turned off. If you enable this then be aware that Java will deserialize the incoming data from the request to Java and that can be a potential security risk. | false | boolean
| *headerFilterStrategy* (filter) | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. | | HeaderFilterStrategy
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -179,7 +181,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 32 options, which are listed below.
+The component supports 34 options, which are listed below.
@@ -188,6 +190,7 @@ The component supports 32 options, which are listed below.
| Name | Description | Default | Type
| *camel.component.jetty.allow-java-serialized-object* | Whether to allow java serialization when a request uses context-type=application/x-java-serialized-object. This is by default turned off. If you enable this then be aware that Java will deserialize the incoming data from the request to Java and that can be a potential security risk. | false | Boolean
| *camel.component.jetty.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.jetty.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.jetty.continuation-timeout* | Allows to set a timeout in millis when using Jetty as consumer (server). By default Jetty uses 30000. You can use a value of = 0 to never expire. If a timeout occurs then the request will be expired and Jetty will return back a http error 503 to the client. This option is only in use when using Jetty with the Asynchronous Routing Engine. | 30000 | Long
| *camel.component.jetty.enable-jmx* | If this option is true, Jetty JMX support will be enabled for this endpoint. | false | Boolean
| *camel.component.jetty.enabled* | Whether to enable auto configuration of the jetty component. This is enabled by default. | | Boolean
@@ -197,6 +200,7 @@ The component supports 32 options, which are listed below.
| *camel.component.jetty.http-configuration* | Jetty component does not use HttpConfiguration. The option is a org.apache.camel.http.common.HttpConfiguration type. | | String
| *camel.component.jetty.jetty-http-binding* | To use a custom org.apache.camel.component.jetty.JettyHttpBinding, which are used to customize how a response should be written for the producer. The option is a org.apache.camel.component.jetty.JettyHttpBinding type. | | String
| *camel.component.jetty.keystore* | Specifies the location of the Java keystore file, which contains the Jetty server's own X.509 certificate in a key entry. | | String
+| *camel.component.jetty.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
| *camel.component.jetty.max-threads* | To set a value for maximum number of threads in server thread pool. Notice that both a min and max size must be configured. | | Integer
| *camel.component.jetty.mb-container* | To use a existing configured org.eclipse.jetty.jmx.MBeanContainer if JMX is enabled that Jetty uses for registering mbeans. The option is a org.eclipse.jetty.jmx.MBeanContainer type. | | String
| *camel.component.jetty.min-threads* | To set a value for minimum number of threads in server thread pool. Notice that both a min and max size must be configured. | | Integer
diff --git a/components/camel-jgroups-raft/src/main/docs/jgroups-raft-component.adoc b/components/camel-jgroups-raft/src/main/docs/jgroups-raft-component.adoc
index b7d9fd7..4a6cbe7 100644
--- a/components/camel-jgroups-raft/src/main/docs/jgroups-raft-component.adoc
+++ b/components/camel-jgroups-raft/src/main/docs/jgroups-raft-component.adoc
@@ -36,7 +36,7 @@ component should connect to.
== Options
// component options: START
-The JGroups raft component supports 5 options, which are listed below.
+The JGroups raft component supports 7 options, which are listed below.
@@ -48,6 +48,8 @@ The JGroups raft component supports 5 options, which are listed below.
| *raftId* (common) | *Required* Unique raftId to use. | | String
| *channelProperties* (common) | Specifies configuration properties of the RaftHandle JChannel used by the endpoint (ignored if raftHandle ref is provided). | raft.xml | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -102,7 +104,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 11 options, which are listed below.
+The component supports 13 options, which are listed below.
@@ -110,8 +112,10 @@ The component supports 11 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.jgroups-raft.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.jgroups-raft.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.jgroups-raft.channel-properties* | Specifies configuration properties of the RaftHandle JChannel used by the endpoint (ignored if raftHandle ref is provided). | raft.xml | String
| *camel.component.jgroups-raft.enabled* | Enable jgroups-raft component | true | Boolean
+| *camel.component.jgroups-raft.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is process [...]
| *camel.component.jgroups-raft.raft-handle* | RaftHandle to use. The option is a org.jgroups.raft.RaftHandle type. | | String
| *camel.component.jgroups-raft.raft-id* | Unique raftId to use. | | String
| *camel.component.jgroups-raft.state-machine* | StateMachine to use. The option is a org.jgroups.protocols.raft.StateMachine type. | | String
diff --git a/components/camel-jgroups/src/main/docs/jgroups-component.adoc b/components/camel-jgroups/src/main/docs/jgroups-component.adoc
index c9b797d..0587e39 100644
--- a/components/camel-jgroups/src/main/docs/jgroups-component.adoc
+++ b/components/camel-jgroups/src/main/docs/jgroups-component.adoc
@@ -40,7 +40,7 @@ component should connect to.
// component options: START
-The JGroups component supports 4 options, which are listed below.
+The JGroups component supports 6 options, which are listed below.
@@ -51,6 +51,8 @@ The JGroups component supports 4 options, which are listed below.
| *channelProperties* (common) | Specifies configuration properties of the JChannel used by the endpoint. | | String
| *enableViewMessages* (consumer) | If set to true, the consumer endpoint will receive org.jgroups.View messages as well (not only org.jgroups.Message instances). By default only regular messages are consumed by the endpoint. | false | boolean
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -110,7 +112,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 9 options, which are listed below.
+The component supports 11 options, which are listed below.
@@ -118,10 +120,12 @@ The component supports 9 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.jgroups.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.jgroups.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.jgroups.channel* | Channel to use. The option is a org.jgroups.JChannel type. | | String
| *camel.component.jgroups.channel-properties* | Specifies configuration properties of the JChannel used by the endpoint. | | String
| *camel.component.jgroups.enable-view-messages* | If set to true, the consumer endpoint will receive org.jgroups.View messages as well (not only org.jgroups.Message instances). By default only regular messages are consumed by the endpoint. | false | Boolean
| *camel.component.jgroups.enabled* | Enable jgroups component | true | Boolean
+| *camel.component.jgroups.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
| *camel.component.jgroups.lock.cluster.service.enabled* | Sets if the jgroups lock cluster service should be enabled or not, default is false. | false | Boolean
| *camel.component.jgroups.lock.cluster.service.id* | Cluster Service ID | | String
| *camel.component.jgroups.lock.cluster.service.jgroups-cluster-name* | JGroups Cluster name | | String
diff --git a/components/camel-jing/src/main/docs/jing-component.adoc b/components/camel-jing/src/main/docs/jing-component.adoc
index 0bc270e..f8cb287 100644
--- a/components/camel-jing/src/main/docs/jing-component.adoc
+++ b/components/camel-jing/src/main/docs/jing-component.adoc
@@ -45,7 +45,7 @@ option compactSyntax to turn on either RNG or RNC mode.
// component options: START
-The Jing component supports 1 options, which are listed below.
+The Jing component supports 3 options, which are listed below.
@@ -53,6 +53,8 @@ The Jing component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -106,7 +108,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -114,7 +116,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.jing.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.jing.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.jing.enabled* | Enable jing component | true | Boolean
+| *camel.component.jing.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-jira/src/main/docs/jira-component.adoc b/components/camel-jira/src/main/docs/jira-component.adoc
index 0e8ce41..8139ce7 100644
--- a/components/camel-jira/src/main/docs/jira-component.adoc
+++ b/components/camel-jira/src/main/docs/jira-component.adoc
@@ -46,7 +46,7 @@ jira://type[?options]
// component options: START
-The Jira component supports 2 options, which are listed below.
+The Jira component supports 4 options, which are listed below.
@@ -55,6 +55,8 @@ The Jira component supports 2 options, which are listed below.
| Name | Description | Default | Type
| *configuration* (advanced) | The JiraConfiguration parameters | | JiraConfiguration
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -137,7 +139,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 10 options, which are listed below.
+The component supports 12 options, which are listed below.
@@ -145,6 +147,7 @@ The component supports 10 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.jira.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.jira.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.jira.configuration.access-token* | (OAuth only) The access token generated by the Jira server. | | String
| *camel.component.jira.configuration.consumer-key* | (OAuth only) The consumer key from Jira settings. | | String
| *camel.component.jira.configuration.delay* | Time in milliseconds to elapse for the next poll. | 6000 | Integer
@@ -154,6 +157,7 @@ The component supports 10 options, which are listed below.
| *camel.component.jira.configuration.username* | (Basic authentication only) The username to authenticate to the Jira server. Use only if OAuth is not enabled on the Jira server. Do not set the username and OAuth token parameter, if they are both set, the username basic authentication takes precedence. | | String
| *camel.component.jira.configuration.verification-code* | (OAuth only) The verification code from Jira generated in the first step of the authorization proccess. | | String
| *camel.component.jira.enabled* | Whether to enable auto configuration of the jira component. This is enabled by default. | | Boolean
+| *camel.component.jira.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-jms/src/main/docs/jms-component.adoc b/components/camel-jms/src/main/docs/jms-component.adoc
index 9551bfa..a31fb56 100644
--- a/components/camel-jms/src/main/docs/jms-component.adoc
+++ b/components/camel-jms/src/main/docs/jms-component.adoc
@@ -182,7 +182,7 @@ about these properties by consulting the relevant Spring documentation.
// component options: START
-The JMS component supports 80 options, which are listed below.
+The JMS component supports 82 options, which are listed below.
@@ -269,6 +269,8 @@ The JMS component supports 80 options, which are listed below.
| *formatDateHeadersTo Iso8601* (producer) | Sets whether date headers should be formatted according to the ISO 8601 standard. | false | boolean
| *headerFilterStrategy* (filter) | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. | | HeaderFilterStrategy
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -426,7 +428,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 171 options, which are listed below.
+The component supports 173 options, which are listed below.
@@ -445,6 +447,7 @@ The component supports 171 options, which are listed below.
| *camel.component.jms.async-stop-listener* | Whether to stop the JmsConsumer message listener asynchronously, when stopping a route. | false | Boolean
| *camel.component.jms.auto-startup* | Specifies whether the consumer container should auto-startup. | true | Boolean
| *camel.component.jms.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.jms.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.jms.cache-level* | Sets the cache level by ID for the underlying JMS resources. See cacheLevelName option for more details. | | Integer
| *camel.component.jms.cache-level-name* | Sets the cache level by name for the underlying JMS resources. Possible values are: CACHE_AUTO, CACHE_CONNECTION, CACHE_CONSUMER, CACHE_NONE, and CACHE_SESSION. The default setting is CACHE_AUTO. See the Spring documentation and Transactions Cache Levels for more information. | CACHE_AUTO | String
| *camel.component.jms.client-id* | Sets the JMS client ID to use. Note that this value, if specified, must be unique and can only be used by a single JMS connection instance. It is typically only required for durable topic subscriptions. If using Apache ActiveMQ you may prefer to use Virtual Topics instead. | | String
@@ -566,6 +569,7 @@ The component supports 171 options, which are listed below.
| *camel.component.jms.jms-key-format-strategy* | Pluggable strategy for encoding and decoding JMS keys so they can be compliant with the JMS specification. Camel provides two implementations out of the box: default and passthrough. The default strategy will safely marshal dots and hyphens (. and -). The passthrough strategy leaves the key as is. Can be used for JMS brokers which do not care whether JMS header keys contain illegal characters. You can provide your own implementation of th [...]
| *camel.component.jms.jms-operations* | Allows you to use your own implementation of the org.springframework.jms.core.JmsOperations interface. Camel uses JmsTemplate as default. Can be used for testing purpose, but not used much as stated in the spring API docs. The option is a org.springframework.jms.core.JmsOperations type. | | String
| *camel.component.jms.lazy-create-transaction-manager* | If true, Camel will create a JmsTransactionManager, if there is no transactionManager injected when option transacted=true. | true | Boolean
+| *camel.component.jms.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then c [...]
| *camel.component.jms.map-jms-message* | Specifies whether Camel should auto map the received JMS message to a suited payload type, such as javax.jms.TextMessage to a String etc. See section about how mapping works below for more details. | true | Boolean
| *camel.component.jms.max-concurrent-consumers* | Specifies the maximum number of concurrent consumers when consuming from JMS (not for request/reply over JMS). See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. When doing request/reply over JMS then the option replyToMaxConcurrentConsumers is used to control number of concurrent consumers on the reply message listener. | | Integer
| *camel.component.jms.max-messages-per-task* | The number of messages per task. -1 is unlimited. If you use a range for concurrent consumers (eg min max), then this option can be used to set a value to eg 100 to control how fast the consumers will shrink when less work is required. | -1 | Integer
diff --git a/components/camel-jmx/src/main/docs/jmx-component.adoc b/components/camel-jmx/src/main/docs/jmx-component.adoc
index abcaf01..b380193 100644
--- a/components/camel-jmx/src/main/docs/jmx-component.adoc
+++ b/components/camel-jmx/src/main/docs/jmx-component.adoc
@@ -18,7 +18,7 @@ monitor Camel using JMX.
== Options
// component options: START
-The JMX component supports 1 options, which are listed below.
+The JMX component supports 3 options, which are listed below.
@@ -26,6 +26,8 @@ The JMX component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -103,7 +105,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -111,7 +113,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.jmx.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.jmx.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.jmx.enabled* | Enable jmx component | true | Boolean
+| *camel.component.jmx.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then c [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-jolt/src/main/docs/jolt-component.adoc b/components/camel-jolt/src/main/docs/jolt-component.adoc
index 2e1c667..0eb81fe 100644
--- a/components/camel-jolt/src/main/docs/jolt-component.adoc
+++ b/components/camel-jolt/src/main/docs/jolt-component.adoc
@@ -46,7 +46,7 @@ format, `?option=value&option=value&...`
// component options: START
-The JOLT component supports 2 options, which are listed below.
+The JOLT component supports 4 options, which are listed below.
@@ -55,6 +55,8 @@ The JOLT component supports 2 options, which are listed below.
| Name | Description | Default | Type
| *transform* (advanced) | Explicitly sets the Transform to use. If not set a Transform specified by the transformDsl will be created | | Transform
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -113,7 +115,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 3 options, which are listed below.
+The component supports 5 options, which are listed below.
@@ -121,7 +123,9 @@ The component supports 3 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.jolt.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.jolt.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.jolt.enabled* | Enable jolt component | true | Boolean
+| *camel.component.jolt.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
| *camel.component.jolt.transform* | Explicitly sets the Transform to use. If not set a Transform specified by the transformDsl will be created. The option is a com.bazaarvoice.jolt.Transform type. | | String
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-jooq/src/main/docs/jooq-component.adoc b/components/camel-jooq/src/main/docs/jooq-component.adoc
index d684012..072ca95 100644
--- a/components/camel-jooq/src/main/docs/jooq-component.adoc
+++ b/components/camel-jooq/src/main/docs/jooq-component.adoc
@@ -44,7 +44,7 @@ If you do not wish to delete the entity bean when it has been processed, you can
== Options
// component options: START
-The JOOQ component supports 2 options, which are listed below.
+The JOOQ component supports 4 options, which are listed below.
@@ -53,6 +53,8 @@ The JOOQ component supports 2 options, which are listed below.
| Name | Description | Default | Type
| *configuration* (common) | Component configuration (database connection, database entity type, etc.) | | JooqConfiguration
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -126,7 +128,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 7 options, which are listed below.
+The component supports 9 options, which are listed below.
@@ -134,12 +136,14 @@ The component supports 7 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.jooq.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.jooq.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.jooq.configuration.consume-delete* | Delete entity after it is consumed | true | Boolean
| *camel.component.jooq.configuration.database-configuration* | | | Configuration
| *camel.component.jooq.configuration.entity-type* | JOOQ entity class | | Class
| *camel.component.jooq.configuration.operation* | Type of operation to execute on query | | JooqOperation
| *camel.component.jooq.configuration.query* | To execute plain SQL query | | String
| *camel.component.jooq.enabled* | Whether to enable auto configuration of the jooq component. This is enabled by default. | | Boolean
+| *camel.component.jooq.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-jpa/src/main/docs/jpa-component.adoc b/components/camel-jpa/src/main/docs/jpa-component.adoc
index aed4236..96064bc 100644
--- a/components/camel-jpa/src/main/docs/jpa-component.adoc
+++ b/components/camel-jpa/src/main/docs/jpa-component.adoc
@@ -98,7 +98,7 @@ You can append query options to the URI in the following format,
// component options: START
-The JPA component supports 5 options, which are listed below.
+The JPA component supports 7 options, which are listed below.
@@ -110,6 +110,8 @@ The JPA component supports 5 options, which are listed below.
| *joinTransaction* (common) | The camel-jpa component will join transaction by default. You can use this option to turn this off, for example if you use LOCAL_RESOURCE and join transaction doesn't work with your JPA provider. This option can also be set globally on the JpaComponent, instead of having to set it on all endpoints. | true | boolean
| *sharedEntityManager* (common) | Whether to use Spring's SharedEntityManager for the consumer/producer. Note in most cases joinTransaction should be set to false as this is not an EXTENDED EntityManager. | false | boolean
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -209,7 +211,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 6 options, which are listed below.
+The component supports 8 options, which are listed below.
@@ -217,9 +219,11 @@ The component supports 6 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.jpa.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.jpa.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.jpa.enabled* | Enable jpa component | true | Boolean
| *camel.component.jpa.entity-manager-factory* | To use the EntityManagerFactory. This is strongly recommended to configure. The option is a javax.persistence.EntityManagerFactory type. | | String
| *camel.component.jpa.join-transaction* | The camel-jpa component will join transaction by default. You can use this option to turn this off, for example if you use LOCAL_RESOURCE and join transaction doesn't work with your JPA provider. This option can also be set globally on the JpaComponent, instead of having to set it on all endpoints. | true | Boolean
+| *camel.component.jpa.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then c [...]
| *camel.component.jpa.shared-entity-manager* | Whether to use Spring's SharedEntityManager for the consumer/producer. Note in most cases joinTransaction should be set to false as this is not an EXTENDED EntityManager. | false | Boolean
| *camel.component.jpa.transaction-manager* | To use the PlatformTransactionManager for managing transactions. The option is a org.springframework.transaction.PlatformTransactionManager type. | | String
|===
diff --git a/components/camel-jsch/src/main/docs/scp-component.adoc b/components/camel-jsch/src/main/docs/scp-component.adoc
index 6a66e5a..05c4e0c 100644
--- a/components/camel-jsch/src/main/docs/scp-component.adoc
+++ b/components/camel-jsch/src/main/docs/scp-component.adoc
@@ -46,7 +46,7 @@ in code).
// component options: START
-The SCP component supports 2 options, which are listed below.
+The SCP component supports 4 options, which are listed below.
@@ -55,6 +55,8 @@ The SCP component supports 2 options, which are listed below.
| Name | Description | Default | Type
| *verboseLogging* (producer) | JSCH is verbose logging out of the box. Therefore we turn the logging down to DEBUG logging by default. But setting this option to true turns on the verbose logging again. | false | boolean
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -135,7 +137,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 3 options, which are listed below.
+The component supports 5 options, which are listed below.
@@ -143,7 +145,9 @@ The component supports 3 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.scp.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.scp.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.scp.enabled* | Enable scp component | true | Boolean
+| *camel.component.scp.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then c [...]
| *camel.component.scp.verbose-logging* | JSCH is verbose logging out of the box. Therefore we turn the logging down to DEBUG logging by default. But setting this option to true turns on the verbose logging again. | false | Boolean
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-json-validator/src/main/docs/json-validator-component.adoc b/components/camel-json-validator/src/main/docs/json-validator-component.adoc
index ebdffe2..c550fc3 100644
--- a/components/camel-json-validator/src/main/docs/json-validator-component.adoc
+++ b/components/camel-json-validator/src/main/docs/json-validator-component.adoc
@@ -40,7 +40,7 @@ the JSON Schema to validate against.
== URI Options
// component options: START
-The JSON Schema Validator component supports 1 options, which are listed below.
+The JSON Schema Validator component supports 3 options, which are listed below.
@@ -48,6 +48,8 @@ The JSON Schema Validator component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -105,7 +107,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -113,7 +115,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.json-validator.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.json-validator.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.json-validator.enabled* | Whether to enable auto configuration of the json-validator component. This is enabled by default. | | Boolean
+| *camel.component.json-validator.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proce [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-jt400/src/main/docs/jt400-component.adoc b/components/camel-jt400/src/main/docs/jt400-component.adoc
index 4301964..17af939 100644
--- a/components/camel-jt400/src/main/docs/jt400-component.adoc
+++ b/components/camel-jt400/src/main/docs/jt400-component.adoc
@@ -43,7 +43,7 @@ You can append query options to the URI in the following format,
== JT400 options
// component options: START
-The JT400 component supports 2 options, which are listed below.
+The JT400 component supports 4 options, which are listed below.
@@ -52,6 +52,8 @@ The JT400 component supports 2 options, which are listed below.
| Name | Description | Default | Type
| *connectionPool* (advanced) | Returns the default connection pool used by this component. | | AS400ConnectionPool
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -136,7 +138,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 3 options, which are listed below.
+The component supports 5 options, which are listed below.
@@ -144,8 +146,10 @@ The component supports 3 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.jt400.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.jt400.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.jt400.connection-pool* | Returns the default connection pool used by this component. The option is a com.ibm.as400.access.AS400ConnectionPool type. | | String
| *camel.component.jt400.enabled* | Enable jt400 component | true | Boolean
+| *camel.component.jt400.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-kafka/src/main/docs/kafka-component.adoc b/components/camel-kafka/src/main/docs/kafka-component.adoc
index bdd9ef9..8b81a31 100644
--- a/components/camel-kafka/src/main/docs/kafka-component.adoc
+++ b/components/camel-kafka/src/main/docs/kafka-component.adoc
@@ -37,7 +37,7 @@ kafka:topic[?options]
// component options: START
-The Kafka component supports 8 options, which are listed below.
+The Kafka component supports 10 options, which are listed below.
@@ -52,6 +52,8 @@ The Kafka component supports 8 options, which are listed below.
| *allowManualCommit* (consumer) | Whether to allow doing manual commits via KafkaManualCommit. If this option is enabled then an instance of KafkaManualCommit is stored on the Exchange message header, which allows end users to access this API and perform manual offset commits via the Kafka consumer. | false | boolean
| *kafkaManualCommit Factory* (consumer) | Factory to use for creating KafkaManualCommit instances. This allows to plugin a custom factory to create custom KafkaManualCommit instances in case special logic is needed when doing manual commits that deviates from the default implementation that comes out of the box. | | KafkaManualCommitFactory
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -195,7 +197,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 98 options, which are listed below.
+The component supports 100 options, which are listed below.
@@ -205,6 +207,7 @@ The component supports 98 options, which are listed below.
| *camel.component.kafka.allow-manual-commit* | Whether to allow doing manual commits via KafkaManualCommit. If this option is enabled then an instance of KafkaManualCommit is stored on the Exchange message header, which allows end users to access this API and perform manual offset commits via the Kafka consumer. | false | Boolean
| *camel.component.kafka.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
| *camel.component.kafka.break-on-first-error* | This options controls what happens when a consumer is processing an exchange and it fails. If the option is false then the consumer continues to the next message and processes it. If the option is true then the consumer breaks out, and will seek back to offset of the message that caused a failure, and then re-attempt to process this message. However this can lead to endless processing of the same message if its bound to fail every time, eg [...]
+| *camel.component.kafka.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.kafka.brokers* | URL of the Kafka brokers to use. The format is host1:port1,host2:port2, and the list can be a subset of brokers or a VIP pointing to a subset of brokers. This option is known as bootstrap.servers in the Kafka documentation. | | String
| *camel.component.kafka.configuration.allow-manual-commit* | Whether to allow doing manual commits via {@link KafkaManualCommit}. <p/> If this option is enabled then an instance of {@link KafkaManualCommit} is stored on the {@link Exchange} message header, which allows end users to access this API and perform manual offset commits via the Kafka consumer. | false | Boolean
| *camel.component.kafka.configuration.auto-commit-enable* | If true, periodically commit to ZooKeeper the offset of messages already fetched by the consumer. This committed offset will be used when the process fails as the position from which the new consumer will begin. | true | Boolean
@@ -298,6 +301,7 @@ The component supports 98 options, which are listed below.
| *camel.component.kafka.configuration.worker-pool-max-size* | Maximum number of threads for the worker pool for continue routing {@link Exchange} after kafka server has acknowledge the message that was sent to it from {@link KafkaProducer} using asynchronous non-blocking processing. | 20 | Integer
| *camel.component.kafka.enabled* | Enable kafka component | true | Boolean
| *camel.component.kafka.kafka-manual-commit-factory* | Factory to use for creating KafkaManualCommit instances. This allows to plugin a custom factory to create custom KafkaManualCommit instances in case special logic is needed when doing manual commits that deviates from the default implementation that comes out of the box. The option is a org.apache.camel.component.kafka.KafkaManualCommitFactory type. | | String
+| *camel.component.kafka.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
| *camel.component.kafka.use-global-ssl-context-parameters* | Enable usage of global SSL context parameters. | false | Boolean
| *camel.component.kafka.worker-pool* | To use a shared custom worker pool for continue routing Exchange after kafka server has acknowledge the message that was sent to it from KafkaProducer using asynchronous non-blocking processing. If using this option then you must handle the lifecycle of the thread pool to shut the pool down when no longer needed. The option is a java.util.concurrent.ExecutorService type. | | String
|===
diff --git a/components/camel-kubernetes/src/main/docs/kubernetes-config-maps-component.adoc b/components/camel-kubernetes/src/main/docs/kubernetes-config-maps-component.adoc
index c0a53a7..6744708 100644
--- a/components/camel-kubernetes/src/main/docs/kubernetes-config-maps-component.adoc
+++ b/components/camel-kubernetes/src/main/docs/kubernetes-config-maps-component.adoc
@@ -14,7 +14,7 @@ provides a producer to execute kubernetes ConfigMap operations and a consumer to
== Component Options
// component options: START
-The Kubernetes ConfigMap component supports 1 options, which are listed below.
+The Kubernetes ConfigMap component supports 3 options, which are listed below.
@@ -22,6 +22,8 @@ The Kubernetes ConfigMap component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -93,7 +95,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -101,7 +103,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.kubernetes-config-maps.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.kubernetes-config-maps.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.kubernetes-config-maps.enabled* | Whether to enable auto configuration of the kubernetes-config-maps component. This is enabled by default. | | Boolean
+| *camel.component.kubernetes-config-maps.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-kubernetes/src/main/docs/kubernetes-deployments-component.adoc b/components/camel-kubernetes/src/main/docs/kubernetes-deployments-component.adoc
index 8af5a36..eb6cbe7 100644
--- a/components/camel-kubernetes/src/main/docs/kubernetes-deployments-component.adoc
+++ b/components/camel-kubernetes/src/main/docs/kubernetes-deployments-component.adoc
@@ -15,7 +15,7 @@ provides a producer to execute kubernetes secret operations.
== Component Options
// component options: START
-The Kubernetes Deployments component supports 1 options, which are listed below.
+The Kubernetes Deployments component supports 3 options, which are listed below.
@@ -23,6 +23,8 @@ The Kubernetes Deployments component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -102,7 +104,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -110,7 +112,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.kubernetes-deployments.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.kubernetes-deployments.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.kubernetes-deployments.enabled* | Whether to enable auto configuration of the kubernetes-deployments component. This is enabled by default. | | Boolean
+| *camel.component.kubernetes-deployments.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-kubernetes/src/main/docs/kubernetes-hpa-component.adoc b/components/camel-kubernetes/src/main/docs/kubernetes-hpa-component.adoc
index 9cc6d25..01c4761 100644
--- a/components/camel-kubernetes/src/main/docs/kubernetes-hpa-component.adoc
+++ b/components/camel-kubernetes/src/main/docs/kubernetes-hpa-component.adoc
@@ -16,7 +16,7 @@ hpa events.
== Component Options
// component options: START
-The Kubernetes HPA component supports 1 options, which are listed below.
+The Kubernetes HPA component supports 3 options, which are listed below.
@@ -24,6 +24,8 @@ The Kubernetes HPA component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -103,7 +105,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -111,7 +113,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.kubernetes-hpa.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.kubernetes-hpa.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.kubernetes-hpa.enabled* | Whether to enable auto configuration of the kubernetes-hpa component. This is enabled by default. | | Boolean
+| *camel.component.kubernetes-hpa.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proce [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-kubernetes/src/main/docs/kubernetes-job-component.adoc b/components/camel-kubernetes/src/main/docs/kubernetes-job-component.adoc
index 4f322a9..cf1ef9f 100644
--- a/components/camel-kubernetes/src/main/docs/kubernetes-job-component.adoc
+++ b/components/camel-kubernetes/src/main/docs/kubernetes-job-component.adoc
@@ -15,7 +15,7 @@ provides a producer to execute kubernetes job operations.
== Component Options
// component options: START
-The Kubernetes Job component supports 1 options, which are listed below.
+The Kubernetes Job component supports 3 options, which are listed below.
@@ -23,6 +23,8 @@ The Kubernetes Job component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -102,7 +104,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -110,7 +112,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.kubernetes-job.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.kubernetes-job.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.kubernetes-job.enabled* | Whether to enable auto configuration of the kubernetes-job component. This is enabled by default. | | Boolean
+| *camel.component.kubernetes-job.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proce [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-kubernetes/src/main/docs/kubernetes-namespaces-component.adoc b/components/camel-kubernetes/src/main/docs/kubernetes-namespaces-component.adoc
index 22796c9..d554f3c 100644
--- a/components/camel-kubernetes/src/main/docs/kubernetes-namespaces-component.adoc
+++ b/components/camel-kubernetes/src/main/docs/kubernetes-namespaces-component.adoc
@@ -16,7 +16,7 @@ kubernetes namespace events.
== Component Options
// component options: START
-The Kubernetes Namespaces component supports 1 options, which are listed below.
+The Kubernetes Namespaces component supports 3 options, which are listed below.
@@ -24,6 +24,8 @@ The Kubernetes Namespaces component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -103,7 +105,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -111,7 +113,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.kubernetes-namespaces.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.kubernetes-namespaces.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.kubernetes-namespaces.enabled* | Whether to enable auto configuration of the kubernetes-namespaces component. This is enabled by default. | | Boolean
+| *camel.component.kubernetes-namespaces.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message i [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-kubernetes/src/main/docs/kubernetes-nodes-component.adoc b/components/camel-kubernetes/src/main/docs/kubernetes-nodes-component.adoc
index 93a4a3a..3f26a9b 100644
--- a/components/camel-kubernetes/src/main/docs/kubernetes-nodes-component.adoc
+++ b/components/camel-kubernetes/src/main/docs/kubernetes-nodes-component.adoc
@@ -16,7 +16,7 @@ node events.
== Component Options
// component options: START
-The Kubernetes Nodes component supports 1 options, which are listed below.
+The Kubernetes Nodes component supports 3 options, which are listed below.
@@ -24,6 +24,8 @@ The Kubernetes Nodes component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -103,7 +105,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -111,7 +113,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.kubernetes-nodes.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.kubernetes-nodes.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.kubernetes-nodes.enabled* | Whether to enable auto configuration of the kubernetes-nodes component. This is enabled by default. | | Boolean
+| *camel.component.kubernetes-nodes.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is pro [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-kubernetes/src/main/docs/kubernetes-persistent-volumes-claims-component.adoc b/components/camel-kubernetes/src/main/docs/kubernetes-persistent-volumes-claims-component.adoc
index 16f1c84..e7e3049 100644
--- a/components/camel-kubernetes/src/main/docs/kubernetes-persistent-volumes-claims-component.adoc
+++ b/components/camel-kubernetes/src/main/docs/kubernetes-persistent-volumes-claims-component.adoc
@@ -15,7 +15,7 @@ provides a producer to execute kubernetes persistent volume claim operations.
== Component Options
// component options: START
-The Kubernetes Persistent Volume Claim component supports 1 options, which are listed below.
+The Kubernetes Persistent Volume Claim component supports 3 options, which are listed below.
@@ -23,6 +23,8 @@ The Kubernetes Persistent Volume Claim component supports 1 options, which are l
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -94,7 +96,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -102,7 +104,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.kubernetes-persistent-volumes-claims.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.kubernetes-persistent-volumes-claims.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | f [...]
| *camel.component.kubernetes-persistent-volumes-claims.enabled* | Whether to enable auto configuration of the kubernetes-persistent-volumes-claims component. This is enabled by default. | | Boolean
+| *camel.component.kubernetes-persistent-volumes-claims.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-kubernetes/src/main/docs/kubernetes-persistent-volumes-component.adoc b/components/camel-kubernetes/src/main/docs/kubernetes-persistent-volumes-component.adoc
index 3d2e7a5..47b1837 100644
--- a/components/camel-kubernetes/src/main/docs/kubernetes-persistent-volumes-component.adoc
+++ b/components/camel-kubernetes/src/main/docs/kubernetes-persistent-volumes-component.adoc
@@ -15,7 +15,7 @@ provides a producer to execute kubernetes persistent volume operations.
== Component Options
// component options: START
-The Kubernetes Persistent Volume component supports 1 options, which are listed below.
+The Kubernetes Persistent Volume component supports 3 options, which are listed below.
@@ -23,6 +23,8 @@ The Kubernetes Persistent Volume component supports 1 options, which are listed
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -94,7 +96,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -102,7 +104,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.kubernetes-persistent-volumes.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.kubernetes-persistent-volumes.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.kubernetes-persistent-volumes.enabled* | Whether to enable auto configuration of the kubernetes-persistent-volumes component. This is enabled by default. | | Boolean
+| *camel.component.kubernetes-persistent-volumes.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first m [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-kubernetes/src/main/docs/kubernetes-pods-component.adoc b/components/camel-kubernetes/src/main/docs/kubernetes-pods-component.adoc
index 8c5f6d3..a66e849 100644
--- a/components/camel-kubernetes/src/main/docs/kubernetes-pods-component.adoc
+++ b/components/camel-kubernetes/src/main/docs/kubernetes-pods-component.adoc
@@ -15,7 +15,7 @@ provides a producer to execute kubernetes pod operations.
== Component Options
// component options: START
-The Kubernetes Pods component supports 1 options, which are listed below.
+The Kubernetes Pods component supports 3 options, which are listed below.
@@ -23,6 +23,8 @@ The Kubernetes Pods component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -102,7 +104,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -110,7 +112,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.kubernetes-pods.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.kubernetes-pods.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.kubernetes-pods.enabled* | Whether to enable auto configuration of the kubernetes-pods component. This is enabled by default. | | Boolean
+| *camel.component.kubernetes-pods.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proc [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-kubernetes/src/main/docs/kubernetes-replication-controllers-component.adoc b/components/camel-kubernetes/src/main/docs/kubernetes-replication-controllers-component.adoc
index 5650a7b..df83154 100644
--- a/components/camel-kubernetes/src/main/docs/kubernetes-replication-controllers-component.adoc
+++ b/components/camel-kubernetes/src/main/docs/kubernetes-replication-controllers-component.adoc
@@ -16,7 +16,7 @@ consume kubernetes replication controller events.
== Component Options
// component options: START
-The Kubernetes Replication Controller component supports 1 options, which are listed below.
+The Kubernetes Replication Controller component supports 3 options, which are listed below.
@@ -24,6 +24,8 @@ The Kubernetes Replication Controller component supports 1 options, which are li
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -103,7 +105,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -111,7 +113,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.kubernetes-replication-controllers.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.kubernetes-replication-controllers.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | fal [...]
| *camel.component.kubernetes-replication-controllers.enabled* | Whether to enable auto configuration of the kubernetes-replication-controllers component. This is enabled by default. | | Boolean
+| *camel.component.kubernetes-replication-controllers.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the fi [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-kubernetes/src/main/docs/kubernetes-resources-quota-component.adoc b/components/camel-kubernetes/src/main/docs/kubernetes-resources-quota-component.adoc
index 2e4bbc8..f8b586d 100644
--- a/components/camel-kubernetes/src/main/docs/kubernetes-resources-quota-component.adoc
+++ b/components/camel-kubernetes/src/main/docs/kubernetes-resources-quota-component.adoc
@@ -15,7 +15,7 @@ provides a producer to execute kubernetes resource quota operations.
== Component Options
// component options: START
-The Kubernetes Resources Quota component supports 1 options, which are listed below.
+The Kubernetes Resources Quota component supports 3 options, which are listed below.
@@ -23,6 +23,8 @@ The Kubernetes Resources Quota component supports 1 options, which are listed be
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -94,7 +96,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -102,7 +104,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.kubernetes-resources-quota.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.kubernetes-resources-quota.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.kubernetes-resources-quota.enabled* | Whether to enable auto configuration of the kubernetes-resources-quota component. This is enabled by default. | | Boolean
+| *camel.component.kubernetes-resources-quota.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first mess [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-kubernetes/src/main/docs/kubernetes-secrets-component.adoc b/components/camel-kubernetes/src/main/docs/kubernetes-secrets-component.adoc
index a4a2e37..eaede11 100644
--- a/components/camel-kubernetes/src/main/docs/kubernetes-secrets-component.adoc
+++ b/components/camel-kubernetes/src/main/docs/kubernetes-secrets-component.adoc
@@ -15,7 +15,7 @@ provides a producer to execute kubernetes secret operations.
== Component Options
// component options: START
-The Kubernetes Secrets component supports 1 options, which are listed below.
+The Kubernetes Secrets component supports 3 options, which are listed below.
@@ -23,6 +23,8 @@ The Kubernetes Secrets component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -94,7 +96,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -102,7 +104,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.kubernetes-secrets.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.kubernetes-secrets.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.kubernetes-secrets.enabled* | Whether to enable auto configuration of the kubernetes-secrets component. This is enabled by default. | | Boolean
+| *camel.component.kubernetes-secrets.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is p [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-kubernetes/src/main/docs/kubernetes-service-accounts-component.adoc b/components/camel-kubernetes/src/main/docs/kubernetes-service-accounts-component.adoc
index 1f34251..eb0d115 100644
--- a/components/camel-kubernetes/src/main/docs/kubernetes-service-accounts-component.adoc
+++ b/components/camel-kubernetes/src/main/docs/kubernetes-service-accounts-component.adoc
@@ -14,7 +14,7 @@ provides a producer to execute kubernetes Service Account operations.
== Component Options
// component options: START
-The Kubernetes Service Account component supports 1 options, which are listed below.
+The Kubernetes Service Account component supports 3 options, which are listed below.
@@ -22,6 +22,8 @@ The Kubernetes Service Account component supports 1 options, which are listed be
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -92,7 +94,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -100,7 +102,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.kubernetes-service-accounts.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.kubernetes-service-accounts.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.kubernetes-service-accounts.enabled* | Whether to enable auto configuration of the kubernetes-service-accounts component. This is enabled by default. | | Boolean
+| *camel.component.kubernetes-service-accounts.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first mes [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-kubernetes/src/main/docs/kubernetes-services-component.adoc b/components/camel-kubernetes/src/main/docs/kubernetes-services-component.adoc
index 408489b..128455b 100644
--- a/components/camel-kubernetes/src/main/docs/kubernetes-services-component.adoc
+++ b/components/camel-kubernetes/src/main/docs/kubernetes-services-component.adoc
@@ -16,7 +16,7 @@ service events.
== Component Options
// component options: START
-The Kubernetes Services component supports 1 options, which are listed below.
+The Kubernetes Services component supports 3 options, which are listed below.
@@ -24,6 +24,8 @@ The Kubernetes Services component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -103,7 +105,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -111,7 +113,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.kubernetes-services.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.kubernetes-services.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.kubernetes-services.enabled* | Whether to enable auto configuration of the kubernetes-services component. This is enabled by default. | | Boolean
+| *camel.component.kubernetes-services.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-kubernetes/src/main/docs/openshift-build-configs-component.adoc b/components/camel-kubernetes/src/main/docs/openshift-build-configs-component.adoc
index 16c3493..add7241 100644
--- a/components/camel-kubernetes/src/main/docs/openshift-build-configs-component.adoc
+++ b/components/camel-kubernetes/src/main/docs/openshift-build-configs-component.adoc
@@ -14,7 +14,7 @@ provides a producer to execute kubernetes build config operations.
== Component Options
// component options: START
-The Openshift Build Config component supports 1 options, which are listed below.
+The Openshift Build Config component supports 3 options, which are listed below.
@@ -22,6 +22,8 @@ The Openshift Build Config component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
diff --git a/components/camel-kubernetes/src/main/docs/openshift-builds-component.adoc b/components/camel-kubernetes/src/main/docs/openshift-builds-component.adoc
index d823ecc..40ae9c2 100644
--- a/components/camel-kubernetes/src/main/docs/openshift-builds-component.adoc
+++ b/components/camel-kubernetes/src/main/docs/openshift-builds-component.adoc
@@ -14,7 +14,7 @@ provides a producer to execute kubernetes build operations.
== Component Options
// component options: START
-The Openshift Builds component supports 1 options, which are listed below.
+The Openshift Builds component supports 3 options, which are listed below.
@@ -22,6 +22,8 @@ The Openshift Builds component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
diff --git a/components/camel-kudu/src/main/docs/kudu-component.adoc b/components/camel-kudu/src/main/docs/kudu-component.adoc
index 4811f7e..356bf8b 100644
--- a/components/camel-kudu/src/main/docs/kudu-component.adoc
+++ b/components/camel-kudu/src/main/docs/kudu-component.adoc
@@ -18,7 +18,7 @@ You must have a valid Kudu instance running. More information are available at h
// component options: START
-The Kudu component supports 1 options, which are listed below.
+The Kudu component supports 3 options, which are listed below.
@@ -26,6 +26,8 @@ The Kudu component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
diff --git a/components/camel-language/src/main/docs/language-component.adoc b/components/camel-language/src/main/docs/language-component.adoc
index 1d056c9..3797d69 100644
--- a/components/camel-language/src/main/docs/language-component.adoc
+++ b/components/camel-language/src/main/docs/language-component.adoc
@@ -41,7 +41,7 @@ language://languageName:resource:scheme:location][?options]
// component options: START
-The Language component supports 1 options, which are listed below.
+The Language component supports 3 options, which are listed below.
@@ -49,6 +49,8 @@ The Language component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -107,7 +109,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -115,7 +117,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.language.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.language.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.language.enabled* | Whether to enable auto configuration of the language component. This is enabled by default. | | Boolean
+| *camel.component.language.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed t [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-ldap/src/main/docs/ldap-component.adoc b/components/camel-ldap/src/main/docs/ldap-component.adoc
index b7ab3d6..acc5c3a 100644
--- a/components/camel-ldap/src/main/docs/ldap-component.adoc
+++ b/components/camel-ldap/src/main/docs/ldap-component.adoc
@@ -45,7 +45,7 @@ You can append query options to the URI in the following format,
// component options: START
-The LDAP component supports 1 options, which are listed below.
+The LDAP component supports 3 options, which are listed below.
@@ -53,6 +53,8 @@ The LDAP component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -109,7 +111,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -117,7 +119,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.ldap.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.ldap.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.ldap.enabled* | Enable ldap component | true | Boolean
+| *camel.component.ldap.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-ldif/src/main/docs/ldif-component.adoc b/components/camel-ldif/src/main/docs/ldif-component.adoc
index 4a56797..25b9cfe 100644
--- a/components/camel-ldif/src/main/docs/ldif-component.adoc
+++ b/components/camel-ldif/src/main/docs/ldif-component.adoc
@@ -54,7 +54,7 @@ You can append query options to the URI in the following format,
== Options
// component options: START
-The LDIF component supports 1 options, which are listed below.
+The LDIF component supports 3 options, which are listed below.
@@ -62,6 +62,8 @@ The LDIF component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -111,7 +113,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -119,7 +121,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.ldif.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.ldif.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.ldif.enabled* | Whether to enable auto configuration of the ldif component. This is enabled by default. | | Boolean
+| *camel.component.ldif.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-log/src/main/docs/log-component.adoc b/components/camel-log/src/main/docs/log-component.adoc
index ccb5671..6883f0c 100644
--- a/components/camel-log/src/main/docs/log-component.adoc
+++ b/components/camel-log/src/main/docs/log-component.adoc
@@ -63,7 +63,7 @@ LogEIP.
// component options: START
-The Log component supports 2 options, which are listed below.
+The Log component supports 4 options, which are listed below.
@@ -72,6 +72,8 @@ The Log component supports 2 options, which are listed below.
| Name | Description | Default | Type
| *exchangeFormatter* (advanced) | Sets a custom ExchangeFormatter to convert the Exchange to a String suitable for logging. If not specified, we default to DefaultExchangeFormatter. | | ExchangeFormatter
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -150,7 +152,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 3 options, which are listed below.
+The component supports 5 options, which are listed below.
@@ -158,8 +160,10 @@ The component supports 3 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.log.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.log.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.log.enabled* | Whether to enable auto configuration of the log component. This is enabled by default. | | Boolean
| *camel.component.log.exchange-formatter* | Sets a custom ExchangeFormatter to convert the Exchange to a String suitable for logging. If not specified, we default to DefaultExchangeFormatter. The option is a org.apache.camel.spi.ExchangeFormatter type. | | String
+| *camel.component.log.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then c [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-lucene/src/main/docs/lucene-component.adoc b/components/camel-lucene/src/main/docs/lucene-component.adoc
index 7311822..f9d7467 100644
--- a/components/camel-lucene/src/main/docs/lucene-component.adoc
+++ b/components/camel-lucene/src/main/docs/lucene-component.adoc
@@ -56,7 +56,7 @@ You can append query options to the URI in the following format,
// component options: START
-The Lucene component supports 2 options, which are listed below.
+The Lucene component supports 4 options, which are listed below.
@@ -65,6 +65,8 @@ The Lucene component supports 2 options, which are listed below.
| Name | Description | Default | Type
| *config* (advanced) | To use a shared lucene configuration | | LuceneConfiguration
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -125,7 +127,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 11 options, which are listed below.
+The component supports 13 options, which are listed below.
@@ -133,6 +135,7 @@ The component supports 11 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.lucene.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.lucene.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.lucene.config.analyzer* | An Analyzer builds TokenStreams, which analyze text. It thus represents a policy for extracting index terms from text. The value for analyzer can be any class that extends the abstract class org.apache.lucene.analysis.Analyzer. Lucene also offers a rich set of analyzers out of the box | | Analyzer
| *camel.component.lucene.config.authority* | Operation to do such as insert or query. | | String
| *camel.component.lucene.config.host* | The URL to the lucene server | | String
@@ -143,6 +146,7 @@ The component supports 11 options, which are listed below.
| *camel.component.lucene.config.src-dir* | An optional directory containing files to be used to be analyzed and added to the index at producer startup. | | File
| *camel.component.lucene.config.uri* | | | URI
| *camel.component.lucene.enabled* | Enable lucene component | true | Boolean
+| *camel.component.lucene.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed the [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-lumberjack/src/main/docs/lumberjack-component.adoc b/components/camel-lumberjack/src/main/docs/lumberjack-component.adoc
index 7e4ba51..ab213c3 100644
--- a/components/camel-lumberjack/src/main/docs/lumberjack-component.adoc
+++ b/components/camel-lumberjack/src/main/docs/lumberjack-component.adoc
@@ -42,7 +42,7 @@ You can append query options to the URI in the following format,
// component options: START
-The Lumberjack component supports 3 options, which are listed below.
+The Lumberjack component supports 5 options, which are listed below.
@@ -52,6 +52,8 @@ The Lumberjack component supports 3 options, which are listed below.
| *sslContextParameters* (security) | Sets the default SSL configuration to use for all the endpoints. You can also configure it directly at the endpoint level. | | SSLContextParameters
| *useGlobalSslContext Parameters* (security) | Enable usage of global SSL context parameters. | false | boolean
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -111,7 +113,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 4 options, which are listed below.
+The component supports 6 options, which are listed below.
@@ -119,7 +121,9 @@ The component supports 4 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.lumberjack.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.lumberjack.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.lumberjack.enabled* | Enable lumberjack component | true | Boolean
+| *camel.component.lumberjack.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed [...]
| *camel.component.lumberjack.ssl-context-parameters* | Sets the default SSL configuration to use for all the endpoints. You can also configure it directly at the endpoint level. The option is a org.apache.camel.support.jsse.SSLContextParameters type. | | String
| *camel.component.lumberjack.use-global-ssl-context-parameters* | Enable usage of global SSL context parameters. | false | Boolean
|===
diff --git a/components/camel-mail/src/main/docs/mail-component.adoc b/components/camel-mail/src/main/docs/mail-component.adoc
index 57cd24e..0a7e8bb 100644
--- a/components/camel-mail/src/main/docs/mail-component.adoc
+++ b/components/camel-mail/src/main/docs/mail-component.adoc
@@ -93,7 +93,7 @@ You can append query options to the URI in the following format,
// component options: START
-The Mail component supports 5 options, which are listed below.
+The Mail component supports 7 options, which are listed below.
@@ -105,6 +105,8 @@ The Mail component supports 5 options, which are listed below.
| *useGlobalSslContext Parameters* (security) | Enable usage of global SSL context parameters. | false | boolean
| *headerFilterStrategy* (filter) | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. | | HeaderFilterStrategy
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -221,7 +223,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 48 options, which are listed below.
+The component supports 50 options, which are listed below.
@@ -229,6 +231,7 @@ The component supports 48 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.mail.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.mail.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.mail.configuration.additional-java-mail-properties* | Sets additional java mail properties, that will append/override any default properties that is set based on all the other options. This is useful if you need to add some special options but want to keep the others as is. | | Properties
| *camel.component.mail.configuration.alternative-body-header* | Specifies the key to an IN message header that contains an alternative email body. For example, if you send emails in text/html format and want to provide an alternative mail body for non-HTML email clients, set the alternative mail body with this key as a header. | CamelMailAlternativeBody | String
| *camel.component.mail.configuration.attachments-content-transfer-encoding-resolver* | To use a custom AttachmentsContentTransferEncodingResolver to resolve what content-type-encoding to use for attachments. | | AttachmentsContentTransferEncodingResolver
@@ -268,6 +271,7 @@ The component supports 48 options, which are listed below.
| *camel.component.mail.content-type-resolver* | Resolver to determine Content-Type for file attachments. The option is a org.apache.camel.component.mail.ContentTypeResolver type. | | String
| *camel.component.mail.enabled* | Enable mail component | true | Boolean
| *camel.component.mail.header-filter-strategy* | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. The option is a org.apache.camel.spi.HeaderFilterStrategy type. | | String
+| *camel.component.mail.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
| *camel.component.mail.use-global-ssl-context-parameters* | Enable usage of global SSL context parameters. | false | Boolean
| *camel.dataformat.mime-multipart.binary-content* | Defines whether the content of binary parts in the MIME multipart is binary (true) or Base-64 encoded (false) Default is false. | false | Boolean
| *camel.dataformat.mime-multipart.content-type-header* | Whether the data format should set the Content-Type header with the type from the data format if the data format is capable of doing so. For example application/xml for data formats marshalling to XML, or application/json for data formats marshalling to JSon etc. | false | Boolean
diff --git a/components/camel-master/src/main/docs/master-component.adoc b/components/camel-master/src/main/docs/master-component.adoc
index 25d77c8..0d51fa9 100644
--- a/components/camel-master/src/main/docs/master-component.adoc
+++ b/components/camel-master/src/main/docs/master-component.adoc
@@ -38,7 +38,7 @@ Where endpoint is any Camel endpoint you want to run in master/slave mode.
== Options
// component options: START
-The Master component supports 3 options, which are listed below.
+The Master component supports 5 options, which are listed below.
@@ -48,6 +48,8 @@ The Master component supports 3 options, which are listed below.
| *service* (advanced) | Inject the service to use. | | CamelClusterService
| *serviceSelector* (advanced) | Inject the service selector used to lookup the CamelClusterService to use. | | Selector
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -100,7 +102,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 4 options, which are listed below.
+The component supports 6 options, which are listed below.
@@ -108,7 +110,9 @@ The component supports 4 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.master.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.master.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.master.enabled* | Whether to enable auto configuration of the master component. This is enabled by default. | | Boolean
+| *camel.component.master.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed the [...]
| *camel.component.master.service* | Inject the service to use. The option is a org.apache.camel.cluster.CamelClusterService type. | | String
| *camel.component.master.service-selector* | Inject the service selector used to lookup the CamelClusterService to use. The option is a org.apache.camel.cluster.CamelClusterService.Selector type. | | String
|===
diff --git a/components/camel-metrics/src/main/docs/metrics-component.adoc b/components/camel-metrics/src/main/docs/metrics-component.adoc
index b44e1cd..3025289 100644
--- a/components/camel-metrics/src/main/docs/metrics-component.adoc
+++ b/components/camel-metrics/src/main/docs/metrics-component.adoc
@@ -40,7 +40,7 @@ metrics:[ meter | counter | histogram | timer | gauge ]:metricname[?options]
== Options
// component options: START
-The Metrics component supports 2 options, which are listed below.
+The Metrics component supports 4 options, which are listed below.
@@ -49,6 +49,8 @@ The Metrics component supports 2 options, which are listed below.
| Name | Description | Default | Type
| *metricRegistry* (advanced) | To use a custom configured MetricRegistry. | | MetricRegistry
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -106,7 +108,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 3 options, which are listed below.
+The component supports 5 options, which are listed below.
@@ -114,7 +116,9 @@ The component supports 3 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.metrics.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.metrics.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.metrics.enabled* | Enable metrics component | true | Boolean
+| *camel.component.metrics.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
| *camel.component.metrics.metric-registry* | To use a custom configured MetricRegistry. The option is a com.codahale.metrics.MetricRegistry type. | | String
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-micrometer/src/main/docs/micrometer-component.adoc b/components/camel-micrometer/src/main/docs/micrometer-component.adoc
index 375586f..b56bfce 100644
--- a/components/camel-micrometer/src/main/docs/micrometer-component.adoc
+++ b/components/camel-micrometer/src/main/docs/micrometer-component.adoc
@@ -43,7 +43,7 @@ micrometer:[ counter | summary | timer ]:metricname[?options]
== Options
// component options: START
-The Micrometer component supports 2 options, which are listed below.
+The Micrometer component supports 4 options, which are listed below.
@@ -52,6 +52,8 @@ The Micrometer component supports 2 options, which are listed below.
| Name | Description | Default | Type
| *metricsRegistry* (advanced) | To use a custom configured MetricRegistry. | | MeterRegistry
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -108,7 +110,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 3 options, which are listed below.
+The component supports 5 options, which are listed below.
@@ -116,7 +118,9 @@ The component supports 3 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.micrometer.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.micrometer.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.micrometer.enabled* | Whether to enable auto configuration of the micrometer component. This is enabled by default. | | Boolean
+| *camel.component.micrometer.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed [...]
| *camel.component.micrometer.metrics-registry* | To use a custom configured MetricRegistry. The option is a io.micrometer.core.instrument.MeterRegistry type. | | String
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-microprofile-metrics/src/main/docs/microprofile-metrics-component.adoc b/components/camel-microprofile-metrics/src/main/docs/microprofile-metrics-component.adoc
index ca71156..8b20df1 100644
--- a/components/camel-microprofile-metrics/src/main/docs/microprofile-metrics-component.adoc
+++ b/components/camel-microprofile-metrics/src/main/docs/microprofile-metrics-component.adoc
@@ -33,7 +33,7 @@ microprofile-metrics:[ concurrent gauge | counter | gauge | histogram | meter |
== Options
// component options: START
-The MicroProfile Metrics component supports 2 options, which are listed below.
+The MicroProfile Metrics component supports 4 options, which are listed below.
@@ -42,6 +42,8 @@ The MicroProfile Metrics component supports 2 options, which are listed below.
| Name | Description | Default | Type
| *metricRegistry* (advanced) | Use a custom MetricRegistry. | | MetricRegistry
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
diff --git a/components/camel-milo/src/main/docs/milo-client-component.adoc b/components/camel-milo/src/main/docs/milo-client-component.adoc
index 91d0d6f..9ad005c 100644
--- a/components/camel-milo/src/main/docs/milo-client-component.adoc
+++ b/components/camel-milo/src/main/docs/milo-client-component.adoc
@@ -26,7 +26,7 @@ for this component:
// component options: START
-The OPC UA Client component supports 6 options, which are listed below.
+The OPC UA Client component supports 8 options, which are listed below.
@@ -39,6 +39,8 @@ The OPC UA Client component supports 6 options, which are listed below.
| *productUri* (common) | Default product URI | | String
| *reconnectTimeout* (common) | Default reconnect timeout | | Long
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -154,7 +156,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 25 options, which are listed below.
+The component supports 27 options, which are listed below.
@@ -164,6 +166,7 @@ The component supports 25 options, which are listed below.
| *camel.component.milo-client.application-name* | Default application name | | String
| *camel.component.milo-client.application-uri* | Default application URI | | String
| *camel.component.milo-client.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.milo-client.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.milo-client.default-configuration.allowed-security-policies* | A set of allowed security policy URIs. Default is to accept all and use the highest. | | Set
| *camel.component.milo-client.default-configuration.application-name* | The application name | Apache Camel adapter for Eclipse Milo | String
| *camel.component.milo-client.default-configuration.application-uri* | The application URI | http://camel.apache.org/EclipseMilo/Client | String
@@ -184,6 +187,7 @@ The component supports 25 options, which are listed below.
| *camel.component.milo-client.default-configuration.session-name* | Session name | | String
| *camel.component.milo-client.default-configuration.session-timeout* | Session timeout in milliseconds | | Long
| *camel.component.milo-client.enabled* | Enable milo-client component | true | Boolean
+| *camel.component.milo-client.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processe [...]
| *camel.component.milo-client.product-uri* | Default product URI | | String
| *camel.component.milo-client.reconnect-timeout* | Default reconnect timeout | | Long
|===
diff --git a/components/camel-milo/src/main/docs/milo-server-component.adoc b/components/camel-milo/src/main/docs/milo-server-component.adoc
index 7aa6303..f4d16c1 100644
--- a/components/camel-milo/src/main/docs/milo-server-component.adoc
+++ b/components/camel-milo/src/main/docs/milo-server-component.adoc
@@ -30,7 +30,7 @@ Value write requests from OPC UA Client will trigger messages which are sent int
// component options: START
-The OPC UA Server component supports 20 options, which are listed below.
+The OPC UA Server component supports 22 options, which are listed below.
@@ -57,6 +57,8 @@ The OPC UA Server component supports 20 options, which are listed below.
| *certificateValidator* (common) | Validator for client certificates | | Supplier
| *defaultCertificate Validator* (common) | Validator for client certificates using default file based approach | | File
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -128,7 +130,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 21 options, which are listed below.
+The component supports 23 options, which are listed below.
@@ -140,6 +142,7 @@ The component supports 21 options, which are listed below.
| *camel.component.milo-server.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
| *camel.component.milo-server.bind-addresses* | Set the addresses of the local addresses the server should bind to | | String
| *camel.component.milo-server.bind-port* | The TCP port the server binds to | | Integer
+| *camel.component.milo-server.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.milo-server.build-info* | Server build info. The option is a org.eclipse.milo.opcua.stack.core.types.structured.BuildInfo type. | | String
| *camel.component.milo-server.certificate-manager* | Server certificate manager. The option is a org.eclipse.milo.opcua.stack.core.application.CertificateManager type. | | String
| *camel.component.milo-server.certificate-validator* | Validator for client certificates. The option is a java.util.function.Supplier<org.eclipse.milo.opcua.stack.core.application.CertificateValidator> type. | | String
@@ -147,6 +150,7 @@ The component supports 21 options, which are listed below.
| *camel.component.milo-server.enable-anonymous-authentication* | Enable anonymous authentication, disabled by default | false | Boolean
| *camel.component.milo-server.enabled* | Enable milo-server component | true | Boolean
| *camel.component.milo-server.hostname* | Server hostname | | String
+| *camel.component.milo-server.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processe [...]
| *camel.component.milo-server.namespace-uri* | The URI of the namespace, defaults to urn:org:apache:camel | | String
| *camel.component.milo-server.product-uri* | The product URI | | String
| *camel.component.milo-server.security-policies* | Security policies | | Set
diff --git a/components/camel-mina/src/main/docs/mina-component.adoc b/components/camel-mina/src/main/docs/mina-component.adoc
index adbdc49..1b793be 100644
--- a/components/camel-mina/src/main/docs/mina-component.adoc
+++ b/components/camel-mina/src/main/docs/mina-component.adoc
@@ -68,7 +68,7 @@ You can append query options to the URI in the following format,
// component options: START
-The Mina component supports 3 options, which are listed below.
+The Mina component supports 5 options, which are listed below.
@@ -78,6 +78,8 @@ The Mina component supports 3 options, which are listed below.
| *configuration* (advanced) | To use the shared mina configuration. | | MinaConfiguration
| *useGlobalSslContext Parameters* (security) | Enable usage of global SSL context parameters. | false | boolean
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -162,7 +164,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 29 options, which are listed below.
+The component supports 31 options, which are listed below.
@@ -170,6 +172,7 @@ The component supports 29 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.mina.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.mina.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.mina.configuration.allow-default-codec* | The mina component installs a default codec if both, codec is null and textline is false. Setting allowDefaultCodec to false prevents the mina component from installing a default codec as the first element in the filter chain. This is useful in scenarios where another filter must be the first in the filter chain, like the SSL filter. | true | Boolean
| *camel.component.mina.configuration.auto-start-tls* | Whether to auto start SSL handshake. | true | Boolean
| *camel.component.mina.configuration.cached-address* | Whether to create the InetAddress once and reuse. Setting this to false allows to pickup DNS changes in the network. | true | Boolean
@@ -197,6 +200,7 @@ The component supports 29 options, which are listed below.
| *camel.component.mina.configuration.transfer-exchange* | Only used for TCP. You can transfer the exchange over the wire instead of just the body. 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. | false | Boolean
| *camel.component.mina.configuration.write-timeout* | Maximum amount of time it should take to send data to the MINA session. Default is 10000 milliseconds. | 10000 | Long
| *camel.component.mina.enabled* | Whether to enable auto configuration of the mina component. This is enabled by default. | | Boolean
+| *camel.component.mina.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
| *camel.component.mina.use-global-ssl-context-parameters* | Enable usage of global SSL context parameters. | false | Boolean
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-mllp/src/main/docs/mllp-component.adoc b/components/camel-mllp/src/main/docs/mllp-component.adoc
index 8fc1d26..373cdd5 100644
--- a/components/camel-mllp/src/main/docs/mllp-component.adoc
+++ b/components/camel-mllp/src/main/docs/mllp-component.adoc
@@ -45,7 +45,7 @@ for this component:
// component options: START
-The MLLP component supports 5 options, which are listed below.
+The MLLP component supports 7 options, which are listed below.
@@ -57,6 +57,8 @@ The MLLP component supports 5 options, which are listed below.
| *defaultCharset* (advanced) | Set the default character set to use for byte to/from String conversions. | ISO-8859-1 | String
| *configuration* (common) | Sets the default configuration to use when creating MLLP endpoints. | | MllpConfiguration
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -140,7 +142,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 31 options, which are listed below.
+The component supports 33 options, which are listed below.
@@ -148,6 +150,7 @@ The component supports 31 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.mllp.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.mllp.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.mllp.configuration.accept-timeout* | Timeout (in milliseconds) while waiting for a TCP connection <p/> TCP Server Only | 60000 | Integer
| *camel.component.mllp.configuration.auto-ack* | Enable/Disable the automatic generation of a MLLP Acknowledgement MLLP Consumers only | true | Boolean
| *camel.component.mllp.configuration.backlog* | The maximum queue length for incoming connection indications (a request to connect) is set to the backlog parameter. If a connection indication arrives when the queue is full, the connection is refused. | 5 | Integer
@@ -174,6 +177,7 @@ The component supports 31 options, which are listed below.
| *camel.component.mllp.configuration.validate-payload* | Enable/Disable the validation of HL7 Payloads If enabled, HL7 Payloads received from external systems will be validated (see Hl7Util.generateInvalidPayloadExceptionMessage for details on the validation). If and invalid payload is detected, a MllpInvalidMessageException (for consumers) or a MllpInvalidAcknowledgementException will be thrown. | false | Boolean
| *camel.component.mllp.default-charset* | Set the default character set to use for byte to/from String conversions. | ISO-8859-1 | String
| *camel.component.mllp.enabled* | Enable mllp component | true | Boolean
+| *camel.component.mllp.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
| *camel.component.mllp.log-phi* | Set the component to log PHI data. | true | Boolean
| *camel.component.mllp.log-phi-max-bytes* | Set the maximum number of bytes of PHI that will be logged in a log entry. | 5120 | Integer
| *camel.component.mllp.configuration.buffer-writes* | *Deprecated* Enable/Disable the buffering of HL7 payloads before writing to the socket. | false | Boolean
diff --git a/components/camel-mock/src/main/docs/mock-component.adoc b/components/camel-mock/src/main/docs/mock-component.adoc
index d07013f..9c31975 100644
--- a/components/camel-mock/src/main/docs/mock-component.adoc
+++ b/components/camel-mock/src/main/docs/mock-component.adoc
@@ -80,7 +80,7 @@ You can append query options to the URI in the following format,
// component options: START
-The Mock component supports 1 options, which are listed below.
+The Mock component supports 3 options, which are listed below.
@@ -88,6 +88,8 @@ The Mock component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -153,7 +155,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -161,7 +163,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.mock.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.mock.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.mock.enabled* | Whether to enable auto configuration of the mock component. This is enabled by default. | | Boolean
+| *camel.component.mock.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-mongodb-gridfs/src/main/docs/mongodb-gridfs-component.adoc b/components/camel-mongodb-gridfs/src/main/docs/mongodb-gridfs-component.adoc
index 7fa1f7e..666a611 100644
--- a/components/camel-mongodb-gridfs/src/main/docs/mongodb-gridfs-component.adoc
+++ b/components/camel-mongodb-gridfs/src/main/docs/mongodb-gridfs-component.adoc
@@ -30,7 +30,7 @@ mongodb-gridfs:connectionBean?database=databaseName&bucket=bucketName[&moreOptio
// component options: START
-The MongoDB GridFS component supports 1 options, which are listed below.
+The MongoDB GridFS component supports 3 options, which are listed below.
@@ -38,6 +38,8 @@ The MongoDB GridFS component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -105,7 +107,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 2 options, which are listed below.
+The component supports 4 options, which are listed below.
@@ -113,7 +115,9 @@ The component supports 2 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.mongodb-gridfs.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.mongodb-gridfs.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.mongodb-gridfs.enabled* | Enable mongodb-gridfs component | true | Boolean
+| *camel.component.mongodb-gridfs.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is proce [...]
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-mongodb/src/main/docs/mongodb-component.adoc b/components/camel-mongodb/src/main/docs/mongodb-component.adoc
index f86e033..d12d587 100644
--- a/components/camel-mongodb/src/main/docs/mongodb-component.adoc
+++ b/components/camel-mongodb/src/main/docs/mongodb-component.adoc
@@ -58,7 +58,7 @@ mongodb:connectionBean?database=databaseName&collection=collectionName&operation
// component options: START
-The MongoDB component supports 2 options, which are listed below.
+The MongoDB component supports 4 options, which are listed below.
@@ -67,6 +67,8 @@ The MongoDB component supports 2 options, which are listed below.
| Name | Description | Default | Type
| *mongoConnection* (common) | Set a client used for connection: all endpoints generated from the component will share this connection bean. | | MongoClient
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -142,7 +144,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 3 options, which are listed below.
+The component supports 5 options, which are listed below.
@@ -150,7 +152,9 @@ The component supports 3 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.mongodb.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.mongodb.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.mongodb.enabled* | Whether to enable auto configuration of the mongodb component. This is enabled by default. | | Boolean
+| *camel.component.mongodb.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
| *camel.component.mongodb.mongo-connection* | Set a client used for connection: all endpoints generated from the component will share this connection bean. The option is a com.mongodb.MongoClient type. | | String
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-msv/src/main/docs/msv-component.adoc b/components/camel-msv/src/main/docs/msv-component.adoc
index f5de05f..bd06a64 100644
--- a/components/camel-msv/src/main/docs/msv-component.adoc
+++ b/components/camel-msv/src/main/docs/msv-component.adoc
@@ -56,7 +56,7 @@ You can append query options to the URI in the following format,
// component options: START
-The MSV component supports 3 options, which are listed below.
+The MSV component supports 5 options, which are listed below.
@@ -66,6 +66,8 @@ The MSV component supports 3 options, which are listed below.
| *schemaFactory* (advanced) | To use the javax.xml.validation.SchemaFactory. | | SchemaFactory
| *resourceResolverFactory* (advanced) | To use a custom LSResourceResolver which depends on a dynamic endpoint resource URI | | ValidatorResourceResolverFactory
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -129,7 +131,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 4 options, which are listed below.
+The component supports 6 options, which are listed below.
@@ -137,7 +139,9 @@ The component supports 4 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.msv.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.msv.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.msv.enabled* | Enable msv component | true | Boolean
+| *camel.component.msv.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then c [...]
| *camel.component.msv.resource-resolver-factory* | To use a custom LSResourceResolver which depends on a dynamic endpoint resource URI. The option is a org.apache.camel.component.validator.ValidatorResourceResolverFactory type. | | String
| *camel.component.msv.schema-factory* | To use the javax.xml.validation.SchemaFactory. The option is a javax.xml.validation.SchemaFactory type. | | String
|===
diff --git a/components/camel-mustache/src/main/docs/mustache-component.adoc b/components/camel-mustache/src/main/docs/mustache-component.adoc
index 08230c0..9f68dd8 100644
--- a/components/camel-mustache/src/main/docs/mustache-component.adoc
+++ b/components/camel-mustache/src/main/docs/mustache-component.adoc
@@ -42,7 +42,7 @@ You can append query options to the URI in the following format,
// component options: START
-The Mustache component supports 2 options, which are listed below.
+The Mustache component supports 4 options, which are listed below.
@@ -51,6 +51,8 @@ The Mustache component supports 2 options, which are listed below.
| Name | Description | Default | Type
| *mustacheFactory* (advanced) | To use a custom MustacheFactory | | MustacheFactory
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -111,7 +113,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 3 options, which are listed below.
+The component supports 5 options, which are listed below.
@@ -119,7 +121,9 @@ The component supports 3 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.mustache.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.mustache.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.mustache.enabled* | Enable mustache component | true | Boolean
+| *camel.component.mustache.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed t [...]
| *camel.component.mustache.mustache-factory* | To use a custom MustacheFactory. The option is a com.github.mustachejava.MustacheFactory type. | | String
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-mvel/src/main/docs/mvel-component.adoc b/components/camel-mvel/src/main/docs/mvel-component.adoc
index 8853644..b1907e9 100644
--- a/components/camel-mvel/src/main/docs/mvel-component.adoc
+++ b/components/camel-mvel/src/main/docs/mvel-component.adoc
@@ -42,7 +42,7 @@ You can append query options to the URI in the following format,
// component options: START
-The MVEL component supports 1 options, which are listed below.
+The MVEL component supports 3 options, which are listed below.
@@ -50,6 +50,8 @@ The MVEL component supports 1 options, which are listed below.
|===
| Name | Description | Default | Type
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -104,7 +106,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 4 options, which are listed below.
+The component supports 6 options, which are listed below.
@@ -112,7 +114,9 @@ The component supports 4 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.mvel.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.mvel.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.mvel.enabled* | Enable mvel component | true | Boolean
+| *camel.component.mvel.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
| *camel.language.mvel.enabled* | Enable mvel language | true | Boolean
| *camel.language.mvel.trim* | Whether to trim the value to remove leading and trailing whitespaces and line breaks | true | Boolean
|===
diff --git a/components/camel-mvel/src/main/docs/mvel-language.adoc b/components/camel-mvel/src/main/docs/mvel-language.adoc
index f28458d..2fcec39 100644
--- a/components/camel-mvel/src/main/docs/mvel-language.adoc
+++ b/components/camel-mvel/src/main/docs/mvel-language.adoc
@@ -52,7 +52,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 4 options, which are listed below.
+The component supports 6 options, which are listed below.
@@ -60,7 +60,9 @@ The component supports 4 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.mvel.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.mvel.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.mvel.enabled* | Enable mvel component | true | Boolean
+| *camel.component.mvel.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
| *camel.language.mvel.enabled* | Enable mvel language | true | Boolean
| *camel.language.mvel.trim* | Whether to trim the value to remove leading and trailing whitespaces and line breaks | true | Boolean
|===
diff --git a/components/camel-mybatis/src/main/docs/mybatis-bean-component.adoc b/components/camel-mybatis/src/main/docs/mybatis-bean-component.adoc
index 6fd1e19..466bfd1 100644
--- a/components/camel-mybatis/src/main/docs/mybatis-bean-component.adoc
+++ b/components/camel-mybatis/src/main/docs/mybatis-bean-component.adoc
@@ -35,7 +35,7 @@ the `configurationUri` option on the `MyBatisComponent` component.
== Options
// component options: START
-The MyBatis Bean component supports 3 options, which are listed below.
+The MyBatis Bean component supports 5 options, which are listed below.
@@ -45,6 +45,8 @@ The MyBatis Bean component supports 3 options, which are listed below.
| *sqlSessionFactory* (advanced) | To use the SqlSessionFactory | | SqlSessionFactory
| *configurationUri* (producer) | Location of MyBatis xml configuration file. The default value is: SqlMapConfig.xml loaded from the classpath | SqlMapConfig.xml | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -99,7 +101,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 4 options, which are listed below.
+The component supports 6 options, which are listed below.
@@ -107,8 +109,10 @@ The component supports 4 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.mybatis-bean.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.mybatis-bean.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.mybatis-bean.configuration-uri* | Location of MyBatis xml configuration file. The default value is: SqlMapConfig.xml loaded from the classpath | SqlMapConfig.xml | String
| *camel.component.mybatis-bean.enabled* | Whether to enable auto configuration of the mybatis-bean component. This is enabled by default. | | Boolean
+| *camel.component.mybatis-bean.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is process [...]
| *camel.component.mybatis-bean.sql-session-factory* | To use the SqlSessionFactory. The option is a org.apache.ibatis.session.SqlSessionFactory type. | | String
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-mybatis/src/main/docs/mybatis-component.adoc b/components/camel-mybatis/src/main/docs/mybatis-component.adoc
index 943235a..3078334 100644
--- a/components/camel-mybatis/src/main/docs/mybatis-component.adoc
+++ b/components/camel-mybatis/src/main/docs/mybatis-component.adoc
@@ -46,7 +46,7 @@ the `configurationUri` option on the `MyBatisComponent` component.
== Options
// component options: START
-The MyBatis component supports 3 options, which are listed below.
+The MyBatis component supports 5 options, which are listed below.
@@ -56,6 +56,8 @@ The MyBatis component supports 3 options, which are listed below.
| *sqlSessionFactory* (advanced) | To use the SqlSessionFactory | | SqlSessionFactory
| *configurationUri* (common) | Location of MyBatis xml configuration file. The default value is: SqlMapConfig.xml loaded from the classpath | SqlMapConfig.xml | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -135,7 +137,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 4 options, which are listed below.
+The component supports 6 options, which are listed below.
@@ -143,8 +145,10 @@ The component supports 4 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.mybatis.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.mybatis.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.mybatis.configuration-uri* | Location of MyBatis xml configuration file. The default value is: SqlMapConfig.xml loaded from the classpath | SqlMapConfig.xml | String
| *camel.component.mybatis.enabled* | Enable mybatis component | true | Boolean
+| *camel.component.mybatis.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed th [...]
| *camel.component.mybatis.sql-session-factory* | To use the SqlSessionFactory. The option is a org.apache.ibatis.session.SqlSessionFactory type. | | String
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-nagios/src/main/docs/nagios-component.adoc b/components/camel-nagios/src/main/docs/nagios-component.adoc
index d824407..b84b297 100644
--- a/components/camel-nagios/src/main/docs/nagios-component.adoc
+++ b/components/camel-nagios/src/main/docs/nagios-component.adoc
@@ -43,7 +43,7 @@ you to send notifications to Nagios.
// component options: START
-The Nagios component supports 2 options, which are listed below.
+The Nagios component supports 4 options, which are listed below.
@@ -52,6 +52,8 @@ The Nagios component supports 2 options, which are listed below.
| Name | Description | Default | Type
| *configuration* (advanced) | To use a shared NagiosConfiguration | | NagiosConfiguration
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -114,7 +116,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 10 options, which are listed below.
+The component supports 12 options, which are listed below.
@@ -122,6 +124,7 @@ The component supports 10 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.nagios.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.nagios.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.nagios.configuration.connection-timeout* | Connection timeout in millis. | 5000 | Integer
| *camel.component.nagios.configuration.encryption* | To specify an encryption method. | | Encryption
| *camel.component.nagios.configuration.host* | This is the address of the Nagios host where checks should be send. | | String
@@ -130,6 +133,7 @@ The component supports 10 options, which are listed below.
| *camel.component.nagios.configuration.port* | The port number of the host. | | Integer
| *camel.component.nagios.configuration.timeout* | Sending timeout in millis. | 5000 | Integer
| *camel.component.nagios.enabled* | Enable nagios component | true | Boolean
+| *camel.component.nagios.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed the [...]
| *camel.component.nagios.configuration.encryption-method* | *Deprecated* To specify an encryption method. | | NagiosEncryptionMethod
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-nats/src/main/docs/nats-component.adoc b/components/camel-nats/src/main/docs/nats-component.adoc
index 106a247..bd663ee 100644
--- a/components/camel-nats/src/main/docs/nats-component.adoc
+++ b/components/camel-nats/src/main/docs/nats-component.adoc
@@ -35,7 +35,7 @@ Where *servers* represents the list of NATS servers.
// component options: START
-The Nats component supports 2 options, which are listed below.
+The Nats component supports 4 options, which are listed below.
@@ -44,6 +44,8 @@ The Nats component supports 2 options, which are listed below.
| Name | Description | Default | Type
| *useGlobalSslContext Parameters* (security) | Enable usage of global SSL context parameters. | false | boolean
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -121,7 +123,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
-The component supports 3 options, which are listed below.
+The component supports 5 options, which are listed below.
@@ -129,7 +131,9 @@ The component supports 3 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.nats.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
+| *camel.component.nats.bridge-error-handler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean
| *camel.component.nats.enabled* | Enable nats component | true | Boolean
+| *camel.component.nats.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...]
| *camel.component.nats.use-global-ssl-context-parameters* | Enable usage of global SSL context parameters. | false | Boolean
|===
// spring-boot-auto-configure options: END
diff --git a/components/camel-netty-http/src/main/docs/netty-http-component.adoc b/components/camel-netty-http/src/main/docs/netty-http-component.adoc
index b3b2550..bcd4c1d 100644
--- a/components/camel-netty-http/src/main/docs/netty-http-component.adoc
+++ b/components/camel-netty-http/src/main/docs/netty-http-component.adoc
@@ -92,7 +92,7 @@ related to UDP transport.
// component options: START
-The Netty HTTP component supports 9 options, which are listed below.
+The Netty HTTP component supports 11 options, which are listed below.
@@ -108,6 +108,8 @@ The Netty HTTP component supports 9 options, which are listed below.
| *executorService* (advanced) | To use the given EventExecutorGroup. | | EventExecutorGroup
| *sslContextParameters* (security) | To configure security using SSLContextParameters | | SSLContextParameters
| *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
|===
// component options: END
@@ -245,7 +247,7 @@ When using Spring Boot make sure to use the following Maven dependency to have s
----
... 33307 lines suppressed ...
[camel] 01/03: CAMEL-14169: Make it easier to configure global
endpoint options once
Posted by da...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git
commit 1e1134834d9d03e8c11b260e59e434d950903888
Author: Claus Ibsen <cl...@gmail.com>
AuthorDate: Tue Nov 12 09:52:31 2019 +0100
CAMEL-14169: Make it easier to configure global endpoint options once
---
.../main/java/org/apache/camel/CamelContext.java | 5 ++
.../apache/camel/GlobalEndpointConfiguration.java | 53 +++++++++++++
.../camel/impl/engine/AbstractCamelContext.java | 7 ++
.../engine/DefaultGlobalEndpointConfiguration.java | 56 ++++++++++++++
.../apache/camel/impl/LazyStartProducerTest.java | 31 ++++++++
.../camel/main/DefaultConfigurationConfigurer.java | 5 ++
.../camel/main/DefaultConfigurationProperties.java | 88 ++++++++++++++++++++++
.../org/apache/camel/support/DefaultComponent.java | 65 +++++++++++++++-
.../org/apache/camel/support/DefaultEndpoint.java | 6 +-
9 files changed, 310 insertions(+), 6 deletions(-)
diff --git a/core/camel-api/src/main/java/org/apache/camel/CamelContext.java b/core/camel-api/src/main/java/org/apache/camel/CamelContext.java
index 1eb0633..cfe73b5 100644
--- a/core/camel-api/src/main/java/org/apache/camel/CamelContext.java
+++ b/core/camel-api/src/main/java/org/apache/camel/CamelContext.java
@@ -504,6 +504,11 @@ public interface CamelContext extends StatefulService, RuntimeConfiguration {
*/
Collection<Endpoint> removeEndpoints(String pattern) throws Exception;
+ /**
+ * Gets the global endpoint configuration, where you can configure common endpoint options.
+ */
+ GlobalEndpointConfiguration getGlobalEndpointConfiguration();
+
// Route Management Methods
//-----------------------------------------------------------------------
diff --git a/core/camel-api/src/main/java/org/apache/camel/GlobalEndpointConfiguration.java b/core/camel-api/src/main/java/org/apache/camel/GlobalEndpointConfiguration.java
new file mode 100644
index 0000000..77705fe
--- /dev/null
+++ b/core/camel-api/src/main/java/org/apache/camel/GlobalEndpointConfiguration.java
@@ -0,0 +1,53 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.camel;
+
+/**
+ * Global endpoint configurations which can be set as defaults when Camel creates new {@link Endpoint}s.
+ */
+public interface GlobalEndpointConfiguration {
+
+ boolean isLazyStartProducer();
+
+ /**
+ * Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup
+ * in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy 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 producer may take a little time and prolong the total processing time of the processing.
+ */
+ void setLazyStartProducer(boolean lazyStartProducer);
+
+ boolean isBridgeErrorHandler();
+
+ /**
+ * 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.
+ * <p/>
+ * By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions,
+ * that will be logged at WARN/ERROR level and ignored.
+ */
+ void setBridgeErrorHandler(boolean bridgeErrorHandler);
+
+ boolean isBasicPropertyBinding();
+
+ /**
+ * Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities.
+ */
+ void setBasicPropertyBinding(boolean basicPropertyBinding);
+
+}
diff --git a/core/camel-base/src/main/java/org/apache/camel/impl/engine/AbstractCamelContext.java b/core/camel-base/src/main/java/org/apache/camel/impl/engine/AbstractCamelContext.java
index 69e0453..9c3681c 100644
--- a/core/camel-base/src/main/java/org/apache/camel/impl/engine/AbstractCamelContext.java
+++ b/core/camel-base/src/main/java/org/apache/camel/impl/engine/AbstractCamelContext.java
@@ -54,6 +54,7 @@ import org.apache.camel.ExtendedCamelContext;
import org.apache.camel.ExtendedStartupListener;
import org.apache.camel.FailedToStartRouteException;
import org.apache.camel.FluentProducerTemplate;
+import org.apache.camel.GlobalEndpointConfiguration;
import org.apache.camel.IsSingleton;
import org.apache.camel.MultipleConsumersSupport;
import org.apache.camel.NoFactoryAvailableException;
@@ -173,6 +174,7 @@ public abstract class AbstractCamelContext extends ServiceSupport implements Ext
private ClassLoader applicationContextClassLoader;
private final AtomicInteger endpointKeyCounter = new AtomicInteger();
private final List<EndpointStrategy> endpointStrategies = new ArrayList<>();
+ private final GlobalEndpointConfiguration globalEndpointConfiguration = new DefaultGlobalEndpointConfiguration();
private final Map<String, Component> components = new ConcurrentHashMap<>();
private final Set<Route> routes = new LinkedHashSet<>();
private final List<Service> servicesToStop = new CopyOnWriteArrayList<>();
@@ -1024,6 +1026,11 @@ public abstract class AbstractCamelContext extends ServiceSupport implements Ext
}
}
+ @Override
+ public GlobalEndpointConfiguration getGlobalEndpointConfiguration() {
+ return globalEndpointConfiguration;
+ }
+
// Route Management Methods
// -----------------------------------------------------------------------
diff --git a/core/camel-base/src/main/java/org/apache/camel/impl/engine/DefaultGlobalEndpointConfiguration.java b/core/camel-base/src/main/java/org/apache/camel/impl/engine/DefaultGlobalEndpointConfiguration.java
new file mode 100644
index 0000000..129db24
--- /dev/null
+++ b/core/camel-base/src/main/java/org/apache/camel/impl/engine/DefaultGlobalEndpointConfiguration.java
@@ -0,0 +1,56 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.camel.impl.engine;
+
+import org.apache.camel.GlobalEndpointConfiguration;
+
+public final class DefaultGlobalEndpointConfiguration implements GlobalEndpointConfiguration {
+
+ private boolean lazyStartProducer;
+ private boolean bridgeErrorHandler;
+ private boolean basicPropertyBinding;
+
+ @Override
+ public boolean isLazyStartProducer() {
+ return lazyStartProducer;
+ }
+
+ @Override
+ public void setLazyStartProducer(boolean lazyStartProducer) {
+ this.lazyStartProducer = lazyStartProducer;
+ }
+
+ @Override
+ public boolean isBridgeErrorHandler() {
+ return bridgeErrorHandler;
+ }
+
+ @Override
+ public void setBridgeErrorHandler(boolean bridgeErrorHandler) {
+ this.bridgeErrorHandler = bridgeErrorHandler;
+ }
+
+ @Override
+ public boolean isBasicPropertyBinding() {
+ return basicPropertyBinding;
+ }
+
+ @Override
+ public void setBasicPropertyBinding(boolean basicPropertyBinding) {
+ this.basicPropertyBinding = basicPropertyBinding;
+ }
+}
diff --git a/core/camel-core/src/test/java/org/apache/camel/impl/LazyStartProducerTest.java b/core/camel-core/src/test/java/org/apache/camel/impl/LazyStartProducerTest.java
index f6c0749..d62c629 100644
--- a/core/camel-core/src/test/java/org/apache/camel/impl/LazyStartProducerTest.java
+++ b/core/camel-core/src/test/java/org/apache/camel/impl/LazyStartProducerTest.java
@@ -18,7 +18,10 @@ package org.apache.camel.impl;
import org.apache.camel.ContextTestSupport;
import org.apache.camel.Exchange;
+import org.apache.camel.component.log.LogComponent;
+import org.apache.camel.component.log.LogEndpoint;
import org.apache.camel.component.mock.MockEndpoint;
+import org.apache.camel.support.DefaultEndpoint;
import org.apache.camel.support.LazyStartProducer;
import org.apache.camel.support.service.ServiceHelper;
import org.junit.Test;
@@ -65,4 +68,32 @@ public class LazyStartProducerTest extends ContextTestSupport {
assertMockEndpointsSatisfied();
}
+
+ @Test
+ public void lazyStartProducerGlobal() throws Exception {
+ context.getGlobalEndpointConfiguration().setLazyStartProducer(true);
+
+ MockEndpoint mock = getMockEndpoint("mock:result");
+ assertTrue(mock.isLazyStartProducer());
+
+ LogEndpoint log = getMandatoryEndpoint("log:foo", LogEndpoint.class);
+ assertTrue(log.isLazyStartProducer());
+ }
+
+ @Test
+ public void lazyStartProducerComponent() throws Exception {
+ context.getComponent("log", LogComponent.class).setLazyStartProducer(true);
+
+ LogEndpoint log = getMandatoryEndpoint("log:foo", LogEndpoint.class);
+ assertTrue(log.isLazyStartProducer());
+
+ // but mock is false
+ MockEndpoint mock = getMockEndpoint("mock:result");
+ assertFalse(mock.isLazyStartProducer());
+
+ // but we can override this via parameter
+ MockEndpoint mock2 = getMockEndpoint("mock:foo?lazyStartProducer=true");
+ assertTrue(mock2.isLazyStartProducer());
+ }
+
}
diff --git a/core/camel-main/src/main/java/org/apache/camel/main/DefaultConfigurationConfigurer.java b/core/camel-main/src/main/java/org/apache/camel/main/DefaultConfigurationConfigurer.java
index d0b889d..9b21acc 100644
--- a/core/camel-main/src/main/java/org/apache/camel/main/DefaultConfigurationConfigurer.java
+++ b/core/camel-main/src/main/java/org/apache/camel/main/DefaultConfigurationConfigurer.java
@@ -156,6 +156,11 @@ public final class DefaultConfigurationConfigurer {
camelContext.getManagementStrategy().getManagementAgent().setCreateConnector(config.isJmxCreateConnector());
}
+ // global endpoint configurations
+ camelContext.getGlobalEndpointConfiguration().setBasicPropertyBinding(config.isEndpointBasicPropertyBinding());
+ camelContext.getGlobalEndpointConfiguration().setBridgeErrorHandler(config.isEndpointBridgeErrorHandler());
+ camelContext.getGlobalEndpointConfiguration().setLazyStartProducer(config.isEndpointLazyStartProducer());
+
camelContext.setBacklogTracing(config.isBacklogTracing());
camelContext.setTracing(config.isTracing());
camelContext.setTracingPattern(config.getTracingPattern());
diff --git a/core/camel-main/src/main/java/org/apache/camel/main/DefaultConfigurationProperties.java b/core/camel-main/src/main/java/org/apache/camel/main/DefaultConfigurationProperties.java
index c90aa66..7d2c955 100644
--- a/core/camel-main/src/main/java/org/apache/camel/main/DefaultConfigurationProperties.java
+++ b/core/camel-main/src/main/java/org/apache/camel/main/DefaultConfigurationProperties.java
@@ -59,6 +59,9 @@ public abstract class DefaultConfigurationProperties<T> {
private boolean autoStartup = true;
private boolean allowUseOriginalMessage;
private boolean endpointRuntimeStatisticsEnabled;
+ private boolean endpointLazyStartProducer;
+ private boolean endpointBridgeErrorHandler;
+ private boolean endpointBasicPropertyBinding;
private boolean useDataType;
private boolean useBreadcrumb;
private ManagementStatisticsLevel jmxManagementStatisticsLevel = ManagementStatisticsLevel.Default;
@@ -521,6 +524,53 @@ public abstract class DefaultConfigurationProperties<T> {
this.endpointRuntimeStatisticsEnabled = endpointRuntimeStatisticsEnabled;
}
+ public boolean isEndpointLazyStartProducer() {
+ return endpointLazyStartProducer;
+ }
+
+ /**
+ * Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup
+ * in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy 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 producer may take a little time and prolong the total processing time of the processing.
+ *
+ * The default value is false.
+ */
+ public void setEndpointLazyStartProducer(boolean endpointLazyStartProducer) {
+ this.endpointLazyStartProducer = endpointLazyStartProducer;
+ }
+
+ public boolean isEndpointBridgeErrorHandler() {
+ return endpointBridgeErrorHandler;
+ }
+
+ /**
+ * 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.
+ * <p/>
+ * By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions,
+ * that will be logged at WARN/ERROR level and ignored.
+ *
+ * The default value is false.
+ */
+ public void setEndpointBridgeErrorHandler(boolean endpointBridgeErrorHandler) {
+ this.endpointBridgeErrorHandler = endpointBridgeErrorHandler;
+ }
+
+ public boolean isEndpointBasicPropertyBinding() {
+ return endpointBasicPropertyBinding;
+ }
+
+ /**
+ * Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities.
+ *
+ * The default value is false.
+ */
+ public void setEndpointBasicPropertyBinding(boolean endpointBasicPropertyBinding) {
+ this.endpointBasicPropertyBinding = endpointBasicPropertyBinding;
+ }
+
public boolean isUseDataType() {
return useDataType;
}
@@ -1137,6 +1187,44 @@ public abstract class DefaultConfigurationProperties<T> {
}
/**
+ * Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup
+ * in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy 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 producer may take a little time and prolong the total processing time of the processing.
+ *
+ * The default value is false.
+ */
+ public T withEndpointLazyStartProducer(boolean endpointLazyStartProducer) {
+ this.endpointLazyStartProducer = endpointLazyStartProducer;
+ return (T) this;
+ }
+
+ /**
+ * 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.
+ * <p/>
+ * By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions,
+ * that will be logged at WARN/ERROR level and ignored.
+ *
+ * The default value is false.
+ */
+ public T withEndpointBridgeErrorHandler(boolean endpointBridgeErrorHandler) {
+ this.endpointBridgeErrorHandler = endpointBridgeErrorHandler;
+ return (T) this;
+ }
+
+ /**
+ * Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities.
+ *
+ * The default value is false.
+ */
+ public T withEndpointBasicPropertyBinding(boolean endpointBasicPropertyBinding) {
+ this.endpointBasicPropertyBinding = endpointBasicPropertyBinding;
+ return (T) this;
+ }
+
+ /**
* Whether to enable using data type on Camel messages.
*
* Data type are automatic turned on if one ore more routes has been explicit configured with input and output types.
diff --git a/core/camel-support/src/main/java/org/apache/camel/support/DefaultComponent.java b/core/camel-support/src/main/java/org/apache/camel/support/DefaultComponent.java
index 723c48e..2e707ff 100644
--- a/core/camel-support/src/main/java/org/apache/camel/support/DefaultComponent.java
+++ b/core/camel-support/src/main/java/org/apache/camel/support/DefaultComponent.java
@@ -67,6 +67,16 @@ public abstract class DefaultComponent extends ServiceSupport implements Compone
@Metadata(label = "advanced",
description = "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities")
private boolean basicPropertyBinding;
+ @Metadata(label = "consumer", 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.")
+ private boolean bridgeErrorHandler;
+ @Metadata(label = "producer",
+ 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 producer may take a little time and prolong the total processing time of the processing.")
+ private boolean lazyStartProducer;
public DefaultComponent() {
}
@@ -211,12 +221,31 @@ public abstract class DefaultComponent extends ServiceSupport implements Compone
// inject camel context
endpoint.setCamelContext(getCamelContext());
- // setup whether to use basic property binding or not which must be done before we set properties
- boolean basic = getAndRemoveParameter(parameters, "basicPropertyBinding", boolean.class, basicPropertyBinding);
+ // setup global options
if (endpoint instanceof DefaultEndpoint) {
- ((DefaultEndpoint) endpoint).setBasicPropertyBinding(basic);
+ DefaultEndpoint de = (DefaultEndpoint) endpoint;
+ de.setBasicPropertyBinding(getCamelContext().getGlobalEndpointConfiguration().isBasicPropertyBinding());;
+ de.setBridgeErrorHandler(getCamelContext().getGlobalEndpointConfiguration().isBridgeErrorHandler());;
+ de.setLazyStartProducer(getCamelContext().getGlobalEndpointConfiguration().isLazyStartProducer());;
+ }
+
+ // setup global options which must be done before we set properties
+ if (endpoint instanceof DefaultEndpoint) {
+ DefaultEndpoint de = (DefaultEndpoint) endpoint;
+ boolean defaultBasic = basicPropertyBinding ? basicPropertyBinding : getCamelContext().getGlobalEndpointConfiguration().isBasicPropertyBinding();
+ boolean basic = getAndRemoveParameter(parameters, "basicPropertyBinding", boolean.class, defaultBasic);
+ de.setBasicPropertyBinding(basic);
+
+ boolean defaultBridge = bridgeErrorHandler ? bridgeErrorHandler : getCamelContext().getGlobalEndpointConfiguration().isBridgeErrorHandler();
+ boolean bridge = getAndRemoveParameter(parameters, "bridgeErrorHandler", boolean.class, defaultBridge);
+ de.setBridgeErrorHandler(bridge);
+
+ boolean defaultLazy = lazyStartProducer ? lazyStartProducer : getCamelContext().getGlobalEndpointConfiguration().isLazyStartProducer();
+ boolean lazy = getAndRemoveParameter(parameters, "lazyStartProducer", boolean.class, defaultLazy);
+ de.setLazyStartProducer(lazy);
}
+ // configure parameters
endpoint.configureProperties(parameters);
if (useIntrospectionOnEndpoint()) {
setProperties(endpoint, parameters);
@@ -252,6 +281,36 @@ public abstract class DefaultComponent extends ServiceSupport implements Compone
this.basicPropertyBinding = basicPropertyBinding;
}
+ public boolean isLazyStartProducer() {
+ return lazyStartProducer;
+ }
+
+ /**
+ * Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup
+ * in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then
+ * the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed
+ * then creating and starting the producer may take a little time and prolong the total processing time of the processing.
+ */
+ public void setLazyStartProducer(boolean lazyStartProducer) {
+ this.lazyStartProducer = lazyStartProducer;
+ }
+
+ public boolean isBridgeErrorHandler() {
+ return bridgeErrorHandler;
+ }
+
+ /**
+ * Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while
+ * the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and
+ * handled by the routing Error Handler.
+ * <p/>
+ * By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions,
+ * that will be logged at WARN/ERROR level and ignored.
+ */
+ public void setBridgeErrorHandler(boolean bridgeErrorHandler) {
+ this.bridgeErrorHandler = bridgeErrorHandler;
+ }
+
/**
* Strategy to do post configuration logic.
* <p/>
diff --git a/core/camel-support/src/main/java/org/apache/camel/support/DefaultEndpoint.java b/core/camel-support/src/main/java/org/apache/camel/support/DefaultEndpoint.java
index c796dd8..c32a403 100644
--- a/core/camel-support/src/main/java/org/apache/camel/support/DefaultEndpoint.java
+++ b/core/camel-support/src/main/java/org/apache/camel/support/DefaultEndpoint.java
@@ -61,7 +61,7 @@ public abstract class DefaultEndpoint extends ServiceSupport implements Endpoint
+ " 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 producer may take a little time and prolong the total processing time of the processing.")
private boolean lazyStartProducer;
- @UriParam(label = "consumer", optionalPrefix = "consumer.", description = "Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while"
+ @UriParam(label = "consumer", 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.")
private boolean bridgeErrorHandler;
@@ -311,8 +311,8 @@ public abstract class DefaultEndpoint extends ServiceSupport implements Endpoint
/**
* To let the consumer use a custom ExceptionHandler.
- + Notice if the option bridgeErrorHandler is enabled then this options is not in use.
- + By default the consumer will deal with exceptions, that will be logged at WARN/ERROR level and ignored.
+ * Notice if the option bridgeErrorHandler is enabled then this options is not in use.
+ * By default the consumer will deal with exceptions, that will be logged at WARN/ERROR level and ignored.
*/
public void setExceptionHandler(ExceptionHandler exceptionHandler) {
this.exceptionHandler = exceptionHandler;
[camel] 02/03: Remove deprecated and not in use interface
Posted by da...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git
commit 88ca3343ff67e53b4d3f5c9d90254f5ea02c5290
Author: Claus Ibsen <cl...@gmail.com>
AuthorDate: Tue Nov 12 09:53:04 2019 +0100
Remove deprecated and not in use interface
---
.../camel/spi/EndpointPropertyConfigurer.java | 35 ----------------------
1 file changed, 35 deletions(-)
diff --git a/core/camel-api/src/main/java/org/apache/camel/spi/EndpointPropertyConfigurer.java b/core/camel-api/src/main/java/org/apache/camel/spi/EndpointPropertyConfigurer.java
deleted file mode 100644
index feb01e2..0000000
--- a/core/camel-api/src/main/java/org/apache/camel/spi/EndpointPropertyConfigurer.java
+++ /dev/null
@@ -1,35 +0,0 @@
-/*
- * Licensed to the Apache Software Foundation (ASF) under one or more
- * contributor license agreements. See the NOTICE file distributed with
- * this work for additional information regarding copyright ownership.
- * The ASF licenses this file to You under the Apache License, Version 2.0
- * (the "License"); you may not use this file except in compliance with
- * the License. You may obtain a copy of the License at
- *
- * http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS,
- * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- * See the License for the specific language governing permissions and
- * limitations under the License.
- */
-package org.apache.camel.spi;
-
-import org.apache.camel.CamelContext;
-
-/**
- * Property configurer for Camel {@link org.apache.camel.Endpoint}
- * which allows fast configurations without using Java reflection.
- */
-@Deprecated
-public interface EndpointPropertyConfigurer extends PropertyConfigurer {
-
- /**
- * Configures the endpoint.
- *
- * @param endpoint the endpoint
- * @param camelContext the camel context
- */
- void configure(Object endpoint, CamelContext camelContext);
-}