This is an automated email from the ASF dual-hosted git repository.
davsclaus 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 710873a Polished docs
710873a is described below
commit 710873a9b0d81cc91869064d9255033cf778e16a
Author: Claus Ibsen <[email protected]>
AuthorDate: Tue Nov 19 15:04:59 2019 +0100
Polished docs
---
.../modules/ROOT/pages/content-enricher.adoc | 2 +-
.../pages/enterprise-integration-patterns.adoc | 2 +-
.../modules/ROOT/pages/event-message.adoc | 2 +-
.../using-getin-or-getout-methods-on-exchange.adoc | 2 +-
docs/user-manual/modules/ROOT/pages/message.adoc | 4 +-
.../modules/ROOT/pages/request-reply.adoc | 44 ++++++++++++++++++++++
.../modules/ROOT/pages/spring-remoting.adoc | 2 +-
.../pages/using-exchange-pattern-annotations.adoc | 2 +-
8 files changed, 52 insertions(+), 8 deletions(-)
diff --git a/docs/user-manual/modules/ROOT/pages/content-enricher.adoc
b/docs/user-manual/modules/ROOT/pages/content-enricher.adoc
index ac602a0..386d700 100644
--- a/docs/user-manual/modules/ROOT/pages/content-enricher.adoc
+++ b/docs/user-manual/modules/ROOT/pages/content-enricher.adoc
@@ -92,7 +92,7 @@ Camel comes with two flavors of content enricher in the DSL
* `pollEnrich`
`enrich` uses a `Producer` to obtain the additional data. It is usually
-used for xref:requestReply-eip.adoc[Request Reply] messaging, for instance
+used for xref:request-reply.adoc[Request Reply] messaging, for instance
to invoke an external web service. +
`pollEnrich` on the other hand uses a xref:polling-consumer.adoc[Polling
Consumer] to obtain the additional data. It is usually used for
diff --git
a/docs/user-manual/modules/ROOT/pages/enterprise-integration-patterns.adoc
b/docs/user-manual/modules/ROOT/pages/enterprise-integration-patterns.adoc
index 71dafcf..9a41130 100644
--- a/docs/user-manual/modules/ROOT/pages/enterprise-integration-patterns.adoc
+++ b/docs/user-manual/modules/ROOT/pages/enterprise-integration-patterns.adoc
@@ -82,7 +82,7 @@ a|image::eip/EventMessageIcon.gif[image]
transmit events from one application to another?
a|image::eip/RequestReplyIcon.gif[image]
-|xref:requestReply-eip.adoc[Request Reply] |When an application sends a
+|xref:request-reply.adoc[Request Reply] |When an application sends a
message, how can it get a response from the receiver?
a|image::eip/CorrelationIdentifierIcon.gif[image]
diff --git a/docs/user-manual/modules/ROOT/pages/event-message.adoc
b/docs/user-manual/modules/ROOT/pages/event-message.adoc
index 8242c05..5f6ad25 100644
--- a/docs/user-manual/modules/ROOT/pages/event-message.adoc
+++ b/docs/user-manual/modules/ROOT/pages/event-message.adoc
@@ -15,7 +15,7 @@ The default behaviour of many
xref:components::index.adoc[Components] is InOnly
such as for xref:components::jms-component.adoc[JMS],
xref:components::jms-component.adoc[File] or
xref:components::seda-component.adoc[SEDA]
-TIP: See the related xref:requestReply-eip.adoc[Request Reply] message.
+TIP: See the related xref:request-reply.adoc[Request Reply] message.
[[eventMessage-ExplicitlyspecifyingInOnly]]
== Explicitly specifying InOnly
diff --git
a/docs/user-manual/modules/ROOT/pages/faq/using-getin-or-getout-methods-on-exchange.adoc
b/docs/user-manual/modules/ROOT/pages/faq/using-getin-or-getout-methods-on-exchange.adoc
index 43905ae..e8031fd 100644
---
a/docs/user-manual/modules/ROOT/pages/faq/using-getin-or-getout-methods-on-exchange.adoc
+++
b/docs/user-manual/modules/ROOT/pages/faq/using-getin-or-getout-methods-on-exchange.adoc
@@ -8,7 +8,7 @@ called Message Exchange Patterns (MEP for short).
The MEP defines the messaging style used such as one-way
(xref:event-message.adoc[InOnly]) or request-reply
-(xref:requestReply-eip.adoc[InOut]),
+(xref:request-reply.adoc[InOut]),
which means you have IN and optionally OUT messages. This closely maps
to other APIs such as WS, WSDL, REST, JBI and the likes.
diff --git a/docs/user-manual/modules/ROOT/pages/message.adoc
b/docs/user-manual/modules/ROOT/pages/message.adoc
index 8b0d05c..2826805 100644
--- a/docs/user-manual/modules/ROOT/pages/message.adoc
+++ b/docs/user-manual/modules/ROOT/pages/message.adoc
@@ -11,11 +11,11 @@ image::eip/MessageSolution.gif[image]
To support various message xref:exchange-pattern.adoc[exchange patterns]
like one way xref:event-message.adoc[Event Message] and
-xref:requestReply-eip.adoc[Request Reply] messages Camel uses an
+xref:request-reply.adoc[Request Reply] messages Camel uses an
xref:exchange.adoc[Exchange] interface which has a *pattern* property
which can be set to *InOnly* for an xref:event-message.adoc[Event
Message] which has a single inbound Message, or *InOut* for a
-xref:requestReply-eip.adoc[Request Reply] where there is an inbound and
+xref:request-reply.adoc[Request Reply] where there is an inbound and
outbound message.
Here is a basic example of sending a Message to a route in *InOnly* and
diff --git a/docs/user-manual/modules/ROOT/pages/request-reply.adoc
b/docs/user-manual/modules/ROOT/pages/request-reply.adoc
new file mode 100644
index 0000000..907a9f2
--- /dev/null
+++ b/docs/user-manual/modules/ROOT/pages/request-reply.adoc
@@ -0,0 +1,44 @@
+[[request-reply]]
+= Request Reply
+:page-source: core/camel-core-engine/src/main/docs/eips/request-reply.adoc
+
+Camel supports the
+http://www.enterpriseintegrationpatterns.com/RequestReply.html[Request
+Reply] from the EIP patterns
+by supporting the Exchange Pattern on a
+Message which can be set to *InOut* to indicate a
+request/reply. Camel Components then implement
+this pattern using the underlying transport or protocols.
+
+image::eip/RequestReply.gif[image]
+
+For example when using xref:components::jms-component.adoc[JMS] with InOut the
component will
+by default perform these actions
+
+* create by default a temporary inbound queue
+* set the JMSReplyTo destination on the request message
+* set the JMSCorrelationID on the request message
+* send the request message
+* consume the response and associate the inbound message to the request
+using the JMSCorrelationID (as you may be performing many concurrent
+request/responses).
+
+TIP: *Related* See the related Event Message message
+
+[[RequestReply-ExplicitlyspecifyingInOut]]
+== Explicitly specifying InOut
+
+When consuming messages from xref:components::jms-component.adoc[JMS] a
Request-Reply is
+indicated by the presence of the *JMSReplyTo* header.
+
+You can explicitly force an endpoint to be in Request Reply mode by
+setting the exchange pattern on the URI. e.g.
+
+[source,text]
+----
+jms:MyQueue?exchangePattern=InOut
+----
+
+You can specify the exchange pattern in DSL rule or Spring
+configuration.
+
diff --git a/docs/user-manual/modules/ROOT/pages/spring-remoting.adoc
b/docs/user-manual/modules/ROOT/pages/spring-remoting.adoc
index 6b6962e..08123af 100644
--- a/docs/user-manual/modules/ROOT/pages/spring-remoting.adoc
+++ b/docs/user-manual/modules/ROOT/pages/spring-remoting.adoc
@@ -112,7 +112,7 @@ serviceInterface.
== Working with InOnly method calls
As of 1.5 Camel supports the @InOnly and @Pattern annotations to let you
-specify which methods are not InOut (xref:requestReply-eip.adoc[Request
+specify which methods are not InOut (xref:request-reply.adoc[Request
Reply]) but are InOnly (oneway or fire and forget
xref:event-message.adoc[Event Message]).
diff --git
a/docs/user-manual/modules/ROOT/pages/using-exchange-pattern-annotations.adoc
b/docs/user-manual/modules/ROOT/pages/using-exchange-pattern-annotations.adoc
index 7fe622a..a8dc022 100644
---
a/docs/user-manual/modules/ROOT/pages/using-exchange-pattern-annotations.adoc
+++
b/docs/user-manual/modules/ROOT/pages/using-exchange-pattern-annotations.adoc
@@ -3,7 +3,7 @@
When working with xref:pojo-producing.adoc[POJO Producing] or
xref:spring-remoting.adoc[Spring Remoting] you invoke methods which
-typically by default are InOut for xref:requestReply-eip.adoc[Request
+typically by default are InOut for xref:request-reply.adoc[Request
Reply]. That is there is an In message and an Out for the result.
Typically invoking this operation will be synchronous, the caller will
block until the server returns a result.
