You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/01/28 11:20:39 UTC

[jira] [Commented] (CAMEL-9545) Dozer classloading may fail with spring based context

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

ASF GitHub Bot commented on CAMEL-9545:
---------------------------------------

GitHub user tdiesler opened a pull request:

    https://github.com/apache/camel/pull/814

    [CAMEL-9545] Dozer classloading may fail with spring based context

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/tdiesler/camel CAMEL-9545

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/camel/pull/814.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #814
    
----
commit 2a71f4257d508ffd05d2d5f447a65294296eae5c
Author: Thomas Diesler <th...@jboss.com>
Date:   2016-01-28T10:18:08Z

    [CAMEL-9545] Dozer classloading may fail with spring based context

----


> Dozer classloading may fail with spring based context
> -----------------------------------------------------
>
>                 Key: CAMEL-9545
>                 URL: https://issues.apache.org/jira/browse/CAMEL-9545
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-dozer
>            Reporter: Thomas Diesler
>             Fix For: 2.17.0, 2.16.3
>
>
> Dozer assumes that it can load user types from the classloader of the dozer implementation, which is of course quite wrong in a modular environment. In Camel we have a hack in DozerTypeConverterLoader, which prior to creating the bean mapper forces the classLoaderBeanName in GlobalSettings to DozerThreadContextClassLoader and then initialises the TCCL with the application ClassLoader associated with the CamelContext.
> With a spring based context, this code path is not executed and therefore the application ClassLoader associated with the CamelContext ignored.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)