[
https://issues.apache.org/jira/browse/FELIX-5727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls resolved FELIX-5727.
-------------------------------
Resolution: Fixed
I reworked how we handle extension bundles in r1813111.
In a nutshell, we now use the appendToClassPathForInstrumentation method on the
appclassloader when the framework has been loaded by the systemclassloader.
Otherwise, we fallback to use the URLClassloader.addURL (if we have been loaded
by a URLClassLoader) but use the files directly now (via file urls).
On java9, that means that if we happen to be loaded by the
PlattformClassLoader, extension bundles will work - provided the jvm has been
started with:
--add-opens=java.base/jdk.internal.loader=ALL-UNNAMED.
Furthermore, I added a ServiceLoader service lookup which allows to provide
extensions that can handle addition to classloaders that are not
URLClassLoaders nor the system classloader.
(I'll document all of this when I'm done with the parent task).
> Allow extension bundles when loaded with the PlattformClassLoader
> -----------------------------------------------------------------
>
> Key: FELIX-5727
> URL: https://issues.apache.org/jira/browse/FELIX-5727
> Project: Felix
> Issue Type: Sub-task
> Components: Framework
> Affects Versions: framework-5.6.8
> Reporter: Karl Pauls
> Assignee: Karl Pauls
> Fix For: framework-5.6.10
>
>
> By default, we are loaded with the PlattformClassloader, which happens to not
> be a URLClassLoder anymore. As a consequence, extension bundles don't work
> anymore.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
