[
https://issues.apache.org/jira/browse/CAMEL-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025285#comment-13025285
]
Heath Kesler commented on CAMEL-3785:
-------------------------------------
Can we just ignore mapMessage on request/reply in the ProducerTemplate and
handle the message as usual. But streamline the processing on async with
mapMessage=false?
> Routing JMS messages with mapMessage=false should be optimized
> --------------------------------------------------------------
>
> Key: CAMEL-3785
> URL: https://issues.apache.org/jira/browse/CAMEL-3785
> Project: Camel
> Issue Type: Improvement
> Components: camel-core, camel-jms
> Affects Versions: 2.7.0
> Reporter: Claus Ibsen
> Fix For: 3.0.0
>
>
> 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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
