Correct. > On Jun 4, 2024, at 7:37 AM, Boeltl, Stefan > <stefan.boe...@fisglobal.com.INVALID> wrote: > > Hi Robbie, > > thanks, that was the one I remembered. > > So if I understand this correctly, we could "mix and match" as we want to and > don't have to be afraid of compatibility issues between 5.18.x (a least > 5.18.4) clients and resource adapter on the on side and 6.x (at least 6.1.0) > broker on the other side? > Thanks! > > Regards > Stefan > > > -----Original Message----- > From: Robbie Gemmell <robbie.gemm...@gmail.com> > Sent: Tuesday, June 4, 2024 12:29 PM > To: users@activemq.apache.org > Subject: Re: Compatibility ActiveMQ Classic 5.18.x resource adapter and > client with 6.x broker > > You will likely have read > https://lists.apache.org/thread/pr2ty60xx54tm3tfnfb1k2hbrmvm59no or the > related Jira https://issues.apache.org/jira/browse/AMQ-9418 > > On Tue, 4 Jun 2024 at 10:54, Boeltl, Stefan > <stefan.boe...@fisglobal.com.invalid> wrote: >> >> Dear committers, >> >> I can't recall where I read about compatibility issues when using 5.18.x >> clients/resource adapter with a 6.x broker (it was something to do with >> javax vs. jakarta namespaces I think), that's why I post the following >> questions: >> >> 1. Are 5.18.x client (activemq-client, so javax namespace) and the resource >> adapter compatible to a 6.x broker (all using Openwire)? >> 2. If not (because of javax/Jakarta clash): would it help to change all >> clients to use activemq-client-jakarta (and what about the resource adapter >> - any way to change to jakarta namespace here?)? >> 3. Any other thoughts for compatibility (besides moving to qpid and AMQP for >> clients - unfortunately there's no XA enabled RA available here) if we need >> to stay on Java 11 (= ActiveMQ 5.18.x) on client side? >> >> Thanks as always! >> >> Stefan >> The information contained in this message is proprietary and/or >> confidential. If you are not the intended recipient, please: (i) delete the >> message and all copies; (ii) do not disclose, distribute or use the message >> in any manner; and (iii) notify the sender immediately. In addition, please >> be aware that any message addressed to our domain is subject to archiving >> and review by persons other than the intended recipient. Thank you. >> Message Encrypted via TLS connection > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@activemq.apache.org > For additional commands, e-mail: users-h...@activemq.apache.org For further > information, visit: https://activemq.apache.org/contact > > The information contained in this message is proprietary and/or confidential. > If you are not the intended recipient, please: (i) delete the message and all > copies; (ii) do not disclose, distribute or use the message in any manner; > and (iii) notify the sender immediately. In addition, please be aware that > any message addressed to our domain is subject to archiving and review by > persons other than the intended recipient. Thank you. > Message Encrypted via TLS connection > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@activemq.apache.org > For additional commands, e-mail: users-h...@activemq.apache.org > For further information, visit: https://activemq.apache.org/contact > >
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@activemq.apache.org For additional commands, e-mail: users-h...@activemq.apache.org For further information, visit: https://activemq.apache.org/contact
