vmassol 2002/07/22 13:59:59
Modified: documentation/docs/xdocs changes.xml features.xml
howto_classpath.xml todo.xml
Log:
updated for new Jakarta Commons jar
Revision Changes Path
1.33 +5 -5 jakarta-cactus/documentation/docs/xdocs/changes.xml
Index: changes.xml
===================================================================
RCS file: /home/cvs/jakarta-cactus/documentation/docs/xdocs/changes.xml,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -r1.32 -r1.33
--- changes.xml 22 Jul 2002 12:26:04 -0000 1.32
+++ changes.xml 22 Jul 2002 20:59:58 -0000 1.33
@@ -52,11 +52,11 @@
Cactus now requires the Commons Logging library
(<code>commons-logging.jar</code>). It is needed as Commons HttpClient
is now using Commons Logging for logging and Cactus depends on
- HttpClient. As a side-effect, Cactus is also now using Commons
- HttpClient for all its internal logs. This lets us use any underlying
- logging implementation : Log4j, LogKit, JDK 1.4 Logging, No Logging
- or SimpleLog (provided with Commons Logging - logs to the console).
- Check the <link href="howto_config.html">Config Howto</link> for how
+ HttpClient. Cactus is also now using Commons HttpClient for all its
+ internal logs. This lets us use any underlying logging implementation :
+ Log4j, LogKit, JDK 1.4 Logging, No Logging or SimpleLog (provided with
+ Commons Logging - logs to the console). Check the
+ <link href="howto_config.html">Config Howto</link> for how
to configure logging in Cactus.
</action>
<action dev="VMA" type="remove">
1.5 +2 -5 jakarta-cactus/documentation/docs/xdocs/features.xml
Index: features.xml
===================================================================
RCS file: /home/cvs/jakarta-cactus/documentation/docs/xdocs/features.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- features.xml 20 Jul 2002 12:48:13 -0000 1.4
+++ features.xml 22 Jul 2002 20:59:59 -0000 1.5
@@ -207,7 +207,8 @@
Howto</link> tutorial for details.
</li>
<li>
- Internal Log4j logging to help debug problems.
+ Internal logging using Jakarta Commons Logging facade framework
+ to help debug problems.
</li>
<li>
HttpUnit integration. See the
@@ -219,10 +220,6 @@
<li>
Support for BASIC authentication. You can test code that uses the
Servlet security API.
- </li>
- <li>
- Ability to define where to locate the Cactus configuration file
- (<code>cactus.properties</code>).
</li>
<li>
Ability to specify, per test case, what redirector to use. Useful,
1.3 +40 -29 jakarta-cactus/documentation/docs/xdocs/howto_classpath.xml
Index: howto_classpath.xml
===================================================================
RCS file: /home/cvs/jakarta-cactus/documentation/docs/xdocs/howto_classpath.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- howto_classpath.xml 13 May 2002 21:35:42 -0000 1.2
+++ howto_classpath.xml 22 Jul 2002 20:59:59 -0000 1.3
@@ -81,9 +81,18 @@
Cactus Cookie handling.
</li>
<li>
- <strong><code>log4j.jar</code> (optional)</strong> : only needed
- when you want Cactus to output debugging information on the client
- side.
+ <strong><code>commons-logging.jar</code></strong> : 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.
+ </li>
+ <li>
+ <strong><code>logging framework jar</code>(optional)</strong> : The
+ logging framework to use (Log4j jar, LogKit jar, etc). It is
+ optional as it is only needed for internal Cactus logging and in
+ addition, the Commons Logging framework provides a simple logger
+ that logs on the console.
</li>
<li>
<strong><code>httpunit.jar</code></strong>, <strong>
@@ -109,19 +118,17 @@
</note>
<p>
- In addition to the above mentionned jars and classes, you will also
- need to put the <strong><code>cactus.properties</code></strong>
- configuration file in your classpath (because it is a java properties
- file). Details are described in the
+ In addition to the above mentionned jars and classes, you may have
+ to put the <strong><code>cactus.properties</code></strong>
+ configuration file in your classpath (Only if you are using it to
+ configure Cactus of course). Details are described in the
<link href="howto_config.html">Config Howto</link> tutorial).
</p>
<note>
- In theory you would also need to put the
- <code>log_client.properties</code> properties file in your classpath.
- However a default one is provided in <code>cactus.jar</code>
- (and thus is on the classpath as <code>cactus.jar</code> is
- itself in the classpath !).
+ If you are using Log4J as the logging framework, you will also
+ need to put a <code>log4j.properties</code> Log4j configuration
+ file in your client side classpath.
</note>
</s2>
@@ -154,30 +161,34 @@
</strong> : will be called by your test classes.
</li>
<li>
- <strong><code>WEB-INF/lib/log4j.jar</code> (optional)</strong> :
- only needed when you want Cactus to output debugging information
- on the server side.
+ <strong><code>WEB-INF/lib/commons-logging.jar</code></strong> :
+ 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.
+ </li>
+ <li>
+ <strong><code>WEB-INF/lib/logging framework jar</code>
+ (optional)</strong> : The logging framework to use (Log4j jar,
+ LogKit jar, etc). It is optional as it is only needed for internal
+ Cactus logging and in addition, the Commons Logging framework
+ provides a simple logger that logs on the console.
</li>
</ul>
<note>
- If you have several webapps that use cactus you may be tempted to
- place the <code>cactus.jar</code> in your container's shared library
- folder. However, this approach will not work in many cases because
- code in a shared location (cactus) cannot access code in a
- specific webapp (your test cases). This restriction makes sense
- since you would not want <code>com.foo.EvilClass</code>
- in webapp A to conflict with <code>com.foo.EvilClass</code> in webapp
- B.
+ If you have several webapps that use cactus you can put all Cactus
+ jars in a place loaded by your container System classloader (provided
+ your container correctly sets the Context classloader). The location
+ is container-dependent; for example for Tomcat 4.x, you can put the
+ jars in <code>TOMCAT_HOME/common/lib</code>.
</note>
<note>
- In theory you would also need to put the
- <code>log_server.properties</code> configuration file in your
- classpath. However a default one is provided in
- <code>cactus.jar</code>
- (and thus is on the classpath as <code>cactus.jar</code> is
- itself in the classpath !).
+ If you are using Log4J as the logging framework, you will also
+ need to put a <code>log4j.properties</code> Log4j configuration
+ file in your server side classpath (usually in
+ <code>WEB-INF/classes</code>).
</note>
</s2>
1.14 +0 -3 jakarta-cactus/documentation/docs/xdocs/todo.xml
Index: todo.xml
===================================================================
RCS file: /home/cvs/jakarta-cactus/documentation/docs/xdocs/todo.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- todo.xml 22 Jul 2002 12:26:04 -0000 1.13
+++ todo.xml 22 Jul 2002 20:59:59 -0000 1.14
@@ -39,9 +39,6 @@
<action assigned-to="Vincent Massol">
Explain how to configure logging using Commons Logging.
</action>
- <action assigned-to="Vincent Massol">
- Modify documentation for new jar : Commons Logging
- </action>
</category>
</version>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
