On 18-01-12 11:15, Peter Firmstone wrote:
This would include adding net.jini.security.Security to that jar file as
well and removing it from jsk-platform.jar
If it is so decided, shall i do the build.xml?
Gr. Sim
--
QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl
Quality
Simon IJskes - QCG wrote:
On 18-01-12 11:15, Peter Firmstone wrote:
This would include adding net.jini.security.Security to that jar file as
well and removing it from jsk-platform.jar
If it is so decided, shall i do the build.xml?
Gr. Sim
Sure, I could use some help.
Cheers,
Peter.
Unlike the Policy Provider, the SecurityManager doesn't need to be
loaded by the extension ClassLoader.
Anyway while designing the new SecurityManager, I've added support for
net.jini.security.SecurityContext and overridden the
SecurityManager.getContext() method, to return a SecurityContext,