[
https://issues.apache.org/jira/browse/CAMEL-12329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-12329.
---------------------------------
Resolution: Fixed
Also fixed the integration tests.
> 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
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 2.21.0
>
>
> 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)
