Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 01921200C2C for ; Fri, 3 Mar 2017 14:24:49 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id F0EBE160B6D; Fri, 3 Mar 2017 13:24:48 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 470F1160B57 for ; Fri, 3 Mar 2017 14:24:48 +0100 (CET) Received: (qmail 99354 invoked by uid 500); 3 Mar 2017 13:24:47 -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 99342 invoked by uid 99); 3 Mar 2017 13:24:47 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Mar 2017 13:24:47 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 12519C214A for ; Fri, 3 Mar 2017 13:24:47 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -2.347 X-Spam-Level: X-Spam-Status: No, score=-2.347 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-2.999, SPF_NEUTRAL=0.652] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id Tn9LpQ_wZVr8 for ; Fri, 3 Mar 2017 13:24:46 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 1DEBB5FC00 for ; Fri, 3 Mar 2017 13:24:46 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id ACC19E02AB for ; Fri, 3 Mar 2017 13:24:45 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 630EB2415A for ; Fri, 3 Mar 2017 13:24:45 +0000 (UTC) Date: Fri, 3 Mar 2017 13:24:45 +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 archived-at: Fri, 03 Mar 2017 13:24:49 -0000 [ https://issues.apache.org/jira/browse/CAMEL-6511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-6511: ------------------------------- Priority: Minor (was: Major) > auto-enable and detect Dozer mappings > ------------------------------------- > > Key: CAMEL-6511 > URL: https://issues.apache.org/jira/browse/CAMEL-6511 > Project: Camel > Issue Type: New Feature > Components: camel-dozer > Reporter: james strachan > Priority: Minor > > 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.3.15#6346)