Decoupling components of a software system at compile time and load time
A method, system and computer program product for decoupling components of a software system at load/compile time to accelerate application startup times. In particular, a software components partitioning (SCP) utility pre-defines a number of (implementation) classes to initiate and facilitate the decoupling process. The SCP utility allows the method names and argument lists to be recorded from a remote interface into a local interface which emulates the remote interface. The local interface is augmented with an annotation to define the remote interface. Additionally, a pre-defined keyword is appended to the name of the local interface to enable the creation of a (pre-defined) classname. Furthermore, when the classname is loaded, an implementation (via a Java implementation class, for example) for the remote class is loaded, and the implementation is associated with a dynamic proxy that implements both the local and remote interfaces, on demand.
1. In a data processing system with a Java platform, a method comprising:
pre-defining, at a load/compile time, a number of implementation classes required to facilitate a decoupling of software components, at the load/compile time, to accelerate application startup;
recording one or more method names and one or more argument lists from a required remote interface into a local interface;
augmenting the local interface to include a ProxiesTo annotation that defines the remote interface in order to alert a runtime process that the local interface emulates the remote interface;
initiating the creation of a dynamic proxy;
appending a predefined keyword to a name of the local interface to enable the generation of a new classname;
detecting when the new classname is loaded; and
in response to the new classname being loaded:
loading an implementation for a remote class associated with the remote interface; and
associating the implementation with the dynamic proxy that implements the local and remote interfaces when required by one of an action and a system action.
2. The method of claim 1 , wherein said pre-defining further comprises:
creating one or more classes that enable the remote interface to be defined by the ProxiesTo annotation; and
applying the ProxiesTo annotation as an augmentation to the local interface in the code development process.
3. The method of claim 1 , wherein said initiating further comprises activating a function that returns a dynamic proxy, given a specified class loader and a specified set of interfaces, which set of interfaces includes the remote interface and the local interface.
4. The method of claim 1 , wherein said enabling further comprises creating one or more classes and keywords that enable the generation of a classname to load an implementation for the remote class and to associate the implementation with the dynamic proxy.
5. A computer program product comprising:
a non-transitory computer readable storage medium; and
program source code on said computer readable storage medium that when executed within a data communication device, said program code provides the functionality of:
pre-defining at a load/compile time, a number of implementation classes required to facilitate a decoupling of software components at the load/compile time to accelerate application startup;
recording a set of method names and argument lists from a required remote interface into a local interface;
augmenting the local interface to include a ProxiesTo annotation that defines the remote interface in order to alert the runtime that the local interface emulates the remote interface;
initiating the creation of a dynamic proxy;
appending a predefined keyword to the name of the local interface to enable the generation of a new classname;
detecting when the new classname is loaded; and
in response to the new classname being loaded:
loading an implementation for a remote class associated with the remote interface; and
associating the implementation with the dynamic proxy that implements the local and remote interfaces when required by one of an action and a system action.
6. The computer program product of claim 5 , wherein said code for pre-defining further comprises code for:
creating one or more classes that enable the remote interface to be defined by the ProxiesTo annotation; and
applying the ProxiesTo annotation as an augmentation to the local interface in the code development process.
7. The computer program product of claim 5 , wherein said code for initiating further comprises code for:
employing a function which returns a dynamic proxy given a specified class loader and a specified set of interfaces which set comprises the remote interface and the local interface.
8. The computer program product of claim 5 , wherein said code for enabling further comprises code for, creating one or more classes and keywords that enable the generation of a classname to load an implementation for the remote class and to associate the implementation with the dynamic proxy.
9. A data processing system comprising:
a processor which executes a Java Platform software;
a memory system which stores the Java Platform;
a utility executing on the processor which enables the processor to:
pre-define, at a load/compile time, a number of classes required to facilitate a decoupling of software components at the load/compile time to accelerate application startup;
record a set of method names and argument lists from a required remote interface into a local interface;
augment the local interface to include a ProxiesTo annotation that defines the remote interface in order to alert the runtime that the local interface emulates the remote interface;
initiate the creation of a dynamic proxy;
append a predefined keyword to the name of the local interface to enable the generation of a new classname;
detect when the new classname is loaded; and
in response to the new classname being loaded:
load an implementation for a remote class associated with the remote interface; and
associate the implementation with the dynamic proxy that implements the local and remote interfaces when required by one of an action and a system action.
10. The system of claim 9 , wherein said pre-define function further comprises functions for enabling the processor to:
create one or more classes that enable the remote interface to be defined by the ProxiesTo annotation; and
apply the ProxiesTo annotation as an augmentation to the local interface in the code development process.
11. The system of claim 9 , wherein said functions that enabled the processor to initiate further comprises functions for the processor to:
employ a function which returns a dynamic proxy given a specified class loader and a specified set of interfaces which set comprises the remote interface and the local interface.
12. The system of claim 9 , wherein said functions that enable further comprises functions that enable the processor to create one or more classes and keywords that enable the generation of a classname to load an implementation for the remote class and to associate the implementation with the dynamic proxy.