This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/main by this push:
new 6ac1302e665 Regen
6ac1302e665 is described below
commit 6ac1302e665596acd5e1554d3b212235156bde8c
Author: Claus Ibsen <claus.ib...@gmail.com>
AuthorDate: Thu Feb 8 18:57:10 2024 +0100
Regen
---
.../dsl/ActivemqComponentBuilderFactory.java | 31 ++++----
.../component/dsl/AmqpComponentBuilderFactory.java | 31 ++++----
.../component/dsl/JmsComponentBuilderFactory.java | 31 ++++----
.../endpoint/dsl/AMQPEndpointBuilderFactory.java | 93 +++++++++++-----------
.../dsl/ActiveMQEndpointBuilderFactory.java | 93 +++++++++++-----------
.../endpoint/dsl/JmsEndpointBuilderFactory.java | 93 +++++++++++-----------
6 files changed, 180 insertions(+), 192 deletions(-)
diff --git
a/dsl/camel-componentdsl/src/generated/java/org/apache/camel/builder/component/dsl/ActivemqComponentBuilderFactory.java
b/dsl/camel-componentdsl/src/generated/java/org/apache/camel/builder/component/dsl/ActivemqComponentBuilderFactory.java
index 028016976e0..5475505cf14 100644
---
a/dsl/camel-componentdsl/src/generated/java/org/apache/camel/builder/component/dsl/ActivemqComponentBuilderFactory.java
+++
b/dsl/camel-componentdsl/src/generated/java/org/apache/camel/builder/component/dsl/ActivemqComponentBuilderFactory.java
@@ -72,8 +72,7 @@ public interface ActivemqComponentBuilderFactory {
* 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.
+ * subscriptions with JMS 1.1.
*
* The option is a: <code>java.lang.String</code> type.
*
@@ -572,12 +571,12 @@ public interface ActivemqComponentBuilderFactory {
* DefaultMessageListenerContainer, for both consumer endpoints and the
* ReplyTo consumer of producer endpoints. Possible values: SimpleAsync
* (uses Spring's SimpleAsyncTaskExecutor) or ThreadPool (uses Spring's
- * ThreadPoolTaskExecutor with optimal values - cached
threadpool-like).
- * If not set, it defaults to the previous behaviour, which uses a
- * cached thread pool for consumer endpoints and SimpleAsync for reply
- * consumers. The use of ThreadPool is recommended to reduce thread
- * trash in elastic configurations with dynamically increasing and
- * decreasing concurrent consumers.
+ * ThreadPoolTaskExecutor with optimal values - cached
+ * thread-pool-like). If not set, it defaults to the previous
behaviour,
+ * which uses a cached thread pool for consumer endpoints and
+ * SimpleAsync for reply consumers. The use of ThreadPool is
recommended
+ * to reduce thread trash in elastic configurations with dynamically
+ * increasing and decreasing concurrent consumers.
*
* The option is a:
*
<code>org.apache.camel.component.jms.DefaultTaskExecutorType</code>
type.
@@ -998,8 +997,8 @@ public interface ActivemqComponentBuilderFactory {
}
/**
* This option is used to allow additional headers which may have
values
- * that are invalid according to JMS specification. For example some
- * message systems such as WMQ do this with header names using prefix
+ * that are invalid according to JMS specification. For example, some
+ * message systems, such as WMQ, do this with header names using prefix
* JMS_IBM_MQMD_ containing values with byte array or other invalid
* types. You can specify multiple header names separated by comma, and
* use as suffix for wildcard matching.
@@ -1274,7 +1273,7 @@ public interface ActivemqComponentBuilderFactory {
* Whether to startup the JmsConsumer message listener asynchronously,
* when starting a route. For example if a JmsConsumer cannot get a
* connection to a remote JMS broker, then it may block while retrying
- * and/or failover. This will cause Camel to block while starting
+ * and/or fail-over. This will cause Camel to block while starting
* routes. By setting this option to true, you will let routes startup,
* while the JmsConsumer connects to the JMS broker using a dedicated
* thread in asynchronous mode. If this option is used, then beware
that
@@ -1444,9 +1443,9 @@ public interface ActivemqComponentBuilderFactory {
return this;
}
/**
- * 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
+ * Whether to include all JMSX prefixed 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.
*
* The option is a: <code>boolean</code> type.
@@ -1898,8 +1897,8 @@ public interface ActivemqComponentBuilderFactory {
return this;
}
/**
- * Allows to control whether stacktraces should be logged or not, by
the
- * default errorHandler.
+ * Allows to control whether stack-traces should be logged or not, by
+ * the default errorHandler.
*
* The option is a: <code>boolean</code> type.
*
diff --git
a/dsl/camel-componentdsl/src/generated/java/org/apache/camel/builder/component/dsl/AmqpComponentBuilderFactory.java
b/dsl/camel-componentdsl/src/generated/java/org/apache/camel/builder/component/dsl/AmqpComponentBuilderFactory.java
index e956aa0bd3c..a891418da80 100644
---
a/dsl/camel-componentdsl/src/generated/java/org/apache/camel/builder/component/dsl/AmqpComponentBuilderFactory.java
+++
b/dsl/camel-componentdsl/src/generated/java/org/apache/camel/builder/component/dsl/AmqpComponentBuilderFactory.java
@@ -52,8 +52,7 @@ public interface AmqpComponentBuilderFactory {
* 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.
+ * subscriptions with JMS 1.1.
*
* The option is a: <code>java.lang.String</code> type.
*
@@ -527,12 +526,12 @@ public interface AmqpComponentBuilderFactory {
* DefaultMessageListenerContainer, for both consumer endpoints and the
* ReplyTo consumer of producer endpoints. Possible values: SimpleAsync
* (uses Spring's SimpleAsyncTaskExecutor) or ThreadPool (uses Spring's
- * ThreadPoolTaskExecutor with optimal values - cached
threadpool-like).
- * If not set, it defaults to the previous behaviour, which uses a
- * cached thread pool for consumer endpoints and SimpleAsync for reply
- * consumers. The use of ThreadPool is recommended to reduce thread
- * trash in elastic configurations with dynamically increasing and
- * decreasing concurrent consumers.
+ * ThreadPoolTaskExecutor with optimal values - cached
+ * thread-pool-like). If not set, it defaults to the previous
behaviour,
+ * which uses a cached thread pool for consumer endpoints and
+ * SimpleAsync for reply consumers. The use of ThreadPool is
recommended
+ * to reduce thread trash in elastic configurations with dynamically
+ * increasing and decreasing concurrent consumers.
*
* The option is a:
*
<code>org.apache.camel.component.jms.DefaultTaskExecutorType</code>
type.
@@ -951,8 +950,8 @@ public interface AmqpComponentBuilderFactory {
}
/**
* This option is used to allow additional headers which may have
values
- * that are invalid according to JMS specification. For example some
- * message systems such as WMQ do this with header names using prefix
+ * that are invalid according to JMS specification. For example, some
+ * message systems, such as WMQ, do this with header names using prefix
* JMS_IBM_MQMD_ containing values with byte array or other invalid
* types. You can specify multiple header names separated by comma, and
* use as suffix for wildcard matching.
@@ -1225,7 +1224,7 @@ public interface AmqpComponentBuilderFactory {
* Whether to startup the JmsConsumer message listener asynchronously,
* when starting a route. For example if a JmsConsumer cannot get a
* connection to a remote JMS broker, then it may block while retrying
- * and/or failover. This will cause Camel to block while starting
+ * and/or fail-over. This will cause Camel to block while starting
* routes. By setting this option to true, you will let routes startup,
* while the JmsConsumer connects to the JMS broker using a dedicated
* thread in asynchronous mode. If this option is used, then beware
that
@@ -1393,9 +1392,9 @@ public interface AmqpComponentBuilderFactory {
return this;
}
/**
- * 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
+ * Whether to include all JMSX prefixed 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.
*
* The option is a: <code>boolean</code> type.
@@ -1824,8 +1823,8 @@ public interface AmqpComponentBuilderFactory {
return this;
}
/**
- * Allows to control whether stacktraces should be logged or not, by
the
- * default errorHandler.
+ * Allows to control whether stack-traces should be logged or not, by
+ * the default errorHandler.
*
* The option is a: <code>boolean</code> type.
*
diff --git
a/dsl/camel-componentdsl/src/generated/java/org/apache/camel/builder/component/dsl/JmsComponentBuilderFactory.java
b/dsl/camel-componentdsl/src/generated/java/org/apache/camel/builder/component/dsl/JmsComponentBuilderFactory.java
index ba412f81d0f..3f9fb33cee9 100644
---
a/dsl/camel-componentdsl/src/generated/java/org/apache/camel/builder/component/dsl/JmsComponentBuilderFactory.java
+++
b/dsl/camel-componentdsl/src/generated/java/org/apache/camel/builder/component/dsl/JmsComponentBuilderFactory.java
@@ -52,8 +52,7 @@ public interface JmsComponentBuilderFactory {
* 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.
+ * subscriptions with JMS 1.1.
*
* The option is a: <code>java.lang.String</code> type.
*
@@ -508,12 +507,12 @@ public interface JmsComponentBuilderFactory {
* DefaultMessageListenerContainer, for both consumer endpoints and the
* ReplyTo consumer of producer endpoints. Possible values: SimpleAsync
* (uses Spring's SimpleAsyncTaskExecutor) or ThreadPool (uses Spring's
- * ThreadPoolTaskExecutor with optimal values - cached
threadpool-like).
- * If not set, it defaults to the previous behaviour, which uses a
- * cached thread pool for consumer endpoints and SimpleAsync for reply
- * consumers. The use of ThreadPool is recommended to reduce thread
- * trash in elastic configurations with dynamically increasing and
- * decreasing concurrent consumers.
+ * ThreadPoolTaskExecutor with optimal values - cached
+ * thread-pool-like). If not set, it defaults to the previous
behaviour,
+ * which uses a cached thread pool for consumer endpoints and
+ * SimpleAsync for reply consumers. The use of ThreadPool is
recommended
+ * to reduce thread trash in elastic configurations with dynamically
+ * increasing and decreasing concurrent consumers.
*
* The option is a:
*
<code>org.apache.camel.component.jms.DefaultTaskExecutorType</code>
type.
@@ -932,8 +931,8 @@ public interface JmsComponentBuilderFactory {
}
/**
* This option is used to allow additional headers which may have
values
- * that are invalid according to JMS specification. For example some
- * message systems such as WMQ do this with header names using prefix
+ * that are invalid according to JMS specification. For example, some
+ * message systems, such as WMQ, do this with header names using prefix
* JMS_IBM_MQMD_ containing values with byte array or other invalid
* types. You can specify multiple header names separated by comma, and
* use as suffix for wildcard matching.
@@ -1206,7 +1205,7 @@ public interface JmsComponentBuilderFactory {
* Whether to startup the JmsConsumer message listener asynchronously,
* when starting a route. For example if a JmsConsumer cannot get a
* connection to a remote JMS broker, then it may block while retrying
- * and/or failover. This will cause Camel to block while starting
+ * and/or fail-over. This will cause Camel to block while starting
* routes. By setting this option to true, you will let routes startup,
* while the JmsConsumer connects to the JMS broker using a dedicated
* thread in asynchronous mode. If this option is used, then beware
that
@@ -1374,9 +1373,9 @@ public interface JmsComponentBuilderFactory {
return this;
}
/**
- * 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
+ * Whether to include all JMSX prefixed 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.
*
* The option is a: <code>boolean</code> type.
@@ -1805,8 +1804,8 @@ public interface JmsComponentBuilderFactory {
return this;
}
/**
- * Allows to control whether stacktraces should be logged or not, by
the
- * default errorHandler.
+ * Allows to control whether stack-traces should be logged or not, by
+ * the default errorHandler.
*
* The option is a: <code>boolean</code> type.
*
diff --git
a/dsl/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/dsl/AMQPEndpointBuilderFactory.java
b/dsl/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/dsl/AMQPEndpointBuilderFactory.java
index 7ede38af013..08d4cb24ecc 100644
---
a/dsl/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/dsl/AMQPEndpointBuilderFactory.java
+++
b/dsl/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/dsl/AMQPEndpointBuilderFactory.java
@@ -47,8 +47,7 @@ public interface AMQPEndpointBuilderFactory {
* 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.
+ * subscriptions with JMS 1.1.
*
* The option is a: <code>java.lang.String</code> type.
*
@@ -733,8 +732,8 @@ public interface AMQPEndpointBuilderFactory {
return this;
}
/**
- * Allows to control whether stacktraces should be logged or not, by
the
- * default errorHandler.
+ * Allows to control whether stack-traces should be logged or not, by
+ * the default errorHandler.
*
* The option is a: <code>boolean</code> type.
*
@@ -750,8 +749,8 @@ public interface AMQPEndpointBuilderFactory {
return this;
}
/**
- * Allows to control whether stacktraces should be logged or not, by
the
- * default errorHandler.
+ * Allows to control whether stack-traces should be logged or not, by
+ * the default errorHandler.
*
* The option will be converted to a <code>boolean</code>
* type.
@@ -1055,12 +1054,12 @@ public interface AMQPEndpointBuilderFactory {
* DefaultMessageListenerContainer, for both consumer endpoints and the
* ReplyTo consumer of producer endpoints. Possible values: SimpleAsync
* (uses Spring's SimpleAsyncTaskExecutor) or ThreadPool (uses Spring's
- * ThreadPoolTaskExecutor with optimal values - cached
threadpool-like).
- * If not set, it defaults to the previous behaviour, which uses a
- * cached thread pool for consumer endpoints and SimpleAsync for reply
- * consumers. The use of ThreadPool is recommended to reduce thread
- * trash in elastic configurations with dynamically increasing and
- * decreasing concurrent consumers.
+ * ThreadPoolTaskExecutor with optimal values - cached
+ * thread-pool-like). If not set, it defaults to the previous
behaviour,
+ * which uses a cached thread pool for consumer endpoints and
+ * SimpleAsync for reply consumers. The use of ThreadPool is
recommended
+ * to reduce thread trash in elastic configurations with dynamically
+ * increasing and decreasing concurrent consumers.
*
* The option is a:
*
<code>org.apache.camel.component.jms.DefaultTaskExecutorType</code>
type.
@@ -1080,12 +1079,12 @@ public interface AMQPEndpointBuilderFactory {
* DefaultMessageListenerContainer, for both consumer endpoints and the
* ReplyTo consumer of producer endpoints. Possible values: SimpleAsync
* (uses Spring's SimpleAsyncTaskExecutor) or ThreadPool (uses Spring's
- * ThreadPoolTaskExecutor with optimal values - cached
threadpool-like).
- * If not set, it defaults to the previous behaviour, which uses a
- * cached thread pool for consumer endpoints and SimpleAsync for reply
- * consumers. The use of ThreadPool is recommended to reduce thread
- * trash in elastic configurations with dynamically increasing and
- * decreasing concurrent consumers.
+ * ThreadPoolTaskExecutor with optimal values - cached
+ * thread-pool-like). If not set, it defaults to the previous
behaviour,
+ * which uses a cached thread pool for consumer endpoints and
+ * SimpleAsync for reply consumers. The use of ThreadPool is
recommended
+ * to reduce thread trash in elastic configurations with dynamically
+ * increasing and decreasing concurrent consumers.
*
* The option will be converted to a
*
<code>org.apache.camel.component.jms.DefaultTaskExecutorType</code>
type.
@@ -1474,7 +1473,7 @@ public interface AMQPEndpointBuilderFactory {
* Whether to startup the JmsConsumer message listener asynchronously,
* when starting a route. For example if a JmsConsumer cannot get a
* connection to a remote JMS broker, then it may block while retrying
- * and/or failover. This will cause Camel to block while starting
+ * and/or fail-over. This will cause Camel to block while starting
* routes. By setting this option to true, you will let routes startup,
* while the JmsConsumer connects to the JMS broker using a dedicated
* thread in asynchronous mode. If this option is used, then beware
that
@@ -1499,7 +1498,7 @@ public interface AMQPEndpointBuilderFactory {
* Whether to startup the JmsConsumer message listener asynchronously,
* when starting a route. For example if a JmsConsumer cannot get a
* connection to a remote JMS broker, then it may block while retrying
- * and/or failover. This will cause Camel to block while starting
+ * and/or fail-over. This will cause Camel to block while starting
* routes. By setting this option to true, you will let routes startup,
* while the JmsConsumer connects to the JMS broker using a dedicated
* thread in asynchronous mode. If this option is used, then beware
that
@@ -1783,9 +1782,9 @@ public interface AMQPEndpointBuilderFactory {
return this;
}
/**
- * 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
+ * Whether to include all JMSX prefixed 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.
*
* The option is a: <code>boolean</code> type.
@@ -1802,9 +1801,9 @@ public interface AMQPEndpointBuilderFactory {
return this;
}
/**
- * 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
+ * Whether to include all JMSX prefixed 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.
*
* The option will be converted to a <code>boolean</code>
@@ -2664,8 +2663,7 @@ public interface AMQPEndpointBuilderFactory {
* 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.
+ * subscriptions with JMS 1.1.
*
* The option is a: <code>java.lang.String</code> type.
*
@@ -3510,8 +3508,8 @@ public interface AMQPEndpointBuilderFactory {
}
/**
* This option is used to allow additional headers which may have
values
- * that are invalid according to JMS specification. For example some
- * message systems such as WMQ do this with header names using prefix
+ * that are invalid according to JMS specification. For example, some
+ * message systems, such as WMQ, do this with header names using prefix
* JMS_IBM_MQMD_ containing values with byte array or other invalid
* types. You can specify multiple header names separated by comma, and
* use as suffix for wildcard matching.
@@ -3965,7 +3963,7 @@ public interface AMQPEndpointBuilderFactory {
* Whether to startup the JmsConsumer message listener asynchronously,
* when starting a route. For example if a JmsConsumer cannot get a
* connection to a remote JMS broker, then it may block while retrying
- * and/or failover. This will cause Camel to block while starting
+ * and/or fail-over. This will cause Camel to block while starting
* routes. By setting this option to true, you will let routes startup,
* while the JmsConsumer connects to the JMS broker using a dedicated
* thread in asynchronous mode. If this option is used, then beware
that
@@ -3990,7 +3988,7 @@ public interface AMQPEndpointBuilderFactory {
* Whether to startup the JmsConsumer message listener asynchronously,
* when starting a route. For example if a JmsConsumer cannot get a
* connection to a remote JMS broker, then it may block while retrying
- * and/or failover. This will cause Camel to block while starting
+ * and/or fail-over. This will cause Camel to block while starting
* routes. By setting this option to true, you will let routes startup,
* while the JmsConsumer connects to the JMS broker using a dedicated
* thread in asynchronous mode. If this option is used, then beware
that
@@ -4274,9 +4272,9 @@ public interface AMQPEndpointBuilderFactory {
return this;
}
/**
- * 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
+ * Whether to include all JMSX prefixed 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.
*
* The option is a: <code>boolean</code> type.
@@ -4293,9 +4291,9 @@ public interface AMQPEndpointBuilderFactory {
return this;
}
/**
- * 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
+ * Whether to include all JMSX prefixed 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.
*
* The option will be converted to a <code>boolean</code>
@@ -5156,8 +5154,7 @@ public interface AMQPEndpointBuilderFactory {
* 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.
+ * subscriptions with JMS 1.1.
*
* The option is a: <code>java.lang.String</code> type.
*
@@ -5575,7 +5572,7 @@ public interface AMQPEndpointBuilderFactory {
* Whether to startup the JmsConsumer message listener asynchronously,
* when starting a route. For example if a JmsConsumer cannot get a
* connection to a remote JMS broker, then it may block while retrying
- * and/or failover. This will cause Camel to block while starting
+ * and/or fail-over. This will cause Camel to block while starting
* routes. By setting this option to true, you will let routes startup,
* while the JmsConsumer connects to the JMS broker using a dedicated
* thread in asynchronous mode. If this option is used, then beware
that
@@ -5600,7 +5597,7 @@ public interface AMQPEndpointBuilderFactory {
* Whether to startup the JmsConsumer message listener asynchronously,
* when starting a route. For example if a JmsConsumer cannot get a
* connection to a remote JMS broker, then it may block while retrying
- * and/or failover. This will cause Camel to block while starting
+ * and/or fail-over. This will cause Camel to block while starting
* routes. By setting this option to true, you will let routes startup,
* while the JmsConsumer connects to the JMS broker using a dedicated
* thread in asynchronous mode. If this option is used, then beware
that
@@ -5883,9 +5880,9 @@ public interface AMQPEndpointBuilderFactory {
return this;
}
/**
- * 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
+ * Whether to include all JMSX prefixed 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.
*
* The option is a: <code>boolean</code> type.
@@ -5902,9 +5899,9 @@ public interface AMQPEndpointBuilderFactory {
return this;
}
/**
- * 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
+ * Whether to include all JMSX prefixed 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.
*
* The option will be converted to a <code>boolean</code>
diff --git
a/dsl/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/dsl/ActiveMQEndpointBuilderFactory.java
b/dsl/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/dsl/ActiveMQEndpointBuilderFactory.java
index 931ee42ebbf..3662d3a62a3 100644
---
a/dsl/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/dsl/ActiveMQEndpointBuilderFactory.java
+++
b/dsl/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/dsl/ActiveMQEndpointBuilderFactory.java
@@ -49,8 +49,7 @@ public interface ActiveMQEndpointBuilderFactory {
* 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.
+ * subscriptions with JMS 1.1.
*
* The option is a: <code>java.lang.String</code> type.
*
@@ -740,8 +739,8 @@ public interface ActiveMQEndpointBuilderFactory {
return this;
}
/**
- * Allows to control whether stacktraces should be logged or not, by
the
- * default errorHandler.
+ * Allows to control whether stack-traces should be logged or not, by
+ * the default errorHandler.
*
* The option is a: <code>boolean</code> type.
*
@@ -757,8 +756,8 @@ public interface ActiveMQEndpointBuilderFactory {
return this;
}
/**
- * Allows to control whether stacktraces should be logged or not, by
the
- * default errorHandler.
+ * Allows to control whether stack-traces should be logged or not, by
+ * the default errorHandler.
*
* The option will be converted to a <code>boolean</code>
* type.
@@ -1062,12 +1061,12 @@ public interface ActiveMQEndpointBuilderFactory {
* DefaultMessageListenerContainer, for both consumer endpoints and the
* ReplyTo consumer of producer endpoints. Possible values: SimpleAsync
* (uses Spring's SimpleAsyncTaskExecutor) or ThreadPool (uses Spring's
- * ThreadPoolTaskExecutor with optimal values - cached
threadpool-like).
- * If not set, it defaults to the previous behaviour, which uses a
- * cached thread pool for consumer endpoints and SimpleAsync for reply
- * consumers. The use of ThreadPool is recommended to reduce thread
- * trash in elastic configurations with dynamically increasing and
- * decreasing concurrent consumers.
+ * ThreadPoolTaskExecutor with optimal values - cached
+ * thread-pool-like). If not set, it defaults to the previous
behaviour,
+ * which uses a cached thread pool for consumer endpoints and
+ * SimpleAsync for reply consumers. The use of ThreadPool is
recommended
+ * to reduce thread trash in elastic configurations with dynamically
+ * increasing and decreasing concurrent consumers.
*
* The option is a:
*
<code>org.apache.camel.component.jms.DefaultTaskExecutorType</code>
type.
@@ -1087,12 +1086,12 @@ public interface ActiveMQEndpointBuilderFactory {
* DefaultMessageListenerContainer, for both consumer endpoints and the
* ReplyTo consumer of producer endpoints. Possible values: SimpleAsync
* (uses Spring's SimpleAsyncTaskExecutor) or ThreadPool (uses Spring's
- * ThreadPoolTaskExecutor with optimal values - cached
threadpool-like).
- * If not set, it defaults to the previous behaviour, which uses a
- * cached thread pool for consumer endpoints and SimpleAsync for reply
- * consumers. The use of ThreadPool is recommended to reduce thread
- * trash in elastic configurations with dynamically increasing and
- * decreasing concurrent consumers.
+ * ThreadPoolTaskExecutor with optimal values - cached
+ * thread-pool-like). If not set, it defaults to the previous
behaviour,
+ * which uses a cached thread pool for consumer endpoints and
+ * SimpleAsync for reply consumers. The use of ThreadPool is
recommended
+ * to reduce thread trash in elastic configurations with dynamically
+ * increasing and decreasing concurrent consumers.
*
* The option will be converted to a
*
<code>org.apache.camel.component.jms.DefaultTaskExecutorType</code>
type.
@@ -1529,7 +1528,7 @@ public interface ActiveMQEndpointBuilderFactory {
* Whether to startup the JmsConsumer message listener asynchronously,
* when starting a route. For example if a JmsConsumer cannot get a
* connection to a remote JMS broker, then it may block while retrying
- * and/or failover. This will cause Camel to block while starting
+ * and/or fail-over. This will cause Camel to block while starting
* routes. By setting this option to true, you will let routes startup,
* while the JmsConsumer connects to the JMS broker using a dedicated
* thread in asynchronous mode. If this option is used, then beware
that
@@ -1554,7 +1553,7 @@ public interface ActiveMQEndpointBuilderFactory {
* Whether to startup the JmsConsumer message listener asynchronously,
* when starting a route. For example if a JmsConsumer cannot get a
* connection to a remote JMS broker, then it may block while retrying
- * and/or failover. This will cause Camel to block while starting
+ * and/or fail-over. This will cause Camel to block while starting
* routes. By setting this option to true, you will let routes startup,
* while the JmsConsumer connects to the JMS broker using a dedicated
* thread in asynchronous mode. If this option is used, then beware
that
@@ -1838,9 +1837,9 @@ public interface ActiveMQEndpointBuilderFactory {
return this;
}
/**
- * 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
+ * Whether to include all JMSX prefixed 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.
*
* The option is a: <code>boolean</code> type.
@@ -1857,9 +1856,9 @@ public interface ActiveMQEndpointBuilderFactory {
return this;
}
/**
- * 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
+ * Whether to include all JMSX prefixed 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.
*
* The option will be converted to a <code>boolean</code>
@@ -2719,8 +2718,7 @@ public interface ActiveMQEndpointBuilderFactory {
* 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.
+ * subscriptions with JMS 1.1.
*
* The option is a: <code>java.lang.String</code> type.
*
@@ -3571,8 +3569,8 @@ public interface ActiveMQEndpointBuilderFactory {
}
/**
* This option is used to allow additional headers which may have
values
- * that are invalid according to JMS specification. For example some
- * message systems such as WMQ do this with header names using prefix
+ * that are invalid according to JMS specification. For example, some
+ * message systems, such as WMQ, do this with header names using prefix
* JMS_IBM_MQMD_ containing values with byte array or other invalid
* types. You can specify multiple header names separated by comma, and
* use as suffix for wildcard matching.
@@ -4026,7 +4024,7 @@ public interface ActiveMQEndpointBuilderFactory {
* Whether to startup the JmsConsumer message listener asynchronously,
* when starting a route. For example if a JmsConsumer cannot get a
* connection to a remote JMS broker, then it may block while retrying
- * and/or failover. This will cause Camel to block while starting
+ * and/or fail-over. This will cause Camel to block while starting
* routes. By setting this option to true, you will let routes startup,
* while the JmsConsumer connects to the JMS broker using a dedicated
* thread in asynchronous mode. If this option is used, then beware
that
@@ -4051,7 +4049,7 @@ public interface ActiveMQEndpointBuilderFactory {
* Whether to startup the JmsConsumer message listener asynchronously,
* when starting a route. For example if a JmsConsumer cannot get a
* connection to a remote JMS broker, then it may block while retrying
- * and/or failover. This will cause Camel to block while starting
+ * and/or fail-over. This will cause Camel to block while starting
* routes. By setting this option to true, you will let routes startup,
* while the JmsConsumer connects to the JMS broker using a dedicated
* thread in asynchronous mode. If this option is used, then beware
that
@@ -4335,9 +4333,9 @@ public interface ActiveMQEndpointBuilderFactory {
return this;
}
/**
- * 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
+ * Whether to include all JMSX prefixed 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.
*
* The option is a: <code>boolean</code> type.
@@ -4354,9 +4352,9 @@ public interface ActiveMQEndpointBuilderFactory {
return this;
}
/**
- * 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
+ * Whether to include all JMSX prefixed 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.
*
* The option will be converted to a <code>boolean</code>
@@ -5217,8 +5215,7 @@ public interface ActiveMQEndpointBuilderFactory {
* 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.
+ * subscriptions with JMS 1.1.
*
* The option is a: <code>java.lang.String</code> type.
*
@@ -5637,7 +5634,7 @@ public interface ActiveMQEndpointBuilderFactory {
* Whether to startup the JmsConsumer message listener asynchronously,
* when starting a route. For example if a JmsConsumer cannot get a
* connection to a remote JMS broker, then it may block while retrying
- * and/or failover. This will cause Camel to block while starting
+ * and/or fail-over. This will cause Camel to block while starting
* routes. By setting this option to true, you will let routes startup,
* while the JmsConsumer connects to the JMS broker using a dedicated
* thread in asynchronous mode. If this option is used, then beware
that
@@ -5662,7 +5659,7 @@ public interface ActiveMQEndpointBuilderFactory {
* Whether to startup the JmsConsumer message listener asynchronously,
* when starting a route. For example if a JmsConsumer cannot get a
* connection to a remote JMS broker, then it may block while retrying
- * and/or failover. This will cause Camel to block while starting
+ * and/or fail-over. This will cause Camel to block while starting
* routes. By setting this option to true, you will let routes startup,
* while the JmsConsumer connects to the JMS broker using a dedicated
* thread in asynchronous mode. If this option is used, then beware
that
@@ -5945,9 +5942,9 @@ public interface ActiveMQEndpointBuilderFactory {
return this;
}
/**
- * 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
+ * Whether to include all JMSX prefixed 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.
*
* The option is a: <code>boolean</code> type.
@@ -5964,9 +5961,9 @@ public interface ActiveMQEndpointBuilderFactory {
return this;
}
/**
- * 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
+ * Whether to include all JMSX prefixed 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.
*
* The option will be converted to a <code>boolean</code>
diff --git
a/dsl/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/dsl/JmsEndpointBuilderFactory.java
b/dsl/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/dsl/JmsEndpointBuilderFactory.java
index a507ac6f97c..576cf3b61da 100644
---
a/dsl/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/dsl/JmsEndpointBuilderFactory.java
+++
b/dsl/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/dsl/JmsEndpointBuilderFactory.java
@@ -47,8 +47,7 @@ public interface JmsEndpointBuilderFactory {
* 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.
+ * subscriptions with JMS 1.1.
*
* The option is a: <code>java.lang.String</code> type.
*
@@ -732,8 +731,8 @@ public interface JmsEndpointBuilderFactory {
return this;
}
/**
- * Allows to control whether stacktraces should be logged or not, by
the
- * default errorHandler.
+ * Allows to control whether stack-traces should be logged or not, by
+ * the default errorHandler.
*
* The option is a: <code>boolean</code> type.
*
@@ -749,8 +748,8 @@ public interface JmsEndpointBuilderFactory {
return this;
}
/**
- * Allows to control whether stacktraces should be logged or not, by
the
- * default errorHandler.
+ * Allows to control whether stack-traces should be logged or not, by
+ * the default errorHandler.
*
* The option will be converted to a <code>boolean</code>
* type.
@@ -1054,12 +1053,12 @@ public interface JmsEndpointBuilderFactory {
* DefaultMessageListenerContainer, for both consumer endpoints and the
* ReplyTo consumer of producer endpoints. Possible values: SimpleAsync
* (uses Spring's SimpleAsyncTaskExecutor) or ThreadPool (uses Spring's
- * ThreadPoolTaskExecutor with optimal values - cached
threadpool-like).
- * If not set, it defaults to the previous behaviour, which uses a
- * cached thread pool for consumer endpoints and SimpleAsync for reply
- * consumers. The use of ThreadPool is recommended to reduce thread
- * trash in elastic configurations with dynamically increasing and
- * decreasing concurrent consumers.
+ * ThreadPoolTaskExecutor with optimal values - cached
+ * thread-pool-like). If not set, it defaults to the previous
behaviour,
+ * which uses a cached thread pool for consumer endpoints and
+ * SimpleAsync for reply consumers. The use of ThreadPool is
recommended
+ * to reduce thread trash in elastic configurations with dynamically
+ * increasing and decreasing concurrent consumers.
*
* The option is a:
*
<code>org.apache.camel.component.jms.DefaultTaskExecutorType</code>
type.
@@ -1079,12 +1078,12 @@ public interface JmsEndpointBuilderFactory {
* DefaultMessageListenerContainer, for both consumer endpoints and the
* ReplyTo consumer of producer endpoints. Possible values: SimpleAsync
* (uses Spring's SimpleAsyncTaskExecutor) or ThreadPool (uses Spring's
- * ThreadPoolTaskExecutor with optimal values - cached
threadpool-like).
- * If not set, it defaults to the previous behaviour, which uses a
- * cached thread pool for consumer endpoints and SimpleAsync for reply
- * consumers. The use of ThreadPool is recommended to reduce thread
- * trash in elastic configurations with dynamically increasing and
- * decreasing concurrent consumers.
+ * ThreadPoolTaskExecutor with optimal values - cached
+ * thread-pool-like). If not set, it defaults to the previous
behaviour,
+ * which uses a cached thread pool for consumer endpoints and
+ * SimpleAsync for reply consumers. The use of ThreadPool is
recommended
+ * to reduce thread trash in elastic configurations with dynamically
+ * increasing and decreasing concurrent consumers.
*
* The option will be converted to a
*
<code>org.apache.camel.component.jms.DefaultTaskExecutorType</code>
type.
@@ -1473,7 +1472,7 @@ public interface JmsEndpointBuilderFactory {
* Whether to startup the JmsConsumer message listener asynchronously,
* when starting a route. For example if a JmsConsumer cannot get a
* connection to a remote JMS broker, then it may block while retrying
- * and/or failover. This will cause Camel to block while starting
+ * and/or fail-over. This will cause Camel to block while starting
* routes. By setting this option to true, you will let routes startup,
* while the JmsConsumer connects to the JMS broker using a dedicated
* thread in asynchronous mode. If this option is used, then beware
that
@@ -1498,7 +1497,7 @@ public interface JmsEndpointBuilderFactory {
* Whether to startup the JmsConsumer message listener asynchronously,
* when starting a route. For example if a JmsConsumer cannot get a
* connection to a remote JMS broker, then it may block while retrying
- * and/or failover. This will cause Camel to block while starting
+ * and/or fail-over. This will cause Camel to block while starting
* routes. By setting this option to true, you will let routes startup,
* while the JmsConsumer connects to the JMS broker using a dedicated
* thread in asynchronous mode. If this option is used, then beware
that
@@ -1782,9 +1781,9 @@ public interface JmsEndpointBuilderFactory {
return this;
}
/**
- * 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
+ * Whether to include all JMSX prefixed 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.
*
* The option is a: <code>boolean</code> type.
@@ -1801,9 +1800,9 @@ public interface JmsEndpointBuilderFactory {
return this;
}
/**
- * 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
+ * Whether to include all JMSX prefixed 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.
*
* The option will be converted to a <code>boolean</code>
@@ -2663,8 +2662,7 @@ public interface JmsEndpointBuilderFactory {
* 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.
+ * subscriptions with JMS 1.1.
*
* The option is a: <code>java.lang.String</code> type.
*
@@ -3508,8 +3506,8 @@ public interface JmsEndpointBuilderFactory {
}
/**
* This option is used to allow additional headers which may have
values
- * that are invalid according to JMS specification. For example some
- * message systems such as WMQ do this with header names using prefix
+ * that are invalid according to JMS specification. For example, some
+ * message systems, such as WMQ, do this with header names using prefix
* JMS_IBM_MQMD_ containing values with byte array or other invalid
* types. You can specify multiple header names separated by comma, and
* use as suffix for wildcard matching.
@@ -3963,7 +3961,7 @@ public interface JmsEndpointBuilderFactory {
* Whether to startup the JmsConsumer message listener asynchronously,
* when starting a route. For example if a JmsConsumer cannot get a
* connection to a remote JMS broker, then it may block while retrying
- * and/or failover. This will cause Camel to block while starting
+ * and/or fail-over. This will cause Camel to block while starting
* routes. By setting this option to true, you will let routes startup,
* while the JmsConsumer connects to the JMS broker using a dedicated
* thread in asynchronous mode. If this option is used, then beware
that
@@ -3988,7 +3986,7 @@ public interface JmsEndpointBuilderFactory {
* Whether to startup the JmsConsumer message listener asynchronously,
* when starting a route. For example if a JmsConsumer cannot get a
* connection to a remote JMS broker, then it may block while retrying
- * and/or failover. This will cause Camel to block while starting
+ * and/or fail-over. This will cause Camel to block while starting
* routes. By setting this option to true, you will let routes startup,
* while the JmsConsumer connects to the JMS broker using a dedicated
* thread in asynchronous mode. If this option is used, then beware
that
@@ -4272,9 +4270,9 @@ public interface JmsEndpointBuilderFactory {
return this;
}
/**
- * 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
+ * Whether to include all JMSX prefixed 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.
*
* The option is a: <code>boolean</code> type.
@@ -4291,9 +4289,9 @@ public interface JmsEndpointBuilderFactory {
return this;
}
/**
- * 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
+ * Whether to include all JMSX prefixed 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.
*
* The option will be converted to a <code>boolean</code>
@@ -5154,8 +5152,7 @@ public interface JmsEndpointBuilderFactory {
* 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.
+ * subscriptions with JMS 1.1.
*
* The option is a: <code>java.lang.String</code> type.
*
@@ -5573,7 +5570,7 @@ public interface JmsEndpointBuilderFactory {
* Whether to startup the JmsConsumer message listener asynchronously,
* when starting a route. For example if a JmsConsumer cannot get a
* connection to a remote JMS broker, then it may block while retrying
- * and/or failover. This will cause Camel to block while starting
+ * and/or fail-over. This will cause Camel to block while starting
* routes. By setting this option to true, you will let routes startup,
* while the JmsConsumer connects to the JMS broker using a dedicated
* thread in asynchronous mode. If this option is used, then beware
that
@@ -5598,7 +5595,7 @@ public interface JmsEndpointBuilderFactory {
* Whether to startup the JmsConsumer message listener asynchronously,
* when starting a route. For example if a JmsConsumer cannot get a
* connection to a remote JMS broker, then it may block while retrying
- * and/or failover. This will cause Camel to block while starting
+ * and/or fail-over. This will cause Camel to block while starting
* routes. By setting this option to true, you will let routes startup,
* while the JmsConsumer connects to the JMS broker using a dedicated
* thread in asynchronous mode. If this option is used, then beware
that
@@ -5881,9 +5878,9 @@ public interface JmsEndpointBuilderFactory {
return this;
}
/**
- * 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
+ * Whether to include all JMSX prefixed 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.
*
* The option is a: <code>boolean</code> type.
@@ -5900,9 +5897,9 @@ public interface JmsEndpointBuilderFactory {
return this;
}
/**
- * 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
+ * Whether to include all JMSX prefixed 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.
*
* The option will be converted to a <code>boolean</code>
