GitHub user hauler opened a pull request:
https://github.com/apache/camel/pull/1545
Use default ("") exchange for reply-to messages
According to https://www.rabbitmq.com/direct-reply-to.html:
> The RPC server will then see a reply-to property with a generated name.
**It should publish to the default exchange ("")** with the routing key set to
this value.
I'm sending request-reply with:
Object reply = rabbitTemplate.convertSendAndReceive("testexch", "test",
"Ping!");
And consuming with:
from("rabbitmq://localhost:5672/testexch?routingKey=test")
.transform(body().append(" Pong!"));
And without this fix applied I'm not getting any reply because
camel-rabbitmq publishes replies to specified "testexch" exchange instead of
default one ("").
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hauler/camel patch-1
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/1545.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1545
----
commit db08229389f01d58790d10154bf9b2750a9f16d9
Author: hauler <rkalashni...@gmail.com>
Date: 2017-03-16T14:03:40Z
Use default ("") exchange for reply-to messages
According to https://www.rabbitmq.com/direct-reply-to.html
"The RPC server will then see a reply-to property with a generated name. It
should publish to the default exchange ("") with the routing key set to this
value".
This will fix sending correct replies to consumers like this:
from("rabbitmq://localhost:5672/testexch?routingKey=test")
.transform(body().append(" Pong!"));
I'm sending request-reply with:
Object resObj = rabbitTemplate.convertSendAndReceive("testexch", "test",
"Ping!");
And without this fix applied I'm not getting any reply.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
