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 B202D11D3E for ; Mon, 25 Aug 2014 06:20:58 +0000 (UTC) Received: (qmail 31978 invoked by uid 500); 25 Aug 2014 06:20:58 -0000 Delivered-To: apmail-camel-issues-archive@camel.apache.org Received: (qmail 31941 invoked by uid 500); 25 Aug 2014 06:20:58 -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 31931 invoked by uid 99); 25 Aug 2014 06:20:58 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Aug 2014 06:20:58 +0000 Date: Mon, 25 Aug 2014 06:20:58 +0000 (UTC) From: "Claus Ibsen (JIRA)" To: issues@camel.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CAMEL-6511) auto-enable and detect Dozer mappings 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-6511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-6511: ------------------------------- Fix Version/s: (was: 2.14.0) (was: Future) 2.15.0 > auto-enable and detect Dozer mappings > ------------------------------------- > > Key: CAMEL-6511 > URL: https://issues.apache.org/jira/browse/CAMEL-6511 > Project: Camel > Issue Type: New Feature > Reporter: james strachan > Assignee: Grzegorz Grzybek > Fix For: 2.15.0 > > > I wonder if we can avoid having to explicitly configure in Spring the DozerTypeConverterLoader class along with the explicit org.dozer.DozerBeanMapper; but instead get camel-core to auto-detect (with META-INF/services or similar OSGi tricks) the presence of the camel-dozer library and then just automatically create it. e.g. using a META-INF/services/..../TypeConverterLoader file to force the lazy creation of the DozerTypeConverterLoader object. > Then also automatically scan for all META-INF/services/dozerMapping.xml files and register them all. > For more info see: > http://camel.apache.org/dozer-type-conversion.html > Then it would feel like Dozer mapping files are kinda like Camel type converters; that they are just automatically discovered and configured on the fly - if they are defined in the convention-over-configuration way? > e.g. given that camel-dozer is on the classpath, all that is required is you add a META-INF/services/dozer/mapping.xml file to the classpath and hey-presto all the type conversions defined inside it are immediately available to Camel -- This message was sent by Atlassian JIRA (v6.2#6252)