Thanks for the information. The move to Jakarta is already further than
expected.
Raymond
On Mon, Jun 19, 2023 at 7:32 PM Matt Pavlovich wrote:
> Hi Raymond-
>
> The plan is currently in ‘draft’ and will firm up once the jakarta-based
> ActiveMQ broker is released (tentatively 5.19.0).
>
> Acti
Hi Raymond-
The plan is currently in ‘draft’ and will firm up once the jakarta-based
ActiveMQ broker is released (tentatively 5.19.0).
ActiveMQ 5.18.x LTS
+ JDK 11
+ javax.jms
+ JMS 2.0
+ Spring 5.x
ActiveMQ 5.19.x
+ JDK 17
+ jakarta.jms
+ Jakarta Messaging 3.x
A Jakarta-compatible broker implementation of ActiveMQ "Classic" is not yet
available, but work is underway. You can track progress here [1].
ActiveMQ Artemis started shipping a Jakarta-compatible broker
implementation in 2.17.0 at the same time as the client was made available
(February 2021). Se
For both the Classic (Since 5.18.0) and Artemis (Since 2.17.0) there is
support for the Jakarta namespace in the client:
1. Classic:
https://mvnrepository.com/artifact/org.apache.activemq/activemq-client-jakarta
2. Artemis:
https://mvnrepository.com/artifact/org.apache.activemq/artemis-jakarta-cli