From f3475dd0ce65adddc7ee7aeecdbcd469a0222d04 Mon Sep 17 00:00:00 2001 From: Juergen Hoeller Date: Tue, 5 Mar 2019 13:35:11 +0100 Subject: [PATCH] Fixed misformatted chapter id --- src/docs/asciidoc/integration.adoc | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/src/docs/asciidoc/integration.adoc b/src/docs/asciidoc/integration.adoc index 96124faddd..06874d05ba 100644 --- a/src/docs/asciidoc/integration.adoc +++ b/src/docs/asciidoc/integration.adoc @@ -1743,10 +1743,9 @@ operations that do not refer to a specific destination. One of the most common uses of JMS messages in the EJB world is to drive message-driven beans (MDBs). Spring offers a solution to create message-driven POJOs (MDPs) in a way -that does not tie a user to an EJB container. (See <> -for detailed coverage of Spring's MDP support.) As from Spring Framework 4.1, endpoint -methods can be simply annotated using `@JmsListener` see <> for more -details. +that does not tie a user to an EJB container. (See <> for detailed +coverage of Spring's MDP support.) As from Spring Framework 4.1, endpoint methods can +be simply annotated using `@JmsListener` see <> for more details. A message listener container is used to receive messages from a JMS message queue and drive the `MessageListener` that is injected into it. The listener container is @@ -2021,7 +2020,7 @@ potentially be blocked indefinitely. The property `receiveTimeout` specifies how the receiver should wait before giving up waiting for a message. -[[jms-asynchronousMessageReception]] +[[jms-receiving-async]] ==== Asynchronous reception: Message-Driven POJOs [NOTE]