Hi With ActiveMQ Classic, you have two features depending if you want to use javax.jms or jakarta namespaces.
I didn't update the Artemis features recently, but I bet it needs an update to mimic what we did in Artemis (in terms of features). For instance, the ActiveMQ broker feature doesn't necessarily need the client feature. I will create a ticket for that and I will work on Artemis Karaf features (including new tests). Regards JB On Fri, Oct 31, 2025 at 8:50 AM Stefan Sämgård <[email protected]> wrote: > > Hello, > > We are using the artemis feature in apache karaf (OSGi) > In the same apache karaf we are also using apache camel 4+ > Apache camel has fully moved to jakarta namespace we think. > > Which means that when we are setting up a jms client with apache camel jms > library we need to use a jakarta.jms interface. Right now we are using the > class: > org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory > > In OSGi compatible mode, this class returns a javax.jms interface rather than > a jakarta.jms > Are there any plans in the for upgrading the jakarta.jms from 2.0.3 to > jakarta.jms 3+ dependencies? > > Best Regards, > Stefan Sämgård > CONFIDENTIALITY AND DISCLAIMER NOTICE | Industri-Matematik International AB > This e-mail, including any attachments, is confidential and intended only for > the addressee. > If you are not the intended recipient, please notify us immediately and > delete this e-mail from your system. > Any use or disclosure of the information contained here in is strictly > prohibited. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information, visit: https://activemq.apache.org/contact
