-----Original Message-----
From: Rod Macpherson [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 22, 2005 9:01 AM
To: Cactus Users List
Subject: RE: Strange Classpath Problem
Placing System.out.print("got here") inside myTest generates these
results:
1) "got here" appears in application server output window in form A) and
all tests succeed
2) "got here" appears in ant output window in form B) and all tests are
Errors
Cactus is trying to run the tests on the client side in form B). That
explains the ClassNotFoundException reported in cactus.xml. Also
explains why setting a break point in the remote server works in form A)
and not in form B).
Any insights appreciated.
TIA
-----Original Message-----
From: Rod Macpherson [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 22, 2005 8:31 AM
To: Cactus Users List
Subject: Strange Classpath Problem
This works without incident exercising all methods:
A) suite.addTestSuite(MyTestSuite.class);
This generates a ClassNotFoundException inside the testConnect method
when it runs the test:
B) suite.addTest(new MyTestSuite("myTest"));
The class that cannot be found is in a static block so it's incidentally
by referencing a class with some statics. Why would it be found in A)
and not B)?
There are clues that seem to suggest it might be trying to execute the
test on the client in form B). That's very strange.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
