On Apr 26, 2014, at 841PM, Greg Trasuk <tras...@stratuscom.com> wrote:
> > And actually, why shouldn’t they be resolved in the application’s class > loader? Isn’t an application possibly looking for a service with a given > name or address? This is why the application classloader includes jsk-lib.jar in it's classpath. The jsk-platform.jar is in the system classloader, not the application (service) classloader. Take a look at the current jsk-platform.jar, jsk-lib.jar and jsk-dl.jar.
