This is an automated email from the ASF dual-hosted git repository.
orpiske pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git
commit 04d2918334107b9b5a3c9bed7e62bc5bb76aeb6d
Author: Otavio R. Piske <angusyo...@gmail.com>
AuthorDate: Sat Feb 24 11:52:34 2024 +0100
CAMEL-20459: documentation fixes for the composed message processor EIP.
Signed-off-by: Otavio R. Piske <angusyo...@gmail.com>
---
.../main/docs/modules/eips/pages/composed-message-processor.adoc | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
a/core/camel-core-engine/src/main/docs/modules/eips/pages/composed-message-processor.adoc
b/core/camel-core-engine/src/main/docs/modules/eips/pages/composed-message-processor.adoc
index 8f55d3945aa..fe1d0d2cb7c 100644
---
a/core/camel-core-engine/src/main/docs/modules/eips/pages/composed-message-processor.adoc
+++
b/core/camel-core-engine/src/main/docs/modules/eips/pages/composed-message-processor.adoc
@@ -12,7 +12,7 @@ Use Composed Message Processor to process a composite message.
The Composed Message Processor splits the message up, routes the sub-messages
to the appropriate destinations
and re-aggregates the responses back into a single message.
-With Camel this pattern is implemented by the xref:split-eip.adoc[Splitter]
+With Camel, this pattern is implemented by the xref:split-eip.adoc[Splitter]
which has built-in aggregation to re-aggregate the responses back into a
single message.
== Example
@@ -20,7 +20,7 @@ which has built-in aggregation to re-aggregate the responses
back into a single
This example uses the xref:split-eip.adoc[Split] EIP as composed message
processor to process each split message,
aggregate and return a single combined response.
-The route and the code comments below explains how you can use the
xref:split-eip.adoc[Split] EIP to
+The route and the code comments below explain how you can use the
xref:split-eip.adoc[Split] EIP to
split each message to sub-message which are processed individually and then
combined back into
a single response message via the custom `AggregationStrategy`
(`MyOrderStrategy`), as the output from the Split EIP.
@@ -28,7 +28,7 @@ a single response message via the custom
`AggregationStrategy` (`MyOrderStrategy
----
// this routes starts from the direct:start endpoint
// the body is then split based on @ separator
-// the splitter in Camel supports InOut as well and for that we need
+// the splitter in Camel supports InOut as well, and for that we need
// to be able to aggregate what response we need to send back, so we provide
our
// own strategy with the class MyOrderStrategy.
from("direct:start")
@@ -38,7 +38,7 @@ from("direct:start")
// this is important to end the splitter route as we do not want to do
more routing
// on each split message
.end()
- // after we have split and handled each message we want to send a single
combined
+ // after we have split and handled each message, we want to send a single
combined
// response back to the original caller, so we let this bean build it for
us
// this bean will receive the result of the aggregate strategy:
MyOrderStrategy
.to("bean:MyOrderService?method=buildCombinedResponse")
