camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Diesler (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-7759) Using the TCCL as the default value of ApplicationContextClassLoader in DefaultCamelContext
Date Fri, 13 Feb 2015 10:11:11 GMT

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

Thomas Diesler commented on CAMEL-7759:
---------------------------------------

This would bind the ApplicationContextClassLoader to the TCCL of the thread that happens to
call CamelContext.start(). IHMO, this is unlikely to be correct.

> Using the TCCL as the default value of ApplicationContextClassLoader in DefaultCamelContext
> -------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-7759
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7759
>             Project: Camel
>          Issue Type: Improvement
>            Reporter: Willem Jiang
>            Assignee: Willem Jiang
>             Fix For: 2.14.0
>
>
> Normally, we just the set the TCCL with the classloader which we want to use to load
the application, as camel always try to setup the right ApplicationContextClassLoader with
Spring or Blueprint, it should be OK if we use the TCCL as the default value of camel ApplicationContextClassLoader.



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

Mime
View raw message