[
https://issues.apache.org/activemq/browse/CAMEL-870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-870.
-------------------------------
Resolution: Fixed
Committed revision 756685.
Updated wiki as well.
> camel-jms - transfer exchange
> -----------------------------
>
> Key: CAMEL-870
> URL: https://issues.apache.org/activemq/browse/CAMEL-870
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-jms
> Affects Versions: 1.3.0, 1.4.0
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.0.0
>
>
> If end-users uses JMS queues as DeadLetterChannel it only send the original
> exchange body and primitive headers. The original caused exception is lost.
> The camel-jms component could benefit from the *exchangeTransfer* option that
> we introduced to camel-mina to send the exchange itself over the wire.
> However end-users must make sure if using remote queues that the consumer of
> the message can deserialize the exchange object.
> Also end-users have requests to be able to set the kind of JmsMessage that is
> used (Text, Byte, Object, etc.)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
