Jetty strives very hard to stop classloader pollution between contexts.
But then applications can often work very hard to defeat that effort... eg
if they pass an instance of an object via attributes of a cross context
dispatch. Other issues can be caused if classes are put on the server path
and
Sharing 1 WebAppClassLoader across multiple contexts is not a
supported configuration.
The lifecycle alone would undo/change behaviors in nasty ways across your
contexts.
I'm frankly surprised you didn't hit issues already, merely starting
multiple contexts sharing a single WebAppClassLoader
Hi Community,
I've been experiencing weird classloading issues due to redeployment of
a single WAR Application containing latest Jersey Framework.
In the current setup I'm using Jetty 9.4.44 as Application Container to
host webapplications on a Linux host. In the past I've restarted the
Jetty
