[Bug libgcj/46774] [gcj] Calling Policy.setPolicy with a new Policy object has no effect on the DefaultSecurityManager

[gandalf at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46774

--- Comment #3 from gandalf at gcc dot gnu.org <gandalf at gcc dot gnu.org> 2010-12-20 18:19:57 UTC ---
Author: gandalf
Date: Mon Dec 20 18:19:52 2010
New Revision: 168092

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=168092
Log:
PR libgcj/46774: Create dynamic ProtectionDomain instances which check the
system policy.

2010-12-13  Andrew John Hughes  <ahughes@redhat.com>

        PR libgcj/46774
        * libjava/java/security/VMAccessController.java:
        (DEFAULT_CONTEXT): Create ProtectionDomain with
        four argument constructor (arguments are the same
        as those implied by the two argument constructor).
        (getContext()): Create ProtectionDomain instances
        with four argument constructor using a null Principal
        array (as before) but including the classloader, which
        was always null before.


Modified:
    branches/gcc-4_5-branch/libjava/ChangeLog
   
branches/gcc-4_5-branch/libjava/classpath/lib/java/security/VMAccessController.class
    branches/gcc-4_5-branch/libjava/java/security/VMAccessController.java