Jakarta Messaging 3.0.0 Specification
Jakarta EE, formerly Java EE, has renamed the javax.jms
package into jakarta.jms
with the Jakarta EE 9 release. The Jakarta Messaging 3.0 specification reflects the corresponding change of namespace. EMS implements both Jakarta Messaging 2.0 (javax.jms
namespace) and 3.0 (jakarta.jms
namespace) in the form of two sets of jar files.
To run applications based on the Jakarta Messaging 2.0 API, include in your CLASSPATH
the relevant jar files from the following list:
-
jakarta.jms-api-2.0.3.jar
(which replacesjms-2.0.jar
) -
tibjms.jar
-
tibjmsadmin.jar
-
tibjmsufo.jar
-
tibrvjms.jar
To run applications based on the Jakarta Messaging 3.0 API, primarily for use in the Jakarta EE 9+ world, use the following files instead:
-
jakarta.jms-api-3/jakarta.jms-api-3.0.0.jar
-
jakarta.jms-api-3/jakarta.jms-tibjms.jar
-
jakarta.jms-api-3/jakarta.jms-tibjmsadmin.jar
-
jakarta.jms-api-3/jakarta.jms-tibjmsufo.jar
-
jakarta.jms-api-3/jakarta.jms-tibrvjms.jar
This applies to every mention of a Jakarta Messaging 2.0 based jar file throughout the present book.