Fraser, In JMS there is the meta data properties in the Connection object. So I guess we should be able to leverage that, atleast using a custom property.
For the following methods, we return the AMQP protocol version. con.getMetaData().getProviderMajorVersion() con.getMetaData().getProviderMinorVersion() Perhaps what's appropriate here is to report the broker's release version and then the AMQP version could be a JMSX custom property. For con.getMetaData().getProviderVersion() we return (for the C++ broker) Version qpid (Client: [exported] ; Broker [<unkown>] ; Protocol: [ 0-10] ) I think it's meant to report the client and broker release versions. If the brokers can send the release version as a connection property we should be able to expose them as either the provider version or via a custom JMSX prop. Could you open a JIRA with your requirement? I can follow up and post a patch and see if I can get it in time for 0-12. Regards, Rajith On Fri, Jun 24, 2011 at 4:31 AM, fadams <[email protected]> wrote: > As it says in the subject. > > The reason why I'm asking is that there seems to be some differences in QMF > between 0.8 and 0.10 and it would be nice to program clients defensively. > > Cheers, > Fraser. > > -- > View this message in context: > http://apache-qpid-users.2158936.n2.nabble.com/Is-there-any-easy-way-for-a-client-to-detect-which-broker-version-it-s-connecting-to-tp6511290p6511290.html > Sent from the Apache Qpid users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:[email protected] > > --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
