diff --git a/src/docbkx/amqp.xml b/src/docbkx/amqp.xml index 105613ba..6bef972a 100644 --- a/src/docbkx/amqp.xml +++ b/src/docbkx/amqp.xml @@ -733,8 +733,8 @@ Object receiveAndConvert(String queueName) throws AmqpException;]]>]]> To see how to use Java to configure the AMQP infrastructure, look at - the Stock sample application, there is the @Configuration class - AbstractStockRabbitConfiguration which in turn has + the Stock sample application, there is the @Configuration class + AbstractStockRabbitConfiguration which in turn has RabbitClientConfiguration and RabbitServerConfiguration subclasses. The code for AbstractStockRabbitConfiguration is show below diff --git a/src/docbkx/sample-apps.xml b/src/docbkx/sample-apps.xml index 2959d6d2..1f829011 100644 --- a/src/docbkx/sample-apps.xml +++ b/src/docbkx/sample-apps.xml @@ -7,18 +7,20 @@
Introduction - The Spring AMQP Samples project includes two sample applications. + The Spring + AMQP Samples project includes two sample applications. The first is a simple "Hello World" example that demonstrates both - synchronous and asynchronous message reception. It provides an excellent - starting point for acquiring an understanding of the essential components. - The second sample is based on a stock-trading use case to demonstrate the - types of interaction that would be common in real world applications. In - this chapter, we will provide a quick walk-through of each sample so that - you can focus on the most important components. The samples are available - in the distribution, and they are both Maven-based, so you should be able - to import them directly into any Maven-aware IDE (such as SpringSource Tool - Suite). + synchronous and asynchronous message reception. It provides an + excellent starting point for acquiring an understanding of the + essential components. The second sample is based on a + stock-trading use case to demonstrate the types of interaction + that would be common in real world applications. In this chapter, + we will provide a quick walk-through of each sample so that you + can focus on the most important components. The samples are both + Maven-based, so you should be able to import them directly into + any Maven-aware IDE (such + as SpringSource + Tool Suite).