On Wed, Oct 15, 2008 at 8:16 PM, Peter Jones <[EMAIL PROTECTED]> wrote:
> Interesting exception trace.  Do you know the actual class of the
> java.security.Policy in effect in this JVM?

Yes, I do;
This is all to set up my automated tests (which I think is River's
weakest point at the moment), so it is a simple inner class. It looks
like this;

// test initialization
        if( System.getSecurityManager() == null )
        {
            Policy allPolicy = new TestPolicyAllPermissions();
            Policy.setPolicy( allPolicy );
            System.setSecurityManager( new SecurityManager() );
        }

// test policy
    private static class TestPolicyAllPermissions extends Policy
    {
        private Permissions permissions;

        private TestPolicyAllPermissions()
        {
            permissions = new Permissions();
            permissions.add( new AllPermission() );
        }

        public PermissionCollection getPermissions( CodeSource codeSource )
        {
            return permissions;
        }

        public void refresh()
        {
        }
    }


Thanks for the elaborate thought on the subject. I have no further
information on the subject, as I have not worked on this since I
posted this last time.

One piece that might be of importance is that the Security Policy
provided to the NonActivatableServiceDescriptor constructor (system
under test), is a standard policy file, but created on the fly. At the
moment it just sets the default grant to AllPermissions.


Cheers
Niclas

Reply via email to