You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by da...@apache.org on 2021/08/10 19:21:24 UTC

[camel] branch main updated: Regen for commit f493999c04b319f5fa4037cd31083afb29a8379f (#5948)

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 c2f6ace  Regen for commit f493999c04b319f5fa4037cd31083afb29a8379f (#5948)
c2f6ace is described below

commit c2f6ace73b0403123234812420ae0bed15efe7d3
Author: github-actions[bot] <41...@users.noreply.github.com>
AuthorDate: Tue Aug 10 21:19:47 2021 +0200

    Regen for commit f493999c04b319f5fa4037cd31083afb29a8379f (#5948)
    
    Signed-off-by: GitHub <no...@github.com>
    
    Co-authored-by: davsclaus <da...@users.noreply.github.com>
---
 .../resources/org/apache/camel/catalog/docs/polling-consumer.adoc       | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/polling-consumer.adoc b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/polling-consumer.adoc
index 8522266..4c78805 100644
--- a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/polling-consumer.adoc
+++ b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/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