cocoon-docs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From da...@cocoon.zones.apache.org
Subject [DAISY] Updated: Sitemap Evaluation
Date Sat, 29 Sep 2007 14:58:15 GMT
A document has been updated:

http://cocoon.zones.apache.org/daisy/documentation/853.html

Document ID: 853
Branch: main
Language: default
Name: Sitemap Evaluation (unchanged)
Document Type: Cocoon Document (unchanged)
Updated on: 9/29/07 2:57:56 PM
Updated by: Vadim Gritsenko

A new version has been created, state: publish

Parts
=====

Content
-------
This part has been updated.
Mime type: text/xml (unchanged)
File name:  (unchanged)
Size: 10408 bytes (previous version: 10300 bytes)
Content diff:
    <html>
    <body>
    
--- <h1>Intro</h1>
+++ <h1>Introduction</h1>
    
    <p>While you can probably understand the basics of a simple sitemap just by
    looking at it, for some constructs it is essential to have some understanding of
--- how the sitemap is evaluated by Cocoon. Here we will look a bit deeper into
--- that.</p>
+++ how the sitemap is evaluated by Cocoon. Here we will have a deeper look into
+++ this.</p>
    
    <h1>What you already knew</h1>
    
--- <p>When a request enters Cocoon, Cocoon uses a so-called sitemap to determine
+++ <p>When a request enters Cocoon, Cocoon uses a <em>sitemap</em> to determine
    what should be done. The sitemap is an XML file. There is one root sitemap
--- called sitemap.xmap which is located in the root of the Cocoon webapp. The root
--- sitemap can mount other sitemaps, allowing modularisation of Cocoon-based
--- applications.</p>
+++ called sitemap.xmap which is located in the root of the Cocoon web application.
+++ The root sitemap can mount other sitemaps, allowing modularization of
+++ Cocoon-based applications.</p>
    
    <h1>Sitemap evaluation result</h1>
    
--- <p>To decide how a request should be handled, Cocoon starts by looking in the
--- map:pipelines element of the sitemap. Usually this starts from the root sitemap
--- (an exception are 'internal requests' which can be relative to the 'current
--- sitemap').</p>
+++ <p>To decide how a request should be handled, first Cocoon looks for the
+++ map:pipelines element in the sitemap file. Usually, Cocoon will look for this
+++ element in the root sitemap, with an exception of <em>internal requests</em>,
+++ which can be evaluated by Cocoon relative to the <em>current sitemap</em>.</p>
    
    <p>Skipping the details of the sitemap evaluation for a moment, the final result
--- of the evaluation of the sitemap can be one of the following:</p>
+++ of the evaluation of a sitemap must always be one of the following:</p>
    
    <ul>
--- <li>an XML-based pipeline is executed (map:generator or map:aggregate,
--- map:transform's, map:serialize)</li>
+++ <li>an XML-based pipeline is executed (one map:generator or map:aggregate,
+++ series of map:transform's, one map:serialize)</li>
    <li>a reader is executed (map:reader) (a reader's purpose is to serve binary
    content without using an XML pipeline)</li>
    <li>a flow controller is called to:</li>
(10 equal lines skipped)
    <li>an internal Cocoon redirect (does not involve HTTP)</li>
    </ul>
    
--- <li>none of these, in which Cocoon will give the error message "No pipeline
--- matched request".</li>
+++ <li>none of the above, in which case Cocoon will give the error message "No
+++ pipeline matched request".</li>
    </ul>
    
    <h1>The simplest pipeline</h1>
(231 equal lines skipped)


Mime
View raw message