On 14/01/2016 8:46 PM, Alan Bateman wrote:
On 14/01/2016 04:06, David Holmes wrote:
Is this because the management API's are actually split across the
base module (java.lang.management) and the jdk.management module? If
so that seem messy. If not then I'm not understanding the issue.
The two management modules are:
java.management - exports the standard/Java APIs: java.lang.management
and javax.management.**. This module also has the JMX agent.
jdk.management - this exports the JDK-specific API com.sun.management.
It's possible to create a run-time image that has neither, both, or has
java.management but not jdk.management.
We just need to make sure that VM handles all cases gracefully.
Of course, but I'm having trouble seeing the overall architecture of the
solution or understanding how the problem manifests. Is it just VM
initialization that assumes classes are always present?
Thanks,
David
-Alan
