You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by ac...@apache.org on 2020/09/11 10:18:36 UTC
[camel] branch master updated (406b09b -> 1e4bd5f)
This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git.
from 406b09b Document update (#4195)
new b31361e Regen catalog
new 1e4bd5f Regen catalog
The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
.../org/apache/camel/catalog/docs/dead-letter-channel.adoc | 8 ++++----
.../resources/org/apache/camel/catalog/docs/failover-eip.adoc | 2 +-
2 files changed, 5 insertions(+), 5 deletions(-)
[camel] 01/02: Regen catalog
Posted by ac...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git
commit b31361e8a20fa9c8a73523508550f409a0bc6a76
Author: Andrea Cosentino <an...@gmail.com>
AuthorDate: Fri Sep 11 12:16:39 2020 +0200
Regen catalog
---
.../org/apache/camel/catalog/docs/dead-letter-channel.adoc | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/dead-letter-channel.adoc b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/dead-letter-channel.adoc
index 456546c..4c615cc 100644
--- a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/dead-letter-channel.adoc
+++ b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/dead-letter-channel.adoc
@@ -157,7 +157,7 @@ original we received.
=== Boundary of original message
The original input means the input message that are bounded by the current unit of work. An unit of work typically spans one route, or multiple routes if they are connected
-using internal endpoints such as direct or seda. When messages is passed via external
+using internal endpoints such as direct or seda. When messages are passed via external
endpoints such as JMS or HTT then the consumer will create a new unit of work, with the
message it received as input as the original input. Also some EIP patterns such as splitter,
multicast, will create a new unit of work boundary for the messages in their sub-route
@@ -207,7 +207,7 @@ The maximum redeliver delay ensures that a delay is never longer than
the value, default 1 minute. This can happen if you turn on the
exponential backoff.
-The maximum redeliveries is the number of redelivery attempts. By
+The maximum redeliveries are the number of redelivery attempts. By
default Camel will try to process the exchange 1 + 5 times. 1 time for
the normal attempt and then 5 attempts as redeliveries.
Setting the maximumRedeliveries to a negative value such as -1 will
@@ -429,7 +429,7 @@ option `allowRedeliveryWhileStopping` which you can use to control if
redelivery is allowed or not; notice that any in progress redelivery
will still be executed. This option can only disallow any redelivery to
be executed *after* the stopping of a route/shutdown of Camel has been
-triggered. If a redelivery is dissallowed then a
+triggered. If a redelivery is disallowed then a
`RejectedExecutionException` is set on the xref:latest@manual:ROOT:exchange.adoc[Exchange]
and the processing of the xref:latest@manual:ROOT:exchange.adoc[Exchange] stops. This means
any consumer will see the xref:latest@manual:ROOT:exchange.adoc[Exchange] as failed due the
@@ -439,7 +439,7 @@ The default value is `true` to be backwards compatible as before. For
example the following sample shows how to do this with Java DSL and XML
DSL
-And the sample sample with XML DSL
+And the sample with XML DSL
[[deadLetterChannel-Samples]]
== Samples
[camel] 02/02: Regen catalog
Posted by ac...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git
commit 1e4bd5f12f2e06c839c76b65d5aef0e679663bd1
Author: Andrea Cosentino <an...@gmail.com>
AuthorDate: Fri Sep 11 12:18:11 2020 +0200
Regen catalog
---
.../generated/resources/org/apache/camel/catalog/docs/failover-eip.adoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/failover-eip.adoc b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/failover-eip.adoc
index ecc36a1..98be858 100644
--- a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/failover-eip.adoc
+++ b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/failover-eip.adoc
@@ -15,7 +15,7 @@ The Failover EIP supports 4 options which are listed below:
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
-| *exception* | A list of class names for specific exceptions to monitor. If no exceptions is configured then all exceptions is monitored | | List
+| *exception* | A list of class names for specific exceptions to monitor. If no exceptions are configured then all exceptions is monitored | | List
| *roundRobin* | Whether or not the failover load balancer should operate in round robin mode or not. If not, then it will always start from the first endpoint when a new message is to be processed. In other words it restart from the top for every message. If round robin is enabled, then it keeps state and will continue with the next endpoint in a round robin fashion. You can also enable sticky mode together with round robin, if so then it will pick the last known good endpoint to use wh [...]
| *sticky* | Whether or not the failover load balancer should operate in sticky mode or not. If not, then it will always start from the first endpoint when a new message is to be processed. In other words it restart from the top for every message. If sticky is enabled, then it keeps state and will continue with the last known good endpoint. You can also enable sticky mode together with round robin, if so then it will pick the last known good endpoint to use when starting the load balanci [...]
| *maximumFailoverAttempts* | A value to indicate after X failover attempts we should exhaust (give up). Use -1 to indicate never give up and continuously try to failover. Use 0 to never failover. And use e.g. 3 to failover at most 3 times before giving up. his option can be used whether or not roundRobin is enabled or not. | -1 | String