A quick update on loading or policy providers with the application
classloader on Java 8, until now we have only ever used the extension
classloader.
The only changes I had to make was to add the policy providers to the
classpath, remove code that caused the JVM to exit if a policy provider
wasn't loaded by the extension classloader and add some permissions to
policy files.
I have a total of approximately 2000 tests to run, initial results
yielded 4 test failures out of 150, of these simple changes to policy
files was all that was necessary for these tests to pass.
Many of our tests use multiple jvm's communicating over networks with
SecurityManager and Policy providers enabled.
Will keep you posted on progress.
Regards,
Peter.
On 23/03/2015 9:30 PM, Alan Bateman wrote:
On 22/03/2015 00:48, Mandy Chung wrote:
:
There are some SPIs that need adjustment to support loading the
providers by the application class loader and the policy SPI
should also be updated in JDK 9.
Right, there are a few areas that need to be updated. In the case of
java.security.Policy then it appears to have never specified how the
policy provider is located. From what I can tell then it used to only
load it via the boot loader but was relaxed later to allow for policy
providers that are "installed" into the run-time image and loaded by
the extension loader. This needs to be re-examined now and also
re-examined to see how it will work with modules going forward.
-Alan
