You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@cocoon.apache.org by gh...@apache.org on 2003/05/08 04:55:11 UTC

cvs commit: cocoon-2.1/src/documentation/xdocs/installing index.xml

ghoward     2003/05/07 19:55:11

  Modified:    src/documentation/xdocs/installing index.xml
  Log:
  Start fixing docs for 2.1.  This is so out of sync now it may be best to 
  replace large sections with the contents of INSTALL.txt.
  
  Revision  Changes    Path
  1.5       +30 -27    cocoon-2.1/src/documentation/xdocs/installing/index.xml
  
  Index: index.xml
  ===================================================================
  RCS file: /home/cvs/cocoon-2.1/src/documentation/xdocs/installing/index.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- index.xml	29 Apr 2003 22:58:22 -0000	1.4
  +++ index.xml	8 May 2003 02:55:11 -0000	1.5
  @@ -34,13 +34,23 @@
         <p><strong>Servlet Engine</strong>
          A Servlet 2.2 compliant servlet engine must be present in order to support
          servlet operation and dynamic request handling. Note that this requirement
  -       is optional for command line operation.
  +       is optional for command line operation.  Note also that Cocoon now ships 
  +       with a stripped down version of Jetty suitable for immediately testing 
  +       with no further downloads.
         </p>
   
  -      <p>If you don't have a servlet engine installed, well, stop right here and
  -      go to the Apache Tomcat project
  -      <link href="http://jakarta.apache.org/tomcat/">http://jakarta.apache.org/tomcat/</link>
  -      then come back when you are done.</p>
  +      <p>When the time comes to run your Cocoon application in a full featured 
  +      servlet container, you may want to consider the following Open Source 
  +      options: 
  +      <ol> 
  +      	<li>The Apache Tomcat project
  +      		<link href="http://jakarta.apache.org/tomcat/">http://jakarta.apache.org/tomcat/</link>
  +      	</li>
  +      	<li>The full version of Jetty 
  +      		<link href="http://jetty.mortbay.org/">http://jetty.mortbay.org/</link>
  +      	</li>
  +      </ol>
  +      </p>
       </s1>
   
       <s1 title="Getting Apache Cocoon">
  @@ -131,41 +141,33 @@
           </p>
           <ol>
             <li>
  -            Create <code>%JAVA_HOME%\jre\lib\endorsed</code> directory.
  +            Create <code>%JAVA_HOME%\jre\lib\endorsed</code> directory.  (Tomcat users 
  +            use <code>%TOMCAT_HOME\common\endorsed</code> instead)
             </li>
             <li>
  -            Copy <code>xerces-XXX.jar</code>, <code>xalan-XXX.jar</code>,
  +            Copy <code>xercesXXX.jar</code>, <code>xalan-XXX.jar</code>,
               and the <code>xml-apis.jar</code> from the
  -            <code>.\lib\core\</code> to the
  -            <code>%JAVA_HOME%\jre\lib\endorsed\</code> directory.
  +            <code>.\lib\endorsed\</code> to the new directory created above.
             </li>
           </ol>
           <p>Due to changes in JDBC between JDK 1.3 and JDK 1.4, it is not possible 
  -           to use Cocoon build on JDK 1.3 with JDK 1.4 when it comes to database
  -           connections.</p>
  -        <p>So if you want to use Cocoon with JDK 1.4, you have to download the
  -           source distribution and build it by hand.
  +           to use Cocoon built on JDK 1.3 with JDK 1.4 when it comes to database
  +           connections.  Make sure you prepare cocoon with a JDK that matches the 
  +           one you will deploy on.
           </p>
         </s2>
   
         <s2 title="JDK Dependency">
  -        <p>Cocoon requires a Java compiler for some components like XSP etc.
  -           The default configuration of Cocoon does not use the compiler provided
  -           with the JDK but it's own version.
  -        </p>
  -        <p>However, if you want to use the JDK compiler, you have to change the
  -           configuration of Cocoon and make sure that the correct compiler is
  -           in the <code>WEB-INF/lib</code> directory. You can find the compiler
  -           in <code>%JAVA_HOME%/lib/javac.jar</code>.
  -        </p>
  -        <p>If you use the source distribution of Cocoon, the build system takes 
  -           care of this and copies the jar file to the appropriate directory. 
  -           If you use the binary distribution or want to switch between different
  -           JDKs you have to copy <code>%JAVA_HOME%/lib/javac.jar</code> to
  -           <code>WEB-INF/lib/javac.jar</code> replacing the existing version.
  +        <p>Cocoon requires a Java compiler for installation and for running some 
  +        	components like XSP etc.  For components, the default configuration of 
  +        	Cocoon does not use the compiler in JAVA_HOME, but a version shipped 
  +        	with Cocoon.
           </p>
  +        <note>You can configure which compiler Cocoon uses in WEB-INF/lib.
  +        </note>
         </s2>
   
  +	  <fixme>Is this still an issue?</fixme>
         <s2 title="UNIX with X server">
           <p>Cocoon is bundled with the <link href="http://xml.apache.org/batik/">Batik</link>
             (SVG rasterization toolkit) to deliver SVG imaging capabilities. Batik uses Java
  @@ -185,6 +187,7 @@
             and X libraries still must be installed.</note>
         </s2>
   
  +	  <fixme>Is this still an issue?</fixme>
         <s2 title="Headless UNIX and PJA">
           <p>If you are using unix with the Sun JDK 1.4, it can run in the
             headless environment (but you still must have X libraries installed!)