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

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.16.3, 2.17.0
• Component/s: camel-dozer
• Estimated Complexity: Unknown
• Assignee: Claus Ibsen
• Reporter: Thomas Diesler
• Created: 28/Jan/16 10:16
• Updated: 29/Jan/16 07:14
• Resolved: 28/Jan/16 10:27

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

Issue Links

• is related to: CAMEL-8748 DozerBeanMapper cannot instantiate DozerThreadContextClassLoader