[
https://issues.apache.org/jira/browse/CAMEL-9545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Diesler updated CAMEL-9545:
----------------------------------
Description:
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.
CrossRef: https://github.com/wildfly-extras/wildfly-camel/issues/1035
was:
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.
> 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
> Assignee: Claus Ibsen
> 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.
> CrossRef: https://github.com/wildfly-extras/wildfly-camel/issues/1035
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
