Part 1, content in the folder
Cactus.jar: The Main Jar, Contains The Framework Classes. You can Find this Jar in [Cactus Root] / lib. CACTUS-ANT.JAR: A Jar Which Contains Some Custom Ant Tasks to Help Integrate Easily with Ant. this is online needed if you wish to use Ant for automating the execution of Cactus tests you also find this jar in [cactus root] / lib httpclient.jar:... Cactus is relying on the Jakarta Commons HttpClient framework for Cookie handling junit.jar: Cactus extends JUnit and thus needs the JUnit jar aspectjrt.jar:. Cactus uses AspectJ for performing several tasks (logging entries and exit of methods, checking configuration, etc) commons-logging.jar:. Cactus uses the Jakarta Commons Logging facade framework to provide seamless Cactus logging using any existing logging framework (Log4j, LogKit, JDK 1.4 logging, etc) It is also needed for Commons HttpClient servletapi.jar:... Required for compiling the Servlet sample Ideally we should be bundling the J2EE jar (which is Required for Compiling The EJB SAM . Ple) However the Sun license does not allow us to redistribute it so you'll need to download it by yourself (see the Sample howto page httpunit.jar:.. Cactus uses the HttpUnit framework to perform complex assertions of returned responses Cactus also Bundles a Default Web Response Object But The Httpunit ONE Should Be Precept For Complex Assertions. Nekohtml.jar: Required by httpunit.
Second, CACTUS uses Cactus Plugin for Eclipse Not Available, but can use the JUnit plugin inherited the JUnit framework to continue testing. If a chainedRuntimeException error occurs, it should be CACTUS.Properties not in Calsspath, which can be set via Windows-> Perferences.
