cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From stef...@locus.apache.org
Subject cvs commit: xml-cocoon/xdocs faq.xml installing.xml
Date Sun, 07 May 2000 16:00:38 GMT
stefano     00/05/07 09:00:38

  Modified:    xdocs    faq.xml installing.xml
  Log:
  some updates and fixes
  
  Revision  Changes    Path
  1.14      +26 -0     xml-cocoon/xdocs/faq.xml
  
  Index: faq.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon/xdocs/faq.xml,v
  retrieving revision 1.13
  retrieving revision 1.14
  diff -u -r1.13 -r1.14
  --- faq.xml	2000/05/05 14:28:40	1.13
  +++ faq.xml	2000/05/07 16:00:37	1.14
  @@ -5,6 +5,24 @@
   <faqs title="Frequently Asked Questions">
   
   <faq>
  + <question>I get the message "Publishing engine could not be initialized"
  +  and a NullPointerException when upgrading from an older version, what's wrong?</question>
  + <answer>
  +  <p>
  +    This is probably due to incompatibilities with the <code>cocoon.properties</code>
  +    configuration file between the old version and the new one. Since Cocoon
  +    is a very modular framework and it's architecture is not yet stable, we
  +    always suggest to replace your old configuration file with the new one
  +    shipped with the new release.
  +  </p>
  +  <p>
  +    We are working to make sure that this won't be required anymore in the
  +    Cocoon2 generation, for now, we apologize for the inconvenience.
  +  </p>
  + </answer>
  +</faq>
  +
  +<faq>
    <question>I get the exception <em>java.lang.NoClassDefFoundError: sun/tools/javac/Main</em></question>
    <answer>
     <p>
  @@ -128,6 +146,14 @@
     to your <code>jserv.conf</code> file to set the response timeout to 60 seconds,

     or increase that number if your machine is very slow and the compilers takes
     more than that time to compile the XSP page the first time you hit it.</p>
  + </answer>
  +</faq>
  +
  +<faq>
  + <question>is there a way to fake the requesting UserAgent from my browser? that
would ease debugging.</question>
  + <answer>
  +  <p>Yes, just append <code>?user-agent="xxx"</code> to your requested
URI and Cocoon will neglect the userAgent
  +  description that your browser is sending and use the one you imposed.</p>
    </answer>
   </faq>
   
  
  
  
  1.12      +34 -11    xml-cocoon/xdocs/installing.xml
  
  Index: installing.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon/xdocs/installing.xml,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- installing.xml	2000/04/27 17:55:16	1.11
  +++ installing.xml	2000/05/07 16:00:37	1.12
  @@ -219,7 +219,7 @@
       </p>
   
       <note>
  -     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).
       </note>
  @@ -253,7 +253,25 @@
   
       <p>
        Make sure you replaced the path to the Cocoon.properties 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 cocoon.properties, and has different instances for
  +      each servlet context, you need to put a copy of cocoon.properties in all
  +      of your servlet contexts that use Cocoon. (It is recommended to put it
  +      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, because
  +      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 contains
  @@ -270,20 +288,25 @@
      </p>
   
      <p>
  -    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 cocoon.properties - or, if you are have some
  +    non-standard properties in cocoon.properties which you need to keep,
  +    refer to the latest cocoon.properties to find out what changes need to
  +    be made, if any.
  +   </p>
  +
  +   <p>
  +    Everything should now be configured fine. Restart both Apache and Tomcat
       and try accessing the samples contained in the distribution to see
       Cocoon in action or the <code>/Cocoon.xml</code> page for Cocoon internal
       status.
      </p>
   
  -    <note>
  -     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 the
  -     <code>jakarta-tomcat</code> CVS module under <em>jakarta.apache.org</em>.
  -     We apologize for this, but it's not something we can control or work
  -     around.
  -    </note>
  +   <note>
  +    Tomcat 3.0 has a bug that prevents Cocoon operation, please download
  +    a later version.
  +   </note>
     </s2>
   
     <s2 title="Installing Cocoon on BEA WebLogic">
  
  
  

Mime
View raw message