Project Jigsaw: Phase Two

mark.reinhold at mark.reinhold at
Mon Jul 7 15:42:41 UTC 2014

2014/7/5 20:59 -0700, krasimir.semerdzhiev at
> ...
> This leaves little options for maneuvering to application server providers,
> different than restarting the app server process. That's (to date) is the
> only reliable way to ensure that a certain application has been properly
> unloaded, regardless how buggy its implementation is.
> It would be great to have a more clear statement in the document (even in
> the case that it falls in the "non requirements" section) to clarify
> whether Jigsaw in Java 9 will have any impact/effect on the above-described
> scenario. I certainly understand that in order to offer a way for Java EE
> application servers to reliably unload/reload modules/applications at
> runtime - this will most probably require an extension of the Java Language
> Specification, which as far as I get it - is currently out of scope for the
> Jigsaw project.

You're right: Providing a means by which an app server can forcibly
terminate and unload an errant application is well beyond the scope
of Jigsaw.  As Alan indicated, it's a very tough problem.  I'll add
a non-requirement in the next draft, just to be perfectly clear on

- Mark

More information about the jigsaw-dev mailing list