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-website.git
The following commit(s) were added to refs/heads/main by this push:
new a44c9f73 Move schema to correct folder
a44c9f73 is described below
commit a44c9f73059c7d2eb344293f1801b8dc8db12b6f
Author: Claus Ibsen <claus.ib...@gmail.com>
AuthorDate: Sun Mar 9 13:46:21 2025 +0100
Move schema to correct folder
---
...el-spring-xml-4.10.2.xsd => camel-spring-4.10.2.xsd} | 0
.../camel-spring-3.22.4.xsd} | 0
static/schema/spring/camel-spring.xsd | 17 ++++++++++++++---
3 files changed, 14 insertions(+), 3 deletions(-)
diff --git a/static/schema/spring-xml/camel-spring-xml-4.10.2.xsd
b/static/schema/spring-xml/camel-spring-4.10.2.xsd
similarity index 100%
rename from static/schema/spring-xml/camel-spring-xml-4.10.2.xsd
rename to static/schema/spring-xml/camel-spring-4.10.2.xsd
diff --git a/static/schema/spring-xml/camel-spring-xml-3.22.4.xsd
b/static/schema/spring/camel-spring-3.22.4.xsd
similarity index 100%
rename from static/schema/spring-xml/camel-spring-xml-3.22.4.xsd
rename to static/schema/spring/camel-spring-3.22.4.xsd
diff --git a/static/schema/spring/camel-spring.xsd
b/static/schema/spring/camel-spring.xsd
index 06008c19..438dd6ef 100644
--- a/static/schema/spring/camel-spring.xsd
+++ b/static/schema/spring/camel-spring.xsd
@@ -10952,7 +10952,11 @@ If enabled then sending messages to the multicasts
occurs concurrently. Note the
messages has been fully processed, before it continues. Its only the sending
and processing the replies from the
multicasts which happens concurrently. When parallel processing is enabled,
then the Camel routing engin will continue
processing using last used thread from the parallel thread pool. However, if
you want to use the original thread that
-called the multicast, then make sure to enable the synchronous option as well.
Default value: false
+called the multicast, then make sure to enable the synchronous option as well.
In parallel processing mode, you may want
+to also synchronous = true to force this EIP to process the sub-tasks using
the upper bounds of the thread-pool. If
+using synchronous = false then Camel will allow its reactive routing engine to
use as many threads as possible, which
+may be available due to sub-tasks using other thread-pools such as
CompletableFuture.runAsync or others. Default value:
+false
]]>
</xs:documentation>
</xs:annotation>
@@ -11992,7 +11996,11 @@ If enabled then sending messages to the recipients
occurs concurrently. Note the
messages has been fully processed, before it continues. Its only the sending
and processing the replies from the
recipients which happens concurrently. When parallel processing is enabled,
then the Camel routing engin will continue
processing using last used thread from the parallel thread pool. However, if
you want to use the original thread that
-called the recipient list, then make sure to enable the synchronous option as
well. Default value: false
+called the recipient list, then make sure to enable the synchronous option as
well. In parallel processing mode, you may
+want to also synchronous = true to force this EIP to process the sub-tasks
using the upper bounds of the thread-pool. If
+using synchronous = false then Camel will allow its reactive routing engine to
use as many threads as possible, which
+may be available due to sub-tasks using other thread-pools such as
CompletableFuture.runAsync or others. Default value:
+false
]]>
</xs:documentation>
</xs:annotation>
@@ -13619,7 +13627,10 @@ If enabled then processing each split messages occurs
concurrently. Note the cal
messages has been fully processed, before it continues. It's only processing
the sub messages from the splitter which
happens concurrently. When parallel processing is enabled, then the Camel
routing engin will continue processing using
last used thread from the parallel thread pool. However, if you want to use
the original thread that called the
-splitter, then make sure to enable the synchronous option as well. Default
value: false
+splitter, then make sure to enable the synchronous option as well. In parallel
processing mode, you may want to also
+synchronous = true to force this EIP to process the sub-tasks using the upper
bounds of the thread-pool. If using
+synchronous = false then Camel will allow its reactive routing engine to use
as many threads as possible, which may be
+available due to sub-tasks using other thread-pools such as
CompletableFuture.runAsync or others. Default value: false
]]>
</xs:documentation>
</xs:annotation>
