Returning a runtime type loaded from an archive in a module system

• US 10,394,528 B2
• Filed: 03/30/2016
• Issued: 08/27/2019
• Est. Priority Date: 03/30/2016
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Zhou, Jiangli, Lam, Ioi Kim, Cheung, Calvin C., Kinnear, Karen Margaret Pearson
• Primary Examiner(s): Miller, Viva
• Application Number:
  US15/085,637
• Publication Number:
  US 20170286065A1
• Time in Patent Office: 1,245 Days
• CPC Class Codes: G06F 8/24 Object-oriented
• CPC Class Codes: G06F 9/44521 Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
• CPC Class Codes: G06F 9/44563 Sharing
• CPC Class Codes: G06F 9/449 Object-oriented method invocation or resolution
• CPC Class Codes: G06F 9/45504 Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators

Abstract

Returning a runtime type loaded from an archive in a module system is disclosed. Operations include (a) identifying, by a class loader implemented in a runtime environment, an archived runtime type loaded into an archive from a module source; (b) identifying a particular package associated with the archived runtime type; (c) determining that the particular package is defined to a runtime module that is defined to (i) the class loader or (ii) any class loader in the class loader hierarchy to which the class loader delegates; and (d) returning directly or indirectly, by the class loader, a runtime type loaded based on the archived runtime type from the archive.

Claims

1. A non-transitory computer readable medium comprising instructions which, when executed by one or more hardware processors, cause performance of operations comprising:

identifying, by a class loader implemented in a first runtime environment, an archived runtime type loaded into an archive from a module source;

identifying a particular package associated with the archived runtime type;

determining whether the particular package is defined to any runtime module, of a module system, that is defined to (i) the class loader or (ii) any class loader in a class loader hierarchy to which the class loader delegates, in the first runtime environment;

responsive at least to determining that the particular package is not defined to any runtime module that is defined to (i) the class loader or (ii) any class loader in the class loader hierarchy to which the class loader delegates, in the first runtime environment;

refraining from loading any runtime type based on the archived runtime type from the archive;

identifying, by the class loader implemented in a second runtime environment, the archived runtime type loaded into the archive from the module source;

determining whether the particular package is defined to any runtime module, of the module system, that is defined to (i) the class loader or (ii) any class loader in the class loader hierarchy to which the class loader delegates, in the second runtime environment;

responsive at least to determining that the particular package is defined to a runtime module that is defined to (i) the class loader or (ii) any class loader in the class loader hierarchy to which the class loader delegates, in the second runtime environment;

returning directly or indirectly, by the class loader, a runtime type loaded based on the archived runtime type from the archive; and

wherein runtime type visibility is enforced by the module system based at least in part on readability of one or more runtime modules as defined in the module system.

2. The medium of claim 1, wherein the module system enforces runtime type accessibility in the first runtime environment.

3. The medium of claim 1, wherein:

determining that the particular package is defined to the runtime module that is defined to (i) the class loader or (ii) any class loader in the class loader hierarchy to which the class loader delegates comprises;

determining that the runtime module is defined to the class loader; and

returning directly or indirectly, by the class loader, the runtime type loaded based on the archived runtime type from the archive comprises;

loading, by the class loader, the runtime type based on the archived runtime type from the archive.

4. The medium of claim 1, wherein refraining from loading the runtime type based on the archived runtime type from the archive is further responsive to:

determining that the archived runtime type was loaded into the archive from the module source.

5. The medium of claim 1, wherein returning directly or indirectly, by the class loader, the runtime type loaded based on the archived runtime type from the archive is further responsive to:

determining that the archived runtime type was loaded into the archive from the module source.

6. The medium of claim 1, wherein returning directly or indirectly, by the class loader, the runtime type loaded based on the archived runtime type from the archive comprises:

storing the runtime type in a memory space used by the first runtime environment to execute operations recited by the runtime type.

7. The medium of claim 1, wherein returning directly or indirectly, by the class loader, the runtime type loaded based on the archived runtime type from the archive comprises:

storing the runtime type in a heap memory.

8. The medium of claim 1, wherein the operations further comprise:

identifying the particular package in one or more statements of the archived runtime type.

9. The medium of claim 1, wherein the class loader hierarchy to which the class loader delegates comprises a parent class loader of the class loader.

10. The medium of claim 1, wherein identifying a particular package associated with the archived runtime type comprises:

identifying that a package membership declared by the archived runtime type identifies the particular package.

11. A non-transitory computer readable medium comprising instructions which, when executed by one or more hardware processors, cause performance of operations comprising:

identifying, by a class loader implemented in a runtime environment, an archived runtime type loaded into an archive from a namespace;

determining whether the archived runtime type is associated with any package that is defined to any runtime module, of a module system, that is defined to (i) the class loader or (ii) any class loader in a class loader hierarchy to which the class loader delegates; and

responsive at least to (a) determining that the archived runtime type is not associated with any package that is defined to any runtime module that is defined to (i) the class loader or (ii) any class loader in the class loader hierarchy to which the class loader delegates, and (b) determining that the archived runtime type was loaded into the archive from the namespace associated with a parent class loader of the class loader;

loading, by the parent class loader, a runtime type based on the archived runtime type from the archive;

passing the runtime type from the parent class loader to the class loader;

returning, by the class loader, the runtime type loaded based on the archived runtime type from the archive; and

wherein runtime type visibility is enforced by the module system based at least in part on readability of one or more runtime modules as defined in the module system.

12. The medium of claim 11, wherein the module system enforces runtime type accessibility in the runtime environment.

13. The medium of claim 11, wherein the operations further comprise:

identifying, by the class loader implemented in a second runtime environment, the archived runtime type loaded into the archive from the namespace;

determining whether the archived runtime type is associated with any package that is defined to any runtime module, of the module system, that is defined to (i) the class loader or (ii) any class loader in a class loader hierarchy to which the class loader delegates, in the second runtime environment; and

responsive at least to determining that the archived runtime type is associated with a package that is defined to a runtime module that is defined to (i) the class loader or (ii) any class loader in the class loader hierarchy to which the class loader delegates, in the second runtime environment;

refraining from loading any runtime type based on the archived runtime type from the archive.

14. The medium of claim 13, wherein refraining from loading the runtime type based on the archived runtime type from the archive is further responsive to determining that the archived runtime type was loaded into the archive from the namespace.

15. A non-transitory computer readable medium comprising instructions which, when executed by one or more hardware processors, cause performance of operations comprising:

identifying, by a class loader implemented in a first runtime environment, an archived runtime type loaded into an archive from a module source;

identifying a particular package associated with the archived runtime type;

determining whether the particular package is defined to any runtime module, of a module system, that is defined to (i) the class loader or (ii) any class loader in a class loader hierarchy to which the class loader delegates, in the first runtime environment;

responsive at least to determining that the particular package is defined to a runtime module that is defined to a parent class loader of the class loader, in the class loader hierarchy to which the class loader delegates, in the first runtime environment;

loading, by the parent class loader, a runtime type based on the archived runtime type from the archive;

passing the runtime type from the parent class loader to the class loader;

returning, by the class loader, the runtime type loaded based on the archived runtime type from the archive;

wherein runtime type visibility is enforced by the module system based at least in part on readability of one or more runtime modules as defined in the module system.

16. The medium of claim 15, wherein the operations further comprise:

identifying, by the class loader implemented in a second runtime environment, the archived runtime type loaded into the archive from the module source;

determining whether the particular package is defined to any runtime module, of the module system, that is defined to (i) the class loader or (ii) any class loader in a class loader hierarchy to which the class loader delegates, in the second runtime environment;

responsive at least to determining that the particular package is not defined to any runtime module that is defined to (i) the class loader or (ii) any class loader in the class loader hierarchy to which the class loader delegates, in the second runtime environment;

refraining from loading any runtime type based on the archived runtime type from the archive.

17. The medium of claim 15, wherein the module system enforces runtime type accessibility in the first runtime environment.

18. The medium of claim 15, wherein returning, by the class loader, the runtime type loaded based on the archived runtime type from the archive comprises:

storing the runtime type in a memory space used to execute operations recited by the runtime type.

19. The medium of claim 15, wherein returning, by the class loader, the runtime type loaded based on the archived runtime type from the archive comprises:

storing the runtime type in a heap memory.

20. The medium of claim 15, wherein the operations further comprise:

identifying the particular package in one or more statements of the archived runtime type.