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/07/19 15:46:59 UTC
cvs commit: xml-cocoon2/xdocs actions.xml avalon.xml caching.xml cinclude-transformer.xml contrib.xml datasources.xml directory-generator.xml docs-book.xml emotional-landscapes.xml esql.xml extending.xml extractor-generator.xml extractor-transformer.xml faq.xml file-generator.xml filter-transformer.xml generators.xml hosting.xml html-generator.xml html-serializer.xml httprequest.xml i18n-transformer.xml imagedirectory-generator.xml index.xml installing.xml jars.xml jsp-generator.xml
cziegeler 01/07/19 06:46:59
Modified: xdocs Tag: cocoon_20_branch actions.xml avalon.xml
caching.xml cinclude-transformer.xml contrib.xml
datasources.xml directory-generator.xml
docs-book.xml emotional-landscapes.xml esql.xml
extending.xml extractor-generator.xml
extractor-transformer.xml faq.xml
file-generator.xml filter-transformer.xml
generators.xml hosting.xml html-generator.xml
html-serializer.xml httprequest.xml
i18n-transformer.xml imagedirectory-generator.xml
index.xml installing.xml jars.xml jsp-generator.xml
Log:
Updated docs from a-j to use the new tags
Revision Changes Path
No revision
No revision
1.2.2.4 +5 -5 xml-cocoon2/xdocs/actions.xml
Index: actions.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/actions.xml,v
retrieving revision 1.2.2.3
retrieving revision 1.2.2.4
diff -u -r1.2.2.3 -r1.2.2.4
--- actions.xml 2001/07/18 11:11:53 1.2.2.3
+++ actions.xml 2001/07/19 13:46:58 1.2.2.4
@@ -2,7 +2,7 @@
<!DOCTYPE document SYSTEM "dtd/document-v10.dtd">
<document>
<header>
- <title>Creating and Using Actions in Cocoon 2</title>
+ <title>Creating and Using Actions in @doctitle@</title>
<version>0.3</version>
<type>Overview document</type>
<authors>
@@ -14,10 +14,10 @@
<body>
<s1 title="What is an Action?">
<p>
- Cocoon has a rich set of tools for publishing web documents, and while
+ @docname@ has a rich set of tools for publishing web documents, and while
XSP and Generators provide alot of functionality, they still mix content
and logic to a certain degree. The Action was created to fill that gap.
- Because the Cocoon 2 Sitemap provides a mechanism to select the pipeline
+ Because the @docname@ Sitemap provides a mechanism to select the pipeline
at run time, we surmised that sometimes we need to adjust the pipeline
based on runtime parameters, or even the contents of the Request parameter.
Without the use of Actions this would make the sitemap almost
@@ -36,7 +36,7 @@
<s2 title="When to use an Action instead of XSP">
<p>
Sometimes it is going to be quicker for you to create and handle
- logic in XSP, because Cocoon recognizes if there have been any
+ logic in XSP, because @docname@ recognizes if there have been any
changes. However, many times it is more desirable to have a separation
between the logic and the display. For instance, we will use a
multipage form. In XSP the logic to handle the results for one
@@ -101,7 +101,7 @@
<p>
There is nothing like a little sample code to get your feet wet.
We are performing something very simple here, but you can get
- more complex examples from the Cocoon code-base.
+ more complex examples from the @docname@ code-base.
</p>
<source>
<![CDATA[
1.1.1.1.2.2 +9 -9 xml-cocoon2/xdocs/avalon.xml
Index: avalon.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/avalon.xml,v
retrieving revision 1.1.1.1.2.1
retrieving revision 1.1.1.1.2.2
diff -u -r1.1.1.1.2.1 -r1.1.1.1.2.2
--- avalon.xml 2001/07/03 07:49:34 1.1.1.1.2.1
+++ avalon.xml 2001/07/19 13:46:58 1.1.1.1.2.2
@@ -3,7 +3,7 @@
<document>
<header>
<title>Avalon</title>
- <subtitle>for Cocoon 2</subtitle>
+ <subtitle>for @doctitle@</subtitle>
<version>0.2</version>
<type>Technical document</type>
<authors>
@@ -12,20 +12,20 @@
<person name="Carsten Ziegeler" email="cziegeler@apache.org"/>
</authors>
<abstract>This document tries to give the basic knowledge of Avalon that is
- necessary to understand Apache Cocoon 2.</abstract>
+ necessary to understand @docname@.</abstract>
</header>
<body>
<s1 title="Goal">
<p>This document tries to give the basic knowledge of Avalon that is
- necessary to understand Apache Cocoon 2.</p>
+ necessary to understand @docname@.</p>
<p>People that are trying to understand Avalon in depth, will probably
- not be much helped by this document. But if you want to understand Cocoon 2,
+ not be much helped by this document. But if you want to understand @docname@,
you have to have a basic grasp of Avalon. </p>
<p>The document also contains the basic configuration steps for
- configuring Avalon components within Cocoon 2.</p>
+ configuring Avalon components within @docname@.</p>
<p>Much of this document is copied and pasted from original Avalon
documentation. However, I hope that the fact that all things relevant for
- Cocoon 2 are put together in one place, will help you to understand Cocoon 2
+ @docname@ are put together in one place, will help you to understand @docname@
faster.</p>
<p>For people wishing to learn Avalon in-depth,
<link href="http://jakarta.apache.org/avalon/index.html">this is your starting
@@ -44,7 +44,7 @@
</ul>
</s1>
<s1 title="The classes and interfaces">
- <p>These classes and interfaces are extensively used by Cocoon 2:</p>
+ <p>These classes and interfaces are extensively used by @docname@:</p>
<s2 title="ComponentManager">
<p><code>org.apache.avalon.framework.component.ComponentManager</code></p>
<p>A <code>ComponentManager</code> selects <code>Component</code>s
@@ -76,7 +76,7 @@
<code>Composer</code>. The <code>Composer</code> must know what type of
<code>Component</code> it is accessing, so it will re-cast the
<code>Component</code> into the type it needs. </p>
- <p><code>Component</code>s in Cocoon 2 are e.g. those defined in
+ <p><code>Component</code>s in @docname@ are e.g. those defined in
<code>cocoon.xconf</code>.</p>
</s2>
<s2 title="Configuration">
@@ -106,7 +106,7 @@
<p>Avalon now incorporates a couple of modifiers for a Component
definition that allows you to control the number of Components
in a pool, and how quickly it grows. This is especially helpful
- in Cocoon 2 where the defaults don't always work well.</p>
+ in @docname@ where the defaults don't always work well.</p>
<p>The magic attributes are "pool-min", "pool-max", and "pool-grow".
The defaults are:</p>
<ol>
1.1.2.9 +8 -8 xml-cocoon2/xdocs/caching.xml
Index: caching.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/caching.xml,v
retrieving revision 1.1.2.8
retrieving revision 1.1.2.9
diff -u -r1.1.2.8 -r1.1.2.9
--- caching.xml 2001/07/18 11:11:53 1.1.2.8
+++ caching.xml 2001/07/19 13:46:58 1.1.2.9
@@ -3,21 +3,21 @@
<document>
<header>
<title>Caching</title>
- <subtitle>in Cocoon 2</subtitle>
+ <subtitle>in @doctitle@</subtitle>
<version>0.9</version>
<type>Technical document</type>
<authors><person name="Carsten Ziegeler" email="cziegeler@apache.org"/>
</authors>
- <abstract>This document explains the basic caching algorithm of Cocoon 2.</abstract>
+ <abstract>This document explains the basic caching algorithm of @docname@.</abstract>
</header>
<body>
<s1 title="Goal">
- <p>This document explains the basic caching algorithm of Cocoon 2.</p>
+ <p>This document explains the basic caching algorithm of @docname@.</p>
</s1>
<s1 title="Overview">
- <p>The caching algorithm of Cocoon 2 has a very flexible and powerful design.
+ <p>The caching algorithm of @docname@ has a very flexible and powerful design.
The used algorithms and components are not hardcoded into the core of
- Cocoon 2. They can be configured using Avalon components.</p>
+ @docname@. They can be configured using Avalon components.</p>
<p>This document describes the available components for caching,
how they can be configured and how to implement own cacheable components.
</p>
@@ -174,9 +174,9 @@
</s2>
</s1>
<s1 title="Configuration">
- <p>The caching of Cocoon 2 can be completely configured by different Avalon
+ <p>The caching of @docname@ can be completely configured by different Avalon
components. This chapter describes which roles must/can be changed
- to tune up your Cocoon 2 system.</p>
+ to tune up your @docname@ system.</p>
<s2 title="The Stream and the Event Pipeline">
<p>The stream and the event pipeline are represented by two Avalon
components which can be configured in the cocoon.xconf:</p>
@@ -226,7 +226,7 @@
</s1>
<s1 title="Java APIs">
<p>For more information on the java apis refer directly to the
- javadocs of Cocoon2.</p>
+ javadocs of @docname@.</p>
<p>The most important packages are:</p>
<ol>
<li><code>org.apache.cocoon.caching</code>: This package declares all interfaces for caching.</li>
1.1.2.3 +2 -2 xml-cocoon2/xdocs/cinclude-transformer.xml
Index: cinclude-transformer.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/cinclude-transformer.xml,v
retrieving revision 1.1.2.2
retrieving revision 1.1.2.3
diff -u -r1.1.2.2 -r1.1.2.3
--- cinclude-transformer.xml 2001/07/17 14:44:44 1.1.2.2
+++ cinclude-transformer.xml 2001/07/19 13:46:58 1.1.2.3
@@ -3,13 +3,13 @@
<document>
<header>
<title>CInclude Transformer</title>
- <subtitle>in Cocoon 2</subtitle>
+ <subtitle>in @doctitle@</subtitle>
<version>0.9</version>
<type>Technical document</type>
<authors>
<person name="Carsten Ziegeler" email="cziegeler@apache.org"/>
</authors>
- <abstract>This document describes the CInclude transformer of Cocoon 2.</abstract>
+ <abstract>This document describes the CInclude transformer of @docname@.</abstract>
</header>
<body>
<s1 title="CInclude Transformer">
1.1.2.3 +23 -23 xml-cocoon2/xdocs/contrib.xml
Index: contrib.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/contrib.xml,v
retrieving revision 1.1.2.2
retrieving revision 1.1.2.3
diff -u -r1.1.2.2 -r1.1.2.3
--- contrib.xml 2001/07/18 11:11:53 1.1.2.2
+++ contrib.xml 2001/07/19 13:46:58 1.1.2.3
@@ -4,7 +4,7 @@
<document>
<header>
- <title>Contribution to Apache Cocoon</title>
+ <title>Contribution to @doctitle@</title>
<authors>
<person name="Robin Green" email="greenrd@hotmail.com"/>
<person name="Stefano Mazzocchi" email="stefano@apache.org"/>
@@ -16,7 +16,7 @@
<s1 title="Introduction">
<p>
- The Cocoon Project is an <link href="http://www.opensource.org/">Open Source</link>
+ The @docname@ Project is an <link href="http://www.opensource.org/">Open Source</link>
volunteer project under the auspices of the
<link href="http://www.apache.org/">Apache Software Foundation (ASF)</link>,
and, in harmony with the Apache webserver itself, it is released under
@@ -29,7 +29,7 @@
</p>
<p>
To begin with, we suggest you to subscribe to the
- <connect href="mail-lists.xml">Cocoon mailing lists</connect>
+ <connect href="mail-lists.xml">@docname@ mailing lists</connect>
(follow the link for information on how to subscribe and to access the mail
list archives), to checkout the <link href="http://xml.apache.org/websrc/index.cgi/xml-cocoon2/">
latest and greatest code</link> (which you find in the xml-cocoon2 module in
@@ -41,7 +41,7 @@
we have work for you!
</p>
<p>
- For financial support in particular, the Cocoon Project and the ASF in general
+ For financial support in particular, the @docname@ Project and the ASF in general
is closely collaborating with the <link href="http://www.sourcexchange.com">Collab.net
SourceXchange</link> program that will provide a legal, solid and
well-established resource for money collecting to fund software production
@@ -62,46 +62,46 @@
<ul>
<li>Answering questions on the <code>cocoon-users</code> mailing list - there is often a problem of
having too many questioners and not enough experts to respond to all the questions.</li>
- <li>Testing Cocoon (especially its less-frequently-used features) on various configurations
+ <li>Testing @docname@ (especially its less-frequently-used features) on various configurations
and reporting back.</li>
<li>Debugging - producing reproduceable test cases and/or finding causes of bugs (at the time of
writing, some known bugs are informally listed on <connect href="todo.xml">To Do</connect>, but
eventually a bug database should be made available on the Apache site).</li>
- <li>Specifying/analysing/designing new features for Cocoon 2 - and beyond. (If you wish to get involved
+ <li>Specifying/analysing/designing new features for @docname@ - and beyond. (If you wish to get involved
with this, please join <code>cocoon-dev@xml.apache.org</code>
- (you may also want to join <code>xsp-dev@xml.apache.org</code>), install and try out Cocoon 2
+ (you may also want to join <code>xsp-dev@xml.apache.org</code>), install and try out @doctitle@
and read some of the <link href="http://mail-archives.apache.org/">mail archives</link>.
You should have a strong "fluency" in XML technologies, Java and a basic understanding of
- the Cocoon 2 architecture - don't just say "it should have XYZ" without reading anything first -
+ the @doctitle@ architecture - don't just say "it should have XYZ" without reading anything first -
because chances are, someone's already thought of that feature!)</li>
<li>Packaging easy-to-install packages (such as RPMs) for the myriad of possible configurations out
- there. (The Cocoon project does not maintain anything but the basic <code>.zip</code> and
+ there. (The @docname@ project does not maintain anything but the basic <code>.zip</code> and
<code>.tar.gz</code> packages, but anyone is welcome to build their own specific packages and
announce them on <code>cocoon-users</code>)</li>
- <li>... and there is just one other thing - don't forget to tell everyone who asks how great Cocoon is! ;-)
- The more people that know about and start to use Cocoon, the larger the pool of
+ <li>... and there is just one other thing - don't forget to tell everyone who asks how great @doctitle@ is! ;-)
+ The more people that know about and start to use @docname@, the larger the pool of
potential contributors there will be
- - so, please, help us by placing the cocoon logo somewhere in your
- site to indicate that you are using and supporting the Cocoon Project.
+ - so, please, help us by placing the @docname@ logo somewhere in your
+ site to indicate that you are using and supporting the @docname@ Project.
</li>
</ul>
<p>
- Thank you very much. <img src="images/cocoon2-small.jpg" alt="Powered by Cocoon"/>
+ Thank you very much. <img src="images/cocoon2-small.jpg" alt="Powered by @docname@"/>
</p>
</s1>
<s1 title="Contributions of Code and Documentation">
- <p>We are starting to use an informal system for accepting contributions to Cocoon.
+ <p>We are starting to use an informal system for accepting contributions to @docname@.
The process varies depending on whether the contribution is a modification (i.e. patch)
or a fairly standalone item, and whether you have commit access (committers have been
granted access by a vote of confidence, so they are assumed to be trustworthy enough
to make changes directly in CVS. If you submit many good patches, you may be
nominated as a committer yourself!)</p>
- <p>If your contribution requires changing more than a few lines of Cocoon (code or
+ <p>If your contribution requires changing more than a few lines of @docname@ (code or
documentation), then it counts as a <strong>patch</strong>. If you have a patch and
- would like to see it incorporated into the Cocoon distribution, take note of the Licensing
+ would like to see it incorporated into the @docname@ distribution, take note of the Licensing
Requirements listed below, and then read the <connect href="patches.xml">Patch management
</connect> page for more information.
</p>
@@ -127,10 +127,10 @@
specified below. See also Licensing Requirements below.]</li>
<li>Inclusion into the main distribution. [Committers must be confident that it should work properly in
most/all environments, it must be documented as appropriate, and it must be considered sufficiently
- useful and general to go into Cocoon. See also Licensing Requirements below].</li>
+ useful and general to go into @docname@. See also Licensing Requirements below].</li>
</ol>
- <s2 title="Testing Requirements for Cocoon Contrib and Distribution">
+ <s2 title="Testing Requirements for @docname@ Contrib and Distribution">
<p>All new code should be tested under the following servlet engines:</p>
<ul>
<li>Apache Tomcat 3.2.2</li>
@@ -143,7 +143,7 @@
<li>A UNIX-type operating system</li>
<li>A JDK version 1.1.x</li>
</ul>
- <p>And obviously, it should be tested against the current CVS snapshot of Cocoon!</p>
+ <p>And obviously, it should be tested against the current CVS snapshot of @docname@!</p>
<p>This testing is designed to iron out the most common kinds of incompatibility
problems (Servlet >2.0 requirements; platform-dependent assumptions; JDK >1.1 code).
@@ -153,7 +153,7 @@
than thorough testing!</p>
</s2>
- <s2 title="Documentation Requirements for Cocoon Distribution">
+ <s2 title="Documentation Requirements for @docname@ Distribution">
<p>All new features (processor, logicsheets, config options etc.) should be documented
appropriately (in XML or in cocoon.properties in the case of config options).</p>
@@ -164,7 +164,7 @@
</p>
</s2>
- <s2 title="Licensing Requirements for the Cocoon Distribution">
+ <s2 title="Licensing Requirements for the @docname@ Distribution">
<p>To avoid legal problems, the Apache Project Management Committee (PMC) have agreed on
a policy for under what licensing code can be accepted into Apache projects:</p>
<ul>
@@ -179,7 +179,7 @@
we do not have the resources nor the inclination to obtain signed statements from all
contributors!</p>
- <p><strong>Note:</strong> Since the <code>contrib/</code> directory of Cocoon CVS contains
+ <p><strong>Note:</strong> Since the <code>contrib/</code> directory of @docname@ CVS contains
third-party. completely optional extensions, one of the above requirements is relaxed.
Code in the contrib directory does not have to have its copyright assigned to the ASF
- but it must still be released under the Apache license.</p>
1.1.1.1.2.2 +9 -9 xml-cocoon2/xdocs/datasources.xml
Index: datasources.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/datasources.xml,v
retrieving revision 1.1.1.1.2.1
retrieving revision 1.1.1.1.2.2
diff -u -r1.1.1.1.2.1 -r1.1.1.1.2.2
--- datasources.xml 2001/07/18 11:11:53 1.1.1.1.2.1
+++ datasources.xml 2001/07/19 13:46:58 1.1.1.1.2.2
@@ -2,7 +2,7 @@
<!DOCTYPE document SYSTEM "dtd/document-v10.dtd">
<document>
<header>
- <title>Using Databases in Cocoon 2</title>
+ <title>Using Databases in @doctitle@</title>
<version>0.3</version>
<type>Overview document</type>
<authors><person name="Berin Loritsch" email="bloritsch@apache.org"/>
@@ -11,7 +11,7 @@
<body>
<s1 title="How do I choose my database?">
<p>
- Cocoon is flexible in the way it allows you to make connections to
+ @docname@ is flexible in the way it allows you to make connections to
a database. There are basically two ways: by redefining all the connection
parameters in each page you use a database, or using a pooled connection.
The first method is slow and doesn't scale well. The second method is more
@@ -20,7 +20,7 @@
<s2 title="Installing the Driver">
<p>
Independent of how you choose to get and maintain your JDBC connections,
- you have to load the driver so Cocoon can use it (unless you are using
+ you have to load the driver so @docname@ can use it (unless you are using
a J2EE container--more on that later). This is an init parameter in
your web.xml file. The following snippet will show you how:
</p>
@@ -45,13 +45,13 @@
</s2>
<s2 title="Defining a Data Source">
<p>
- Cocoon allows you to specify a pooled data source that you can use
- for throughout the Cocoon system. There are two different types of
+ @docname@ allows you to specify a pooled data source that you can use
+ for throughout the @docname@ system. There are two different types of
data sources: JDBC and J2EE. The difference is in who controls the
- connection. The JDBC data source lets Cocoon handle all the pooling
- logic. The J2EE data source tells Cocoon how to pull the DataSource
+ connection. The JDBC data source lets @docname@ handle all the pooling
+ logic. The J2EE data source tells @docname@ how to pull the DataSource
object from a J2EE container (thats Java 2 Enterprise Edition)--the
- major caveat is that Cocoon must be installed as part of a Enterprise
+ major caveat is that @docname@ must be installed as part of a Enterprise
Application.
</p>
<p>
@@ -134,7 +134,7 @@
<s3 title="The J2EE Connection Property">
<p>
The J2EE connection has only one property and it is absolutely
- required. Cocoon uses JNDI to look up the DataSource with the
+ required. @docname@ uses JNDI to look up the DataSource with the
name you specified in "dbname".
</p>
</s3>
1.1.2.5 +2 -2 xml-cocoon2/xdocs/directory-generator.xml
Index: directory-generator.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/directory-generator.xml,v
retrieving revision 1.1.2.4
retrieving revision 1.1.2.5
diff -u -r1.1.2.4 -r1.1.2.5
--- directory-generator.xml 2001/07/18 11:11:53 1.1.2.4
+++ directory-generator.xml 2001/07/19 13:46:58 1.1.2.5
@@ -3,13 +3,13 @@
<document>
<header>
<title>Directory Generator</title>
- <subtitle>in Cocoon 2</subtitle>
+ <subtitle>in @doctitle@</subtitle>
<version>0.9</version>
<type>Technical document</type>
<authors>
<person name="Carsten Ziegeler" email="cziegeler@apache.org"/>
</authors>
- <abstract>This document describes the directory generator of Cocoon 2.</abstract>
+ <abstract>This document describes the directory generator of @docname@.</abstract>
</header>
<body>
<s1 title="Directory Generator">
1.3.2.15 +2 -2 xml-cocoon2/xdocs/docs-book.xml
Index: docs-book.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/docs-book.xml,v
retrieving revision 1.3.2.14
retrieving revision 1.3.2.15
diff -u -r1.3.2.14 -r1.3.2.15
--- docs-book.xml 2001/07/18 15:37:47 1.3.2.14
+++ docs-book.xml 2001/07/19 13:46:58 1.3.2.15
@@ -1,6 +1,6 @@
<?xml version="1.0"?>
-<book title="Cocoon 2 documentation" copyright="@year@ The Apache Software Foundation">
+<book title="@doctitle@ documentation" copyright="@year@ The Apache Software Foundation">
<separator/>
<page id="index" label="Index" source="index.xml"/>
<page id="license" label="License" source="license.xml"/>
@@ -89,7 +89,7 @@
<todo id="todo" label="Todo" source="todo.xml"/>
<separator/>
<page id="livesites" label="Live Sites" source="livesites.xml"/>
- <page id="hosting" label="Cocoon Hosting" source="hosting.xml"/>
+ <page id="hosting" label="@docname@ Hosting" source="hosting.xml"/>
<separator/>
<external label="Bug Database" href="http://nagoya.apache.org/bugzilla/index.html"/>
<external label="Code Repository" href="http://xml.apache.org/websrc/index.cgi/xml-cocoon2/"/>
1.1.1.1.2.2 +30 -30 xml-cocoon2/xdocs/emotional-landscapes.xml
Index: emotional-landscapes.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/emotional-landscapes.xml,v
retrieving revision 1.1.1.1.2.1
retrieving revision 1.1.1.1.2.2
diff -u -r1.1.1.1.2.1 -r1.1.1.1.2.2
--- emotional-landscapes.xml 2001/07/18 11:11:53 1.1.1.1.2.1
+++ emotional-landscapes.xml 2001/07/19 13:46:58 1.1.1.1.2.2
@@ -5,8 +5,8 @@
<document>
<header>
- <title>Cocoon Emotional Landscapes</title>
- <subtitle>why you can't afford to miss Cocoon</subtitle>
+ <title>@doctitle@ Emotional Landscapes</title>
+ <subtitle>why you can't afford to miss @docname@</subtitle>
<authors>
<person name="Stefano Mazzocchi" email="stefano@apache.org"/>
</authors>
@@ -41,7 +41,7 @@
</p>
<p>
-I'll explain you what the Apache Cocoon project is about and what we are
+I'll explain you what the @docname@ project is about and what we are
doing to solve the problems that we encountered in our web engineering
experiences, but from an executive perspective, yes, because we all had
the problems of managing a web site, dealing with our colleagues, rushing
@@ -331,7 +331,7 @@
</p>
<p>
-Cocoon 1.0 did exactly this.
+@docname@ 1.0 did exactly this.
</p>
</s1>
@@ -341,9 +341,9 @@
<p>
If XML is a lingua franca, it means that XML software can work on almost
anything without caring about what it is. So, if a cell phone requests
-the page, Cocoon just has to change transformation rules and send the
+the page, @docname@ just has to change transformation rules and send the
WAP page to the phone. Or, if you want a nice PDF to printout your
-monthly report, you change the transformation rules and Cocoon creates
+monthly report, you change the transformation rules and @docname@ creates
the PDF for you, or the VRML, or the VoiceML, or your own proprietary
B2B markup.
</p>
@@ -358,14 +358,14 @@
<s1 title="Separation of Concerns (SoC)">
<p>
-Cocoon was not the first product to perform server side XML
+@docname@ was not the first product to perform server side XML
transformations, nor will be the last one (in a few years, these
solutions will be the rule rather than the exception). What is the
-"plus" that the Cocoon project adds?
+"plus" that the @docname@ project adds?
</p>
<p>
-I believe the most important Cocoon feature is SoC-based design.
+I believe the most important @docname@ feature is SoC-based design.
</p>
<p>
@@ -381,15 +381,15 @@
</p>
<p>
-For a web publishing system, the Cocoon project uses what we call the
+For a web publishing system, the @docname@ project uses what we call the
"pyramid of contacts" which outlines four major concern areas and five
contracts between them. Here is the picture:
</p>
-<figure src="images/pyramid-model.gif" alt="The Cocoon 2 Pyramid Model of Contracts"/>
+<figure src="images/pyramid-model.gif" alt="The @doctitle@ Pyramid Model of Contracts"/>
<p>
-Cocoon is "engineered" to provide you a way to isolate these four
+@docname@ is "engineered" to provide you a way to isolate these four
concern areas using just those 5 contracts, removing the contract
between style and logic that has been bugging web site development since
the beginning of the web.
@@ -399,7 +399,7 @@
Why? because programmers and graphic people have very different skills
and work habits... so, instead of creating GUIs to hide the things that
can be harmful (like graphic to programmers or logic to designers),
-Cocoon allows you to separate the things into different files, allowing
+@docname@ allows you to separate the things into different files, allowing
you to "seal" your working groups into separate virtual rooms connected
with the other rooms only by those "pipes" (the contracts), that you
give them from the management area.
@@ -459,17 +459,17 @@
</p>
<p>
-With the Cocoon architecture all this is a couple of line changes away.
+With the @docname@ architecture all this is a couple of line changes away.
</p>
</s1>
- <s1 title="The Cocoon innovations">
+ <s1 title="The @docname@ innovations">
<p>
The technologies defined in the XML model are the base of everything,
but many technologies and solutions were designed specifically for the
-Cocoon project:
+@docname@ project:
</p>
<ul>
@@ -493,8 +493,8 @@
This means that you can implement the tags using your favorite language,
without having to force your programmers to use a specific programming
language. At the time of writing, only the Java programming language is
-implemented (being Cocoon written in Java), but it's easy to picture
-development of other language hooks for XSP once Cocoon receives more
+implemented (being @docname@ written in Java), but it's easy to picture
+development of other language hooks for XSP once @docname@ receives more
attention.
</p>
@@ -594,7 +594,7 @@
<s1 title="The Resource View concept">
<p>
- The third big innovation of the Cocoon project is the notion of
+ The third big innovation of the @docname@ project is the notion of
"resource views". It's kind of an abstract concept so I'd like
to start with an example to explain the problem.
</p>
@@ -654,7 +654,7 @@
</p>
<p>
-The problem is that all other publishing systems except Cocoon "hide"
+The problem is that all other publishing systems except @docname@ "hide"
this information inside the system, there is no standard way to "ask"
for the original RDF-ized semantic content of the requested resource.
</p>
@@ -664,7 +664,7 @@
</p>
<p>
-In Cocoon you can define "views" for each resource or group of
+In @docname@ you can define "views" for each resource or group of
resources: you can ask for the "content" view, or for the "schema" view
(that returns you the structure of the document and the information to
validate it), the "link" view that returns you the pages that are
@@ -677,17 +677,17 @@
</p>
<p>
-Cocoon itself uses the view for its batch mode: it performs as a crawler
+@docname@ itself uses the view for its batch mode: it performs as a crawler
and saves a snapshot of the site on disk, useful for creating offline
documentation or CD-ROM snapshots of dynamic web sites.
</p>
</s1>
- <s1 title="Cocoon present">
+ <s1 title="@docname@ present">
<p>
-The Cocoon project is currently discussing new features such as "content
+The @docname@ project is currently discussing new features such as "content
aggregation" that would simplify the creation of portal-like sites where
content is aggregated from different sources into the same page.
</p>
@@ -697,10 +697,10 @@
</p>
</s1>
- <s1 title="Cocoon future">
+ <s1 title="@docname@ future">
<p>
-In the future, Cocoon will provide local semantic searching capabilities
+In the future, @docname@ will provide local semantic searching capabilities
allowing you to gain immediate advantage of the time invested in
creating highly semantic content for your site.
</p>
@@ -709,7 +709,7 @@
I believe this is the only way to convince people to invest time and
resources into creating a better content model for their local
information. We still don't have any idea on how this will happen or how
-it will work, but I believe the Cocoon project has a major role in the
+it will work, but I believe the @docname@ project has a major role in the
promotion of the next web generation and semantic searching is a big
part of it.
</p>
@@ -719,7 +719,7 @@
</p>
<p>
-A further future goal is to allow Cocoon to exchange semantic indexing
+A further future goal is to allow @docname@ to exchange semantic indexing
information in a Peer2Peer way to create a decentralized semantic search
engine... (even if there are big protocol scalability problems to
solve). Consider this high steam vaporware, but I believe that it will
@@ -735,7 +735,7 @@
<p>
If you reached this far by reading all sections, I was successful in
getting your attention and I think you are able to both understand the
-importance of the Cocoon Project and distinguish most of the marketing
+importance of the @docname@ Project and distinguish most of the marketing
hype that surrounds XML and friends.
</p>
@@ -746,7 +746,7 @@
</p>
<p>
-Cocoon uses XML as a core piece of its framework, but improves the model
+@docname@ uses XML as a core piece of its framework, but improves the model
to give you the tools you need and is designed to be flexible enough to
follow your needs as well as paradigm shifts that will happen in the
future.
1.1.2.4 +1 -1 xml-cocoon2/xdocs/esql.xml
Index: esql.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/esql.xml,v
retrieving revision 1.1.2.3
retrieving revision 1.1.2.4
diff -u -r1.1.2.3 -r1.1.2.4
--- esql.xml 2001/07/18 11:11:53 1.1.2.3
+++ esql.xml 2001/07/19 13:46:58 1.1.2.4
@@ -12,7 +12,7 @@
<p>The ESQL logicsheet is an
XSP logicsheet that performs sql queries and serializes their
-results as XML. This allows you to work with data from a wide variety of different sources when using Cocoon.
+results as XML. This allows you to work with data from a wide variety of different sources when using @docname@.
</p>
<p>It has a number of important advantages over the old (deprecated) SQL logicsheet and SQL processor.
1.1.1.1.2.2 +4 -4 xml-cocoon2/xdocs/extending.xml
Index: extending.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/extending.xml,v
retrieving revision 1.1.1.1.2.1
retrieving revision 1.1.1.1.2.2
diff -u -r1.1.1.1.2.1 -r1.1.1.1.2.2
--- extending.xml 2001/07/18 11:11:53 1.1.1.1.2.1
+++ extending.xml 2001/07/19 13:46:58 1.1.1.1.2.2
@@ -3,7 +3,7 @@
<!DOCTYPE document SYSTEM "dtd/document-v10.dtd">
<document>
<header>
- <title>Extending Cocoon 2</title>
+ <title>Extending @doctitle@</title>
<version>0.1</version>
<type>Technical document</type>
<authors>
@@ -12,7 +12,7 @@
</header>
<body>
<s1 title="Introduction">
- <p>If you want to extend the functionality of Cocoon 2, it may be unclear
+ <p>If you want to extend the functionality of @docname@, it may be unclear
how to achieve your goal. This page tries to indicate when to write what, and
to give an overview of what already exists (so you don't duplicate other's
efforts).</p>
@@ -59,7 +59,7 @@
This one is responsible for making your XSP pages work.</li>
<li>
<code>StatusGenerator</code> - Generates an XML representation of
- the current status of Cocoon. This can be considered "for administration use",
+ the current status of @docname@. This can be considered "for administration use",
i.e. your application probably won't deal with this one.</li>
</ul>
<p>All these classes are in the <code>org.apache.cocoon.generation</code>
@@ -166,7 +166,7 @@
</s1>
<s1 title="About Action">
<p>[FIXME: We have to wait until we can see what is going to happen here. Also, I wonder if this belongs here or should deserve a separate page.]</p>
- <p>The Action part will be used for making Cocoon able to react on form input. This will make Cocoon no longer a simple basis for web publishing, but will make it apt for web interaction as well.</p>
+ <p>The Action part will be used for making @docname@ able to react on form input. This will make @docname@ no longer a simple basis for web publishing, but will make it apt for web interaction as well.</p>
</s1>
<s1 title="About XSP">
<anchor id="xsp"/>
1.1.2.3 +2 -2 xml-cocoon2/xdocs/extractor-generator.xml
Index: extractor-generator.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/extractor-generator.xml,v
retrieving revision 1.1.2.2
retrieving revision 1.1.2.3
diff -u -r1.1.2.2 -r1.1.2.3
--- extractor-generator.xml 2001/07/18 07:42:20 1.1.2.2
+++ extractor-generator.xml 2001/07/19 13:46:58 1.1.2.3
@@ -3,13 +3,13 @@
<document>
<header>
<title>Fragment Extractor Generator</title>
- <subtitle>in Cocoon 2</subtitle>
+ <subtitle>in @doctitle@</subtitle>
<version>0.9</version>
<type>Technical document</type>
<authors>
<person name="Carsten Ziegeler" email="cziegeler@apache.org"/>
</authors>
- <abstract>This document describes the fragment extractor generator of Cocoon 2.</abstract>
+ <abstract>This document describes the fragment extractor generator of @docname@</abstract>
</header>
<body>
<s1 title="Fragment Extractor Generator">
1.1.2.3 +2 -2 xml-cocoon2/xdocs/extractor-transformer.xml
Index: extractor-transformer.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/extractor-transformer.xml,v
retrieving revision 1.1.2.2
retrieving revision 1.1.2.3
diff -u -r1.1.2.2 -r1.1.2.3
--- extractor-transformer.xml 2001/07/18 07:42:20 1.1.2.2
+++ extractor-transformer.xml 2001/07/19 13:46:58 1.1.2.3
@@ -3,13 +3,13 @@
<document>
<header>
<title>Fragment Extractor Transformer</title>
- <subtitle>in Cocoon 2</subtitle>
+ <subtitle>in @doctitle@</subtitle>
<version>0.9</version>
<type>Technical document</type>
<authors>
<person name="Carsten Ziegeler" email="cziegeler@apache.org"/>
</authors>
- <abstract>This document describes the Fragment Extractor transformer of Cocoon 2.</abstract>
+ <abstract>This document describes the Fragment Extractor transformer of @docname@.</abstract>
</header>
<body>
<s1 title="Fragment Extractor Transformer">
1.1.1.1.2.8 +23 -23 xml-cocoon2/xdocs/faq.xml
Index: faq.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/faq.xml,v
retrieving revision 1.1.1.1.2.7
retrieving revision 1.1.1.1.2.8
diff -u -r1.1.1.1.2.7 -r1.1.1.1.2.8
--- faq.xml 2001/07/19 10:46:06 1.1.1.1.2.7
+++ faq.xml 2001/07/19 13:46:58 1.1.1.1.2.8
@@ -30,11 +30,11 @@
</faq>
<faq>
<question>
- Why does Cocoon take so long to start?
+ Why does @docname@ take so long to start?
</question>
<answer>
<p>
- Cocoon compiles sitemaps into java classes to increase runtime performance,
+ @docname@ compiles sitemaps into java classes to increase runtime performance,
this is done only at startup and only if the sitemap file is modified, for
all the other requests the compiled sitemap is executed. See question #7
for information on how to pre-compile the sitemap and the XSP's.
@@ -61,7 +61,7 @@
</question>
<answer>
<p>
- Cocoon requires a JAXP 1.1 compliant parser. Recent servlet engines
+ @docname@ requires a JAXP 1.1 compliant parser. Recent servlet engines
(like Tomcat 3.2.1) use older xml parsers. You have to replace the xml
parser with a newer one (e.g. the Xerces 1.3.0).
</p>
@@ -79,15 +79,15 @@
</question>
<answer>
<p>
- Contact the Cocoon Users mail list (cocoon-users@xml.apache.org).
+ Contact the @docname@ Users mail list (cocoon-users@xml.apache.org).
Please, do not contact developers directly for help since the user list are
normally much more responsive and users normally have more experience in
solving installation problems than developers do.
</p>
<p>
- Cocoon has a log file that is stored in the context where you placed
- Cocoon. It is located in '{cocoon}/WEB-INF/logs/cocoon/log' where
- {cocoon} is the context where Cocoon is installed. Many times, the
+ @docname@ has a log file that is stored in the context where you placed
+ @docname@. It is located in '{cocoon}/WEB-INF/logs/cocoon/log' where
+ {cocoon} is the context where @docname@ is installed. Many times, the
information contained in that file will help others help you.
</p>
</answer>
@@ -127,7 +127,7 @@
</faq>
<faq>
<question>
- Cocoon won't start and I get a "java.lang.NoSuchMethodError: org.apache.log.LogKit: method
+ @docname@ won't start and I get a "java.lang.NoSuchMethodError: org.apache.log.LogKit: method
createLogger(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)Lorg/apache/log/Logger;
not found" in my Servlet Container's log.
</question>
@@ -137,21 +137,21 @@
distribution.
</p>
<p>
- Even better, if you build Cocoon with "build -Dinclude.webapp.libs webapp" then
- Cocoon will create a complete WAR file for you with all necessary libraries.
+ Even better, if you build @docname@ with "build -Dinclude.webapp.libs webapp" then
+ @docname@ will create a complete WAR file for you with all necessary libraries.
</p>
</answer>
</faq>
<faq>
<question>
- Cocoon still won't start, this time I get
+ @docname@ still won't start, this time I get
javax.xml.transform.TransformerConfigurationException: Namespace not supported by SAXParser
- in the Cocoon log file.
+ in the @docname@ log file.
</question>
<answer>
<p>
This is a classloader issue with Tomcat and some other Servlet Engines. Basically
- it means that the Xerces library included with Cocoon is not being found. The solution
+ it means that the Xerces library included with @docname@ is not being found. The solution
is to place the Xerces library first in the classpath.
</p>
</answer>
@@ -272,7 +272,7 @@
<question>I want to use the XXX matcher/serializer/selecter/etc but there's no
examples :(</question>
<answer>
- <p>If you've checked the sample webapps which come with Cocoon, and you've
+ <p>If you've checked the sample webapps which come with @docname@, and you've
looked in the documentation (which does exist!) check both the user and
dev archives. If it hasn't been resolved before <strong>first</strong>
email the user group and, after a <strong>reasonable</strong> (ie 1 or 2
@@ -326,22 +326,22 @@
</answer>
</faq>
<faq>
- <question>How could I have my Cocoon app in an URI other than
+ <question>How could I have my @docname@app in an URI other than
<you-server>/cocoon/<my-app>?
</question>
<answer>
- <note> This entry refers only to an Apache + Tomcat + Cocoon configuration,
- and was tested under: Windows NT 4.0 + Apache 1.3.14 + Tomcat 3.2 + Cocoon
+ <note> This entry refers only to an Apache + Tomcat + @docname@ configuration,
+ and was tested under: Windows NT 4.0 + Apache 1.3.14 + Tomcat 3.2 + @docname@
2.0b1.
</note>
<p>Test whether Tomcat passes everything under the /cocoon context to
- Cocoon. This may be tested by pointing your browser at
+ @docname@. This may be tested by pointing your browser at
<your-server>:8080/cocoon/xsp/simple, if a text page named
"A simple XSP page", everything's fine.
</p>
<p>Now, suppose:</p>
<ol>
- <li>you have a Cocoon application named "foo" which works fine when
+ <li>you have a @docname@ application named "foo" which works fine when
called with <your-server>:8080/cocoon/foo
</li>
<li>you want the "foo" app to be called from
@@ -393,12 +393,12 @@
</answer>
</faq>
<faq>
- <question>How could I have my Cocoon app in a directory other than
+ <question>How could I have my @docname@ app in a directory other than
$TOMCAT_HOME/webapps/cocoon/<my-app>?
</question>
<answer>
- <note>This entry refers only to an Apache + Tomcat + Cocoon configuration,
- and was tested under: Windows NT 4.0 + Apache 1.3.14 + Tomcat 3.2 + Cocoon
+ <note>This entry refers only to an Apache + Tomcat + @docname@ configuration,
+ and was tested under: Windows NT 4.0 + Apache 1.3.14 + Tomcat 3.2 + @docname@
2.0b1.
</note>
<p>Let's suppose the following:</p>
@@ -422,7 +422,7 @@
</map:pipeline>
]]>
</source>
- <p>The "file:" type of source forces Cocoon to search the sub-sitemap under
+ <p>The "file:" type of source forces @docname@ to search the sub-sitemap under
the specified directory (which happens to be "c:\foo", since this is a
Windows system).
</p>
1.1.2.2 +2 -3 xml-cocoon2/xdocs/file-generator.xml
Index: file-generator.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/file-generator.xml,v
retrieving revision 1.1.2.1
retrieving revision 1.1.2.2
diff -u -r1.1.2.1 -r1.1.2.2
--- file-generator.xml 2001/07/12 21:06:08 1.1.2.1
+++ file-generator.xml 2001/07/19 13:46:58 1.1.2.2
@@ -2,14 +2,13 @@
<!DOCTYPE document SYSTEM "dtd/document-v10.dtd">
<document>
<header>
- <title>File Generator</title>
- <subtitle>in Cocoon 2</subtitle>
+ <title>File Generator in @doctitle@</title>
<version>0.9</version>
<type>Technical document</type>
<authors>
<person name="Carsten Ziegeler" email="cziegeler@apache.org"/>
</authors>
- <abstract>This document describes the file generator of Cocoon 2.</abstract>
+ <abstract>This document describes the file generator of @docname@.</abstract>
</header>
<body>
<s1 title="File Generator">
1.1.2.2 +2 -3 xml-cocoon2/xdocs/filter-transformer.xml
Index: filter-transformer.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/filter-transformer.xml,v
retrieving revision 1.1.2.1
retrieving revision 1.1.2.2
diff -u -r1.1.2.1 -r1.1.2.2
--- filter-transformer.xml 2001/07/18 07:42:20 1.1.2.1
+++ filter-transformer.xml 2001/07/19 13:46:58 1.1.2.2
@@ -2,8 +2,7 @@
<!DOCTYPE document SYSTEM "dtd/document-v10.dtd">
<document>
<header>
- <title>Filter Transformer</title>
- <subtitle>in Cocoon 2</subtitle>
+ <title>Filter Transformer in @doctitle@</title>
<version>0.9</version>
<type>Technical document</type>
<authors>
@@ -11,7 +10,7 @@
<person name="Sven Beauprez" email="Sven.Beauprez@the-ecorp.com"/>
<person name="Davanum Srinivas" email="dims@yahoo.com"/>
</authors>
- <abstract>This document describes the Filter transformer of Cocoon 2.</abstract>
+ <abstract>This document describes the Filter transformer of @docname@.</abstract>
</header>
<body>
<s1 title="Filter Transformer">
1.1.2.5 +4 -5 xml-cocoon2/xdocs/generators.xml
Index: generators.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/generators.xml,v
retrieving revision 1.1.2.4
retrieving revision 1.1.2.5
diff -u -r1.1.2.4 -r1.1.2.5
--- generators.xml 2001/07/18 07:42:20 1.1.2.4
+++ generators.xml 2001/07/19 13:46:58 1.1.2.5
@@ -2,18 +2,17 @@
<!DOCTYPE document SYSTEM "dtd/document-v10.dtd">
<document>
<header>
- <title>Generators</title>
- <subtitle>in Cocoon 2</subtitle>
+ <title>Generators in @doctitle@</title>
<version>0.9</version>
<type>Technical document</type>
<authors>
<person name="Carsten Ziegeler" email="cziegeler@apache.org"/>
</authors>
- <abstract>This document describes all available generators of Cocoon 2.</abstract>
+ <abstract>This document describes all available generators of @docname@.</abstract>
</header>
<body>
<s1 title="Goal">
- <p>This document lists all available generators of Cocoon 2 and
+ <p>This document lists all available generators of @doctitle@ and
describes their purpose.</p>
</s1>
<s1 title="Overview">
@@ -23,7 +22,7 @@
see <link href="sitemap.html">the sitemap</link>.
</p>
</s1>
- <s1 title="The Generators in Apache Cocoon 2">
+ <s1 title="The Generators in @doctitle@">
<ul>
<li><link href="file-generator.html">File Generator</link> (The default generator)</li>
<li><link href="html-generator.html">HTML Generator</link> (optional)</li>
1.1.2.2 +9 -9 xml-cocoon2/xdocs/hosting.xml
Index: hosting.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/hosting.xml,v
retrieving revision 1.1.2.1
retrieving revision 1.1.2.2
diff -u -r1.1.2.1 -r1.1.2.2
--- hosting.xml 2001/06/07 19:13:53 1.1.2.1
+++ hosting.xml 2001/07/19 13:46:58 1.1.2.2
@@ -4,7 +4,7 @@
<document>
<header>
- <title>Cocoon Hosting</title>
+ <title>@docname@ Hosting</title>
<authors>
<person name="Robin Green" email="greenrd@hotmail.com"/>
</authors>
@@ -12,28 +12,28 @@
<body>
- <s1 title="Cocoon Hosting">
+ <s1 title="@docname@ Hosting">
<p>
- Here is a list of sites that provide Cocoon web hosting, and which versions are
+ Here is a list of sites that provide @docname@ web hosting, and which versions are
provided (if known). Version information may not be up-to-date on this list, so
always check with the site itself to make sure.
</p>
<p>
- To add your site to this list - you must have cocoon up and running and be
+ To add your site to this list - you must have @docname@ up and running and be
accepting application forms! - send an email to cocoon-users@xml.apache.org.
</p>
<ul>
- <li><link href="http://www.aoindustries.com/">AO Industries</link> - Cocoon 1.8.</li>
+ <li><link href="http://www.aoindustries.com/">AO Industries</link> - @docname@ 1.8.</li>
<li><link href="http://webartists.net/webhosting.html">Webartists</link> (German)</li>
- <li><link href="http://www.capital-internet.net/">Capital Internet</link> - Cocoon 1.8</li>
+ <li><link href="http://www.capital-internet.net/">Capital Internet</link> - @docname@ 1.8</li>
<li><strong>[FREE]</strong> -
<link href="http://dev.startcom.org/">MediaHost Free Developer Accounts</link> -
- Cocoon 1.8</li>
+ @docname@ 1.8</li>
<li><link href="http://www.mmaweb.net/">Motivational Marketing Associates, Inc</link> -
- Cocoon 1.7.4</li>
- <li><link href="http://www.spilkalideriv.kiev.ua/">www.spilkalideriv.kiev.ua</link> - Cocoon 1.8</li>
+ @docname@ 1.7.4</li>
+ <li><link href="http://www.spilkalideriv.kiev.ua/">www.spilkalideriv.kiev.ua</link> - @docname@ 1.8</li>
</ul>
</s1>
1.1.2.3 +3 -4 xml-cocoon2/xdocs/html-generator.xml
Index: html-generator.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/html-generator.xml,v
retrieving revision 1.1.2.2
retrieving revision 1.1.2.3
diff -u -r1.1.2.2 -r1.1.2.3
--- html-generator.xml 2001/07/17 09:28:17 1.1.2.2
+++ html-generator.xml 2001/07/19 13:46:58 1.1.2.3
@@ -2,14 +2,13 @@
<!DOCTYPE document SYSTEM "dtd/document-v10.dtd">
<document>
<header>
- <title>HTML Generator</title>
- <subtitle>in Cocoon 2</subtitle>
+ <title>HTML Generator in @doctitle@</title>
<version>0.9</version>
<type>Technical document</type>
<authors>
<person name="Carsten Ziegeler" email="cziegeler@apache.org"/>
</authors>
- <abstract>This document describes the html generator of Cocoon 2.</abstract>
+ <abstract>This document describes the html generator of @docname@.</abstract>
</header>
<body>
<s1 title="HTML Generator">
@@ -17,7 +16,7 @@
It acts similar to the file generator with the difference that it reads
html documents and converts them using jtidy to xhtml.</p>
<p>This generator is optional and requires the jtidy package
- in the lib directory when building cocoon 2. However,
+ in the lib directory when building @docname@. However,
the distribution includes this package already.</p>
<ul>
<li>Name : html</li>
1.1.2.2 +2 -3 xml-cocoon2/xdocs/html-serializer.xml
Index: html-serializer.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/html-serializer.xml,v
retrieving revision 1.1.2.1
retrieving revision 1.1.2.2
diff -u -r1.1.2.1 -r1.1.2.2
--- html-serializer.xml 2001/07/12 21:06:17 1.1.2.1
+++ html-serializer.xml 2001/07/19 13:46:58 1.1.2.2
@@ -2,14 +2,13 @@
<!DOCTYPE document SYSTEM "dtd/document-v10.dtd">
<document>
<header>
- <title>HTML Serializer</title>
- <subtitle>in Cocoon 2</subtitle>
+ <title>HTML Serializer in @doctitle@</title>
<version>0.9</version>
<type>Technical document</type>
<authors>
<person name="Carsten Ziegeler" email="cziegeler@apache.org"/>
</authors>
- <abstract>This document describes the html serializer of Cocoon 2.</abstract>
+ <abstract>This document describes the html serializer of @docname@.</abstract>
</header>
<body>
<s1 title="HTML Serializer">
1.2.2.2 +15 -15 xml-cocoon2/xdocs/httprequest.xml
Index: httprequest.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/httprequest.xml,v
retrieving revision 1.2.2.1
retrieving revision 1.2.2.2
diff -u -r1.2.2.1 -r1.2.2.2
--- httprequest.xml 2001/07/18 11:11:53 1.2.2.1
+++ httprequest.xml 2001/07/19 13:46:58 1.2.2.2
@@ -2,22 +2,22 @@
<!DOCTYPE document SYSTEM "dtd/document-v10.dtd">
<document>
<header>
- <title>Cocoon @version@</title>
+ <title>@doctitle@</title>
<subtitle>What happens if a http request arrives</subtitle>
<version>0.1</version>
<type>Technical Document</type>
<authors><person name="Tom Klaasen" email="tom.klaasen@the-ecorp.com"/>
</authors>
- <abstract>This document tries to explain Cocoon 2 (based on the version
+ <abstract>This document tries to explain @docname@ (based on the version
@version@) technically. We do this by describing what happens if somebody types in
- the URL of a simple Cocoon page.</abstract>
+ the URL of a simple @docname@ page.</abstract>
</header>
<body>
<s1 title="Introduction">
<s2 title="Goal">
- <p>This document tries to explain Cocoon 2 (based on the version @version@)
+ <p>This document tries to explain @docname@ (based on the version @version@)
technically. We do this by describing what happens if somebody types in the URL
- of a simple Cocoon page.</p>
+ of a simple @docname@ page.</p>
</s2>
<s2 title="Intended public">
<p>The reader should have a knowledge of:</p>
@@ -31,14 +31,14 @@
</s1>
<s1 title="The configuration assumptions">
<p>The sequence of events described in this document, depends on some
- assumptions with regard to the configuration of Cocoon. That's what's described
+ assumptions with regard to the configuration of @docname@. That's what's described
here.</p>
<s2 title="sitemap.xmap">
- <p>The task of the sitemap is to define the pipelines that Cocoon will
+ <p>The task of the sitemap is to define the pipelines that @docname@ will
apply to URI's called in one's browser.</p>
<p>This is the minimal sitemap that is necessary. The lines here are
included in the standard sitemap.xmap that comes with the distribution of
- Cocoon @version@.</p>
+ @docname@ @version@.</p>
<p>The sitemap is defined in <code>${cocoon}/sitemap.xmap</code>.</p>
<source><![CDATA[
<?xml version="1.0"?>
@@ -98,7 +98,7 @@
<p><code>cocoon.xconf</code> is the file that defines the
<link href="avalon.html">Avalon</link> Components.</p>
<p>For our study, we need the standard <code>cocoon.xconf</code> file
- of Cocoon @version@.</p>
+ of @docname@ @version@.</p>
<p>It can be found in <code>${cocoon}/cocoon.xconf</code>.</p>
<source><![CDATA[
<?xml version="1.0"?>
@@ -183,7 +183,7 @@
<s1 title="The sequence of things">
<s2 title="Role of Tomcat">
<p>The role of Tomcat is to initialize the CocoonServlet, and to
- receive the HttpRequest and pass it on to the Cocoon servlet.</p>
+ receive the HttpRequest and pass it on to the CocoonServlet.</p>
<s3 title="Initialize CocoonServlet">
<p>This is done by calling
<code>CocoonServlet.init(ServletConfig)</code>. This is the standard servlet
@@ -199,13 +199,13 @@
<s3 title="Overview">
<p>The steps that happen on initialization, are:</p>
<s4 title="Find the classpath">
- <p>Cocoon needs to know the classpath for compilation of the files
+ <p>@docname@ needs to know the classpath for compilation of the files
it generates itself. This is where the classpath is stored.</p>
</s4>
<s4 title="Find the init file">
<p>The init file (normally <code>cocoon.xconf</code>, as defined in
<code>${cocoon}/WEB-INF/web.xml</code>) contains the necessary information for
- Cocoon to decide which classes to use for which roles (refer to
+ @docname@ to decide which classes to use for which roles (refer to
<link href="avalon.html">Avalon</link>).</p>
<p>This is a feature that is added for increased configurability.
If you were developing a one time solution, the information in this file would
@@ -221,11 +221,11 @@
<p>The handling of <code>cocoon.xconf</code> goes as follows:</p>
<ol>
<li>Get the parser: This is something necessary for
- bootstrapping: cocoon.xconf contains the parser to be used by Cocoon, but
- cocoon.xconf is an xml file that has to be parsed itself. That's why Cocoon
+ bootstrapping: cocoon.xconf contains the parser to be used by @docname@, but
+ cocoon.xconf is an xml file that has to be parsed itself. That's why @docname@
gets a default parser out of the System properties (this refers to the
environment variable <code>$org.apache.cocoon.components.parser.Parser</code>
- of the OS). If no parser is defined in the environment, Cocoon will use
+ of the OS). If no parser is defined in the environment, @docname@ will use
<code>org.apache.cocoon.components.parser.JaxpParser</code> (a hard-coded
default).</li>
<li>Get the components: Cocoon uses roles (refer to
1.1.2.3 +5 -6 xml-cocoon2/xdocs/i18n-transformer.xml
Index: i18n-transformer.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/i18n-transformer.xml,v
retrieving revision 1.1.2.2
retrieving revision 1.1.2.3
diff -u -r1.1.2.2 -r1.1.2.3
--- i18n-transformer.xml 2001/07/18 11:11:53 1.1.2.2
+++ i18n-transformer.xml 2001/07/19 13:46:58 1.1.2.3
@@ -2,8 +2,7 @@
<!DOCTYPE document SYSTEM "dtd/document-v10.dtd">
<document>
<header>
- <title>I18n Transformer</title>
- <subtitle>in Cocoon 2</subtitle>
+ <title>I18n Transformer in @doctitle@</title>
<version>0.9</version>
<type>Technical document</type>
<authors>
@@ -11,7 +10,7 @@
</authors>
<abstract>
This document describes an approach for internationalization of XML
- documents within Cocoon 2. It introduces some tags to markup text
+ documents within @docname@. It introduces some tags to markup text
that should be translated and a format for dictionaries.
The first proposal was made by Infozone Group (http://www.infozone-group.org).
</abstract>
@@ -20,11 +19,11 @@
<s1 title="I18n Transformer">
<p>
Developing and maintaining multi-language sites is common problem for web developers.
- The usage of XML and XSL makes this task much more easier, especially with Cocoon's
+ The usage of XML and XSL makes this task much more easier, especially with @docname@'s
content, logic and presentation separation concept.
</p>
<p>
- This approach for internationalization (further - i18n) of XML documents within Cocoon 2
+ This approach for internationalization (further - i18n) of XML documents within @docname@
is based on a transformer - <link href="javadocs/org/apache/cocoon/transformation/I18nTransformer.html">
<code>I18nTransformer</code>
</link>
@@ -360,7 +359,7 @@
<s2 title="Contacts">
<p>
Feel free to contact for any comments and improvement ideas either directly <link href="mailto:kpiroumian@flagship.ru">Konstantin Piroumian</link>
- or through the <link href="/cocoon/mail-lists.html">Cocoon Mail List</link>.
+ or through the <link href="/cocoon/mail-lists.html">@docname@ Mail List</link>.
</p>
</s2>
</s1>
1.1.2.4 +2 -2 xml-cocoon2/xdocs/imagedirectory-generator.xml
Index: imagedirectory-generator.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/imagedirectory-generator.xml,v
retrieving revision 1.1.2.3
retrieving revision 1.1.2.4
diff -u -r1.1.2.3 -r1.1.2.4
--- imagedirectory-generator.xml 2001/07/18 11:11:53 1.1.2.3
+++ imagedirectory-generator.xml 2001/07/19 13:46:58 1.1.2.4
@@ -3,13 +3,13 @@
<document>
<header>
<title>Image Directory Generator</title>
- <subtitle>in Cocoon 2</subtitle>
+ <subtitle>in @doctitle@</subtitle>
<version>0.9</version>
<type>Technical document</type>
<authors>
<person name="Carsten Ziegeler" email="cziegeler@apache.org"/>
</authors>
- <abstract>This document describes the image directory generator of Cocoon 2.</abstract>
+ <abstract>This document describes the image directory generator of @docname@.</abstract>
</header>
<body>
<s1 title="Image Directory Generator">
1.1.1.1.2.4 +37 -37 xml-cocoon2/xdocs/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/index.xml,v
retrieving revision 1.1.1.1.2.3
retrieving revision 1.1.1.1.2.4
diff -u -r1.1.1.1.2.3 -r1.1.1.1.2.4
--- index.xml 2001/07/16 06:36:08 1.1.1.1.2.3
+++ index.xml 2001/07/19 13:46:58 1.1.1.1.2.4
@@ -4,7 +4,7 @@
<document>
<header>
- <title>Cocoon2</title>
+ <title>@doctitle@</title>
<subtitle>XML Publishing Framework</subtitle>
<authors>
<person name="Stefano Mazzocchi" email="stefano@apache.org"/>
@@ -15,16 +15,16 @@
<s1 title="What is it?">
<p>
- Cocoon2 is a complete rewrite of the Cocoon XML publishing framework that
+ @doctitle@ is a complete rewrite of the @docname@ XML publishing framework that
is supposed to remove all those design constraint that emerged from the
- Cocoon1 experience.
+ @docname@ 1 experience.
</p>
<p>
This documentation is alpha, like anything else, so don't expect
that much. If you are not a developer and you are not willing to test
new stuff that may not work as expected, we suggest you to refer to the latest
- Cocoon1 release which is very stable.
+ @docname@ 1 release which is very stable.
</p>
<p>
@@ -33,14 +33,14 @@
</s1>
<s1 title="A new look">
- <p>The Cocoon Project will evidence its new course with a new logo that was
+ <p>The @docname@ Project will evidence its new course with a new logo that was
designed by Cocoon's creator Stefano Mazzocchi. Here it is:</p>
- <figure src="images/cocoon2.gif" alt="The new Cocoon Logo"/>
+ <figure src="images/cocoon2.gif" alt="The new @docname@ Logo"/>
</s1>
<s1 title="Introduction">
- <p>The Cocoon Project has gone a long way since its creation on
+ <p>The @docname@ Project has gone a long way since its creation on
January 1999. It started as a simple servlet for static XSL styling and became
more and more powerful as new features were added. Unfortunately, design
decisions made early in the project influenced its evolution. Today, some of
@@ -48,7 +48,7 @@
solidified. For this reason, those design decisions need to be reconsidered
under this new light.</p>
- <p>While Cocoon started as a small step in the direction of a new
+ <p>While @docname@ started as a small step in the direction of a new
web publishing idea based on better design patterns and reviewed estimations
of management issues, the technology used was not mature enough for tools to
emerge. Today, most web engineers consider XML as the key for an improved web
@@ -62,22 +62,22 @@
<s1 title="Passive APIs vs. Active APIs">
<p>Web serving environments must be fast and scalable to be
- useful. Cocoon1 was born as a "proof of concept" rather than
+ useful. @docname@ 1 was born as a "proof of concept" rather than
production software and had significant design restrictions, based mainly on
the availability of freely redistributable tools. Other issues were lack of
detailed knowledge on the APIs available as well as underestimation of the
project success, being created as a way to learn XSL rather than a full
publishing system capable of taking care of all XML web publishing needs.</p>
- <p>For the above reasons, Cocoon 1 was based on the DOM level 1
+ <p>For the above reasons, @docname@ 1 was based on the DOM level 1
API which is a <em>passive</em> API and was intended mainly for client side
operation. This is mainly due to the fact that most DOM
implementations require the document to reside in memory. While this is
practical for small documents and thus good for the "proof of
- concept" stage, it is now considered a main design constraint for Cocoon
+ concept" stage, it is now considered a main design constraint for @docname@
scalability.</p>
- <p>Since the goal of Cocoon 2 is the ability to process
+ <p>Since the goal of @docname@ 2 is the ability to process
simultaneously multiple 100Mb documents in JVM with a few Mbs of heap size,
careful memory use and tuning of internal components is a key issue. To reach
this goal, an improved API model was needed. This is now identified in the SAX
@@ -104,7 +104,7 @@
<dt>Lowered memory consumption</dt>
<dd>
Since most of the
- server processing required in Cocoon is incremental, an incremental model
+ server processing required in @docname@ is incremental, an incremental model
allows XML production events to be transformed directly into output events
and character written on streams, thus avoiding the need to store them in
memory.
@@ -137,19 +137,19 @@
</dd>
</dl>
- <p>The above points alone would be enough for the Cocoon 2
+ <p>The above points alone would be enough for the @doctitle@
paradigm shift, even if this event based model impacts not only the general
architecture of the publishing system but also its internal processing
components such as XSLT processing and PDF formatting. These components will
require substantial work and maybe design reconsideration to be able to follow
- a pure event-based model. The Cocoon Project will work closely with the other
+ a pure event-based model. The @docname@ Project will work closely with the other
component projects to be able to influence their operation in this direction.</p>
</s1>
<s1 title="Reactors Reconsidered">
<p>Another design choice that should be revised is the reactor
pattern that was introduced to allow components to be connected in more
- flexible way. In fact, by contrast to the fixed pipe model used up to Cocoon
+ flexible way. In fact, by contrast to the fixed pipe model used up to @docname@
1.3.1, the reactor approach allows components to be dynamically connected,
depending on reaction instructions introduced inside the documents.</p>
@@ -187,15 +187,15 @@
(that based their improved site structure on internal contracts).</p>
<p>The simplification and engineering of web site management is
- considered one of the most important Cocoon 2 goals. This is done mainly by
+ considered one of the most important @doctitle@ goals. This is done mainly by
technologically imposing a reduced number of contracts and placing them in a
hierarchical shape, suitable for replacing current high-structure web site
management models.</p>
- <p>The model that Cocoon 2 adopts is the "pyramid model of
+ <p>The model that @doctitle@ adopts is the "pyramid model of
web contracts" which is outlined in the picture below</p>
- <figure src="images/pyramid-model.gif" alt="The Cocoon 2 Pyramid Model of Contracts"/>
+ <figure src="images/pyramid-model.gif" alt="The @doctitle@ Pyramid Model of Contracts"/>
<p>and is composed by four different working contexts (the rectangles)</p>
@@ -233,7 +233,7 @@
<li>content - style</li>
</ul>
- <p>Note that there is no <em>logic - style</em> contract. Cocoon 2 aims to
+ <p>Note that there is no <em>logic - style</em> contract. @doctitle@ aims to
provide both software and guidelines to allow you to remove such a
contract.</p>
</s1>
@@ -244,18 +244,18 @@
point. For example, if the W3C-recommended method to link stylesheets to XML
documents is used, the content and style contexts overlap and it's impossible
to change the styling behavior of the document without changing it. The same
- is true for the processing instructions used by the Cocoon 1 reactor to drive
+ is true for the processing instructions used by the @docname@ 1 reactor to drive
the page processing: each stage specifies the next stage to determine the result,
thus increasing management and debugging complexity. Another overlapping in
context contracts is the need for URL-encoded parameters to drive the page output.
These overlaps break the pyramid model and increase the management costs.</p>
- <p>In Cocoon 2, the reactor pattern will be abandoned in favor of
+ <p>In @doctitle@, the reactor pattern will be abandoned in favor of
a pipeline mapping technique. This is based on the fact that the number of
different contracts is limited even for big sites and grows with a rate
that is normally much less than its size.</p>
- <p>Also, for performance reasons, Cocoon 2 will try to compile
+ <p>Also, for performance reasons, @doctitle@ will try to compile
everything that is possibly compilable (pages/XSP into generators, stylesheets
into transformers, etc...) so, in this new model, the <em>processing chain</em>
that generates the page contains (in a direct executable form) all the
@@ -263,19 +263,19 @@
response.</p>
<p>This means that instead of using event-driven request-time DTD interpretation
- (done in all Cocoon 1 processors), these will be either compiled into transformers
+ (done in all @docname@ 1 processors), these will be either compiled into transformers
directly (XSLT stylesheet compilation) or compiled into generators using
logicsheets and XSP which will remove totally the need for request-time
interpretation solutions like DCP that will be removed.</p>
- <note>Some of these features are already present in latest Cocoon 1.x
- releases but the Cocoon 2 architecture will make them central to its new
+ <note>Some of these features are already present in latest @docname@ 1.x
+ releases but the @docname@ 2 architecture will make them central to its new
core.</note>
</s1>
<s1 title="Sitemap">
- <p>In Cocoon 2 terminology, a <em>sitemap</em> is the collection of pipeline
- matching informations that allow the Cocoon engine to associate the requested
+ <p>In @docname@ 2 terminology, a <em>sitemap</em> is the collection of pipeline
+ matching informations that allow the @docname@ engine to associate the requested
URI to the proper response-producing pipeline.</p>
<p>The sitemap physically represents the central repository for web site
@@ -287,27 +287,27 @@
</s1>
<s1 title="Pre-compilation, Pre-generation and Caching">
- <p>The cache system in Cocoon 1 will be ported with very little
+ <p>The cache system in @docname@ 1 will be ported with very little
design changes since it's very flexible and was not polluted by early design
constraints since it appeared in later versions. The issue regarding static
file caching that, no matter what, will always be slower than direct web server
- caching, means that Cocoon 2 will be as <em>proxy friendly</em> as possible.</p>
+ caching, means that @docname@ 2 will be as <em>proxy friendly</em> as possible.</p>
<p>To be able to put most of the static part of the job back on the web
- server (where it belongs), Cocoon 2 will greatly improve its command line
+ server (where it belongs), @docname@ 2 will greatly improve its command line
operation, allowing the creation of <em>site makefiles</em> that will
automatically scan the web site and the source documents and will provide a
way to <em>regenerate</em> the static part of a web site (images and tables
included!) based on the same XML model used in the dynamic operation version.</p>
- <p>Cocoon 2 will, in fact, be the integration between Cocoon 1 and Stylebook.</p>
+ <p>@docname@ 2 will, in fact, be the integration between @docname@ 1 and Stylebook.</p>
<p>It will be up to the web server administrator to use static
regeneration capabilities on a time basis, manually or triggered by some
- particular event (e.g. database update signal) since Cocoon 2 will only provide
+ particular event (e.g. database update signal) since @docname@ 2 will only provide
servlet and command line capabilities. The nice integration is based on the
fact that there will be no behavioral difference if the files are dynamically
- generated in Cocoon 2 via the servlet operation and cached internally or
+ generated in @docname@ 2 via the servlet operation and cached internally or
pre-generated and served directly by the web server, as long as URI contracts
are kept the same by the system administrator (via URL-rewriting or aliasing)</p>
@@ -317,7 +317,7 @@
</s1>
<s1 title="Development Status">
- <p>Cocoon 2 development has reached "beta quality"
+ <p>@docname@ 2 development has reached "beta quality"
You might take a look at it on the <em>xml-cocoon2</em>
CVS module. If you are not a CVS expert, this means
typing:</p>
@@ -330,10 +330,10 @@
</source>
<p>For more information on CVS access, refer to the CVS docs on this web site.</p>
- <note>To get the current version of Cocoon 2 you have to checkout the
+ <note>To get the current version of @docname@ 2 you have to checkout the
branch called cocoon_20_branch. The HEAD of the cvs repository is used
for the developer team to store and test new ideas which will be
- perhaps included in later releases of Cocoon2.</note>
+ perhaps included in later releases of @docname@ 2.</note>
</s1>
</body>
1.6.2.8 +50 -50 xml-cocoon2/xdocs/installing.xml
Index: installing.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/installing.xml,v
retrieving revision 1.6.2.7
retrieving revision 1.6.2.8
diff -u -r1.6.2.7 -r1.6.2.8
--- installing.xml 2001/07/19 07:59:02 1.6.2.7
+++ installing.xml 2001/07/19 13:46:58 1.6.2.8
@@ -3,7 +3,7 @@
<document>
<header>
- <title>Installing Cocoon2</title>
+ <title>Installing @doctitle@</title>
<authors>
<person name="Stefano Mazzocchi" email="stefano@apache.org"/>
<person name="Giacomo Pati" email="Giacomo.Pati@pwr.ch"/>
@@ -17,12 +17,12 @@
<s1 title="System Requirements">
<p>
- Cocoon2 requires the following systems to be already installed in your system:
+ @doctitle@ requires the following systems to be already installed in your system:
</p>
<p><strong>Java Virtual Machine</strong>
A Java 1.2 or later compatible virtual machine must be present for both
- command line and servlet type usage of Cocoon. Note that all servlet engines
+ command line and servlet type usage of @docname@. Note that all servlet engines
require a JVM to run so if you are already using servlets you already have
one installed.
</p>
@@ -41,16 +41,16 @@
</s1>
- <s1 title="Getting Apache Cocoon 2">
+ <s1 title="Getting Apache @doctitle@">
<p>
- You have two choices for getting Cocoon2: you can either download
+ You have two choices for getting @doctitle@: you can either download
a stable relese or you can get the latest in development version
directly from the cvs repository.
</p>
<s2 title="Download a distribution">
<p>
You can simply download the latest official release from the
- <link href="http://xml.apache.org/dist/cocoon2">cocoon2 distribution</link>
+ <link href="http://xml.apache.org/dist/cocoon2">@docname@ distribution</link>
directory.
</p>
</s2>
@@ -79,7 +79,7 @@
window;</li>
<li>Wait until you see "*****CVS exited normally with code 0*****" in the
log window;</li>
- <li>The Cocoon2 source is now on your harddrive.</li>
+ <li>The @docname@ source is now on your harddrive.</li>
</ol>
</s2>
<s2 title="Step-by-step cvs instructions for Unix">
@@ -89,15 +89,15 @@
<li>When asked for the password: answer "anoncvs".</li>
<li>Enter "cvs -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic -z3 checkout -r cocoon_20_branch xml-cocoon2". This will create a directory called "xml-cocoon2" where the Cocoon2 source will be stored.</li>
<li>Wait until cvs has finished.</li>
- <li>The Cocoon2 source is now on your harddrive.</li>
+ <li>The @docname@ source is now on your harddrive.</li>
</ol>
- <p>In case you want to update your Cocoon2 source tree to the
+ <p>In case you want to update your @docname@ source tree to the
current version, change to the "xml-cocoon2" directory and
call "cvs -z3 update -d -P".</p>
</s2>
</s1>
- <s1 title="Building Cocoon2">
+ <s1 title="Building @doctitle@">
<s2 title="Set JAVA_HOME environment variable">
@@ -113,7 +113,7 @@
</s2>
- <s2 title="Create the Cocoon WAR package">
+ <s2 title="Create the @docname@ WAR package">
<p>To do this you simply have to type:</p>
@@ -129,7 +129,7 @@
<s2 title="Making the sql examples work out of the box">
<p>
- The sample web application delivered with Cocoon2 contains some
+ The sample web application delivered with @docname@ 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
@@ -149,7 +149,7 @@
</s2>
<s2 title="Adding additional components">
<p>
- Some of the components delivered with Cocoon2 required additional libraries,
+ Some of the components delivered with @docname@ required additional libraries,
e.g. the Php generator or the FOP serializer (for more information about
these components, refer to their documentation).
</p>
@@ -157,7 +157,7 @@
Most of these libraries are already included in the distribution, but some
have to be downloaded manually. The build task checks whether you have
the required libraries or not and includes the optional components only
- if you have the libraries available when you build Cocoon2.
+ if you have the libraries available when you build @docname@.
</p>
<p>
A library/package is available to the build process when it is located
@@ -202,7 +202,7 @@
</s2>
</s1>
- <s1 title="Installing Cocoon2">
+ <s1 title="Installing @docname@">
<p>In most servlet engines, this is just a matter of copying
the war file in a specific directory and the engine will take
@@ -211,7 +211,7 @@
<s2 title="Installing on Tomcat 3.X">
<p>Tomcat currently uses a different version of the XML parser
- than Cocoon. To get Cocoon to work, you need to perform the
+ than @docname@. To get @docname@ to work, you need to perform the
following steps:</p>
<ol>
@@ -241,7 +241,7 @@
<li>
<strong>Copy cocoon/lib/xerces-XXX.jar file to tomcat\lib</strong>
- Cocoon will now be able to see and use the correct XML libraries.
+ @docname@ will now be able to see and use the correct XML libraries.
</li>
<li>
@@ -254,12 +254,12 @@
</li>
<li>
- <strong>Start using Cocoon</strong>
+ <strong>Start using @docname@</strong>
Access the URI
<link href="http://localhost:8080/cocoon/">http://localhost:8080/cocoon/</link>
- with your favorite browser and start to enjoy the world of Cocoon.
- Note that the first time you access Cocoon, it will take a few
- seconds to start, since Cocoon needs to compile parts of itself.
+ with your favorite browser and start to enjoy the world of @docname@.
+ Note that the first time you access @docname@, it will take a few
+ seconds to start, since @docname@ needs to compile parts of itself.
</li>
</ol>
@@ -268,7 +268,7 @@
<s2 title="Installing on Tomcat 4.X">
- <p>Note that Tomcat-4.0 beta1 will not work with Cocoon2. You
+ <p>Note that Tomcat-4.0 beta1 will not work with @doctitle@. You
must use Tomcat-4.0 beta3 or a nightly build from
<link href="http://jakarta.apache.org/builds/jakarta-tomcat-4.0/nightly/">http://jakarta.apache.org/builds/jakarta-tomcat-4.0/nightly/</link>
</p>
@@ -280,9 +280,9 @@
(Having said that, I do :-)</p>
- <p>Tomcat 4.0 does not expose the servlet.jar file to Cocoon by default,
- so <strong>before you build the cocoon webapp</strong> you will need to
- add the following to the cocoon servlet definition in the web.xml file:</p>
+ <p>Tomcat 4.0 does not expose the servlet.jar file to @docname@ by default,
+ so <strong>before you build the @docname@ webapp</strong> you will need to
+ add the following to the @docname@ servlet definition in the web.xml file:</p>
<source>
<init-param>
@@ -296,11 +296,11 @@
<li>
<strong>Modify cocoon/webapp/WEB-INF/web.xml</strong>
- Add the code shown above to the cocoon web.xml file
+ Add the code shown above to the @docname@ web.xml file
</li>
<li>
- <strong>Build the cocoon webapp</strong>
+ <strong>Build the @docname@ webapp</strong>
Build the webapp as described above. This will now include
the corrected web.xml file.
</li>
@@ -315,12 +315,12 @@
</li>
<li>
- <strong>Start using Cocoon</strong>
+ <strong>Start using @docname@</strong>
Access the URI
<link href="http://localhost:8080/cocoon/">http://localhost:8080/cocoon/</link>
- with your favorite browser and start to enjoy the world of Cocoon.
- Note that the first time you access Cocoon, it will take a few
- seconds to start, since Cocoon needs to compile parts of itself.
+ with your favorite browser and start to enjoy the world of @docname@.
+ Note that the first time you access @docname@, it will take a few
+ seconds to start, since @docname@ needs to compile parts of itself.
</li>
</ol>
@@ -329,7 +329,7 @@
<s2 title="Installing on BEA Weblogic 6.0">
- <p>This installs Cocoon 2 using the cocoon.war file.
+ <p>This installs @docname@ using the cocoon.war file.
This was successfully installed under Windows 2000.
Unix users will need to adjust appropriately. If you haven't done so already,
build a domain and a server. In this discussion, the name of the domain
@@ -355,10 +355,10 @@
</li>
<li>
- Congratulations! (hopefully) you should see the Cocoon welcome page.
+ Congratulations! (hopefully) you should see the @docname@ welcome page.
</li>
</ol>
- <note>If you have problems with starting up cocoon, you can modify the CLASSPATH in the .cmd files and
+ <note>If you have problems with starting up @docname@, you can modify the CLASSPATH in the .cmd files and
ensure that xerces-XXX.jar is picked up before any other jars.
<br/>
<code>set CLASSPATH=.;c:\bea\jdk130\jre\lib\xerces-XXX.jar;.\lib\weblogic_sp.jar;.\lib\weblogic.jar</code>
@@ -368,7 +368,7 @@
<s2 title="Installing on ServletExec 3.1 (In Process with IIS)">
- <p>This installs Cocoon 2 in a "war" configuration. This was successfully
+ <p>This installs @docname@ in a "war" configuration. This was successfully
installed under Windows NT 4.0 and IIS 4. I don't believe that SE is
available for unix.</p>
@@ -378,20 +378,20 @@
<li>Install IIS as usual</li>
<li>Install ServletExec (default paths will be used throughout), but
don't start it.</li>
- <li>Build Cocoon 2's war file (include lib's)</li>
+ <li>Build @docname@'s war file (include lib's)</li>
<li>Copy <em>cocoon.war</em> into
<em>C:\Program Files\New Atlanta\ServletExec ISAPI\webapps\default</em>,
creating the directory default if required.</li>
<li>Start IIS.</li>
- <li>Open the Cocoon welcome page (http://localhost/cocoon/)</li>
+ <li>Open the @docname@ welcome page (http://localhost/cocoon/)</li>
<li>
- Congratulations! (hopefully) you should see the Cocoon welcome page.
+ Congratulations! (hopefully) you should see the @docname@ welcome page.
</li>
</ol>
</s2>
<s2 title="Installing on JBoss 2.2.2 with Tomcat 3.2.2">
- <p>This section describes the deployment of the Cocoon 2 sample WAR with
- the JBoss 2.2.2/Tomcat-3.2.2 package. It assumes that you built Cocoon 2 as described above. All steps have been tested with a fresh JBoss 2.2.2 installation on Linux and Windows ME(sic).</p>
+ <p>This section describes the deployment of the @docname@ sample WAR with
+ the JBoss 2.2.2/Tomcat-3.2.2 package. It assumes that you built @docname@ as described above. All steps have been tested with a fresh JBoss 2.2.2 installation on Linux and Windows ME(sic).</p>
<note>The JBoss/Tomcat bundle is available from the <link href="http://sourceforge.net/projects/jboss/">JBoss project page</link></note>
<p>The JBoss/Tomcat package has the following directory
structure</p>
@@ -401,8 +401,8 @@
</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 2 distribution or CVS checkout.</li></ul>
- <p>In order to get Cocoon 2 running you have to install Xerces as default XML parser for JBoss.</p>
+ <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 @docname@ distribution or CVS checkout.</li></ul>
+ <p>In order to get @docname@ running you have to install Xerces as default XML parser for JBoss.</p>
<ul>
<li>Stop the server if it is running.</li>
<li>Remove the following files from the <code>jboss/lib</code> directory
@@ -439,18 +439,18 @@
<li>Start JBoss with <code>run_with_tomcat.sh</code> or <code>run_with_tomcat.bat</code></li>
<li>Copy <code>cocoon/build/cocoon/cocoon.war</code> to <code>jboss/deploy</code></li>
<li>Check the server log to make sure that <code>J2EE application: [...]/cocoon.war is deployed.</code></li>
- <li>Open the Cocoon welcome page (http://localhost:8080/cocoon/)</li>
+ <li>Open the @docname@ welcome page (http://localhost:8080/cocoon/)</li>
<li>
- Congratulations! (hopefully) you should see the Cocoon welcome page.
+ Congratulations! (hopefully) you should see the @docname@ welcome page.
</li>
</ul>
- <note>As both JBoss and Cocoon 2 ship with a Hypersonic database installed, these two conflict and you won't be able to use Cocoon's database (SQL) samples. Then again, you probably use JBoss for EJB persistence anyway, so this shouldn't bother you too much ;-)
+ <note>As both JBoss and @docname@ ship with a Hypersonic database installed, these two conflict and you won't be able to use @docname@ database (SQL) samples. Then again, you probably use JBoss for EJB persistence anyway, so this shouldn't bother you too much ;-)
</note>
</s2>
<s2 title="Installing on Resin 2.0.0">
<p>
- This section describes the deployment of the Cocoon 2 sample WAR with Resin 2.0.0.
- It assumes that you built Cocoon 2 as described above. All steps have been tested
+ This section describes the deployment of the @docname@ sample WAR with Resin 2.0.0.
+ It assumes that you built @docname@ as described above. All steps have been tested
with a fresh Resin 2.0.0 installation (the package is available from
<link href="http://www.caucho.com/download/">Resin's download page</link>)
</p>
@@ -460,7 +460,7 @@
[path]/resin-2.0.0/lib
[path]/resin-2.0.0/webapps
[path]...</source>
- <p>In order to get Cocoon 2 running you have to install Xerces as default XML parser for Resin.</p>
+ <p>In order to get @docname@ running you have to install Xerces as default XML parser for Resin.</p>
<ul>
<li>Stop the server if it is running.</li><li>Remove the following files from the <code>resin-2.0.0/lib</code> directory
<ul>
@@ -476,8 +476,8 @@
</ul>
<ul>
<li>Start Resin as usual</li>
- <li>Open the Cocoon welcome page (http://localhost:8080/cocoon/)</li>
- <li>Congratulations! (hopefully) you should see the Cocoon welcome page.</li>
+ <li>Open the @docname@ welcome page (http://localhost:8080/cocoon/)</li>
+ <li>Congratulations! (hopefully) you should see the @docname@ welcome page.</li>
</ul>
</s2>
</s1>
1.1.2.7 +8 -8 xml-cocoon2/xdocs/jars.xml
Index: jars.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/jars.xml,v
retrieving revision 1.1.2.6
retrieving revision 1.1.2.7
diff -u -r1.1.2.6 -r1.1.2.7
--- jars.xml 2001/07/18 11:11:53 1.1.2.6
+++ jars.xml 2001/07/19 13:46:58 1.1.2.7
@@ -4,7 +4,7 @@
<document>
<header>
- <title>Cocoon 2 JARs</title>
+ <title>@doctitle@ JARs</title>
<authors>
<person name="John Morrison" email="john.morrison@uk.experian.com"/>
</authors>
@@ -20,9 +20,9 @@
<tr>
<th>Jar name</th>
<th>Description</th>
- <th>Required by Core Cocoon</th>
- <th>Required by Cocoon Component</th>
- <th>Required by Cocoon Sample</th>
+ <th>Required by Core @docname@</th>
+ <th>Required by @docname@ Component</th>
+ <th>Required by @docname@ Sample</th>
<th>Comment</th>
</tr>
<tr>
@@ -57,7 +57,7 @@
<td>No</td>
<td/>
<td/>
- <td>Is this used outside of the Cocoon samples?</td>
+ <td>Is this used outside of the @docname@ samples?</td>
</tr>
<tr>
<td><link href="http://xml.apache.org/batik/">batik-libs</link></td>
@@ -84,8 +84,8 @@
'adopted'.</td>
</tr>
<tr>
- <td><link href="http://xml.apache.org/cocoon2/">cocoon</link></td>
- <td>Apache Cocoon is a 100% pure Java publishing framework that relies on
+ <td><link href="http://xml.apache.org/cocoon2/">@docname@</link></td>
+ <td>@docname@ is a 100% pure Java publishing framework that relies on
new W3C technologies (such as XML, XSL, SVG, etc..) to provide web
content.</td>
<td>Yes!</td>
@@ -179,7 +179,7 @@
<td>Yes</td>
<td/>
<td/>
- <td>Cocoon logging.</td>
+ <td>@docname@ logging.</td>
</tr>
<tr>
<td><link href="http://www.weft.co.uk/library/maybeupload/">maybeupload</link></td>
1.1.2.2 +2 -3 xml-cocoon2/xdocs/jsp-generator.xml
Index: jsp-generator.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/jsp-generator.xml,v
retrieving revision 1.1.2.1
retrieving revision 1.1.2.2
diff -u -r1.1.2.1 -r1.1.2.2
--- jsp-generator.xml 2001/07/12 21:06:36 1.1.2.1
+++ jsp-generator.xml 2001/07/19 13:46:58 1.1.2.2
@@ -2,14 +2,13 @@
<!DOCTYPE document SYSTEM "dtd/document-v10.dtd">
<document>
<header>
- <title>JSP Generator</title>
- <subtitle>in Cocoon 2</subtitle>
+ <title>JSP Generator in @doctitle@</title>
<version>0.9</version>
<type>Technical document</type>
<authors>
<person name="Carsten Ziegeler" email="cziegeler@apache.org"/>
</authors>
- <abstract>This document describes the jsp generator of Cocoon 2.</abstract>
+ <abstract>This document describes the jsp generator of @docname@.</abstract>
</header>
<body>
<s1 title="JSP Generator">
----------------------------------------------------------------------
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