Java Platform Module System : Potential Additional Issue s

[mark.reinhold at oracle.com]

Thanks for raising these issues.  Replies inline below.

2016/3/2 3:30:00 -0800, Andrew Dinn <adinn at redhat.com>:
> Issue:
> 
> The first point at issue in JEP 261 arises under heading/subheading
> "Removed: Bootstrap class-path options/Open design issues" where it says:
> 
> "Should the -Xbootclasspath/a option, and the corresponding JVM TI API,
> be deprecated in JDK 9 with the intent to remove them in JDK 10?"
> 
> Problem:
> 
> Byteman requires the JVMTI API in order to be able to instrument classes
> which belong to the bootstrap. ...
> 
> Possible Resolution:
> 
> Retain this privileged API for JVMTI agents

New issue: http://openjdk.java.net/projects/jigsaw/spec/issues/#BootstrapClassLoaderSearchInJVMTI

> Issue:
> 
> The second point at issue in JEP 261 arises under heading "Risks and
> Assumptions" where it says
> 
> "The java.lang.reflect.AccessibleObject::setAccessible method cannot be
> used to gain access to members of packages that are not exported by
> their defining modules; an InaccessibleObjectException will be thrown.
> If a framework library, such as a serializer, needs access to such
> members then the relevant packages must be exported to the framework
> module either via exports declarations in module descriptors or the
> -XaddExports command-line option."
> 
> Problem:
> 
> Byteman relies upon the use of reflective access via setAccessible to
> enable injected code to invoke non-public methods and read or update
> non-public fields. Such access is critical to support both tracing,
> monitoring and debugging of application behaviour and engineering of
> fault injection scenarios.
> 
> ...
> 
> Possible Resolution:
> 
> Provide agent code with special permissions to employ the setAccessible
> API without risking an InaccessibleObjectException.

New issue: http://openjdk.java.net/projects/jigsaw/spec/issues/#ReflectiveAccessByInstrumentationAgents

- Mark