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 5b389af CAMEL-16861: Cleanup and update EIP docs
5b389af is described below
commit 5b389afff48a3fcb9d250044f42fc443b5121617
Author: Claus Ibsen <claus.ib...@gmail.com>
AuthorDate: Thu Oct 7 14:55:03 2021 +0200
CAMEL-16861: Cleanup and update EIP docs
---
.../docs/modules/eips/pages/message-translator.adoc | 5 +----
.../docs/modules/eips/pages/messaging-bridge.adoc | 21 ++++++++++++++++++---
.../docs/modules/eips/pages/messaging-gateway.adoc | 7 +++----
.../docs/modules/eips/pages/messaging-mapper.adoc | 2 ++
4 files changed, 24 insertions(+), 11 deletions(-)
diff --git
a/core/camel-core-engine/src/main/docs/modules/eips/pages/message-translator.adoc
b/core/camel-core-engine/src/main/docs/modules/eips/pages/message-translator.adoc
index aaf8ad2..7b0cae2 100644
---
a/core/camel-core-engine/src/main/docs/modules/eips/pages/message-translator.adoc
+++
b/core/camel-core-engine/src/main/docs/modules/eips/pages/message-translator.adoc
@@ -93,7 +93,4 @@ And in XML:
=== Message Translator using Data Format
-TODO:
-
-
-
+See xref:marshal-eip.adoc[Marshal] EIP for more details and examples.
diff --git
a/core/camel-core-engine/src/main/docs/modules/eips/pages/messaging-bridge.adoc
b/core/camel-core-engine/src/main/docs/modules/eips/pages/messaging-bridge.adoc
index 1a1e268..4fac74e 100644
---
a/core/camel-core-engine/src/main/docs/modules/eips/pages/messaging-bridge.adoc
+++
b/core/camel-core-engine/src/main/docs/modules/eips/pages/messaging-bridge.adoc
@@ -10,9 +10,15 @@ image::eip/MessagingBridge.gif[image]
Use a Messaging Bridge, a connection between messaging systems, to replicate
messages between systems.
-You can use Camel to bridge different systems using Camel components and
routes.
+You can use Camel to bridge different systems using Camel
xref:components::index.adoc[Components]
+and bridge the endpoints together in a
xref:latest@manual:ROOT:routes.adoc[Route].
-A basic bridge between two queues can be done with a Camel route:
+Another alternative is to bridge systems using
xref:change-data-capture.adoc[Change Data Capture].
+
+== Example
+
+A basic bridge between two messaging systems (such as WebsphereMQ and
xref:components::activemq-component.adoc[ActiveMQ])
+can be done with a single Camel route:
[source,java]
----
@@ -20,4 +26,13 @@ from("mq:queue:foo")
.to("activemq:queue:foo")
----
-Another alternative is to bridge systems using
xref:change-data-capture.adoc[Change Data Capture].
\ No newline at end of file
+And in XML
+
+[source,xml]
+----
+<route>
+ <from uri="mq:queue:foo"/>
+ <to uri="activemq:queue:foo"/>
+</route>
+----
+
diff --git
a/core/camel-core-engine/src/main/docs/modules/eips/pages/messaging-gateway.adoc
b/core/camel-core-engine/src/main/docs/modules/eips/pages/messaging-gateway.adoc
index c1a57fc..3484a11 100644
---
a/core/camel-core-engine/src/main/docs/modules/eips/pages/messaging-gateway.adoc
+++
b/core/camel-core-engine/src/main/docs/modules/eips/pages/messaging-gateway.adoc
@@ -11,8 +11,7 @@ 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 way
-to bind a Java interface to the message exchange.
+Components like xref:components::bean-component.adoc[Bean] provides 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.
+Another approach is to use `@Produce` annotations
(xref:latest@manual:ROOT:pojo-producing.adoc[POJO Producing])
+which also can be used to hide Camel APIs and thereby encapsulate access,
acting as a Messaging Gateway EIP solution.
diff --git
a/core/camel-core-engine/src/main/docs/modules/eips/pages/messaging-mapper.adoc
b/core/camel-core-engine/src/main/docs/modules/eips/pages/messaging-mapper.adoc
index 25bb3be..0f856c9 100644
---
a/core/camel-core-engine/src/main/docs/modules/eips/pages/messaging-mapper.adoc
+++
b/core/camel-core-engine/src/main/docs/modules/eips/pages/messaging-mapper.adoc
@@ -21,3 +21,5 @@ xref:latest@manual:ROOT:type-converter.adoc[Type Converter]'s
from the messaging
Java Objects representing the data model of the component in question.
Combining this with the
xref:message-translator.adoc[Message Translator] to have the Messaging Mapper
EIP pattern.
+Camel also integrates with external mapping software such as
xref:components::atlasmap-component.adoc[AtlasMap].
+
