The current test harness will try to create databases in subdirectories, with the name of the test. Also, the derby_tests.policy file gets copied to the correct test dir and accessed through there. I envisaged that without useprocess=false, creation of databases would have failed. Even if we'd have directories created by hand beforehand, we'd still have a problem because the derby_tests.policy file normally gets copied to a proper place in the test directories and as this doesn't happen on the remote host, we'd have incorrect file permissions...
Also, it seemed to me that as the actual network interaction was bigger, it made sense to speed up the process by having as much as possible reuse of databases; but that was more of a side-issue.
I'll try to think of a way to explain that succinctly in the section 4.14 if you think all this makes sense.
Myrna
On 1/29/06, Daniel John Debrunner <[EMAIL PROTECTED]> wrote:
Sorry that the changes to run useProcess under the security manager
broke the remote testing, I was not aware of the implications. Looking
at section 4.14 or the testing README, I couldn't understand why when
running in this mode useProcess=false is choosen. Why not continue to
run the clients as they did before?
Dan.
