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
w
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
Thanks Mandy, replies inline...
- Original message -
>
>
> On 3/21/2015 5:12 AM, Peter Firmstone wrote:
> > Just wondering, with the removal of the extensions directory, what's
> > the correct way of specifying a policy provider?
> >
> > We currently have a number of nested policy provi
On 3/21/2015 5:12 AM, Peter Firmstone wrote:
Just wondering, with the removal of the extensions directory, what's the
correct way of specifying a policy provider?
We currently have a number of nested policy providers that are loaded by the
extension classloader.
Do you set the custom polic
Just wondering, with the removal of the extensions directory, what's the
correct way of specifying a policy provider?
We currently have a number of nested policy providers that are loaded by the
extension classloader.
Thanks,
Peter.
