Hello Keith,
Normally, with a major release, I could expect some broken APIs when developing code for an older version of the Qpid Broker such as REST API for communicating with the broker or any configuration related disruptive changes. Does the 7.0 version include any disruptive change? Or if I just bump the version of my broker to 7.0 (from 6.0), it will work out of the box? Regards, Adel ________________________________ From: Keith W <[email protected]> Sent: Wednesday, September 27, 2017 9:38:15 AM To: [email protected] Subject: Plans for Qpid Broker J v7.0 Hi all, Qpid Broker J (the Java Broker) is stabilising ready for the next release. The major user facing changes in this release will be: much improved AMQP 1.0 support, support for JMS 2.0 clients implementing the AMQP 1.0 JMS bind mapping, and much improved message conversion to benefit users with applications using AMQP 1.0 and the older AMQP protocols. We hope to be putting out an RC in a few weeks time. This anyone has any additional needs, please discuss here. cheers, Keith. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
