Major Description
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.)