In order to muck about with the ClassLoader to do some stuff with OSGI and RMI we've implemented our own RMIClassLoaderSpi, copied the resultant jar to lib/, added its package to org.osgi.framework.bootdelegation in java6-server.profile and are starting virgo with a -D setting java.rmi.server.RMIClassLoaderSpi so that it uses our own version.
This works great - except in one of my machines where it doesn't and the class is not available to the system at runtime (e.g. Class.forName()).
My question is, are there any tips available regarding how I can debug this? For example, is there a way of finding out what packages are actually being made available by the bootdelegation directive?
Chris Frost Messages: 230 Registered: January 2010 Location: Southampton, England
Have a look at the commands available in the telnet shell. Their are two shells, one for the kernel region and one for the user region, you will need to enable them with their respective configs. In the Virgo Kernel and above their are some extra classloading commands that could help you, just type help to see what else is available.
I have explored this line of enquiry but wasn't able to find the relevant commands or really understand the output of the ones I tried. Would you be able to give me one further hint?
Thanks for the reply,