[EMAIL PROTECTED] wrote: > "David W. Van Couvering" <[EMAIL PROTECTED]> writes: > > >>I got this too, I was pretty sure it was that junit is trying to read >>system properties, the first one being "user.dir". I think it also then >>tries to read Junit properties out of the user's home directory? >> >>I spent some time trying to modify the test harness to indicate where >>the third party jars were to try and fix this, but finally gave up and >>turned off security manager for my JUnit test (I was going to log a >>separate bug for this, I just didn't think it was worth spending all my >>time trying to fix this right now). > > > I tried that too, but I could not get it to work. I tried setting > "noSecurityManager" to true, in all places that I could think of (prop > file, commnad line, and in the code itself), but I still got the same > errors. > > After reading section 4.13 in the java/testing/readme.htm file I was > unsure about whether this property was used in embedded mode.
Yes it is. In section 4.13 by client JVM I meant the JVM where the test was running and calling the JDBC client directly, either embededded, derby network client or JCC. I will try and make that more clear, the formatting seems to have got confused as well. I haven't looked though to see how Junit tests are run by the harness and how they interact with the security manager. Dan.
