Yes, this was my experience also. You can't have multiple
configurations in a VM instance, because everything is dependent on
system properties (both Derby itself as well as the test harness
infrastructure). I don't *think* using classloaders will help because
system properties, as I understand it, are VM-wide and span
classloaders. But I haven't explicitly tested that.
David
Dag H. Wanvik wrote:
Hi,
"KM" == Kathey Marsden <[EMAIL PROTECTED]> wrote:
KM> Thanks for working on the test.
I am encountering an issue making a test for the setting of
derby.stream.error.* properties. It seems the testing harness gives me
no easy way to test combinations of system properites; once the driver
is loaded, I am stuck with a particular setting of system-wide
properties, e.g.
Properties p = System.getProperties();
p.put("derby.stream.error.method",
"org.apache.derbyTesting.functionTests.tests.lang.TestErrorStreamTarget.getStream");
:
Class.forName(driver).newInstance();
allows the test to boot a Derby redirecting the error log, but if I
want to test several possibilities, it would seem I need to start
another VM or use explicit class loaders. I could use brute force and
make a test per combination of properties settings I want to test, but
that seems ugly.. Any ideas?
Thanks,
Dag
KM> I'll pick up Derby-213.
KM> Please do let me know if you are looking for interesting network
KM> server tasks when you are done with your test.
