diff options
Diffstat (limited to 'src/asciidoc')
| -rw-r--r-- | src/asciidoc/core-beans.adoc | 10 | ||||
| -rw-r--r-- | src/asciidoc/core-resources.adoc | 4 | ||||
| -rw-r--r-- | src/asciidoc/integration.adoc | 9 |
3 files changed, 11 insertions, 12 deletions
diff --git a/src/asciidoc/core-beans.adoc b/src/asciidoc/core-beans.adoc index f899f2c7..249bb87a 100644 --- a/src/asciidoc/core-beans.adoc +++ b/src/asciidoc/core-beans.adoc @@ -3560,11 +3560,11 @@ init-method. [[aware-list]] === Other Aware interfaces -Besides `ApplicationContextAware` and `BeanNameAware` discussed above, Spring offers a -range of `Aware` interfaces that allow beans to indicate to the container that they -require a certain __infrastructure__ dependency. The most important `Aware` interfaces -are summarized below - as a general rule, the name is a good indication of the -dependency type: +Besides `ApplicationContextAware` and `BeanNameAware` discussed above, Spring offers +a range of `Aware` callback interfaces that allow beans to indicate to the container +that they require a certain __infrastructure__ dependency. The most important `Aware` +interfaces are summarized below - as a general rule, the name is a good indication of +the dependency type: [[beans-factory-nature-aware-list]] .Aware interfaces diff --git a/src/asciidoc/core-resources.adoc b/src/asciidoc/core-resources.adoc index 4ba4ce1b..699e5a48 100644 --- a/src/asciidoc/core-resources.adoc +++ b/src/asciidoc/core-resources.adoc @@ -289,8 +289,8 @@ The following table summarizes the strategy for converting ``String``s to ``Reso [[resources-resourceloaderaware]] == The ResourceLoaderAware interface -The `ResourceLoaderAware` interface is a special marker interface, identifying objects -that expect to be provided with a `ResourceLoader` reference. +The `ResourceLoaderAware` interface is a special callback interface which identifies +components that expect to be provided with a `ResourceLoader` reference: [source,java,indent=0] [subs="verbatim,quotes"] diff --git a/src/asciidoc/integration.adoc b/src/asciidoc/integration.adoc index 825c58e3..1b8442ea 100644 --- a/src/asciidoc/integration.adoc +++ b/src/asciidoc/integration.adoc @@ -1932,10 +1932,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 <<jms-asynchronousMessageReception>> -for detailed coverage of Spring's MDP support.) As from Spring Framework 4.1, endpoint -methods can be simply annotated using `@JmsListener` see <<jms-annotated>> for more -details. +that does not tie a user to an EJB container. (See <<jms-receiving-async>> for detailed +coverage of Spring's MDP support.) As from Spring Framework 4.1, endpoint methods can +be simply annotated using `@JmsListener` see <<jms-annotated>> 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 @@ -2209,7 +2208,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] |