Re: Does anyone rely on ProtectionDomain static constructor?

This relates to my other post about a non blocking policy. Basically the two argument constructor was designed around applets and granting permission to code, not subjects, the access decisions were made at ProtectionDomain construction time , the policy is never consulted. Inside Java 2 Plat

Re: Non Blocking java.security.Policy - synchronized method is superclass.

Dan Creswell wrote: On 8 January 2012 11:40, Peter Firmstone wrote: How much can this one synchronized method spoil scalability? Not much as far as I can see - there's going to be a one off initialisation cost and after that it's a fast path with a single reference check and a retur

Build failed in Jenkins: River-trunk-QA-bsd #4

See Changes: [peter_firmstone] River-402 Fix null pointer exception -- [...truncated 8812 lines...] [java] com/sun/jini/test/spec/javaspace/conformance/snapshot/SnapshotTransactionTakeIfExi

Re: Does anyone rely on ProtectionDomain static constructor?

Can you explain a bit more of the motivation for asking the questions below? On 8 January 2012 11:49, Peter Firmstone wrote: > Does anyone rely on static ProtectionDomain's? > > new ProtectionDomain(codeSource, permissions) > > Static domains do not consult the Policy, ever. > > Does anyone rely

Re: Non Blocking java.security.Policy - synchronized method is superclass.

On 8 January 2012 11:40, Peter Firmstone wrote: > Appended is a new java.security.Policy implementation, it fully supports > the existing java policy syntax and accepts alternate PolicyParser's. > > All state is immutable, except for 2 volatile references, referents > replaced, not mutated, when t

Does anyone rely on ProtectionDomain static constructor?

Does anyone rely on static ProtectionDomain's? new ProtectionDomain(codeSource, permissions) Static domains do not consult the Policy, ever. Does anyone rely on a ProtectionDomain that doesn't consult the installed policy for security decisions? Regards, Peter.

Non Blocking java.security.Policy - synchronized method is superclass.

Appended is a new java.security.Policy implementation, it fully supports the existing java policy syntax and accepts alternate PolicyParser's. All state is immutable, except for 2 volatile references, referents replaced, not mutated, when the policy is updated. One referent is an array containin

Non Blocking java.security.Policy - synchronized method is superclass.

Appended is a new java.security.Policy implementation, it fully supports the existing java policy syntax and accepts alternate PolicyParser's. All state is immutable, except for 2 volatile references, referents replaced, not mutated, when the policy is updated. One referent is an array contai