This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a commit to branch release-1.4.x
in repository https://gitbox.apache.org/repos/asf/camel-k.git
The following commit(s) were added to refs/heads/release-1.4.x by this push:
new d2eb10a Fixed camel website links in 1.4.x docs from absolute to
relative
d2eb10a is described below
commit d2eb10a291246c7b0d956e4be49470dd919d5cf9
Author: Andrea Cosentino <anco...@gmail.com>
AuthorDate: Thu Jun 24 07:21:07 2021 +0200
Fixed camel website links in 1.4.x docs from absolute to relative
---
.../ROOT/pages/kamelets/kameletbindings-error-handler.adoc | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git
a/docs/modules/ROOT/pages/kamelets/kameletbindings-error-handler.adoc
b/docs/modules/ROOT/pages/kamelets/kameletbindings-error-handler.adoc
index fe3f1ce..b6688e7 100644
--- a/docs/modules/ROOT/pages/kamelets/kameletbindings-error-handler.adoc
+++ b/docs/modules/ROOT/pages/kamelets/kameletbindings-error-handler.adoc
@@ -23,12 +23,12 @@ spec:
[[kameletbindings-error-handler-types]]
== Error Handler Types
-We have different types of error handler: `ǹone`, `log`,
`dead-letter-channel`, `bean`, `ref`. The `errorHandler` parameter is optional.
The runtime will use the configuration to create an
https://camel.apache.org/manual/latest/error-handler.html[Error Handler] as
specified by Apache Camel.
+We have different types of error handler: `ǹone`, `log`,
`dead-letter-channel`, `bean`, `ref`. The `errorHandler` parameter is optional.
The runtime will use the configuration to create an
/manual/latest/error-handler.html[Error Handler] as specified by Apache Camel.
[[kameletbindings-error-handler-none]]
=== No error handler
-There may be certain cases where you want to just ignore any failure happening
on your integration. In this situation just use a `ǹone` error handler. Under
the hood the configuration will create a
https://camel.apache.org/manual/latest/error-handler.html#ErrorHandler-NoErrorHandler[`No`
error handler builder].
+There may be certain cases where you want to just ignore any failure happening
on your integration. In this situation just use a `ǹone` error handler. Under
the hood the configuration will create a
/manual/latest/error-handler.html#ErrorHandler-NoErrorHandler[`No` error
handler builder].
[source,yaml]
----
@@ -49,7 +49,7 @@ spec:
[[kameletbindings-error-handler-log]]
=== Log error handler
-Apache Camel offers a default behavior for handling any failure: log to
standard output. However you can use the `log` error handler to specify other
behaviors such as redelivery or delay policy. Under the hood the configuration
will create a
https://camel.apache.org/manual/latest/error-handler.html#_defaulterrorhandler[`Default`
error handler builder].
+Apache Camel offers a default behavior for handling any failure: log to
standard output. However you can use the `log` error handler to specify other
behaviors such as redelivery or delay policy. Under the hood the configuration
will create a /manual/latest/error-handler.html#_defaulterrorhandler[`Default`
error handler builder].
[source,yaml]
@@ -74,7 +74,7 @@ spec:
[[kameletbindings-error-handler-dlc]]
=== Dead Letter Channel error handler
-The `Dead Letter Channel` is probably the most interesting error handler type
as it allows you to redirect any failing event to any other component, such as
a third party URI, a queue or even another `Kamelet` which will be performing
certain logic with the failing event. Under the hood the configuration will
create a
https://camel.apache.org/manual/latest/error-handler.html#_dead_letter_channel[`Dead
Letter Channel` error handler builder].
+The `Dead Letter Channel` is probably the most interesting error handler type
as it allows you to redirect any failing event to any other component, such as
a third party URI, a queue or even another `Kamelet` which will be performing
certain logic with the failing event. Under the hood the configuration will
create a /manual/latest/error-handler.html#_dead_letter_channel[`Dead Letter
Channel` error handler builder].
[source,yaml]
----
@@ -153,4 +153,4 @@ spec:
----
<1> The name of the bean to be looked up at runtime
-NOTE: make sure to have the `ref` correctly bind at runtime.
\ No newline at end of file
+NOTE: make sure to have the `ref` correctly bind at runtime.
