I'm not aware of any specific issues in using the two together, however it is not a combination I have tried mysel. The 7.0.0 broker was a major update with various work on its AMQP 1.0 support, plus the 0.11.1 client is now pretty old. We dont plan any more releases in the 0.11.x client stream.
Obviously the JVM version is the governing issue either way, but I'll still note that you can use the JMS 2.0 client with things only built against the 1.1 API, the 2.0 jar just also has to be on the classpath as well at runtime. On 11 January 2018 at 16:55, bryand <[email protected]> wrote: > I am just getting started with qpid broker-j and have installed the latest > release (7.0.0). I'm hoping that qpid broker-j can replace our ActiveMQ > broker. We have some older JMS consumers that are using JMS 1.1 and JDK > 1.7 and can't be upgraded near term so I need to use a qpid jms client at > those older levels. I have successfully prototyped with qpid-jms-0.11.1 > with qpid-broker-j-7.0.0 but wanted to double check using an older qpid jms > release is something that will be ok ('supported' if you will). For our > newer JMS (and AMPQ) consumers I'll plan on using the most current qpid jms > client of Qpid JMS 0.28.0, > > > > -- > Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
