----- Original Message -----
From: "Dan Cancro" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, August 06, 2001 8:35 PM
Subject: how many cactus.properties files are there?
> I'm just getting started with using this, but I'm a little confused about
> the cactus.properties file.
>
> Is there A) one of these per server, or B) one per application?
>
The answer is B). Usually what happens is that you have directory structure
(src/, doc/, lib/, ...) per application that you develop. And usually you
want to run the cactus tests as part of your suite of unit tests to ensure
that the application under development is running fine.
>
>
> If "A", then
>
>
> "Each project using Cactus need to have such a file" (from the provided
> cactus.properties file)
yes
>
> and
>
> "...
> For example, if you have the following configuration :
>
> Your webapp is called "mywebapp"
> The URLs specified in your cactus.properties are
> "http://localhost:8080/mywebapp/ServletRedirector"; for the
> cactus.servletRedirectorURL property and
> "http://localhost:8080/mywebapp/JspRedirector"; for the
> cactus.jspRedirectorURL property
> ..."
>
> (from the configuration instructions) do not make sense to me.
>
why ? mywebapp is specific to a given project.
>
>
> If "B", then "put in the CLASSPATH" (from the provided cactus.properties
> file) doesn't make sense to me since there's one CLASSPATH per server, and
> the server uses the first file by a name ("cactus.properties") that it
finds
> in the CLASSPATH, so it would ignore all but the first one of these it
> finds.
cactus.properties is only used on the client side, (see
http://jakarta.apache.org/commons/cactus to understand how it works, there
is a nice animated gif and click on it to undestand even better how it
works)
Note: Try to never put anything on the server system classpath, but rather
use the WEB-INF/lib and WEB-INF/classes directory which are per-application
classpaths.
>
> Thanks,
> Dan
You're welcome. Tell me if you still need more information.
-Vincent
