WLab’s access to the virtualisation backend, authentication, and data storage was written to enable easy implementation of alternative solutions. Java interfaces and/or abstract classes are used for each function; implementations are provided to access Hyper-V, an LDAP-based directory and XML files respectively.
The diagram illustrates these interfaces and the corresponding implementations provided. Classes shown in white/dotted lines illustrate where future work might potentially take place to provide alternative functionality.
To use any alternative implementations of these interfaces, you will need to modify the Spring configuration accordingly. If, for example, you provide a new implementation of VirtualisationAccess, e.g. VirtualisationAccessVMWareImpl, to make use of it the virtualisationAccess bean in application-properties.xml will need to be modified to refer to your new class. Any parameters your new class expects to be injected will also need to be included in the bean definition.
Further information about these interfaces can be found in the Javadoc, available at http://www.paulneve.com/wlab/javadoc.