- Who was involved with Sun in the creation of the specification of Java Message Service 1.0.2?
Answer: A number of important industry players initially collaborated with Sun to define the first draft of the Java Message Service specification.In addition, many comments were received from other companies, government and educational organizations, and others during the three-month public review period.
- What is compelling about the Java Message Service?
Answer: The Java Message Service is compelling for these reasons:
- It is the first enterprise messaging API that has achieved wide industry support.
- It simplifies the development of enterprise applications by providing standard messaging concepts and conventions that apply across a wide range of enterprise messaging systems.
- It leverages existing, enterprise-proven messaging systems.
- Why should developers use the Java Message Service?
Answer: The Java Message Service makes it easy to do the following:
- Write portable, message-based business applications
- 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?
Answer: Message-based applications are fundamentally different from remote procedure call based applications.Once a developer understands how best to employ both technologies, the JMS API 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 components?
Answer: Since J2EE version 1.2 was released, Enterprise JavaBeans components have been able to use the JMS API to send enterprise messages and receive them synchronously.The Java 2 SDK, Enterprise Edition, version 1.3, now available, provides a new kind of enterprise bean, the message-driven bean, that allows an enterprise application to receive messages asynchronously.
- What is the relationship between the Java Message Service and the Java Naming and Directory Interface (JNDI) API?
Answer: The JMS API, like the other Java Enterprise APIs, uses the JNDI API for administration.The JMS API 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 preconfigured objects.This insures that JMS applications are easy to deploy and administer.
- What is the relationship between the Java Message Service and the Java DataBase Connectivity (JDBC) API?
Answer: JMS clients may also use the JDBC API.They may use both the JMS API and the JDBC API in the same transaction.In most cases, they will achieve this automatically by implementing these clients as enterprise beans.They may also use the Java Transaction API.
- What is the relationship between the Java Message Service, the Java Transaction API, and the Java Transaction Service?
Answer: The Java Transaction API (JTA) provides a client API for delimiting distributed transactions and an API for accessing a resource's ability to participate in a distributed transaction.A JMS client may use JTA to delimit distributed transactions.A JMS provider can optionally support distributed transactions via JTA.
The Java Transaction Service (JTS) can be used with the JMS API to form distributed transactions that combine message sends and receives with database updates and other JTS aware services.These services should be handled automatically when a JMS client is run from within an application server such as a J2EE server; however, it is also possible for JMS clients to program them explicitly.
- Where can I find a JMS API discussion group?
Answer: You can find a JMS API discussion forum at http://java.sun.com/j2ee/community/forums/index.html.You must be a member of the Java Developer Connection to join this forum.
- What JDK release does the JMS API need?
Answer: The JMS API requires JDK/JRE release 1.1.x or higher.