Hi Robbie that's good news.
Did you see my later post? I'd be interested in yours (and others) view
on the following
I'm curious though. What's the reason for validating a replyTo address using
an exchange declare? What I mean by that is that I'd have thought that in
general a reply to
Agreed, that is a bug and the cache is useless (harmful even) as a
result. I have raised a JIRA
(https://issues.apache.org/jira/browse/QPID-3440) for it and attached
a patch with a test to detect it, and update the transport code
generator to fix it.
It hasnt been applied yet though, because it
Thanks for the update Gordon - glad I'm not imagining things :-)
I'm curious though. What's the reason for validating a replyTo address using
an exchange declare? What I mean by that is that I'd have thought that in
general a reply to address gets sent by a producer client as its return
address
On 08/14/2011 08:47 PM, fadams wrote:
Hello all,
In a JMS client I've created an address string of the form:
qmf.default.direct/qmfc-zappa.17410
and used this to create a reply address:
replyAddress = syncSession.createQueue(address);
which is then used in various request/response patterns
