New issue: ModuleClassLoader is final

David M. Lloyd david.lloyd at
Thu Mar 3 03:16:50 UTC 2016

On 03/02/2016 09:08 PM, David M. Lloyd wrote:
> On 03/02/2016 06:12 PM, David M. Lloyd wrote:
>> If ModuleClassLoader is final, then it is impossible to have (for
>> example) an OSGi implementation where OSGi bundles map to modules,
>> because the class loader of OSGi bundles must implement an OSGi
>> interface.  Other containers may also wish to use ModuleClassLoader
>> subclasses to store assocations in similar ways with deployment modules
>> or bundles; the prevalence of the TCCL to mark the currently active
>> application's class loader makes this a particularly useful technique.
> After updating my checkout I see that this class is actually completely
> gone now.  Am I correct in understanding that in the current
> implementation, a Layer can establish any ClassLoader for a module (via
> Layer.ClassLoaderFinder)?

Now Function<String, ClassLoader>, which was going to be my next question...


More information about the jpms-spec-experts mailing list