How Does the JMS API Work with the J2EE Platform?
When the JMS API was introduced in 1998, its most important purpose was to allow Java applications to access existing messaging-oriented middleware (MOM) systems, such as MQSeries from IBM. Since that time, many vendors have adopted and implemented the JMS API, so that a JMS product can now provide a complete messaging capability for an enterprise. Since the 1.3 release of the J2EE platform (“the J2EE 1.3 platform”), the JMS API has been an integral part of the platform, and application developers can use messaging with components using J2EE APIs (“J2EE components”). The JMS API in the J2EE platform has the following features. * Application clients, Enterprise JavaBeans (EJB) components, and Web components can send or synchronously receive a JMS message. Application clients can in addition receive JMS messages asynchronously. (Applets, however, are not required to support the JMS API.) * Message-driven beans, which are a kind of enterprise bean, enable the asynchronous consumption of m
