This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch camel-3.21.x
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/camel-3.21.x by this push:
new 056ea5333a9 Regen
056ea5333a9 is described below
commit 056ea5333a9fb31aa0640ecf15b897a1250a0609
Author: Claus Ibsen <[email protected]>
AuthorDate: Thu Sep 21 18:29:27 2023 +0200
Regen
---
camel-dependencies/pom.xml | 4 +-
.../apache/camel/catalog/schemas/camel-spring.xsd | 148 +++++++++++++--------
2 files changed, 93 insertions(+), 59 deletions(-)
diff --git a/camel-dependencies/pom.xml b/camel-dependencies/pom.xml
index 1b5eed95a76..bda841ed0f0 100644
--- a/camel-dependencies/pom.xml
+++ b/camel-dependencies/pom.xml
@@ -271,7 +271,7 @@
<influx-java-driver-version>2.22</influx-java-driver-version>
<irclib-version>1.10</irclib-version>
<ironmq-version>3.0.5</ironmq-version>
- <ivy-version>2.5.1</ivy-version>
+ <ivy-version>2.5.2</ivy-version>
<jackrabbit-version>2.21.18</jackrabbit-version>
<jackson-jq-version>1.0.0-preview.20220705</jackson-jq-version>
<jackson-version>1.9.12</jackson-version>
@@ -521,7 +521,7 @@
<spring-integration-version>5.5.17</spring-integration-version>
<spring-ldap-version>2.4.1</spring-ldap-version>
<spring-rabbitmq-version>2.4.8</spring-rabbitmq-version>
- <spring-security-version>5.8.5</spring-security-version>
+ <spring-security-version>5.8.7</spring-security-version>
<spring-vault-core-version>2.3.3</spring-vault-core-version>
<spring-version>${spring5-version}</spring-version>
<spring-version-range>[5,6)</spring-version-range>
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/schemas/camel-spring.xsd
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/schemas/camel-spring.xsd
index c1598f379c9..69b09ac8743 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/schemas/camel-spring.xsd
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/schemas/camel-spring.xsd
@@ -5742,20 +5742,24 @@ with custom headers and include the original message
body. The former wont let
you do this, as its using the original message body and headers as they are.
You
cannot enable both useOriginalMessage and useOriginalBody. The original input
message is defensively copied, and the copied message body is converted to
-org.apache.camel.StreamCache if possible, to ensure the body can be read when
-the original message is being used later. If the body is not converted to
-org.apache.camel.StreamCache then the body will not be able to re-read when
-accessed later. Important: The original input means the input message that are
-bounded by the current org.apache.camel.spi.UnitOfWork . An unit of work
-typically spans one route, or multiple routes if they are connected using
-internal endpoints such as direct or seda. When messages is passed via external
-endpoints such as JMS or HTTP then the consumer will create a new unit of work,
-with the message it received as input as the original input. Also some EIP
-patterns such as splitter, multicast, will create a new unit of work boundary
-for the messages in their sub-route (eg the splitted message); however these
-EIPs have an option named shareUnitOfWork which allows to combine with the
-parent unit of work in regard to error handling and therefore use the parent
-original message. By default this feature is off. Default value: false
+org.apache.camel.StreamCache if possible (stream caching is enabled, can be
+disabled globally or on the original route), to ensure the body can be read
when
+the original message is being used later. If the body is converted to
+org.apache.camel.StreamCache then the message body on the current
+org.apache.camel.Exchange is replaced with the org.apache.camel.StreamCache
+body. If the body is not converted to org.apache.camel.StreamCache then the
body
+will not be able to re-read when accessed later. Important: The original input
+means the input message that are bounded by the current
+org.apache.camel.spi.UnitOfWork . An unit of work typically spans one route, or
+multiple routes if they are connected using internal endpoints such as direct
or
+seda. When messages is passed via external endpoints such as JMS or HTTP then
+the consumer will create a new unit of work, with the message it received as
+input as the original input. Also some EIP patterns such as splitter,
multicast,
+will create a new unit of work boundary for the messages in their sub-route (eg
+the splitted message); however these EIPs have an option named shareUnitOfWork
+which allows to combine with the parent unit of work in regard to error
handling
+and therefore use the parent original message. By default this feature is off.
+Default value: false
]]></xs:documentation>
</xs:annotation>
</xs:attribute>
@@ -5781,20 +5785,24 @@ with custom headers and include the original message
body. The former wont let
you do this, as its using the original message body and headers as they are.
You
cannot enable both useOriginalMessage and useOriginalBody. The original input
message is defensively copied, and the copied message body is converted to
-org.apache.camel.StreamCache if possible, to ensure the body can be read when
-the original message is being used later. If the body is not converted to
-org.apache.camel.StreamCache then the body will not be able to re-read when
-accessed later. Important: The original input means the input message that are
-bounded by the current org.apache.camel.spi.UnitOfWork . An unit of work
-typically spans one route, or multiple routes if they are connected using
-internal endpoints such as direct or seda. When messages is passed via external
-endpoints such as JMS or HTTP then the consumer will create a new unit of work,
-with the message it received as input as the original input. Also some EIP
-patterns such as splitter, multicast, will create a new unit of work boundary
-for the messages in their sub-route (eg the splitted message); however these
-EIPs have an option named shareUnitOfWork which allows to combine with the
-parent unit of work in regard to error handling and therefore use the parent
-original message. By default this feature is off. Default value: false
+org.apache.camel.StreamCache if possible (stream caching is enabled, can be
+disabled globally or on the original route), to ensure the body can be read
when
+the original message is being used later. If the body is converted to
+org.apache.camel.StreamCache then the message body on the current
+org.apache.camel.Exchange is replaced with the org.apache.camel.StreamCache
+body. If the body is not converted to org.apache.camel.StreamCache then the
body
+will not be able to re-read when accessed later. Important: The original input
+means the input message that are bounded by the current
+org.apache.camel.spi.UnitOfWork . An unit of work typically spans one route, or
+multiple routes if they are connected using internal endpoints such as direct
or
+seda. When messages is passed via external endpoints such as JMS or HTTP then
+the consumer will create a new unit of work, with the message it received as
+input as the original input. Also some EIP patterns such as splitter,
multicast,
+will create a new unit of work boundary for the messages in their sub-route (eg
+the splitted message); however these EIPs have an option named shareUnitOfWork
+which allows to combine with the parent unit of work in regard to error
handling
+and therefore use the parent original message. By default this feature is off.
+Default value: false
]]></xs:documentation>
</xs:annotation>
</xs:attribute>
@@ -12235,7 +12243,25 @@ have to enable that option as well.
<xs:annotation>
<xs:documentation xml:lang="en"><![CDATA[
Will use the original input message body when an org.apache.camel.Exchange for
-this on completion. By default this feature is off. Default value: false
+this on completion. The original input message is defensively copied, and the
+copied message body is converted to org.apache.camel.StreamCache if possible
+(stream caching is enabled, can be disabled globally or on the original route),
+to ensure the body can be read when the original message is being used later.
If
+the body is converted to org.apache.camel.StreamCache then the message body on
+the current org.apache.camel.Exchange is replaced with the
+org.apache.camel.StreamCache body. If the body is not converted to
+org.apache.camel.StreamCache then the body will not be able to re-read when
+accessed later. Important: The original input means the input message that are
+bounded by the current org.apache.camel.spi.UnitOfWork . An unit of work
+typically spans one route, or multiple routes if they are connected using
+internal endpoints such as direct or seda. When messages is passed via external
+endpoints such as JMS or HTTP then the consumer will create a new unit of work,
+with the message it received as input as the original input. Also some EIP
+patterns such as splitter, multicast, will create a new unit of work boundary
+for the messages in their sub-route (eg the split message); however these EIPs
+have an option named shareUnitOfWork which allows to combine with the parent
+unit of work in regard to error handling and therefore use the parent original
+message. By default this feature is off. Default value: false
]]></xs:documentation>
</xs:annotation>
</xs:attribute>
@@ -12491,20 +12517,24 @@ with custom headers and include the original message
body. The former wont let
you do this, as its using the original message body and headers as they are.
You
cannot enable both useOriginalMessage and useOriginalBody. The original input
message is defensively copied, and the copied message body is converted to
-org.apache.camel.StreamCache if possible, to ensure the body can be read when
-the original message is being used later. If the body is not converted to
-org.apache.camel.StreamCache then the body will not be able to re-read when
-accessed later. Important: The original input means the input message that are
-bounded by the current org.apache.camel.spi.UnitOfWork . An unit of work
-typically spans one route, or multiple routes if they are connected using
-internal endpoints such as direct or seda. When messages is passed via external
-endpoints such as JMS or HTTP then the consumer will create a new unit of work,
-with the message it received as input as the original input. Also some EIP
-patterns such as splitter, multicast, will create a new unit of work boundary
-for the messages in their sub-route (eg the split message); however these EIPs
-have an option named shareUnitOfWork which allows to combine with the parent
-unit of work in regard to error handling and therefore use the parent original
-message. By default this feature is off. Default value: false
+org.apache.camel.StreamCache if possible (stream caching is enabled, can be
+disabled globally or on the original route), to ensure the body can be read
when
+the original message is being used later. If the body is converted to
+org.apache.camel.StreamCache then the message body on the current
+org.apache.camel.Exchange is replaced with the org.apache.camel.StreamCache
+body. If the body is not converted to org.apache.camel.StreamCache then the
body
+will not be able to re-read when accessed later. Important: The original input
+means the input message that are bounded by the current
+org.apache.camel.spi.UnitOfWork . An unit of work typically spans one route, or
+multiple routes if they are connected using internal endpoints such as direct
or
+seda. When messages is passed via external endpoints such as JMS or HTTP then
+the consumer will create a new unit of work, with the message it received as
+input as the original input. Also some EIP patterns such as splitter,
multicast,
+will create a new unit of work boundary for the messages in their sub-route (eg
+the split message); however these EIPs have an option named shareUnitOfWork
+which allows to combine with the parent unit of work in regard to error
handling
+and therefore use the parent original message. By default this feature is off.
+Default value: false
]]></xs:documentation>
</xs:annotation>
</xs:attribute>
@@ -12530,20 +12560,24 @@ with custom headers and include the original message
body. The former wont let
you do this, as its using the original message body and headers as they are.
You
cannot enable both useOriginalMessage and useOriginalBody. The original input
message is defensively copied, and the copied message body is converted to
-org.apache.camel.StreamCache if possible, to ensure the body can be read when
-the original message is being used later. If the body is not converted to
-org.apache.camel.StreamCache then the body will not be able to re-read when
-accessed later. Important: The original input means the input message that are
-bounded by the current org.apache.camel.spi.UnitOfWork . An unit of work
-typically spans one route, or multiple routes if they are connected using
-internal endpoints such as direct or seda. When messages is passed via external
-endpoints such as JMS or HTTP then the consumer will create a new unit of work,
-with the message it received as input as the original input. Also some EIP
-patterns such as splitter, multicast, will create a new unit of work boundary
-for the messages in their sub-route (eg the split message); however these EIPs
-have an option named shareUnitOfWork which allows to combine with the parent
-unit of work in regard to error handling and therefore use the parent original
-message. By default this feature is off. Default value: false
+org.apache.camel.StreamCache if possible (stream caching is enabled, can be
+disabled globally or on the original route), to ensure the body can be read
when
+the original message is being used later. If the body is converted to
+org.apache.camel.StreamCache then the message body on the current
+org.apache.camel.Exchange is replaced with the org.apache.camel.StreamCache
+body. If the body is not converted to org.apache.camel.StreamCache then the
body
+will not be able to re-read when accessed later. Important: The original input
+means the input message that are bounded by the current
+org.apache.camel.spi.UnitOfWork . An unit of work typically spans one route, or
+multiple routes if they are connected using internal endpoints such as direct
or
+seda. When messages is passed via external endpoints such as JMS or HTTP then
+the consumer will create a new unit of work, with the message it received as
+input as the original input. Also some EIP patterns such as splitter,
multicast,
+will create a new unit of work boundary for the messages in their sub-route (eg
+the split message); however these EIPs have an option named shareUnitOfWork
+which allows to combine with the parent unit of work in regard to error
handling
+and therefore use the parent original message. By default this feature is off.
+Default value: false
]]></xs:documentation>
</xs:annotation>
</xs:attribute>
