On 08/07/2016 20:38, Jason Greene wrote:
Now I realize that there is an effort underway to de-privilege modules, but I
suspect that a portion of the JDK will continue to enjoy special power for
precisely the same usability concerns that apply to frameworks / standards
which extend the platform.
Just on terminology again. The effort to "de-privilege" modules
defence-in-depth where we have been moving the non-core modules out of
the boot loader (where they have all security permissions) to the
platform class loader where they can be configured with less (and if
possible minimum) security permissions.
As regards "enjoy special power" then the only module that is known to
the VM and module system is "java.base". The java.base module, as you
probably know, is the core of the system. The java.base modules has the
VM, java.lang.**, the implementation of core reflection, method handles,
and everything else that make up the core runtime and APIs. The other 70
or so standard and JDK-specific modules [1] are just modules, no
different to user modules that are deployed on the application module path.
-Alan
[1] http://openjdk.java.net/jeps/200
