A deployed plugin can load classes from the system classloader.
This can be very problematic if the plugin ships a library which is already part of the system classloader.
The DeploymentManager of Vert.x takes care of creating the classloader.
Is it possible to affect classloading using the JPMS?
How can we ensure that the plugin code always runs in dedicated thread that is bound to the isolating class loader? Currently the plugin request code is not being executed in the plugin verticle eventloop.
Jotschi
commented
5 years ago
A deployed plugin can load classes from the system classloader. This can be very problematic if the plugin ships a library which is already part of the system classloader.
The DeploymentManager of Vert.x takes care of creating the classloader.
We have a test which actually tests that loading of parent deps works: https://github.com/gentics/vertx-filesystem-service-factory/blob/32dd3c8247934b944d4944b6693b3ae99a8baef8/src/test/java/io/vertx/filesystem/FilesystemVerticleFactoryTest.java#L146
Questions