Method, system, and program for loading program components

• US 20040019887A1
• Filed: 07/25/2002
• Published: 01/29/2004
• Est. Priority Date: 07/25/2002
• Status: Abandoned Application

• Current Assignee: Microsystems Company LLC
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Taylor, Brandon E., Connor, William H.
• Application Number:
  US10/205,753
• Publication Number:
  US 20040019887A1
• Time in Patent Office: Days
• US Class Current: 717/166
• CPC Class Codes: G06F 9/445 Program loading or initiating bootstrapping G06F9/4401; security arrangements for program loading or initiating G06F21/57

Abstract

Provided are a method, system, and program for loading program components into a runtime environment. A loader hierarchy is provided indicating an order in which loaders are invoked to load multiple types of program components. A plurality of first type loaders are used to load a first type of program components that are capable of being used by a second type of program components loaded by at least one second type loader. The second type loader is defined at a lower level in the loader hierarchy than the first type component loaders.

Claims

1. A method for loading program components into a runtime environment, comprising:

providing a loader hierarchy indicating an order in which loaders are invoked to load multiple types of program components; and

using a plurality of first type loaders to load a first type of program components that are capable of being used by a second type of program components loaded by at least one second type loader, wherein each second type loader is defined at a lower level in the loader hierarchy than the first type component loaders.

2. The method of claim 1, wherein the first type of program components comprise shared program components, the second type of program components comprise non-shared program components, the first type loaders comprise shared component loaders, the at least one second type loader comprises a non-shared component loader, and wherein non-shared program components loaded by one non-shared component loader is not capable of being used by non-shared program components loaded by other non-shared component loaders.

3. The method of claim 2, wherein the shared program components comprise common interfaces enabling communication between components in the system.

4. The method of claim 2, wherein the non-shared program components loaded by the at least one non-shared component loader comprises variable system components that are a member of a set of non-shared program components comprising:

services, facility implementations, plug-ins, and dynamically loaded modules.

5. The method of claim 2, further comprising:

using multiple non-shared component loaders to load sets of non-shared program components;

determining whether one set of non-shared program components loaded by one non-shared component loader are available to be removed from the runtime environment; and

indicating the determined set of non-shared program components as available for removal from the runtime environment.

6. The method of claim 2, further comprising:

providing annotations for each shared component loader to provide information on the shared program components loaded by the shared component loader, wherein the annotations for one shared program component loader do not include annotations for shared program components loaded by other shared component loaders.

7. The method of claim 2, wherein different security policies are associated with different shared component loaders, thereby providing different security policies for shared program components loaded by different shared component class loaders.

8. The method of claim 1, wherein the first and second types of program components to load include class files including interfaces and wherein the first type and second type loaders load interfaces of the class files into the runtime environment.

9. The method of claim 8, wherein the first type and second type loaders comprise Java class loaders.

10. The method of claim 9, wherein the first type of loaders comprise root class loaders and wherein the second type of loaders comprise component class loaders.

11. The method of claim 1, further comprising:

using the loader hierarchy to determine one first type or second type component loader to use to load one second type program component capable of being loaded by one second type loader.

12. The method of claim 11, wherein using the loader hierarchy to load the second type program component capable of being loaded by one second type loader comprises:

determining a highest first type loader according to the loader hierarchy capable of loading the second type program component; and

using the determined highest first type loader to load the second type program component if one first type component loader is capable of loading the second type program component.

13. The method of claim 12, further comprising:

using the second type program loader capable of loading the second type program component if no first type component loader is capable of loading the second type program component.

14. A system for loading program components into a runtime environment, comprising:

means for providing a loader hierarchy indicating an order in which loaders are invoked to load multiple types of program components; and

means for using a plurality of first type loaders to load a first type of program components that are capable of being used by a second type of program components loaded by at least one second type loader, wherein each second type loader is defined at a lower level in the loader hierarchy than the first type component loaders.

15. The system of claim 14, wherein the first type of program components comprise shared program components, the second type of program components comprise non-shared program components, the first type loaders comprise shared component loaders, the at least one second type loader comprises a non-shared component loader, and wherein non-shared program components loaded by one non-shared component loader is not capable of being used by non-shared program components loaded by other non-shared component loaders.

16. The system of claim 15, wherein the shared program components comprise common interfaces enabling communication between components in the system.

17. The system of claim 16, wherein the non-shared program components loaded by the at least one non-shared component loader comprises variable system components that are a member of a set of non-shared program components comprising:

services, facility implementations, plug-ins, and dynamically loaded modules.

18. The system of claim 15, further comprising:

means for using multiple non-shared component loaders to load sets of non-shared program components;

means for determining whether one set of non-shared program components loaded by one non-shared component loader are available to be removed from the runtime environment; and

means for indicating the determined set of non-shared program components as available for removal from the runtime environment.

19. The system of claim 15, further comprising:

means for providing annotations for each shared component loader to provide information on the shared program components loaded by the shared component loader,

wherein the annotations for one shared program component loader do not include annotations for shared program components loaded by other shared component loaders.

20. The system of claim 15, wherein different security policies are associated with different shared component loaders, thereby providing different security policies for shared program components loaded by different shared component class loaders.

21. The system of claim 14, wherein the first and second types of program components to load include class files including interfaces and wherein the first type and second type loaders load interfaces of the class files into the runtime environment.

22. The system of claim 21, wherein the first type and second type loaders comprise Java class loaders.

23. The system of claim 22, wherein the first type of loaders comprise root class loaders and wherein the second type of loaders comprise component class loaders.

24. The system of claim 14, further comprising:

means for using the loader hierarchy to determine one first type or second type component loader to use to load one second type program component capable of being loaded by one second type loader.

25. The system of claim 24, wherein the means for using the loader hierarchy to load the second type program component capable of being loaded by one second type loader further performs:

determining a highest first type loader according to the loader hierarchy capable of loading the second type program component; and

using the determined highest first type loader to load the second type program component if one first type component loader is capable of loading the second type program component.

26. The system of claim 25, further comprising:

means for using the second type program loader capable of loading the second type program component if no first type component loader is capable of loading the second type program component.

27. An article of manufacture for loading program components into a runtime environment, wherein the article of manufacture causes operations to be performed, the operations comprising:

providing a loader hierarchy indicating an order in which loaders are invoked to load multiple types of program components; and

using a plurality of first type loaders to load a first type of program components that are capable of being used by a second type of program components loaded by at least one second type loader, wherein each second type loader is defined at a lower level in the loader hierarchy than the first type component loaders.

28. The article of manufacture of claim 27, wherein the first type of program components comprise shared program components, the second type of program components comprise non-shared program components, the first type loaders comprise shared component loaders, the at least one second type loader comprises a non-shared component loader, and wherein non-shared program components loaded by one non-shared component loader is not capable of being used by non-shared program components loaded by other non-shared component loaders.

29. The article of manufacture of claim 28, wherein the shared program components comprise common interfaces enabling communication between components in the system.

30. The article of manufacture of claim 28, wherein the non-shared program components loaded by the at least one non-shared component loader comprises variable system components that are a member of a set of non-shared program components comprising:

services, facility implementations, plug-ins, and dynamically loaded modules.

31. The article of manufacture of claim 28, further comprising:

using multiple non-shared component loaders to load sets of non-shared program components;

determining whether one set of non-shared program components loaded by one non-shared component loader are available to be removed from the runtime environment; and

indicating the determined set of non-shared program components as available for removal from the runtime environment.

32. The article of manufacture of claim 28, further comprising:

providing annotations for each shared component loader to provide information on the shared program components loaded by the shared component loader, wherein the annotations for one shared program component loader do not include annotations for shared program components loaded by other shared component loaders.

33. The article of manufacture of claim 28, wherein different security policies are associated with different shared component loaders, thereby providing different security policies for shared program components loaded by different shared component class loaders.

34. The article of manufacture of claim 27, wherein the first and second types of program components to load include class files including interfaces and wherein the first type and second type loaders load interfaces of the class files into the runtime environment.

35. The article of manufacture of claim 34, wherein the first type and second type loaders comprise Java class loaders.

36. The article of manufacture of claim 35, wherein the first type of loaders comprise root class loaders and wherein the second type of loaders comprise component class loaders.

37. The article of manufacture of claim 27, further comprising:

using the loader hierarchy to determine one first type or second type component loader to use to load one second type program component capable of being loaded by one second type loader.

38. The article of manufacture of claim 37, wherein using the loader hierarchy to load the second type program component capable of being loaded by one second type loader comprises:

determining a highest first type loader according to the loader hierarchy capable of loading the second type program component; and

using the determined highest first type loader to load the second type program component if one first type component loader is capable of loading the second type program component.

39. The article of manufacture of claim 38, further comprising:

using the second type program loader capable of loading the second type program component if no first type component loader is capable of loading the second type program component.

40. A memory device including at least one data structure, comprising:

a loader hierarchy indicating an order in which loaders are invoked to load multiple types of program components, wherein a plurality of first type loaders are used to load a first type of program components that are capable of being used by a second type of program components loaded by at least one second type loader, wherein each second type loader is defined at a lower level in the loader hierarchy than the first type component loaders.

41. The memory device of claim 40, wherein the first type of program components comprise shared program components, the second type of program components comprise non-shared program components, the first type loaders comprise shared component loaders, the at least one second type loader comprises a non-shared component loader, and wherein non-shared program components loaded by one non-shared component loader is not capable of being used by non-shared program components loaded by other non-shared component loaders.

42. The memory device of claim 41, wherein multiple non-shared component loaders are used to load sets of non-shared program components.

43. The memory device of claim 41, further comprising:

annotations for each shared component loader to provide information on the shared program components loaded by the shared component loader, wherein the annotations for one shared program component loader do not include annotations for shared program components loaded by other shared component loaders.

44. The memory device of claim 41, wherein different security policies are associated with different shared component loaders, thereby providing different security policies for shared program components loaded by different shared component class loaders.

45. The memory device of claim 40, wherein the first and second types of program components to load include class files including interfaces and wherein the first type and second type loaders load interfaces of the class files into the runtime environment.

46. The memory device of claim 40, wherein the loader hierarchy is used to determine one first type or second type component loader to use to load one second type program component capable of being loaded by one second type loader.