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 8EA6618535 for ; Tue, 13 Oct 2015 06:03:14 +0000 (UTC) Received: (qmail 64783 invoked by uid 500); 13 Oct 2015 06:03:05 -0000 Delivered-To: apmail-camel-issues-archive@camel.apache.org Received: (qmail 64743 invoked by uid 500); 13 Oct 2015 06:03:05 -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 64733 invoked by uid 99); 13 Oct 2015 06:03:05 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Oct 2015 06:03:05 +0000 Date: Tue, 13 Oct 2015 06:03:05 +0000 (UTC) From: "Claus Ibsen (JIRA)" To: issues@camel.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (CAMEL-9178) Apache Camel is not able to read map-id in Dozer mapping xml but does not throw any error 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-9178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-9178. -------------------------------- Resolution: Fixed Assignee: Claus Ibsen Fix Version/s: 2.16.1 2.17.0 2.15.4 Thanks the type converted needed to lookup the map-id and provide as parameter to dozer. As dozer was not able to do this by itself. > Apache Camel is not able to read map-id in Dozer mapping xml but does not throw any error > ----------------------------------------------------------------------------------------- > > Key: CAMEL-9178 > URL: https://issues.apache.org/jira/browse/CAMEL-9178 > Project: Camel > Issue Type: Improvement > Components: camel-dozer > Affects Versions: 2.12.0, 2.14.0 > Reporter: MADHUMITA > Assignee: Claus Ibsen > Priority: Minor > Fix For: 2.15.4, 2.17.0, 2.16.1 > > > I used camel dozer and configured with a mapping.xml for dozer mapping. > Camel fails to do Dozer mapping for the elements mapped with map-id but does not throw any error. > In camel context file define DozerTypeConverterLoader and DozerBeanMapper as follows: > class="org.apache.camel.converter.dozer.DozerTypeConverterLoader" /> > > > > > dozer/mapping.xml > > > > > where mapping.xml is the file where the dozer mappings should be defined. > > > > Example: > In camel-context camel will look for the mapping for conversion to PortInNotification as defined in the dozer/mapping.xml > > ${body.getNPOOrNPOCOrNPOR.get(0)} > > > > > In mapping.xml: > > > a.b.v1.PortInNotification > x.y.NPOCType > > > requestID.id > requestId > > > referenceID.id > referenceId > > > > > Camel-dozer is not able to trace this mapping,however it does not throw any error and simply returns an object of type PortInNotification with null attributes. > On removal of map-id attribute it is able to correctly lookup the mapping of PortInNotification from the mapping.xml -- This message was sent by Atlassian JIRA (v6.3.4#6332)