ActiveMQ Artemis embraces Jakarta EE
by Domenico Francesco Bruscino
Posted on Friday September 10, 2021 at 12:46PM in Artemis
Jakarta EE is the evolution of Java EE, a set of specifications that enables the world wide community of java developers to work on cloud native java enterprise applications. With Jakarta EE, the community now has an open source project to collaborate on advancing enterprise Java. Jakarta EE’s goal is to accelerate business application development for cloud computing, enabling the migration of real-world workloads to a world of containers, microservices, Kubernetes, service mesh, and other cloud native technologies.
ActiveMQ Artemis provides two clients that implement the Jakarta Messaging specifications: ActiveMQ Artemis JMS Client and ActiveMQ Artemis Jakarta Client. The first client implements Jakarta Messaging 2.0 for Jakarta EE 8 and its maven coordinates are org.apache.activemq:artemis-jms-client. The second implements Jakarta Messaging 3.0 for Jakarta EE 9 and its maven coordinates are org.apache.activemq:artemis-jakarta-client.
Jakarta Messaging is a Java API that allows applications to create, send, receive, and read messages. Jakarta Messaging defines a common set of interfaces and associated semantics that allow programs written in the Java programming language to communicate with other messaging implementations. See the documentation on Using JMS for further details.
Apache ActiveMQ Artemis also provides a simple integration for Jakarta Contexts and Dependency Injection. It can use an embedded broker or connect to a remote broker, its maven coordinates are org.apache.activemq:artemis-cdi-client. Jakarta Dependency Injection specifies a means for obtaining objects in such a way as to maximize reusability, testability and maintainability, compared to traditional approaches such as constructors, factories, and service locators (e.g., JNDI). See the documentation on CDI Integration for further details.
Jakarta Messaging has a lot of pending new features. During the Java EE 8 cycle, a number of them have actually been worked on quite a bit and they could be included in the next release Jakarta Messaging for Jakarta EE 10. ActiveMQ Artemis has completed the migration to Jakarta EE since the 2.18.0 version and it is ready to implement the next Jakarta Messaging specifications.
Comments are closed for this entry.