You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2018/03/07 07:45:00 UTC

[jira] [Created] (CAMEL-12329) camel-rabbitmq - Use another header for exchange override header in producer

Claus Ibsen created CAMEL-12329:
-----------------------------------

             Summary: camel-rabbitmq - Use another header for exchange override header in producer
                 Key: CAMEL-12329
                 URL: https://issues.apache.org/jira/browse/CAMEL-12329
             Project: Camel
          Issue Type: Improvement
          Components: camel-rabbitmq
            Reporter: Claus Ibsen


See CAMEL-12324

We should not let rabbitmq.EXCHANGE_NAME be used as the override destination for the producer. As this can lead to the problem with

from foo

  to bar

Will route foo -> foo instead.

So if the end user want to use a header to route to another destination that configured in the endpoint uri, you would need to use some other header for that, so rabbitmq.EXCHANGE_NAME becomes "read-only" and dont affect anything. This is also how JMS component works etc.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)