cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robin Green" <>
Subject [PATCH] Doc patches - new requirements and some cleanups
Date Sat, 06 May 2000 20:54:46 GMT
Here are patches for installing.xml and faq.xml. This should clear up the 
confusions about the NullPointerExceptions some people have been having with 
the latest 1.7.3 release. If I have misunderstood it, go ahead, flame me. ;)

--- installing.xml~     Sat May  6 06:09:22 2000
+++ installing.xml      Sat May  6 19:21:02 2000
@@ -219,7 +219,7 @@

-     from this version of Cocoon the <code>cocoon.jar</code>
+     The <code>cocoon.jar</code>
      package should be added to the servlet engine classpath as any other
      required package (as shown above).
@@ -253,7 +253,25 @@

      Make sure you replaced the path to the file with the
-     actual location of that file on your system.
+     location of that file on your system,
+     <strong>relative to the context root</strong>. Even if you start the
+     filename with a / it will still be relative to the context root.
+    </p>
+    <note>
+      Because Cocoon now (since version 1.7.3) uses getResource () in the
+      Servlet API to read, and has different instances 
+      each servlet context, you need to put a copy of in 
+      of your servlet contexts that use Cocoon. (It is recommended to put 
+      in the context's WEB-INF directory,
+      or a password-protected directory, to prevent anyone from being able
+      to read it over the web.)
+      However, you <strong>cannot</strong> use symbolic
+      links on Unix to point to a file outside of the current context, 
+      Tomcat does not allow it for security reasons.
+    </note>
+    <p>
      Note that you should not need to change anything from the template
      properties file found in the distribution, but you must edit it for
      more complex operation. Please refer directly to the file that 
@@ -270,19 +288,24 @@

-    Everything should be configured fine. Restart both Apache and Tomcat
+     If you have upgraded Cocoon from an older version and Cocoon won't
+     initialize, either ensure that
+     you are using the latest - or, if you are have some
+     non-standard properties in which you need to keep,
+     refer to the latest to find out what changes need to
+     be made, if any.
+   </p>
+   <p>
+    Everything should now be configured fine. Restart both Apache and 
     and try accessing the samples contained in the distribution to see
     Cocoon in action or the <code>/Cocoon.xml</code> page for Cocoon 

-     Tomcat 3.0 has a bug that prevents Cocoon operation. In order to make
-     Cocoon work under Tomcat you need to download a newer version or, if
-     none is yet avaiable, build it from the latest source code found in 
-     <code>jakarta-tomcat</code> CVS module under 
-     We apologize for this, but it's not something we can control or work
-     around.
+     Tomcat 3.0 has a bug that prevents Cocoon operation. Please download
+     a later version.

--- faq.xml~    Sat May  6 06:09:22 2000
+++ faq.xml     Sat May  6 20:31:28 2000
@@ -5,6 +5,19 @@
<faqs title="Frequently Asked Questions">

+ <question>I get the message "Publishing engine could not be initialized"
+  and a NullPointerException</question>
+ <answer>
+  <p>
+    This is probably due to the new system introduced in
+    version 1.7.3. You now have to put a file in every
+    servlet context that uses Cocoon
+    (see <link href="install.html">Installation</link> for more details)
+  </p>
+ </answer>
  <question>I get the exception <em>java.lang.NoClassDefFoundError: 

Get Your Private, Free E-mail from MSN Hotmail at

View raw message