cocoon-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject cvs commit: xml-cocoon2/documentation/xdocs/ctwig index.xml ctwig-basic01.xml ctwig-basic02.xml ctwig-basic03.xml ctwig-contributing.xml ctwig-gettingstarted.xml ctwig-installing.xml ctwig-resources.xml ctwig-transformations.xml ctwig-why.xml
Date Thu, 01 Nov 2001 04:16:05 GMT
crossley    01/10/31 20:16:05

  Modified:    documentation/xdocs/ctwig index.xml ctwig-basic01.xml
                        ctwig-basic02.xml ctwig-basic03.xml
                        ctwig-contributing.xml ctwig-gettingstarted.xml
                        ctwig-installing.xml ctwig-resources.xml
                        ctwig-transformations.xml ctwig-why.xml
  Log:
  Add Document Type Declaration
  Mend many XML validation errors
  
  Revision  Changes    Path
  1.3       +5 -7      xml-cocoon2/documentation/xdocs/ctwig/index.xml
  
  Index: index.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon2/documentation/xdocs/ctwig/index.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- index.xml	2001/10/23 07:06:54	1.2
  +++ index.xml	2001/11/01 04:16:04	1.3
  @@ -1,8 +1,6 @@
  -<?xml version="1.0"?>
  +<?xml version="1.0" encoding="UTF-8"?>
  +<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.0//EN" "dtd/document-v10.dtd">
   
  -<!--
  -<!DOCTYPE document SYSTEM "./dtd/document-v10.dtd">
  --->
   <document>
   	<header>
   		<title>cTwIG - Cocoon Two Idiots Guide</title>
  @@ -19,9 +17,9 @@
   			<p>One final point...  All the work I am doing is on Windows 2000 boxes thus I
cannot vouch for validity of my rantings on any Unix or other Windows (95, 98, NT4, ME etc)
box.  Hopefully this will change over time but for the time being this will have to do.</p>
   			<p>I hope these pages can be of use!</p>
   			<p><link href="mailto:jez@pigbite.com">Jeremy Aston</link></p>
  -		</s1>
   		<s2 title="Disclaimer">
  -			<p class="disclaimer">Disclaimer type thang...  I will always sincerely aim that
all the information here is as accurate.  If I make an errors I promise to put them right
as soon as I know about them, please help by <link href="ctwig-contributing.html">contributing</link>
if and when you see anything that is wrong or misleading.  Please always check the official
documentation and take that as the most accurate.  Please always ensure you have backups of
critical files.  I cannot guarantee that none of the instructions on my pages could harm your
system but all the information is there in good faith and will be changed if it is found to
be wrong.  Please take your share of the responsibility and act professionally and with care.
 Ta ever so!  Jez.</p>
  +			<p>Disclaimer type thang...  I will always sincerely aim that all the information
here is as accurate.  If I make an errors I promise to put them right as soon as I know about
them, please help by <link href="ctwig-contributing.html">contributing</link>
if and when you see anything that is wrong or misleading.  Please always check the official
documentation and take that as the most accurate.  Please always ensure you have backups of
critical files.  I cannot guarantee that none of the instructions on my pages could harm your
system but all the information is there in good faith and will be changed if it is found to
be wrong.  Please take your share of the responsibility and act professionally and with care.
 Ta ever so!  Jez.</p>
   		</s2>
  +		</s1>
   	</body>
  -</document>
  \ No newline at end of file
  +</document>
  
  
  
  1.3       +11 -10    xml-cocoon2/documentation/xdocs/ctwig/ctwig-basic01.xml
  
  Index: ctwig-basic01.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon2/documentation/xdocs/ctwig/ctwig-basic01.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- ctwig-basic01.xml	2001/10/23 07:06:54	1.2
  +++ ctwig-basic01.xml	2001/11/01 04:16:04	1.3
  @@ -1,12 +1,12 @@
  -<?xml version="1.0"?>
  +<?xml version="1.0" encoding="UTF-8"?>
  +<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.0//EN" "dtd/document-v10.dtd">
   
  -<!--
  -<!DOCTYPE document SYSTEM "./dtd/document-v10.dtd">
  --->
  -<?xml-stylesheet href="document2html.xsl" type="text/xsl"?>
   <document>
   	<header>
   		<title>cTwIG - Cocoon Two Idiots Guide - Basic XML/XSL Transformation</title>
  +		<authors>
  +			<person name="Jeremy Aston" email="jez@pigbite.com"/>
  +		</authors>
   	</header>
   
   	<body>
  @@ -50,7 +50,7 @@
       <map:serialize/> 
     </map:match>
   				]]></source>
  -				<p>What this construct does is to tell C2 to do something when it recieves a
request for <b>ctwig/basic01-01.xml</b>.  The "something" that C2 will do is pass
the <b>ctwig/basic01-01.xml</b> file through a "file" generator.  This basically
parses the XML.  The result parsed stream then gets transformed using <b>ctwig/basic01-01.xsl</b>
and rendered.</p>
  +				<p>What this construct does is to tell C2 to do something when it recieves a
request for <strong><code>ctwig/basic01-01.xml</code></strong>.  The
"something" that C2 will do is pass the <strong><code>ctwig/basic01-01.xml</code></strong>
file through a "file" generator.  This basically parses the XML.  The result parsed stream
then gets transformed using <strong><code>ctwig/basic01-01.xsl</code></strong>
and rendered.</p>
   				<p>Calling <fork href="http://localhost:8080/cocoon/ctwig/basic01-01.xml">http://localhost:8080/cocoon/ctwig/basic01-01.xml</fork>
will result in a simple HTML page being rendered.</p>
   			</s2>
   			<s2 title="Simple Wildcards in the Sitemap File">
  @@ -62,7 +62,7 @@
       <map:serialize/> 
     </map:match>
   				]]></source>
  -				<p>then C2 will substitutue the <b>{1}</b> meta-tag with the whatever
is in the wildcard section of the request.  This means that is every XML file has a corresponding
XSL file with the same filename (before the extension) then requesting the XML file will result
in it being served.</p>
  +				<p>then C2 will substitutue the <strong><code>{1}</code></strong>
meta-tag with the whatever is in the wildcard section of the request.  This means that is
every XML file has a corresponding XSL file with the same filename (before the extension)
then requesting the XML file will result in it being served.</p>
   				<p>This also allows us to do a kind of request re-writing function.  Take the
following sitemap construct:</p>
   				<source><![CDATA[
     <map:match pattern="ctwig/*.html"> 
  @@ -71,7 +71,7 @@
       <map:serialize/> 
     </map:match>
   				]]></source>
  -				<p>This allows us to request an HTML file from the ctwig folder.  What will actually
happen though is that C2 willtake the wildcard portion and use that to look for XML and XSL
files with the same filename and use them to generate the response stream contents.  For example;
<fork href="http://localhost:8080/cocoon/ctwig/basic01-01.html">http://localhost:8080/cocoon/ctwig/basic01-01.html</fork>
will cause C2 to look for <b>ctwig/basic01-01.xml</b> and transform it with <b>ctwig/basic01-01.xsl</b>
to produce the final page.</p>
  +				<p>This allows us to request an HTML file from the ctwig folder.  What will actually
happen though is that C2 willtake the wildcard portion and use that to look for XML and XSL
files with the same filename and use them to generate the response stream contents.  For example;
<fork href="http://localhost:8080/cocoon/ctwig/basic01-01.html">http://localhost:8080/cocoon/ctwig/basic01-01.html</fork>
will cause C2 to look for <strong><code>ctwig/basic01-01.xml</code></strong>
and transform it with <strong><code>ctwig/basic01-01.xsl</code></strong>
to produce the final page.</p>
   			</s2>
   			<s2 title="Using a Single XSL File">
   				<p>Consider a scenario where you have multiple XML files which are you wish to
transform in a common fashion (for example into HTML).  If your XML has been designed well
and follows a common DTD there is no reason why one XSL file can transform all the XML files.
 Many of the C2 examples do this, using one, single, common XSL file for rendering all the
examples to HTML and another for transforming them into a source code view.  This again is
achieved using the sitemap file with a construct similar to the following:</p>
  @@ -82,8 +82,9 @@
       <map:serialize/> 
     </map:match>
   				]]></source>
  -				<p>Here, a request for an HTML page will look for a corresponding XML file and
transform it using <b>ctwig/file2html.xsl</b>.  <sub><em><b>TODO
- PROVIDE AN EXAMPLE.</b></em></sub></p>
  +				<p>Here, a request for an HTML page will look for a corresponding XML file and
transform it using <strong><code>ctwig/file2html.xsl</code></strong>.</p>
   			</s2>
  +  <note>TODO: PROVIDE AN EXAMPLE.</note>
   		</s1>
   	</body>
  -</document>
  \ No newline at end of file
  +</document>
  
  
  
  1.3       +6 -6      xml-cocoon2/documentation/xdocs/ctwig/ctwig-basic02.xml
  
  Index: ctwig-basic02.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon2/documentation/xdocs/ctwig/ctwig-basic02.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- ctwig-basic02.xml	2001/10/23 07:06:54	1.2
  +++ ctwig-basic02.xml	2001/11/01 04:16:04	1.3
  @@ -1,12 +1,12 @@
  -<?xml version="1.0"?>
  +<?xml version="1.0" encoding="UTF-8"?>
  +<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.0//EN" "dtd/document-v10.dtd">
   
  -<!--
  -<!DOCTYPE document SYSTEM "./dtd/document-v10.dtd">
  --->
  -<?xml-stylesheet href="document2html.xsl" type="text/xsl"?>
   <document>
   	<header>
   		<title>cTwIG - Cocoon Two Idiots Guide - Basic XSP Processing</title>
  +		<authors>
  +			<person name="Jeremy Aston" email="jez@pigbite.com"/>
  +		</authors>
   	</header>
   
   	<body>
  @@ -48,4 +48,4 @@
   			</s2>
   		</s1>
   	</body>
  -</document>
  \ No newline at end of file
  +</document>
  
  
  
  1.3       +9 -9      xml-cocoon2/documentation/xdocs/ctwig/ctwig-basic03.xml
  
  Index: ctwig-basic03.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon2/documentation/xdocs/ctwig/ctwig-basic03.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- ctwig-basic03.xml	2001/10/23 07:06:54	1.2
  +++ ctwig-basic03.xml	2001/11/01 04:16:04	1.3
  @@ -1,12 +1,12 @@
  -<?xml version="1.0"?>
  +<?xml version="1.0" encoding="UTF-8"?>
  +<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.0//EN" "dtd/document-v10.dtd">
   
  -<!--
  -<!DOCTYPE document SYSTEM "./dtd/document-v10.dtd">
  --->
  -<?xml-stylesheet href="document2html.xsl" type="text/xsl"?>
   <document>
   	<header>
   		<title>cTwIG - Cocoon Two Idiots Guide - Basic XSP/Logicsheet Processing</title>
  +		<authors>
  +			<person name="Jeremy Aston" email="jez@pigbite.com"/>
  +		</authors>
   	</header>
   
   	<body>
  @@ -63,8 +63,8 @@
   </xsl:template>
   
   </xsl:stylesheet>]]></source>
  -				<p>You will note that the logicsheet has a reference to the ctwig namespace.
 This <b>must</b> match the namespace used in the XSP page.  The logicsheet uses
a standard XSL template match to find the reference to "ctwig:greeting" and replace it with
the logic.</p>
  -				<em>Again, please note that this example uses "http://apache.org/xsp" as the
XSP namespace.  This is different to older C1 based examples and should be used instead. 
If you do not then any logicsheet example definitely will not work.</em>
  +				<p>You will note that the logicsheet has a reference to the ctwig namespace.
 This <strong>must</strong> match the namespace used in the XSP page.  The logicsheet
uses a standard XSL template match to find the reference to "ctwig:greeting" and replace it
with the logic.</p>
  +				<p><em>Again, please note that this example uses "http://apache.org/xsp"
as the XSP namespace.  This is different to older C1 based examples and should be used instead.
 If you do not then any logicsheet example definitely will not work.</em></p>
   				<p>To make this work firstly make sure that basic3-01.xml in the {TOMCAT_HOME}\webapps\cocoon\ctwig\xsp
folder.  This will allow it to be captured by the same sitemap command that is used in the
previous examples.  Secondly, make sure that the ctwig logicsheet (ctwig.xsl) is in {TOMCAT_HOME}/webapps/cocoon/WEB-INF/classes/com/pigbite/logicsheets
folder.  The final thing to do is to add a reference to the logicsheet source in to C2 so
it knows where to go and find it.  This is done by adding the following construct to {TOMCAT_HOME}\webapps\cocoon\cocoon.xconf:</p>
   				<source><![CDATA[
     <builtin-logicsheet>
  @@ -79,10 +79,10 @@
      name="href"
      value="file:///{TOMCAT_HOME}/webapps/cocoon/ctwig/logicsheet/ctwig.xsl">]]></source>
   				<p>Obviously replace {TOMCAT_HOME} with whatever the actual path is on your machine
(e.g. d:\java\tomcat).  Note the use of three forward slashes after the "file:".  This is
so that it properly refers to the root, you still have to include the drive letter however.</p>
  -				<p>Again, the URI parameter <b>must</b> be the same as the namespace
declarations for everything to get properly resolved.</p>
  +				<p>Again, the URI parameter <strong>must</strong> be the same as
the namespace declarations for everything to get properly resolved.</p>
   				<p>To test this code call <fork href="http://localhost:8080/cocoon/ctwig/xsp/basic03-01.xml">http://localhost:8080/cocoon/ctwig/xsp/basic03-01.xml</fork></p>
   
   			</s2>
   		</s1>
   	</body>
  -</document>
  \ No newline at end of file
  +</document>
  
  
  
  1.3       +8 -8      xml-cocoon2/documentation/xdocs/ctwig/ctwig-contributing.xml
  
  Index: ctwig-contributing.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon2/documentation/xdocs/ctwig/ctwig-contributing.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- ctwig-contributing.xml	2001/10/23 07:06:54	1.2
  +++ ctwig-contributing.xml	2001/11/01 04:16:04	1.3
  @@ -1,20 +1,20 @@
  -<?xml version="1.0"?>
  +<?xml version="1.0" encoding="UTF-8"?>
  +<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.0//EN" "dtd/document-v10.dtd">
   
  -<!--
  -<!DOCTYPE document SYSTEM "./dtd/document-v10.dtd">
  --->
  -<?xml-stylesheet href="document2html.xsl" type="text/xsl"?>
   <document>
   	<header>
   		<title>cTwIG - Cocoon Two Idiots Guide - Contributing</title>
  +		<authors>
  +			<person name="Jeremy Aston" email="jez@pigbite.com"/>
  +		</authors>
   	</header>
   
   	<body>
   		<s1 title="Contributing">
  -			<p>I am more than happy to recieve amendments, improvements and so on to these
pages.  I want the information to be as up to date and as accurate as possible so please do
not hesitate to let me know if you find anything wrong.  I would also be really pleased to
receive submissions of more tutorial documentation for C2.  I hope that sections will develop
for areas such as the sitemap, configuration tutorials, development techniques and so on which
will require reasonable effort to develop however I think it would also be good to take up
the suggestion of a FAQ based on some of the common questions that come up on the list.  I
will start this off over the next couple of days and try and add to it as quickly as possible.</p>
  -			<p>I have written these pages in the xdocs format, thus it would be really useful
if any contributions are in that format.  If you want to see examples of the markup required
please check the files in the C2 xdocs folder that comes as part of the distribution.  The
DTD is in xdocs/dtd/document-v10.dtd.  I am more than happy to take contributions in email,
MS Word, PDF, TXT etc however any conversion may delay the publishing process.</p>
  +			<p>I am more than happy to recieve amendments, improvements and so on to these
pages.  I want the information to be as up to date and as accurate as possible so please do
not hesitate to let me know if you find anything wrong.  I would also be really pleased to
receive submissions of more tutorial documentation for C2.  I hope that sections will develop
for areas such as the sitemap, configuration tutorials, development techniques and so on which
will require reasonable effort to develop however I think it would also be good to take up
the suggestion of a FAQ based on some of the common questions that come up on the list.  I
will start this off soon and try and add to it as quickly as possible.</p>
  +			<p>I have written these pages in the xdocs format, thus it would be really useful
if any contributions are in that format (see <link href="http://xml.apache.org/cocoon2/contrib.html">Contributing</link>
for explanation of the diff format and CVS).  If you want to see examples of the markup required
please check the files in the C2 xdocs folder that comes as part of the distribution.  The
DTD is in xdocs/dtd/document-v10.dtd.  I am more than happy to take contributions in email,
MS Word, PDF, TXT etc however any conversion may delay the publishing process.</p>
   			<p>Please email <link href="mailto:ctwig@pigbite.com">ctwig@pigbite.com</link>
with your comments, ideas and submissions.</p>
   			<p>Many thanks - Jez</p>
   		</s1>
   	</body>
  -</document>
  \ No newline at end of file
  +</document>
  
  
  
  1.3       +7 -7      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.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- ctwig-gettingstarted.xml	2001/10/23 07:06:54	1.2
  +++ ctwig-gettingstarted.xml	2001/11/01 04:16:04	1.3
  @@ -1,12 +1,12 @@
  -<?xml version="1.0"?>
  +<?xml version="1.0" encoding="UTF-8"?>
  +<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.0//EN" "dtd/document-v10.dtd">
   
  -<!--
  -<!DOCTYPE document SYSTEM "./dtd/document-v10.dtd">
  --->
  -<?xml-stylesheet href="document2html.xsl" type="text/xsl"?>
   <document>
   	<header>
   		<title>cTwIG - Cocoon Two Idiots Guide - Getting Started</title>
  +		<authors>
  +			<person name="Jeremy Aston" email="jez@pigbite.com"/>
  +		</authors>
   	</header>
   
   	<body>
  @@ -24,7 +24,7 @@
   			</s2>
   
   			<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 Windows machines is 
  +				<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>
   			</s2>
   
  @@ -47,4 +47,4 @@
   			</s2>
   		</s1>
   	</body>
  -</document>
  \ No newline at end of file
  +</document>
  
  
  
  1.3       +12 -16    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.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- ctwig-installing.xml	2001/10/23 07:06:54	1.2
  +++ ctwig-installing.xml	2001/11/01 04:16:04	1.3
  @@ -1,12 +1,12 @@
  -<?xml version="1.0"?>
  +<?xml version="1.0" encoding="UTF-8"?>
  +<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.0//EN" "dtd/document-v10.dtd">
   
  -<!--
  -<!DOCTYPE document SYSTEM "./dtd/document-v10.dtd">
  --->
  -<?xml-stylesheet href="document2html.xsl" type="text/xsl"?>
   <document>
   	<header>
   		<title>cTwIG - Cocoon Two Idiots Guide - Installing</title>
  +		<authors>
  +			<person name="Jeremy Aston" email="jez@pigbite.com"/>
  +		</authors>
   	</header>
   
   	<body>
  @@ -15,26 +15,22 @@
   				<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.  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>.</strong></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>
   			</s2>
   			<s2 title="Download Cocoon 2">
  -				<p>The latest distribution for Windows machines 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.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>
   			</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>
   				<ul>
   					<li>Set JAVA_HOME</li>
   					<li>Create the WAR using
  -						<source><![CDATA[
  -  .\build.bat -Dinclude.webapp.libs=yes webapp
  -						]]></source>
  -						<p>What this does is to create the web application and packaged cocoon.war
under the {COCOON_HOME}/build/cocoon folder.</p>
  +						<code>.\build.bat -Dinclude.webapp.libs=yes webapp</code>
  +						What this does is to create the web application and packaged cocoon.war under the
{COCOON_HOME}/build/cocoon folder.
   					</li>
   					<li>Optionally make the SQL examples work out of the box.  If you perform this
step using
  -						<source><![CDATA[
  -  .\build.bat -Dinclude.webapp.libs=yes 
  -	   -Dinstall.war={{TOMCAT_HOME}\webapps} install]]></source>
  -						<p>then it will basically copy the cocoon.war file across to the Tomcat webapps
folder ready for immediate use.</p>
  +						<code>.\build.bat -Dinclude.webapp.libs=yes -Dinstall.war={{TOMCAT_HOME}\webapps}
install</code>
  +						then it will basically copy the cocoon.war file across to the Tomcat webapps folder
ready for immediate use.
   					</li>
   					<li>Add any additional components (I like FOP for example)</li>
   				</ul>
  @@ -72,4 +68,4 @@
   			</s2>
   		</s1>
   	</body>
  -</document>
  \ No newline at end of file
  +</document>
  
  
  
  1.3       +10 -10    xml-cocoon2/documentation/xdocs/ctwig/ctwig-resources.xml
  
  Index: ctwig-resources.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon2/documentation/xdocs/ctwig/ctwig-resources.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- ctwig-resources.xml	2001/10/23 07:06:54	1.2
  +++ ctwig-resources.xml	2001/11/01 04:16:04	1.3
  @@ -1,20 +1,20 @@
  -<?xml version="1.0"?>
  +<?xml version="1.0" encoding="UTF-8"?>
  +<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.0//EN" "dtd/document-v10.dtd">
   
  -<!--
  -<!DOCTYPE document SYSTEM "./dtd/document-v10.dtd">
  --->
  -<?xml-stylesheet href="document2html.xsl" type="text/xsl"?>
   <document>
   	<header>
   		<title>cTwIG - Cocoon Two Idiots Guide - Resources</title>
  +		<authors>
  +			<person name="Jeremy Aston" email="jez@pigbite.com"/>
  +		</authors>
   	</header>
   
   	<body>
   		<s1 title="Resources">
   			<s2 title="Apache Cocoon 2 Web Site">
  -				<p>The main place is <a href="http://xml.apache.org/cocoon2/index.html">here</a>!!</p>
  -				<p>Granted, the C2 documentation is still in Alpha, but there is alot there and
it goes into alot 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/index.html.</p>
  +				<p>The main place is <link href="http://xml.apache.org/cocoon2/"><code>http://xml.apache.org/cocoon2/</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>
   			</s2>
   			<s2 title="Apache Cocoon Users Mail List">
   				<p><link href="mailto:cocoon-users-subscribe@xml.apache.org">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/cocoon2/mail-lists.html">documentation</fork>.</p>
  @@ -22,7 +22,7 @@
   			</s2>
   			<s2 title="Other Pages">
   				<ul>
  -					<li>David Parry has put together a really good <fork href="http://www.suranyami.com/XSPtutorial/index.html">XSP
Tutorial</fork> which is C1.8 based but has all the basic principles you need for C2.</li>
  +					<li>David Parry has put together a really good <fork href="http://www.suranyami.com/XSPtutorial/">XSP
Tutorial</fork> which is C1.8 based but has all the basic principles you need for C2.</li>
   					<li>Michael Bierenfeld directed me to a cocoon-users <fork href="http://mailman.real-time.com/pipermail/cocoon-users/2001-June/016150.html">posting</fork>
that has an example taglib (logicsheet) download.  Thanks to Gary Clark for the posting and
example.</li>
   					<li><link href="mailto:ccambien@ivision.fr">Cyril Cambien</link>
has developed more examples at his <fork href="http://chello.sourceforge.net/">CHello!</fork>
(Cocoon Hello!) site.</li>
   					<li><link href="mailto:lmocz@galatea.com">Lajos Moczar</link> has
developed some more advanced hints and tips at his <fork href="http://www.galatea.com/flashguides/cocoon-tips-2.xml">flashguides</fork>
site.</li>
  @@ -33,4 +33,4 @@
   			</s2>
   		</s1>
   	</body>
  -</document>
  \ No newline at end of file
  +</document>
  
  
  
  1.3       +7 -7      xml-cocoon2/documentation/xdocs/ctwig/ctwig-transformations.xml
  
  Index: ctwig-transformations.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon2/documentation/xdocs/ctwig/ctwig-transformations.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- ctwig-transformations.xml	2001/10/23 07:06:54	1.2
  +++ ctwig-transformations.xml	2001/11/01 04:16:04	1.3
  @@ -1,12 +1,12 @@
  -<?xml version="1.0"?>
  +<?xml version="1.0" encoding="UTF-8"?>
  +<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.0//EN" "dtd/document-v10.dtd">
   
  -<!--
  -<!DOCTYPE document SYSTEM "./dtd/document-v10.dtd">
  --->
  -<?xml-stylesheet href="document2html.xsl" type="text/xsl"?>
   <document>
   	<header>
   		<title>cTwIG - Cocoon Two Idiots Guide - Transformations</title>
  +		<authors>
  +			<person name="Jeremy Aston" email="jez@pigbite.com"/>
  +		</authors>
   	</header>
   
   	<body>
  @@ -19,7 +19,7 @@
   			</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>
  -				<p><em>Please note that, unless otherwise indicated, all my examples assume
that the files are in a folder called <b>ctwig</b> underneath {TOMCAT_HOME}/webapps/cocoon.</em></p>
  +				<p><em>Please note that, unless otherwise indicated, all my examples assume
that the files are in a folder called</em> <strong><code>ctwig</code></strong>
<em>underneath</em> <code>{TOMCAT_HOME}/webapps/cocoon/</code></p>
   				<ul>
   					<li><link href="ctwig-basic01.html">Basic XML/XSL Transformation (Ref:
BASIC01)</link></li>
   					<li><link href="ctwig-basic02.html">Basic XSP Processing (Ref: BASIC02)</link></li>
  @@ -29,4 +29,4 @@
   			</s2>
   		</s1>
   	</body>
  -</document>
  \ No newline at end of file
  +</document>
  
  
  
  1.3       +6 -6      xml-cocoon2/documentation/xdocs/ctwig/ctwig-why.xml
  
  Index: ctwig-why.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon2/documentation/xdocs/ctwig/ctwig-why.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- ctwig-why.xml	2001/10/23 07:06:54	1.2
  +++ ctwig-why.xml	2001/11/01 04:16:04	1.3
  @@ -1,12 +1,12 @@
  -<?xml version="1.0"?>
  +<?xml version="1.0" encoding="UTF-8"?>
  +<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.0//EN" "dtd/document-v10.dtd">
   
  -<!--
  -<!DOCTYPE document SYSTEM "./dtd/document-v10.dtd">
  --->
  -<?xml-stylesheet href="document2html.xsl" type="text/xsl"?>
   <document>
   	<header>
   		<title>cTwIG - Cocoon Two Idiots Guide - Why?</title>
  +		<authors>
  +			<person name="Jeremy Aston" email="jez@pigbite.com"/>
  +		</authors>
   	</header>
   
   	<body>
  @@ -19,4 +19,4 @@
   			<p>I am now trying to build some prototype code and realising that sharing my
experiences might help others.  At worst it'll be how not to do it!</p>
   		</s1>
   	</body>
  -</document>
  \ No newline at end of file
  +</document>
  
  
  

----------------------------------------------------------------------
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


Mime
View raw message