[ 
https://issues.apache.org/jira/browse/CAMEL-14593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen resolved CAMEL-14593.
---------------------------------
    Fix Version/s: 3.1.0
       Resolution: Fixed

> Eager type converter creation breaks WildFly integration
> --------------------------------------------------------
>
>                 Key: CAMEL-14593
>                 URL: https://issues.apache.org/jira/browse/CAMEL-14593
>             Project: Camel
>          Issue Type: Bug
>    Affects Versions: 3.1.0
>            Reporter: Thomas Diesler
>            Assignee: Thomas Diesler
>            Priority: Major
>             Fix For: 3.1.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Below we have a callback to the wildfly-camel integration that registers 
> additional PackageScanClassResolvers, which are able scan stuff on a modules 
> classpath.
>  
> {code:java}
>         // Call all registered trackers with this context
>         // Note, this may use a partially constructed object
>         CamelContextTracker.notifyContextCreated(this);
> {code}
> Doing this after creating the type converters, results in camel not seeing 
> converters from the deployment module. Other stuff may also be missing.
> CrossRef: https://github.com/wildfly-extras/wildfly-camel/issues/2951



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to