vmassol 01/05/04 01:17:13
Modified: cactus/docs/framework/xdocs installation.xml
Log:
added more explanations about CLASSPATHs and fixed the name of the cactus jars
Revision Changes Path
1.5 +35 -4 jakarta-commons/cactus/docs/framework/xdocs/installation.xml
Index: installation.xml
===================================================================
RCS file: /home/cvs/jakarta-commons/cactus/docs/framework/xdocs/installation.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- installation.xml 2001/05/04 08:01:06 1.4
+++ installation.xml 2001/05/04 08:17:10 1.5
@@ -98,7 +98,7 @@
</p>
<ol>
<li>
- Put the <code>cactus-<servlet API>-<version>.jar</code>
+ Put the <code>commons-cactus.jar</code>
file in the <code>WEB-INF/lib</code> directory of the webapp that
you are testing (If your servlet engine does not support web
applications, just make sure that it is in the
@@ -238,9 +238,40 @@
</s2>
- <s2 title="Step 3 : Client-side installation with JUnit">
+ <s2 title="Step 3 : The server side CLASSPATH">
<p>
+ Here is the list of files that need to be in your server CLASSPATH :
+ </p>
+ <ul>
+ <li>
+ the classes under test. These would normally be put under your
+ webapp <code>WEB-INF/classes</code> directory,
+ </li>
+ <li>
+ the test classes. These would normally be put under your webapp
+ <code>WEB-INF/classes</code> directory,
+ </li>
+ <li>
+ the cactus jar (<code>commons-cactus.jar</code>). It should
+ normally be put under your webapp <code>WEB-INF/lib</code>
+ directory. However if you use Cactus to test several webapps you
+ might want to factor it out by putting it in the server's global
+ CLASSPATH,
+ </li>
+ <li>
+ the JUnit jar (<code>junit.jar</code>). It should
+ normally be put under your webapp <code>WEB-INF/lib</code>
+ directory. However if you use it for several other webapps you
+ might want to factor it out by putting it in the server's global
+ CLASSPATH,
+ </li>
+ </ul>
+ </s2>
+
+ <s2 title="Step 4 : Client-side installation with JUnit">
+
+ <p>
A Cactus suite of tests is started using JUnit test runners (see
the <link href="using.html">using</link> section). You need to
put the following files in your client-side CLASSPATH :
@@ -250,7 +281,7 @@
The JUnit jar file,
</li>
<li>
- The Cactus jar : <code>cactus-<servlet
API>-<version>.jar</code>,
+ The Cactus jar : <code>commons-cactus.jar</code>,
</li>
<li>
The Cactus configuration file <code>cactus.properties</code> (see
@@ -268,7 +299,7 @@
</s2>
- <s2 title="Step 4 : Configure Cactus">
+ <s2 title="Step 5 : Configure Cactus">
<p>
You need to <link href="configuration.html">configure</link> Cactus
