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
The following commit(s) were added to refs/heads/master by this push:
new cdfe437 Regen
cdfe437 is described below
commit cdfe437be5babff32bdcf8797636f18f70ee7d9e
Author: Andrea Cosentino <anco...@gmail.com>
AuthorDate: Fri Sep 11 14:52:15 2020 +0200
Regen
---
.../generated/resources/org/apache/camel/catalog/docs/intercept.adoc | 4 ++--
.../resources/org/apache/camel/catalog/docs/message-history.adoc | 2 +-
.../resources/org/apache/camel/catalog/docs/messaging-gateway.adoc | 3 +--
3 files changed, 4 insertions(+), 5 deletions(-)
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/intercept.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/intercept.adoc
index aa805f4..7f08ba3 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/intercept.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/intercept.adoc
@@ -118,7 +118,7 @@ Exchange will continue its route, and thus it will
continue to `mock:first`.
You can also attach a Predicate to only trigger if
-certain conditions is meet. For instance in the route below we intercept
+certain conditions are meet. For instance in the route below we intercept
when a test message is send to us, so we can do some custom processing
before we continue routing:
@@ -152,7 +152,7 @@ default Camel will send to the original intended
destination after the
intercepted route completes. And as the regular intercept you can also
define an `when` Predicate so we only intercept if
the Predicate evaluates to *true*. This allows you
-do do a bit of filtering, to only intercept when certain criteria is
+do a bit of filtering, to only intercept when certain criteria is
meet. And finally you can send the Exchange to an endpoint with the `afterUrl`
option. You can use this to process the response from the original endpoint.
Let start with a simple example, where we want to intercept when an
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/message-history.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/message-history.adoc
index 203ee34..170f59a 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/message-history.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/message-history.adoc
@@ -142,7 +142,7 @@
errorHandler(defaultErrorHandler().logExhaustedMessageBody(true));
== MessageHistory API
When message history is enabled during routing Camel captures how the Exchange
is routed, as a `org.apache.camel.MessageHistory` entity
-that is stored on the Exchange. On the `org.apache.camel.MessageHistory` there
is information abut the
+that is stored on the Exchange. On the `org.apache.camel.MessageHistory` there
is information about the
route id, processor id, timestamp, and elapsed time it took to process the
Exchange by the processor.
You can access the message history from Java code:
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/messaging-gateway.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/messaging-gateway.adoc
index 10e2c11..e535588 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/messaging-gateway.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/messaging-gateway.adoc
@@ -12,9 +12,8 @@ image::eip/MessagingGatewaySolution.gif[image]
Use a Messaging Gateway, a class than wraps messaging-specific method calls
and exposes domain-specific methods to the application.
Camel has several endpoint components that support the Messaging Gateway from
the EIP patterns.
-Components like xref:components::bean-component.adoc[Bean] and
xref:components::bean-component.adoc[CXF] provide a a way
+Components like xref:components::bean-component.adoc[Bean] and
xref:components::bean-component.adoc[CXF] provide a way
to bind a Java interface to the message exchange.
Another approach is to use `@Produce` annotations which you can read about in
xref:latest@manual:ROOT:pojo-producing.adoc[POJO Producing]
which also can be used as a Messaging Gateway EIP solution.
-
