Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Won't Fix
-
2.7.0
-
None
Description
Look at JmsLoadBalanceFailoverWithForceSendOriginalJmsMessageTest in camel-jms unit tests.
We should maybe try to look for a solution where you can just configure mapMessage=false and transferException=true on the JmsComponent configuration and then don't have to bother anything on the endpoint uri configs.
Also the code in JmsMessage should know its mapMessage=false, and thus avoid extracting headers/body from the underlying JMSMessage to optimize that. It can be a bit tricky though if a ProducerTemplate sends and wants a reply, and thus the message body should be extracted.