cocoon-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From vgritse...@apache.org
Subject svn commit: r178781 - /cocoon/branches/BRANCH_2_1_X/src/documentation/xdocs/userdocs/transformers/cinclude-transformer.xml
Date Fri, 27 May 2005 14:16:00 GMT
Author: vgritsenko
Date: Fri May 27 07:15:59 2005
New Revision: 178781

URL: http://svn.apache.org/viewcvs?rev=178781&view=rev
Log:
indent / reflow

Modified:
    cocoon/branches/BRANCH_2_1_X/src/documentation/xdocs/userdocs/transformers/cinclude-transformer.xml

Modified: cocoon/branches/BRANCH_2_1_X/src/documentation/xdocs/userdocs/transformers/cinclude-transformer.xml
URL: http://svn.apache.org/viewcvs/cocoon/branches/BRANCH_2_1_X/src/documentation/xdocs/userdocs/transformers/cinclude-transformer.xml?rev=178781&r1=178780&r2=178781&view=diff
==============================================================================
--- cocoon/branches/BRANCH_2_1_X/src/documentation/xdocs/userdocs/transformers/cinclude-transformer.xml
(original)
+++ cocoon/branches/BRANCH_2_1_X/src/documentation/xdocs/userdocs/transformers/cinclude-transformer.xml
Fri May 27 07:15:59 2005
@@ -17,346 +17,360 @@
 <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.0//EN" "document-v10.dtd">
 
 <document>
- <header>
-  <title>CInclude Transformer</title>
-  <subtitle>in @doctitle@</subtitle>
-  <version>0.9</version>
-  <type>Technical document</type>
-  <authors>
-   <person name="Carsten Ziegeler" email="cziegeler@apache.org"/>
-  </authors>
-  <abstract>This document describes the CInclude transformer.</abstract>
- </header>
- <body>
-  <s1 title="CInclude Transformer">
-   <p>This transformer includes XML in the current stream and acts therefore
+  <header>
+    <title>CInclude Transformer</title>
+    <subtitle>in @doctitle@</subtitle>
+    <version>0.9</version>
+    <type>Technical document</type>
+    <authors>
+      <person name="Carsten Ziegeler" email="cziegeler@apache.org"/>
+    </authors>
+    <abstract>This document describes the CInclude transformer.</abstract>
+  </header>
+
+  <body>
+    <s1 title="CInclude Transformer">
+      <p>This transformer includes XML in the current stream and acts therefore
       as a kind of (dynamic) content aggregation. Two forms are supported by
       the transformer: one verbose and flexible approach, and a simple approach.
       We will first discuss the simple approach and
       the more flexible is mentioned in the next chapter. In addition
       the cinclude transformer provides a caching mechanism (for the
       simple include form).</p>
-   <p>
-    This transformer triggers for the element <code>include</code> in the
-    namespace "http://apache.org/cocoon/include/1.0".
-    The <code>src</code> attribute contains the url which points to
-    an xml resource which is included instead of the element.
-    With the attributes <code>element</code>, <code>ns</code> and
-    <code>prefix</code> it is possible to specify an element
-    which surrounds the included content.
-   </p>
-   <ul>
-    <li>Name : cinclude</li>
-    <li>Class: org.apache.cocoon.transformation.CIncludeTransformer</li>
-    <li>Cacheable: no.</li>
-   </ul>
-   <p>
-    A simple example might help to use the CIncludeTransfomer effectively:
-   </p>
-   <p>
-    Add the CIncludeTransformer to the components in your sitemap.xmap
-   </p>
-<source><![CDATA[
+
+      <p>This transformer triggers for the element <code>include</code>
in the
+      namespace "http://apache.org/cocoon/include/1.0". The <code>src</code>
+      attribute contains the url which points to an xml resource which is
+      included instead of the element. With the attributes <code>element</code>,
+      <code>ns</code> and <code>prefix</code> it is possible to specify
an
+      element which surrounds the included content.</p>
+
+      <ul>
+        <li>Name : cinclude</li>
+        <li>Class: org.apache.cocoon.transformation.CIncludeTransformer</li>
+        <li>Cacheable: no.</li>
+      </ul>
+
+      <p>A simple example might help to use the CIncludeTransfomer effectively:</p>
+
+      <p>Add the CIncludeTransformer to the components in your sitemap.xmap</p>
+
+      <source><![CDATA[
 ...
 <map:components>
 ...
-  <map:transformers default="xslt">
-  ...
-    <map:transformer name="cinclude"
-      src="org.apache.cocoon.transformation.CIncludeTransformer"/>
-  ...
-]]></source>
-   <p>
-     Next define in your pipeline to use the CIncludeTransformer
-   </p>
-<source><![CDATA[
+<map:transformers default="xslt">
+...
+<map:transformer name="cinclude"
+src="org.apache.cocoon.transformation.CIncludeTransformer"/>
+...
+      ]]></source>
+
+      <p>Next, define in your pipeline to use the CIncludeTransformer</p>
+
+      <source><![CDATA[
 <map:match pattern="cinc/simple-cinc">
-  <map:generate src="cinc/simple-cinc.xml"/>
-  <map:transform type="cinclude"/>
-  <map:transform src="stylesheets/page/simple-page2html.xsl"/>
-  <map:serialize/>
+<map:generate src="cinc/simple-cinc.xml"/>
+<map:transform type="cinclude"/>
+<map:transform src="stylesheets/page/simple-page2html.xsl"/>
+<map:serialize/>
 </map:match>
-]]></source>
+      ]]></source>
+
+      <p>In this example pipeline it assumed that simple-cinc.xml contains
+      the include element. Beside defining the include element
+      it defines the namespace URI "http://apache.org/cocoon/include/1.0".
+      This helps the CIncludeTransformer to find the tag to get replaced by
+      the xml content referenced via the src attribute.
+      The simple-cinc.xml may look like this:</p>
 
-   <p>
-    In this example pipeline it assumed that simple-cinc.xml contains
-    the include element. Beside defining the include element
-    it defines the namespace URI "http://apache.org/cocoon/include/1.0".
-    This helps the CIncludeTransformer to find the tag to get replaced by
-    the xml content referenced via the src attribute.
-    The simple-cinc.xml may look like this:
-   </p>
-<source><![CDATA[
+      <source><![CDATA[
 <?xml version="1.0" encoding="UTF-8"?>
-<page 
-  xmlns:cinclude="http://apache.org/cocoon/include/1.0">
-  <title>Hello</title>
-  <content>
-    <para>This is my first Cocoon page!</para>
-    <cinclude:include src="include.xml" element="included"/>
-  </content>
+<page
+xmlns:cinclude="http://apache.org/cocoon/include/1.0">
+<title>Hello</title>
+<content>
+<para>This is my first Cocoon page!</para>
+<cinclude:include src="include.xml" element="included"/>
+</content>
 </page>
-]]></source>
+      ]]></source>
+
+      <p>Next you should define the include.xml file which is included.
+      A simple include.xml might look like this:</p>
 
-   <p>
-    Next you should define the include.xml file which is included.
-    A simple include.xml might look like this:
-   </p>
-<source><![CDATA[
+      <source><![CDATA[
 <?xml version="1.0"?>
 <p>
- I am <strong>included</strong> by CIncludeTransformer.
- I come from "include.xml".
+I am <strong>included</strong> by CIncludeTransformer.
+I come from "include.xml".
 </p>
-]]></source>
+      ]]></source>
 
-   <p>
-    Now finally we have everything put together the xml content after the
-    CIncludeTransformer processing will look like this:
-   </p>
-<source><![CDATA[
+      <p>Now finally we have everything put together the xml content after
+      the CIncludeTransformer processing will look like this:</p>
+
+      <source><![CDATA[
 <?xml version="1.0" encoding="UTF-8"?>
-<page 
-  xmlns:cinclude="http://apache.org/cocoon/include/1.0">
-  <title>Hello</title>
-  <content>
-    <para>This is my first Cocoon page!</para>
-    <included>
-      <p>
-        I am <strong>included</strong> by CIncludeTransformer.
-        I come from "include.xml".
-      </p>
-    </included>
-  </content>
+<page
+xmlns:cinclude="http://apache.org/cocoon/include/1.0">
+<title>Hello</title>
+<content>
+<para>This is my first Cocoon page!</para>
+<included>
+<p>
+I am <strong>included</strong> by CIncludeTransformer.
+I come from "include.xml".
+</p>
+</included>
+</content>
 </page>
-]]></source>
-  </s1>
-<s1 title="Including External XML (simple)">
+      ]]></source>
+    </s1>
+
+    <s1 title="Including External XML (simple)">
       <p>One feature of the cinclude transformer (this is currently not
-         supported by the caching cinclude transformer) is including XML from
-       external sources, e.g. files or from an HTTP server. 
-       The <code>cinclude:includexml</code> tag starts including of XML:</p>

+      supported by the caching cinclude transformer) is including XML from
+      external sources, e.g. files or from an HTTP server.
+      The <code>cinclude:includexml</code> tag starts including of XML:</p>
+
       <source>
-&lt;cinclude:includexml&gt;  &lt;!-- Include XML from HTTP server --&gt;
-     &lt;cinclude:src&gt;http://external.news.com/flashnews.xml&lt;/cinclude:src&gt;
-&lt;/cinclude:includexml&gt;
-</source> 
-      <p> This would be a simple way of "get"ting XML data from an
-       external site. Using this method it is also possible to pass parameters in the
-       url - just as you would in a "get" sent from a browser.</p> 
+        &lt;cinclude:includexml&gt;  &lt;!-- Include XML from HTTP server --&gt;
+        &lt;cinclude:src&gt;http://external.news.com/flashnews.xml&lt;/cinclude:src&gt;
+        &lt;/cinclude:includexml&gt;
+      </source>
+
+      <p>This would be a simple way of "get"ting XML data from an
+      external site. Using this method it is also possible to pass parameters in the
+      url - just as you would in a "get" sent from a browser.</p>
+
       <source>
-&lt;cinclude:includexml&gt;  &lt;!-- Include XML from HTTP server --&gt;
-    &lt;cinclude:src&gt;http://external.news.com/flashnews.xml?id=1234&amp;myname=matthew&lt;/cinclude:src&gt;
-&lt;/cinclude:includexml&gt;
-</source> 
-      <p>If the external XML is not valid or not available, the 
-       transformer signals an error to the pipeline and the document containing the
-       include command is not available.</p> 
-      <p>For this purpose the <code>ignoreErrors</code> attribute can be
-       used:</p> 
+        &lt;cinclude:includexml&gt;  &lt;!-- Include XML from HTTP server --&gt;
+        &lt;cinclude:src&gt;http://external.news.com/flashnews.xml?id=1234&amp;myname=matthew&lt;/cinclude:src&gt;
+        &lt;/cinclude:includexml&gt;
+      </source>
+
+      <p>If the external XML is not valid or not available, the
+      transformer signals an error to the pipeline and the document containing the
+      include command is not available.</p>
+
+      <p>For this purpose the <code>ignoreErrors</code> attribute can be
used:</p>
+
       <source>
-&lt;cinclude:includexml ignoreErrors="true"&gt;
-...
-&lt;/cinclude:includexml&gt;</source> 
-    </s1> 
+        &lt;cinclude:includexml ignoreErrors="true"&gt;
+          ...
+        &lt;/cinclude:includexml&gt;
+      </source>
+    </s1>
+
     <s1 title="Including External XML (advanced)">
       <p>The above section shows you how to include XML data from an
-       external source such as an HTTP server using the simple "get" method supplied
-       in the HTTP protocol. For more advanced uses you will wish to be able to send
-       "Post" or other HTTP methods to the server. In addition you may want to
-       actually send XML data to the server - just as you would using an HTML form.
-       The format of this resource is slightly more complicated:</p> 
+      external source such as an HTTP server using the simple "get" method supplied
+      in the HTTP protocol. For more advanced uses you will wish to be able to send
+      "Post" or other HTTP methods to the server. In addition you may want to
+      actually send XML data to the server - just as you would using an HTML form.
+      The format of this resource is slightly more complicated:</p>
       <source>
-&lt;?xml version="1.0"?&gt;
-&lt;data xmlns:cinclude="http://apache.org/cocoon/include/1.0"&gt;
-&lt;cinclude:includexml&gt;
-    &lt;cinclude:src&gt;http://itsunshine/tamino/blah&lt;/cinclude:src&gt;
-    &lt;cinclude:configuration&gt;
-  &lt;cinclude:parameter&gt;
-    &lt;cinclude:name&gt;method&lt;/cinclude:name&gt;
-    &lt;cinclude:value&gt;POST&lt;/cinclude:value&gt;
-  &lt;/cinclude:parameter&gt;
-    &lt;/cinclude:configuration&gt;
-    &lt;cinclude:parameters&gt;
-      &lt;cinclude:parameter&gt;
-    &lt;cinclude:name&gt;message&lt;/cinclude:name&gt;
-    &lt;cinclude:value&gt;Hi there&lt;/cinclude:value&gt;
-  &lt;/cinclude:parameter&gt;
-  &lt;cinclude:parameter&gt;
-    &lt;cinclude:name&gt;_Process&lt;/cinclude:name&gt;
-    &lt;cinclude:value&gt;&lt;name&gt;matti&lt;/name&gt;&lt;age&gt;36&lt;/age&gt;&lt;/cinclude:value&gt;
-  &lt;/cinclude:parameter&gt;
-    &lt;/cinclude:parameters&gt;
-&lt;/cinclude:includexml&gt;
-&lt;/data&gt;
-    </source> 
+        &lt;?xml version="1.0"?&gt;
+        &lt;data xmlns:cinclude="http://apache.org/cocoon/include/1.0"&gt;
+        &lt;cinclude:includexml&gt;
+        &lt;cinclude:src&gt;http://itsunshine/tamino/blah&lt;/cinclude:src&gt;
+        &lt;cinclude:configuration&gt;
+        &lt;cinclude:parameter&gt;
+        &lt;cinclude:name&gt;method&lt;/cinclude:name&gt;
+        &lt;cinclude:value&gt;POST&lt;/cinclude:value&gt;
+        &lt;/cinclude:parameter&gt;
+        &lt;/cinclude:configuration&gt;
+        &lt;cinclude:parameters&gt;
+        &lt;cinclude:parameter&gt;
+        &lt;cinclude:name&gt;message&lt;/cinclude:name&gt;
+        &lt;cinclude:value&gt;Hi there&lt;/cinclude:value&gt;
+        &lt;/cinclude:parameter&gt;
+        &lt;cinclude:parameter&gt;
+        &lt;cinclude:name&gt;_Process&lt;/cinclude:name&gt;
+        &lt;cinclude:value&gt;&lt;name&gt;matti&lt;/name&gt;&lt;age&gt;36&lt;/age&gt;&lt;/cinclude:value&gt;
+        &lt;/cinclude:parameter&gt;
+        &lt;/cinclude:parameters&gt;
+        &lt;/cinclude:includexml&gt;
+        &lt;/data&gt;
+      </source>
+
       <p>Lets look at the tags. The tag <code>cinclude:src</code> defines
the address of the
-       resource we want to access and then comes a list of (optional)
-       connection-specific parameters (enclosed in the <code>cinclude:configuration</code>
tag).
-       In this example the HTTP-method ("POST") is passed into the connection. The
-       format of these parameters is discussed next.</p> 
+      resource we want to access and then comes a list of (optional)
+      connection-specific parameters (enclosed in the <code>cinclude:configuration</code>
tag).
+      In this example the HTTP-method ("POST") is passed into the connection. The
+      format of these parameters is discussed next.</p>
+
       <p>Then comes the list of parameters we wish to pass into the
-       function. Each parameter defined has a name and a value. The value can either
-       be text or XML.</p> 
+      function. Each parameter defined has a name and a value. The value can either
+      be text or XML.</p>
+
       <p>The format of the parameters is the same as for the connection
-       configuration.</p> 
-    </s1> 
-  <s1 title="Caching">
-   <p>This transformer includes XML in the current stream and acts therefore
+      configuration.</p>
+    </s1>
+
+    <s1 title="Caching">
+      <p>This transformer includes XML in the current stream and acts therefore
       as a kind of (dynamic) content aggregation. However, the included content
       might be very big or either it might take a lot of time to fetch
       the content. If, in those cases, your content does not change too
       frequently, you can turn on caching for these contents.</p>
-   <p>
-    To turn on caching, this transformer triggers for the element <code>cached-include</code>

-    in the namespace "http://apache.org/cocoon/include/1.0/caching".
-    The <code>src</code> attribute contains the url which points to
-    an xml resource that is included instead of the element.
-    It is possible to mix the <code>cached-include</code> and the <code>include</code>
-    element, so only parts are cached and others are not.
-   </p>
-   <p>
-    A simple example might help to use the caching effectively:
-   </p>
-   <p>
-     First define your pipeline to use the CIncludeTransformer with
-     caching turned on; you turn on caching by setting the <code>expires</code>
-     parameter to a value greater than 0. The exact meaning of this
-     parameter is explained below.
-   </p>
-<source><![CDATA[
+
+      <p>To turn on caching, this transformer triggers for the element
+      <code>cached-include</code> in the namespace
+      <code>http://apache.org/cocoon/include/1.0/caching</code>.
+      The <code>src</code> attribute contains the url which points to
+      an xml resource that is included instead of the element.
+      It is possible to mix the <code>cached-include</code> and the
+      <code>include</code> element, so only parts are cached and others
+      are not.</p>
+
+      <p>A simple example might help to use the caching effectively:</p>
+
+      <p>First define your pipeline to use the CIncludeTransformer with
+      caching turned on; you turn on caching by setting the <code>expires</code>
+      parameter to a value greater than 0. The exact meaning of this
+      parameter is explained below.</p>
+
+      <source><![CDATA[
 <map:match pattern="cinc/simple-cinc">
-  <map:generate src="cinc/simple-cinc.xml"/>
-  <map:transform type="cinclude">
-      <map:parameter name="expires" value="600"/>
-  </map:transform>
-  <map:transform src="stylesheets/page/simple-page2html.xsl"/>
-  <map:serialize/>
+<map:generate src="cinc/simple-cinc.xml"/>
+<map:transform type="cinclude">
+<map:parameter name="expires" value="600"/>
+</map:transform>
+<map:transform src="stylesheets/page/simple-page2html.xsl"/>
+<map:serialize/>
 </map:match>
-]]></source>
+      ]]></source>
 
-   <p>
-    In this example-pipeline it is assumed that simple-cinc.xml contains
-    the <code>cached-include</code> element. Beside defining the element
-    it uses the namespace URI "http://apache.org/cocoon/include/1.0".
-    This helps the transformer to find the tag to get replaced by
-    the xml content referenced via the src attribute.
-    The simple-cinc.xml may look like this:
-   </p>
-<source><![CDATA[
+      <p>In this example-pipeline it is assumed that simple-cinc.xml
+      contains the <code>cached-include</code> element. Beside defining
+      the element it uses the namespace URI
+      <code>http://apache.org/cocoon/include/1.0</code>. This helps the
+      transformer to find the tag to get replaced by the xml content
+      referenced via the src attribute. The simple-cinc.xml may look like
+      this:</p>
+
+      <source><![CDATA[
 <?xml version="1.0" encoding="UTF-8"?>
-<page 
-  xmlns:cinclude="http://apache.org/cocoon/include/1.0">
-  <title>Hello</title>
-  <content>
-    <para>This is my first Cocoon page!</para>
-    <cinclude:cached-include src="http://server/document1.xml"/>
-    <cinclude:cached-include src="http://server/document2.xml"/>
-  </content>
+<page
+xmlns:cinclude="http://apache.org/cocoon/include/1.0">
+<title>Hello</title>
+<content>
+<para>This is my first Cocoon page!</para>
+<cinclude:cached-include src="http://server/document1.xml"/>
+<cinclude:cached-include src="http://server/document2.xml"/>
+</content>
 </page>
-]]></source>
+      ]]></source>
+
+      <p>Now finally we have everything put together the xml content after
+      the CIncludeTransformer processing will look like this:</p>
 
-   <p>
-    Now finally we have everything put together the xml content after the
-    CIncludeTransformer processing will look like this:
-   </p>
-<source><![CDATA[
+      <source><![CDATA[
 <?xml version="1.0" encoding="UTF-8"?>
-<page 
-  xmlns:cinclude="http://apache.org/cocoon/include/1.0">
-  <title>Hello</title>
-  <content>
-    <para>This is my first Cocoon page!</para>
-    <document1>
-        CONTENT OF document 1
-    </document1>
-    <document2>
-        CONTENT OF document 2
-    </document2>
-  </content>
+<page
+xmlns:cinclude="http://apache.org/cocoon/include/1.0">
+<title>Hello</title>
+<content>
+<para>This is my first Cocoon page!</para>
+<document1>
+CONTENT OF document 1
+</document1>
+<document2>
+CONTENT OF document 2
+</document2>
+</content>
 </page>
-]]></source>
-  <p>So, of course even with caching turned on, this transformer acts like the 
-  usual cinclude transformer. But as you can see from the example above, you 
-  can define an expires value. The fetched content is cached for the duration of 
-  this value; in the example above the content is cached for 10 minutes. So, if 
-  during the next 10 minutes after the first time this pipeline was processed, 
-  someone else requests this pipeline, the content is not fetched again from a 
-  distant server (or whereever the content is stored). It is directly delivered 
-  from the cache. When the 10 minutes have expired, the next time the pipeline 
-  is requested, the content is fetched again and stored in the cache for the 
-  next 10 minutes.</p>
-  <p>You can fine tune the behaviour of the transformer with several parameters.</p>
-  <p>The <code>expires</code> parameter defines the expiration date of
the
-    content in seconds from the time the pipeline is requested.</p>
- <p>Usually the content is cached in the common store, but you
-   can also define a writeable/modifiable source with the "source" parameter,
- e.g. "file:/c:/temp". Then the cached content is written into this
- directory.</p>
- <p>With the optional <code>purge</code> set to <code>true</code>
-  the cache is purged which means the cached content is regarded as
-  invalid nevertheless if it has expired or not.</p>
- <p>With the optional parameter <code>parallel</code> the various
-  included contents are processed (included) in parallel rather than
-  in a series.</p>
- <p>With the optional parameter <code>preemptive</code> set to <code>true</code>
-  a pre-emptive caching is activated. When a resource is requested with
-  pre-emptive caching, this transformer always attempts to get the 
-  content from the cache. If the content is not in the cache, it is
-  of course retrieved from the original source and cached.
-  If the cached resource has expired, it is still provided. The cache
-  is updated by a background task. This task has to be started
-  beforehand.</p>
-   <p>
-     Complete Example:
-   </p>
-<source><![CDATA[
+      ]]></source>
+
+      <p>So, of course even with caching turned on, this transformer acts like the
+      usual cinclude transformer. But as you can see from the example above, you
+      can define an expires value. The fetched content is cached for the duration of
+      this value; in the example above the content is cached for 10 minutes. So, if
+      during the next 10 minutes after the first time this pipeline was processed,
+      someone else requests this pipeline, the content is not fetched again from a
+      distant server (or whereever the content is stored). It is directly delivered
+      from the cache. When the 10 minutes have expired, the next time the pipeline
+      is requested, the content is fetched again and stored in the cache for the
+      next 10 minutes.</p>
+      <p>You can fine tune the behaviour of the transformer with several parameters.</p>
+      <p>The <code>expires</code> parameter defines the expiration date
of the
+      content in seconds from the time the pipeline is requested.</p>
+      <p>Usually the content is cached in the common store, but you
+      can also define a writeable/modifiable source with the "source" parameter,
+      e.g. "file:/c:/temp". Then the cached content is written into this
+      directory.</p>
+      <p>With the optional <code>purge</code> set to <code>true</code>
+      the cache is purged which means the cached content is regarded as
+      invalid nevertheless if it has expired or not.</p>
+      <p>With the optional parameter <code>parallel</code> the various
+      included contents are processed (included) in parallel rather than
+      in a series.</p>
+      <p>With the optional parameter <code>preemptive</code> set to <code>true</code>
+      a pre-emptive caching is activated. When a resource is requested with
+      pre-emptive caching, this transformer always attempts to get the
+      content from the cache. If the content is not in the cache, it is
+      of course retrieved from the original source and cached.
+      If the cached resource has expired, it is still provided. The cache
+      is updated by a background task. This task has to be started
+      beforehand.</p>
+
+      <p>Complete Example:</p>
+
+      <source><![CDATA[
 <map:match pattern="cinc/simple-cinc">
-  <map:generate src="cinc/simple-cinc.xml"/>
-  <map:transform type="cinclude">
-      <map:parameter name="expires" value="600"/>
-      <map:parameter name="purge" value="false"/>
-      <map:parameter name="parallel" value="true"/>
-      <map:parameter name="preemptive" value="false"/>
-      <map:parameter name="source" value="file:/c:/temp"/>
-  </map:transform>
-  <map:transform src="stylesheets/page/simple-page2html.xsl"/>
-  <map:serialize/>
+<map:generate src="cinc/simple-cinc.xml"/>
+<map:transform type="cinclude">
+<map:parameter name="expires" value="600"/>
+<map:parameter name="purge" value="false"/>
+<map:parameter name="parallel" value="true"/>
+<map:parameter name="preemptive" value="false"/>
+<map:parameter name="source" value="file:/c:/temp"/>
+</map:transform>
+<map:transform src="stylesheets/page/simple-page2html.xsl"/>
+<map:serialize/>
 </map:match>
-]]></source>
-  </s1>
-  <s1 title="Configuration">
-<p>Besides the usual transformer configuration, this transformer requires some components.
-You have to add the following lines to the cocoon.xconf:</p>
-<source><![CDATA[
- <component class="org.apache.cocoon.transformation.helpers.DefaultIncludeCacheManager"

-            role="org.apache.cocoon.transformation.helpers.IncludeCacheManager"
-            logger="test">
-    <!-- Specify this only if you use preemptive-caching -->
-    <parameter name="preemptive-loader-url" value="http://localhost:8080/cocoon/loader"/>
- </component>
-]]></source>
-  <p>If you want to use preemptive caching, you have to specify a URI inside Cocoon
that contains 
-     the preemptive-loader action. This pipeline is automatically called, when
-     preemptive loading is actived and requried. It loads the content in the background.</p>
-     <p>First you have to define the action:</p>
-<source><![CDATA[
+      ]]></source>
+    </s1>
+
+    <s1 title="Configuration">
+      <p>Besides the usual transformer configuration, this transformer requires some
components.
+      You have to add the following lines to the cocoon.xconf:</p>
+
+      <source><![CDATA[
+      <component class="org.apache.cocoon.transformation.helpers.DefaultIncludeCacheManager"
+      role="org.apache.cocoon.transformation.helpers.IncludeCacheManager"
+      logger="test">
+      <!-- Specify this only if you use preemptive-caching -->
+      <parameter name="preemptive-loader-url" value="http://localhost:8080/cocoon/loader"/>
+      </component>
+      ]]></source>
+
+      <p>If you want to use preemptive caching, you have to specify a URI inside Cocoon
that contains
+      the preemptive-loader action. This pipeline is automatically called, when
+      preemptive loading is actived and requried. It loads the content in the background.</p>
+      <p>First you have to define the action:</p>
+
+      <source><![CDATA[
 ...
 <map:components>
 ...
-  <map:actions>
-  ...
-      <map:action name="preemptive"
-                  src="org.apache.cocoon.transformation.helpers.PreemptiveLoaderAction"/>
-  ...
-]]></source>  
-   <p>Then you must define a pipeline containing the action. This is the pipeline that
-   has to be configured in the cocoon.xconf:</p>
-<source><![CDATA[
-   <map:match pattern="loader">
-       <map:act type="preemptive"></map:act>
-   </map:match>
-]]></source>  
-</s1>
- </body>
+<map:actions>
+...
+<map:action name="preemptive"
+src="org.apache.cocoon.transformation.helpers.PreemptiveLoaderAction"/>
+...
+      ]]></source>
+
+      <p>Then you must define a pipeline containing the action. This is the pipeline
that
+      has to be configured in the cocoon.xconf:</p>
+
+      <source><![CDATA[
+      <map:match pattern="loader">
+      <map:act type="preemptive"></map:act>
+      </map:match>
+      ]]></source>
+    </s1>
+  </body>
 </document>



Mime
View raw message