[
https://issues.apache.org/jira/browse/CAMEL-12471?focusedWorklogId=305338&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-305338
]
ASF GitHub Bot logged work on CAMEL-12471:
------------------------------------------
Author: ASF GitHub Bot
Created on: 02/Sep/19 22:21
Start Date: 02/Sep/19 22:21
Worklog Time Spent: 10m
Work Description: hedgy commented on pull request #3134: CAMEL-12471: Fix
overriding rabbit mq exchange name with EXCHANGE_OVE…
URL: https://github.com/apache/camel/pull/3134
…RRIDE_NAME header.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 305338)
Time Spent: 0.5h (was: 20m)
> Dots in RabbitMQ-component headers do not work
> ----------------------------------------------
>
> Key: CAMEL-12471
> URL: https://issues.apache.org/jira/browse/CAMEL-12471
> Project: Camel
> Issue Type: Bug
> Components: camel-rabbitmq
> Affects Versions: 2.21.0
> Reporter: Peter
> Priority: Minor
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Setting Exchange headers does not work for all the constants. E.g.:
> .setHeader(RabbitMQConstants.DELIVERY_MODE, constant("2"))
> .setHeader(RabbitMQConstants.EXCHANGE_OVERRIDE_NAME, constant("test"))
> .setHeader(RabbitMQConstants.ROUTING_KEY, simple("${header.msgType}"))
> Only the header for routingkey is set as header. If I set the headers like
> this, so without using a dot (.) then all get set, but are useless ofcourse:
> .setHeader("rabbitmq_DELIVERY_MODE", constant("2"))
> .setHeader("rabbitmq_EXCHANGE_OVERRIDE_NAME", constant("test"))
> .setHeader(RabbitMQConstants.ROUTING_KEY, simple("${header.msgType}"))
> So only the ROUTING_KEY header exists in the function "publishToRabbitMQ" of
> the "RabbitMQMessagePublisher".
> I'm still checking but for now I have no idea why the header for the
> routingkey is working as expected but the others not.
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
