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 320446403167 camel-sjms: drop the transferExchange note from
transferException (#29491)
320446403167 is described below
commit 3204464031670d3c39090bc15ad7e03aefdcfb3e
Author: dhairya05 <[email protected]>
AuthorDate: Tue Nov 10 12:15:56 2026 +0530
camel-sjms: drop the transferExchange note from transferException (#29491)
---
.../org/apache/camel/catalog/components/sjms.json | 2 +-
.../org/apache/camel/catalog/components/sjms2.json | 2 +-
.../org/apache/camel/component/sjms/sjms.json | 2 +-
.../apache/camel/component/sjms/SjmsEndpoint.java | 1 -
.../org/apache/camel/component/sjms2/sjms2.json | 2 +-
.../endpoint/dsl/Sjms2EndpointBuilderFactory.java | 102 ++++++++++-----------
.../endpoint/dsl/SjmsEndpointBuilderFactory.java | 102 ++++++++++-----------
7 files changed, 100 insertions(+), 113 deletions(-)
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/components/sjms.json
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/components/sjms.json
index 4f76c1f5e2ea..a2ab3a0a85af 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/components/sjms.json
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/components/sjms.json
@@ -100,7 +100,7 @@
"objectMessageEnabled": { "index": 43, "kind": "parameter", "displayName":
"Object Message Enabled", "group": "advanced", "label": "advanced", "required":
false, "type": "boolean", "javaType": "boolean", "deprecated": false,
"autowired": false, "secret": false, "security": "insecure:serialization",
"defaultValue": false, "description": "Whether to enable sending and receiving
JMS ObjectMessage. By default this is disabled because Java object
serialization is a known source of securit [...]
"recoveryInterval": { "index": 44, "kind": "parameter", "displayName":
"Recovery Interval", "group": "advanced", "label": "advanced", "required":
false, "type": "duration", "javaType": "long", "deprecated": false,
"autowired": false, "secret": false, "defaultValue": "5000", "description":
"Specifies the interval between recovery attempts, i.e. when a connection is
being refreshed, in milliseconds. The default is 5000 ms, that is, 5 seconds."
},
"synchronous": { "index": 45, "kind": "parameter", "displayName":
"Synchronous", "group": "advanced", "label": "advanced", "required": false,
"type": "boolean", "javaType": "boolean", "deprecated": false, "autowired":
false, "secret": false, "defaultValue": false, "description": "Sets whether
synchronous processing should be strictly used" },
- "transferException": { "index": 46, "kind": "parameter", "displayName":
"Transfer Exception", "group": "advanced", "label": "advanced", "required":
false, "type": "boolean", "javaType": "boolean", "deprecated": false,
"autowired": false, "secret": false, "security": "insecure:serialization",
"defaultValue": false, "description": "If enabled and you are using Request
Reply messaging (InOut) and an Exchange failed on the consumer side, then the
caused Exception will be send back in res [...]
+ "transferException": { "index": 46, "kind": "parameter", "displayName":
"Transfer Exception", "group": "advanced", "label": "advanced", "required":
false, "type": "boolean", "javaType": "boolean", "deprecated": false,
"autowired": false, "secret": false, "security": "insecure:serialization",
"defaultValue": false, "description": "If enabled and you are using Request
Reply messaging (InOut) and an Exchange failed on the consumer side, then the
caused Exception will be send back in res [...]
"batching": { "index": 47, "kind": "parameter", "displayName": "Batching",
"group": "batch", "label": "consumer,batch", "required": false, "type":
"boolean", "javaType": "boolean", "deprecated": false, "autowired": false,
"secret": false, "defaultValue": false, "description": "Enable batch consuming.
The route receives one Exchange per batch, whose body is a List of the
individual JMS messages, instead of one Exchange per message." },
"batchInterval": { "index": 48, "kind": "parameter", "displayName": "Batch
Interval", "group": "batch", "label": "consumer,batch", "required": false,
"type": "duration", "javaType": "long", "deprecated": false, "autowired":
false, "secret": false, "defaultValue": "1000", "description": "Time in millis,
measured from the first message received into a new batch, after which the
batch is dispatched even if batchSize has not been reached, comparable to the
Aggregator EIP's completionInte [...]
"batchSize": { "index": 49, "kind": "parameter", "displayName": "Batch
Size", "group": "batch", "label": "consumer,batch", "required": false, "type":
"integer", "javaType": "int", "deprecated": false, "autowired": false,
"secret": false, "defaultValue": 100, "description": "Maximum number of
messages per batch." },
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/components/sjms2.json
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/components/sjms2.json
index fd31be61e94f..d791bd456ddb 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/components/sjms2.json
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/components/sjms2.json
@@ -103,7 +103,7 @@
"objectMessageEnabled": { "index": 46, "kind": "parameter", "displayName":
"Object Message Enabled", "group": "advanced", "label": "advanced", "required":
false, "type": "boolean", "javaType": "boolean", "deprecated": false,
"autowired": false, "secret": false, "security": "insecure:serialization",
"defaultValue": false, "description": "Whether to enable sending and receiving
JMS ObjectMessage. By default this is disabled because Java object
serialization is a known source of securit [...]
"recoveryInterval": { "index": 47, "kind": "parameter", "displayName":
"Recovery Interval", "group": "advanced", "label": "advanced", "required":
false, "type": "duration", "javaType": "long", "deprecated": false,
"autowired": false, "secret": false, "defaultValue": "5000", "description":
"Specifies the interval between recovery attempts, i.e. when a connection is
being refreshed, in milliseconds. The default is 5000 ms, that is, 5 seconds."
},
"synchronous": { "index": 48, "kind": "parameter", "displayName":
"Synchronous", "group": "advanced", "label": "advanced", "required": false,
"type": "boolean", "javaType": "boolean", "deprecated": false, "autowired":
false, "secret": false, "defaultValue": false, "description": "Sets whether
synchronous processing should be strictly used" },
- "transferException": { "index": 49, "kind": "parameter", "displayName":
"Transfer Exception", "group": "advanced", "label": "advanced", "required":
false, "type": "boolean", "javaType": "boolean", "deprecated": false,
"autowired": false, "secret": false, "security": "insecure:serialization",
"defaultValue": false, "description": "If enabled and you are using Request
Reply messaging (InOut) and an Exchange failed on the consumer side, then the
caused Exception will be send back in res [...]
+ "transferException": { "index": 49, "kind": "parameter", "displayName":
"Transfer Exception", "group": "advanced", "label": "advanced", "required":
false, "type": "boolean", "javaType": "boolean", "deprecated": false,
"autowired": false, "secret": false, "security": "insecure:serialization",
"defaultValue": false, "description": "If enabled and you are using Request
Reply messaging (InOut) and an Exchange failed on the consumer side, then the
caused Exception will be send back in res [...]
"batching": { "index": 50, "kind": "parameter", "displayName": "Batching",
"group": "batch", "label": "consumer,batch", "required": false, "type":
"boolean", "javaType": "boolean", "deprecated": false, "autowired": false,
"secret": false, "defaultValue": false, "description": "Enable batch consuming.
The route receives one Exchange per batch, whose body is a List of the
individual JMS messages, instead of one Exchange per message." },
"batchInterval": { "index": 51, "kind": "parameter", "displayName": "Batch
Interval", "group": "batch", "label": "consumer,batch", "required": false,
"type": "duration", "javaType": "long", "deprecated": false, "autowired":
false, "secret": false, "defaultValue": "1000", "description": "Time in millis,
measured from the first message received into a new batch, after which the
batch is dispatched even if batchSize has not been reached, comparable to the
Aggregator EIP's completionInte [...]
"batchSize": { "index": 52, "kind": "parameter", "displayName": "Batch
Size", "group": "batch", "label": "consumer,batch", "required": false, "type":
"integer", "javaType": "int", "deprecated": false, "autowired": false,
"secret": false, "defaultValue": 100, "description": "Maximum number of
messages per batch." },
diff --git
a/components/camel-sjms/src/generated/resources/META-INF/org/apache/camel/component/sjms/sjms.json
b/components/camel-sjms/src/generated/resources/META-INF/org/apache/camel/component/sjms/sjms.json
index 4f76c1f5e2ea..a2ab3a0a85af 100644
---
a/components/camel-sjms/src/generated/resources/META-INF/org/apache/camel/component/sjms/sjms.json
+++
b/components/camel-sjms/src/generated/resources/META-INF/org/apache/camel/component/sjms/sjms.json
@@ -100,7 +100,7 @@
"objectMessageEnabled": { "index": 43, "kind": "parameter", "displayName":
"Object Message Enabled", "group": "advanced", "label": "advanced", "required":
false, "type": "boolean", "javaType": "boolean", "deprecated": false,
"autowired": false, "secret": false, "security": "insecure:serialization",
"defaultValue": false, "description": "Whether to enable sending and receiving
JMS ObjectMessage. By default this is disabled because Java object
serialization is a known source of securit [...]
"recoveryInterval": { "index": 44, "kind": "parameter", "displayName":
"Recovery Interval", "group": "advanced", "label": "advanced", "required":
false, "type": "duration", "javaType": "long", "deprecated": false,
"autowired": false, "secret": false, "defaultValue": "5000", "description":
"Specifies the interval between recovery attempts, i.e. when a connection is
being refreshed, in milliseconds. The default is 5000 ms, that is, 5 seconds."
},
"synchronous": { "index": 45, "kind": "parameter", "displayName":
"Synchronous", "group": "advanced", "label": "advanced", "required": false,
"type": "boolean", "javaType": "boolean", "deprecated": false, "autowired":
false, "secret": false, "defaultValue": false, "description": "Sets whether
synchronous processing should be strictly used" },
- "transferException": { "index": 46, "kind": "parameter", "displayName":
"Transfer Exception", "group": "advanced", "label": "advanced", "required":
false, "type": "boolean", "javaType": "boolean", "deprecated": false,
"autowired": false, "secret": false, "security": "insecure:serialization",
"defaultValue": false, "description": "If enabled and you are using Request
Reply messaging (InOut) and an Exchange failed on the consumer side, then the
caused Exception will be send back in res [...]
+ "transferException": { "index": 46, "kind": "parameter", "displayName":
"Transfer Exception", "group": "advanced", "label": "advanced", "required":
false, "type": "boolean", "javaType": "boolean", "deprecated": false,
"autowired": false, "secret": false, "security": "insecure:serialization",
"defaultValue": false, "description": "If enabled and you are using Request
Reply messaging (InOut) and an Exchange failed on the consumer side, then the
caused Exception will be send back in res [...]
"batching": { "index": 47, "kind": "parameter", "displayName": "Batching",
"group": "batch", "label": "consumer,batch", "required": false, "type":
"boolean", "javaType": "boolean", "deprecated": false, "autowired": false,
"secret": false, "defaultValue": false, "description": "Enable batch consuming.
The route receives one Exchange per batch, whose body is a List of the
individual JMS messages, instead of one Exchange per message." },
"batchInterval": { "index": 48, "kind": "parameter", "displayName": "Batch
Interval", "group": "batch", "label": "consumer,batch", "required": false,
"type": "duration", "javaType": "long", "deprecated": false, "autowired":
false, "secret": false, "defaultValue": "1000", "description": "Time in millis,
measured from the first message received into a new batch, after which the
batch is dispatched even if batchSize has not been reached, comparable to the
Aggregator EIP's completionInte [...]
"batchSize": { "index": 49, "kind": "parameter", "displayName": "Batch
Size", "group": "batch", "label": "consumer,batch", "required": false, "type":
"integer", "javaType": "int", "deprecated": false, "autowired": false,
"secret": false, "defaultValue": 100, "description": "Maximum number of
messages per batch." },
diff --git
a/components/camel-sjms/src/main/java/org/apache/camel/component/sjms/SjmsEndpoint.java
b/components/camel-sjms/src/main/java/org/apache/camel/component/sjms/SjmsEndpoint.java
index 62fdbc00b175..199db6762a0d 100644
---
a/components/camel-sjms/src/main/java/org/apache/camel/component/sjms/SjmsEndpoint.java
+++
b/components/camel-sjms/src/main/java/org/apache/camel/component/sjms/SjmsEndpoint.java
@@ -313,7 +313,6 @@ public class SjmsEndpoint extends DefaultEndpoint
+ " then the caused Exception will be send back in
response as a jakarta.jms.ObjectMessage."
+ " If the client is Camel, the returned Exception
is rethrown. This allows you to use Camel JMS as a bridge"
+ " in your routing - for example, using
persistent queues to enable robust routing."
- + " Notice that if you also have transferExchange
enabled, this option takes precedence."
+ " The caught exception is required to be
serializable."
+ " The original Exception on the consumer side
can be wrapped in an outer exception"
+ " such as org.apache.camel.RuntimeCamelException
when returned to the producer."
diff --git
a/components/camel-sjms2/src/generated/resources/META-INF/org/apache/camel/component/sjms2/sjms2.json
b/components/camel-sjms2/src/generated/resources/META-INF/org/apache/camel/component/sjms2/sjms2.json
index fd31be61e94f..d791bd456ddb 100644
---
a/components/camel-sjms2/src/generated/resources/META-INF/org/apache/camel/component/sjms2/sjms2.json
+++
b/components/camel-sjms2/src/generated/resources/META-INF/org/apache/camel/component/sjms2/sjms2.json
@@ -103,7 +103,7 @@
"objectMessageEnabled": { "index": 46, "kind": "parameter", "displayName":
"Object Message Enabled", "group": "advanced", "label": "advanced", "required":
false, "type": "boolean", "javaType": "boolean", "deprecated": false,
"autowired": false, "secret": false, "security": "insecure:serialization",
"defaultValue": false, "description": "Whether to enable sending and receiving
JMS ObjectMessage. By default this is disabled because Java object
serialization is a known source of securit [...]
"recoveryInterval": { "index": 47, "kind": "parameter", "displayName":
"Recovery Interval", "group": "advanced", "label": "advanced", "required":
false, "type": "duration", "javaType": "long", "deprecated": false,
"autowired": false, "secret": false, "defaultValue": "5000", "description":
"Specifies the interval between recovery attempts, i.e. when a connection is
being refreshed, in milliseconds. The default is 5000 ms, that is, 5 seconds."
},
"synchronous": { "index": 48, "kind": "parameter", "displayName":
"Synchronous", "group": "advanced", "label": "advanced", "required": false,
"type": "boolean", "javaType": "boolean", "deprecated": false, "autowired":
false, "secret": false, "defaultValue": false, "description": "Sets whether
synchronous processing should be strictly used" },
- "transferException": { "index": 49, "kind": "parameter", "displayName":
"Transfer Exception", "group": "advanced", "label": "advanced", "required":
false, "type": "boolean", "javaType": "boolean", "deprecated": false,
"autowired": false, "secret": false, "security": "insecure:serialization",
"defaultValue": false, "description": "If enabled and you are using Request
Reply messaging (InOut) and an Exchange failed on the consumer side, then the
caused Exception will be send back in res [...]
+ "transferException": { "index": 49, "kind": "parameter", "displayName":
"Transfer Exception", "group": "advanced", "label": "advanced", "required":
false, "type": "boolean", "javaType": "boolean", "deprecated": false,
"autowired": false, "secret": false, "security": "insecure:serialization",
"defaultValue": false, "description": "If enabled and you are using Request
Reply messaging (InOut) and an Exchange failed on the consumer side, then the
caused Exception will be send back in res [...]
"batching": { "index": 50, "kind": "parameter", "displayName": "Batching",
"group": "batch", "label": "consumer,batch", "required": false, "type":
"boolean", "javaType": "boolean", "deprecated": false, "autowired": false,
"secret": false, "defaultValue": false, "description": "Enable batch consuming.
The route receives one Exchange per batch, whose body is a List of the
individual JMS messages, instead of one Exchange per message." },
"batchInterval": { "index": 51, "kind": "parameter", "displayName": "Batch
Interval", "group": "batch", "label": "consumer,batch", "required": false,
"type": "duration", "javaType": "long", "deprecated": false, "autowired":
false, "secret": false, "defaultValue": "1000", "description": "Time in millis,
measured from the first message received into a new batch, after which the
batch is dispatched even if batchSize has not been reached, comparable to the
Aggregator EIP's completionInte [...]
"batchSize": { "index": 52, "kind": "parameter", "displayName": "Batch
Size", "group": "batch", "label": "consumer,batch", "required": false, "type":
"integer", "javaType": "int", "deprecated": false, "autowired": false,
"secret": false, "defaultValue": 100, "description": "Maximum number of
messages per batch." },
diff --git
a/dsl/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/dsl/Sjms2EndpointBuilderFactory.java
b/dsl/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/dsl/Sjms2EndpointBuilderFactory.java
index 844f83eb28b6..9112aff8e5db 100644
---
a/dsl/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/dsl/Sjms2EndpointBuilderFactory.java
+++
b/dsl/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/dsl/Sjms2EndpointBuilderFactory.java
@@ -1309,15 +1309,14 @@ public interface Sjms2EndpointBuilderFactory {
* be send back in response as a jakarta.jms.ObjectMessage. If the
* client is Camel, the returned Exception is rethrown. This allows you
* to use Camel JMS as a bridge in your routing - for example, using
- * persistent queues to enable robust routing. Notice that if you also
- * have transferExchange enabled, this option takes precedence. The
- * caught exception is required to be serializable. The original
- * Exception on the consumer side can be wrapped in an outer exception
- * such as org.apache.camel.RuntimeCamelException when returned to the
- * producer. Use this with caution as the data is using Java Object
- * serialization and requires the received to be able to deserialize
the
- * data at Class level, which forces a strong coupling between the
- * producers and consumer!.
+ * persistent queues to enable robust routing. The caught exception is
+ * required to be serializable. The original Exception on the consumer
+ * side can be wrapped in an outer exception such as
+ * org.apache.camel.RuntimeCamelException when returned to the
producer.
+ * Use this with caution as the data is using Java Object serialization
+ * and requires the received to be able to deserialize the data at
Class
+ * level, which forces a strong coupling between the producers and
+ * consumer!.
*
* The option is a: <code>boolean</code> type.
*
@@ -1337,15 +1336,14 @@ public interface Sjms2EndpointBuilderFactory {
* be send back in response as a jakarta.jms.ObjectMessage. If the
* client is Camel, the returned Exception is rethrown. This allows you
* to use Camel JMS as a bridge in your routing - for example, using
- * persistent queues to enable robust routing. Notice that if you also
- * have transferExchange enabled, this option takes precedence. The
- * caught exception is required to be serializable. The original
- * Exception on the consumer side can be wrapped in an outer exception
- * such as org.apache.camel.RuntimeCamelException when returned to the
- * producer. Use this with caution as the data is using Java Object
- * serialization and requires the received to be able to deserialize
the
- * data at Class level, which forces a strong coupling between the
- * producers and consumer!.
+ * persistent queues to enable robust routing. The caught exception is
+ * required to be serializable. The original Exception on the consumer
+ * side can be wrapped in an outer exception such as
+ * org.apache.camel.RuntimeCamelException when returned to the
producer.
+ * Use this with caution as the data is using Java Object serialization
+ * and requires the received to be able to deserialize the data at
Class
+ * level, which forces a strong coupling between the producers and
+ * consumer!.
*
* The option will be converted to a <code>boolean</code> type.
*
@@ -2541,15 +2539,14 @@ public interface Sjms2EndpointBuilderFactory {
* be send back in response as a jakarta.jms.ObjectMessage. If the
* client is Camel, the returned Exception is rethrown. This allows you
* to use Camel JMS as a bridge in your routing - for example, using
- * persistent queues to enable robust routing. Notice that if you also
- * have transferExchange enabled, this option takes precedence. The
- * caught exception is required to be serializable. The original
- * Exception on the consumer side can be wrapped in an outer exception
- * such as org.apache.camel.RuntimeCamelException when returned to the
- * producer. Use this with caution as the data is using Java Object
- * serialization and requires the received to be able to deserialize
the
- * data at Class level, which forces a strong coupling between the
- * producers and consumer!.
+ * persistent queues to enable robust routing. The caught exception is
+ * required to be serializable. The original Exception on the consumer
+ * side can be wrapped in an outer exception such as
+ * org.apache.camel.RuntimeCamelException when returned to the
producer.
+ * Use this with caution as the data is using Java Object serialization
+ * and requires the received to be able to deserialize the data at
Class
+ * level, which forces a strong coupling between the producers and
+ * consumer!.
*
* The option is a: <code>boolean</code> type.
*
@@ -2569,15 +2566,14 @@ public interface Sjms2EndpointBuilderFactory {
* be send back in response as a jakarta.jms.ObjectMessage. If the
* client is Camel, the returned Exception is rethrown. This allows you
* to use Camel JMS as a bridge in your routing - for example, using
- * persistent queues to enable robust routing. Notice that if you also
- * have transferExchange enabled, this option takes precedence. The
- * caught exception is required to be serializable. The original
- * Exception on the consumer side can be wrapped in an outer exception
- * such as org.apache.camel.RuntimeCamelException when returned to the
- * producer. Use this with caution as the data is using Java Object
- * serialization and requires the received to be able to deserialize
the
- * data at Class level, which forces a strong coupling between the
- * producers and consumer!.
+ * persistent queues to enable robust routing. The caught exception is
+ * required to be serializable. The original Exception on the consumer
+ * side can be wrapped in an outer exception such as
+ * org.apache.camel.RuntimeCamelException when returned to the
producer.
+ * Use this with caution as the data is using Java Object serialization
+ * and requires the received to be able to deserialize the data at
Class
+ * level, which forces a strong coupling between the producers and
+ * consumer!.
*
* The option will be converted to a <code>boolean</code> type.
*
@@ -3310,15 +3306,14 @@ public interface Sjms2EndpointBuilderFactory {
* be send back in response as a jakarta.jms.ObjectMessage. If the
* client is Camel, the returned Exception is rethrown. This allows you
* to use Camel JMS as a bridge in your routing - for example, using
- * persistent queues to enable robust routing. Notice that if you also
- * have transferExchange enabled, this option takes precedence. The
- * caught exception is required to be serializable. The original
- * Exception on the consumer side can be wrapped in an outer exception
- * such as org.apache.camel.RuntimeCamelException when returned to the
- * producer. Use this with caution as the data is using Java Object
- * serialization and requires the received to be able to deserialize
the
- * data at Class level, which forces a strong coupling between the
- * producers and consumer!.
+ * persistent queues to enable robust routing. The caught exception is
+ * required to be serializable. The original Exception on the consumer
+ * side can be wrapped in an outer exception such as
+ * org.apache.camel.RuntimeCamelException when returned to the
producer.
+ * Use this with caution as the data is using Java Object serialization
+ * and requires the received to be able to deserialize the data at
Class
+ * level, which forces a strong coupling between the producers and
+ * consumer!.
*
* The option is a: <code>boolean</code> type.
*
@@ -3338,15 +3333,14 @@ public interface Sjms2EndpointBuilderFactory {
* be send back in response as a jakarta.jms.ObjectMessage. If the
* client is Camel, the returned Exception is rethrown. This allows you
* to use Camel JMS as a bridge in your routing - for example, using
- * persistent queues to enable robust routing. Notice that if you also
- * have transferExchange enabled, this option takes precedence. The
- * caught exception is required to be serializable. The original
- * Exception on the consumer side can be wrapped in an outer exception
- * such as org.apache.camel.RuntimeCamelException when returned to the
- * producer. Use this with caution as the data is using Java Object
- * serialization and requires the received to be able to deserialize
the
- * data at Class level, which forces a strong coupling between the
- * producers and consumer!.
+ * persistent queues to enable robust routing. The caught exception is
+ * required to be serializable. The original Exception on the consumer
+ * side can be wrapped in an outer exception such as
+ * org.apache.camel.RuntimeCamelException when returned to the
producer.
+ * Use this with caution as the data is using Java Object serialization
+ * and requires the received to be able to deserialize the data at
Class
+ * level, which forces a strong coupling between the producers and
+ * consumer!.
*
* The option will be converted to a <code>boolean</code> type.
*
diff --git
a/dsl/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/dsl/SjmsEndpointBuilderFactory.java
b/dsl/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/dsl/SjmsEndpointBuilderFactory.java
index 97613d7dd6b4..b6f287d66985 100644
---
a/dsl/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/dsl/SjmsEndpointBuilderFactory.java
+++
b/dsl/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/dsl/SjmsEndpointBuilderFactory.java
@@ -1234,15 +1234,14 @@ public interface SjmsEndpointBuilderFactory {
* be send back in response as a jakarta.jms.ObjectMessage. If the
* client is Camel, the returned Exception is rethrown. This allows you
* to use Camel JMS as a bridge in your routing - for example, using
- * persistent queues to enable robust routing. Notice that if you also
- * have transferExchange enabled, this option takes precedence. The
- * caught exception is required to be serializable. The original
- * Exception on the consumer side can be wrapped in an outer exception
- * such as org.apache.camel.RuntimeCamelException when returned to the
- * producer. Use this with caution as the data is using Java Object
- * serialization and requires the received to be able to deserialize
the
- * data at Class level, which forces a strong coupling between the
- * producers and consumer!.
+ * persistent queues to enable robust routing. The caught exception is
+ * required to be serializable. The original Exception on the consumer
+ * side can be wrapped in an outer exception such as
+ * org.apache.camel.RuntimeCamelException when returned to the
producer.
+ * Use this with caution as the data is using Java Object serialization
+ * and requires the received to be able to deserialize the data at
Class
+ * level, which forces a strong coupling between the producers and
+ * consumer!.
*
* The option is a: <code>boolean</code> type.
*
@@ -1262,15 +1261,14 @@ public interface SjmsEndpointBuilderFactory {
* be send back in response as a jakarta.jms.ObjectMessage. If the
* client is Camel, the returned Exception is rethrown. This allows you
* to use Camel JMS as a bridge in your routing - for example, using
- * persistent queues to enable robust routing. Notice that if you also
- * have transferExchange enabled, this option takes precedence. The
- * caught exception is required to be serializable. The original
- * Exception on the consumer side can be wrapped in an outer exception
- * such as org.apache.camel.RuntimeCamelException when returned to the
- * producer. Use this with caution as the data is using Java Object
- * serialization and requires the received to be able to deserialize
the
- * data at Class level, which forces a strong coupling between the
- * producers and consumer!.
+ * persistent queues to enable robust routing. The caught exception is
+ * required to be serializable. The original Exception on the consumer
+ * side can be wrapped in an outer exception such as
+ * org.apache.camel.RuntimeCamelException when returned to the
producer.
+ * Use this with caution as the data is using Java Object serialization
+ * and requires the received to be able to deserialize the data at
Class
+ * level, which forces a strong coupling between the producers and
+ * consumer!.
*
* The option will be converted to a <code>boolean</code> type.
*
@@ -2466,15 +2464,14 @@ public interface SjmsEndpointBuilderFactory {
* be send back in response as a jakarta.jms.ObjectMessage. If the
* client is Camel, the returned Exception is rethrown. This allows you
* to use Camel JMS as a bridge in your routing - for example, using
- * persistent queues to enable robust routing. Notice that if you also
- * have transferExchange enabled, this option takes precedence. The
- * caught exception is required to be serializable. The original
- * Exception on the consumer side can be wrapped in an outer exception
- * such as org.apache.camel.RuntimeCamelException when returned to the
- * producer. Use this with caution as the data is using Java Object
- * serialization and requires the received to be able to deserialize
the
- * data at Class level, which forces a strong coupling between the
- * producers and consumer!.
+ * persistent queues to enable robust routing. The caught exception is
+ * required to be serializable. The original Exception on the consumer
+ * side can be wrapped in an outer exception such as
+ * org.apache.camel.RuntimeCamelException when returned to the
producer.
+ * Use this with caution as the data is using Java Object serialization
+ * and requires the received to be able to deserialize the data at
Class
+ * level, which forces a strong coupling between the producers and
+ * consumer!.
*
* The option is a: <code>boolean</code> type.
*
@@ -2494,15 +2491,14 @@ public interface SjmsEndpointBuilderFactory {
* be send back in response as a jakarta.jms.ObjectMessage. If the
* client is Camel, the returned Exception is rethrown. This allows you
* to use Camel JMS as a bridge in your routing - for example, using
- * persistent queues to enable robust routing. Notice that if you also
- * have transferExchange enabled, this option takes precedence. The
- * caught exception is required to be serializable. The original
- * Exception on the consumer side can be wrapped in an outer exception
- * such as org.apache.camel.RuntimeCamelException when returned to the
- * producer. Use this with caution as the data is using Java Object
- * serialization and requires the received to be able to deserialize
the
- * data at Class level, which forces a strong coupling between the
- * producers and consumer!.
+ * persistent queues to enable robust routing. The caught exception is
+ * required to be serializable. The original Exception on the consumer
+ * side can be wrapped in an outer exception such as
+ * org.apache.camel.RuntimeCamelException when returned to the
producer.
+ * Use this with caution as the data is using Java Object serialization
+ * and requires the received to be able to deserialize the data at
Class
+ * level, which forces a strong coupling between the producers and
+ * consumer!.
*
* The option will be converted to a <code>boolean</code> type.
*
@@ -3235,15 +3231,14 @@ public interface SjmsEndpointBuilderFactory {
* be send back in response as a jakarta.jms.ObjectMessage. If the
* client is Camel, the returned Exception is rethrown. This allows you
* to use Camel JMS as a bridge in your routing - for example, using
- * persistent queues to enable robust routing. Notice that if you also
- * have transferExchange enabled, this option takes precedence. The
- * caught exception is required to be serializable. The original
- * Exception on the consumer side can be wrapped in an outer exception
- * such as org.apache.camel.RuntimeCamelException when returned to the
- * producer. Use this with caution as the data is using Java Object
- * serialization and requires the received to be able to deserialize
the
- * data at Class level, which forces a strong coupling between the
- * producers and consumer!.
+ * persistent queues to enable robust routing. The caught exception is
+ * required to be serializable. The original Exception on the consumer
+ * side can be wrapped in an outer exception such as
+ * org.apache.camel.RuntimeCamelException when returned to the
producer.
+ * Use this with caution as the data is using Java Object serialization
+ * and requires the received to be able to deserialize the data at
Class
+ * level, which forces a strong coupling between the producers and
+ * consumer!.
*
* The option is a: <code>boolean</code> type.
*
@@ -3263,15 +3258,14 @@ public interface SjmsEndpointBuilderFactory {
* be send back in response as a jakarta.jms.ObjectMessage. If the
* client is Camel, the returned Exception is rethrown. This allows you
* to use Camel JMS as a bridge in your routing - for example, using
- * persistent queues to enable robust routing. Notice that if you also
- * have transferExchange enabled, this option takes precedence. The
- * caught exception is required to be serializable. The original
- * Exception on the consumer side can be wrapped in an outer exception
- * such as org.apache.camel.RuntimeCamelException when returned to the
- * producer. Use this with caution as the data is using Java Object
- * serialization and requires the received to be able to deserialize
the
- * data at Class level, which forces a strong coupling between the
- * producers and consumer!.
+ * persistent queues to enable robust routing. The caught exception is
+ * required to be serializable. The original Exception on the consumer
+ * side can be wrapped in an outer exception such as
+ * org.apache.camel.RuntimeCamelException when returned to the
producer.
+ * Use this with caution as the data is using Java Object serialization
+ * and requires the received to be able to deserialize the data at
Class
+ * level, which forces a strong coupling between the producers and
+ * consumer!.
*
* The option will be converted to a <code>boolean</code> type.
*
