[
https://issues.apache.org/jira/browse/CAMEL-12471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-12471.
---------------------------------
Fix Version/s: 3.0.0.RC2
2.25.0
2.24.2
2.23.4
3.0.0
Resolution: Fixed
> 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
> Fix For: 3.0.0, 2.23.4, 2.24.2, 2.25.0, 3.0.0.RC2
>
> Time Spent: 40m
> 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)
