Well, the tutorial classes are not in a separate package. They are in the default package, so there is no package name to specify. Does Tomcat or Cactus have a problem with the default package?
Jim Babka Senior S/W Engineer and Team Lead, Context Aware Dynamic Selection (512)286-5195, tie line 363-5195 ba...@us.ibm.com From: <chris.persiche...@thomsonreuters.com> To: <cactus-user@jakarta.apache.org> Date: 11/10/2010 03:23 PM Subject: RE: Cactus tutorial needs updating I had the same problem. You need to include the package name of the class in the url. http://localhost:8080/test/ServletTestRunner?suite=com.company.TestSampleServlet --Chris -----Original Message----- From: Jim Babka [mailto:ba...@us.ibm.com] Sent: Wednesday, November 10, 2010 2:14 PM To: Cactus Users List Subject: RE: Cactus tutorial needs updating OK, so I got Tomcat 5.5.31, copied all the Cactus JARs to Tomcat's common/lib directory, then followed the tutorial instructions. I set up a web app as directed, with the following directory structure under webapps: ├──test │ └──WEB_INF │ └──classes The classes directory has: SampleServlet.class TestSampleServlet.class However, when I try to browse to http://localhost:8080/test/ServletTestRunner?suite=TestSampleServlet, I get this error. Is there something else I need to do in order to enable Tomcat to find the class? Should the class be in a different place than the test/WEB-INF/classes directory? HTTP Status 500 - type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception javax.servlet.ServletException: Failed to load test suite [TestSampleServlet], Reason is [Class not found "TestSampleServlet"] org.apache.cactus.server.runner.ServletTestRunner.run(ServletTestRunner.java:303) org.apache.cactus.server.runner.ServletTestRunner.doGet_aroundBody0(ServletTestRunner.java:187) org.apache.cactus.server.runner.ServletTestRunner.doGet_aroundBody1$advice(ServletTestRunner.java:225) org.apache.cactus.server.runner.ServletTestRunner.doGet(ServletTestRunner.java:1) javax.servlet.http.HttpServlet.service(HttpServlet.java:689) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) Jim Babka Senior S/W Engineer and Team Lead, Context Aware Dynamic Selection (512)286-5195, tie line 363-5195 ba...@us.ibm.com From: "Bennett, Jeffrey" <jjbenn...@onecommunications.com> To: "Cactus Users List" <cactus-user@jakarta.apache.org> Date: 11/10/2010 08:18 AM Subject: RE: Cactus tutorial needs updating Jim- Can't speak officially, but I use Cactus 1.8.1 with Tomcat 5.5.30 (which does still have the common/lib structure). I don't think you need any of those jars in Tomcat itself, although you probably need to place them in the cactified-war. In the setup I use, I only see aspectjrt (but we do some AspectJ stuff) and commons-logging (necessary, as we want Tomcat to use Log4J for its own logs) from the list you provided. However, commons-discovery, commons-httpclient, cargo, cactus, jasper and junit are in most of the cactified wars we operate on. Good Luck- -Jeff P.S. Anyone successful at taking Cactus to Tomcat 7 yet? Pretty sure it's impossible due to cactus's use of Cargo 1.0B2 (short of recompiling Cactus), but just curious. -----Original Message----- From: Jim Babka [mailto:ba...@us.ibm.com] Sent: Tuesday, November 09, 2010 7:00 PM To: cactus-user@jakarta.apache.org Subject: Cactus tutorial needs updating The Cactus tutorial needs to be updated. It talks about Tomcat 4 (which you can't even get anymore). The real issue, though, is it says this: ---------------------------- Copy the following jars to [tomcat-root]/common/lib: cactus.jar commons-httpclient.jar commons-logging.jar junit.jar aspectjrt.jar ---------------------------- First, there is no common/lib directory in Tomcat 6, and second, those JARs do not exist in the Cactus 1.8.1 distribution. Here are the JARs that are there now: aspectjrt-1.5.3.jar cactus.core.framework.uberjar.javaEE.14-1.8.1.jar cactus.integration.ant-1.8.1.jar cactus.integration.shared.api-1.8.1.jar cargo-ant-1.0-beta-2.jar cargo-core-container-jonas-1.0-beta-2.jar cargo-core-uberjar-1.0-beta-2.jar commons-discovery-0.4.jar commons-httpclient-3.1.jar commons-logging-1.1.jar geronimo-ejb_2.1_spec-1.1.jar geronimo-j2ee-management_1.0_spec-1.1.jar httpunit-1.6.jar jasper-compiler-5.5.9.jar jasper-runtime-5.5.9.jar junit-3.8.2.jar mx4j-3.0.2.jar mx4j-remote-3.0.2.jar nekohtml-1.9.6.jar org.mortbay.jetty-5.1.9.jar servlet-api-2.4.jar I can guess the right JARs to use for everything but "cactus.jar". Can someone please explain what JARs are needed for Cactus now, and where they should go? Jim Babka Senior S/W Engineer and Team Lead, Context Aware Dynamic Selection (512)286-5195, tie line 363-5195 babka at us.ibm.com --------------------------------------------------------------------- To unsubscribe, e-mail: cactus-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: cactus-user-h...@jakarta.apache.org This email was sent to you by Thomson Reuters, the global news and information company. Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Thomson Reuters. --------------------------------------------------------------------- To unsubscribe, e-mail: cactus-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: cactus-user-h...@jakarta.apache.org