You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "james strachan (JIRA)" <ji...@apache.org> on 2013/07/04 14:53:48 UTC

[jira] [Created] (CAMEL-6511) auto-enable and detect Dozer mappings

james strachan created CAMEL-6511:
-------------------------------------

             Summary: 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


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.

Then also automatically scan for all META-INF/services/dozer/mapping.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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira