ndlesiecki 01/10/03 07:49:05
Modified: docs/framework/xdocs getting_started.xml
Log:
added a note explaining the problem with putting the cactus jar in a shared location
Revision Changes Path
1.6 +12 -0 jakarta-cactus/docs/framework/xdocs/getting_started.xml
Index: getting_started.xml
===================================================================
RCS file: /home/cvs/jakarta-cactus/docs/framework/xdocs/getting_started.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- getting_started.xml 2001/09/25 14:11:13 1.5
+++ getting_started.xml 2001/10/03 14:49:05 1.6
@@ -235,6 +235,7 @@
or as expanded war. It should have the following structure, which
will ensure that the classpath is correct :
</p>
+
<ul>
<li>
<strong><code>WEB-INF/lib/cactus.jar</code></strong> : the
@@ -260,6 +261,17 @@
on the server side.
</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.
+ </note>
<note>
In theory you would also need to put the
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
