Your custom classloader probably does this:
1. Checks the java.class.path system property.
2. Iterates over the jar files there, trying to find one that
includes the thirdparty classes.
3. Loads the classes.
Try this: put the "thirdparty.jar" on the classpath.
If that works, then modify the java.class.path system property
before you launch the custom class loader. If it doesn't, well...
Better yet, ask the third party supplier how the custom class loader
can be configured.
/LS
> From: Korosh Afshar [mailto:[EMAIL PROTECTED]]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
