Dynamic modules and bidirectional interoperation
forax at univ-mlv.fr
forax at univ-mlv.fr
Fri Oct 28 17:01:17 UTC 2016
----- Mail original -----
> De: "mark reinhold" <mark.reinhold at oracle.com>
> À: "Remi Forax" <forax at univ-mlv.fr>
> Cc: jpms-spec-experts at openjdk.java.net
> Envoyé: Vendredi 28 Octobre 2016 18:16:49
> Objet: Re: Dynamic modules and bidirectional interoperation
> 2016/10/28 8:41:41 -0700, Remi Forax <forax at univ-mlv.fr>:
>> De: "mark reinhold" <mark.reinhold at oracle.com>
>> Envoyé: Mercredi 26 Octobre 2016 19:24:47
>>> 2016/10/26 9:32:42 -0700, Thomas Watson <tjwatson at us.ibm.com>,
>>> jpms-spec-comments:
>>>> ...
>>>>
>>>> Will there will be a specified order in which the nodes are traversed
>>>> when there are multiple paths to a node? More specifically will the
>>>> parents have a specified order in which they are delegated to?
>>>
>>> Yes, the parents of a new configuration will be specified in an ordered
>>> list and during resolution they'll be searched depth-first, in the order
>>> in which they occur in the list. Depth-first order makes it easy to
>>> reason about resolution, since it works just like a search path.
>>
>> I fail to seen how this is not a mini-classpath with exactly the same
>> issues as the classpath.
>
> It's not a "mini" class path; it's more like a "mini" or "run time"
> module path. It's better than a class path because it's a means to
> locate whole modules rather than individual types, as discussed in
> SotMS:
>
> http://openjdk.java.net/projects/jigsaw/spec/sotms/#the-module-path
it's not a modulepath it's a moduletreepath,
so i agree it does not have exactly same issue as the classpath, but the main issue is very similar, if you take a look to the list of parents, it's not enough to see which module will be chosen, like with the classpath, if you open all the jars you will find your cookie, with the moduletreepath, if you crawle the tree in deep-first order, you will find your module, in my opinion, in both cases, if you take a look to the list of jars or the list of parents,
you have no idea where to find what you're looking for. And here, it's even worst, because at least the classpath has a string representation.
>
> - Mark
Rémi
More information about the jpms-spec-experts
mailing list