Overview

The Java Message Service (JMS) provides a vendor-neutral API for accessing asynchronous messaging products. JMS separates messaging functionality into queues and topics to allow existing messaging products to support at least a subset of the specification easily. Until recently, Enterprise Java Beans were unable to directly subscribe to JMS events. In EJB 2.0, the message-driven bean type has been added to allow EJBs to directly receive asynchronous messages.

JMS can be effectively used for asynchnonous messaging and system integration.

Java Message Service (lecture, handouts, ppt)
JMS Example (source.zip, jmsApp.ear)
    - requires a JMS Topic (ejava.jms.topics.general) and two connection factories (ejava.jms.factories.publisher and subscriber)

--v--fall02 semester --v--
Personnel JMS Example (source, PersonnelApp.ear, PersonnelApp_src.jar, mydomain config.xml)

This example builds on the previous Personnel SessionBean/BMP example in that it extends the RegistrarEJB and overrides previous deployment descriptors to provide the ability to publish a message with every added Person and a Message Driven Bean to accept/print that message.

Sun's main JMS page

JMS Documentation, Samples

JMS FAQ (http://e-docs.bea.com/wls/docs61/faq/jms.html)