----- Original Message -----
From: "Kelvin Tan" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; "Vincent Massol"
<[EMAIL PROTECTED]>
Sent: Thursday, May 03, 2001 9:50 AM
Subject: Re: [cactus] Help with Cactus
> Vincent,
>
> Thanks for your prompt reply! Actually I had noticed that para that you
> highlighted.
>
> "The Server part is usually packaged as a war file that you put in your
> Servlet engine webapps directory.
>
> On the client side you simply need to put the above-mentionned classes in
> your CLASSPATH (don't forget to put the cactus.properties file in your
> CLASSPATH). You start running the tests by starting a JUnit runner (either
> the gui one or the text one). "
>
> Unfortunately, the part is not clear (to me), the Server part
> the classes you want to test,
> your Cactus test classes,
> the Cactus jar,
> the JUnit jar,
>
> needs to be WARed. Is there a necessary directory structure, what xml
> deployment files need to be included in this WAR?
>
> Is it sufficient to just place the test classes in a directory mentioned
in
> the classpath or is it necessary to specify the classes individually?
>
> Thanks!
>
Ok, Here is an example webapp :
<mywebapp>/WEB-INF
|_ classes
|_ your classes under test (under the correct directory hierarchy)
|_ your test classes (under the correct directory hierarchy)
|_ lib
|_ commons-cactus.jar
|_ junit.jar
Alternatively, if you use Cactus for testing several webapps, you might want
to remove the jars from <mywebapp>/WEB-INF/lib and put them in the general
classpath of your application server so that they will available to any
webapp.
Note: Check the sample application that is delivered as part of Cactus. It
constructs a war file.
Hope it helps.
Vincent.
