camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-6511) auto-enable and detect Dozer mappings
Date Mon, 25 Aug 2014 06:20:59 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-6511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14108799#comment-14108799
] 

Claus Ibsen commented on CAMEL-6511:
------------------------------------

We may wanna give some thoughs to some kind of way a component can enlist some service that
reacts upon events such as when a camel context is being created | started | stopped etc.
so it can do some work - such as scanning for dozer mappings and auto enlisting them.

> 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)

Mime
View raw message