You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Willem Jiang (JIRA)" <ji...@apache.org> on 2013/11/26 09:54:35 UTC
[jira] [Resolved] (CAMEL-6809) rabbitmq.EXCHANGE_NAME header used
in preference to uri exchange name
[ https://issues.apache.org/jira/browse/CAMEL-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang resolved CAMEL-6809.
---------------------------------
Resolution: Fixed
Fix Version/s: 2.13.0
2.12.3
Added bridgeEndpoint option to ignore the rabbitmq.EXCHANGE_NAME header.
Applied the patch into trunk and camel-2.12.x branches.
> rabbitmq.EXCHANGE_NAME header used in preference to uri exchange name
> ---------------------------------------------------------------------
>
> Key: CAMEL-6809
> URL: https://issues.apache.org/jira/browse/CAMEL-6809
> Project: Camel
> Issue Type: Improvement
> Components: camel-rabbitmq
> Affects Versions: 2.12.0
> Reporter: Fergus Nelson
> Assignee: Willem Jiang
> Fix For: 2.12.3, 2.13.0
>
>
> RabbitMQProducer.process method uses the existing rabbitmq.EXCHANGE_NAME header in preference to the exchange name that is part of the endpoint uri. This means that when consuming off one exchange and producing onto another, the rabbitmq.EXCHANGE_NAME needs to be explicitally removed, otherwise the messages will not be sent to the exchange name defined in the destinition uri.
> The exchange name is a required part of the endpoint uri.
> http://camel.apache.org/rabbitmq.html, so would it be better to ignore the header completely in the RabbitMQProducer? At least then the messages would go where you were expecting them to.
> Happy to submit a pull request on Github if that helps.
--
This message was sent by Atlassian JIRA
(v6.1#6144)