All,
I ran into a situation where having a null parent ClassLoader appears to
have no visibility outside of the core Java platform packages. This is
expected, as confirmed by this bug report:
https://bugs.openjdk.java.net/browse/JDK-8161269
If I want my custom ClassLoader to be able to see, for example, the
classes in the java.sql module, I think I want to use the "platform
class loader" as the parent instead of null.
Does that sound correct? Or should it be the system class loader? Or a
different one altogether?
Thanks,
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
