Kathey Marsden wrote:
David W. Van Couvering wrote:
When I was doing the classloader work, I had to grant permission to
the Derby codebase to be able to do classloader-related work
(createClassloader, accessClassInPackage.sun.reflect, getClassloader,
getProtectionDomain).
How do I know whether granting a certain permission is shadowing a
"bug" versus the right thing to do?
I was a little confused by this question, but I think in general, if
existing tests started needing new permissions, that would be a bug.
Well, that doesn't seem completely fair. If I am adding new, valuable
functionality that requires new permissions, I think it's reasonable to
add them to the list. How would I get my classloader work in, for instance?
We don't ship a default policy file but have samples in the
documentation. It would be good to have security manager on and
sample policy files used with the framework scripts, particularly for
network server.
Yes, I think that would be great... Not yet itching enough to scratch
this, though...
David
Thanks
Kathey
begin:vcard
fn:David W Van Couvering
n:Van Couvering;David W
org:Sun Microsystems, Inc.;Database Technology Group
email;internet:[EMAIL PROTECTED]
title:Senior Staff Software Engineer
tel;work:510-550-6819
tel;cell:510-684-7281
x-mozilla-html:TRUE
version:2.1
end:vcard
