[camel] branch camel-3.x updated: Fix saga-eip timeout description (#9472)

[zh...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

zhfeng pushed a commit to branch camel-3.x
in repository https://gitbox.apache.org/repos/asf/camel.git


The following commit(s) were added to refs/heads/camel-3.x by this push:
     new 16bc25d9ece Fix saga-eip timeout description (#9472)
16bc25d9ece is described below

commit 16bc25d9ece94bfd21fb88abbfd51faaafef68e7
Author: Zheng Feng <zh...@gmail.com>
AuthorDate: Tue Mar 7 20:40:40 2023 +0800

    Fix saga-eip timeout description (#9472)
---
 .../src/main/docs/modules/eips/pages/saga-eip.adoc            | 11 +++++------
 1 file changed, 5 insertions(+), 6 deletions(-)

diff --git a/core/camel-core-engine/src/main/docs/modules/eips/pages/saga-eip.adoc b/core/camel-core-engine/src/main/docs/modules/eips/pages/saga-eip.adoc
index 9fa2bca7214..47fd11fc230 100644
--- a/core/camel-core-engine/src/main/docs/modules/eips/pages/saga-eip.adoc
+++ b/core/camel-core-engine/src/main/docs/modules/eips/pages/saga-eip.adoc
@@ -145,11 +145,10 @@ Configuration can be done in the Spring Boot `application.yaml` file:
 [source,yaml]
 ----
 camel:
-  service:
-    lra:
-      enabled: true
-      coordinator-url: http://lra-service-host
-      local-participant-url: http://my-host-as-seen-by-lra-service:8080/context-path
+  lra:
+    enabled: true
+    coordinator-url: http://lra-service-host
+    local-participant-url: http://my-host-as-seen-by-lra-service:8080/context-path
 ----
 
 Once done, the Saga EIP can be directly used inside Camel routes, and it will use the LRA Saga Service under the hood.
@@ -355,7 +354,7 @@ from("direct:newOrder")
     .log("Order ${body} created");
 ----
 
-All participants (e.g. credit service, order service) can set their own timeout. The minimum value of those timeouts is taken as timeout for the saga when they are composed together.
+All participants (e.g. credit service, order service) can set their own timeout. When a participant joins an existing transaction, the timeout of the already active saga can be influenced. It should calculate the moment in time the saga would become eligible for cancellation based on the time which the request enters the method and the timeout. When this moment is earlier than the moment calculated for the saga at that time, this new moment becomes the timeout moment for the saga. So whe [...]
 
 A timeout can also be specified at saga level as follows: