cziegeler 01/07/19 07:20:03
Modified: xdocs Tag: cocoon_20_branch ldap-transformer.xml
license.xml link-serializer.xml livesites.xml
log-transformer.xml logicsheet-concepts.xml
logicsheet-forms.xml logicsheet.xml mail-lists.xml
matchers_selectors.xml overview.xml patches.xml
pdf-serializer.xml php-generator.xml
readdomsession-transformer.xml
request-generator.xml request.xml
script-generator.xml serializers.xml
serverpages-generator.xml sessions.xml
site-book.xml sitemap.xml sql-transformer.xml
status-generator.xml stream-generator.xml
svg-serializer.xml svgjpeg-serializer.xml
svgpng-serializer.xml svgxml-serializer.xml
text-serializer.xml transformers.xml uc2.xml
velocity-generator.xml vrml-serializer.xml
wap-serializer.xml who.xml
writedomsession-transformer.xml
xinclude-transformer.xml xml-serializer.xml
xslt-transformer.xml xsp-internals.xml xsp.xml
xt-transformer.xml
Log:
Updated docs from k-z to use the new tags
Revision Changes Path
No revision
No revision
1.1.2.3 +3 -3 xml-cocoon2/xdocs/ldap-transformer.xml
Index: ldap-transformer.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/ldap-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
--- ldap-transformer.xml 2001/07/18 07:42:20 1.1.2.2
+++ ldap-transformer.xml 2001/07/19 14:20:01 1.1.2.3
@@ -3,13 +3,13 @@
<document>
<header>
<title>LDAP 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="[EMAIL
PROTECTED]"/>
</authors>
- <abstract>This document describes the LDAP transformer of
Cocoon 2.</abstract>
+ <abstract>This document describes the LDAP transformer of
@[EMAIL PROTECTED]</abstract>
</header>
<body>
<s1 title="LDAP Transformer">
@@ -26,7 +26,7 @@
</ul>
<p>This transformer is optional and not available in
the binary distribution.
However if you want to use it, you have to retrieve the
jndi package,
- copy the jar file into the lib directory of cocoon and
rebuild.
+ copy the jar file into the lib directory of @docname@
and rebuild.
</p>
<p>
The file will be specified in a parameter tag in the sitemap pipeline to the
1.1.1.1.2.1 +3 -3 xml-cocoon2/xdocs/license.xml
Index: license.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/license.xml,v
retrieving revision 1.1.1.1
retrieving revision 1.1.1.1.2.1
diff -u -r1.1.1.1 -r1.1.1.1.2.1
--- license.xml 2001/05/09 20:50:22 1.1.1.1
+++ license.xml 2001/07/19 14:20:01 1.1.1.1.2.1
@@ -4,14 +4,14 @@
<document>
<header>
- <title>Cocoon Public License</title>
+ <title>@docname@ Public License</title>
<authors>
<person name="Stefano Mazzocchi" email="[EMAIL PROTECTED]"/>
</authors>
</header>
<body>
-<s1 title="Cocoon Public License">
+<s1 title="@docname@ Public License">
<source><![CDATA[
============================================================================
The Apache Software License, Version 1.1
@@ -35,7 +35,7 @@
Alternately, this acknowledgment may appear in the software itself, if
and wherever such third-party acknowledgments normally appear.
- 4. The names "Cocoon" and "Apache Software Foundation" must not be used to
+ 4. The names "@docname@" and "Apache Software Foundation" must not be
used to
endorse or promote products derived from this software without prior
written permission. For written permission, please contact
[EMAIL PROTECTED]
1.1.2.2 +2 -2 xml-cocoon2/xdocs/link-serializer.xml
Index: link-serializer.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/link-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
--- link-serializer.xml 2001/07/12 21:06:43 1.1.2.1
+++ link-serializer.xml 2001/07/19 14:20:01 1.1.2.2
@@ -3,13 +3,13 @@
<document>
<header>
<title>Link Serializer</title>
- <subtitle>in Cocoon 2</subtitle>
+ <subtitle>in @doctitle@</subtitle>
<version>0.9</version>
<type>Technical document</type>
<authors>
<person name="Carsten Ziegeler" email="[EMAIL
PROTECTED]"/>
</authors>
- <abstract>This document describes the link serializer of
Cocoon 2.</abstract>
+ <abstract>This document describes the link serializer of
@[EMAIL PROTECTED]</abstract>
</header>
<body>
<s1 title="Link Serializer">
1.1.2.4 +5 -5 xml-cocoon2/xdocs/livesites.xml
Index: livesites.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/livesites.xml,v
retrieving revision 1.1.2.3
retrieving revision 1.1.2.4
diff -u -r1.1.2.3 -r1.1.2.4
--- livesites.xml 2001/07/12 21:06:45 1.1.2.3
+++ livesites.xml 2001/07/19 14:20:01 1.1.2.4
@@ -3,7 +3,7 @@
<document>
<header>
- <title>Live Sites powered by Cocoon</title>
+ <title>Live Sites powered by @docname@</title>
<authors>
<person name="Donald Ball" email="[EMAIL PROTECTED]"/>
<person name="Stefano Mazzocchi" email="[EMAIL PROTECTED]"/>
@@ -12,9 +12,9 @@
</header>
<body>
- <s1 title="Live Sites powered by Cocoon 1.X">
+ <s1 title="Live Sites powered by @docname@ 1.X">
<p>
- Here is a list of web sites that are proudly powered by Cocoon 1.X
+ Here is a list of web sites that are proudly powered by @docname@ 1.X
(in chronological order):
</p>
@@ -66,9 +66,9 @@
</ul>
</s1>
- <s1 title="Live Sites powered by Cocoon 2.X">
+ <s1 title="Live Sites powered by @docname@ 2.X">
<p>
- Here is a list of web sites that are proudly powered by Cocoon 2.X
+ Here is a list of web sites that are proudly powered by @docname@ 2.X
(in chronological order):
</p>
1.1.2.5 +2 -2 xml-cocoon2/xdocs/log-transformer.xml
Index: log-transformer.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/log-transformer.xml,v
retrieving revision 1.1.2.4
retrieving revision 1.1.2.5
diff -u -r1.1.2.4 -r1.1.2.5
--- log-transformer.xml 2001/07/18 11:30:09 1.1.2.4
+++ log-transformer.xml 2001/07/19 14:20:01 1.1.2.5
@@ -3,13 +3,13 @@
<document>
<header>
<title>Log 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="[EMAIL
PROTECTED]"/>
</authors>
- <abstract>This document describes the Log transformer of
Cocoon 2.</abstract>
+ <abstract>This document describes the Log transformer of
@[EMAIL PROTECTED]</abstract>
</header>
<body>
<s1 title="Log Transformer">
1.1.1.1.2.2 +2 -2 xml-cocoon2/xdocs/logicsheet-concepts.xml
Index: logicsheet-concepts.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/logicsheet-concepts.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
--- logicsheet-concepts.xml 2001/07/18 11:11:53 1.1.1.1.2.1
+++ logicsheet-concepts.xml 2001/07/19 14:20:01 1.1.1.1.2.2
@@ -329,7 +329,7 @@
</p>
<p>
- Thus, for example, when Cocoon is used as a servlet, XSP pages
+ Thus, for example, when @docname@ is used as a servlet, XSP pages
need access to the underlying servlet engine objects: request,
response, session, servlet config, etc.
</p>
@@ -454,7 +454,7 @@
Logicsheet preprocessor is still unimplemented.
Preprocessing may be performed as well in XSLT by using
<em>extension functions</em>. Logicsheet preprocessing is meant to be
- used in those cases where the XSLT processor being used by Cocoon
+ used in those cases where the XSLT processor being used by @docname@
does not support XSLT extensions. (As of this writing, only
<link href="http://xml.apache.org/xalan/";>Xalan</link>
is known to support XSLT extensions).
1.1.2.4 +1 -1 xml-cocoon2/xdocs/logicsheet-forms.xml
Index: logicsheet-forms.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/logicsheet-forms.xml,v
retrieving revision 1.1.2.3
retrieving revision 1.1.2.4
diff -u -r1.1.2.3 -r1.1.2.4
--- logicsheet-forms.xml 2001/07/18 11:11:53 1.1.2.3
+++ logicsheet-forms.xml 2001/07/19 14:20:01 1.1.2.4
@@ -12,7 +12,7 @@
<body>
<s1 title="Introduction?">
<p>
- For most web applications input is essential. Cocoon provides a
+ For most web applications input is essential. @docname@ provides a
variety of modules to support basic interaction like simple syntax
checking of input data or writing input data to databases.
</p>
1.1.2.2 +15 -15 xml-cocoon2/xdocs/logicsheet.xml
Index: logicsheet.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/logicsheet.xml,v
retrieving revision 1.1.2.1
retrieving revision 1.1.2.2
diff -u -r1.1.2.1 -r1.1.2.2
--- logicsheet.xml 2001/06/14 11:42:55 1.1.2.1
+++ logicsheet.xml 2001/07/19 14:20:01 1.1.2.2
@@ -14,9 +14,9 @@
<s1 title="Introduction">
<p>This document is intended as an introduction and brief tutorial to
using and
- creating Cocoon XSP logicsheets. It is assumed that the reader has a
working
+ creating @docname@ XSP logicsheets. It is assumed that the reader has a
working
knowledge of XML and XSLT, and has worked through at least the basic XSP
examples
- supplied with Cocoon. Although this is not intended as a tutorial for XSP
+ supplied with @[EMAIL PROTECTED] Although this is not intended as a
tutorial for XSP
specifically, much of the material may be helpful in gaining a fuller
understanding
of XSP.</p>
</s1>
@@ -26,14 +26,14 @@
will use these terms interchangeably. The term "taglib" comes from JSP,
which
inspired XSP. An XSP logicsheet is a "tag library" in the sense that it
defines
a set of custom XML tags which can be used within an XSP program to insert
whole
- blocks of code into the file. Cocoon comes with several pre-defined
"taglibs",
+ blocks of code into the file. @docname@ comes with several pre-defined
"taglibs",
such as the request taglib. Using the request taglib, you can insert the
following
tag into your XSP code to obtain the HTTP request parameter named "fruit"
(e.g., if
your URL looks something like "http://myserver.org/index.xml?fruit=apple";,
the value
of "fruit" is "apple"):</p>
<source><![CDATA[<request:get-parameter name="fruit"/>]]></source>
- <p>We will discuss how to use Cocoon's pre-defined taglibs in a later
section. The
+ <p>We will discuss how to use @docname@'s pre-defined taglibs in a later
section. The
important thing to understand is that all taglibs are defined by a
logicsheet. A
logicsheet, as we will see, is a special kind of XSL stylesheet, whose
output is an
XSP file.</p>
@@ -41,7 +41,7 @@
<s1 title="Hello World!">
<p>We'll start with some simple <code>Hello, World!</code> examples,
starting with
- a simple HTML file, and extending it using Cocoon technologies until we
have a
+ a simple HTML file, and extending it using @docname@ technologies until we
have a
working (if trivial) example of XSP using a custom logicsheet.</p>
<s2 title="Simple HTML Example">
@@ -250,7 +250,7 @@
First, as in the previous examples, you can tell XSP explicitly what
logicsheets to apply, using the <?xml-logicsheet?> processing
instruction
along with the usual <?cocoon-process?> instruction that tells
- Cocoon to use XSP:</p>
+ @docname@ to use XSP:</p>
<source><![CDATA[
<?cocoon-process type="xsp"?>
<?xml-logicsheet href="logicsheet.greeting.xsl"?>]]>
@@ -258,14 +258,14 @@
<p>There is another way to apply a logicsheet, which doesn't require a
processing instruction for each file that uses the logicsheet. The
- second way to use a logicsheet depends on whether you are using Cocoon 1
- or Cocoon 2. For Cocoon 2, take a look at the
- <link href="http://xml.apache.org/cocoon/cocoon2/";>Cocoon 2 Site</link>.
- For Cocoon 1, a logicsheet's namespace may be declared in the
+ second way to use a logicsheet depends on whether you are using @docname@ 1
+ or @docname@ 2. For @docname@ 2, take a look at the
+ <link href="http://xml.apache.org/cocoon/cocoon2/";>@docname@ Site</link>.
+ For @docname@, a logicsheet's namespace may be declared in the
cocoon.properties file. These declarations take the form</p>
<source>processor.xsp.logicsheet.namespace-name.language = URL to
file</source>
- <p>Cocoon's pre-defined logicsheets are already declared in this file. For
+ <p>@docname@'s pre-defined logicsheets are already declared in this file.
For
instance, the declaration of the request taglib is the following:</p>
<source>
processor.xsp.logicsheet.request.java
@@ -301,7 +301,7 @@
<p>There are some very important differences between using the
<?xml-logicsheet?>
processing instruction vs. the cocoon.properties entry to apply a
logicsheet.
Using cocoon.properties, any time the logicsheet changes, it is necessary
to
- restart Cocoon. If you instead use the processing instruction, Cocoon
will detect
+ restart @[EMAIL PROTECTED] If you instead use the processing instruction,
@docname@ will detect
modifications to your logicsheet, and recompile your XSP programs
accordingly.
Also, if you need to explicitly control the order in which your
logicsheets are
applied, you need to use the processing instruction. Logicsheets will be
applied
@@ -343,7 +343,7 @@
XML/XSL complications. It also lets you see exactly the results of XSLT
transformation
using your logicsheet.</dd>
<dt>Steal Code</dt>
- <dd>The authors of the logicsheets distributed with Cocoon have already
solved
+ <dd>The authors of the logicsheets distributed with @docname@ have
already solved
numerous problems that you may encounter. Read their code (it is in the
source
tree) and borrow from it liberally. Reading this code is also a good
way to
gain insight into logicsheet design.</dd>
@@ -356,7 +356,7 @@
source file, and there is the possibility that other logicsheets may
also be acting
on the same file (either before or after our logicsheet), there are a
few templates
which are more or less required in any logicsheet. The templates below
were all
- pulled from the taglib logicsheets distributed with Cocoon.</p>
+ pulled from the taglib logicsheets distributed with @[EMAIL
PROTECTED]</p>
<p>The first of these is simply a template to copy anything you don't
directly act
upon yourself. You probably have a template similar to this in most of
your
stylesheets already.</p>
@@ -416,7 +416,7 @@
<s2 title="Logicsheets Using Logicsheets">
<p>Since software tends to build on other software, you will probably
find
yourself wanting to write logicsheets which make use of other
logicsheets,
- particularly the logicsheets provided with Cocoon. This is very
possible.
+ particularly the logicsheets provided with @[EMAIL PROTECTED] This is
very possible.
When using one logicsheet inside another, the most important thing to
remember
is that you must declare the namespace for the second logicsheet not
only in
the first logicsheet, but also in any XSP program that uses the first
logicsheet,
1.1.2.3 +14 -14 xml-cocoon2/xdocs/mail-lists.xml
Index: mail-lists.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/mail-lists.xml,v
retrieving revision 1.1.2.2
retrieving revision 1.1.2.3
diff -u -r1.1.2.2 -r1.1.2.3
--- mail-lists.xml 2001/06/11 11:36:58 1.1.2.2
+++ mail-lists.xml 2001/07/19 14:20:01 1.1.2.3
@@ -20,16 +20,16 @@
<li><link
href="http://dmoz.org/Computers/Data_Formats/Markup_Languages/XML/";>ODP XML
links</link>
- a wealth of general XML information.</li>
<li><connect href="mail-archives.xml">Mailing list archives</connect> -
- a veritable goldmine of Cocoon-specific information - if you know where
to look!</li>
+ a veritable goldmine of @[EMAIL PROTECTED] information - if you know
where to look!</li>
</ol>
</s1>
- <s1 title="Cocoon Users">
+ <s1 title="@docname@ Users">
<p><link href="mailto:[EMAIL PROTECTED]">Subscribe</link>
<link href="mailto:[EMAIL PROTECTED]">Unsubscribe</link>
</p>
- <p>The general Cocoon list, for problems, bug reports, asking for advice
on how
+ <p>The general @docname@ list, for problems, bug reports, asking for
advice on how
best to implement a site, comparisons with other XML frameworks, etc.
But don't forget to look in the FAQ first, please!</p>
@@ -48,7 +48,7 @@
<p><strong>IMPORTANT:</strong> If you are posting about a problem you are
having
(as most people do), it will aid in finding a speedy resolution if you
provide
- full configuration details (especially the <strong>Cocoon version
number</strong>,
+ full configuration details (especially the <strong>@docname@ version
number</strong>,
but also your operating system, JDK version, and servlet engine), and
full details
of any errors encountered (including full error messages and stack
traces).</p>
@@ -66,18 +66,18 @@
delay before your post is reviewed and accepted. This is to prevent
spam.</note>
</s1>
- <s1 title="Cocoon Dev">
+ <s1 title="@docname@ Dev">
<p><link href="mailto:[EMAIL PROTECTED]">Subscribe</link>
<link href="mailto:[EMAIL PROTECTED]">Unsubscribe</link>
</p>
<p>This list is for developers <strong>working on</strong> or wanting to
work on
- Cocoon itself (not developers merely working <strong>with</strong>
Cocoon),
- for code patches to Cocoon to be posted (please use <code>diff -u</code>
format),
- and for general Cocoon 2 questions.</p>
+ @docname@ itself (not developers merely working <strong>with</strong>
@docname@),
+ for code patches to @docname@ to be posted (please use <code>diff
-u</code> format),
+ and for general @docname@ questions.</p>
- <p>Note this is <strong>NOT</strong> for general Cocoon questions like
"Why
- isn't Cocoon working on my machine?" -
+ <p>Note this is <strong>NOT</strong> for general @docname@ questions like
"Why
+ isn't @docname@ working on my machine?" -
please ask those sorts of questions on cocoon-users (after reading the
FAQ first, of course).</p>
@@ -85,7 +85,7 @@
delay before your post is reviewed and accepted. This is to prevent
spam.</note>
</s1>
- <s1 title="Cocoon Cvs">
+ <s1 title="@docname@ Cvs">
<p><link href="mailto:[EMAIL PROTECTED]">Subscribe</link>
<link href="mailto:[EMAIL PROTECTED]">Unsubscribe</link>
</p>
@@ -107,14 +107,14 @@
<p>This list began life on November 2000, and was created to discuss the
standardisation and implementation of the dynamic content language XSP,
- which is used not only in Cocoon but in other software such as AxKit.
+ which is used not only in @docname@ but in other software such as AxKit.
You are recommended to have a strong working knowledge of XSP before
joining
this list.</p>
<p>Note this is <strong>NOT</strong> for general XSP questions like
"Why doesn't my XSP page work?" - please ask those sorts of questions on
the relevant list for your XSP software (e.g. cocoon-users if you're
using
- Cocoon) - after checking the FAQ first of course!
+ @docname@) - after checking the FAQ first of course!
</p>
</s1>
@@ -124,7 +124,7 @@
ODP XML links</link> for related websites.)</p>
<ul>
<li><link href="http://www.mulberrytech.com/xsl/";>Mulberrytech XSL
list</link> -
- more appropriate than Cocoon Users for general XSL questions.</li>
+ more appropriate than @docname@ Users for general XSL questions.</li>
<li><link href="http://xml.apache.org/mail.html";>XML Apache
Projects</link> -
list of mailing lists for all the projects on xml.apache.org.</li>
<li>Some servlet engines have their own mailing lists for servlet-engine
1.1.2.3 +2 -2 xml-cocoon2/xdocs/matchers_selectors.xml
Index: matchers_selectors.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/matchers_selectors.xml,v
retrieving revision 1.1.2.2
retrieving revision 1.1.2.3
diff -u -r1.1.2.2 -r1.1.2.3
--- matchers_selectors.xml 2001/07/18 11:11:53 1.1.2.2
+++ matchers_selectors.xml 2001/07/19 14:20:01 1.1.2.3
@@ -18,12 +18,12 @@
of the request processing. One particular matcher you're probably
familiar with, is the WildcardURIMatcher. That is the one that
determines the (sub-)pipeline in the welcome example. But there are
- many more matchers supplied with Cocoon, one matches the requested
+ many more matchers supplied with @docname@, one matches the requested
URI on regular expressions, others match the client's hostname,
existence of parameters and so on.
</p>
<p>
- There is also a number of selectors supplied with Cocoon. Selectors
+ There is also a number of selectors supplied with @[EMAIL PROTECTED]
Selectors
test a generally simple boolean expression and allow to select on
roughly the same things as matchers would. There is a selector on
the client's hostname, on the client's browser etc.
1.1.1.1.2.1 +6 -6 xml-cocoon2/xdocs/overview.xml
Index: overview.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/overview.xml,v
retrieving revision 1.1.1.1
retrieving revision 1.1.1.1.2.1
diff -u -r1.1.1.1 -r1.1.1.1.2.1
--- overview.xml 2001/05/09 20:50:23 1.1.1.1
+++ overview.xml 2001/07/19 14:20:01 1.1.1.1.2.1
@@ -2,25 +2,25 @@
<!DOCTYPE document SYSTEM "dtd/document-v10.dtd">
<document>
<header>
- <title>Overview of Cocoon 2</title>
+ <title>Overview of @doctitle@</title>
<version>0.1</version>
<type>Overview document</type>
<authors><person name="Tom Klaasen" email="[EMAIL PROTECTED]"/>
</authors>
</header>
<body>
- <s1 title="What is Cocoon">
- <p>Cocoon is an XML publishing framework. It allows you to
define XML
+ <s1 title="What is @docname@">
+ <p>@docname@ is an XML publishing framework. It allows you to
define XML
documents and transformations to be applied on it, to
eventually generate a
presentation format of your choice (HTML, PDF, SVG, ...).</p>
- <p>Cocoon also gives you the possibility to have logic in your
XML files
+ <p>@docname@ also gives you the possibility to have logic in
your XML files
(so that the XML file itself can become dynamically
generated).</p>
</s1>
<s1 title="General structure">
<p>This section gives a general overview of how an XML document
is
- handled by Cocoon.</p>
+ handled by @[EMAIL PROTECTED]</p>
<s2 title="Pipeline">
- <p>Cocoon relies on the pipeline model: an XML document is
pushed
+ <p>@docname@ relies on the pipeline model: an XML document is
pushed
through a pipeline, that exists in several
transformation steps of your
document. Every pipeline begins with a generator,
continues with zero or more
transformers, and ends with a serializer. This can be
compared to the
1.1.2.3 +1 -1 xml-cocoon2/xdocs/patches.xml
Index: patches.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/patches.xml,v
retrieving revision 1.1.2.2
retrieving revision 1.1.2.3
diff -u -r1.1.2.2 -r1.1.2.3
--- patches.xml 2001/07/18 11:11:53 1.1.2.2
+++ patches.xml 2001/07/19 14:20:01 1.1.2.3
@@ -18,7 +18,7 @@
This is an <strong>informal</strong> list - in chronological order -
of some of the noteworthy patches that have been posted
to the <link href="mailto:[email protected]";>cocoon-dev</link>
mailing list.
- These patches are not (yet) part of the Cocoon project, but need
reviewing for possible
+ These patches are not (yet) part of the @docname@ project, but need
reviewing for possible
inclusion. This system was instituted because, due to the large volume of
mail and
the lack of time of the committers, some patches tended to get forgotten
about. This
queue does not guarantee that any patch will be reviewed within a
reasonable time frame,
1.1.2.3 +2 -2 xml-cocoon2/xdocs/pdf-serializer.xml
Index: pdf-serializer.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/pdf-serializer.xml,v
retrieving revision 1.1.2.2
retrieving revision 1.1.2.3
diff -u -r1.1.2.2 -r1.1.2.3
--- pdf-serializer.xml 2001/07/17 09:28:17 1.1.2.2
+++ pdf-serializer.xml 2001/07/19 14:20:01 1.1.2.3
@@ -3,13 +3,13 @@
<document>
<header>
<title>PDF Serializer</title>
- <subtitle>in Cocoon 2</subtitle>
+ <subtitle>in @doctitle@</subtitle>
<version>0.9</version>
<type>Technical document</type>
<authors>
<person name="Carsten Ziegeler" email="[EMAIL
PROTECTED]"/>
</authors>
- <abstract>This document describes the pdf serializer of Cocoon
2.</abstract>
+ <abstract>This document describes the pdf serializer of
@[EMAIL PROTECTED]</abstract>
</header>
<body>
<s1 title="PDF Serializer">
1.1.2.2 +2 -2 xml-cocoon2/xdocs/php-generator.xml
Index: php-generator.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/php-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
--- php-generator.xml 2001/07/12 21:06:55 1.1.2.1
+++ php-generator.xml 2001/07/19 14:20:01 1.1.2.2
@@ -3,13 +3,13 @@
<document>
<header>
<title>Php 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="[EMAIL
PROTECTED]"/>
</authors>
- <abstract>This document describes the php generator of Cocoon
2.</abstract>
+ <abstract>This document describes the php generator of @[EMAIL
PROTECTED]</abstract>
</header>
<body>
<s1 title="Php Generator">
1.1.2.2 +2 -2 xml-cocoon2/xdocs/readdomsession-transformer.xml
Index: readdomsession-transformer.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/readdomsession-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
--- readdomsession-transformer.xml 2001/07/18 07:42:20 1.1.2.1
+++ readdomsession-transformer.xml 2001/07/19 14:20:01 1.1.2.2
@@ -3,7 +3,7 @@
<document>
<header>
<title>Read DOM Session Transformer</title>
- <subtitle>in Cocoon 2</subtitle>
+ <subtitle>in @doctitle@</subtitle>
<version>0.9</version>
<type>Technical document</type>
<authors>
@@ -11,7 +11,7 @@
<person name="Sven Beauprez" email="[EMAIL PROTECTED]"/>
<person name="Davanum Srinivas" email="[EMAIL
PROTECTED]"/>
</authors>
- <abstract>This document describes the read dom session
transformer of Cocoon 2.</abstract>
+ <abstract>This document describes the read dom session
transformer of @[EMAIL PROTECTED]</abstract>
</header>
<body>
<s1 title="Read DOM Session Transformer">
1.1.2.4 +2 -2 xml-cocoon2/xdocs/request-generator.xml
Index: request-generator.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/request-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
--- request-generator.xml 2001/07/16 13:26:20 1.1.2.3
+++ request-generator.xml 2001/07/19 14:20:01 1.1.2.4
@@ -3,13 +3,13 @@
<document>
<header>
<title>Request 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="[EMAIL PROTECTED]"/>
</authors>
- <abstract>This document describes the request generator of Cocoon
2.</abstract>
+ <abstract>This document describes the request generator of @[EMAIL
PROTECTED]</abstract>
</header>
<body>
<s1 title="Request Generator">
1.1.2.3 +1 -1 xml-cocoon2/xdocs/request.xml
Index: request.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/request.xml,v
retrieving revision 1.1.2.2
retrieving revision 1.1.2.3
diff -u -r1.1.2.2 -r1.1.2.3
--- request.xml 2001/06/25 09:38:52 1.1.2.2
+++ request.xml 2001/07/19 14:20:01 1.1.2.3
@@ -79,7 +79,7 @@
</xsp:page>
]]></source>
-<p>If your server is www.mydomain.com and you save this XML in your Cocoon
+<p>If your server is www.mydomain.com and you save this XML in your @docname@
document tree as /cocoon/request.xml, then you can see the effect of the
<em>request</em> elements by opening your browser with the URL
<code>http://www.mydomain.com/cocoon/request.xml?fruit=apple</code></p>
1.1.2.2 +2 -2 xml-cocoon2/xdocs/script-generator.xml
Index: script-generator.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/script-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
--- script-generator.xml 2001/07/12 21:07:03 1.1.2.1
+++ script-generator.xml 2001/07/19 14:20:01 1.1.2.2
@@ -3,13 +3,13 @@
<document>
<header>
<title>Script 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="[EMAIL
PROTECTED]"/>
</authors>
- <abstract>This document describes the script generator of
Cocoon 2.</abstract>
+ <abstract>This document describes the script generator of
@[EMAIL PROTECTED]</abstract>
</header>
<body>
<s1 title="Script Generator">
1.1.2.5 +4 -4 xml-cocoon2/xdocs/serializers.xml
Index: serializers.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/serializers.xml,v
retrieving revision 1.1.2.4
retrieving revision 1.1.2.5
diff -u -r1.1.2.4 -r1.1.2.5
--- serializers.xml 2001/07/18 07:42:20 1.1.2.4
+++ serializers.xml 2001/07/19 14:20:01 1.1.2.5
@@ -3,17 +3,17 @@
<document>
<header>
<title>Serializers</title>
- <subtitle>in Cocoon 2</subtitle>
+ <subtitle>in @doctitle@</subtitle>
<version>0.9</version>
<type>Technical document</type>
<authors>
<person name="Carsten Ziegeler" email="[EMAIL
PROTECTED]"/>
</authors>
- <abstract>This document describes all available serializers of
Cocoon 2.</abstract>
+ <abstract>This document describes all available serializers of
@[EMAIL PROTECTED]</abstract>
</header>
<body>
<s1 title="Goal">
- <p>This document lists all available serializers of
Cocoon 2 and
+ <p>This document lists all available serializers of
@doctitle@ and
describes their purpose.</p>
</s1>
<s1 title="Overview">
@@ -22,7 +22,7 @@
see <link href="sitemap.html">the sitemap</link>.
</p>
</s1>
- <s1 title="The Serializers in Apache Cocoon 2">
+ <s1 title="The Serializers in @doctitle@">
<ul>
<li><link href="html-serializer.html">HTML
Serializer</link> (The default serializer)</li>
<li><link href="xml-serializer.html">XML
Serializer</link></li>
1.1.2.2 +2 -2 xml-cocoon2/xdocs/serverpages-generator.xml
Index: serverpages-generator.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/serverpages-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
--- serverpages-generator.xml 2001/07/12 21:07:09 1.1.2.1
+++ serverpages-generator.xml 2001/07/19 14:20:01 1.1.2.2
@@ -3,13 +3,13 @@
<document>
<header>
<title>Server Pages 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="[EMAIL
PROTECTED]"/>
</authors>
- <abstract>This document describes the server pages generator
of Cocoon 2.</abstract>
+ <abstract>This document describes the server pages generator
of @[EMAIL PROTECTED]</abstract>
</header>
<body>
<s1 title="Server Pages Generator">
1.2.2.2 +13 -13 xml-cocoon2/xdocs/sessions.xml
Index: sessions.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/sessions.xml,v
retrieving revision 1.2.2.1
retrieving revision 1.2.2.2
diff -u -r1.2.2.1 -r1.2.2.2
--- sessions.xml 2001/07/18 11:11:53 1.2.2.1
+++ sessions.xml 2001/07/19 14:20:01 1.2.2.2
@@ -4,7 +4,7 @@
<document>
<header>
- <title>Session tracking with Cocoon</title>
+ <title>Session tracking with @docname@</title>
<subtitle>Introduction, Installation and Example</subtitle>
<version>0.1</version>
<type>Technical Document</type>
@@ -12,16 +12,16 @@
<person name="J�rg Prante" email="[EMAIL PROTECTED]"/>
</authors>
<abstract>
- This document explains what Cocoon 2 provides to support session
tracking.
+ This document explains what @docname@ provides to support session
tracking.
Session tracking is an important feature for web server frameworks
because HTTP and related protocols are stateless,
- but sometimes we need stateful information about visitors of a Cocoon
site.
+ but sometimes we need stateful information about visitors of a @docname@
site.
For a more precise analysis of a web site, the tracking of visitors
should work independent of the visitor's browser and of the visitor's
decision
- whether we enabled cookies or not. Last not least, Cocoon 2 should not
+ whether we enabled cookies or not. Last not least, @docname@ should not
be dependant of the method the servlet engine prefers to generate
session IDs.
In this document, it is described step by step what has to be done to
enable
- Cocoon 2 for session management.
+ @docname@ for session management.
</abstract>
</header>
@@ -33,7 +33,7 @@
because HTTP is a stateless protocol. There are many solutions known
to obtain stateful information. Client-side storage of state
information
like the usage of cookies will not be discussed here, since this
depends
- heavily on the client's browser. Since Cocoon is a server-side
framework,
+ heavily on the client's browser. Since @docname@ is a server-side
framework,
storing visitor information at the server side will give full access
to the list of all visitors, to what they have done, and what they
are
doing.
@@ -45,7 +45,7 @@
system resources before wasting it.
</p>
<p>
- If you decided to set up session tracking, Cocoon 2 offers you:
+ If you decided to set up session tracking, @docname@ offers you:
</p>
<ul>
<li>creation of new session IDs</li>
@@ -59,7 +59,7 @@
<s2 title="The session:encode-url template">
<p>
- To enable Cocoon for URI-based session IDs, an XSP template with the
name
+ To enable @docname@ for URI-based session IDs, an XSP template with
the name
<code>session:encode-url</code> will do this for you. It uses the
<code>encodeURL</code> method from the Servlet API which encodes
an URL in a way that a session ID is being attached. Consult your
@@ -102,7 +102,7 @@
The best place of a web site where new sessions should be created
is the entry point
where all or most of the visitors step in. After creating the
session, or
retrieving an old session, the visitor is redirected to a start
page.
- In Cocoon, you must edit your sitemap in order to
+ In @docname@, you must edit your sitemap in order to
specify this interesting point of session creation.
The <code>map-redirect-to</code>
has an extra attribute <code>session</code>, which can be set to
<code>true</code>
@@ -112,15 +112,15 @@
</p>
<p>
- How can Cocoon recognize URIs with appended session IDs? The answer
is:
- Cocoon can match a wildcard against your sessionized pages and
keeps happy.
+ How can @docname@ recognize URIs with appended session IDs? The
answer is:
+ @docname@ can match a wildcard against your sessionized pages and
keeps happy.
So please do not forget to append an asterisk '*' to your patterns
in the pipelines.
</p>
<p>
This fragment from <code>sitemap.xsl</code> shows how you can add a
<code>map:redirect-to</code> to
- your Cocoon framework with session handling at the root URL for your
+ your @docname@ framework with session handling at the root URL for
your
web application:
</p>
@@ -193,7 +193,7 @@
<p>
If you have been successful with installing the session feature and
the example file, the following HTML output will be generated by
- Cocoon from the above <code>sessionpage.xsp</code> example, which shows
+ @docname@ from the above <code>sessionpage.xsp</code> example, which
shows
how the rewritten link looks like. Please don't ask
why the session ID in the generated link is different from yours.
</p>
1.3.2.17 +3 -3 xml-cocoon2/xdocs/site-book.xml
Index: site-book.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/site-book.xml,v
retrieving revision 1.3.2.16
retrieving revision 1.3.2.17
diff -u -r1.3.2.16 -r1.3.2.17
--- site-book.xml 2001/07/18 15:37:52 1.3.2.16
+++ site-book.xml 2001/07/19 14:20:01 1.3.2.17
@@ -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">
<external href="../index.html" label="Back"/>
<separator/>
@@ -89,14 +89,14 @@
<page id="3rdparty" label="3rd Party" source="3rdparty.xml"/>
<page id="patches" label="Patch Queue" source="patches.xml"/>
<separator/>
- <external href="../cocoon/index.html" label="Cocoon 1 Site"/>
+ <external href="../cocoon/index.html" label="@docname@ 1 Site"/>
<separator/>
<faqs id="faqs" label="FAQ File" source="faq.xml" />
<changes id="changes" label="Changes" source="changes.xml"/>
<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.4 +6 -6 xml-cocoon2/xdocs/sitemap.xml
Index: sitemap.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/sitemap.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
--- sitemap.xml 2001/07/18 11:11:53 1.1.1.1.2.3
+++ sitemap.xml 2001/07/19 14:20:01 1.1.1.1.2.4
@@ -17,7 +17,7 @@
<s1 title="The Sitemap">
<p>
This document is used as a working draft for
- Cocoon architects to understand the issues associated with
+ @docname@ architects to understand the issues associated with
sitemaps and XML publishing in general. It must be considered as a
working
draft and may be updated at any time.
</p>
@@ -27,7 +27,7 @@
Mazzocchi ([EMAIL PROTECTED]) and Pierpaolo Fumagalli ([EMAIL PROTECTED])
but grew as a collaborative effort to provide a solid foundation of
design patterns and usability guidelines to create a solid foundation
- of sitemap programmability and usability to the Cocoon Publishing
+ of sitemap programmability and usability to the @docname@ Publishing
Framework.
</p>
@@ -63,7 +63,7 @@
<li>sitemaps must scale along with the site and should not impose growth
limitation to the site as a whole nor limit its administration with size
increase.</li>
- <li>sitemaps should contain all the information required to Cocoon to
+ <li>sitemaps should contain all the information required to @docname@ to
generate all the requests it receives.</li>
<li>sitemaps should contain information for both dynamic operation as
well as offline generation.</li>
@@ -71,14 +71,14 @@
need.</li>
<li>basic web-serving functionalities (redirection, error pages,
resource authorisation) should be provided.</li>
- <li>sitemaps should not limit Cocoon's intrinsic modular
extensibility.</li>
+ <li>sitemaps should not limit @docname@'s intrinsic modular
extensibility.</li>
<li>resources must be matched with all possible state variables, not
only with URI (http parameters, environment variables, server
parameters, time, etc...).</li>
<li>sitemaps should embed the notion of "semantic resources" to be
future-compatible with semantic crawling and indexing.</li>
<li>sitemaps should be flexible enough to allow a complete web site to
- be built with Cocoon.</li>
+ be built with @[EMAIL PROTECTED]</li>
</ol>
<s2 title="The Structure">
@@ -146,7 +146,7 @@
<dt>type</dt>
<dd>The type attribute gives the component a reference which can be
used to point to them in the pipeline section.</dd>
<dt>src</dt>
- <dd>Specifies where Cocoon finds the class representing this
component. Note that the content of
+ <dd>Specifies where @docname@ finds the class representing this
component. Note that the content of
the src attribute must be specified as an URI.
</dd>
</dl>
1.2.2.4 +3 -3 xml-cocoon2/xdocs/sql-transformer.xml
Index: sql-transformer.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/sql-transformer.xml,v
retrieving revision 1.2.2.3
retrieving revision 1.2.2.4
diff -u -r1.2.2.3 -r1.2.2.4
--- sql-transformer.xml 2001/07/18 11:11:53 1.2.2.3
+++ sql-transformer.xml 2001/07/19 14:20:01 1.2.2.4
@@ -5,7 +5,7 @@
<document>
<header>
<title>SQL Transformer</title>
- <subtitle>in Cocoon 2</subtitle>
+ <subtitle>in @doctitle@</subtitle>
<version>0.9</version>
<authors>
<person name="Sven Beauprez" email="[EMAIL PROTECTED]"/>
@@ -87,7 +87,7 @@
<title>Hello</title>
<content>
- <para>This is my first Cocoon2 page filled with sql data!</para>
+ <para>This is my first @docname@ page filled with sql data!</para>
<execute-query xmlns="http://apache.org/cocoon/SQL/2.0";>
<query name="department">
@@ -136,7 +136,7 @@
<page xmlns:sql="http://apache.org/cocoon/SQL/2.0";>
<title>Hello</title>
<content>
- <para>This is my first Cocoon2 page filled with sql data!</para>
+ <para>This is my first @docname@ page filled with sql data!</para>
<rowset nrofrows="2" name="department"
xmlns="http://apache.org/cocoon/SQL/2.0";>
<row>
1.1.2.3 +3 -3 xml-cocoon2/xdocs/status-generator.xml
Index: status-generator.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/status-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
--- status-generator.xml 2001/07/16 14:56:55 1.1.2.2
+++ status-generator.xml 2001/07/19 14:20:01 1.1.2.3
@@ -3,17 +3,17 @@
<document>
<header>
<title>Status 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="[EMAIL
PROTECTED]"/>
</authors>
- <abstract>This document describes the status generator of
Cocoon 2.</abstract>
+ <abstract>This document describes the status generator of
@[EMAIL PROTECTED]</abstract>
</header>
<body>
<s1 title="Status Generator">
- <p>The status generator creates xml from the current
status of cocoon 2.</p>
+ <p>The status generator creates xml from the current
status of cocoon.</p>
<p>The information is surrounded by the root element
<code>statusinfo</code>
and grouped with the elements <code>group</code> and
<code>value</code>.</p>
<p>The <code>statusinfo</code> element has the
attributes <code>host</code>
1.1.2.3 +2 -2 xml-cocoon2/xdocs/stream-generator.xml
Index: stream-generator.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/stream-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
--- stream-generator.xml 2001/07/12 21:07:19 1.1.2.2
+++ stream-generator.xml 2001/07/19 14:20:01 1.1.2.3
@@ -3,14 +3,14 @@
<document>
<header>
<title>Stream Generator</title>
- <subtitle>in Cocoon 2</subtitle>
+ <subtitle>in @doctitle@</subtitle>
<version>0.9</version>
<type>Technical document</type>
<authors>
<person name="Kinga Dziembowska" email="[EMAIL PROTECTED]"/>
<person name="Davanum Srinivas" email="[EMAIL
PROTECTED]"/>
</authors>
- <abstract>This document describes the stream generator of
Cocoon 2.</abstract>
+ <abstract>This document describes the stream generator of
@[EMAIL PROTECTED]</abstract>
</header>
<body>
<s1 title="Stream Generator">
1.1.1.1.2.1 +3 -3 xml-cocoon2/xdocs/svg-serializer.xml
Index: svg-serializer.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/svg-serializer.xml,v
retrieving revision 1.1.1.1
retrieving revision 1.1.1.1.2.1
diff -u -r1.1.1.1 -r1.1.1.1.2.1
--- svg-serializer.xml 2001/05/09 20:50:23 1.1.1.1
+++ svg-serializer.xml 2001/07/19 14:20:01 1.1.1.1.2.1
@@ -18,7 +18,7 @@
valid Scalable Vector Graphic documents
(currently to the
2000-08-02 Candidate Recommendation
specification) and
renders it to an image which is served
just like any other
- document in Cocoon 2.
+ document in @[EMAIL PROTECTED]
</p>
<p>
Why would you want to do this? Well,
charts can be produced from the
@@ -27,7 +27,7 @@
beautified.
</p>
<note>
- For examples of this serializer, see
the Cocoon 2 welcome
+ For examples of this serializer, see
the @docname@ welcome
page in the distribution (<code>[cocoon2
root]/welcome</code>).
</note>
@@ -64,7 +64,7 @@
stream is generated from the
file <code>sample.svg</code>, which is
serialized using the
<code>svg2jpeg</code> serializer. This
serializer is configured to use
a specific transcoder. The MIME type
- is specified so that Cocoon 2
can tell the client which type the
+ is specified so that @docname@
can tell the client which type the
document is. It can be seen
that in general the use of this
serializer is identical to that
of the other serializers.
</p>
1.1.2.2 +2 -2 xml-cocoon2/xdocs/svgjpeg-serializer.xml
Index: svgjpeg-serializer.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/svgjpeg-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
--- svgjpeg-serializer.xml 2001/07/12 21:07:23 1.1.2.1
+++ svgjpeg-serializer.xml 2001/07/19 14:20:01 1.1.2.2
@@ -3,13 +3,13 @@
<document>
<header>
<title>SVG/JPEG Serializer</title>
- <subtitle>in Cocoon 2</subtitle>
+ <subtitle>in @doctitle@</subtitle>
<version>0.9</version>
<type>Technical document</type>
<authors>
<person name="Carsten Ziegeler" email="[EMAIL
PROTECTED]"/>
</authors>
- <abstract>This document describes the svg/jpeg serializer of
Cocoon 2.</abstract>
+ <abstract>This document describes the svg/jpeg serializer of
@[EMAIL PROTECTED]</abstract>
</header>
<body>
<s1 title="SVG/JPEG Serializer">
1.1.2.2 +2 -2 xml-cocoon2/xdocs/svgpng-serializer.xml
Index: svgpng-serializer.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/svgpng-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
--- svgpng-serializer.xml 2001/07/12 21:07:26 1.1.2.1
+++ svgpng-serializer.xml 2001/07/19 14:20:01 1.1.2.2
@@ -3,13 +3,13 @@
<document>
<header>
<title>SVG/PNG Serializer</title>
- <subtitle>in Cocoon 2</subtitle>
+ <subtitle>in @doctitle@</subtitle>
<version>0.9</version>
<type>Technical document</type>
<authors>
<person name="Carsten Ziegeler" email="[EMAIL
PROTECTED]"/>
</authors>
- <abstract>This document describes the svg/png serializer of
Cocoon 2.</abstract>
+ <abstract>This document describes the svg/png serializer of
@[EMAIL PROTECTED]</abstract>
</header>
<body>
<s1 title="SVG/PNG Serializer">
1.1.2.2 +2 -2 xml-cocoon2/xdocs/svgxml-serializer.xml
Index: svgxml-serializer.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/svgxml-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
--- svgxml-serializer.xml 2001/07/12 21:07:30 1.1.2.1
+++ svgxml-serializer.xml 2001/07/19 14:20:01 1.1.2.2
@@ -3,13 +3,13 @@
<document>
<header>
<title>SVG/XML Serializer</title>
- <subtitle>in Cocoon 2</subtitle>
+ <subtitle>in @doctitle@</subtitle>
<version>0.9</version>
<type>Technical document</type>
<authors>
<person name="Carsten Ziegeler" email="[EMAIL
PROTECTED]"/>
</authors>
- <abstract>This document describes the svg/xml serializer of
Cocoon 2.</abstract>
+ <abstract>This document describes the svg/xml serializer of
@[EMAIL PROTECTED]</abstract>
</header>
<body>
<s1 title="SVG/XML Serializer">
1.1.2.2 +2 -2 xml-cocoon2/xdocs/text-serializer.xml
Index: text-serializer.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/text-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
--- text-serializer.xml 2001/07/12 21:07:33 1.1.2.1
+++ text-serializer.xml 2001/07/19 14:20:01 1.1.2.2
@@ -3,13 +3,13 @@
<document>
<header>
<title>Text Serializer</title>
- <subtitle>in Cocoon 2</subtitle>
+ <subtitle>in @doctitle@</subtitle>
<version>0.9</version>
<type>Technical document</type>
<authors>
<person name="Carsten Ziegeler" email="[EMAIL
PROTECTED]"/>
</authors>
- <abstract>This document describes the text serializer of
Cocoon 2.</abstract>
+ <abstract>This document describes the text serializer of
@[EMAIL PROTECTED]</abstract>
</header>
<body>
<s1 title="Text Serializer">
1.1.2.5 +4 -4 xml-cocoon2/xdocs/transformers.xml
Index: transformers.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/transformers.xml,v
retrieving revision 1.1.2.4
retrieving revision 1.1.2.5
diff -u -r1.1.2.4 -r1.1.2.5
--- transformers.xml 2001/07/18 07:42:21 1.1.2.4
+++ transformers.xml 2001/07/19 14:20:01 1.1.2.5
@@ -3,17 +3,17 @@
<document>
<header>
<title>Transformers</title>
- <subtitle>in Cocoon 2</subtitle>
+ <subtitle>in @doctitle@</subtitle>
<version>0.9</version>
<type>Technical document</type>
<authors>
<person name="Carsten Ziegeler" email="[EMAIL
PROTECTED]"/>
</authors>
- <abstract>This document describes all available transformers
of Cocoon 2.</abstract>
+ <abstract>This document describes all available transformers
of @[EMAIL PROTECTED]</abstract>
</header>
<body>
<s1 title="Goal">
- <p>This document lists all available transformers of
Cocoon 2 and
+ <p>This document lists all available transformers of
@doctitle@ and
describes their purpose.</p>
</s1>
<s1 title="Overview">
@@ -22,7 +22,7 @@
see <link href="sitemap.html">the sitemap</link>.
</p>
</s1>
- <s1 title="The Transformers in Apache Cocoon 2">
+ <s1 title="The Transformers in @doctitle@">
<ul>
<li><link href="xslt-transformer.html">XSLT
Transformer</link> (The default transformer)</li>
<li><link
href="extractor-transformer.html">Fragment Extractor Transformer</link></li>
1.3.2.3 +22 -22 xml-cocoon2/xdocs/uc2.xml
Index: uc2.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/uc2.xml,v
retrieving revision 1.3.2.2
retrieving revision 1.3.2.3
diff -u -r1.3.2.2 -r1.3.2.3
--- uc2.xml 2001/07/18 11:11:53 1.3.2.2
+++ uc2.xml 2001/07/19 14:20:01 1.3.2.3
@@ -31,7 +31,7 @@
</li>
<li>
<jump anchor="what-problems">
- What problem does Cocoon2 solve?
+ What problem does @docname@ solve?
</jump>
</li>
<li>
@@ -78,23 +78,23 @@
</ul>
<p>What You need not know:</p>
<ul>
- <li>Cocoon 1</li>
+ <li>@docname@ 1</li>
</ul>
</s1>
<anchor id="a-little-history"/>
<s1 title="A Little History">
- <s2 title="Cocoon1">
+ <s2 title="@[EMAIL PROTECTED]">
<ul>
- <li>Cocoon project was founded in Jan. 1999 by Stefano Mazzocchi as
an open source project under Apache Software Foundation.</li>
+ <li>@docname@ project was founded in Jan. 1999 by Stefano Mazzocchi
as an open source project under Apache Software Foundation.</li>
<li>Started as a simple servlet for XSL styling of XML content.</li>
<li>Was based on DOM level 1 API. This choice turned out to be
quite limiting for speed/memory efficiency.</li>
<li>Used reactor pattern to connect components. This allowed the
reaction instructions to be placed inside the documents. Though appealing, it
caused difficulties in managing highly dynamic web-sites.</li>
<li>Allowed context overlap to happen by having processing
instructions in documents/stylesheets.</li>
</ul>
</s2>
- <s2 title="Cocoon2">
+ <s2 title="@doctitle@">
<ul>
- <li>A separate codebase to incorporate Cocoon1 learnings.</li>
+ <li>A separate codebase to incorporate @[EMAIL PROTECTED]
learnings.</li>
<li>Designed for execution speed/memory efficiency and scalability
to process very large documents by switching processing model from DOM to
SAX.</li>
<li>Centralizes the management functions by allowing processing
pipeline specification in a sitemap (an XML file), replacing the embedded
processing instruction model.</li>
<li>Better support for pre-compilation, pre-generation and caching
for better performance.</li>
@@ -102,7 +102,7 @@
</s2>
</s1>
<anchor id="what-problems"/>
- <s1 title="What problem does Cocoon2 solve?">
+ <s1 title="What problem does @doctitle@ solve?">
<p>Basic problem to be solved:</p>
<s2 title="Separation of content, style, logic and management functions
in an XML content based web site (and web services).">
<figure src="images/pyramid-model.gif" alt="The @Name@ Pyramid Model
of Contracts"/>
@@ -130,7 +130,7 @@
<anchor id="c2-architecture"/>
<s1 title="Architecture.">
<figure src="images/architecture.gif" alt="Architecture"/>
- <s2 title="Core Cocoon">
+ <s2 title="Core @docname@">
<ul>
<li>Avalon framework for logging, configuration, threading, context
etc.</li>
<li>Caching mechanism</li>
@@ -140,7 +140,7 @@
<li>...</li>
</ul>
</s2>
- <s2 title="Cocoon Components">
+ <s2 title="@docname@ Components">
<ul>
<li>Specific generators</li>
<li>Specific transformers</li>
@@ -243,7 +243,7 @@
</s3>
<s3 title="Logicsheet as tag library">
<ul>
- <li>The logicsheet is packaged as a reusable tag library and
registered with Cocoon in cocoon.xconf file.</li>
+ <li>The logicsheet is packaged as a reusable tag library and
registered with @docname@ in cocoon.xconf file.</li>
<li>Tag library has a namespace declaration, declared in the
original logicsheet and matched in <code><xsp:page></code> xmlns:...
attribute.</li>
<li>Effective separation of content, logic and management</li>
</ul>
@@ -274,7 +274,7 @@
...
</map:sitemap>
]]></source>
- <p>Sitemap contains configuration information for a Cocoon engine:</p>
+ <p>Sitemap contains configuration information for a @docname@
engine:</p>
<ul>
<li>list of matchers</li>
<li>list of generators</li>
@@ -296,7 +296,7 @@
<li>wildcard matcher</li>
<li>regexp matcher</li>
</ul>
- <p>More matchers can be added without modifying Cocoon.</p>
+ <p>More matchers can be added without modifying @[EMAIL PROTECTED]</p>
<p>Matchers help in specifying a specific pipeline processing for a
group of URIs.</p>
<p>Sitemap entries for different types of matchers</p>
<source><![CDATA[
@@ -327,7 +327,7 @@
<li>Request generator</li>
<li>...</li>
</ul>
- <p>More generators can be added without modifying Cocoon.</p>
+ <p>More generators can be added without modifying @[EMAIL
PROTECTED]</p>
<p>Sitemap entries for different types of generators</p>
<source><![CDATA[
<map:generators default="file">
@@ -369,7 +369,7 @@
<li>...</li>
</ul>
<p>Log Transformer is a good debugging tool.</p>
- <p>More transformers can be added without modifying Cocoon.</p>
+ <p>More transformers can be added without modifying @[EMAIL
PROTECTED]</p>
<p>Sitemap entries for different types of transformers</p>
<source><![CDATA[
<map:transformers default="xslt">
@@ -402,7 +402,7 @@
<li>XML Serializer</li>
<li>...</li>
</ul>
- <p>More serializers can be added without modifying Cocoon.</p>
+ <p>More serializers can be added without modifying @[EMAIL
PROTECTED]</p>
<p>Sitemap entries for different types of serializers</p>
<source><![CDATA[
<map:serializers default="html">
@@ -441,7 +441,7 @@
<p>Primary mechanism to add program logic (code) to XSPs.</p>
<p>These need to be registered in configuration file cocoon.xconf.</p>
<p>Logicsheets are used by the generator to transform XML structure
before generating program.</p>
- <p>Cocoon comes with a no. of built-in logic sheets:</p>
+ <p>@docname@ comes with a no. of built-in logic sheets:</p>
<ul>
<li>request.xsl</li>
<li>response.xsl</li>
@@ -489,17 +489,17 @@
</s1>
<anchor id="cocoon-configuration"/>
<s1 title="@Name@ Configuration.">
- <p>Cocoon is highly configurable. Main configuration files, assuming
Cocoon deployment as a servlet in a servlet container, are (directory locations
assume Tomcat servlet container):</p>
+ <p>@docname@ is highly configurable. Main configuration files, assuming
@docname@ deployment as a servlet in a servlet container, are (directory
locations assume Tomcat servlet container):</p>
<ul>
<li><code>sitemap.xmap</code>: the sitemap file. By default, located
in <code>$TOMCAT_HOME/webapps/cocoon</code> directory.</li>
<li><code>cocoon.xconf</code>: configuration file having logicsheet
registrations. Specifies, sitemap.xmap location and other such parameters. By
default, located in <code>$TOMCAT_HOME/webapps/cocoon</code> directory.</li>
<li><code>web.xml</code>: servlet deployment descriptor. Specifies
location of cocoon.xconf, log file location and other such parameters. Located
in <code>$TOMCAT_HOME/webapps/cocoon/WEB-INF</code> directory.</li>
- <li><code>cocoon.roles</code>: mapping file for Core Cocoon
components name and implementation classes. For example, if you want to use a
parser other than the default one, you need to modify this file.</li>
+ <li><code>cocoon.roles</code>: mapping file for Core @docname@
components name and implementation classes. For example, if you want to use a
parser other than the default one, you need to modify this file.</li>
</ul>
</s1>
<anchor id="work-area"/>
<s1 title="@Name@ Work Area">
- <p>Cocoon produces execution log entries for debugging/auditing.</p>
+ <p>@docname@ produces execution log entries for debugging/auditing.</p>
<ul>
<li>The amount of data to be logged can be controlled by
log-level parameter in web.xml file. The default is DEBUG
@@ -508,7 +508,7 @@
<code>$TOMCAT_HOME/webapps/cocoon/WEB-INF/logs/cocoon.log</code>.</li>
</ul>
- <p>Cocoon keeps the generated .java files in a directory tree
+ <p>@docname@ keeps the generated .java files in a directory tree
starting at (by default):</p>
<code>$TOMCAT_HOME/webapps/work/localhost_8080%2Fcocoon/org/apache/cocoon/www</code>.
@@ -519,7 +519,7 @@
<anchor id="use-with-tomcat"/>
<s1 title="Use with Tomcat">
<p>Download Tomcat from Apache site.</p>
- <p>Download Cocoon sources from Apache CVS (binaries not available for
Cocoon2 yet). [Command assume UNIX Bourne shell]</p>
+ <p>Download @docname@ sources from Apache CVS. [Command assume UNIX
Bourne shell]</p>
<source><![CDATA[
export CVSROOT=:pserver:[EMAIL PROTECTED]:/home/cvspublic
cvs login
@@ -528,7 +528,7 @@
]]></source>
<p>Build sources as per instruction in Install file.</p>
<p>Move the <code>cocoon.war</code> file to
<code>$TOMCAT_HOME/webapps</code> directory.</p>
- <p>Start the servlet engine. Type-in the URL
<code>http://localhost:8080/cocoon</code> in your browser. You should see the
Cocoon welcome message.</p>
+ <p>Start the servlet engine. Type-in the URL
<code>http://localhost:8080/cocoon</code> in your browser. You should see the
@docname@ welcome message.</p>
<p>Consult Install file if you face problems.</p>
</s1>
</body>
1.1.2.2 +2 -2 xml-cocoon2/xdocs/velocity-generator.xml
Index: velocity-generator.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/velocity-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
--- velocity-generator.xml 2001/07/12 21:07:38 1.1.2.1
+++ velocity-generator.xml 2001/07/19 14:20:01 1.1.2.2
@@ -3,13 +3,13 @@
<document>
<header>
<title>Velocity 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="[EMAIL
PROTECTED]"/>
</authors>
- <abstract>This document describes the file velocity of Cocoon
2.</abstract>
+ <abstract>This document describes the file velocity of @[EMAIL
PROTECTED]</abstract>
</header>
<body>
<s1 title="Velocity Generator">
1.1.2.2 +2 -2 xml-cocoon2/xdocs/vrml-serializer.xml
Index: vrml-serializer.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/vrml-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
--- vrml-serializer.xml 2001/07/12 21:07:42 1.1.2.1
+++ vrml-serializer.xml 2001/07/19 14:20:01 1.1.2.2
@@ -3,13 +3,13 @@
<document>
<header>
<title>VRML Serializer</title>
- <subtitle>in Cocoon 2</subtitle>
+ <subtitle>in @doctitle@</subtitle>
<version>0.9</version>
<type>Technical document</type>
<authors>
<person name="Carsten Ziegeler" email="[EMAIL
PROTECTED]"/>
</authors>
- <abstract>This document describes the vrml serializer of
Cocoon 2.</abstract>
+ <abstract>This document describes the vrml serializer of
@[EMAIL PROTECTED]</abstract>
</header>
<body>
<s1 title="VRML Serializer">
1.1.2.2 +2 -2 xml-cocoon2/xdocs/wap-serializer.xml
Index: wap-serializer.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/wap-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
--- wap-serializer.xml 2001/07/12 21:07:45 1.1.2.1
+++ wap-serializer.xml 2001/07/19 14:20:01 1.1.2.2
@@ -3,13 +3,13 @@
<document>
<header>
<title>WAP/WML Serializer</title>
- <subtitle>in Cocoon 2</subtitle>
+ <subtitle>in @doctitle@</subtitle>
<version>0.9</version>
<type>Technical document</type>
<authors>
<person name="Carsten Ziegeler" email="[EMAIL
PROTECTED]"/>
</authors>
- <abstract>This document describes the wap/wml serializer of
Cocoon 2.</abstract>
+ <abstract>This document describes the wap/wml serializer of
@[EMAIL PROTECTED]</abstract>
</header>
<body>
<s1 title="WML/WAP Serializer">
1.1.2.2 +1 -1 xml-cocoon2/xdocs/who.xml
Index: who.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/who.xml,v
retrieving revision 1.1.2.1
retrieving revision 1.1.2.2
diff -u -r1.1.2.1 -r1.1.2.2
--- who.xml 2001/06/19 17:28:23 1.1.2.1
+++ who.xml 2001/07/19 14:20:01 1.1.2.2
@@ -14,7 +14,7 @@
<s1 title="Who we are">
<p>
- The Cocoon Project operates on a meritocracy: the more you do, the more
+ The @docname@ Project operates on a meritocracy: the more you do, the
more
responsibility you will obtain. This page lists all of the people who
have
gone the extra mile and are Committers. If you would like to get
involved,
the first step is to join the mailing lists.
1.1.2.2 +2 -2 xml-cocoon2/xdocs/writedomsession-transformer.xml
Index: writedomsession-transformer.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/writedomsession-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
--- writedomsession-transformer.xml 2001/07/18 07:42:21 1.1.2.1
+++ writedomsession-transformer.xml 2001/07/19 14:20:01 1.1.2.2
@@ -3,7 +3,7 @@
<document>
<header>
<title>Write DOM Session Transformer</title>
- <subtitle>in Cocoon 2</subtitle>
+ <subtitle>in @doctitle@</subtitle>
<version>0.9</version>
<type>Technical document</type>
<authors>
@@ -11,7 +11,7 @@
<person name="Sven Beauprez" email="[EMAIL PROTECTED]"/>
<person name="Davanum Srinivas" email="[EMAIL
PROTECTED]"/>
</authors>
- <abstract>This document describes the write dom session
transformer of Cocoon 2.</abstract>
+ <abstract>This document describes the write dom session
transformer of @[EMAIL PROTECTED]</abstract>
</header>
<body>
<s1 title="Write DOM Session Transformer">
1.1.2.3 +2 -2 xml-cocoon2/xdocs/xinclude-transformer.xml
Index: xinclude-transformer.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/xinclude-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
--- xinclude-transformer.xml 2001/07/17 14:44:52 1.1.2.2
+++ xinclude-transformer.xml 2001/07/19 14:20:01 1.1.2.3
@@ -3,13 +3,13 @@
<document>
<header>
<title>XInclude 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="[EMAIL
PROTECTED]"/>
</authors>
- <abstract>This document describes the XInclude transformer of
Cocoon 2.</abstract>
+ <abstract>This document describes the XInclude transformer of
@[EMAIL PROTECTED]</abstract>
</header>
<body>
<s1 title="XInclude Transformer">
1.1.2.2 +2 -2 xml-cocoon2/xdocs/xml-serializer.xml
Index: xml-serializer.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/xml-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
--- xml-serializer.xml 2001/07/12 21:07:55 1.1.2.1
+++ xml-serializer.xml 2001/07/19 14:20:01 1.1.2.2
@@ -3,13 +3,13 @@
<document>
<header>
<title>XML Serializer</title>
- <subtitle>in Cocoon 2</subtitle>
+ <subtitle>in @doctitle@</subtitle>
<version>0.9</version>
<type>Technical document</type>
<authors>
<person name="Carsten Ziegeler" email="[EMAIL
PROTECTED]"/>
</authors>
- <abstract>This document describes the xml serializer of Cocoon
2.</abstract>
+ <abstract>This document describes the xml serializer of
@[EMAIL PROTECTED]</abstract>
</header>
<body>
<s1 title="XML Serializer">
1.1.2.3 +2 -2 xml-cocoon2/xdocs/xslt-transformer.xml
Index: xslt-transformer.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/xslt-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
--- xslt-transformer.xml 2001/07/18 11:11:53 1.1.2.2
+++ xslt-transformer.xml 2001/07/19 14:20:01 1.1.2.3
@@ -3,13 +3,13 @@
<document>
<header>
<title>XSLT 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="[EMAIL
PROTECTED]"/>
</authors>
- <abstract>This document describes the xslt transformer of
Cocoon 2.</abstract>
+ <abstract>This document describes the xslt transformer of
@[EMAIL PROTECTED]</abstract>
</header>
<body>
<s1 title="Trax/XSLT Transformer">
1.2.2.2 +20 -20 xml-cocoon2/xdocs/xsp-internals.xml
Index: xsp-internals.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/xsp-internals.xml,v
retrieving revision 1.2.2.1
retrieving revision 1.2.2.2
diff -u -r1.2.2.1 -r1.2.2.2
--- xsp-internals.xml 2001/07/18 11:11:53 1.2.2.1
+++ xsp-internals.xml 2001/07/19 14:20:01 1.2.2.2
@@ -16,7 +16,7 @@
<body>
<s1 title="Index">
<p>
- This document presents Cocoon's dynamic markup language
+ This document presents @docname@'s dynamic markup language
framework and its use in implementing XSP:
</p>
@@ -28,7 +28,7 @@
</li>
<li>
<jump anchor="cocoon-generators">
- XSP and Cocoon Generators
+ XSP and @docname@ Generators
</jump>
</li>
<li>
@@ -130,9 +130,9 @@
</s1>
<anchor id="cocoon-generators"/>
- <s1 title="XSP and Cocoon Generators">
+ <s1 title="XSP and @docname@ Generators">
<p>
- As a rule, XSP pages are translated into Cocoon
+ As a rule, XSP pages are translated into @docname@
<link href="javadocs/org/apache/cocoon/generators/Generator.html">
<code><em>Generator</em></code>'s.
</link>
@@ -144,7 +144,7 @@
<link
href="javadocs/org/apache/cocoon/generators/ServerPagesGenerator.html">
<code><em>ServerPagesGenerator</em></code>,
</link>
- a proxy that uses Cocoon's
+ a proxy that uses @docname@'s
<jump anchor="program-generator"><code>ProgramGenerator</code></jump>
component to load pages and subsequently delegates actual SAX event
generation to them.
@@ -152,10 +152,10 @@
<note>
The terms <code>Generator</code> and <code>ProgramGenerator</code> are
- somewhat confusing. Here, <code>Generator</code> refers to a Cocoon
+ somewhat confusing. Here, <code>Generator</code> refers to a @docname@
<code>org.apache.cocoon.generators.Generator</code> instance
responsible
- for the initial feeding of Cocoon's SAX pipeline.
- <code>ProgramGenerator</code>, on the other hand, refers to a Cocoon
+ for the initial feeding of @docname@'s SAX pipeline.
+ <code>ProgramGenerator</code>, on the other hand, refers to a @docname@
component responsible for building and executing programs derived from
XML
documents containing dynamic markup:
<link
href="javadocs/org/apache/cocoon/components/language/generator/ProgramGenerator.html">
@@ -297,9 +297,9 @@
<code>ServerPagesGenerator</code> to assert whether dynamic content
should
not be regenerated for a given request. The default implementation
unconditionally returns <code>true</code>, but can be overridden by XSP
- pages based on their interpretation of the Cocoon <code>request</code>
+ pages based on their interpretation of the @docname@
<code>request</code>
object. This is an <em>experimental</em> feature that will become
- meaningful only when a SAX-event caching mechanism is added to Cocoon.
+ meaningful only when a SAX-event caching mechanism is added to @[EMAIL
PROTECTED]
</p>
<p>
@@ -314,7 +314,7 @@
<anchor id="programming-language"/>
<s1 title="The Programming Language Processor">
<p>
- A Cocoon's
+ A @docname@'s
<link
href="javadocs/org/apache/cocoon/components/language/programming/ProgrammingLanguage.html">
<code>ProgrammingLanguage</code>
</link>
@@ -803,9 +803,9 @@
</s2>
<anchor id="class-loader"/>
- <s2 title="The Cocoon Class Loader">
+ <s2 title="The @docname@ Class Loader">
<p>
- To circumvent standard Java class loaders limitation, Cocoon provides
a
+ To circumvent standard Java class loaders limitation, @docname@
provides a
simple customized class loader
<link
href="javadocs/org/apache/cocoon/components/classloader/RepositoryClassLoader.html">
(<code>RepositoryClassLoader</code>)
@@ -923,7 +923,7 @@
<note>
Despite being supported by BSF, Rhino Javascript is separately
- supported by Cocoon as a compiled language in order to take
+ supported by @docname@ as a compiled language in order to take
advantage of automatic class reloading and persistent class file
storage.
</note>
@@ -942,7 +942,7 @@
<anchor id="markup-language"/>
<s1 title="The Markup Language Processor">
<p>
- A Cocoon's
+ A @docname@'s
<link
href="javadocs/org/apache/cocoon/components/language/markup/MarkupLanguage.html">
<code>MarkupLanguage</code>
@@ -1032,7 +1032,7 @@
The current code generation strategy is DOM-based. In principle,
this is adequate because document preprocessing may need random
access to document nodes. Code generation is being reconsidered,
- however, to overcome this and make it possible to reuse Cocoon's
+ however, to overcome this and make it possible to reuse @docname@'s
SAX-based filtering pipeline.
</note>
@@ -1401,11 +1401,11 @@
<p>
XSP for Java currently provides only 2 builtin logicsheets:
<code>request</code> and <code>response</code>, associated
- with their corresponding Cocoon counterparts.
+ with their corresponding @docname@ counterparts.
</p>
<note>
- A mechanism is needed for Cocoon to pass additional objects
+ A mechanism is needed for @docname@ to pass additional objects
to XSP pages. In particular, for the servlet execution
environment, access to servlet objects is a must.
</note>
@@ -1415,7 +1415,7 @@
<anchor id="dom-xsp"/>
<s1 title="The DOM-XSP Markup Language">
<p>
- The new, SAX-based XSP version for Cocoon2 is not backwards
+ The new, SAX-based XSP version for @doctitle@ is not backwards
compatible with its DOM-based former self.
</p>
@@ -1577,7 +1577,7 @@
<s1 title="Named Components">
<p>
In order to support pluggable markup and programming languages,
- a new abstraction was added to Cocoon's <code>arch</code>
+ a new abstraction was added to @docname@'s <code>arch</code>
core interfaces:
<link href="javadocs/org/apache/arch/named/NamedComponent.html">
<code>NamedComponent</code>.
1.1.1.1.2.1 +2 -2 xml-cocoon2/xdocs/xsp.xml
Index: xsp.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/xsp.xml,v
retrieving revision 1.1.1.1
retrieving revision 1.1.1.1.2.1
diff -u -r1.1.1.1 -r1.1.1.1.2.1
--- xsp.xml 2001/05/09 20:50:24 1.1.1.1
+++ xsp.xml 2001/07/19 14:20:01 1.1.1.1.2.1
@@ -7,13 +7,13 @@
not together), I give you a list of pointers in the sequence
you should read
them.</p>
<ol>
- <li>Get Cocoon 2 <link href="install.html">up and
running</link>. Surf
+ <li>Get @doctitle@ <link href="install.html">up and
running</link>. Surf
to <code>[webhost]/cocoon/slides/slides?section=4</code> and
following. This
gives you a first insight in the XSP ground idea.</li>
<li>Read the XSP Logicsheets page. This tells you how to use
and make
your own XSP logicsheets and XSP pages.</li>
<li>If you're still hungry for more, read the XSP Internals
page. This
- describes how XSP's are handled internally by Cocoon 2.</li>
+ describes how XSP's are handled internally by @[EMAIL
PROTECTED]</li>
</ol>
</s1>
</body>
1.1.2.3 +3 -3 xml-cocoon2/xdocs/xt-transformer.xml
Index: xt-transformer.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/xt-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
--- xt-transformer.xml 2001/07/17 09:28:17 1.1.2.2
+++ xt-transformer.xml 2001/07/19 14:20:01 1.1.2.3
@@ -3,13 +3,13 @@
<document>
<header>
<title>XT 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="[EMAIL
PROTECTED]"/>
</authors>
- <abstract>This document describes the XT transformer of Cocoon
2.</abstract>
+ <abstract>This document describes the XT transformer of
@[EMAIL PROTECTED]</abstract>
</header>
<body>
<s1 title="XT Transformer">
@@ -17,7 +17,7 @@
which uses the xt transformer instead of a trax
compatible
transformer.</p>
<p>This transformer is optional and requires the xt
package
- in the lib directory when building cocoon 2. However,
+ in the lib directory when building @[EMAIL PROTECTED]
However,
the distribution includes this package already.</p>
<ul>
<li>Name : xt</li>
----------------------------------------------------------------------
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
