I would suspect that this is the issue too. There are several places that
doAs() is used to read property values so that security contexts that are
already active can be utilized when appropriate. It seems like that is the case
here.
Gregg Wonderly
Sim IJskes - QCG wrote:
Peter Firmstone wrote:
I worked it out; in PreferredClassProvider, the property
java.rmi.server.codebase is retrieved by a static initializer block,
the DynamicPolicyProvider hasn't been set up properly when the
permission check executes, it is rejected. I've added an object
method to check if the value is null, it requests it later
successfully. I don't know why this is so, I'm using Java 6 in server
mode with source = 5. Is it a compiler optimisation?
Are you sure you aren't hit by a recursive call to the PolicyProvider?
Reading a property is checked against the policy isn't it?
Gr. Sim
