Please ask questions on the users mailing list. There are no 3.6.0 or 4.2.0 versions of the old AMQP 0-x qpid-client, so I guess you are really referencing Camel versions there. Given that and the rest of your mail, I think what you are more specifically asking is really whether there are plans to support Jakarta Messaging 3.x (which is entirely independent from requiring Java 17, though some projects have updated to both at the same time in their own releases) for the old qpid-client. That client isnt really actively maintained anymore, and there have been no discussion about such support, and the old qpid-client is also only a JMS 1.1 provider anyway so it would need a lot more than just package import renames, so I believe the answer is no.
The newer AMQP 1.0 Qpid JMS client has had Jakarta Messaging 3.x support since its 2.0.0 release in April 2022, current version is 2.5.0. On Fri, 8 Dec 2023 at 22:18, Nimish Date <nimish.d...@gmail.com> wrote: > > Hello Team, > > My current Camel application uses PooledConnectionFactory from > org.apache.qpid.client (version 3.6.0). It also creates a JmsConfiguration > object and sets the PooledConnectionFactory object into it. > I'm planning to upgrade camel-jms and qpid-client to 4.2.0. I noticed that > PooledConnectionFactory class in org.apache.qpid.client version 4.2.0 is > using javax.jms.* and not jakarta.jms.* > I wanted to know if there are any plans to support Java 17 for qpid-client > version 4.2.0 > > Appreciate all your efforts and hardwork. > > Thank You, > ND --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
