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-spring-boot.git


The following commit(s) were added to refs/heads/master by this push:
     new be6258d  Regen
be6258d is described below

commit be6258d9457cbafa7ff58610fbecf649f86d7882
Author: Claus Ibsen <claus.ib...@gmail.com>
AuthorDate: Mon Mar 2 07:35:56 2020 +0100

    Regen
---
 .../camel/springboot/catalog/components/kafka.json |  2 +-
 .../catalog/components/xmlsecurity-verify.json     |  2 +-
 .../springboot/KafkaComponentConfiguration.java    | 24 +++++++-------
 .../XmlVerifierComponentConfiguration.java         | 38 +++++++++++-----------
 docs/modules/ROOT/pages/activemq-starter.adoc      |  8 ++---
 docs/modules/ROOT/pages/amqp-starter.adoc          |  6 ++--
 docs/modules/ROOT/pages/stomp-starter.adoc         |  2 +-
 7 files changed, 41 insertions(+), 41 deletions(-)

diff --git 
a/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/kafka.json
 
b/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/kafka.json
index 450d57f..a6424ea 100644
--- 
a/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/kafka.json
+++ 
b/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/kafka.json
@@ -110,9 +110,9 @@
     "sslProtocol": { "kind": "property", "displayName": "Ssl Protocol", 
"group": "security", "label": "common,security", "required": false, "type": 
"string", "javaType": "java.lang.String", "deprecated": false, "secret": false, 
"defaultValue": "TLS", "configurationClass": 
"org.apache.camel.component.kafka.KafkaConfiguration", "configurationField": 
"configuration", "description": "The SSL protocol used to generate the 
SSLContext. Default setting is TLS, which is fine for most cases. Allow [...]
     "sslProvider": { "kind": "property", "displayName": "Ssl Provider", 
"group": "security", "label": "common,security", "required": false, "type": 
"string", "javaType": "java.lang.String", "deprecated": false, "secret": false, 
"configurationClass": "org.apache.camel.component.kafka.KafkaConfiguration", 
"configurationField": "configuration", "description": "The name of the security 
provider used for SSL connections. Default value is the default security 
provider of the JVM." },
     "sslTrustmanagerAlgorithm": { "kind": "property", "displayName": "Ssl 
Trustmanager Algorithm", "group": "security", "label": "common,security", 
"required": false, "type": "string", "javaType": "java.lang.String", 
"deprecated": false, "secret": false, "defaultValue": "PKIX", 
"configurationClass": "org.apache.camel.component.kafka.KafkaConfiguration", 
"configurationField": "configuration", "description": "The algorithm used by 
trust manager factory for SSL connections. Default value is [...]
+    "sslTruststoreLocation": { "kind": "property", "displayName": "Ssl 
Truststore Location", "group": "security", "label": "producer,security", 
"required": false, "type": "string", "javaType": "java.lang.String", 
"deprecated": false, "secret": false, "configurationClass": 
"org.apache.camel.component.kafka.KafkaConfiguration", "configurationField": 
"configuration", "description": "The location of the trust store file." },
     "sslTruststoreType": { "kind": "property", "displayName": "Ssl Truststore 
Type", "group": "security", "label": "common,security", "required": false, 
"type": "string", "javaType": "java.lang.String", "deprecated": false, 
"secret": false, "defaultValue": "JKS", "configurationClass": 
"org.apache.camel.component.kafka.KafkaConfiguration", "configurationField": 
"configuration", "description": "The file format of the trust store file. 
Default value is JKS." },
     "schemaRegistryURL": { "kind": "property", "displayName": "Schema Registry 
URL", "group": "confluent", "label": "confluent", "required": false, "type": 
"string", "javaType": "java.lang.String", "deprecated": false, "secret": false, 
"configurationClass": "org.apache.camel.component.kafka.KafkaConfiguration", 
"configurationField": "configuration", "description": "URL of the Confluent 
Platform schema registry servers to use. The format is host1:port1,host2:port2. 
This is known as schema [...]
-    "sslTruststoreLocation": { "kind": "property", "displayName": "Ssl 
Truststore Location", "group": "security", "label": "producer,security", 
"required": false, "type": "string", "javaType": "java.lang.String", 
"deprecated": false, "secret": false, "configurationClass": 
"org.apache.camel.component.kafka.KafkaConfiguration", "configurationField": 
"configuration", "description": "The location of the trust store file." },
     "sslTruststorePassword": { "kind": "property", "displayName": "Ssl 
Truststore Password", "group": "security", "label": "producer,security", 
"required": false, "type": "string", "javaType": "java.lang.String", 
"deprecated": false, "secret": true, "configurationClass": 
"org.apache.camel.component.kafka.KafkaConfiguration", "configurationField": 
"configuration", "description": "The password for the trust store file." },
     "useGlobalSslContextParameters": { "kind": "property", "displayName": "Use 
Global Ssl Context Parameters", "group": "security", "label": "security", 
"required": false, "type": "boolean", "javaType": "boolean", "deprecated": 
false, "secret": false, "defaultValue": "false", "description": "Enable usage 
of global SSL context parameters." }
   },
diff --git 
a/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/xmlsecurity-verify.json
 
b/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/xmlsecurity-verify.json
index 2085a9c..77ba69a 100644
--- 
a/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/xmlsecurity-verify.json
+++ 
b/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/xmlsecurity-verify.json
@@ -25,12 +25,12 @@
     "disallowDoctypeDecl": { "kind": "property", "displayName": "Disallow 
Doctype Decl", "group": "common", "label": "common", "required": false, "type": 
"boolean", "javaType": "java.lang.Boolean", "deprecated": false, "secret": 
false, "defaultValue": "true", "configurationClass": 
"org.apache.camel.component.xmlsecurity.processor.XmlVerifierConfiguration", 
"configurationField": "verifierConfiguration", "description": "Disallows that 
the incoming XML document contains DTD DOCTYPE declarat [...]
     "keySelector": { "kind": "property", "displayName": "Key Selector", 
"group": "producer", "label": "", "required": false, "type": "object", 
"javaType": "javax.xml.crypto.KeySelector", "deprecated": false, "secret": 
false, "configurationClass": 
"org.apache.camel.component.xmlsecurity.processor.XmlVerifierConfiguration", 
"configurationField": "verifierConfiguration", "description": "Provides the key 
for validating the XML signature." },
     "omitXmlDeclaration": { "kind": "property", "displayName": "Omit Xml 
Declaration", "group": "common", "label": "common", "required": false, "type": 
"boolean", "javaType": "java.lang.Boolean", "deprecated": false, "secret": 
false, "defaultValue": "false", "configurationClass": 
"org.apache.camel.component.xmlsecurity.processor.XmlVerifierConfiguration", 
"configurationField": "verifierConfiguration", "description": "Indicator 
whether the XML declaration in the outgoing message body shou [...]
+    "lazyStartProducer": { "kind": "property", "displayName": "Lazy Start 
Producer", "group": "producer", "label": "producer", "required": false, "type": 
"boolean", "javaType": "boolean", "deprecated": false, "secret": false, 
"defaultValue": false, "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 r [...]
     "outputNodeSearch": { "kind": "property", "displayName": "Output Node 
Search", "group": "producer", "label": "", "required": false, "type": "object", 
"javaType": "java.lang.Object", "deprecated": false, "secret": false, 
"configurationClass": 
"org.apache.camel.component.xmlsecurity.processor.XmlVerifierConfiguration", 
"configurationField": "verifierConfiguration", "description": "Sets the output 
node search value for determining the node from the XML signature document 
which shall be  [...]
     "outputNodeSearchType": { "kind": "property", "displayName": "Output Node 
Search Type", "group": "producer", "label": "", "required": false, "type": 
"string", "javaType": "java.lang.String", "deprecated": false, "secret": false, 
"defaultValue": "Default", "configurationClass": 
"org.apache.camel.component.xmlsecurity.processor.XmlVerifierConfiguration", 
"configurationField": "verifierConfiguration", "description": "Determines the 
search type for determining the output node which is se [...]
     "outputXmlEncoding": { "kind": "property", "displayName": "Output Xml 
Encoding", "group": "common", "label": "common", "required": false, "type": 
"string", "javaType": "java.lang.String", "deprecated": false, "secret": false, 
"configurationClass": 
"org.apache.camel.component.xmlsecurity.processor.XmlVerifierConfiguration", 
"configurationField": "verifierConfiguration", "description": "The character 
encoding of the resulting signed XML document. If null then the encoding of the 
origin [...]
     "removeSignatureElements": { "kind": "property", "displayName": "Remove 
Signature Elements", "group": "producer", "label": "", "required": false, 
"type": "boolean", "javaType": "java.lang.Boolean", "deprecated": false, 
"secret": false, "defaultValue": "false", "configurationClass": 
"org.apache.camel.component.xmlsecurity.processor.XmlVerifierConfiguration", 
"configurationField": "verifierConfiguration", "description": "Indicator 
whether the XML signature elements (elements with local [...]
     "schemaResourceUri": { "kind": "property", "displayName": "Schema Resource 
Uri", "group": "common", "label": "common", "required": false, "type": 
"string", "javaType": "java.lang.String", "deprecated": false, "secret": false, 
"configurationClass": 
"org.apache.camel.component.xmlsecurity.processor.XmlVerifierConfiguration", 
"configurationField": "verifierConfiguration", "description": "Classpath to the 
XML Schema. Must be specified in the detached XML Signature case for 
determining th [...]
-    "lazyStartProducer": { "kind": "property", "displayName": "Lazy Start 
Producer", "group": "producer", "label": "producer", "required": false, "type": 
"boolean", "javaType": "boolean", "deprecated": false, "secret": false, 
"defaultValue": false, "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 r [...]
     "secureValidation": { "kind": "property", "displayName": "Secure 
Validation", "group": "producer", "label": "", "required": false, "type": 
"boolean", "javaType": "java.lang.Boolean", "deprecated": false, "secret": 
false, "defaultValue": "true", "configurationClass": 
"org.apache.camel.component.xmlsecurity.processor.XmlVerifierConfiguration", 
"configurationField": "verifierConfiguration", "description": "Enables secure 
validation. If true then secure validation is enabled." },
     "validationFailedHandler": { "kind": "property", "displayName": 
"Validation Failed Handler", "group": "producer", "label": "", "required": 
false, "type": "object", "javaType": 
"org.apache.camel.component.xmlsecurity.api.ValidationFailedHandler", 
"deprecated": false, "secret": false, "configurationClass": 
"org.apache.camel.component.xmlsecurity.processor.XmlVerifierConfiguration", 
"configurationField": "verifierConfiguration", "description": "Handles the 
different validation failed si [...]
     "xmlSignature2Message": { "kind": "property", "displayName": "Xml 
Signature2 Message", "group": "producer", "label": "", "required": false, 
"type": "object", "javaType": 
"org.apache.camel.component.xmlsecurity.api.XmlSignature2Message", 
"deprecated": false, "secret": false, "configurationClass": 
"org.apache.camel.component.xmlsecurity.processor.XmlVerifierConfiguration", 
"configurationField": "verifierConfiguration", "description": "Bean which maps 
the XML signature to the output-mes [...]
diff --git 
a/components-starter/camel-kafka-starter/src/main/java/org/apache/camel/component/kafka/springboot/KafkaComponentConfiguration.java
 
b/components-starter/camel-kafka-starter/src/main/java/org/apache/camel/component/kafka/springboot/KafkaComponentConfiguration.java
index 4282393..9d9ea00 100644
--- 
a/components-starter/camel-kafka-starter/src/main/java/org/apache/camel/component/kafka/springboot/KafkaComponentConfiguration.java
+++ 
b/components-starter/camel-kafka-starter/src/main/java/org/apache/camel/component/kafka/springboot/KafkaComponentConfiguration.java
@@ -651,6 +651,10 @@ public class KafkaComponentConfiguration
      */
     private String sslTrustmanagerAlgorithm = "PKIX";
     /**
+     * The location of the trust store file.
+     */
+    private String sslTruststoreLocation;
+    /**
      * The file format of the trust store file. Default value is JKS.
      */
     private String sslTruststoreType = "JKS";
@@ -662,10 +666,6 @@ public class KafkaComponentConfiguration
      */
     private String schemaRegistryURL;
     /**
-     * The location of the trust store file.
-     */
-    private String sslTruststoreLocation;
-    /**
      * The password for the trust store file.
      */
     private String sslTruststorePassword;
@@ -1404,6 +1404,14 @@ public class KafkaComponentConfiguration
         this.sslTrustmanagerAlgorithm = sslTrustmanagerAlgorithm;
     }
 
+    public String getSslTruststoreLocation() {
+        return sslTruststoreLocation;
+    }
+
+    public void setSslTruststoreLocation(String sslTruststoreLocation) {
+        this.sslTruststoreLocation = sslTruststoreLocation;
+    }
+
     public String getSslTruststoreType() {
         return sslTruststoreType;
     }
@@ -1420,14 +1428,6 @@ public class KafkaComponentConfiguration
         this.schemaRegistryURL = schemaRegistryURL;
     }
 
-    public String getSslTruststoreLocation() {
-        return sslTruststoreLocation;
-    }
-
-    public void setSslTruststoreLocation(String sslTruststoreLocation) {
-        this.sslTruststoreLocation = sslTruststoreLocation;
-    }
-
     public String getSslTruststorePassword() {
         return sslTruststorePassword;
     }
diff --git 
a/components-starter/camel-xmlsecurity-starter/src/main/java/org/apache/camel/component/xmlsecurity/springboot/XmlVerifierComponentConfiguration.java
 
b/components-starter/camel-xmlsecurity-starter/src/main/java/org/apache/camel/component/xmlsecurity/springboot/XmlVerifierComponentConfiguration.java
index 5580f16..4b061b5 100644
--- 
a/components-starter/camel-xmlsecurity-starter/src/main/java/org/apache/camel/component/xmlsecurity/springboot/XmlVerifierComponentConfiguration.java
+++ 
b/components-starter/camel-xmlsecurity-starter/src/main/java/org/apache/camel/component/xmlsecurity/springboot/XmlVerifierComponentConfiguration.java
@@ -74,6 +74,17 @@ public class XmlVerifierComponentConfiguration
      */
     private Boolean omitXmlDeclaration = false;
     /**
+     * Whether the producer should be started lazy (on the first message). By
+     * starting lazy you can use this to allow CamelContext and routes to
+     * startup in situations where a producer may otherwise fail during 
starting
+     * and cause the route to fail being started. By deferring this startup to
+     * be lazy then 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 = false;
+    /**
      * Sets the output node search value for determining the node from the XML
      * signature document which shall be set to the output message body. The
      * class of the value depends on the type of the output node search. The
@@ -112,17 +123,6 @@ public class XmlVerifierComponentConfiguration
      */
     private String schemaResourceUri;
     /**
-     * Whether the producer should be started lazy (on the first message). By
-     * starting lazy you can use this to allow CamelContext and routes to
-     * startup in situations where a producer may otherwise fail during 
starting
-     * and cause the route to fail being started. By deferring this startup to
-     * be lazy then 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 = false;
-    /**
      * Enables secure validation. If true then secure validation is enabled.
      */
     private Boolean secureValidation = true;
@@ -240,6 +240,14 @@ public class XmlVerifierComponentConfiguration
         this.omitXmlDeclaration = omitXmlDeclaration;
     }
 
+    public Boolean getLazyStartProducer() {
+        return lazyStartProducer;
+    }
+
+    public void setLazyStartProducer(Boolean lazyStartProducer) {
+        this.lazyStartProducer = lazyStartProducer;
+    }
+
     public String getOutputNodeSearch() {
         return outputNodeSearch;
     }
@@ -280,14 +288,6 @@ public class XmlVerifierComponentConfiguration
         this.schemaResourceUri = schemaResourceUri;
     }
 
-    public Boolean getLazyStartProducer() {
-        return lazyStartProducer;
-    }
-
-    public void setLazyStartProducer(Boolean lazyStartProducer) {
-        this.lazyStartProducer = lazyStartProducer;
-    }
-
     public Boolean getSecureValidation() {
         return secureValidation;
     }
diff --git a/docs/modules/ROOT/pages/activemq-starter.adoc 
b/docs/modules/ROOT/pages/activemq-starter.adoc
index 103061a..d90a359 100644
--- a/docs/modules/ROOT/pages/activemq-starter.adoc
+++ b/docs/modules/ROOT/pages/activemq-starter.adoc
@@ -39,7 +39,7 @@ The component supports 100 options, which are listed below.
 | *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 |  | String
+| *camel.component.activemq.broker-url* | Sets the broker URL to use to 
connect to ActiveMQ |  | String
 | *camel.component.activemq.cache-level* | Sets the cache level by ID for the 
underlying JMS resources. See cacheLevelName option for more details. |  | 
Integer
 | *camel.component.activemq.cache-level-name* | Sets the cache level by name 
for the underlying JMS resources. Possible values are: CACHE_AUTO, 
CACHE_CONNECTION, CACHE_CONSUMER, CACHE_NONE, and CACHE_SESSION. The default 
setting is CACHE_AUTO. See the Spring documentation and Transactions Cache 
Levels for more information. | CACHE_AUTO | String
 | *camel.component.activemq.client-id* | Sets the JMS client ID to use. Note 
that this value, if specified, must be unique and can only be used by a single 
JMS connection instance. It is typically only required for durable topic 
subscriptions. If using Apache ActiveMQ you may prefer to use Virtual Topics 
instead. |  | String
@@ -70,8 +70,8 @@ The component supports 100 options, which are listed below.
 | *camel.component.activemq.header-filter-strategy* | To use a custom 
org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel 
message. The option is a org.apache.camel.spi.HeaderFilterStrategy type. |  | 
String
 | *camel.component.activemq.idle-consumer-limit* | Specify the limit for the 
number of consumers that are allowed to be idle at any given time. | 1 | Integer
 | *camel.component.activemq.idle-task-execution-limit* | Specifies the limit 
for idle executions of a receive task, not having received any message within 
its execution. If this limit is reached, the task will shut down and leave 
receiving to other executing tasks (in the case of dynamic scheduling; see the 
maxConcurrentConsumers setting). There is additional doc available from Spring. 
| 1 | Integer
-| *camel.component.activemq.include-all-j-m-s-x-properties* | Whether to 
include all JMSXxxx properties when mapping from JMS to Camel Message. Setting 
this to true will include properties such as JMSXAppID, and JMSXUserID etc. 
Note: If you are using a custom headerFilterStrategy then this option does not 
apply. | false | Boolean
-| *camel.component.activemq.include-sent-j-m-s-message-i-d* | Only applicable 
when sending to JMS destination using InOnly (eg fire and forget). Enabling 
this option will enrich the Camel Exchange with the actual JMSMessageID that 
was used by the JMS client when the message was sent to the JMS destination. | 
false | Boolean
+| *camel.component.activemq.include-all-jmsx-properties* | Whether to include 
all JMSXxxx properties when mapping from JMS to Camel Message. Setting this to 
true will include properties such as JMSXAppID, and JMSXUserID etc. Note: If 
you are using a custom headerFilterStrategy then this option does not apply. | 
false | Boolean
+| *camel.component.activemq.include-sent-jms-message-id* | Only applicable 
when sending to JMS destination using InOnly (eg fire and forget). Enabling 
this option will enrich the Camel Exchange with the actual JMSMessageID that 
was used by the JMS client when the message was sent to the JMS destination. | 
false | Boolean
 | *camel.component.activemq.jms-key-format-strategy* | Pluggable strategy for 
encoding and decoding JMS keys so they can be compliant with the JMS 
specification. Camel provides two implementations out of the box: default and 
passthrough. The default strategy will safely marshal dots and hyphens (. and 
-). The passthrough strategy leaves the key as is. Can be used for JMS brokers 
which do not care whether JMS header keys contain illegal characters. You can 
provide your own implementation  [...]
 | *camel.component.activemq.jms-message-type* | Allows you to force the use of 
a specific javax.jms.Message implementation for sending JMS messages. Possible 
values are: Bytes, Map, Object, Stream, Text. By default, Camel would determine 
which JMS message type to use from the In body type. This option allows you to 
specify it. |  | JmsMessageType
 | *camel.component.activemq.lazy-create-transaction-manager* | If true, Camel 
will create a JmsTransactionManager, if there is no transactionManager injected 
when option transacted=true. | true | Boolean
@@ -118,7 +118,7 @@ The component supports 100 options, which are listed below.
 | *camel.component.activemq.transfer-exception* | If enabled and you are using 
Request Reply messaging (InOut) and an Exchange failed on the consumer side, 
then the caused Exception will be send back in response as a 
javax.jms.ObjectMessage. If the client is Camel, the returned Exception is 
rethrown. This allows you to use Camel JMS as a bridge in your routing - for 
example, using persistent queues to enable robust routing. Notice that if you 
also have transferExchange enabled, this opti [...]
 | *camel.component.activemq.transfer-exchange* | You can transfer the exchange 
over the wire instead of just the body and headers. The following fields are 
transferred: In body, Out body, Fault body, In headers, Out headers, Fault 
headers, exchange properties, exchange exception. This requires that the 
objects are serializable. Camel will exclude any non-serializable objects and 
log it at WARN level. You must enable this option on both the producer and 
consumer side, so Camel knows the p [...]
 | *camel.component.activemq.trust-all-packages* | Define if all Java packages 
are trusted or not (for Java object JMS message types). Notice its not 
recommended practice to send Java serialized objects over network. Setting this 
to true can expose security risks, so use this with care. | false | Boolean
-| *camel.component.activemq.use-message-i-d-as-correlation-i-d* | Specifies 
whether JMSMessageID should always be used as JMSCorrelationID for InOut 
messages. | false | Boolean
+| *camel.component.activemq.use-message-id-as-correlation-id* | Specifies 
whether JMSMessageID should always be used as JMSCorrelationID for InOut 
messages. | false | Boolean
 | *camel.component.activemq.use-pooled-connection* | Enables or disables 
whether a PooledConnectionFactory will be used so that when messages are sent 
to ActiveMQ from outside of a message consuming thread, pooling will be used 
rather than the default with the Spring JmsTemplate which will create a new 
connection, session, producer for each message then close them all down again. 
The default value is true. | false | Boolean
 | *camel.component.activemq.use-single-connection* | Enables or disables 
whether a Spring SingleConnectionFactory will be used so that when messages are 
sent to ActiveMQ from outside of a message consuming thread, pooling will be 
used rather than the default with the Spring JmsTemplate which will create a 
new connection, session, producer for each message then close them all down 
again. The default value is false and a pooled connection is used by default. | 
false | Boolean
 | *camel.component.activemq.username* | Username to use with the 
ConnectionFactory. You can also configure username/password directly on the 
ConnectionFactory. |  | String
diff --git a/docs/modules/ROOT/pages/amqp-starter.adoc 
b/docs/modules/ROOT/pages/amqp-starter.adoc
index a0885d4..54c3f5a 100644
--- a/docs/modules/ROOT/pages/amqp-starter.adoc
+++ b/docs/modules/ROOT/pages/amqp-starter.adoc
@@ -69,9 +69,9 @@ The component supports 97 options, which are listed below.
 | *camel.component.amqp.header-filter-strategy* | To use a custom 
org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel 
message. The option is a org.apache.camel.spi.HeaderFilterStrategy type. |  | 
String
 | *camel.component.amqp.idle-consumer-limit* | Specify the limit for the 
number of consumers that are allowed to be idle at any given time. | 1 | Integer
 | *camel.component.amqp.idle-task-execution-limit* | Specifies the limit for 
idle executions of a receive task, not having received any message within its 
execution. If this limit is reached, the task will shut down and leave 
receiving to other executing tasks (in the case of dynamic scheduling; see the 
maxConcurrentConsumers setting). There is additional doc available from Spring. 
| 1 | Integer
-| *camel.component.amqp.include-all-j-m-s-x-properties* | Whether to include 
all JMSXxxx properties when mapping from JMS to Camel Message. Setting this to 
true will include properties such as JMSXAppID, and JMSXUserID etc. Note: If 
you are using a custom headerFilterStrategy then this option does not apply. | 
false | Boolean
+| *camel.component.amqp.include-all-jmsx-properties* | Whether to include all 
JMSXxxx properties when mapping from JMS to Camel Message. Setting this to true 
will include properties such as JMSXAppID, and JMSXUserID etc. Note: If you are 
using a custom headerFilterStrategy then this option does not apply. | false | 
Boolean
 | *camel.component.amqp.include-amqp-annotations* | Whether to include AMQP 
annotations when mapping from AMQP to Camel Message. Setting this to true will 
map AMQP message annotations to message headers. Due to limitations in Apache 
Qpid JMS API, currently delivery annotations are ignored. | false | Boolean
-| *camel.component.amqp.include-sent-j-m-s-message-i-d* | Only applicable when 
sending to JMS destination using InOnly (eg fire and forget). Enabling this 
option will enrich the Camel Exchange with the actual JMSMessageID that was 
used by the JMS client when the message was sent to the JMS destination. | 
false | Boolean
+| *camel.component.amqp.include-sent-jms-message-id* | Only applicable when 
sending to JMS destination using InOnly (eg fire and forget). Enabling this 
option will enrich the Camel Exchange with the actual JMSMessageID that was 
used by the JMS client when the message was sent to the JMS destination. | 
false | Boolean
 | *camel.component.amqp.jms-key-format-strategy* | Pluggable strategy for 
encoding and decoding JMS keys so they can be compliant with the JMS 
specification. Camel provides two implementations out of the box: default and 
passthrough. The default strategy will safely marshal dots and hyphens (. and 
-). The passthrough strategy leaves the key as is. Can be used for JMS brokers 
which do not care whether JMS header keys contain illegal characters. You can 
provide your own implementation of t [...]
 | *camel.component.amqp.jms-message-type* | Allows you to force the use of a 
specific javax.jms.Message implementation for sending JMS messages. Possible 
values are: Bytes, Map, Object, Stream, Text. By default, Camel would determine 
which JMS message type to use from the In body type. This option allows you to 
specify it. |  | JmsMessageType
 | *camel.component.amqp.lazy-create-transaction-manager* | If true, Camel will 
create a JmsTransactionManager, if there is no transactionManager injected when 
option transacted=true. | true | Boolean
@@ -117,7 +117,7 @@ The component supports 97 options, which are listed below.
 | *camel.component.amqp.transaction-timeout* | The timeout value of the 
transaction (in seconds), if using transacted mode. | -1 | Integer
 | *camel.component.amqp.transfer-exception* | If enabled and you are using 
Request Reply messaging (InOut) and an Exchange failed on the consumer side, 
then the caused Exception will be send back in response as a 
javax.jms.ObjectMessage. If the client is Camel, the returned Exception is 
rethrown. This allows you to use Camel JMS as a bridge in your routing - for 
example, using persistent queues to enable robust routing. Notice that if you 
also have transferExchange enabled, this option t [...]
 | *camel.component.amqp.transfer-exchange* | You can transfer the exchange 
over the wire instead of just the body and headers. The following fields are 
transferred: In body, Out body, Fault body, In headers, Out headers, Fault 
headers, exchange properties, exchange exception. This requires that the 
objects are serializable. Camel will exclude any non-serializable objects and 
log it at WARN level. You must enable this option on both the producer and 
consumer side, so Camel knows the paylo [...]
-| *camel.component.amqp.use-message-i-d-as-correlation-i-d* | Specifies 
whether JMSMessageID should always be used as JMSCorrelationID for InOut 
messages. | false | Boolean
+| *camel.component.amqp.use-message-id-as-correlation-id* | Specifies whether 
JMSMessageID should always be used as JMSCorrelationID for InOut messages. | 
false | Boolean
 | *camel.component.amqp.username* | Username to use with the 
ConnectionFactory. You can also configure username/password directly on the 
ConnectionFactory. |  | String
 | *camel.component.amqp.wait-for-provision-correlation-to-be-updated-counter* 
| Number of times to wait for provisional correlation id to be updated to the 
actual correlation id when doing request/reply over JMS and when the option 
useMessageIDAsCorrelationID is enabled. | 50 | Integer
 | 
*camel.component.amqp.wait-for-provision-correlation-to-be-updated-thread-sleeping-time*
 | Interval in millis to sleep each time while waiting for provisional 
correlation id to be updated. | 100 | Long
diff --git a/docs/modules/ROOT/pages/stomp-starter.adoc 
b/docs/modules/ROOT/pages/stomp-starter.adoc
index f52a918..f407536 100644
--- a/docs/modules/ROOT/pages/stomp-starter.adoc
+++ b/docs/modules/ROOT/pages/stomp-starter.adoc
@@ -26,7 +26,7 @@ The component supports 14 options, which are listed below.
 | Name | Description | Default | Type
 | *camel.component.stomp.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.stomp.bridge-error-handler* | Allows for bridging the 
consumer to the Camel routing Error Handler, which mean any exceptions occurred 
while the consumer is trying to pickup incoming messages, or the likes, will 
now be processed as a message and handled by the routing Error Handler. By 
default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal 
with exceptions, that will be logged at WARN or ERROR level and ignored. | 
false | Boolean
-| *camel.component.stomp.broker-u-r-l* | The URI of the Stomp broker to 
connect to | tcp://localhost:61613 | String
+| *camel.component.stomp.broker-url* | The URI of the Stomp broker to connect 
to | tcp://localhost:61613 | String
 | *camel.component.stomp.configuration* | Component configuration. The option 
is a org.apache.camel.component.stomp.StompConfiguration type. |  | String
 | *camel.component.stomp.custom-headers* | To set custom headers. The option 
is a java.util.Properties type. |  | String
 | *camel.component.stomp.enabled* | Whether to enable auto configuration of 
the stomp component. This is enabled by default. |  | Boolean

Reply via email to