Re: "Are there any other differences you have noted?"
Well yeah :-) as we've previously discussed Event subscriptions appear to
return MapMessages in 0.8 and BytesMessages (which need to be decoded into
Lists as per your example) in 0.10
clearly I can use instanceof to get the Message derived type, but I was
curious about alternatives as I'm not fond of overusing instanceof.
On a (QMF) related note I'm making real progress on my auditing client using
the info you've previously supplied one thing is troubling me though. I
noticed a post a couple of days ago on the subject of "Object IDs in QMF v2
API". I've been using your example code to pull out queues/exchanges etc and
I'm definitely seeing objectID (using ((Map)object.get("_object_id"));) but
the API post seems to suggest "In the v2 API, the object ID is called
DataAddr. Refer to the hasAddr and getAddr methods in the Data class, "
which don't look anything like I'm pulling out.
Gordon Sim wrote:
>
>
> Really, there should not be changes that aren't backward compatible,
> else the QMF messages themselves should provide sufficient context to
> determine how to correctly interpret them.
>
> The one difference I've seen is in the content-type. Unfortunately that
> doesn't seem to be exposed through JMS(?). Are there any other
> differences you have noted?
>
>
--
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-tp6511290p6512339.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]
