The intended audience of this document is Java developers who are familiar with the JMS specification. Readers are not required to know all the details of AMQP protocols. However, some knowledge of AMQP basic concepts would be advantageous for reading of this document.
This document only covers the usage of 0-8, 0-9 and 0-9-1 AMQP protocols with Qpid JMS client. The specifications for these protocols are available from the AMQP web site.
The document covers some specific implementation details of JMS connections, sessions, consumers and producers in Chapter 5, Understanding the Qpid JMS client. It also demonstrates how to write a simple point to point and simple publish/subscribe application using Qpid JMS Client in Chapter 4, Examples.
The Qpid JMS Client supports various configuration options which can be set via JVM system properties, connection URLs and JNDI configuration file. The setting of system properties is described in Chapter 9, System Properties. The details of supported options within the connection URLs are given in Chapter 7, Connection URLs. The details of Qpid JMS client JNDI properties format is provided in Chapter 6, JNDI Properties Format. The Qpid destination URL format is covered in Chapter 8, Binding URL.
The Qpid JMS Client can be used for writing of JMS vendor neutral messaging applications. However, in some cases it might be required to use specific AMQP features. Thus, the Qpid client provides the extended operation set to invoke those features.
Chapter 10, Logging provides the details about turning on client logging which can help in debugging of various issues while developing the messaging applications.
The details about Qpid JMS Client Exceptions are provided in Appendix A, Exceptions
Apache Qpid, Messaging built on AMQP; Copyright © 2013 The Apache Software Foundation; Licensed under the Apache License, Version 2.0; Apache Qpid, Qpid, Qpid Proton, Proton, Apache, the Apache feather logo, and the Apache Qpid project logo are trademarks of The Apache Software Foundation; All other marks mentioned may be trademarks or registered trademarks of their respective owners