org.openjdk.jigsaw.Catalog.readLocalModuleInfo

[Jonathan Gibbons]

Should I be concerned that Catalog.readLocalModuleInfo is being called 
an absurdly high number of times during Configurator.configurePaths?

I have a scenario where javac is compiling 3 small modules, and it 
creates a javac-specific impl of Catalog for use by the Configurator. 
The impl of readLocalModuleInfo is being called a total of **416** times 
for these 3 modules.

What seems anomalous to me is that the method is called 
**read**LocalModuleInfo, implying there might be disk activity 
involved.  As such, I presumed, perhaps naively, that it would be called 
once per module id, and the resulting ModuleInfo cached inside the 
Configurator.

Clearly, I can manage to cache the results and avoid creating a new 
ModuleInfo object on every call. But I wonder if other code that impls 
this method is falling into the same trap and assuming it will be called 
just just per module id per use of the Configurator.

-- Jon