Abstract: A system and method for integrating legacy code into a component-based system. A component-based system is provided that allows legacy components to locate necessary artifacts, and includes: a context finder that is installed as a context classloader, wherein the context finder analyzes an execution stack to identify a component that initiated a context classloader call during runtime; and a buddy loading system that examines the component to determine if the component requires buddy loading to locate an artifact and locates the artifact using a predefined policy.

Abstract: A method, system, tool, and program product for more efficiently utilizing Java property resource bundles. Specifically, under the present invention, the string key of a resource bundle is changed to allow it to take up less space in memory. This may be accomplished by converting the key values from string type to integer type values. In the alternative, this may be accomplished by converting the entire property resource bundle to a Java class. This conversion may occur during design time or, in the alternative, may happen at run time of an application that is to access the Java property resource bundle. The conversion of the resource bundle to a class eliminates the run-time errors due to the Java run-time environment's ability to determine the existence of required values. This conversion further improves memory utilization by removing the string keys.

Abstract: A system and method for integrating legacy code into a component-based system. A component-based system is provided that allows legacy components to locate necessary artifacts, and includes: a context finder that is installed as a context classloader, wherein the context finder analyzes an execution stack to identify a component that initiated a context classloader call during runtime; and a buddy loading system that examines the component to determine if the component requires buddy loading to locate an artifact and locates the artifact using a predefined policy.

Abstract: Provided is a method and tool for automatically including libraries in a buildpath. While developing a package, a user creates a list of potential libraries in a special classpath container but does not add these libraries to the project manifest. The method tracks the packages used in the project and, once a particular package is used, or referenced, the user is notified if the libraries necessary for that particular package are not in the manifest and will thus not be available at runtime. The user can then add the required library or libraries to the manifest. The user can also set an option so that the tool automatically adds a library to the manifest when the tool detects that the library is required.

Abstract: Improved techniques are defined for dynamically loading components which have prerequisite relationships more complex than the simple single inheritance chains which are supported with prior art dynamic class loading techniques. Multiple prerequisites are supported in this improved technique, and in preferred embodiments, an arbitrary number of prerequisites may be explicitly specified for a component. Furthermore, techniques are disclosed which enable delaying the loading and initialization of components until such time as a class in the component is actually needed, thereby improving overall efficiency of the system. Optional filtering and export aspects may also be supported to selectively expose classes for use by dependent components and to enable a component to opt out of re-exporting the classes of its prerequisites, respectively.

Abstract: Improved techniques are defined for dynamically loading components which have prerequisite relationships more complex than the simple single inheritance chains which are supported with prior art dynamic class loading techniques. Multiple prerequisites are supported in this improved technique, and in preferred embodiments, an arbitrary number of prerequisites may be explicitly specified for a component. Furthermore, techniques are disclosed which enable delaying the loading and initialization of components until such time as a class in the component is actually needed, thereby improving overall efficiency of the system. Optional filtering and export aspects may also be supported to selectively expose classes for use by dependent components and to enable a component to opt out of re-exporting the classes of its prerequisites, respectively.