[CAMEL-8349] Context should be started with defined TCCL

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.15.0
• Component/s: camel-core
• Estimated Complexity: Unknown
• Assignee: Willem Jiang
• Reporter: Thomas Diesler
• Created: 13/Feb/15 09:51
• Updated: 04/Mar/15 08:19
• Resolved: 26/Feb/15 09:15

Description

During CamelContext.start() we may call into various 3rd party modules that rely on resource discovery through TCCL. Therefore, we should provide a well defined value for TCCL during context start.

In the WildFly integration layer I attempted to do this using events. This approach is flawed however because there is no guarantee of event delivery. Conceptually, the requirement for a certain TCCL by 3rd party should not leak into client code. Instead, camel should be dealing with these TCCL requirements and provide client code a way to defined the ClassLoader associated with the context. the role of which is the ApplicationClassLoader.

I therefore propose setting the TCCL to the ApplicationClassLoader (if there is one) just before we call into doStart()

Issue Links

• is related to: CAMEL-7759 Using the TCCL as the default value of ApplicationContextClassLoader in DefaultCamelContext