[
https://issues.apache.org/jira/browse/FELIX-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13054818#comment-13054818
]
Brandon Ehle commented on FELIX-42:
-----------------------------------
Are there any updates on this? I am currently running into this issue when
trying to running HornetQ embedded in a OSGi service.
> Define a strategy for dealing with context class loader usage
> -------------------------------------------------------------
>
> Key: FELIX-42
> URL: https://issues.apache.org/jira/browse/FELIX-42
> Project: Felix
> Issue Type: New Feature
> Components: Framework
> Reporter: Richard S. Hall
> Priority: Minor
>
> Many third-party libraries use the context class loader associated with a
> thread as a means to implement plugins or as a way to gain access to classes
> in a context outside of the library itself, such as from another component or
> module. This mechanism does not play well with the OSGi framework, which does
> its own fair share of class loader magic. Further, the context class loader
> provides access to potentially arbitrary classes, which (from the perspective
> of the OSGi framework) breaks modularity. Regardless, in the interest of
> making Felix play well with these third-party libraries, it is worthwhile to
> investigate whether a strategy for dealing with the context class loader can
> be devised, such as setting the context class loader at the callback entry
> points for each bundle.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
