The Java Message Service specification, version 1.1 is the best source of information for understanding the finer details of JMS.
- The JMS API documentation is essential for JMS programming.
- For enterprise development, you'll need the Java 2 Enterprise Edition. J2EE version 1.2 requires compliant application servers to have the JMS API present, but it does not mandate the presence of a JMS provider; J2EE version 1.3 requires application servers to supply a JMS provider. J2EE version 1.4 requires application servers to supply a JMS provider that supports both domains.
- Message-driven beans, part of the EJB 2.0 specification,
add asynchronous notification abilities to Enterprise JavaBeans containers.
Java Message Service programs using WebSphere MQ v5.3 and WebSphere Studio Application Developer v5", also by Willy Farrell, describes how to obtain, install, and use IBM tools to write JMS programs. ( developerWorks,
- Bobby Woolf shows how JMS 1.1 simplifies messaging with unified domains: ( developerWorks, August 2002).
- Nicholas Whitehead shows you how to make your JMS solution work with any vendor in his article, "Implementing vendor-independent JMS solutions" ( developerWorks,
- For a distillation of the changes in JMS 1.1, see David Currie's "Get the message " ( developerWorks,
- You'll find articles about every aspect of Java programming in
the developerWorks Java technology
- Also see the Java technology zone tutorials page for a complete listing of
free Java-focused tutorials from developerWorks.
Get products and technologies