Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Wed, 27 Apr 2011 12:48:03 +0000 (UTC)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: dev@camel.apache.org
Message-ID: <76365840.5727.1303908483146.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1898965734.15426.1299936959371.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (CAMEL-3785) Routing JMS messages with
 mapMessage=false should be optimized
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CAMEL-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025773#comment-13025773 ] 

Claus Ibsen commented on CAMEL-3785:
------------------------------------

Yeah we could consider producer template a corner case and have it optimized for regular routes which is what end users uses. 

> 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