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 <mattr...@gmail.com> 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). > > 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 > + Spring 6.x > > Thanks, > Matt Pavlovich > > > On Jun 19, 2023, at 11:11 AM, ski n <raymondmees...@gmail.com> wrote: > > > > 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-client > > > > But what about the broker itself? I am using both brokers embedded in a > > Spring Boot application. Is support for the broker on server side already > > planned? Will there be two versions available > > like currently for example with Jetty 10.x (javax) and 11.x (jakarta)? > > > > Raymond > >
