I check "all projects" for the class path of the client, and I still get the
Failed to invoke suite():java.lang.NoClassDefFoundError So I still stuck running cactus from the command line against Weblogic, instead inside VAJ. -----Original Message----- From: Idler, Todd [mailto:[EMAIL PROTECTED]] Sent: Monday, October 15, 2001 8:46 AM To: '[EMAIL PROTECTED]' Subject: RE: VAJ 3.5.3 Class loader problem Hi David and Aklil, I was having a similar problem and finally remembered what I did to correct it. I don't currently have VisualAge installed and I'm going from memory on this one. You might also look in the archived postings because I believe that there was another thread on this topic. The problem may be that the Servlet API project can't be found by the client-side of the cactus test. The Servlet project is automatically included in the classpath for WTE, but you need to explicitly add it to the classpath of the project that contains the test class. You can either add the Servlet project globally for use in all projects or you can add it specifically to the classpath for the project that you are testing. As an explanation for those who don't use VisualAge, you can add VisualAge projects to the classpath in addition to directories. I think that the offending class was ServletException. One of my test methods was declared as throwing this exception. Since the exception class couldn't be found, the suite wasn't successfully created. Even though testXxxx() is executed on the server side, the exceptions it throws must be locatable on the client side. Todd
