hg: jigsaw/jigsaw/hotspot: Summary: Allow passing in a non-null module loader to translate to boot loader.
david.holmes at oracle.com
Wed May 23 18:32:13 PDT 2012
On 24/05/2012 10:42 AM, Mandy Chung wrote:
> In module mode, a relevant question is what module do classes loaded by
> the non-module class loader belong to?
I would say they don't, by definition, belong to a module. But this
presumes a hybrid model where you have both "classpath" elements and
modules. But the very question indicates such a hybrid model must exist.
> What types are visible to that non-module class loader?
I'm not sure I understand the question. What types are considered
"visible" to a particular class loader today?
> One initial proposal is to have classes loaded by a non-module class
> loader belong to the module in which that class loader is created.
I don't see why they must be considered part of any module. This seems
to be creating a distinction between a module as a unit of distribution,
and a module as a runtime-entity. I've so far been assuming these are
one and the same.
> Therefore, all types visible to the module will also be visible to that
> non-module class loader. Details are yet to be fleshed out and prototyped.
More information about the jigsaw-dev