E271828, please see the message below from Tim Bish, the developer who knows the C++ interface the best. Are you willing to use the test setup you already have plus a debugger to figure out why this isn't working as expected?
Tim ---------- Forwarded message ---------- From: "Timothy Bish" <tabish...@gmail.com> Date: May 26, 2017 7:45 AM Subject: Re: BlobMessage in ActiveMQ-CPP by now 2017 To: "Tim Bain" <tb...@alumni.duke.edu> Cc: On 05/26/2017 08:40 AM, Tim Bain wrote: > > That's not how I expected it would work. Every message ultimately gets > converted to the OpenWire protocol, no matter which language you use, so I > assumed that methods with the same name in the different languages would > translate to the same OpenWire content, but it sounds like that's not > happening here. > > Tim Bish, could you please explain what users can expect in terms of > compatibility when using different languages for sending and receiving > messages? Or is the fact that this particular method isn't compatible > across languages just a bug? > > > I would suggest some debugging and testing as it's still unclear what's > been done here. The plumbing of BlobMessage is mostly not implemented > outside Java so I don't expect the upload download bits would work, other > things should but I welcome others who want to contribute to dive in and > help out with the code and testing. > > On May 25, 2017 7:09 PM, "e271828" <165442...@qq.com> wrote: > >> Both c++ and java have already implemente setStringProperty and >> getStringProperty. >> But I found that send blobmessage by useing the setStringProperty in c++ >> which can not been received by useing the getStringProperty in java. >> >> >> >> -- >> View this message in context: http://activemq.2283324.n4.nab >> ble.com/BlobMessage-in-ActiveMQ-CPP-by-now-2017-tp4726457p4726595.html >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >> > > -- > Tim Bish > twitter: @tabish121 > blog: http://timbish.blogspot.com/ > >
