Thanks Gordon. Adding the link option worked. However, even after
msg.setProperty("x-amqp-0-10.routing-key", "keyX"); // publisher
msg.getProperties()["x-amqp-0-10.routing-key"].asString() is still the
queue name, not "keyX" (at the subscriber);
Is this an expected behavior?
Thank you!
jjw
On Tue, Jan 19, 2016 at 11:53 AM, Gordon Sim <g...@redhat.com> wrote:
> On 01/19/2016 05:23 PM, jjw tectec wrote:
>
>> Hi Gordon,
>>
>> Yes, changing the key name to queue name made messages flow end-to-end.
>> I had also suspected that the routing key wasn't set the way I wanted it
>> be. So I had tried to set and get routing-key property at the client
>> sides:
>>
>> publisher:
>> msg.setProperty("x-amqp-0-10.routing-key", "keyX");
>>
>> subscriber:
>> cout << msg.getProperties()["x-amqp-0-10.routing-key"].asString();
>>
>> But the above code caused the following compilation errors:
>>
>> /usr/bin/ld: /tmp/ccNXSPL7.o: undefined reference to symbol
>> '_ZN4qpid5types7VariantD1Ev'
>> //usr/local/lib/libqpidtypes.so.1: error adding symbols: DSO missing from
>> command line
>>
>> Do you know why was that?
>>
>
> Are you adding -lqpidtypes to your link options when compiling/linking?
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>
