As Justin said, see https://activemq.apache.org/jms2. The 5.18.x zip distribution is only javax.jms API package based, nothing will change for the zip until 5.19.x adds jakarta.jms API package support for the wider codebase, something which is still being worked on (e.g https://github.com/apache/activemq/pull/996). The transitional activemq-client-jakarta module added in 5.18.x which is jakarta.jms API package based, is a separate module available from Maven Central. Note that per the https://activemq.apache.org/jms2 page it can't be used embedded in the same JVM as the broker (or javax based activemq-client). Note also you should avoid the 5.18.0 activemq-client-jakarta as it was actually broken, be sure to use 5.18.1 or the current 5.18.2.
On Mon, 7 Aug 2023 at 18:55, Justin Bertram <jbert...@apache.org> wrote: > > Which exact client library are you using? > > ActiveMQ 5.18.x introduced the activemq-client-jakarta module which is > separate from the normal JMS client. You can find the versions here [1]. > > That said, the client is not "fully compatible" as certain methods have not > yet been implemented. See this page [2] for more details. > > > Justin > > [1] > https://central.sonatype.com/artifact/org.apache.activemq/activemq-client-jakarta/5.18.0/versions > [2] https://activemq.apache.org/jms2 > > On Mon, Aug 7, 2023 at 12:43 PM Jayesh Vaishnav <jayeshk.vaish...@gmail.com> > wrote: > > > Hello, > > > > I am currently migrating to activemq5.18 which has support for jakarta > > namespace, however there are still references to old javax packages, I am > > getting ClassNotFoundException for javax.jms.JMSException, the right > > package should be jakarta.jms > > > > In the zip distribution, I see jakarta-2.X is used for which the underlying > > package is still javax. Rather to fully support jakarta namespace, we > > should move to jakarta 3.x > > > > Seems we are not fully compliant yet. can we make changes to fix this > > > > THanks > >
