[
https://issues.apache.org/jira/browse/CAMEL-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13832380#comment-13832380
]
Willem Jiang commented on CAMEL-6809:
-------------------------------------
In Camel the message header can override the setting of the endpoint, if you
want to build a proxy, I think we could add an option bridgeEndpoint in
camel-rabbitmq endpoint to let the producer ignore the header setting as we do
in camel-http.
> 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
>
> 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)
