The original question from the forums ( http://forums.novell.com/showthread.php?t=394263 ) follows:
I'm looking for a way to improve the installation "experience" for a
user when installing my Live@edu custom Driver.
The driver works only with the Remote Loader and I would like for the
user to be able to select, when adding a driver using the Remote Loader
Console, my driver from the drop down "Driver" list.
It would appear the RLC is scanning the directory for dll and jar files
- presumably looking for a valid 'header'.
Any assistance/advice would be warmly received!
After looking into it for a while there did not seem to be a pattern with regard to the creation of the JAR files with the classes. Some of the classes had 'dirxml/driver' in their path and others had 'idm/driver'. They were never alone in their directory within the JAR so that was not a variable either. Eventually engineering came back with the following:
[The Remote Loader Console] looks in the .jar files for classes that implement the interface
com.novell.nds.dirxml.driver.DriverShim. The .jar files must not be compressed.
So the main part is the Interface which must be implemented on the class to be loaded. The JAR compression (or non-compression) requirement has been around for quite a while with IDM and apparently this is one reason why.
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.