Hi Gordon, thanks a million, just tried it out and it worked like a charm!
Cheers, Daniel 2015-01-22 18:31 GMT+01:00 Gordon Sim <[email protected]>: > On 01/22/2015 04:32 PM, Daniel Wenske wrote: > >> I switched on the qpid library logging and can see the properties are >> there. It shows the following: >> >> ------------------------------------------------ >> >> [b9cbdccd-8dec-46e6-a777-4d47e5d80c5a]: 0 <- @transfer(20) [handle=2, >> delivery-id=36, delivery-tag=b"3", message-format=0] (1824705) >> "\x00Sp\xc0\x04\x02AP\x04\x00Sr\xc1\x17\x02\xa1\x0dx- >> opt-to-type\xa1\x05topic\x00Ss\xc0m\x0a\xa1;ID:er0jb01. >> ttt.aaa-56349-1421830015225-3:12667:22:2:202@\xa1\x1dtopic://USERA. >> MasterDataTopic >> @@@@@@\x83\x00\x00\x01K\x12PS\x86\x00St\xc18\x02\xa1\ >> x15uniqueMessageTypeCode\xa1\x1eRD_SNAPSHOT_ALT_INSTRUMENT_ >> IDS\x00Sw\xb1\x00\x1b\xd6\xe5<? >> xml version="1.0" encoding="UTF-8" standalone="yes"?>... (truncated, msg >> content follows...) >> >> ------------------------------------------------ >> >> I am expecting a field called uniqueMessageTypeCode (which I see in the >> dump above) containing a string value RD_SNAPSHOT_ALT_INSTRUMENT_IDS - >> which also seems to be in place. x-opt-to-type (with value "topic") is >> also >> contained, but I manage to extract only this one, not the one I am >> actually >> interested in. >> >> Any help is greatly appreciated & thanks in advance >> > > This looks like https://issues.apache.org/jira/browse/QPID-5908. The > x-opt-type is an annotation, and as per the bug description, on decoding > it, the library is erroneously replacing the properties map with the > annotations map. > > The issue is fixed in 0.30, but you can also set a connection option > 'nest_annotations' to true as a workaround. That way you will get the > x-opt-type annotation within a nested map keyed > 'x-amqp-message-annotations', along side the property. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
