svn commit: r1329677 [9/27] - in /cocoon/site/site/2.2/core-modules: ./ core/ core/2.2/ core/2.2/css/ core/2.2/images/ core/2.2/js/ core/css/ core/images/ core/images/logos/ core/js/ css/ images/ js/
[email protected] Tue, 24 Apr 2012 12:40:02 -0000
Newsgroups
gmane.text.xml.cocoon.cvs
Message-ID
<[email protected] >
Modified: cocoon/site/site/2.2/core-modules/core/2.2/689_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.2/core-modules/core/2.2/689_1_1.html?rev=1329677&r1=1329676&r2=1329677&view=diff
==============================================================================
--- cocoon/site/site/2.2/core-modules/core/2.2/689_1_1.html (original)
+++ cocoon/site/site/2.2/core-modules/core/2.2/689_1_1.html Tue Apr 24 12:39:52 2012
@@ -29,17 +29,13 @@
<head>
<title> Cocoon Core - XML Pipeline Contracts
</title>
- <style type="text/css" media="all">
- @import url("./css/maven-base.css");
- @import url("./css/maven-theme.css");
- @import url("./css/site.css");
- </style>
+ <link rel="stylesheet" href="./css/apache-cocoon-thien-maven-skin.min.css" />
<link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
- <script src="./js/getBlank.js" language="javascript" type="text/javascript"></script>
- <meta name="author" content="The Cocoon Community" />
- <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+ <script src="./js/apache-cocoon-thien-maven-skin.min.js" language="javascript" type="text/javascript"></script>
+ <meta name="author" content="Apache Cocoon Documentation Team" />
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
</head>
- <body>
+ <body onload="javascript:prettyPrint();">
<div id="breadtrail">
<p><a href="http://www.apache.org">Apache</a> » <a href="../../../../">Cocoon</a> »</p>
</div>
@@ -77,7 +73,7 @@
<li><a href="../../../../2.2/core-modules/">Core <span class="pl-version-small">2.2</span></a></li>
<li><a href="../../../../2.2/blocks/">Blocks <span class="pl-version-small">2.2</span></a></li>
<li><a href="../../../../2.2/maven-plugins/">Maven Plugins <span class="pl-version-small">2.2</span></a></li>
- <li><strong><a href="../../../..//3.0/">Cocoon 3.0 <span class="pl-version-small">[alpha]</span></a></em></strong></li>
+ <li><strong><a href="../../../..//3.0/">Cocoon 3.0</a></em></strong></li>
<li><strong><a href="../../../../subprojects/">Subprojects</a></strong></li>
</ul>
</div>
@@ -92,7 +88,7 @@
<ul>
<li >
- <a href="1270_1_1.html">Introduction</a>
+ <a href="index.html">Introduction</a>
</li>
</ul>
</li>
@@ -315,8 +311,6 @@
-
-
<li class='menuCollapse'>
<a href="842_1_1.html">Reference</a>
@@ -604,7 +598,7 @@
</li>
<li >
- <a href="1380_1_1.html">Using Control Flow</a>
+ <a href="1380_1_1.html">Using Control Flow</a>
</li>
</ul>
</li>
@@ -638,11 +632,11 @@
</li>
<li >
- <a href="1399_1_1.html">Logging configuration</a>
+ <a href="1399_1_1.html">Logging Configuration</a>
</li>
<li >
- <a href="1259_1_1.html">Component Configurations</a>
+ <a href="1259_1_1.html">Component Configuration</a>
</li>
<li >
@@ -651,109 +645,107 @@
</ul>
</li>
<li>
- Project Documentation
+ Project Reports
<ul>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- <li class='menuCollapse'>
- <a href="project-info.html">Project Information</a>
- </li>
+ <li >
+ <a href="changes-report.html">Changes Report</a>
+ </li>
-
-
-
-
-
-
-
-
- <li class='menuCollapse'>
- <a href="project-reports.html">Project Reports</a>
- </li>
+ <li >
+ <a href="apidocs/">JavaDocs</a>
+ </li>
</ul>
</li>
</ul>
<div class="main">
- <div id="contentBody"><div id="bodyText"><h1 class="docTitle">XML Pipeline Contracts</h1><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">XML Pipeline Contracts</h1><p>The XMLProducer contract is part of how Cocoon assembles the actual SAX
+ <!-- Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License. -->
+ <div id="contentBody"><div id="bodyText"><h1 class="docTitle">XML Pipeline Contracts</h1><h1>XML Pipeline Contracts</h1><p>The XMLProducer contract is part of how Cocoon assembles the actual SAX
pipeline to handle a particular request. It is a little different from the
Sitemap related interfaces in that the focus is on the assembled pipeline
instead of the decisions of which elements to use in the pipeline. If you think
of the pipeline in a strict engineering mindset, an XMLProducer is a
-<em>source</em> of SAX events and an XMLConsumer is a <em>sink</em> for SAX
-events. An XMLPipe is both a source and a sink of SAX Events.</p><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">The XMLProducer</h2><p>The XMLProducer is a very simple beast, comprised of only one method to give
-the component the next element of the pipeline. Cocoon calls the
+<i>source</i> of SAX events and an XMLConsumer is a <i>sink</i> for SAX
+events.  An XMLPipe is both a source and a sink of SAX Events.</p><div class="section" style="background:none;padding:0;"><h2 style="background:none;padding:0;">The XMLProducer<a name="The_XMLProducer"></a></h2></div><p>The XMLProducer is a very simple beast, comprised of only one method to give
+the component the next element of the pipeline.  Cocoon calls the
<tt>setConsumer()</tt> method with the reference to the next XMLConsumer in the
-pipeline. The approach allows the XMLProducer to call the different SAX related
+pipeline.  The approach allows the XMLProducer to call the different SAX related
methods on the XMLConsumer without knowing ahead of time what that consumer will
-be. The design is very simple and very powerful in that it allows Cocoon to
-daisy chain several components in any order and then execute the pipeline.</p><p>Any producer can be paired with any consumer and we have a pipeline. The
+be.  The design is very simple and very powerful in that it allows Cocoon to
+daisy chain several components in any order and then execute the pipeline.</p><p>Any producer can be paired with any consumer and we have a pipeline.  The
core design is very powerful and allows the end user to mix and match sitemap
-components as they see fit. Cocoon will always call setConsumer() on every
+components as they see fit.  Cocoon will always call setConsumer() on every
XMLProducer in a pipeline or it will throw an exception saying that the pipeline
-is invalid (i.e. there is no serializer for the pipeline). The only contract
+is invalid (i.e. there is no serializer for the pipeline).  The only contract
that the XMLProducer has to worry about is that it must always make calls to the
-XMLConsumer passed in through the <tt>setConsumer()</tt> method.</p><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">The XMLConsumer</h2><p>An XMLConsumer is much more complex due to the interfaces it implements. An
-XMLConsumer is also a SAX ContentHandler and a SAX LexicalHandler. That means
-the XMLConsumer has to respect all the contracts with the SAX interfaces. SAX
-stands for Serialized API for XML. A document start, and each element start
-must be matched by the corresponding element end or document end. So why does
-Cocoon use SAX instead of manipulating a DOM? For two main reasons: performance
-and scalability. A DOM tree is much more heavy on system memory than successive
-calls to an API. SAX events can be sent as soon as they are read from the
+XMLConsumer passed in through the <tt>setConsumer()</tt> method.</p><div class="section" style="background:none;padding:0;"><h2 style="background:none;padding:0;">The XMLConsumer<a name="The_XMLConsumer"></a></h2></div><p>An XMLConsumer is much more complex due to the interfaces it implements.  An
+XMLConsumer is also a SAX ContentHandler and a SAX LexicalHandler.  That means
+the XMLConsumer has to respect all the contracts with the SAX interfaces.  SAX
+stands for Serialized API for XML.  A document start, and each element start
+must be matched by the corresponding element end or document end.  So why does
+Cocoon use SAX instead of manipulating a DOM?  For two main reasons: performance
+and scalability.  A DOM tree is much more heavy on system memory than successive
+calls to an API.  SAX events can be sent as soon as they are read from the
originating XML, the parsing and processing can happen essentially at the same
time.</p><p>Most people's needs will be handled just fine with the ContentHandler
-interface, as that declares your namespaces. However if you need lexical
+interface, as that declares your namespaces.  However if you need lexical
support to resolve entity names and such, you need the LexicalHandler
-interface. The AbstractXMLConsumer base class can make implementing this
+interface.  The AbstractXMLConsumer base class can make implementing this
interface easier so that you only need to override the events you intend to do
-anything with.</p><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">The XMLPipe</h2><p>The XMLPipe is both an XMLProducer and an XMLConsumer. All the Transformers
-implement this interface for example. By having an XMLPipe interface, we can
-chain more than one pipeline component together. What this means is that Cocoon
-will honor all the XMLProducer contracts in a pipeline first. The SAX pipeline
-will be completely assembled before any SAX calls are issued. Cocoon does not
-want any stray calls to get lost. There can be zero or more XMLPipes in a
+anything with.</p><div class="section" style="background:none;padding:0;"><h2 style="background:none;padding:0;">The XMLPipe<a name="The_XMLPipe"></a></h2></div><p>The XMLPipe is both an XMLProducer and an XMLConsumer.  All the Transformers
+implement this interface for example.  By having an XMLPipe interface, we can
+chain more than one pipeline component together.  What this means is that Cocoon
+will honor all the XMLProducer contracts in a pipeline first.  The SAX pipeline
+will be completely assembled before any SAX calls are issued.  Cocoon does not
+want any stray calls to get lost.  There can be zero or more XMLPipes in a
pipeline, but there must always be at least one XMLProducer and XMLConsumer
pair.</p><p>Because an XMLPipe is both a source and a sink for SAX events, the basic
contract that you need to worry about is that you must forward any SAX events on
-that you are not intercepting and transforming. As you receive your
+that you are not intercepting and transforming.  As you receive your
<tt>startDocument</tt> event, pass it on to the XMLConsumer you received as part
-of the XMLProducer side of the contract. An example ASCII art will help make it
-a bit more clear:</p><pre>XMLProducer -> (XMLConsumer)XMLPipe(XMLProducer) -> XMLConsumer
-</pre><p>A typical example would be using the FileGenerator (an XMLProducer), sending
+of the XMLProducer side of the contract.  An example ASCII art will help make it
+a bit more clear:</p><div><pre>XMLProducer -> (XMLConsumer)XMLPipe(XMLProducer) -> XMLConsumer
+</pre></div><p>A typical example would be using the FileGenerator (an XMLProducer), sending
events to an XSLTTransformer (an XMLPipe), which then sends events to an
-HTMLSerializer (an XMLConsumer). The XSLTTransformer acts as an XMLConsumer to
-the FileGenerator, and also acts as an XMLProducer to the HTMLSerializer. It is
+HTMLSerializer (an XMLConsumer).  The XSLTTransformer acts as an XMLConsumer to
+the FileGenerator, and also acts as an XMLProducer to the HTMLSerializer.  It is
still the responsibility of the XMLPipe component to ensure that the XML passed
on to the next component is valid--provided the XML received from the previous
-component is valid. In layman's terms it means if you don't intend to alter the
-input, just pass it on. In most cases we just want to transform a small snippet
-of XML. For example, inserting a snippet of XML based on an embedded element in
-a certain namespace. Anything that doesn't belong to the namespace you are
-worried about should be passed on as is.</p></div><div class="editUrl"><div><em>Errors and Improvements?</em> If you see any errors or potential improvements in this document please help
- us: <a href="http://cocoon.zones.apache.org/daisy/cdocs/689?branch=1&language=1">View, Edit or comment</a> on the latest development version (registration required).
- </div></div></div>
+component is valid.  In layman's terms it means if you don't intend to alter the
+input, just pass it on.  In most cases we just want to transform a small snippet
+of XML.  For example, inserting a snippet of XML based on an embedded element in
+a certain namespace.  Anything that doesn't belong to the namespace you are
+worried about should be passed on as is.</p></div></div>
+
</div>
</div>
<!-- end of content -->
<div id="footer">
- <p>©
- 1999-2008
+ <p>Copyright ©
+ 1999-2012
The Apache Software Foundation
+ All Rights Reserved.</p>
+
+ <p>
+ Apache Cocoon, Apache, the Apache feather logo, and the Apache Cocoon project logos are trademarks of The Apache Software Foundation.
+ All other marks mentioned may be trademarks or registered trademarks of their respective owners.
</p>
</div>
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript">
Modified: cocoon/site/site/2.2/core-modules/core/2.2/690_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.2/core-modules/core/2.2/690_1_1.html?rev=1329677&r1=1329676&r2=1329677&view=diff
==============================================================================
--- cocoon/site/site/2.2/core-modules/core/2.2/690_1_1.html (original)
+++ cocoon/site/site/2.2/core-modules/core/2.2/690_1_1.html Tue Apr 24 12:39:52 2012
@@ -29,17 +29,13 @@
<head>
<title> Cocoon Core - Writing Cache Efficient Components
</title>
- <style type="text/css" media="all">
- @import url("./css/maven-base.css");
- @import url("./css/maven-theme.css");
- @import url("./css/site.css");
- </style>
+ <link rel="stylesheet" href="./css/apache-cocoon-thien-maven-skin.min.css" />
<link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
- <script src="./js/getBlank.js" language="javascript" type="text/javascript"></script>
- <meta name="author" content="The Cocoon Community" />
- <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+ <script src="./js/apache-cocoon-thien-maven-skin.min.js" language="javascript" type="text/javascript"></script>
+ <meta name="author" content="Apache Cocoon Documentation Team" />
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
</head>
- <body>
+ <body onload="javascript:prettyPrint();">
<div id="breadtrail">
<p><a href="http://www.apache.org">Apache</a> » <a href="../../../../">Cocoon</a> »</p>
</div>
@@ -77,7 +73,7 @@
<li><a href="../../../../2.2/core-modules/">Core <span class="pl-version-small">2.2</span></a></li>
<li><a href="../../../../2.2/blocks/">Blocks <span class="pl-version-small">2.2</span></a></li>
<li><a href="../../../../2.2/maven-plugins/">Maven Plugins <span class="pl-version-small">2.2</span></a></li>
- <li><strong><a href="../../../..//3.0/">Cocoon 3.0 <span class="pl-version-small">[alpha]</span></a></em></strong></li>
+ <li><strong><a href="../../../..//3.0/">Cocoon 3.0</a></em></strong></li>
<li><strong><a href="../../../../subprojects/">Subprojects</a></strong></li>
</ul>
</div>
@@ -92,7 +88,7 @@
<ul>
<li >
- <a href="1270_1_1.html">Introduction</a>
+ <a href="index.html">Introduction</a>
</li>
</ul>
</li>
@@ -297,8 +293,6 @@
-
-
<li class='menuCollapse'>
<a href="842_1_1.html">Reference</a>
@@ -586,7 +580,7 @@
</li>
<li >
- <a href="1380_1_1.html">Using Control Flow</a>
+ <a href="1380_1_1.html">Using Control Flow</a>
</li>
</ul>
</li>
@@ -620,11 +614,11 @@
</li>
<li >
- <a href="1399_1_1.html">Logging configuration</a>
+ <a href="1399_1_1.html">Logging Configuration</a>
</li>
<li >
- <a href="1259_1_1.html">Component Configurations</a>
+ <a href="1259_1_1.html">Component Configuration</a>
</li>
<li >
@@ -633,45 +627,39 @@
</ul>
</li>
<li>
- Project Documentation
+ Project Reports
<ul>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- <li class='menuCollapse'>
- <a href="project-info.html">Project Information</a>
- </li>
+ <li >
+ <a href="changes-report.html">Changes Report</a>
+ </li>
-
-
-
-
-
-
-
-
- <li class='menuCollapse'>
- <a href="project-reports.html">Project Reports</a>
- </li>
+ <li >
+ <a href="apidocs/">JavaDocs</a>
+ </li>
</ul>
</li>
</ul>
<div class="main">
- <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Writing Cache Efficient Components</h1><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Writing Cache Efficient Components</h1><p>The bulk of this document is based heavily on documentation that Sylvain
+ <!-- Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License. -->
+ <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Writing Cache Efficient Components</h1><h1>Writing Cache Efficient Components</h1><p>The bulk of this document is based heavily on documentation that Sylvain
Wallez wrote on
-<a href="http://wiki.apache.org/cocoon/WritingForCacheEfficiency">Writing for
+<a class="externalLink" href="http://wiki.apache.org/cocoon/WritingForCacheEfficiency">Writing for
Cache Efficiency</a>. We're just reorganizing the information in a way that's
easier to digest. As you recall, to enable caching for a sitemap component you
have to implement the <a href="675_1_1.html">CacheableProcessingComponent
@@ -679,13 +667,13 @@ contracts</a>. Unfortunately, that does
the impact of verifying the cache validity of a component. The general strategy
that works best for cacheable components is lazy evaluation, or wait until the
last possible moment before you do your calculations--because you may not need
-them.</p><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Understanding the Order of Calls</h2><p>In order to know when to actually do the complex set up for any given
+them.</p><div class="section" style="background:none;padding:0;"><h2 style="background:none;padding:0;">Understanding the Order of Calls<a name="Understanding_the_Order_of_Calls"></a></h2></div><p>In order to know when to actually do the complex set up for any given
resource, it helps to know the exact order of calls as it relates to that
-component. From the perspective of this document you can assume the pipeline
-has already been set up, and we are now getting the components ready. Cocoon is
-deterministic in the sense that the call order is the same every time. Making
-your caching more efficient requires that you take advantage of this knowledge.
-First the sequence of events:</p><ol type="1">
+component.  From the perspective of this document you can assume the pipeline
+has already been set up, and we are now getting the components ready.  Cocoon is
+deterministic in the sense that the call order is the same every time.  Making
+your caching more efficient requires that you take advantage of this knowledge. 
+First the sequence of events:</p><ol style="list-style-type: decimal">
<li>Cocoon calls <tt>setup()</tt>--which includes serializers that implement
SitemapModelComponent.</li>
<li>Cocoon calls <tt>getMimeType()</tt> on the serializer (or reader).</li>
@@ -697,9 +685,9 @@ otherwise we jump to step 7.</li>
of calling your component; or if the Validity object is invalid, Cocoon will
then call your component; otherwise, Cocoon falls through to the next step.</li>
<li>If we have gotten to this point, Cocoon will call the <tt>getValidity()</tt>
-method on your CacheableProcessingComponent. Cocoon will then compare the
+method on your CacheableProcessingComponent.  Cocoon will then compare the
previous validity object against the new one, or if this is the first call to
-<tt>getValidity()</tt> then we validate the returned validity object. If the
+<tt>getValidity()</tt> then we validate the returned validity object.  If the
cache entry is valid Cocoon uses the cached results, otherwise we call the
component.</li>
<li>If the validity still can't be determined the next step is dependant on the
@@ -708,72 +696,76 @@ or default to safety and fresh data).</l
<li>Assuming we have gotten this far and the key is either not in the cache or
the entry is stale, Cocoon calls <tt>setXMLConsumer()</tt> on all the
XMLProducer components (typically generators and transformers), and
-<tt><tt>setOutputStream()</tt></tt> on the Serializer or Reader.</li>
+<tt>setOutputStream()</tt> on the Serializer or Reader.</li>
<li>Cocoon calls the <tt>generate()</tt> method on the Generator or Reader.</li>
</ol>That's a lot of steps, providing as many opportunities to use a cache as
-possible. It also provides the opportunity to delay when we incur certain
-checks until the last possible moment.<div class="note"><div><strong>Note: </strong>The Cocoon team has been working on an adaptive cache which
-performs cost calculations. It measures the cost of generating/transforming a
+possible.  It also provides the opportunity to delay when we incur certain
+checks until the last possible moment.<div class="note"><div><b>Note: </b>The Cocoon team has been working on an adaptive cache which
+performs cost calculations.  It measures the cost of generating/transforming a
result, the cost of determining its cache validity, and its own influence on the
-system. The bottom line is that just because something may be a valid entry, it
+system.  The bottom line is that just because something may be a valid entry, it
may still be cheaper to generate the resource in terms of that cost function
-than to use the cached value. The only guarantees that you have for when
+than to use the cached value.  The only guarantees that you have for when
something is going to be called are the methods from the sitemap interfaces and
the big component interfaces (i.e. the Generator, Transformer, Serializer, and
-Reader). Don't perform any critical setup inside a CacheableProcessingComponent
-method.</div></div><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Case Study: Improving the TraxTransformer</h2>Back in 2003, the TraxTransformer performed all caching and heavy payload
-setup within the <tt>setup()</tt> method. What this meant was that the
+Reader).  Don't perform any critical setup inside a CacheableProcessingComponent
+method.</div></div><div class="section" style="background:none;padding:0;"><h2 style="background:none;padding:0;">Case Study: Improving the TraxTransformer<a name="Case_Study:_Improving_the_TraxTransformer"></a></h2></div>Back in 2003, the TraxTransformer performed all caching and heavy payload
+setup within the <tt>setup()</tt> method.  What this meant was that the
TransformerHandler object was being created for the XSLT file at the same time
-the FileValidity object for that file was set up. The TransformerHandler object
-is heavy, and there is alot of work in setting that thing up. The affect is
+the FileValidity object for that file was set up.  The TransformerHandler object
+is heavy, and there is alot of work in setting that thing up.  The affect is
that the TraxTransformer incurred the cost of setting up the TransformerHandler
-whether it was used or not. When the pipeline pulled from the cache, the
-TransformerHandler was created and discarded. You have the overhead of the
+whether it was used or not.  When the pipeline pulled from the cache, the
+TransformerHandler was created and discarded.  You have the overhead of the
garbage collection along with unused objects.Sylvain saw the problem, and delayed creating the TransformerHandler until
-Cocoon called the <tt>setXMLConsumer()</tt> method. This ensured that every
+Cocoon called the <tt>setXMLConsumer()</tt> method.  This ensured that every
opportunity was given to check cache validity and we only incurred the cost of
-creating the TransformerHandler when Cocoon was really going to use it. Another
+creating the TransformerHandler when Cocoon was really going to use it.  Another
safe place to put the completed setup code is on the <tt>startDocument()</tt>
-SAX method. At this point it is clear we are currently using the
+SAX method.  At this point it is clear we are currently using the
TransformerHandler, so it will also work.After everything was said and done, the TraxTransformer performed between 5%
-to 30% better depending on the complexity of the TransformerHandler. The key
-was delaying the heavy lifting until it was actually needed.<h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">AggregateValidity and DelayedAggregateValidity</h2>Some components like the DirectoryGenerator and the TraxTransformer rely on
-the validity of other factors than just a template or a set of files. These
-components often can't determine the validity at setup time. The solution is to
-use the AggregateValidity and more specifically the DelayedAggregateValidity.
+to 30% better depending on the complexity of the TransformerHandler.  The key
+was delaying the heavy lifting until it was actually needed.<div class="section" style="background:none;padding:0;"><h2 style="background:none;padding:0;">AggregateValidity and DelayedAggregateValidity<a name="AggregateValidity_and_DelayedAggregateValidity"></a></h2></div>Some components like the DirectoryGenerator and the TraxTransformer rely on
+the validity of other factors than just a template or a set of files.  These
+components often can't determine the validity at setup time.  The solution is to
+use the AggregateValidity and more specifically the DelayedAggregateValidity. 
The aggregated validity object provides an interface for you to add additional
validity components inside and returns the result of the set (typically if one
-validity object is undertermined or invalid the whole set is). You can add to
-the aggregated validity object as the pipeline is executed. Every time the
+validity object is undertermined or invalid the whole set is).  You can add to
+the aggregated validity object as the pipeline is executed.  Every time the
TraxTransformer includes another XML document using the <tt>document()</tt>
function in XSLT, it's FileValidity is added to the aggregated validity object.
The DirectoryGenerator relies on an internal pipeline to be run, and because
we don't know the validity until after the pipeline is run, it is impossible to
-set up the validity objects ahead of time. The solution in this case is to use
-the DelayedAggregateValidity object. Placeholders are given using the
+set up the validity objects ahead of time.  The solution in this case is to use
+the DelayedAggregateValidity object.  Placeholders are given using the
DelayedValidity interface, and when the solid validity object is ready it can be
-used. Essentially the full validity object is assembled as the pipeline is
-run. The next time the aggregated validity object is inspected it is set up
+used.  Essentially the full validity object is assembled as the pipeline is
+run.  The next time the aggregated validity object is inspected it is set up
already.While these are possible solutions to a complex problem, they do incur their
-own overhead. Done well, the overhead is still less than creating the content
+own overhead.  Done well, the overhead is still less than creating the content
fresh every time--but care should be taken that we don't have a huge validity
object tree by having aggregate validity objects including aggregate validity
-objects that include aggregate validity objects. In short, you have to keep it
-simple. The general rule of thumb is that if you can't write a simple unit test
-for it, you probably need to start looking to simplify. Cocoon has many tools
+objects that include aggregate validity objects.  In short, you have to keep it
+simple.  The general rule of thumb is that if you can't write a simple unit test
+for it, you probably need to start looking to simplify.  Cocoon has many tools
for caching and cache control, understanding how things work will help you write
-more efficient components.</div><div class="editUrl"><div><em>Errors and Improvements?</em> If you see any errors or potential improvements in this document please help
- us: <a href="http://cocoon.zones.apache.org/daisy/cdocs/690?branch=1&language=1">View, Edit or comment</a> on the latest development version (registration required).
- </div></div></div>
+more efficient components.</div></div>
+
</div>
</div>
<!-- end of content -->
<div id="footer">
- <p>©
- 1999-2008
+ <p>Copyright ©
+ 1999-2012
The Apache Software Foundation
+ All Rights Reserved.</p>
+
+ <p>
+ Apache Cocoon, Apache, the Apache feather logo, and the Apache Cocoon project logos are trademarks of The Apache Software Foundation.
+ All other marks mentioned may be trademarks or registered trademarks of their respective owners.
</p>
</div>
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript">
Modified: cocoon/site/site/2.2/core-modules/core/2.2/694_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.2/core-modules/core/2.2/694_1_1.html?rev=1329677&r1=1329676&r2=1329677&view=diff
==============================================================================
--- cocoon/site/site/2.2/core-modules/core/2.2/694_1_1.html (original)
+++ cocoon/site/site/2.2/core-modules/core/2.2/694_1_1.html Tue Apr 24 12:39:52 2012
@@ -29,17 +29,13 @@
<head>
<title> Cocoon Core - Creating a Transformer
</title>
- <style type="text/css" media="all">
- @import url("./css/maven-base.css");
- @import url("./css/maven-theme.css");
- @import url("./css/site.css");
- </style>
+ <link rel="stylesheet" href="./css/apache-cocoon-thien-maven-skin.min.css" />
<link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
- <script src="./js/getBlank.js" language="javascript" type="text/javascript"></script>
- <meta name="author" content="The Cocoon Community" />
- <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+ <script src="./js/apache-cocoon-thien-maven-skin.min.js" language="javascript" type="text/javascript"></script>
+ <meta name="author" content="Apache Cocoon Documentation Team" />
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
</head>
- <body>
+ <body onload="javascript:prettyPrint();">
<div id="breadtrail">
<p><a href="http://www.apache.org">Apache</a> » <a href="../../../../">Cocoon</a> »</p>
</div>
@@ -77,7 +73,7 @@
<li><a href="../../../../2.2/core-modules/">Core <span class="pl-version-small">2.2</span></a></li>
<li><a href="../../../../2.2/blocks/">Blocks <span class="pl-version-small">2.2</span></a></li>
<li><a href="../../../../2.2/maven-plugins/">Maven Plugins <span class="pl-version-small">2.2</span></a></li>
- <li><strong><a href="../../../..//3.0/">Cocoon 3.0 <span class="pl-version-small">[alpha]</span></a></em></strong></li>
+ <li><strong><a href="../../../..//3.0/">Cocoon 3.0</a></em></strong></li>
<li><strong><a href="../../../../subprojects/">Subprojects</a></strong></li>
</ul>
</div>
@@ -92,7 +88,7 @@
<ul>
<li >
- <a href="1270_1_1.html">Introduction</a>
+ <a href="index.html">Introduction</a>
</li>
</ul>
</li>
@@ -319,8 +315,6 @@
-
-
<li class='menuCollapse'>
<a href="842_1_1.html">Reference</a>
@@ -608,7 +602,7 @@
</li>
<li >
- <a href="1380_1_1.html">Using Control Flow</a>
+ <a href="1380_1_1.html">Using Control Flow</a>
</li>
</ul>
</li>
@@ -642,11 +636,11 @@
</li>
<li >
- <a href="1399_1_1.html">Logging configuration</a>
+ <a href="1399_1_1.html">Logging Configuration</a>
</li>
<li >
- <a href="1259_1_1.html">Component Configurations</a>
+ <a href="1259_1_1.html">Component Configuration</a>
</li>
<li >
@@ -655,83 +649,77 @@
</ul>
</li>
<li>
- Project Documentation
+ Project Reports
<ul>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- <li class='menuCollapse'>
- <a href="project-info.html">Project Information</a>
- </li>
+ <li >
+ <a href="changes-report.html">Changes Report</a>
+ </li>
-
-
-
-
-
-
-
-
- <li class='menuCollapse'>
- <a href="project-reports.html">Project Reports</a>
- </li>
+ <li >
+ <a href="apidocs/">JavaDocs</a>
+ </li>
</ul>
</li>
</ul>
<div class="main">
- <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Creating a Transformer</h1><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Creating a Transformer</h1><p>In 90% of all cases XSLT will perform all your transformation needs better
-than anything else out there. I'll be completely blunt and say that creating a
-transformer that does anything truly substantial is not for the faint of heart.
-The issue has to do with using SAX event streams to process the XML. SAX vs.
-DOM was a design tradeoff to favor scalability over ease of use. A particularly
+ <!-- Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License. -->
+ <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Creating a Transformer</h1><h1>Creating a Transformer</h1><p>In 90% of all cases XSLT will perform all your transformation needs better
+than anything else out there.  I'll be completely blunt and say that creating a
+transformer that does anything truly substantial is not for the faint of heart. 
+The issue has to do with using SAX event streams to process the XML.  SAX vs.
+DOM was a design tradeoff to favor scalability over ease of use.  A particularly
large DOM tree can cripple a web application and you lose all the benefit of
such a powerful architecture like Cocoon.</p><p>The transformer we are going to create in this tutorial is actually very
-trivial. You'll have to take the lessons from this and expand them if you want
-to do something more exciting. We will be using a transformer to insert a
-timestamp when we see an element called "time-stamp" in a specified namespace.
+trivial.  You'll have to take the lessons from this and expand them if you want
+to do something more exciting.  We will be using a transformer to insert a
+timestamp when we see an element called "time-stamp" in a specified namespace. 
Along the way we will look at some ways of lowering the impact of having your
-transformer in the pipeline. To use our transformer we will have a sitemap
-snippet similar to the following:</p><pre><map:match pattern="timed-hello.xml">
+transformer in the pipeline.  To use our transformer we will have a sitemap
+snippet similar to the following:</p><div><pre><map:match pattern="timed-hello.xml">
<map:generate src="hello.xml"/>
<map:transformer type="time"/>
<map:serialize/>
</map:match>
-</pre><p>Notice that we didn't have a "src" attribute for our transformer? In this
-case our example is so trivial that we really don't need one. If we wanted to
+</pre></div><p>Notice that we didn't have a "src" attribute for our transformer?  In this
+case our example is so trivial that we really don't need one.  If we wanted to
add a little more functionality we could pass in a format using the src
-attribute, but that could also be done by modifying our markup. Just so we are
-complete in what we expect to do, we want to take the following XML:</p><pre><ts:time xmlns:ts="unc:time"/>
-</pre><p>into the current date and time ending with the minute (ex. Sep. 16, 2005
-12:59 PM).</p><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">How the Sitemap Treats a Transformer</h2><p>All Transformer components are SitemapModelComponents and XMLPipelines, in
-addition they can be CacheableProcessingComponents. All of those contracts have
-been covered in depth already. Once the sitemap determines that we need to pass
+attribute, but that could also be done by modifying our markup.  Just so we are
+complete in what we expect to do, we want to take the following XML:</p><div><pre><ts:time xmlns:ts="unc:time"/>
+</pre></div><p>into the current date and time ending with the minute (ex. Sep. 16, 2005
+12:59 PM).</p><div class="section" style="background:none;padding:0;"><h2 style="background:none;padding:0;">How the Sitemap Treats a Transformer<a name="How_the_Sitemap_Treats_a_Transformer"></a></h2></div><p>All Transformer components are SitemapModelComponents and XMLPipelines, in
+addition they can be CacheableProcessingComponents.  All of those contracts have
+been covered in depth already.  Once the sitemap determines that we need to pass
results through your transformer (i.e. there are no cached entries for the
pipeline up to this point), the <tt>setXMLConsumer()</tt> method is called, and
you know the pipeline is being processed as soon as you receive the
-<tt>startDocument()</tt> event.</p><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">AbstractTransformer: A Good Start</h2><p>The AbstractTransformer has everything you need to pass SAX events through
-unmolested. You have the different objects from the setup method accessible as
+<tt>startDocument()</tt> event.</p><div class="section" style="background:none;padding:0;"><h2 style="background:none;padding:0;">AbstractTransformer: A Good Start<a name="AbstractTransformer:_A_Good_Start"></a></h2></div><p>The AbstractTransformer has everything you need to pass SAX events through
+unmolested.  You have the different objects from the setup method accessible as
fields in the class, and the XMLPipeline contract is already set up to pass
-through the SAX events to the XMLConsumer. We will only need to do a couple
-things to set up caching properly. In fact because our input doesn't rely on
+through the SAX events to the XMLConsumer.  We will only need to do a couple
+things to set up caching properly.  In fact because our input doesn't rely on
any external source of information we can have a constant for the cache key: the
-namespace we are transforming.</p><h3 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">The Transformer Skeleton</h3><p>The skeleton code does nothing more than set up the cache validity object we
-will be using. You might be thinking that we can't cache anything so dynamic as
+namespace we are transforming.</p><div class="section"><h3>The Transformer Skeleton<a name="The_Transformer_Skeleton"></a></h3><p>The skeleton code does nothing more than set up the cache validity object we
+will be using.  You might be thinking that we can't cache anything so dynamic as
the time of day, but we can cache it for as long as the shortest amount of time
-we are displaying. If you are being slammed with 150 simultaneous users a
+we are displaying.  If you are being slammed with 150 simultaneous users a
second all asking for something that has the time of day inserted, we should be
-able to generate it once and reuse the results until the clock advances.</p><pre>import org.apache.avalon.framework.parameters.Parameters;
+able to generate it once and reuse the results until the clock advances.</p><div><pre>import org.apache.avalon.framework.parameters.Parameters;
import org.apache.cocoon.ProcessingException;
import org.apache.cocoon.caching.CacheableProcessingComponent;
import org.apache.cocoon.environment.SourceResolver;
@@ -760,32 +748,32 @@ public class TimeTransformer extends Abs
}
// ... skip other methods later.
-}</pre><p>We set up some constants that will be used later such as our time format, the
+}</pre></div><p>We set up some constants that will be used later such as our time format, the
namespace we are checking, and the number of milliseconds that make up a
-minute. The other two instance fields are the cacheValidity object and the date
-formatter. Because by definition none of the formatters are threadsafe, we have
-to create a new one for each instance of this transformer. Technically speaking
+minute.  The other two instance fields are the cacheValidity object and the date
+formatter.  Because by definition none of the formatters are threadsafe, we have
+to create a new one for each instance of this transformer.  Technically speaking
we could make it a ThreadLocal object, but we wanted to keep things simple here.
-</p><h3 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">The Cache Clues</h3><p>Since the caching aspect of this component is really simple, let's just get
-it out of the way here. First thing is that the key for this transformer should
+</p></div><div class="section"><h3>The Cache Clues<a name="The_Cache_Clues"></a></h3><p>Since the caching aspect of this component is really simple, let's just get
+it out of the way here.  First thing is that the key for this transformer should
not change with the time of day, so let's use the namespace we are checking as
-the cache key:</p><pre> public Serializable getKey()
+the cache key:</p><div><pre> public Serializable getKey()
{
return NAMESPACE;
- }</pre><p>And finally, we already set up our validity object in the <tt>setup()</tt>
-call in the skeleton code. Let's just pass it back.</p><pre> public SourceValidity getValidity()
+ }</pre></div><p>And finally, we already set up our validity object in the <tt>setup()</tt>
+call in the skeleton code.  Let's just pass it back.</p><div><pre> public SourceValidity getValidity()
{
return cacheValidity;
}
-</pre><h3 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Performing the Transformation</h3><p>At this point the only thing we didn't do yet is set up our date formatter.
-We have two choices: delayed evaluation or structured evaluation. With delayed
+</pre></div></div><div class="section"><h3>Performing the Transformation<a name="Performing_the_Transformation"></a></h3><p>At this point the only thing we didn't do yet is set up our date formatter. 
+We have two choices: delayed evaluation or structured evaluation.  With delayed
evaluation we wait until we actually have a <tt>ts:time</tt> element to
-transform before we set up the formatter. With structured evaluation we take
+transform before we set up the formatter.  With structured evaluation we take
advantage of the fact that <tt>startDocument()</tt> is called before anything
-else and we do it then. The actual solution to the problem depends on the
+else and we do it then.  The actual solution to the problem depends on the
liklihood of always having an element to transform and the cost of creating the
-objects you need to work with. Because our case is really simple, its a
-tossup. We'll go with structured evaluation just because it's clearer code:</p><pre> public void startDocument()
+objects you need to work with.  Because our case is really simple, its a
+tossup.  We'll go with structured evaluation just because it's clearer code:</p><div><pre> public void startDocument()
{
super.startDocument();
formatter = new SimpleDateFormatter(FORMAT);
@@ -796,12 +784,12 @@ tossup. We'll go with structured evalu
super.endDocument();
formatter = null; // just cleanup for the garbage collector's sake
}
-</pre><p>All that's left is to actually perform the transformation. Again, we need to
+</pre></div><p>All that's left is to actually perform the transformation.  Again, we need to
override two methods because of the <tt>startElement()</tt> and
-<tt>endElement()</tt> pairing. To make things more interesting we will even add
-some simple validation to our code. There should be no embedded text inside the
+<tt>endElement()</tt> pairing.  To make things more interesting we will even add
+some simple validation to our code.  There should be no embedded text inside the
element we are listening for, so we will include a new field which is a boolean
-flag for whether we are in the timestamp element or not:</p><pre> private boolean isInTimeElement = false;
+flag for whether we are in the timestamp element or not:</p><div><pre> private boolean isInTimeElement = false;
public void startElement(String namespace, String name, String qName, Attributes attrib)
{
@@ -825,30 +813,30 @@ flag for whether we are in the timestamp
super.startElement(namespace, name, qName, attrib);
}
-</pre><p>Before we move on to the characters() evaluation, let's spend some time with
-the code above. First we check if it is legal to have sub-elements, which of
-course only happens when we are not in a time element. Next, we check if the
-element we recieved is one we have to worry about. If we are in the right
+</pre></div><p>Before we move on to the characters() evaluation, let's spend some time with
+the code above.  First we check if it is legal to have sub-elements, which of
+course only happens when we are not in a time element.  Next, we check if the
+element we recieved is one we have to worry about.  If we are in the right
namespace, we check the element name and throw an exception if the element name
-is anything other than "time". Assuming we have the time element in our
+is anything other than "time".  Assuming we have the time element in our
namespace we substitute the <tt>startElement()</tt> call with the coresponding
<tt>characters</tt><tt>()</tt> call, turn on the <tt>isInTimeElement</tt> flag,
-and finally return immediately. Otherwise we will simply forward on the
-<tt>startElement()</tt> call as usual. Another thing to note is that we called
+and finally return immediately.  Otherwise we will simply forward on the
+<tt>startElement()</tt> call as usual.  Another thing to note is that we called
the <tt>characters()</tt> event directly on the content handler instead of
-calling our own transformer. We did that to make sure that our validation code
-doesn't reject the date string we want to pass on. Now to validate our own
-<tt>characters()</tt> method:</p><pre> public void characters(char[] chars, int start, int end)
+calling our own transformer.  We did that to make sure that our validation code
+doesn't reject the date string we want to pass on.  Now to validate our own
+<tt>characters()</tt> method:</p><div><pre> public void characters(char[] chars, int start, int end)
{
if ( isInTimeElement ) throw new SAXException("Cannot have embedded text");
super.characters(chars, start, end);
}
-</pre><p>The <tt>characters()</tt> event is really simple, and we only throw an
-exception if the user tried to embed characters inside the timestamp element.
+</pre></div><p>The <tt>characters()</tt> event is really simple, and we only throw an
+exception if the user tried to embed characters inside the timestamp element. 
Now for the endElement() so that we can turn of the <tt>isInTimeElement</tt>
flag and swallow the matching <tt>endElement()</tt> event for our timestamp
-element:</p><pre> public void endElement(String namespace, String name, String qName)
+element:</p><div><pre> public void endElement(String namespace, String name, String qName)
{
if ( NAMESPACE.equals(namespace) && "time".equals(name) )
{
@@ -858,41 +846,45 @@ element:</p><pre> public void endElem
super.endElement(namespace, name, qName)
}
-</pre><p>Now we are done with the component.</p><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Additional Things to Consider for Transformers</h2><p>There are a couple things to keep in mind when dealing with SAX streams and
-designing your transformers. First, it takes more time to iterate through a set
+</pre></div><p>Now we are done with the component.</p></div><div class="section" style="background:none;padding:0;"><h2 style="background:none;padding:0;">Additional Things to Consider for Transformers<a name="Additional_Things_to_Consider_for_Transformers"></a></h2></div><p>There are a couple things to keep in mind when dealing with SAX streams and
+designing your transformers.  First, it takes more time to iterate through a set
of attributes for every element looking for an attribute in your namespace than
-it does to look for an element with the namespace you desire. In short,
-elements are faster to evaluate than attributes. Use them when you can.
-Secondly, remember to evaluate namespaces/name combinations and not QNames. A
+it does to look for an element with the namespace you desire.  In short,
+elements are faster to evaluate than attributes.  Use them when you can. 
+Secondly, remember to evaluate namespaces/name combinations and not QNames.  A
QName (or Qualified Name in XML speak) is name including the prefix matching a
-namespace. The only time you should look at the QName is if you need to treat
-different "contexts" of transformation for the namespace. In other words unless
+namespace.  The only time you should look at the QName is if you need to treat
+different "contexts" of transformation for the namespace.  In other words unless
you need to treat "ts:time" separate from "nt:time" ignore the QName--most of
the time you just care whether or not you are dealing with a particular
-namespace.</p><p>Lastly, validation is a tricky thing. Many times you want validation in
-development but not in production because it is expensive to do. In our example
-we included validation but never provided a way to turn it off. For this case
+namespace.</p><p>Lastly, validation is a tricky thing.  Many times you want validation in
+development but not in production because it is expensive to do.  In our example
+we included validation but never provided a way to turn it off.  For this case
the validation is so trivial that it's acceptable to keep the logic in
-production--but it does make the code a bit more complex. Sometimes the
-validation code can be a source of errors. Test your validation code, but
-assume that you are receiving valid XML. After all this is a transformer. The
+production--but it does make the code a bit more complex.  Sometimes the
+validation code can be a source of errors.  Test your validation code, but
+assume that you are receiving valid XML.  After all this is a transformer.  The
Generator should have been tested to make sure that the XML generated is valid.
</p><p>As a final measure to ensure your transformer isn't turning previously valid
-XML into invalid XML. A quick test is to take a valid XML document and
+XML into invalid XML.  A quick test is to take a valid XML document and
transform it using your transformer--serializing to a stream and feeding that
-into a validating XML parser. It seems weird, but it is a simple test to set up
-for all transformers to make sure they don't introduce errors of their own.</p></div><div class="editUrl"><div><em>Errors and Improvements?</em> If you see any errors or potential improvements in this document please help
- us: <a href="http://cocoon.zones.apache.org/daisy/cdocs/694?branch=1&language=1">View, Edit or comment</a> on the latest development version (registration required).
- </div></div></div>
+into a validating XML parser.  It seems weird, but it is a simple test to set up
+for all transformers to make sure they don't introduce errors of their own.</p></div></div>
+
</div>
</div>
<!-- end of content -->
<div id="footer">
- <p>©
- 1999-2008
+ <p>Copyright ©
+ 1999-2012
The Apache Software Foundation
+ All Rights Reserved.</p>
+
+ <p>
+ Apache Cocoon, Apache, the Apache feather logo, and the Apache Cocoon project logos are trademarks of The Apache Software Foundation.
+ All other marks mentioned may be trademarks or registered trademarks of their respective owners.
</p>
</div>
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript">
Modified: cocoon/site/site/2.2/core-modules/core/2.2/725_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.2/core-modules/core/2.2/725_1_1.html?rev=1329677&r1=1329676&r2=1329677&view=diff
==============================================================================
--- cocoon/site/site/2.2/core-modules/core/2.2/725_1_1.html (original)
+++ cocoon/site/site/2.2/core-modules/core/2.2/725_1_1.html Tue Apr 24 12:39:52 2012
@@ -29,17 +29,13 @@
<head>
<title> Cocoon Core - Creating a Serializer
</title>
- <style type="text/css" media="all">
- @import url("./css/maven-base.css");
- @import url("./css/maven-theme.css");
- @import url("./css/site.css");
- </style>
+ <link rel="stylesheet" href="./css/apache-cocoon-thien-maven-skin.min.css" />
<link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
- <script src="./js/getBlank.js" language="javascript" type="text/javascript"></script>
- <meta name="author" content="The Cocoon Community" />
- <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+ <script src="./js/apache-cocoon-thien-maven-skin.min.js" language="javascript" type="text/javascript"></script>
+ <meta name="author" content="Apache Cocoon Documentation Team" />
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
</head>
- <body>
+ <body onload="javascript:prettyPrint();">
<div id="breadtrail">
<p><a href="http://www.apache.org">Apache</a> » <a href="../../../../">Cocoon</a> »</p>
</div>
@@ -77,7 +73,7 @@
<li><a href="../../../../2.2/core-modules/">Core <span class="pl-version-small">2.2</span></a></li>
<li><a href="../../../../2.2/blocks/">Blocks <span class="pl-version-small">2.2</span></a></li>
<li><a href="../../../../2.2/maven-plugins/">Maven Plugins <span class="pl-version-small">2.2</span></a></li>
- <li><strong><a href="../../../..//3.0/">Cocoon 3.0 <span class="pl-version-small">[alpha]</span></a></em></strong></li>
+ <li><strong><a href="../../../..//3.0/">Cocoon 3.0</a></em></strong></li>
<li><strong><a href="../../../../subprojects/">Subprojects</a></strong></li>
</ul>
</div>
@@ -92,7 +88,7 @@
<ul>
<li >
- <a href="1270_1_1.html">Introduction</a>
+ <a href="index.html">Introduction</a>
</li>
</ul>
</li>
@@ -319,8 +315,6 @@
-
-
<li class='menuCollapse'>
<a href="842_1_1.html">Reference</a>
@@ -608,7 +602,7 @@
</li>
<li >
- <a href="1380_1_1.html">Using Control Flow</a>
+ <a href="1380_1_1.html">Using Control Flow</a>
</li>
</ul>
</li>
@@ -642,11 +636,11 @@
</li>
<li >
- <a href="1399_1_1.html">Logging configuration</a>
+ <a href="1399_1_1.html">Logging Configuration</a>
</li>
<li >
- <a href="1259_1_1.html">Component Configurations</a>
+ <a href="1259_1_1.html">Component Configuration</a>
</li>
<li >
@@ -655,61 +649,59 @@
</ul>
</li>
<li>
- Project Documentation
+ Project Reports
<ul>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- <li class='menuCollapse'>
- <a href="project-info.html">Project Information</a>
- </li>
+ <li >
+ <a href="changes-report.html">Changes Report</a>
+ </li>
-
-
-
-
-
-
-
-
- <li class='menuCollapse'>
- <a href="project-reports.html">Project Reports</a>
- </li>
+ <li >
+ <a href="apidocs/">JavaDocs</a>
+ </li>
</ul>
</li>
</ul>
<div class="main">
- <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Creating a Serializer</h1><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Creating a Serializer</h1><p>For most problems, Cocoon has a serializer ready for you. However, you may
-have to deal with some new unique binary format which is fed by your XML. The
-SVG to PNG serializer works in this way as does the FOP to PDF serializer.
+ <!-- Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License. -->
+ <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Creating a Serializer</h1><h1>Creating a Serializer</h1><p>For most problems, Cocoon has a serializer ready for you.  However, you may
+have to deal with some new unique binary format which is fed by your XML.  The
+SVG to PNG serializer works in this way as does the FOP to PDF serializer. 
Given that there are only so many ways to present data on the web, it is very
-difficult to come up with an example serializer that is new and useful.
-Nevertheless we will present the <a href="http://www.yaml.org">YAML</a>
-serializer. There is no real direct mapping of concepts, but the only thing
-that you can't map directly in YAML to XML is the attributes.</p></div><div class="editUrl"><div><em>Errors and Improvements?</em> If you see any errors or potential improvements in this document please help
- us: <a href="http://cocoon.zones.apache.org/daisy/cdocs/725?branch=1&language=1">View, Edit or comment</a> on the latest development version (registration required).
- </div></div></div>
+difficult to come up with an example serializer that is new and useful. 
+Nevertheless we will present the <a class="externalLink" href="http://www.yaml.org">YAML</a>
+serializer.  There is no real direct mapping of concepts, but the only thing
+that you can't map directly in YAML to XML is the attributes.</p></div></div>
+
</div>
</div>
<!-- end of content -->
<div id="footer">
- <p>©
- 1999-2008
+ <p>Copyright ©
+ 1999-2012
The Apache Software Foundation
+ All Rights Reserved.</p>
+
+ <p>
+ Apache Cocoon, Apache, the Apache feather logo, and the Apache Cocoon project logos are trademarks of The Apache Software Foundation.
+ All other marks mentioned may be trademarks or registered trademarks of their respective owners.
</p>
</div>
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript">
Modified: cocoon/site/site/2.2/core-modules/core/2.2/808_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.2/core-modules/core/2.2/808_1_1.html?rev=1329677&r1=1329676&r2=1329677&view=diff
==============================================================================
--- cocoon/site/site/2.2/core-modules/core/2.2/808_1_1.html (original)
+++ cocoon/site/site/2.2/core-modules/core/2.2/808_1_1.html Tue Apr 24 12:39:52 2012
@@ -29,17 +29,13 @@
<head>
<title> Cocoon Core - map:sitemap
</title>
- <style type="text/css" media="all">
- @import url("./css/maven-base.css");
- @import url("./css/maven-theme.css");
- @import url("./css/site.css");
- </style>
+ <link rel="stylesheet" href="./css/apache-cocoon-thien-maven-skin.min.css" />
<link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
- <script src="./js/getBlank.js" language="javascript" type="text/javascript"></script>
- <meta name="author" content="The Cocoon Community" />
- <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+ <script src="./js/apache-cocoon-thien-maven-skin.min.js" language="javascript" type="text/javascript"></script>
+ <meta name="author" content="Apache Cocoon Documentation Team" />
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
</head>
- <body>
+ <body onload="javascript:prettyPrint();">
<div id="breadtrail">
<p><a href="http://www.apache.org">Apache</a> » <a href="../../../../">Cocoon</a> »</p>
</div>
@@ -77,7 +73,7 @@
<li><a href="../../../../2.2/core-modules/">Core <span class="pl-version-small">2.2</span></a></li>
<li><a href="../../../../2.2/blocks/">Blocks <span class="pl-version-small">2.2</span></a></li>
<li><a href="../../../../2.2/maven-plugins/">Maven Plugins <span class="pl-version-small">2.2</span></a></li>
- <li><strong><a href="../../../..//3.0/">Cocoon 3.0 <span class="pl-version-small">[alpha]</span></a></em></strong></li>
+ <li><strong><a href="../../../..//3.0/">Cocoon 3.0</a></em></strong></li>
<li><strong><a href="../../../../subprojects/">Subprojects</a></strong></li>
</ul>
</div>
@@ -92,7 +88,7 @@
<ul>
<li >
- <a href="1270_1_1.html">Introduction</a>
+ <a href="index.html">Introduction</a>
</li>
</ul>
</li>
@@ -244,8 +240,6 @@
-
-
@@ -350,8 +344,6 @@
-
-
@@ -423,10 +415,6 @@
</li>
<li >
- <a href="822_1_1.html">map:pipes</a>
- </li>
-
- <li >
<a href="821_1_1.html">map:reader</a>
</li>
@@ -768,7 +756,7 @@
</li>
<li >
- <a href="1380_1_1.html">Using Control Flow</a>
+ <a href="1380_1_1.html">Using Control Flow</a>
</li>
</ul>
</li>
@@ -802,11 +790,11 @@
</li>
<li >
- <a href="1399_1_1.html">Logging configuration</a>
+ <a href="1399_1_1.html">Logging Configuration</a>
</li>
<li >
- <a href="1259_1_1.html">Component Configurations</a>
+ <a href="1259_1_1.html">Component Configuration</a>
</li>
<li >
@@ -815,54 +803,52 @@
</ul>
</li>
<li>
- Project Documentation
+ Project Reports
<ul>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- <li class='menuCollapse'>
- <a href="project-info.html">Project Information</a>
- </li>
+ <li >
+ <a href="changes-report.html">Changes Report</a>
+ </li>
-
-
-
-
-
-
-
-
- <li class='menuCollapse'>
- <a href="project-reports.html">Project Reports</a>
- </li>
+ <li >
+ <a href="apidocs/">JavaDocs</a>
+ </li>
</ul>
</li>
</ul>
<div class="main">
- <div id="contentBody"><div id="bodyText"><h1 class="docTitle">map:sitemap</h1><h1>Attributes</h1><h1>Occurence</h1><h2>Children</h2><p>This element can have the following children:</p><ul><li>map:action-sets</li><li>map:components</li><li>map:flow</li><li>map:pipelines</li><li>map:resources</li><li>map:views</li></ul></div><div class="editUrl"><div><em>Errors and Improvements?</em> If you see any errors or potential improvements in this document please help
- us: <a href="http://cocoon.zones.apache.org/daisy/cdocs/808?branch=1&language=1">View, Edit or comment</a> on the latest development version (registration required).
- </div></div></div>
+ <!-- Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License. -->
+ <div id="contentBody"><div id="bodyText"><h1 class="docTitle">map:sitemap</h1><h1>Attributes</h1><h1>Occurence</h1><div class="section" style="background:none;padding:0;"><h2 style="background:none;padding:0;">Children<a name="Children"></a></h2></div><p>This element can have the following children:</p><ul><li>map:action-sets</li><li>map:components</li><li>map:flow</li><li>map:pipelines</li><li>map:resources</li><li>map:views</li></ul></div></div>
+
</div>
</div>
<!-- end of content -->
<div id="footer">
- <p>©
- 1999-2008
+ <p>Copyright ©
+ 1999-2012
The Apache Software Foundation
+ All Rights Reserved.</p>
+
+ <p>
+ Apache Cocoon, Apache, the Apache feather logo, and the Apache Cocoon project logos are trademarks of The Apache Software Foundation.
+ All other marks mentioned may be trademarks or registered trademarks of their respective owners.
</p>
</div>
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript">
Modified: cocoon/site/site/2.2/core-modules/core/2.2/809_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.2/core-modules/core/2.2/809_1_1.html?rev=1329677&r1=1329676&r2=1329677&view=diff
==============================================================================
--- cocoon/site/site/2.2/core-modules/core/2.2/809_1_1.html (original)
+++ cocoon/site/site/2.2/core-modules/core/2.2/809_1_1.html Tue Apr 24 12:39:52 2012
@@ -29,17 +29,13 @@
<head>
<title> Cocoon Core - map:components
</title>
- <style type="text/css" media="all">
- @import url("./css/maven-base.css");
- @import url("./css/maven-theme.css");
- @import url("./css/site.css");
- </style>
+ <link rel="stylesheet" href="./css/apache-cocoon-thien-maven-skin.min.css" />
<link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
- <script src="./js/getBlank.js" language="javascript" type="text/javascript"></script>
- <meta name="author" content="The Cocoon Community" />
- <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+ <script src="./js/apache-cocoon-thien-maven-skin.min.js" language="javascript" type="text/javascript"></script>
+ <meta name="author" content="Apache Cocoon Documentation Team" />
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
</head>
- <body>
+ <body onload="javascript:prettyPrint();">
<div id="breadtrail">
<p><a href="http://www.apache.org">Apache</a> » <a href="../../../../">Cocoon</a> »</p>
</div>
@@ -77,7 +73,7 @@
<li><a href="../../../../2.2/core-modules/">Core <span class="pl-version-small">2.2</span></a></li>
<li><a href="../../../../2.2/blocks/">Blocks <span class="pl-version-small">2.2</span></a></li>
<li><a href="../../../../2.2/maven-plugins/">Maven Plugins <span class="pl-version-small">2.2</span></a></li>
- <li><strong><a href="../../../..//3.0/">Cocoon 3.0 <span class="pl-version-small">[alpha]</span></a></em></strong></li>
+ <li><strong><a href="../../../..//3.0/">Cocoon 3.0</a></em></strong></li>
<li><strong><a href="../../../../subprojects/">Subprojects</a></strong></li>
</ul>
</div>
@@ -92,7 +88,7 @@
<ul>
<li >
- <a href="1270_1_1.html">Introduction</a>
+ <a href="index.html">Introduction</a>
</li>
</ul>
</li>
@@ -253,8 +249,6 @@
-
-
<li class='menuExpand'>
<a href="842_1_1.html">Reference</a>
@@ -359,8 +353,6 @@
-
-
<li class='menuExpand'>
<a href="811_1_1.html">Other elements</a>
@@ -423,10 +415,6 @@
</li>
<li >
- <a href="822_1_1.html">map:pipes</a>
- </li>
-
- <li >
<a href="821_1_1.html">map:reader</a>
</li>
@@ -768,7 +756,7 @@
</li>
<li >
- <a href="1380_1_1.html">Using Control Flow</a>
+ <a href="1380_1_1.html">Using Control Flow</a>
</li>
</ul>
</li>
@@ -802,11 +790,11 @@
</li>
<li >
- <a href="1399_1_1.html">Logging configuration</a>
+ <a href="1399_1_1.html">Logging Configuration</a>
</li>
<li >
- <a href="1259_1_1.html">Component Configurations</a>
+ <a href="1259_1_1.html">Component Configuration</a>
</li>
<li >
@@ -815,54 +803,52 @@
</ul>
</li>
<li>
- Project Documentation
+ Project Reports
<ul>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- <li class='menuCollapse'>
- <a href="project-info.html">Project Information</a>
- </li>
+ <li >
+ <a href="changes-report.html">Changes Report</a>
+ </li>
-
-
-
-
-
-
-
-
- <li class='menuCollapse'>
- <a href="project-reports.html">Project Reports</a>
- </li>
+ <li >
+ <a href="apidocs/">JavaDocs</a>
+ </li>
</ul>
</li>
</ul>
<div class="main">
- <div id="contentBody"><div id="bodyText"><h1 class="docTitle">map:components</h1><h1>Attributes</h1><h1>Occurence</h1><h2>Children</h2><p>This element can have the following children:</p><ul><li>map:actions</li><li>map:generators</li><li>map:matchers</li><li>map:pipes</li><li>map:selectors</li><li>map:serializers</li><li>map:transformers</li></ul></div><div class="editUrl"><div><em>Errors and Improvements?</em> If you see any errors or potential improvements in this document please help
- us: <a href="http://cocoon.zones.apache.org/daisy/cdocs/809?branch=1&language=1">View, Edit or comment</a> on the latest development version (registration required).
- </div></div></div>
+ <!-- Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License. -->
+ <div id="contentBody"><div id="bodyText"><h1 class="docTitle">map:components</h1><h1>Attributes</h1><h1>Occurence</h1><div class="section" style="background:none;padding:0;"><h2 style="background:none;padding:0;">Children<a name="Children"></a></h2></div><p>This element can have the following children:</p><ul><li>map:actions</li><li>map:generators</li><li>map:matchers</li><li>map:pipes</li><li>map:selectors</li><li>map:serializers</li><li>map:transformers</li></ul></div></div>
+
</div>
</div>
<!-- end of content -->
<div id="footer">
- <p>©
- 1999-2008
+ <p>Copyright ©
+ 1999-2012
The Apache Software Foundation
+ All Rights Reserved.</p>
+
+ <p>
+ Apache Cocoon, Apache, the Apache feather logo, and the Apache Cocoon project logos are trademarks of The Apache Software Foundation.
+ All other marks mentioned may be trademarks or registered trademarks of their respective owners.
</p>
</div>
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript">
Modified: cocoon/site/site/2.2/core-modules/core/2.2/810_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.2/core-modules/core/2.2/810_1_1.html?rev=1329677&r1=1329676&r2=1329677&view=diff
==============================================================================
--- cocoon/site/site/2.2/core-modules/core/2.2/810_1_1.html (original)
+++ cocoon/site/site/2.2/core-modules/core/2.2/810_1_1.html Tue Apr 24 12:39:52 2012
@@ -29,17 +29,13 @@
<head>
<title> Cocoon Core - map:actions
</title>
- <style type="text/css" media="all">
- @import url("./css/maven-base.css");
- @import url("./css/maven-theme.css");
- @import url("./css/site.css");
- </style>
+ <link rel="stylesheet" href="./css/apache-cocoon-thien-maven-skin.min.css" />
<link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
- <script src="./js/getBlank.js" language="javascript" type="text/javascript"></script>
- <meta name="author" content="The Cocoon Community" />
- <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+ <script src="./js/apache-cocoon-thien-maven-skin.min.js" language="javascript" type="text/javascript"></script>
+ <meta name="author" content="Apache Cocoon Documentation Team" />
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
</head>
- <body>
+ <body onload="javascript:prettyPrint();">
<div id="breadtrail">
<p><a href="http://www.apache.org">Apache</a> » <a href="../../../../">Cocoon</a> »</p>
</div>
@@ -77,7 +73,7 @@
<li><a href="../../../../2.2/core-modules/">Core <span class="pl-version-small">2.2</span></a></li>
<li><a href="../../../../2.2/blocks/">Blocks <span class="pl-version-small">2.2</span></a></li>
<li><a href="../../../../2.2/maven-plugins/">Maven Plugins <span class="pl-version-small">2.2</span></a></li>
- <li><strong><a href="../../../..//3.0/">Cocoon 3.0 <span class="pl-version-small">[alpha]</span></a></em></strong></li>
+ <li><strong><a href="../../../..//3.0/">Cocoon 3.0</a></em></strong></li>
<li><strong><a href="../../../../subprojects/">Subprojects</a></strong></li>
</ul>
</div>
@@ -92,7 +88,7 @@
<ul>
<li >
- <a href="1270_1_1.html">Introduction</a>
+ <a href="index.html">Introduction</a>
</li>
</ul>
</li>
@@ -253,8 +249,6 @@
-
-
<li class='menuExpand'>
<a href="842_1_1.html">Reference</a>
@@ -359,8 +353,6 @@
-
-
<li class='menuExpand'>
<a href="811_1_1.html">Other elements</a>
@@ -423,10 +415,6 @@
</li>
<li >
- <a href="822_1_1.html">map:pipes</a>
- </li>
-
- <li >
<a href="821_1_1.html">map:reader</a>
</li>
@@ -768,7 +756,7 @@
</li>
<li >
- <a href="1380_1_1.html">Using Control Flow</a>
+ <a href="1380_1_1.html">Using Control Flow</a>
</li>
</ul>
</li>
@@ -802,11 +790,11 @@
</li>
<li >
- <a href="1399_1_1.html">Logging configuration</a>
+ <a href="1399_1_1.html">Logging Configuration</a>
</li>
<li >
- <a href="1259_1_1.html">Component Configurations</a>
+ <a href="1259_1_1.html">Component Configuration</a>
</li>
<li >
@@ -815,43 +803,37 @@
</ul>
</li>
<li>
- Project Documentation
+ Project Reports
<ul>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- <li class='menuCollapse'>
- <a href="project-info.html">Project Information</a>
- </li>
+ <li >
+ <a href="changes-report.html">Changes Report</a>
+ </li>
-
-
-
-
-
-
-
-
- <li class='menuCollapse'>
- <a href="project-reports.html">Project Reports</a>
- </li>
+ <li >
+ <a href="apidocs/">JavaDocs</a>
+ </li>
</ul>
</li>
</ul>
<div class="main">
- <div id="contentBody"><div id="bodyText"><h1 class="docTitle">map:actions</h1><h1>Attributes</h1><table class="bodyTable">
+ <!-- Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License. -->
+ <div id="contentBody"><div id="bodyText"><h1 class="docTitle">map:actions</h1><h1>Attributes</h1><table border="0" class="bodyTable">
<tbody>
<tr class="a">
<th>
@@ -870,18 +852,22 @@
</td>
</tr>
</tbody>
-</table><h1>Occurence</h1><h2>Children</h2><p>This element can have the following children:</p><ul><li>map:action</li></ul></div><div class="editUrl"><div><em>Errors and Improvements?</em> If you see any errors or potential improvements in this document please help
- us: <a href="http://cocoon.zones.apache.org/daisy/cdocs/810?branch=1&language=1">View, Edit or comment</a> on the latest development version (registration required).
- </div></div></div>
+</table><h1>Occurence</h1><div class="section" style="background:none;padding:0;"><h2 style="background:none;padding:0;">Children<a name="Children"></a></h2></div><p>This element can have the following children:</p><ul><li>map:action</li></ul></div></div>
+
</div>
</div>
<!-- end of content -->
<div id="footer">
- <p>©
- 1999-2008
+ <p>Copyright ©
+ 1999-2012
The Apache Software Foundation
+ All Rights Reserved.</p>
+
+ <p>
+ Apache Cocoon, Apache, the Apache feather logo, and the Apache Cocoon project logos are trademarks of The Apache Software Foundation.
+ All other marks mentioned may be trademarks or registered trademarks of their respective owners.
</p>
</div>
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript">