We've been trying to get an ActiveMQ client build using the new jakarta classes, we had been playing with shading Active MQ (byte code update of imports) inspired by https://github.com/apache/tomcat-jakartaee-migration, we could maybe use this while we wait for the official 3.0 support, we are just thinking about the timelines to make a proper decision.
What do you think? are you aware of anybody trying a similar approach? Regards On Sun, 25 Sept 2022 at 21:59, Andrés Torres García <towers...@gmail.com> wrote: > Understood Matt, right now we don't use the new API methods, what we are > looking for is JMS 3 compatibility with JMS 1 features. > > As mentioned Spring Boot 3 has removed the support and we are checking if > we can keep it or if we need to move on. Do you have any ETAs in mind for > the JMS 2.0/3.0? like first half of 2023 o second half? > > Regards > > On Wed, 21 Sept 2022 at 17:34, Matt Pavlovich <mattr...@gmail.com> wrote: > >> Hi Andrés- >> >> The remaining operations are pretty straight forward and I plan on >> getting to them here shortly. Thank you for the offer of help— the most >> pressing need is to get real-world feedback from users. If you have cycles >> to do some feedback testing, that would be great! The feature status is >> still “tech preview". >> >> 1. Setup a SNAPSHOT build from ‘main’ and test against your application >> use cases in your environment. Specifically, test the JMS 2.0 APIs methods >> 2. Review the doc page (https://activemq.apache.org/jms2 < >> https://activemq.apache.org/jms2>) and let us know if there are other >> things we should call out. >> >> Thanks, >> Matt Pavlovich >> >> > On Sep 21, 2022, at 5:30 AM, Andrés Torres García <towers...@gmail.com> >> wrote: >> > >> > Hi Matt, >> > >> > I can see https://github.com/apache/activemq/pull/729 nice! Is there a >> way >> > we can help and contribute? do we have a list of pending tasks to be >> tackle? >> > >> > Regards >> > >> > On Tue, 20 Sept 2022 at 19:41, Matt Pavlovich <mattr...@gmail.com> >> wrote: >> > >> >> Hi Andrés- >> >> >> >> Works has already begun on JMS 2.0 support that is a pre-req to >> supporting >> >> jakarta and JMS 3.0. The first few patches have been merged. >> >> >> >> Keep an eye out for the release notes for general availability. >> >> >> >> Thanks, >> >> Matt Pavlovich >> >> >> >>> On Sep 20, 2022, at 2:57 AM, Andrés Torres García < >> towers...@gmail.com> >> >> wrote: >> >>> >> >>> Hi there, >> >>> >> >>> Active MQ is our default Message Broker for asynchronous >> communication. >> >>> >> >>> ActiveMQ support has been removed >> >>> <https://github.com/spring-projects/spring-boot/issues/28591>from >> Spring >> >>> Boot 3/Framework 6 due to ActiveMQ client not supporting a JMS 3.0 >> >> client. >> >>> Due to the migration from *javax.jms* to the *jakarta.jms* in JEE9 it >> >> looks >> >>> like it won't be possible to use JMS 1/2, so we won't be able to use >> >> Active >> >>> MQ client as-is. >> >>> >> >>> We use Spring Cloud Stream >> >>> < >> >> >> https://community.backbase.com/documentation/ServiceSDK/latest/use_spring_cloud_stream >> >>> >> >>> to abstract the message broker, so there is an opportunity to swap to >> a >> >>> different broker. >> >>> >> >>> We could also explore Artemis, the next major version of ActiveMQ (v6) >> >> with >> >>> a JMS 3.0 client. >> >>> >> >>> Our doubt is: is the community interested in a JMS 3.0 client for >> >> ActiveMQ? >> >>> we could work on it and create a PR in >> >> https://github.com/apache/activemq, >> >>> any thoughts? >> >>> >> >>> We also tried a byte code transformation of ActiveMQ client to change >> >>> imports from javax.jms to jakarta.jms using the *maven-shade-plugin*. >> but >> >>> it feels a little bit hacky to put that in Production. >> >>> >> >>> Thanks in advance >> >> >> >> >> >>
