This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch camel-3.11.x
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/camel-3.11.x by this push:
new 1c5aad0 Polish and cleanup documentation
1c5aad0 is described below
commit 1c5aad03c5714bf9ac8ce438f4730c594367de10
Author: Claus Ibsen <claus.ib...@gmail.com>
AuthorDate: Tue Aug 10 14:52:32 2021 +0200
Polish and cleanup documentation
---
.../src/main/docs/modules/eips/pages/polling-consumer.adoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/core/camel-core-engine/src/main/docs/modules/eips/pages/polling-consumer.adoc
b/core/camel-core-engine/src/main/docs/modules/eips/pages/polling-consumer.adoc
index 8522266..4c78805 100644
---
a/core/camel-core-engine/src/main/docs/modules/eips/pages/polling-consumer.adoc
+++
b/core/camel-core-engine/src/main/docs/modules/eips/pages/polling-consumer.adoc
@@ -323,7 +323,7 @@ executed. For instance if Camel should poll a file network,
and this
network resource is not available then a *`java.io.IOException`* could
occur. As this error happens *before* any
xref:latest@manual:ROOT:exchange.adoc[Exchange]
has been created and prepared for routing, then the regular
-xref:latest@manual:ROOT:error-handling-in-camel.adoc[Error handling in Camel]
does not
+xref:latest@manual:ROOT:error-handler.adoc[Error handler] does not
apply. So what does the consumer do then? Well the exception is
propagated back to the *`run`* method where its handled. Camel will by
default log the exception at *`WARN`* level and then ignore it. At next
