crossley 2003/05/29 02:46:24
Modified: src/webapp sitemap.xmap
Log:
Polish the explanatory text.
Revision Changes Path
1.19 +12 -11 cocoon-2.1/src/webapp/sitemap.xmap
Index: sitemap.xmap
===================================================================
RCS file: /home/cvs/cocoon-2.1/src/webapp/sitemap.xmap,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- sitemap.xmap 15 May 2003 14:10:20 -0000 1.18
+++ sitemap.xmap 29 May 2003 09:46:24 -0000 1.19
@@ -9,7 +9,8 @@
| documentation. For specific components, have a look also at the
| javadocs for them. Most pipelines are present to demonstrate some
| feature or technique, often they are explained in more detail in
- | the accompanying documentation.
+ | the accompanying documentation. The sitemaps which come with each
+ | sample and each block will help to explain.
|
| CVS $Id$
+-->
@@ -29,9 +30,9 @@
| consumes these events and produces a byte stream.
|
| Some things to note here: each generator has a unique name, this
- | name is mapped to a java class, one name is declared as default
- | generator. In addition each generator may have additional
- | configurations as child elements.
+ | name is mapped to a java class, one name is declared as the default
+ | generator. Each generator may have additional configurations as
+ | child elements.
|
| Additional attributes are targeted at the component manager. The optional
| "label" attribute is relevant for the view concept below. The optional
@@ -47,7 +48,7 @@
| generators by using different names. No configuration options are
| shared between these instances, however.
|
- | All components follow this schema.
+ | All components follow this scheme.
+-->
<map:generators default="file">
<map:generator label="content,data" logger="sitemap.generator.file" name="file"
pool-grow="4" pool-max="32" pool-min="8"
src="org.apache.cocoon.generation.FileGenerator"/>
@@ -420,7 +421,7 @@
<!--+
| This transformer gets the input SAX events and transforms them
- | using the default trasformer (the XSLT transformer) thus
+ | using the default transformer (the XSLT transformer) thus
| applying the XSLT stylesheet indicated in the "src" attribute
| and sending the output down the pipeline to be processed by the
| next stage.
@@ -441,13 +442,13 @@
<!--+
| The default matching is also capable of matching more than a
- | single request by the use of 'wildcards'. There are two kins of
+ | single request by the use of 'wildcards'. There are two kinds of
| wildcards:
|
| "*" means "anything that does not contain a path separator"
| "**" means "anything including path separators"
|
- | The tokens matched by the wildcards are put passed over as sitemap
+ | The tokens matched by the wildcards are passed over as sitemap
| variables. Those variables can be accessed using the '{...}' syntax
| inside the attributes. The URI-matching tokens are associated to
| numbered variables, as shown in the following match that processes all
@@ -528,12 +529,12 @@
<!--+
| At the very end of a pipeline, you can catch the errors triggered
| by the pipeline execution. The error handler is an internal sitemap
- | component that when triggered by an error takes over the normal
+ | component that, when triggered by an error, takes over the normal
| pipeline execution.
| You can here use the "notifying" generator that produces an XML
| representation and further manipulate this document for presentation
| on screen.
- | You can also use any other generator you want if you don't want the
+ | You can also use any other generator if you don't want the
| error to be displayed on screen. The "exception" selector can help
| you to define different screens for different error types.
+-->
