[
https://issues.apache.org/jira/browse/CAMEL-12069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16280401#comment-16280401
]
Pascal Schumacher edited comment on CAMEL-12069 at 12/6/17 4:37 PM:
--------------------------------------------------------------------
Looks like this was unintentionally broken by
https://github.com/apache/camel/commit/5dd59162e4ac9335e497934b8d662f598cb779d1
was (Author: pascalschumacher):
Looks like this was broken unintentionally broken by
https://github.com/apache/camel/commit/5dd59162e4ac9335e497934b8d662f598cb779d1
> ActiveMQ/JMS component: transferExchange option does not transfer exchange
> properties
> -------------------------------------------------------------------------------------
>
> Key: CAMEL-12069
> URL: https://issues.apache.org/jira/browse/CAMEL-12069
> Project: Camel
> Issue Type: Bug
> Components: camel-activemq, camel-jms
> Affects Versions: 2.20.1
> Reporter: Pascal Schumacher
>
> The ActiveMQ/JMS component documenation generated from the
> _JMSComponent#setTransferExchange_ javadoc states:
> {quote}
> You can transfer the exchange over the wire instead of just the body and
> headers.
> The following fields are transferred: In body, Out body, Fault body, In
> headers, Out headers, Fault headers, exchange properties, exchange exception.
> {quote}
> But exchange properties are *not* transfered.
> I debuged into this and noticed that _JMSBinding#createJmsMessage_ calls
> _DefaultExchangeHolder.marshal(exchange, false,
> endpoint.isAllowSerializedHeaders())_ when _transferExchange_ is _true_. The
> _false_ parameter is the reason that the exchange properties are not included
> in the JMS message.
> This should either be fixed or the documentation should be updated.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
