[
https://issues.apache.org/jira/browse/CAMEL-11517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16076350#comment-16076350
]
Dmitry Volodin commented on CAMEL-11517:
----------------------------------------
It's expected behavior and transferExchange option works as defined, however
tests are not correctly implemented.
All Camel headers are propagated to JMS (AMQ) and headerFilterStrategy need to
be specified for disabling header propagation.
A new issue for fixing tests will create.
> transferExchange option doesn't work as expected
> ------------------------------------------------
>
> Key: CAMEL-11517
> URL: https://issues.apache.org/jira/browse/CAMEL-11517
> Project: Camel
> Issue Type: Bug
> Components: camel-jms
> Affects Versions: 2.20.0
> Reporter: Dmitry Volodin
> Assignee: Dmitry Volodin
> Priority: Minor
> Labels: test
> Attachments: amq-screenshot.png
>
>
> I've tested a camel-amqp component with ActiveMQ Artemis (AMQ) system and
> detected that all Camel Headers (in my case CamelHttp* ) were propagated
> inside the message properties.
> Next, changed some (JmsTransferExchangeTest, JmsInOutTransferExchangeTest)
> transferExchange related tests (from 'transferExchange=true' to
> 'transferExchange=false') and all test were passed successfully that looks
> very strange.
> This issue need to be verify.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
