morrijr 02/01/14 07:22:16
Modified: src/documentation/xdocs/ctwig ctwig-installing.xml
ctwig-resources.xml ctwig-transformations.xml
src/documentation/xdocs/installing index.xml
Log:
Spelling errors and typos...
Revision Changes Path
1.2 +5 -5 xml-cocoon2/src/documentation/xdocs/ctwig/ctwig-installing.xml
Index: ctwig-installing.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/src/documentation/xdocs/ctwig/ctwig-installing.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- ctwig-installing.xml 3 Jan 2002 12:31:02 -0000 1.1
+++ ctwig-installing.xml 14 Jan 2002 15:22:15 -0000 1.2
@@ -14,7 +14,7 @@
<s2 title="Introduction">
<p>Installing C2 is straight-forward. 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 for {COCOON_HOME}).</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 that wherever {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 for {COCOON_HOME}).</p>
<p><strong>I'm really sorry, but at the moment these
examples relate to the latest distribution, 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">
@@ -34,9 +34,9 @@
</li>
<li>Add any additional components (I like FOP
for example)</li>
</ul>
- <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>Next, copy the xerces_xxx.jar to {TOMCAT_HOME}\lib,
delete the Tomcat jaxp jar and rename the parser.jar as instructed.</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>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 nothing - 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
(and resolved in 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>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 was 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
build.xml file.</p>
@@ -48,7 +48,7 @@
<p>Delete {TOMCAT_HOME}\webapps\cocoon.war.</p>
<p>Create {TOMCAT_HOME}\webapps\cocoon folder. If you
performed the test above using the war then this folder will already exist and you can
skip the next instruction.</p>
<p>Copy {COCOON_HOME}\build\cocoon\webapp\* to
{TOMCAT_HOME}\webapps\cocoon</p>
- <p>Restart tomcat and try
http://localhost:8080/cocoon. The welcome page should come up!</p>
+ <p>Restart Tomcat and try
http://localhost:8080/cocoon. The welcome page should come up!</p>
</s2>
<s2 title="Telling Apache about Cocoon">
<p>Note this assumes that mod_jk has been installed
and configured.</p>
@@ -59,7 +59,7 @@
JkMount /cocoon/* ajp12
]]></source>
<p>The first line includes the an Apache config file
that Tomcat automatically generates. This has all the alias directives for each of
the contexts in {TOMCAT_HOME}\conf\server.xml. The second line tells anything
requested to /cocoon to be sent to Tomcat (and then onwards to Cocoon).</p>
- <p>Restart tomcat THEN apache. The reason for this
way round is apache relies on the {TOMCAT_HOME}\conf\mod_jk.conf-auto which is built
by Tomcat everytime it starts.</p>
+ <p>Restart Tomcat THEN apache. The reason for this
way round is apache relies on the {TOMCAT_HOME}\conf\mod_jk.conf-auto which is built
by Tomcat everytime it starts.</p>
<p>You can then try http://localhost/cocoon. It
should work!</p>
<p>You are now ready to look at the examples and start
doing some <link href="ctwig-transformations.html">basic transformations</link></p>
</s2>
1.2 +2 -2 xml-cocoon2/src/documentation/xdocs/ctwig/ctwig-resources.xml
Index: ctwig-resources.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/src/documentation/xdocs/ctwig/ctwig-resources.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- ctwig-resources.xml 3 Jan 2002 12:31:02 -0000 1.1
+++ ctwig-resources.xml 14 Jan 2002 15:22:15 -0000 1.2
@@ -14,10 +14,10 @@
<s2 title="Apache Cocoon Web Site">
<p>The main place is <link
href="http://xml.apache.org/cocoon/";><code>http://xml.apache.org/cocoon/</code></link></p>
<p>The C2 documentation is still (and always will be)
under development. There is a lot of useful information there and it goes into a lot
more detail than here. Read it and digest it. I am certainly doing that as I go
along and quite quickly understanding more of the architecture and concepts. I will
seek to distill the main points into this site, but the main place is still the
supplied documentation.</p>
- <p>You will also find the documentation in your C2
installation under {COCCON_HOME}/docs/</p>
+ <p>You will also find the documentation in your C2
installation under {COCOON_HOME}/docs/</p>
</s2>
<s2 title="Apache Cocoon Users Mail List">
- <p><link
href="mailto:[EMAIL PROTECTED]";>Subscribe</link> to the Cocoon
users mail list! This is a great resource for asking and answwering questions. For
more details, and pointers to other related lists, see the <fork
href="http://xml.apache.org/cocoon/mail-lists.html";>documentation</fork>.</p>
+ <p><link
href="mailto:[EMAIL PROTECTED]";>Subscribe</link> to the Cocoon
users mail list! This is a great resource for asking and answering questions. For
more details, and pointers to other related lists, see the <fork
href="http://xml.apache.org/cocoon/mail-lists.html";>documentation</fork>.</p>
<p>You can also access an excellent, searchable,
archive of the users mail list at <fork
href="http://marc.theaimsgroup.com/?l=xml-cocoon-users";>The Aims Group</fork>. Use
this 'cos lots of things are there! Other list archive information is available in
the <fork
href="http://xml.apache.org/cocoon/mail-archives.html";>documentation</fork>.</p>
</s2>
<s2 title="Other Pages">
1.2 +1 -1
xml-cocoon2/src/documentation/xdocs/ctwig/ctwig-transformations.xml
Index: ctwig-transformations.xml
===================================================================
RCS file:
/home/cvs/xml-cocoon2/src/documentation/xdocs/ctwig/ctwig-transformations.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- ctwig-transformations.xml 3 Jan 2002 12:31:02 -0000 1.1
+++ ctwig-transformations.xml 14 Jan 2002 15:22:15 -0000 1.2
@@ -15,7 +15,7 @@
<p>Once C2 is installed you want to be able to serve
pages. It's all too easy to jump into doing complex XML/XSL/Logicsheet stuff without
understanding the basics of how it works. When I failed in this I changed my approach
to trying to do the simplest things then build up. This way has enforced some
concepts and most importantly started me on the way to becoming familiar with the
sitemap.</p>
</s2>
<s2 title="The Sitemap">
- <p>The bighgest change I have seen in C2 over C1.8 is
the Sitemap. This file ({TOMCAT_HOME}\webapps\cocoon\sitemap.xmap) contains a load of
XML that tells Cocoon what code handles what type of requests and what actions should
take place when a file is requested. It looks to be really powerful and as I
understand it more I will seek to open it up to more understanding. For the time
being it is sufficent to know that you have to do stuff with this file before anything
will work!</p>
+ <p>The biggest change I have seen in C2 over C1.8 is
the Sitemap. This file ({TOMCAT_HOME}\webapps\cocoon\sitemap.xmap) contains a load of
XML that tells Cocoon what code handles what type of requests and what actions should
take place when a file is requested. It looks to be really powerful and as I
understand it more I will seek to open it up to more understanding. For the time
being it is sufficent to know that you have to do stuff with this file before anything
will work!</p>
</s2>
<s2 title="The Building Blocks">
<p>The links below will take you to examples of using
C2 to serve XML that increase in complexity and demonstrate some of the techniques
that I am using. If you know better ways of doing these things or can add something
new please <link href="ctwig-contributing.html">contribute</link> and I will make the
examples better. One final point - these pages are being served from simple free web
space. C2 is not running behind this so I cannot provide working results of my
examples on this site. You will have to create the files and get them to work
yourself for the time being.</p>
1.4 +3 -3 xml-cocoon2/src/documentation/xdocs/installing/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/src/documentation/xdocs/installing/index.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- index.xml 11 Jan 2002 23:09:44 -0000 1.3
+++ index.xml 14 Jan 2002 15:22:16 -0000 1.4
@@ -132,7 +132,7 @@
The sample web application delivered with Cocoon contains some
examples which require a sql database. To make them work out of
the box, the hsqldb is included. However, this database needs
- the installation path to work correctly. Using tomcat (see notes
+ the installation path to work correctly. Using Tomcat (see notes
below) you could use the following instruction to directly
build a web application which is alreary configured for the sql
examples. The build script will copy it directly to your webapps
@@ -326,7 +326,7 @@
<li>Unpack the jars into a place where your jdk will be able to use them--
$JAVAHOME/jre/classes works for j2sdk1.3</li>
- <li>Then add the following to your tomcat startup script
+ <li>Then add the following to your Tomcat startup script
(using CATALINA_OPTS if it is 4.x, TOMCAT_OPTS if it is 3.x)
</li>
</ol>
@@ -494,7 +494,7 @@
</source>
<p>Subsequently, </p>
<ul><li><code>jboss</code> denotes the
<code>JBoss-2.2.2_Tomcat-3.2.2/jboss</code> directory</li>
- <li><code>tomcat</code> is short for
<code>JBoss-2.2.2_Tomcat-3.2.2/tomcat</code></li><li>and <code>cocoon</code> is the
base directory of your Cocoon distribution or CVS checkout.</li></ul>
+ <li><code>Tomcat</code> is short for
<code>JBoss-2.2.2_Tomcat-3.2.2/tomcat</code></li><li>and <code>cocoon</code> is the
base directory of your Cocoon distribution or CVS checkout.</li></ul>
<p>In order to get Cocoon running you have to install Xerces as default XML
parser for JBoss.</p>
<ul>
<li>Stop the server if it is running.</li>
----------------------------------------------------------------------
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
