Richard S. Hall wrote:
> Yes, the main approach for solving such situations is to use probing
> (i.e, the extender model) as opposed to asking the context class loader.
That's not acceptable. We need a way to make this work. We can't
change the code in the JDK (e.g., JAF) to depend on some OSGi-specific
workaround. Even if this means adding a non-standard feature to the
OSGi class loaders, we need to fix this.