db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dyre.Tjeldv...@Sun.COM
Subject Re: [jira] Updated: (DERBY-85) NPE when creating a trigger on a table and default schema doesn't exist.
Date Wed, 30 Nov 2005 17:30:02 GMT
Daniel John Debrunner <djd@debrunners.com> writes:

> Dyre Tjeldvoll (JIRA) wrote:
>>      [ http://issues.apache.org/jira/browse/DERBY-85?page=all ]
>> Dyre Tjeldvoll updated DERBY-85:
>> --------------------------------
>>     Attachment: derby-85.diff
>>                 derby-85.stat
>>                 derbyall_report.txt
>> New patch with Junit test case.
>> Note that I had to modify the SecurityManager policy to grant more privileges to
 derbyTesting.jar and junit.jar
>> Anyone interested SecurityManager issues may want to review those changes carefully.
> Why do you need to grant permissions to read all files for the
> derbyTesting and junit jars?

I'm sorry, but I think you need to ask the junit developers about
that.  I don't know exactly which files junit wants to access, but the
last error I saw (before granting read access to all files), was an
access exception because junit was trying to read my home directory to
figure out if there was a junit.properties file there, I think. I
don't really understand why derbyTesting.jar needs the same access,
but I assume it is because the Bugs class (which inherits TestCase)
ends up there...

I guess it is possible to find the minimal set of file and property
rights needed by junit, either by reading the junit source, or through
trial and error, but given the comment in the policy file about not
trying to make the test harness secure, I didn't think it was worth

> Why not just all files under the user.dir?
> Dan.


However, experience shows that for many people and many applications a
dose of paranoia is reasonable - Bjarne Stroustrup

View raw message