camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CAMEL-12069) ActiveMQ/JMS component: transferExchange option does not transfer exchange properties
Date Wed, 06 Dec 2017 20:02:00 GMT


ASF GitHub Bot commented on CAMEL-12069:

PascalSchumacher opened a new pull request #2139: CAMEL-12069: ActiveMQ/JMS component: transferExchange
option does not…
   … transfer exchange properties
   TransferExchange now includes exchange properties again. This restores the previous behavior
accidentally broken by 5dd59162e4ac9335e497934b8d662f598cb779d1.

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> ActiveMQ/JMS component: transferExchange option does not transfer exchange properties
> -------------------------------------------------------------------------------------
>                 Key: CAMEL-12069
>                 URL:
>             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

View raw message