Re: ActiveMQ client support for JMS 3.0

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 wrote: > Understood Matt, right now we don't use the new API methods, what we are > looking for is

Re: ActiveMQ client support for JMS 3.0

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 > wrote: > > &

ActiveMQ client support for JMS 3.0

Hi there, Active MQ is our default Message Broker for asynchronous communication. ActiveMQ support has been removed from Spring Boot 3/Framework 6 due to ActiveMQ client not supporting a JMS 3.0 client. Due to the migration from

Re: ActiveMQ client support for JMS 3.0

he 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 Ga