[CAMEL-8689] camel-dozer: Multiple contexts / bundles - Does not use the correct classloader

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.15.1
• Fix Version/s: 2.14.3, 2.15.3, 2.16.0
• Component/s: camel-dozer
• Estimated Complexity: Unknown
• Assignee: Raúl Kripalani
• Reporter: Raúl Kripalani
• Created: 23/Apr/15 12:37
• Updated: 06/May/15 13:50
• Resolved: 04/May/15 18:54

Description

Dozer is a tough library to work with in a multi-module context, because of its use of singletons for configuration. In an OSGi environment, each bundle will have its own classloader but Dozer's architecture makes it impossible to cater for this scenario nicely. Unfortunately, it expects a single container-wide classloader configured in the BeanContainer singleton.

In Camel we worked around this by providing a custom DozerClassLoader implementation that is aware of the Camel Context, but what happens if we are sharing Dozer across multiple Camel Contexts? The most recently initialized context will override the container-wide classloader.

We need a solution such that the classloader can dynamically change based on the Camel Context that is using the component.

Issue Links

• relates to: CAMEL-8748 DozerBeanMapper cannot instantiate DozerThreadContextClassLoader