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 e840a6c CAMEL-16861: Cleanup and update EIP docs
e840a6c is described below
commit e840a6c3f10a39d692fff1d7cde6b62eaf17495d
Author: Claus Ibsen <claus.ib...@gmail.com>
AuthorDate: Tue Oct 5 09:02:08 2021 +0200
CAMEL-16861: Cleanup and update EIP docs
---
.../docs/modules/eips/pages/message-broker.adoc | 5 ++--
.../main/docs/modules/eips/pages/message-bus.adoc | 27 +++++++++-------------
.../docs/modules/eips/pages/message-channel.adoc | 24 +++++++++----------
.../modules/eips/pages/message-dispatcher.adoc | 14 ++++++-----
4 files changed, 33 insertions(+), 37 deletions(-)
diff --git
a/core/camel-core-engine/src/main/docs/modules/eips/pages/message-broker.adoc
b/core/camel-core-engine/src/main/docs/modules/eips/pages/message-broker.adoc
index 239c375..419f8aa 100644
---
a/core/camel-core-engine/src/main/docs/modules/eips/pages/message-broker.adoc
+++
b/core/camel-core-engine/src/main/docs/modules/eips/pages/message-broker.adoc
@@ -11,8 +11,9 @@ image::eip/MessageBroker.gif[image]
Use a central Message Broker that can receive messages from multiple
destinations,
determine the correct destination and route the message to the correct channel.
-Camel supports integration with existing message broker systems such as Apache
ActiveMQ,
-Apache Kafka, RabbitMQ, and cloud queue systems such as AWS SQS, and others.
+Camel supports integration with existing message broker systems such as
xref:components::activemq-component.adoc[ActiveMQ],
+xref:components::kafka-component.adoc[Kafka],
xref:components::spring-rabbitmq-component.adoc[RabbitMQ],
+and cloud queue systems such as xref:components::aws2-s3-component.adoc[AWS
SQS], and others.
These Camel components allows to both send and receive data from message
brokers.
diff --git
a/core/camel-core-engine/src/main/docs/modules/eips/pages/message-bus.adoc
b/core/camel-core-engine/src/main/docs/modules/eips/pages/message-bus.adoc
index 8008926..b0de75e 100644
--- a/core/camel-core-engine/src/main/docs/modules/eips/pages/message-bus.adoc
+++ b/core/camel-core-engine/src/main/docs/modules/eips/pages/message-bus.adoc
@@ -8,30 +8,25 @@ consumers to be decoupled.
image::eip/MessageBusSolution.gif[image]
-Folks often assume that a Message Bus is a JMS though so you may wish to
-refer to the xref:components::jms-component.adoc[JMS] component for
traditional MOM support. +
+A messaging system such as Apache ActiveMQ can be used as Message Bus.
-
-[[MessageBus-Example]]
-== Samples
+== Example
The following demonstrates how the Camel message bus can be used to
-communicate with consumers and producers
+ingest message into the bus with the xref:components::jms-component.adoc[JMS]
component.
[source,java]
------------------------------------------------
-from("direct:start")
- .pollEnrich("file:inbox?fileName=data.txt")
- .to("jms:queue:foo");
------------------------------------------------
+----
+from("file:inbox")
+ .to("jms:inbox");
+----
And in XML:
[source,xml]
-----------------------------------------------------
+----
<route>
- <from uri="direct:start"/>
- <pollEnrich uri="file:inbox?fileName=data.txt"/>
- <to uri="jms:queue:foo"/>
+ <from uri="file:inbox"/>
+ <to uri="jms:inbox"/>
</route>
-----------------------------------------------------
+----
diff --git
a/core/camel-core-engine/src/main/docs/modules/eips/pages/message-channel.adoc
b/core/camel-core-engine/src/main/docs/modules/eips/pages/message-channel.adoc
index c5e33ac..d77a907 100644
---
a/core/camel-core-engine/src/main/docs/modules/eips/pages/message-channel.adoc
+++
b/core/camel-core-engine/src/main/docs/modules/eips/pages/message-channel.adoc
@@ -3,30 +3,29 @@
Camel supports the
http://www.enterpriseintegrationpatterns.com/MessageChannel.html[Message
Channel] from the xref:enterprise-integration-patterns.adoc[EIP
-patterns]. The Message Channel is an internal implementation detail of
-the `Endpoint` interface and all interactions with the Message Channel are via
the
-Endpoint interfaces.
+patterns].
+
+The Message Channel is an internal implementation detail of
+the `Endpoint` interface, where all interactions of the channel is via the
+https://www.javadoc.io/doc/org.apache.camel/camel-api/current/org/apache/camel/Endpoint.html[Endpoint].
image::eip/MessageChannelSolution.gif[image]
-== Samples
+== Example
-In JMS, Message Channels are represented by topics and queues such as
-the following
+In xref:components::jms-component.adoc[JMS], Message Channels are represented
by topics and queues such as
+the following:
[source,text]
-------------
jms:queue:foo
-------------
-This message channel can be then used within the
-xref:components::jms-component.adoc[JMS] component
-
-And the following shows a little Java route snippet:
+The following shows a little Java route snippet:
[source,java]
----
-from("direct:foo")
+from("file:foo")
.to("jms:queue:foo")
----
@@ -35,8 +34,7 @@ And in XML:
[source,xml]
----
<route>
- <from uri="direct:foo">
+ <from uri="file:foo"/>
<to uri="jms:queue:foo"/>
</route>
----
-
diff --git
a/core/camel-core-engine/src/main/docs/modules/eips/pages/message-dispatcher.adoc
b/core/camel-core-engine/src/main/docs/modules/eips/pages/message-dispatcher.adoc
index 42a362f..0c36c51 100644
---
a/core/camel-core-engine/src/main/docs/modules/eips/pages/message-dispatcher.adoc
+++
b/core/camel-core-engine/src/main/docs/modules/eips/pages/message-dispatcher.adoc
@@ -4,11 +4,13 @@ Camel supports the
https://www.enterpriseintegrationpatterns.com/patterns/messaging/MessageDispatcher.html[Message
Dispatcher]
from the xref:enterprise-integration-patterns.adoc[EIP patterns] book.
-Camel supports the Message Dispatcher from the EIP patterns using various
approaches.
-
image::eip/MessageDispatcher.gif[image]
-You can use a component like JMS with selectors to implement a
xref:selective-consumer.adoc[Selective Consumer]
-as the Message Dispatcher implementation. Or you can use an
xref:message-endpoint.adoc[Message Endpoint]
-as the Message Dispatcher itself and then use a xref:choice-eip.adoc[Content
Based Router]
-as the Message Dispatcher.
+In Camel the Message Dispatcher can be archived in different ways such as:
+
+* You can use a component like xref:components::jms-component.adoc[JMS] with
selectors
+to implement a xref:selective-consumer.adoc[Selective Consumer] as the Message
Dispatcher implementation.
+
+* Or you can use a xref:message-endpoint.adoc[Message Endpoint] as the Message
Dispatcher itself, and
+ combine this with the xref:choice-eip.adoc[Content Based Router] as the
Message Dispatcher.
+
