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 2245f5c1eb1 Typos in kamelet component and added link in MicroProfile
Fault Tolerance component documentation (#7893)
2245f5c1eb1 is described below
commit 2245f5c1eb1c63ec0beaaf598cc476bb6038a1ff
Author: lfabriko <[email protected]>
AuthorDate: Mon Jun 27 13:14:38 2022 +0200
Typos in kamelet component and added link in MicroProfile Fault Tolerance
component documentation (#7893)
* Typos in kamelet component documentation
* Added link to Circuit Breaker EIP to MicroProfile Fault Tolerance
component
---
components/camel-kamelet/src/main/docs/kamelet-component.adoc | 4 ++--
.../src/main/docs/microprofile-fault-tolerance.adoc | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/components/camel-kamelet/src/main/docs/kamelet-component.adoc
b/components/camel-kamelet/src/main/docs/kamelet-component.adoc
index 828eb8e3ce5..58ba700f968 100644
--- a/components/camel-kamelet/src/main/docs/kamelet-component.adoc
+++ b/components/camel-kamelet/src/main/docs/kamelet-component.adoc
@@ -62,7 +62,7 @@ routeTemplate("setMyBody")
[IMPORTANT]
====
-To let the *Kamelet* component wiring the materialized route to the caller
processor, we need to be able to identify the input and output endpoint of the
route and this is done by using `kamele:source` to mark the input endpoint and
`kamelet:sink` for the output endpoint.
+To let the *Kamelet* component wiring the materialized route to the caller
processor, we need to be able to identify the input and output endpoint of the
route and this is done by using `kamelet:source` to mark the input endpoint and
`kamelet:sink` for the output endpoint.
====
Then the template can be instantiated and invoked as shown below:
@@ -76,7 +76,7 @@ from("direct:setMyBody")
Behind the scenes, the *Kamelet* component does the following things:
-1. it instantiates a route out of the Route Template identified by the given
`templateId` path parameter (in this case `setBody`)
+1. it instantiates a route out of the Route Template identified by the given
`templateId` path parameter (in this case `setMyBody`)
2. it will act like the `direct` component and connect the current route to
the materialized one.
If you had to do it programmatically, it would have been something like:
diff --git
a/components/camel-microprofile/camel-microprofile-fault-tolerance/src/main/docs/microprofile-fault-tolerance.adoc
b/components/camel-microprofile/camel-microprofile-fault-tolerance/src/main/docs/microprofile-fault-tolerance.adoc
index 97f65534d50..05232fb260b 100644
---
a/components/camel-microprofile/camel-microprofile-fault-tolerance/src/main/docs/microprofile-fault-tolerance.adoc
+++
b/components/camel-microprofile/camel-microprofile-fault-tolerance/src/main/docs/microprofile-fault-tolerance.adoc
@@ -10,7 +10,7 @@
This component supports the Circuit Breaker EIP with the MicroProfile Fault
Tolerance library.
-For more details see the Circuit Breaker EIP documentation.
+For more details see the xref:eips:circuitBreaker-eip.adoc[Circuit Breaker
EIP] documentation.
Maven users will need to add the following dependency to their `pom.xml`
for this component:
