> On Mar 31, 2017, at 1:10 PM, Alan Bateman <alan.bate...@oracle.com> wrote: > > On 31/03/2017 17:36, Sergey Bylokhov wrote: > >> Hello, >> Please review the fix for jdk9. >> >> There is an optional dependency of java.datatransfer module from >> java.desktop. If the java.desktop module is not present then the application >> will not be able to use java.awt.Image and related DataFlavor.imageFlavor. >> So the specification is updated to clarify this behavior. Note that the text >> «not successfully loaded» is used, because it is also used for the similar >> issue in the constructor of this class. >> >> Bug: https://bugs.openjdk.java.net/browse/JDK-8177672 >> Webrev can be found at: http://cr.openjdk.java.net/~serb/8177672/webrev.00 > I think I would go for something like: > > "Return null if java.awt.Image is not visible, the java.desktop module is not > loaded, or the java.desktop module is not in the run-time image."
This is better. Sergey - the “not readable” part is no longer applicable as reflective access to module is readable by default [1]. We should go through the existing javadoc e.g. MXBean [2] and clean up - that’s a separate issue that we will follow up. Mandy [1] http://openjdk.java.net/projects/jigsaw/spec/issues/#ReflectionWithoutReadability [2] http://download.java.net/java/jdk9/docs/api/javax/management/MXBean.html