[FELIX-42] Define a strategy for dealing with context class loader usage

• Type: New Feature
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Component/s: Framework
• Assignee: Unassigned
• Reporter: Richard S. Hall
• Created: 28/Dec/05 06:41
• Updated: 25/Jun/11 18:33

Description

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.