[
https://issues.apache.org/jira/browse/CAMEL-7728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14113422#comment-14113422
]
Tomohisa Igarashi commented on CAMEL-7728:
------------------------------------------
FYI - I needed to do CamelContext.setApplicationContextClassLoader() explicitly
before adding route to get work with this fix. Apparently the CamelContext
application context class loader is initialized with the class loader other
than bundle deployment class loader on karaf by default.
The original TCCL at deploying SwitchYard quickstart bundle:
BundleClassLoader{bundle=[DelegatingBundle:
[org.switchyard.quickstarts.switchyard-camel-mqtt-binding [246],
org.ops4j.pax.cdi.weld [117], org.jboss.weld.osgi-bundle [115],
org.switchyard.components.switchyard-component-bean [210],
org.apache.deltaspike.core.deltaspike-core-api [118]]],parent=null}
ApplicationContextClassLoader in CamelContext:
org.apache.felix.framework.BundleWiringImpl@54f6b00e
> Setup the TCCL before create the instance from the BaseResolver
> ---------------------------------------------------------------
>
> Key: CAMEL-7728
> URL: https://issues.apache.org/jira/browse/CAMEL-7728
> Project: Camel
> Issue Type: Improvement
> Components: camel-osgi
> Reporter: Willem Jiang
> Assignee: Willem Jiang
> Fix For: 2.12.5, 2.13.3, 2.14.0
>
>
> It could be useful for creating the instance if we can set up the TCCL with
> the camel application context class loader in the OSGi world.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
