Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Sat, 11 Jul 2015 22:19:04 +0000 (UTC)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12501245.1299936891000.163483.1436653144550@Atlassian.JIRA>
In-Reply-To: <JIRA.12501245.1299936891000@Atlassian.JIRA>
References: <JIRA.12501245.1299936891000@Atlassian.JIRA>
 <JIRA.12501245.1299936891942@arcas>
Subject: [jira] [Resolved] (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:all-tabpanel ]

Claus Ibsen resolved CAMEL-3785.
--------------------------------
    Resolution: Won't Fix

> 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 was sent by Atlassian JIRA
(v6.3.4#6332)