Return-Path: X-Original-To: apmail-camel-issues-archive@minotaur.apache.org Delivered-To: apmail-camel-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 977B7179E3 for ; Tue, 14 Apr 2015 05:44:12 +0000 (UTC) Received: (qmail 34604 invoked by uid 500); 14 Apr 2015 05:44:12 -0000 Delivered-To: apmail-camel-issues-archive@camel.apache.org Received: (qmail 34566 invoked by uid 500); 14 Apr 2015 05:44:12 -0000 Mailing-List: contact issues-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list issues@camel.apache.org Received: (qmail 34557 invoked by uid 99); 14 Apr 2015 05:44:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Apr 2015 05:44:12 +0000 Date: Tue, 14 Apr 2015 05:44:12 +0000 (UTC) From: "Claus Ibsen (JIRA)" To: issues@camel.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (CAMEL-8628) camel-dozer component fails when multiple expressions are used in a mapping MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CAMEL-8628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-8628. -------------------------------- Resolution: Fixed Fix Version/s: 2.16.0 2.15.2 Assignee: Claus Ibsen Thanks for the PR > camel-dozer component fails when multiple expressions are used in a mapping > --------------------------------------------------------------------------- > > Key: CAMEL-8628 > URL: https://issues.apache.org/jira/browse/CAMEL-8628 > Project: Camel > Issue Type: Bug > Components: camel-dozer > Affects Versions: 2.15.1 > Reporter: Keith Babo > Assignee: Claus Ibsen > Fix For: 2.15.2, 2.16.0 > > > The reference to the current exchange is cleared on each invocation of ExpressionMapper in the done() method. If a mapping file contains multiple expression mappings, the first expression clears out the exchange reference and subsequent expression mappings fail with: > {noformat} > java.lang.IllegalStateException: Current exchange has not been set for ExpressionMapper > {noformat} > Fix is to not clear the reference in ExpressionMapper.done(). We should do this in DozerProducer after all mappings in the mapping file have completed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)