Vemund Ostgaard wrote:
Can you confirm that if you add the following line to
derby_tests.policy, the problem goes away? The line should be added to
all three of the derby.jar, derbynet.jar, and derbytools.jar sections,
which is easiest to do if you just search for "DERBY-622" and then add
this line right after it:
permission java.lang.RuntimePermission "getProtectionDomain";
Yes, this seems to solve the problem in my environment.
Excellent. I haven't had any better ideas about how to fix this, so
I suggest the following:
- Assign the bug to yourself
- Work up an explicit patch proposal incorporating this change
- Attach it to the bug and let's give the community a chance to review it.
- Unless the reviewers are able to come up with a better solution,
we'll go with this one.
How does that sound?
thanks,
bryan
