To the issues:
1) The ReplyTo message property isn't being propagated from sender to
receiver. This is easily notable by trying the examples\messaging
client/server, which fails with a 'Error: no reply address specified
for...'. I noticed this in my own attempt at a request - response pattern,
in which the Address returned from the received message is empty.
2) The nomenclature for specifying the auto-delete node property as part of
an address string isn't working as shown in
qpid\cpp\examples\messaging\client.cpp#49 : Address foo( "#name;
{create:always, type:queue, node-properties:{x-ampq0-10-auto-delete:true}}"
); The queue is created, but not with an auto-delete attribute set.
FWIW, I'm still learning the underlying qpid code or I'd be posting fixes,
it'll take me a few more days to grok data flow through this code, and I'm
still learning my way around boost. I thought I'd raise these to see if I'm
missing something obvious, and to see if I should be opening bugs for these
sorts of issues...
Kerry,
Welcome to the project, The example that you are experimenting with is
the new API with address encapsulation
that we have been working on so that is probably why there are a few
issues on it. thanks for sending them along. This
API is built as a layer ontop of the already hardened API in C++.
Thus, this issue should be reasonably isolated to this layer. If you for
example look at the direct or other examples at
declare_queues.cpp you will see the commands that setup queues. auto
delete will work correctly on these, and reply too as
these features have been used extensively
So I expect, not having looked but the issue is probably that the new
address object is not translating the auto-delete to the
declare call correctly.
Gordon will know for sure as he did this work for C++.
Carl.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
