Myrna van Lunteren wrote:
Now I looked at the patch for DERBY-668, and I don't see that it addresses DERBY-622 at all...
I think my comment was overly alarming; sorry about that! What I meant to say was that I have also been working on changing the way that sysinfo behaves when it is run with a SecurityManager. Specifically, I am working on the part of sysinfo which analyzes the classpath, and there are security manager issues involving: - is sysinfo allowed to read the java.class.path property - is sysinfo allowed to call getProtectionDomain for a class So I've added some new PrivilegedAction code, and I've added some new code which catches SecurityException and prints messages trying to help the user understand the security restrictions they're hitting, and so forth. I agree with you that the issues being addressed are independent, and our two patches don't have to interact at all. I just wanted to alert you to the fact that we both seemed to be working in the general area of "sysinfo and SecurityManagers". thanks, bryan P.S. Updated patch for DERBY-668 should arrive this weekend, with changes incorporating Andrew's feedback (Thanks Andrew!)
