Java Message Service

David A Chappell, Richard Monson-Haefel

"O'Reilly Media, Inc.", Dec 4, 2000 - Computers - 240 pages

This book is a thorough introduction to Java Message Service (JMS), the standard Java application program interface (API) from Sun Microsystems that supports the formal communication known as "messaging" between computers in a network. JMS provides a common interface to standard messaging protocols and to special messaging services in support of Java programs. The messages exchange crucial data between computers, rather than between users--information such as event notification and service requests. Messaging is often used to coordinate programs in dissimilar systems or written in different programming languages.Using the JMS interface, a programmer can invoke the messaging services of IBM's MQSeries, Progress Software's SonicMQ, and other popular messaging product vendors. In addition, JMS supports messages that contain serialized Java objects and messages that contain Extensible Markup Language (XML) pages.Messaging is a powerful new paradigm that makes it easier to uncouple different parts of an enterprise application. Messaging clients work by sending messages to a message server, which is responsible for delivering the messages to their destination. Message delivery is asynchronous, meaning that the client can continue working without waiting for the message to be delivered. The contents of the message can be anything from a simple text string to a serialized Java object or an XML document.Java Message Service shows how to build applications using the point-to-point and publish-and-subscribe models; how to use features like transactions and durable subscriptions to make an application reliable; and how to use messaging within Enterprise JavaBeans. It also introduces a new EJB type, the MessageDrivenBean, that is part of EJB 2.0, and discusses integration of messaging into J2EE.

Contents

• Understanding the Messaging Paradigm: 1
• Developing a Simple Example: 17
• Anatomy of a JMS Message: 34
• PublishandSubscribe Messaging: 58
• PointtoPoint Messaging: 78
• Guaranteed Messaging Transactions Acknowledgments and Failures: 97
• Deployment Considerations: 126
• J2EE EJB and JMS: 142
• JMS Providers: 155
• The Java Message Service API: 165
• Message Headers: 183
• Message Properties: 196
• Message Selectors: 204
• Index: 211

Popular passages

Page 18 - String username) { this. connection = con; this. pubSession = pubSess; this. subSession = subSess; this. publisher = pub; this. username = username; /* public void onMessage (Message message) { try { TextMessage textMessage = (TextMessage) message; String text = textMessage. getText () ; System.‎

Page 13 - Once a message is sent, the messaging client can move on to other tasks; it doesn't have to wait for a response. This is the major difference between RPC and asynchronous messaging, and is critical to understanding the advantages offered by MOM systems. In an asynchronous messaging system, each subsystem (Accounts Receivable, Inventory, etc.) is decoupled from the other systems (see Figure 1-9).‎

Bibliographic information

• Title: Java Message Service
• Authors: David A Chappell, Richard Monson-Haefel
• Edition: revised
• Publisher: "O'Reilly Media, Inc.", 2000
• ISBN: 0596550502, 9780596550509
• Length: 240 pages
• Subjects: Computers / General; Computers / Languages / General; Computers / Languages / Java; Computers / Languages / XML; Computers / Software Development & Engineering / General