The message you are responding to was sent to the ActiveMQ users mailing list, not directly to you. You received it because you are *subscribed* to the ActiveMQ users mailing list.
Justin On Thu, Jul 20, 2023 at 10:16 AM KOROTKOVA Anna < anna.korotk...@raiffeisen.ru> wrote: > Hi. > Sorry? Is it for me? > > -----Original Message----- > From: Markus Lenzbauer <m.lenzba...@znt.de> > Sent: Thursday, July 20, 2023 6:05 PM > To: users@activemq.apache.org > Subject: RE: Re: Activemq 5.18.1 integration with Wildfly 28.0.1 > > Hi Matt, > > do you have a rough estimation when we can expect this to be available? > > Regards, > Markus > > On 2023/06/28 14:22:47 Matt Pavlovich wrote: > > Hello Anil- > > > > ActiveMQ support for Jakarta is coming in 5.19.x > > Thanks, > > -Matt > > > On Jun 28, 2023, at 5:52 AM, Anil Kumar Ravva > <ar...@opentext.com.INVALID> wrote: > > > > > > Hi, > > > Please find my query below. > > > > > > > > > We want to integrate Wildly 28.0.1 with Activemq 5.18.1. > > > But we are not able to do this, and the excepetions are coming for > the jakarta namespaces. > > > 1. Wildfly 28.0.1 is using the jakarta namespace. > > > 2. Activemq latest(5.18.1) is using the javax namespace in its jars. > > > > > > So can you suggest is there any workaround to use the activemq > 5.18.1 with wildfly 28.0.1 > > > Is there any plan to upgrade the activemq with jakarta specifications. > > > > > > Am I missing anything here? > > > > > > > > > Regards, > > > > > > Anil > > > > > > > > ----------------------------------- > > This message and any attachment are confidential and may be privileged or > otherwise protected from disclosure. If you are not the intended recipient > any use, distribution, copying or disclosure is strictly prohibited. If you > have received this message in error, please notify the sender immediately > either by telephone or by e-mail and delete this message and any attachment > from your system. Correspondence via e-mail is for information purposes > only. AO Raiffeisenbank neither makes nor accepts legally binding > statements by e-mail unless otherwise agreed. > > ----------------------------------- >
