cocoon-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From gree...@apache.org
Subject cvs commit: xml-cocoon/xdocs installing.xml cocoon2.xml
Date Thu, 11 Jan 2001 14:04:20 GMT
greenrd     01/01/11 06:04:20

  Modified:    xdocs    installing.xml cocoon2.xml
  Log:
  minor docs updates
  
  Revision  Changes    Path
  1.42      +47 -29    xml-cocoon/xdocs/installing.xml
  
  Index: installing.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon/xdocs/installing.xml,v
  retrieving revision 1.41
  retrieving revision 1.42
  diff -u -r1.41 -r1.42
  --- installing.xml	2001/01/11 01:14:33	1.41
  +++ installing.xml	2001/01/11 14:04:19	1.42
  @@ -71,6 +71,12 @@
      is required for Cocoon page compilation.
     </p>
   
  +  <p>
  +   It is <strong>very important</strong> to ensure that the xerces jar is in
front
  +   of other XML parsers in the CLASSPATH. This is the most frequent source of errors
  +   in installing Cocoon!
  +  </p>
  +
     <note>
      The Ant, Stylebook and Servlet packages are only used in the build system and
      are <strong>not</strong> used by Cocoon at run-time. So you can safely
  @@ -108,7 +114,10 @@
   <source>wrapper.classpath=[path-to-jar]/[jar-name].jar</source>
   
      <p>
  -    Here is an example:
  +    Here is an example: <strong>This is an EXAMPLE only and may not be 
  +    up to date. If you get errors, first check that all the required jar files
  +    (see top of page)
  +    from cocoon/lib are on your CLASSPATH, and spelled correctly.</strong>
      </p>
   
   <source>
  @@ -227,7 +236,8 @@
       A context in Tomcat describes to Tomcat how and when to load a particular servlet
       and Cocoon is one such servlet. First we need to make sure that Tomcat knows how to
       load the Cocoon .jar files. To begin with, you must copy any .jar files from
  -    <code>$COCOON_HOME/lib</code> to <code>$TOMCAT_HOME/lib</code>
that are necessary for Cocoon to run.
  +    <code>$COCOON_HOME/lib</code> to <code>$TOMCAT_HOME/lib</code>
that are necessary for Cocoon to run
  +    (see top of page).
       In addition, you must copy <code>$COCOON_HOME/bin/cocoon.jar</code> to
<code>$TOMCAT_HOME/lib</code>.
      </p>
   
  @@ -375,7 +385,7 @@
       make sure that <code>xerces.jar</code> is located 
       <strong>before</strong> 
       other XML jars in the CLASSPATH, otherwise XSP won't work.
  -    On UNIX at least,
  +    On UNIX at least, Tomcat
       constructs its own CLASSPATH automatically and then adds the environment 
       CLASSPATH, so manually setting the CLASSPATH before running Tomcat won't work.
       Instead, a hack which some people have found to work is (in the case of Tomcat 3.1)
renaming
  @@ -394,9 +404,8 @@
   
   <s2 title="Installing Cocoon on ServletExec 2.2">
   
  -<p>After you have obtained all the jar packages you need
  -(see the above section), you should add
  -them to your <code>Classpath.pref</code> file.
  +<p>Add all the required .jar files
  +(see top of page) to your <code>Classpath.pref</code> file.
   Then, add this to the <code>servlets.properties</code> file:</p>
   
   <source>servlet.Cocoon.code=org.apache.cocoon.Cocoon
  @@ -435,9 +444,8 @@
   
      <s3 title="BEA WebLogic version 4.5.1">
       <p>
  -     After you have obtained all the jar packages you need (see the above
  -     section), you should add all of them (included the <code>cocoon.jar</code>
  -     package to your <code>weblogic.class.path</code> variable either
  +     Add all of the required jar files (see top of page)
  +     to your <code>weblogic.class.path</code> variable, either
        using the <em>t3config</em> utility or use the <code>-Dweblogic.class.path</code>
        argument with the java runtime that invokes the system.
       </p>
  @@ -452,14 +460,6 @@
        path in your system.
       </p>
   
  -    <p>
  -     At this point, you should check if your system matches the global
  -     considerations about Cocoon properties. Usually, you might want to give
  -     the installation a try as it is and then read again that section if
  -     something goes wrong. Most installations don't need any changes to
  -     be operational.
  -    </p>
  -
      </s3>
   
      <s3 title="BEA WebLogic version 5.1 / Enterprise 5.1 J-Engine">
  @@ -469,10 +469,7 @@
        Enterprise 5.1 J-Engine.)</p>
   
       <ul>
  -     <li>Add the xerces, xalan, fop, turbine-pool, servlet, and cocoon JAR files
(from the
  -      distribution) to your CLASSPATH. (See below). If you're using Java
  -      2, you should also add the tools.jar file from the JDK distribution
  -      to your CLASSPATH.</li>
  +     <li>Add all the required jar files (see top of page) to your CLASSPATH.</li>
        <li>Create a new subdirectory tree of your WLS run time directory
         "cocoonwar/WEB-INF" and copy the default web.xml file (from the
         src/WEB-INF directory of the distribution) there.</li>
  @@ -555,8 +552,16 @@
      <s3 title="JRun version 2.3">
       <p>
        For the JRun portion, you must add all Cocoon jars to the java.classpath
  -     in [jrun-home]/jsm-default/properties with something like:
  +     in [jrun-home]/jsm-default/properties.
       </p>
  +
  +   <p>
  +    Here is an example: <strong>This is an EXAMPLE only and may not be
  +    up to date. If you get errors, first check that all the required jar files
  +    (see top of page)
  +    from cocoon/lib are on your CLASSPATH.</strong>
  +   </p>
  +                                                                                      
                                     
   <source>java.classpath=[previous jrun jars]:[cocoon-home]/lib/xerces.jar:
   [cocoon-home]/lib/stylebook.jar:[cocoon-home]/lib/fop.jar:
   [cocoon-home]/bin/cocoon.jar:[cocoon-home]/lib/xalan.jar:
  @@ -634,7 +639,7 @@
       The "Alias" line above is optional; but it will make
       testing the setup much easier.  To verify that all is working,
       make sure to test out the XSP demos.  If you get a
  -    java.lang.NoSuchMethodError: org.w3c.dom.Node error, try moving
  +    NoSuchMethodError, try moving
       the xerces.jar to the front of JRun's java.classpath, restart
       JRun, and try the XSP again.
      </p>
  @@ -659,20 +664,27 @@
   servlet.cocoon.initArgs=properties=<yourpath to cocoon>/cocoon/conf/cocoon.properties]]>
   </source>
   
  -    <p>In the <code>jvm12.conf</code>, add all the needed ".jar" to the
<code>jvm.classpath</code> line 
  +    <p>In the <code>jvm12.conf</code>, add all the needed ".jar" files
to the <code>jvm.classpath</code> line 
       and uncomment it. This would make the following line, for example, if you
       installed Netscape on D: drive. (Note: This should be all on one line, but 
       for legibility it is split accross lines.)</p>
   
  +   <p>
  +    <strong>This is an EXAMPLE only and may not be
  +    up to date. If you get errors, first check that all the required jar files
  +    (see top of page)
  +    from cocoon/lib are on your CLASSPATH.</strong>
  +   </p>
  +
       <source>jvm.classpath=d:/Netscape/Server4/plugins/samples/servlets/beans.10/SDKBeans10.jar;
   d:/Netscape/Server4/plugins/samples/servlets/beans/SDKBeans.jar;
   d:/Netscape/Server4/bin/https/jar/Bugbase.jar;
   d:/Netscape/Server4/bin/https/jar/Calljsac.jar;
   D:/Netscape/Server4/docs/cocoon/bin/cocoon.jar;
  -D:/Netscape/Server4/docs/cocoon/lib/fop_0_12_1.jar;
  -D:/Netscape/Server4/docs/cocoon/lib/stylebook-1.0-b2.jar;
  -D:/Netscape/Server4/docs/cocoon/lib/xalan_1_0_1.jar;
  -D:/Netscape/Server4/docs/cocoon/lib/xerces_1_0_3.jar
  +D:/Netscape/Server4/docs/cocoon/lib/fop_0_15.jar;
  +D:/Netscape/Server4/docs/cocoon/lib/turbine-pool.jar;
  +D:/Netscape/Server4/docs/cocoon/lib/xalan_1_2_D02.jar;
  +D:/Netscape/Server4/docs/cocoon/lib/xerces_1_2.jar
   </source>
   
       <p>In the rules.properties file, add the following line (this is made to turn
around a regexp bug in iWS):</p>
  @@ -711,6 +723,12 @@
       <p><strong>WARNING! Do NOT add servlet_2_2.jar (from the Cocoon distribution)
to the CLASSPATH.
        This is only provided for the purposes of rebuilding Cocoon, and because WebSphere
uses
        non-standard Servlet API calls, this jar may cause WebSphere to fail.</strong></p>
  +   <p>
  +    <strong>This is an EXAMPLE only and may not be
  +    up to date. If you get errors, first check that all the required jar files
  +    (see top of page)
  +    from cocoon/lib are on your CLASSPATH.</strong>
  +   </p>
   
      <source><![CDATA[
   # usage: wscp -f ws.tcl
  @@ -725,7 +743,7 @@
   ApplicationServer modify $appserv/ -attribute
   {{CommandLineArgs {-classpath D:/cocoon-1.8/lib/bsf.jar;D:/cocoon-1.8/lib/bsfengines.jar;
   D:/cocoon-1.8/lib/turbine-pool.jar;D:/cocoon-1.8/lib/xerces_1_2.jar;
  -D:/cocoon-1.8/lib/xalan_1_2_D02.jar;D:/cocoon-1.8/lib/fop_0_13_0.jar;
  +D:/cocoon-1.8/lib/xalan_1_2_D02.jar;D:/cocoon-1.8/lib/fop_0_15_0.jar;
   D:/WebSphere/AppServer/jdk/lib/tools.jar;D:\cocoon-1.8\bin\cocoon.jar}}}
   
   # create the cocoon web application
  
  
  
  1.8       +7 -3      xml-cocoon/xdocs/cocoon2.xml
  
  Index: cocoon2.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon/xdocs/cocoon2.xml,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- cocoon2.xml	2000/09/19 23:01:40	1.7
  +++ cocoon2.xml	2001/01/11 14:04:19	1.8
  @@ -301,10 +301,14 @@
     CVS branch in the Cocoon CVS module. If you are not a CVS expert, this means
     typing:</p>
   
  -  <source>cvs checkout -r xml-cocoon2 xml-cocoon</source>
  +  <source>
  +    cvs -d :pserver:anoncvs@xml.apache.org:/home/cvspublic login
  +    Password: anoncvs
   
  -  <p>For more information on CVS access, refer to the CVS docs on this web
  -  site.</p>
  +    cvs -d :pserver:anoncvs@xml.apache.org:/home/cvspublic checkout -r xml-cocoon2 xml-cocoon
  +  </source>
  +
  +  <p>For more information on CVS access, refer to the CVS docs on this web site.</p>
   </s1>
   
   </body>
  
  
  

Mime
View raw message