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.
Posted on Wednesday July 19, 2017 at 09:09PM in General
The ActiveMQ PMC is glad to announce the results of the call for logo vote.
The winner is.. with a total of 80 votes:Read More
Posted on Thursday July 13, 2017 at 05:09PM in General
Disclaimer: I am talking about ActiveMQ Artemis internals here, giving tips on how you could achieve something similar on any system.
Systems today make heavy usage of Executors. No matter what system you chose, they are always there... Executors everywhere.
One pitfall they usually bring is: you will have to create one Runnable every time you call the executor:Read More
Posted on Monday July 10, 2017 at 05:45PM in General
Posted on Thursday June 01, 2017 at 02:16PM in ActiveMQ
The Apache ActiveMQ logo was created a few years ago. While the project continues to evolve, the logo needs to be updated to reflect current ActiveMQ technology. So, the PMC has discussed making a “Call For Entry” where you can submit a new ActiveMQ Logo.
TL;DR: Make your Apache ActiveMQ logo submissions as a PR with your files towards in this folder: https://github.com/apache/activemq/tree/master/docs/imgRead More
Posted on Saturday February 04, 2017 at 04:39AM in Artemis
On this blog post I will give a quick tutorial on how to write a .NET client with Artemis, using the AMQP libraries and protocolRead More
Posted on Tuesday December 13, 2016 at 07:50PM in Artemis
ActiveMQ Artemis can be extremely fast in both transactional and non transactional cases.
This article will give you some hints on how to produce messages extremely fast with thousands messages per second in transactional mode.Read More