The Java Message Service makes it EASY to write business applications that asynchronously send and receive critical business data and events.

The Java Message Service defines a common enterprise messaging API that is designed to be easily and efficiently supported by a wide range of enterprise messaging products.

The Java Message Service supports both message queueing and publish-subscribe styles of messaging.


Is the Java Message Service another mail API?

The term messaging is quite broadly defined in computing. It is used for describing various operating system concepts; it is used to describe email and fax systems; and with JMS, it is used to describe asynchronous communication between enterprise applications.

JMS messages are asynchronous requests, reports or events that are consumed by enterprise applications, not humans. They contain vital information needed to coordinate these systems. They contain precisely formatted data that describe specific business actions. Through the exchange of these messages each application tracks the progress of the enterprise.


Is the Java Message Service a product?

No, the Java Message Service is the specification of a common API for enterprise messaging. A JMS provider supplied by an enterprise messaging vendor is required to use it.


When will the Java Message Service specification be available? Where?

The Java Message Service 1.0 specification is available now at http://java.sun.com/products/jms.


Who was involved with Sun in the creation of the specification of Java Message Service 1.0?

A number of important industry players initially collaboratively with Sun to define the first draft of Java Message Service specification. In addition many comments were received from other companies, government and educational organizations and others during the 3 month public review period.


What is compelling about Java Message Service?

Java Message Service is compelling because:

1) It is the first enterprise messaging API that has achieved wide industry support.

2) It simplifies the developing of enterprise applications by providing standard messaging concepts and conventions that apply across a wide range of enterprise messaging systems.

3) It leverages existing, enterprise proven messaging systems.


Why should developers use Java Message Service?

Java Message Service will make it :

(1) easy to write portable, message-based business applications

(2) easy to extend existing message-based applications by adding new JMS clients that interoperate fully with their existing non-JMS clients


What does a programmer need to learn to use the Java Message Service?

Message based applications are fundamentally different than remote procedure call based applications. Once a developer understands how best to employ both technologies, JMS makes writing message based applications as easy as learning a few additional interfaces.


What is the relationship between the Java Message Service and Enterprise JavaBeans?

Today, EJB components can use JMS to send enterprise messages. A future version of EJB will define how to build an EJB component that is message driven.


What is the relationship between Java Message Service and the Java Naming and Directory Interface?

JMS like the other Java Enterprise API's, uses JNDI for administration. JMS defines ConnectionFactories and Destinations as administered objects that are configured and placed in a JNDI naming context. JMS clients then look up and use these pre-configured objects. This insures that JMS applications are easy to deploy and administer.