jakarta-cactus-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rod Macpherson" <rmacpher...@abovehealth.com>
Subject RE: Strange Classpath Problem
Date Thu, 22 Sep 2005 16:01:01 GMT
Placing System.out.print("got here") inside myTest generates these

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

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. 


-----Original Message-----
From: Rod Macpherson [mailto:rmacpherson@abovehealth.com] 
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: cactus-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-user-help@jakarta.apache.org

View raw message