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

cvs commit: xml-cocoon2/documentation/xdocs/ctwig ctwig-gettingstarted.xml ctwig-installing.xml

cziegeler    01/11/07 07:05:55

  Modified:    documentation/xdocs/ctwig Tag: cocoon_20_branch
                        ctwig-gettingstarted.xml ctwig-installing.xml
  Log:
  Slightly updated docs
  
  Revision  Changes    Path
  No                   revision
  
  
  No                   revision
  
  
  1.1.2.3   +1 -1      xml-cocoon2/documentation/xdocs/ctwig/ctwig-gettingstarted.xml
  
  Index: ctwig-gettingstarted.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon2/documentation/xdocs/ctwig/ctwig-gettingstarted.xml,v
  retrieving revision 1.1.2.2
  retrieving revision 1.1.2.3
  diff -u -r1.1.2.2 -r1.1.2.3
  --- ctwig-gettingstarted.xml	2001/11/01 04:20:25	1.1.2.2
  +++ ctwig-gettingstarted.xml	2001/11/07 15:05:55	1.1.2.3
  @@ -25,7 +25,7 @@
   
   			<s2 title="Where do I get it from?">
   				<p>Go to <fork href="http://xml.apache.org/cocoon2/">http://www.apache.org/cocoon2/</fork> and download it from there.  The latest distribution for any operating system
  -				<fork href="http://xml.apache.org/cocoon2/dist/Cocoon-2.0rc1a.zip">Cocoon 2 Release Candidate 1a</fork>.  This file contains the Cocoon code, samples, documentation and the Java libraries that enable the Cocoon to work such as Xerces and Xalan.</p>
  +				<fork href="http://xml.apache.org/cocoon2/dist/Cocoon-2.0rc2.zip">Cocoon 2 Release Candidate 2</fork>.  This file contains the Cocoon code, samples, documentation and the Java libraries that enable the Cocoon to work such as Xerces and Xalan.</p>
   			</s2>
   
   			<s2 title="What assumptions have you made?">
  
  
  
  1.1.2.3   +5 -5      xml-cocoon2/documentation/xdocs/ctwig/ctwig-installing.xml
  
  Index: ctwig-installing.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon2/documentation/xdocs/ctwig/ctwig-installing.xml,v
  retrieving revision 1.1.2.2
  retrieving revision 1.1.2.3
  diff -u -r1.1.2.2 -r1.1.2.3
  --- ctwig-installing.xml	2001/11/01 04:20:25	1.1.2.2
  +++ ctwig-installing.xml	2001/11/07 15:05:55	1.1.2.3
  @@ -14,11 +14,11 @@
   			<s2 title="Introduction">
   				<p>Installing C2 is not a complete nightmare.  I found that following the instructions in the documentation worked just fine.  The only issue here is that by following the instructions you end up with a WAR file and this is no good for development because you cannot add your own code or make changes to existing files without repackaging it all up.</p>
   				<p>To get around these problems you need to install it as an unpacked application and get your servlet engine to recognise it as such.</p>
  -				<p>Please note the assumptions about platform, user knowledge and existing applications in the <link href="ctwig-why.html">Why?</link> section and also note thatw herever {TOMCAT_HOME}, {COCOON_HOME} or {APACHE_HOME} appears it should be replaced with the path it is installed into on your machine (e.g. d:\java\cocoon\2.02rc1a for {COCOON_HOME}).</p>
  -				<p><strong>I'm really sorry, but at the moment these examples relate to C2rc1a, Tomcat 3.2.3 and Apache 1.3.19 on Windows 2000.</strong> It is probably all the same for any operating system (remember, that is the promise of Java and XML). I would like to do TC4/Unix notes but do not have the time at the momement.  If you can help then please <link href="ctwig-contributing.html">contribute</link>.</p>
  +				<p>Please note the assumptions about platform, user knowledge and existing applications in the <link href="ctwig-why.html">Why?</link> section and also note thatw herever {TOMCAT_HOME}, {COCOON_HOME} or {APACHE_HOME} appears it should be replaced with the path it is installed into on your machine (e.g. d:\java\cocoon\2.02rc2 for {COCOON_HOME}).</p>
  +				<p><strong>I'm really sorry, but at the moment these examples relate to C2rc2, Tomcat 3.2.3 and Apache 1.3.19 on Windows 2000.</strong> It is probably all the same for any operating system (remember, that is the promise of Java and XML). I would like to do TC4/Unix notes but do not have the time at the momement.  If you can help then please <link href="ctwig-contributing.html">contribute</link>.</p>
   			</s2>
   			<s2 title="Download Cocoon 2">
  -				<p>The latest distribution for any operating system is <fork href="http://xml.apache.org/cocoon2/dist/Cocoon-2.0rc1a.zip">Cocoon 2 release candidate 1a</fork>.  This file contains the Cocoon code, samples, documentation and the Java libraries that enable the Cocoon to work such as Xerces and Xalan.  The file is in ZIP format.  When you have downloaded it then extract it to somewhere.  This path becomes your {COCOON_HOME}.</p>
  +				<p>The latest distribution for any operating system is <fork href="http://xml.apache.org/cocoon2/dist/Cocoon-2.0rc2.zip">Cocoon 2 release candidate 2</fork>.  This file contains the Cocoon code, samples, documentation and the Java libraries that enable the Cocoon to work such as Xerces and Xalan.  The file is in ZIP format.  When you have downloaded it then extract it to somewhere.  This path becomes your {COCOON_HOME}.</p>
   			</s2>
   			<s2 title="Basic Configuration">
   				<p>Follow the instructions on building C2 as per the installation guide that comes with C2.  It can also be found <fork href="http://xml.apache.org/cocoon2/install.html">here</fork> as well.  Obviously since you have got the ZIP distribution you do not have to do the CVS bit thus you can start at the Building Apache Cocoon 2 section.  Do each of the following steps:</p>
  @@ -37,9 +37,9 @@
   				<p>Next, copy the xerces_xxx.jar to {TOMCAT_HOME}\lib, delete the tomcat jaxp jar and rename the parser.jar as instructuted.</p>
   				<p>An important point is that if you are running Tomcat as an NT service then you will need to change {TOMCAT_HOME}\conf\wrapper.properties to reflect the classpath changes.  Make sure xerces is first in line, remove (or comment out) the jaxp and rename the parser.jar reference.  This is all done with the wrapper.class_path bit.</p>
   				<p>If you did run the second build.bat command above or if you copy cocoon.war into {TOMCAT_HOME}\webapps then you can check that C2 is working.  Restart Tomcat and http://localhost:8080/cocoon should work.  Note at this point Apache is doing nowt - Tomcat is doing the http serving.  If there are any problems then check that the tomcat classpath in wrapper.properties is correct and you have done the work in {TOMCAT_HOME}\lib as descibed above.</p>
  -				<p>One other situation that came to light in C2 RC1 (as opposed to RC1a) was that the build file was including a reference to the LDAP transformer classes and since the JAR is not included then you would see an error when starting C2 along the lines of:</p>
  +				<p>One other situation that came to light in C2 RC1 (as opposed to RC1a and RC2) was that the build file was including a reference to the LDAP transformer classes and since the JAR is not included then you would see an error when starting C2 along the lines of:</p>
   				<p>org.apache.cocoon.ProcessingException: Exception in Handler: org.apache.avalon.framework.component.ComponentException: Could not set up Component for hint: org\apache\cocoon\www\sitemap_xmap</p>
  -				<p>This has been resolved in C2 RC1a by making changing the offending include line in build.xml.  Have a look and see.  You will need to change this line if you want to use the LDAP transformer as per the instructions in the RC1a build.xml file.</p>
  +				<p>This has been resolved in C2 RC1a and RC2 by making changing the offending include line in build.xml.  Have a look and see.  You will need to change this line if you want to use the LDAP transformer as per the instructions in the RC1a build.xml file.</p>
   				<p>One other good point about testing, especially if you are upgrading, is to delete the Cocoon working files in {TOMCAT_HOME}\work.  If left in between upgrades, you can easily get precompiled code sent instead of the new pages being compiled and served.</p>
   			</s2>
   			<s2 title="Configure C2 to run in Unpackaged Mode">
  
  
  

----------------------------------------------------------------------
In case of troubles, e-mail:     webmaster@xml.apache.org
To unsubscribe, e-mail:          cocoon-cvs-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-cvs-help@xml.apache.org