cocoon-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ilgro...@apache.org
Subject svn commit: r1329268 [1/4] - in /cocoon/site/site/2.2: ./ css/ images/ js/
Date Mon, 23 Apr 2012 14:59:39 GMT
Author: ilgrosso
Date: Mon Apr 23 14:59:38 2012
New Revision: 1329268

URL: http://svn.apache.org/viewvc?rev=1329268&view=rev
Log:
Publishing updated Cocoon 2.2 site

Added:
    cocoon/site/site/2.2/css/apache-cocoon-thien-maven-skin.min.css   (with props)
    cocoon/site/site/2.2/dependency-management.html   (with props)
    cocoon/site/site/2.2/distribution-management.html   (with props)
    cocoon/site/site/2.2/images/close.gif   (with props)
    cocoon/site/site/2.2/images/external.png   (with props)
    cocoon/site/site/2.2/integration.html   (with props)
    cocoon/site/site/2.2/issue-tracking.html   (with props)
    cocoon/site/site/2.2/js/apache-cocoon-thien-maven-skin.min.js   (with props)
    cocoon/site/site/2.2/plugins.html   (with props)
Removed:
    cocoon/site/site/2.2/.htaccess
    cocoon/site/site/2.2/1327_1_1.html
Modified:
    cocoon/site/site/2.2/1159_1_1.html
    cocoon/site/site/2.2/1290_1_1.html
    cocoon/site/site/2.2/1291_1_1.html
    cocoon/site/site/2.2/1347_1_1.html
    cocoon/site/site/2.2/1362_1_1.html
    cocoon/site/site/2.2/1366_1_1.html
    cocoon/site/site/2.2/1402_1_1.html
    cocoon/site/site/2.2/1420_1_1.html
    cocoon/site/site/2.2/1447_1_1.html
    cocoon/site/site/2.2/1448_1_1.html
    cocoon/site/site/2.2/1454_1_1.html
    cocoon/site/site/2.2/css/site.css
    cocoon/site/site/2.2/dependencies.html
    cocoon/site/site/2.2/images/cocoon-logo.gif
    cocoon/site/site/2.2/images/cocoon_logo.jpg
    cocoon/site/site/2.2/images/cocoon_logo.png
    cocoon/site/site/2.2/index.html
    cocoon/site/site/2.2/license.html
    cocoon/site/site/2.2/project-info.html
    cocoon/site/site/2.2/project-summary.html

Modified: cocoon/site/site/2.2/1159_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.2/1159_1_1.html?rev=1329268&r1=1329267&r2=1329268&view=diff
==============================================================================
--- cocoon/site/site/2.2/1159_1_1.html (original)
+++ cocoon/site/site/2.2/1159_1_1.html Mon Apr 23 14:59:38 2012
@@ -29,17 +29,13 @@
   <head>
     <title>      Cocoon 2.2 Site - Your first Cocoon application using Maven 2
   </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> &raquo; <a href="../">Cocoon</a> &raquo;</p>
     </div>
@@ -74,7 +70,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>
@@ -89,7 +85,7 @@
             <ul>
                   
     <li >
-              <a href="1327_1_1.html">Overview</a>
+              <a href="index.html">Overview</a>
         </li>
                   
     <li >
@@ -99,10 +95,6 @@
     <li >
               <a href="1420_1_1.html">New in 2.2</a>
         </li>
-                  
-    <li >
-              <a href="1454_1_1.html">Test2</a>
-        </li>
               </ul>
     </li>
       <li>
@@ -150,116 +142,136 @@
     </li>
       </ul>
        <div class="main">
-         <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Your first Cocoon application using Maven 2</h1><p>In this tutorial, you will:</p><ol type="1">
+         <!-- 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">Your first Cocoon application using Maven 2</h1><p>In this tutorial, you will:</p><ol style="list-style-type: decimal">
 <li>Create a Cocoon block (the application resources and logic)</li>
 <li>Import the block as a project in Eclipse</li>
 <li>Start the block as a web application and access it from your browser</li>
-</ol><div class="note"><div><strong>Note: </strong>First, make sure that you have Maven 2.0.9 or above installed.
-You can check this by calling <tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">mvn --version</tt> from the command line. If
+</ol><div class="note"><div><b>Note: </b>First, make sure that you have Maven 2.0.9 or above installed.
+You can check this by calling <tt>mvn --version</tt> from the command line. If
 this doesn't work for you, read the
-<a href="http://maven.apache.org/guides/getting-started/maven-in-five-minutes.html">Maven
-in 5 Minutes</a> tutorial.</div></div><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Creating a Cocoon block</h1>Create a new directory which will be the root directory of your Cocoon
+<a class="externalLink" href="http://maven.apache.org/guides/getting-started/maven-in-five-minutes.html">Maven
+in 5 Minutes</a> tutorial.</div></div><h1>Creating a Cocoon block</h1>Create a new directory which will be the root directory of your Cocoon
 application and change into it. For this tutorial, let's name it
 <tt>getting-started-app</tt>.The next step is to create a Cocoon block to contain your custom application.
-The development of any Cocoon web application should be done within one or more 
-blocks.  Cocoon blocks are little different to other Maven blocks except they
+The development of any Cocoon web application should be done within one or more&#xa0;
+blocks.&#xa0; Cocoon blocks are little different to other Maven blocks except they
 have a particular expected <a href="../2.2/core-modules/core/2.2/1263_1_1.html">directory and file
-structure</a>.<div class="note"><div><strong>Note: </strong>You could manually create your blocks, but a simpler and less
-error-prone process is to use Maven's 'archetype' plugin.  This allows you to
-select from a list of block types and have Maven create them for you.  By
-default, the list of Maven archetypes is quite large.  For convenience, a
+structure</a>.<div class="note"><div><b>Note: </b>You could manually create your blocks, but a simpler and less
+error-prone process is to use Maven's 'archetype' plugin.&#xa0; This allows you to
+select from a list of block types and have Maven create them for you.&#xa0; By
+default, the list of Maven archetypes is quite large.&#xa0; For convenience, a
 catalog of Cocoon specific archetypes is available on the Cocoon web site and
-you will make use of this in the following instructions.</div></div>Run the following Maven command:<pre>mvn archetype:generate -DarchetypeCatalog=http://cocoon.apache.org
-</pre><p>Maven will generate some output and then interactively ask you for some
-information:</p><pre>Choose archetype:
+you will make use of this in the following instructions.</div></div>Run the following Maven command:<div><pre>mvn archetype:generate -DarchetypeCatalog=http://cocoon.apache.org
+</pre></div><p>Maven will generate some output and then interactively ask you for some
+information:</p><div><pre>Choose archetype:
 1: remote -&gt; cocoon-22-archetype-block-plain (Creates an empty Cocoon block; useful
- if you want to add another block to a Cocoon application)
+&#xa0;if you want to add another block to a Cocoon application)
 2: remote -&gt; cocoon-22-archetype-block (Creates a Cocoon block containing some small
- samples)
+&#xa0;samples)
 3: remote -&gt; cocoon-22-archetype-webapp (Creates a web application configured to
  host Cocoon blocks. Just add the block dependencies)
-Choose a number:  (1/2/3): <strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">2</strong>
-</pre><p>Maven first asks which archetype you want to create.  Item 2 in this list is
-the standard Cocoon block with some small sample files already in place.</p><pre>Define value for groupId: : <strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">com.mycompany</strong>
-Define value for artifactId: : <strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">myBlock1</strong>
-Define value for version:  1.0-SNAPSHOT: : <strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">1.0.0</strong>
-Define value for package: : <strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">com.mycompany.myBlock1</strong><strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher"><strong>
-</strong></strong></pre><p>Maven then asks a few more questions.  Just enter the details as shown
-above.  The groupId is a label that you can use to group all the blocks in your
-application.  The artifactId is the unique label that will identify this block
-from all others.  It is also the name of the directory that will be created to
-contain the block's files.  The package is the Java package that any Java files
-in the block will be assigned to.</p><div class="note"><div><strong>Note: </strong>If you are using a cocoon binary build from svn trunk then you
+Choose a number:  (1/2/3): <b>2</b>
+</pre></div><p>Maven first asks which archetype you want to create.&#xa0; Item 2 in this list is
+the standard Cocoon block with some small sample files already in place.</p><div><pre>Define value for groupId: : <b>com.mycompany</b>
+Define value for artifactId: : <b>myBlock1</b>
+Define value for version:  1.0-SNAPSHOT: : <b>1.0.0</b>
+Define value for package: : <b>com.mycompany.myBlock1</b><b><b>
+</b></b></pre></div><p>Maven then asks a few more questions.&#xa0; Just enter the details as shown
+above.&#xa0; The groupId is a label that you can use to group all the blocks in your
+application.&#xa0; The artifactId is the unique label that will identify this block
+from all others.&#xa0; It is also the name of the directory that will be created to
+contain the block's files.&#xa0; The package is the Java package that any Java files
+in the block will be assigned to.</p><div class="note"><div><b>Note: </b>If you are using a cocoon binary build from svn trunk then you
 probably want to change the archetypeVersion to the most recent one, matching
 the svn trunk. (see
-<tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">[<tt>c</tt></tt><tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">ocoon-svn]/tools/archetypes/cocoon-22-archetype-block/pom.xml</tt>)
-</div></div><p>Looking at the filesystem, you should find following directory structure:</p><pre>getting-started-app
-<tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher"> +-</tt><tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">myBlock1
+<tt>[<tt>c</tt></tt><tt>ocoon-svn]/tools/archetypes/cocoon-22-archetype-block/pom.xml</tt>)
+</div></div><p>Looking at the filesystem, you should find following directory structure:</p><div><pre>getting-started-app
+<tt>&#xa0;+-</tt><tt>myBlock1
     +-pom.xml
     +-src
        +-[...]
-</tt></pre><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Import the block in Eclipse</h1><div class="note"><div><strong>Note: </strong>Cocoon is not tied to Eclipse IDE by any means. This step only
+</tt></pre></div><h1>Import the block in Eclipse</h1><div class="note"><div><b>Note: </b>Cocoon is not tied to Eclipse IDE by any means. This step only
 describes what can be done to avoid tedious work of setting up project in
-Eclipse manually.<br xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher"></br>
+Eclipse manually.<br />
 If you don't use Eclipse, you can either skip this step or find a similar
-procedure to load the block in the IDE of your choice.</div></div><p>Change into the <tt>myBlock1</tt> directory and call</p><pre>mvn eclipse:eclipse</pre><p>This will create the necessary project descriptors for Eclipse. In Eclipse
-you can import the project into your workspace: <em>File &gt;  Import... &gt;
-Existing Projects into Workspace</em></p><p>If that's the first time you use Eclipse together with a project created by
+procedure to load the block in the IDE of your choice.</div></div><p>Change into the <tt>myBlock1</tt> directory and call</p><div><pre>mvn eclipse:eclipse</pre></div><p>This will create the necessary project descriptors for Eclipse. In Eclipse
+you can import the project into your workspace: <i>File &gt;&#xa0; Import... &gt;
+Existing Projects into Workspace</i></p><p>If that's the first time you use Eclipse together with a project created by
 Maven 2, we recommend you read the
-<a href="http://maven.apache.org/guides/mini/guide-ide-eclipse.html">Maven Guide
-using Eclipse with Maven 2.x</a>.</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Run the block as Java web application</h1><p>After creating the Cocoon block you probably want to run it. For this purpose
+<a class="externalLink" href="http://maven.apache.org/guides/mini/guide-ide-eclipse.html">Maven Guide
+using Eclipse with Maven 2.x</a>.</p><h1>Run the block as Java web application</h1><p>After creating the Cocoon block you probably want to run it. For this purpose
 there is a Maven plugin that generates a minimal web application that loads your
-block. The pom.xml of your block already contains the necessary settings.</p><pre>mvn jetty:run</pre><p>and point your browser at <tt>http://localhost:8888/myBlock1/</tt> and get a
-hello world page.</p><div class="note"><div><strong>Note: </strong>The mentioned minimal web application is automatically created,
-when <tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">mvn jetty:run</tt> is invoked. This happens because the rcl goal of the
+block. The pom.xml of your block already contains the necessary settings.</p><div><pre>mvn jetty:run</pre></div><p>and point your browser at <tt>http://localhost:8888/myBlock1/</tt> and get a
+hello world page.</p><div class="note"><div><b>Note: </b>The mentioned minimal web application is automatically created,
+when <tt>mvn jetty:run</tt> is invoked. This happens because the rcl goal of the
 Cocoon plugin is bound to the Maven build lifecycle which is invoked too, when
-the jetty:run goal is executed. See the block's <tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">pom.xml </tt>for details.
-</div></div><div class="note"><div><strong>Note: </strong>This process can be manually triggered with <tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">mvn
-cocoon:prepare</tt> too.</div></div><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Conclusion and further information</h1><p>So far you have created a Cocoon block and been able to run it in Jetty. 
-This is only the first step to creating a full-blown Cocoon application.  If you
-would like to know  more read the following tutorials:</p><ul>
-<li><a href="1290_1_1.html">Your first XML pipeline</a><br></br>
-Cocoon is well known for its XML pipelines.  In this tutorial you will learn how
+the jetty:run goal is executed. See the block's <tt>pom.xml </tt>for details.
+</div></div><div class="note"><div><b>Note: </b>This process can be manually triggered with <tt>mvn
+cocoon:prepare</tt> too.</div></div><h1>Conclusion and further information</h1><p>So far you have created a Cocoon block and been able to run it in Jetty.&#xa0;
+This is only the first step to creating a full-blown Cocoon application.&#xa0; If you
+would like to know&#xa0; more read the following tutorials:</p><ul>
+<li><a href="1290_1_1.html">Your first XML pipeline</a><br />
+Cocoon is well known for its XML pipelines.&#xa0; In this tutorial you will learn how
 to setup your first pipeline and discover the power of Cocoon sitemaps.</li>
-<li><a href="1291_1_1.html">Adding a second block</a><br></br>
+<li><a href="1291_1_1.html">Adding a second block</a><br />
 This tutorial creates a web application that has a dependency on another block.
 There are use cases that require more than one block, e.g. you want to have all
 style specific resources within a single block that can be easily exchanged at
 deployment time (aka skinning).</li>
-<li><a href="../2.2/maven-plugins/maven-plugin/1.0/1297_1_1.html">Usage of the reloading classloader plugin</a><br></br>
+<li><a href="../2.2/maven-plugins/maven-plugin/1.0/1297_1_1.html">Usage of the reloading classloader plugin</a><br />
 The reloading classloader plugin enables rapid development of Cocoon
 applications since you don't have to restart the servlet container whenever one
 of your Java classes changes. Additionally, it enables the reloading of Cocoon
 resources too if they change.</li>
-<li><a href="1362_1_1.html">Deploying a Cocoon application<br></br>
+<li><a href="1362_1_1.html">Deploying a Cocoon application<br />
 </a>Eventually, you will probably need to create a Java web application (war
 file) in order to deploy your application to a servlet container such as Tomcat
-or Jetty, etc.  This tutorial shows you how.<a href="../2.2/core-modules/core/2.2/1263_1_1.html"><br></br>
+or Jetty, etc.&#xa0; This tutorial shows you how.<a href="../2.2/core-modules/core/2.2/1263_1_1.html"><br />
 </a></li>
-</ul>For the time being, we <em>recommend</em> you use <em>Maven 2</em> as your
+</ul>For the time being, we <i>recommend</i> you use <i>Maven 2</i> as your
 build system (though there is no hard dependency on it). This has the advantage
 that the build system is standardized and Cocoon web applications can reuse the
 toolset (create Eclipse configuration files, create releases, produce
 documentation, etc.). More information about Maven 2 can be found at the project
-<a href="http://maven.apache.org">website</a>.  We especially recommend reading:
+<a class="externalLink" href="http://maven.apache.org">website</a>.&#xa0; We especially recommend reading:
 <ul>
 <li>
-<a href="http://maven.apache.org/guides/getting-started/maven-in-five-minutes.html">Maven
+<a class="externalLink" href="http://maven.apache.org/guides/getting-started/maven-in-five-minutes.html">Maven
 in 5 minutes</a> and the</li>
-<li><a href="http://maven.apache.org/guides/getting-started/index.html">Getting
+<li><a class="externalLink" href="http://maven.apache.org/guides/getting-started/index.html">Getting
 started guide</a></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/1159?branch=1&language=1">View, Edit or comment</a> on the latest development version (registration required).
-      </div></div></div>
+</ul></div></div>
+       
        </div>
     </div>
 
     <!-- end of content -->
     <div id="footer">
-      <p>&#169;  
-          1999-2008
+      <p>Copyright &copy;  
+          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/1290_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.2/1290_1_1.html?rev=1329268&r1=1329267&r2=1329268&view=diff
==============================================================================
--- cocoon/site/site/2.2/1290_1_1.html (original)
+++ cocoon/site/site/2.2/1290_1_1.html Mon Apr 23 14:59:38 2012
@@ -29,17 +29,13 @@
   <head>
     <title>      Cocoon 2.2 Site - Your first XML pipeline (publishing)
   </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> &raquo; <a href="../">Cocoon</a> &raquo;</p>
     </div>
@@ -74,7 +70,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>
@@ -89,7 +85,7 @@
             <ul>
                   
     <li >
-              <a href="1327_1_1.html">Overview</a>
+              <a href="index.html">Overview</a>
         </li>
                   
     <li >
@@ -99,10 +95,6 @@
     <li >
               <a href="1420_1_1.html">New in 2.2</a>
         </li>
-                  
-    <li >
-              <a href="1454_1_1.html">Test2</a>
-        </li>
               </ul>
     </li>
       <li>
@@ -150,82 +142,98 @@
     </li>
       </ul>
        <div class="main">
+         <!-- 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">Your first XML pipeline (publishing)</h1><p>This tutorial is based on the <a href="1159_1_1.html">&quot;Your first Cocoon
 application using Maven 2&quot;</a> guide which shows how to bootstrap a Cocoon
-project.</p><p>In this tutorial you will</p><ol type="1">
+project.</p><p>In this tutorial you will</p><ol style="list-style-type: decimal">
 <li>get an overview of what Cocoon pipelines and sitemaps are</li>
 <li>create your first pipeline that emits XML</li>
 <li>enhance this first pipeline by adding an XML transformation step based on
 XSLT that produces HTML as output</li>
 <li>write a pipeline that creates a PDF document</li>
-</ol><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Overview</h1>Cocoon is based around the concept of pipelines:<img width="713" height="223" name="pipeline" alt="pipeline" src="NO_LINK"></img>If a request comes in, a <a href="../2.2/core-modules/core/2.2/850_1_1.html"><strong>generator</strong>
-</a>produces <a href="http://www.saxproject.org/">SAX events</a> that represent
-the XML, <a href="../2.2/core-modules/core/2.2/851_1_1.html"><strong>tranformers</strong> </a>can alter the
+</ol><h1>Overview</h1>Cocoon is based around the concept of pipelines:<img src="NO_LINK" width="713" height="223" alt="pipeline" />If a request comes in, a <a href="../2.2/core-modules/core/2.2/850_1_1.html"><b>generator</b>
+</a>produces <a class="externalLink" href="http://www.saxproject.org/">SAX events</a> that represent
+the XML, <a href="../2.2/core-modules/core/2.2/851_1_1.html"><b>tranformers</b> </a>can alter the
 stream of SAX events and a
-<a href="../2.2/core-modules/core/2.2/849_1_1.html"><strong>serializ<strong>e</strong></strong><strong>r</strong></a>
+<a href="../2.2/core-modules/core/2.2/849_1_1.html"><b>serializ<b>e</b></b><b>r</b></a>
 finally creates an output stream which is sent to the client.The image above shows the 3 most popular components:<ul>
 <li>file generator</li>
 <li>XSLT transformer</li>
 <li>HTML serializer</li>
-</ul><strong>Sitemaps</strong> are used to define those pipelines and connect them
+</ul><b>Sitemaps</b> are used to define those pipelines and connect them
 with requests. These connections are defined by some kind of rules. In the
-context  of Cocoon  those rules are named matchers. Whenever one of those rules
-(<em>matcher</em>) matches, a pipeline is executed.<h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Create a pipeline in the sitemap</h1>First, open <tt>src\main\resources\COB-INF\sitemap.xmap</tt> in your favorite
+context&#xa0; of Cocoon&#xa0; those rules are named matchers. Whenever one of those rules
+(<i>matcher</i>) matches, a pipeline is executed.<h1>Create a pipeline in the sitemap</h1>First, open <tt>src\main\resources\COB-INF\sitemap.xmap</tt> in your favorite
 XML editor. That's your block's base sitemap. There are already some pipelines
 there (<tt>/sitemap/pipelines</tt>) but for the sake of this tutorial, let's
-create your own pipeline.<pre>&lt;map:sitemap xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
+create your own pipeline.<div><pre>&lt;map:sitemap xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
  xsi:schemaLocation=&quot;http://apache.org/cocoon/sitemap/1.0 
   http://cocoon.apache.org/schema/sitemap/cocoon-sitemap-1.0.xsd&quot;
  xmlns:map=&quot;http://apache.org/cocoon/sitemap/1.0&quot;&gt;
 
   &lt;map:pipelines&gt;
-<strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">    &lt;map:pipeline&gt;
-<strong>      &lt;map:match pattern=&quot;myFirstPipeline&quot;&gt;
+<b>    &lt;map:pipeline&gt;
+<b>      &lt;map:match pattern=&quot;myFirstPipeline&quot;&gt;
         &lt;map:generate src=&quot;myXmlFile.xml&quot; type=&quot;file&quot;/&gt;
         &lt;map:serialize type=&quot;xml&quot;/&gt;
-      &lt;/map:match&gt;</strong>
-    &lt;/map:pipeline&gt;</strong>
+      &lt;/map:match&gt;</b>
+    &lt;/map:pipeline&gt;</b>
     [...]
   &lt;/map:pipelines&gt;
 
 &lt;/map:sitemap&gt;
-</pre>The <tt>map:match </tt>element has an attribute <tt>@pattern</tt>. If the
-request <tt>http://localhost:8888/myBlock1/<strong>myFirstPipeline</strong></tt>
-comes in, this matcher <em>matches</em> and the request processing continues
+</pre></div>The <tt>map:match </tt>element has an attribute <tt>@pattern</tt>. If the
+request <tt>http://localhost:8888/myBlock1/<b>myFirstPipeline</b></tt>
+comes in, this matcher <i>matches</i> and the request processing continues
 with the generation of <tt>myXmlFile.xml</tt>. This file has to be in the same
-directory as the sitemap:<pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
+directory as the sitemap:<div><pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
 &lt;content&gt;test&lt;/content&gt;
-</pre><div class="note"><div><strong>Note: </strong>You might wonder why the matcher only has to look for the
-pattern myFirstPipeline. The reason is that <tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">myBlock1</tt> is handled by the
+</pre></div><div class="note"><div><b>Note: </b>You might wonder why the matcher only has to look for the
+pattern myFirstPipeline. The reason is that <tt>myBlock1</tt> is handled by the
 block dispatching mechanism. In particular for your block, this path is set in
-<tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">src/main/resources/META-INF/cocoon/spring/servlet-service.xml</tt> in
-<tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">/beans/bean[id='com.mycompany.myBlock4.block']/context/@mount-path</tt></div></div><p>After saving the sitemap and the XML file, you can point you browser to
+<tt>src/main/resources/META-INF/cocoon/spring/servlet-service.xml</tt> in
+<tt>/beans/bean[id='com.mycompany.myBlock4.block']/context/@mount-path</tt></div></div><p>After saving the sitemap and the XML file, you can point you browser to
 <tt>http://localhost:8888/myBlock</tt><tt><tt>1</tt>/myFirstPipeline</tt> and
 you will see the output of your first own pipeline serialized as XML
-(<tt>&lt;map:serialize type=&quot;xml&quot;/&gt;</tt>).</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Adding an XSLT transformation step</h1><p>The first pipeline wasn't really exciting, just reading some XML file and
+(<tt>&lt;map:serialize type=&quot;xml&quot;/&gt;</tt>).</p><h1>Adding an XSLT transformation step</h1><p>The first pipeline wasn't really exciting, just reading some XML file and
 serializing it without changing anything. The second example will add a
-transformation step based on <a href="http://www.w3.org/TR/xslt">XSLT</a>:</p><pre>&lt;map:sitemap xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
+transformation step based on <a class="externalLink" href="http://www.w3.org/TR/xslt">XSLT</a>:</p><div><pre>&lt;map:sitemap xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
  xsi:schemaLocation=&quot;http://apache.org/cocoon/sitemap/1.0 
   http://cocoon.apache.org/schema/sitemap/cocoon-sitemap-1.0.xsd&quot;
  xmlns:map=&quot;http://apache.org/cocoon/sitemap/1.0&quot;&gt;
 
   &lt;map:pipelines&gt;
     &lt;map:pipeline&gt;
-      &lt;map:match pattern=&quot;myFirstPipeline&quot;&gt;
+     &#xa0;&lt;map:match pattern=&quot;myFirstPipeline&quot;&gt;
         &lt;map:generate src=&quot;myXmlFile.xml&quot; type=&quot;file&quot;/&gt;
         &lt;map:serialize type=&quot;xml&quot;/&gt;
-      &lt;/map:match&gt; <strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher"><strong><strong>      
+      &lt;/map:match&gt; <b><b><b>      
       &lt;map:match pattern=&quot;mySecondPipeline&quot;&gt;
         &lt;map:generate src=&quot;myXmlFile.xml&quot; type=&quot;file&quot;/&gt;
-</strong></strong><strong><strong><strong><strong>        &lt;map:transform src=&quot;myXsltFile.xslt&quot; type=&quot;xslt&quot;/&gt;</strong></strong></strong></strong>
-<strong><strong>        &lt;map:serialize type=&quot;html&quot;/&gt;
-      &lt;/map:match&gt;</strong></strong></strong>
+</b></b><b><b><b><b>        &lt;map:transform src=&quot;myXsltFile.xslt&quot; type=&quot;xslt&quot;/&gt;</b></b></b></b>
+<b><b>        &lt;map:serialize type=&quot;html&quot;/&gt;
+      &lt;/map:match&gt;</b></b></b>
     &lt;/map:pipeline&gt;
     [...]
   &lt;/map:pipelines&gt;
 
-&lt;/map:sitemap&gt;</pre><p>The XSLT file is very simple and creates an XML following the structure of
-XHTML (though without using any namespaces in order to keep things simple):</p><pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
+&lt;/map:sitemap&gt;</pre></div><p>The XSLT file is very simple and creates an XML following the structure of
+XHTML (though without using any namespaces in order to keep things simple):</p><div><pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
 &lt;xsl:stylesheet version=&quot;1.0&quot; xmlns:xsl=&quot;http://www.w3.org/1999/XSL/Transform&quot;&gt;
   &lt;xsl:template match=&quot;/&quot;&gt;
     &lt;html&gt;
@@ -238,22 +246,22 @@ XHTML (though without using any namespac
       &lt;/body&gt;
     &lt;/html&gt;
   &lt;/xsl:template&gt;
-&lt;/xsl:stylesheet&gt;</pre><p>After saving the sitemap and the XSLT file, you can point you browser to
+&lt;/xsl:stylesheet&gt;</pre></div><p>After saving the sitemap and the XSLT file, you can point you browser to
 <tt>http://localhost:8888/myBlock</tt><tt><tt>1</tt>/mySecondPipeline</tt> and
 you will see the output, this time its HTML because of the use of the HTML
-serializer.</p><div class="note"><div><strong>Note: </strong>In this tutorial you have already implemented two pipelines but
+serializer.</p><div class="note"><div><b>Note: </b>In this tutorial you have already implemented two pipelines but
 there is only one pipeline element used in the sitemap. Given this is confusing
 when you use Cocoon sitemaps the first time. However, there is a reason for
-this: The <tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">&lt;pipeline&gt; </tt>element indicates which <em xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">pipeline
-implementation</em> is used. If there is no <tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">@type</tt> attribute, the
+this: The <tt>&lt;pipeline&gt; </tt>element indicates which <i>pipeline
+implementation</i> is used. If there is no <tt>@type</tt> attribute, the
 generators, tranformers and serializers are invoked from a caching pipeline
-implementation. <br xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher"></br>
+implementation. <br />
 When Cocoon developers talk about pipelines, they mean a series of a matcher
 that includes at least a generator and a serializer. Transformers and other
-sitemap components are optional.</div></div><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Creating a PDF</h1><p>The first example created XML and the second one HTML. One of the strength of
+sitemap components are optional.</div></div><h1>Creating a PDF</h1><p>The first example created XML and the second one HTML. One of the strength of
 Cocoon is that it makes it very simple to support many different output formats.
 The result of this third example will be a PDF, again based on
-<em>myXmlFile.xml</em>:</p><pre>&lt;map:sitemap xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
+<i>myXmlFile.xml</i>:</p><div><pre>&lt;map:sitemap xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
  xsi:schemaLocation=&quot;http://apache.org/cocoon/sitemap/1.0 
   http://cocoon.apache.org/schema/sitemap/cocoon-sitemap-1.0.xsd&quot;
  xmlns:map=&quot;http://apache.org/cocoon/sitemap/1.0&quot;&gt;
@@ -268,19 +276,19 @@ The result of this third example will be
         &lt;map:generate src=&quot;myXmlFile.xml&quot; type=&quot;file&quot;/&gt;
         &lt;map:transform src=&quot;myXsltFile.xslt&quot; type=&quot;xslt&quot;/&gt;
         &lt;map:serialize type=&quot;html&quot;/&gt;
-      &lt;/map:match&gt; <strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher"><strong><strong>      
+      &lt;/map:match&gt; <b><b><b>      
       &lt;map:match pattern=&quot;myThirdPipeline&quot;&gt;
         &lt;map:generate src=&quot;myXmlFile.xml&quot; type=&quot;file&quot;/&gt;
-</strong></strong><strong><strong><strong><strong>        &lt;map:transform src=&quot;myXml2PdfFile.xslt&quot; type=&quot;xslt&quot;/&gt;</strong></strong></strong></strong>
-<strong><strong>        &lt;map:serialize type=&quot;fo2pdf&quot;/&gt;
-      &lt;/map:match&gt;</strong></strong></strong>
+</b></b><b><b><b><b>        &lt;map:transform src=&quot;myXml2PdfFile.xslt&quot; type=&quot;xslt&quot;/&gt;</b></b></b></b>
+<b><b>        &lt;map:serialize type=&quot;fo2pdf&quot;/&gt;
+      &lt;/map:match&gt;</b></b></b>
     &lt;/map:pipeline&gt;
     [...]
   &lt;/map:pipelines&gt;
 
-&lt;/map:sitemap&gt;</pre><p>This pipeline needs a different XSLT file which transforms the XML of
+&lt;/map:sitemap&gt;</pre></div><p>This pipeline needs a different XSLT file which transforms the XML of
 myXmlFile.xml to some XML that can be used by
-<a href="http://xmlgraphics.apache.org/fop/">FOP</a> to create PDF:</p><pre>&lt;?xml version=&quot;1.0&quot;?&gt;
+<a class="externalLink" href="http://xmlgraphics.apache.org/fop/">FOP</a> to create PDF:</p><div><pre>&lt;?xml version=&quot;1.0&quot;?&gt;
 &lt;xsl:stylesheet version=&quot;1.0&quot;
   xmlns:xsl=&quot;http://www.w3.org/1999/XSL/Transform&quot;
   xmlns:fo=&quot;http://www.w3.org/1999/XSL/Format&quot;&gt;
@@ -329,33 +337,37 @@ myXmlFile.xml to some XML that can be us
       &lt;/fo:page-sequence&gt;
     &lt;/fo:root&gt;
   &lt;/xsl:template&gt;
-&lt;/xsl:stylesheet&gt;</pre><p>You also have to use a different serializer for this example, a serializer
+&lt;/xsl:stylesheet&gt;</pre></div><p>You also have to use a different serializer for this example, a serializer
 that can use the XML created by the stylesheet and produce PDF based on it.
 Cocoon ships this serializer as part of the FOP block. Since the block that you
 created probably doesn't have the FOP block added as dependency, this has to be
 done before you can test your pipeline. Adding a block requires editing the
-pom.xml of your block:</p><pre>  &lt;dependencies&gt;
+pom.xml of your block:</p><div><pre>  &lt;dependencies&gt;
     [...]
     &lt;dependency&gt;
-      &lt;groupId&gt;<strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">org.apache.cocoon</strong>&lt;/groupId&gt;
-      &lt;artifactId&gt;<strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">cocoon-fop-impl</strong>&lt;/artifactId&gt;
-      &lt;version&gt;<strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">1.0.0</strong>&lt;/version&gt;
+      &lt;groupId&gt;<b>org.apache.cocoon</b>&lt;/groupId&gt;
+      &lt;artifactId&gt;<b>cocoon-fop-impl</b>&lt;/artifactId&gt;
+      &lt;version&gt;<b>1.0.0</b>&lt;/version&gt;
     &lt;/dependency&gt;
     [...]
-  &lt;/dependencies&gt;</pre><p>Rebuild your block</p><pre>mvn compile</pre><p>and start the servlet container again:</p><pre>mvn jetty:run</pre><p>Now you can point your browser at
+  &lt;/dependencies&gt;</pre></div><p>Rebuild your block</p><div><pre>mvn compile</pre></div><p>and start the servlet container again:</p><div><pre>mvn jetty:run</pre></div><p>Now you can point your browser at
 <tt>http://localhost:8888/myBlock</tt><tt><tt>1</tt>/myThirdPipeline</tt> and
-you will get a PDF as result.</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/1290?branch=1&language=1">View, Edit or comment</a> on the latest development version (registration required).
-      </div></div></div>
+you will get a PDF as result.</p></div></div>
+       
        </div>
     </div>
 
     <!-- end of content -->
     <div id="footer">
-      <p>&#169;  
-          1999-2008
+      <p>Copyright &copy;  
+          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/1291_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.2/1291_1_1.html?rev=1329268&r1=1329267&r2=1329268&view=diff
==============================================================================
--- cocoon/site/site/2.2/1291_1_1.html (original)
+++ cocoon/site/site/2.2/1291_1_1.html Mon Apr 23 14:59:38 2012
@@ -29,17 +29,13 @@
   <head>
     <title>      Cocoon 2.2 Site - Modularize Cocoon apps (Using blocks)
   </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> &raquo; <a href="../">Cocoon</a> &raquo;</p>
     </div>
@@ -74,7 +70,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>
@@ -89,7 +85,7 @@
             <ul>
                   
     <li >
-              <a href="1327_1_1.html">Overview</a>
+              <a href="index.html">Overview</a>
         </li>
                   
     <li >
@@ -99,10 +95,6 @@
     <li >
               <a href="1420_1_1.html">New in 2.2</a>
         </li>
-                  
-    <li >
-              <a href="1454_1_1.html">Test2</a>
-        </li>
               </ul>
     </li>
       <li>
@@ -150,46 +142,62 @@
     </li>
       </ul>
        <div class="main">
+         <!-- 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">Modularize Cocoon apps (Using blocks)</h1><p>In the basic tutorial <a href="1159_1_1.html">&quot;Your first Cocoon application
 using Maven 2&quot;</a> you created your first block. Cocoon 2.2 introduced the
 concept of blocks because it should help you to split your application into
 smaller parts. This increases the maintainability and reusability by orders of
-magnitude.</p><p>In this tutorial you will</p><ol type="1">
+magnitude.</p><p>In this tutorial you will</p><ol style="list-style-type: decimal">
 <li>create a second block</li>
 <li>connect one block with another one</li>
 <li>use a pipeline fragement available in one block from within another block
 </li>
-</ol><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Create a second block</h1>For this purpose move into the <tt>getting-started-app</tt> directory and use
-the Maven 2 archetype command again:<pre>mvn archetype:generate -DarchetypeCatalog=http://cocoon.apache.org
-</pre>First choose the archetype:<pre>Choose archetype:
+</ol><h1>Create a second block</h1>For this purpose move into the <tt>getting-started-app</tt> directory and use
+the Maven 2 archetype command again:<div><pre>mvn archetype:generate -DarchetypeCatalog=http://cocoon.apache.org
+</pre></div>First choose the archetype:<div><pre>Choose archetype:
 1: remote -&gt; cocoon-22-archetype-block-plain (Creates an empty Cocoon block; useful
- if you want to add another block to a Cocoon application)
+&#xa0;if you want to add another block to a Cocoon application)
 2: remote -&gt; cocoon-22-archetype-block (Creates a Cocoon block containing some small
- samples)
+&#xa0;samples)
 3: remote -&gt; cocoon-22-archetype-webapp (Creates a web application configured to
  host Cocoon blocks. Just add the block dependencies)
-Choose a number:  (1/2/3): <strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">2
-</strong></pre>Then respond to the other questions as follows:<pre>Define value for groupId: : <strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">com.mycompany</strong>
-Define value for artifactId: : <strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">myBlock2</strong>
-Define value for version:  1.0-SNAPSHOT: : <strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">1.0.0</strong>
-Define value for package: : <strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">com.mycompany.myBlock2</strong></pre><p>The result is a second Cocoon block called myBlock2.  You should find the
-directory structure of your application now looks as follows:</p><pre>getting-started-app
-<tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher"> +-</tt><tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">myBlock1
+Choose a number:  (1/2/3): <b>2
+</b></pre></div>Then respond to the other questions as follows:<div><pre>Define value for groupId: : <b>com.mycompany</b>
+Define value for artifactId: : <b>myBlock2</b>
+Define value for version:  1.0-SNAPSHOT: : <b>1.0.0</b>
+Define value for package: : <b>com.mycompany.myBlock2</b></pre></div><p>The result is a second Cocoon block called myBlock2.&#xa0; You should find the
+directory structure of your application now looks as follows:</p><div><pre>getting-started-app
+<tt>&#xa0;+-</tt><tt>myBlock1
  |  +-pom.xml
  |  +-src
  |     +-[...]</tt>
-<tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher"> +-</tt><tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">myBlock2
+<tt>&#xa0;+-</tt><tt>myBlock2
     +-pom.xml
     +-src
        +-[...]
 
-</tt></pre><p>Move into the myBlock2 folder and execute the following command:</p><pre>mvn install eclipse:eclipse</pre><p>This builds and copies the second block into your local Maven repository so
+</tt></pre></div><p>Move into the myBlock2 folder and execute the following command:</p><div><pre>mvn install eclipse:eclipse</pre></div><p>This builds and copies the second block into your local Maven repository so
 that other dependent blocks and projects can see it and then creates the
-necessary files to allow you to import the block as a project in Eclipse.</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Connect two blocks</h1><p>Let's assume that you want to use a pipeline defined in <tt>myBlock2</tt>
+necessary files to allow you to import the block as a project in Eclipse.</p><h1>Connect two blocks</h1><p>Let's assume that you want to use a pipeline defined in <tt>myBlock2</tt>
 from within <tt>myBlock1</tt>. You have to establish the connection between the
 two blocks. Edit
-<tt>getting-started-app/<strong>myBlock1</strong>/src/main/resources/META-INF/cocoon/spring/block-servlet-service.xml:</tt>
-</p><pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
+<tt>getting-started-app/<b>myBlock1</b>/src/main/resources/META-INF/cocoon/spring/block-servlet-service.xml:</tt>
+</p><div><pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
 &lt;beans xmlns=&quot;http://www.springframework.org/schema/beans&quot;
   xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
   xmlns:servlet=&quot;http://cocoon.apache.org/schema/servlet&quot;
@@ -198,123 +206,127 @@ two blocks. Edit
 
   &lt;bean id=&quot;com.mycompany.myBlock1.service&quot; class=&quot;org.apache.cocoon.sitemap.SitemapServlet&quot;&gt;
     &lt;servlet:context mount-path=&quot;/myBlock1&quot; context-path=&quot;blockcontext:/myBlock1/&quot;&gt;
-<strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">      &lt;servlet:connections&gt;
+<b>      &lt;servlet:connections&gt;
         &lt;entry key=&quot;myBlock2&quot; value-ref=&quot;com.mycompany.myBlock2.service&quot;/&gt;
-      &lt;/servlet:connections&gt;</strong>
+      &lt;/servlet:connections&gt;</b>
     &lt;/servlet:context&gt;
   &lt;/bean&gt;
 
 &lt;/beans&gt;
-</pre><p>Additionally, you have to record the fact that myBlock1 has a dependency on
+</pre></div><p>Additionally, you have to record the fact that myBlock1 has a dependency on
 myBlock2 by editing myBlock1's Maven project descriptor
-(<tt>getting-started-app/<strong>myBlock1</strong>/pom.xml</tt>):</p><pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
+(<tt>getting-started-app/<b>myBlock1</b>/pom.xml</tt>):</p><div><pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
 &lt;project&gt;
   [...]
   &lt;dependencies&gt;
     [...]
-<strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">    &lt;dependency&gt;
+<b>    &lt;dependency&gt;
       &lt;groupId&gt;com.mycompany&lt;/groupId&gt;
       &lt;artifactId&gt;myBlock2&lt;/artifactId&gt;
       &lt;version&gt;1.0-SNAPSHOT&lt;/version&gt;
-    &lt;/dependency&gt;</strong>
+    &lt;/dependency&gt;</b>
   &lt;/dependencies&gt;
   [...]
 &lt;/project&gt;
-</pre><p>If you use the RCL goal of the Cocoon Maven plugin, you will also want to add
+</pre></div><p>If you use the RCL goal of the Cocoon Maven plugin, you will also want to add
 the location of the new block to the configuration file of block1. This has the
 advantage that you can work on block2 and the changes take effect immediately.
-Open getting-started-app/myBlock1/rcl.properties and add</p><pre>com.mycompany.myBlock1.service%classes-dir=./target/classes
+Open getting-started-app/myBlock1/rcl.properties and add</p><div><pre>com.mycompany.myBlock1.service%classes-dir=./target/classes
 
-<strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">com.mycompany.myBlock2.service%classes-dir=../myBlock2/target/classes
+<b>com.mycompany.myBlock2.service%classes-dir=../myBlock2/target/classes
 %exclude-lib=com.mycompany:myBlock2
-</strong></pre><p>Restart the servlet container by invoking</p><pre>mvn jetty:run 
-</pre><p>Now it's time to test connection. For that purpose add a pipeline to the
+</b></pre></div><p>Restart the servlet container by invoking</p><div><pre>mvn jetty:run 
+</pre></div><p>Now it's time to test connection. For that purpose add a pipeline to the
 sitemap of block1
 (<tt>getting-started-app/myBlock1/src/main/resources/COB-INF/sitemap.xmap</tt>):
-</p><pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
+</p><div><pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
 &lt;map:sitemap xmlns:map=&quot;http://apache.org/cocoon/sitemap/1.0&quot;&gt;
   &lt;map:pipelines&gt;
     [...]
     &lt;map:pipeline&gt;
       &lt;map:match pattern=&quot;callingBlock2&quot;&gt;
-        &lt;map:generate src=&quot;<strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">servlet:myBlock2:/spring-bean</strong>&quot; type=&quot;file&quot;/&gt;
+        &lt;map:generate src=&quot;<b>servlet:myBlock2:/spring-bean</b>&quot; type=&quot;file&quot;/&gt;
         &lt;map:serialize type=&quot;xml&quot;/&gt;
       &lt;/map:match&gt;
     &lt;/map:pipeline&gt;
     [...]
   &lt;/map:pipelines&gt;
 &lt;/map:sitemap&gt;
-</pre><p>The file generator of this pipeline uses a special purpose protocol, the
+</pre></div><p>The file generator of this pipeline uses a special purpose protocol, the
 servlet protocol, to access a pipeline defined in the other block. If you enter
 <tt>http://localhost:8888/myBlock1/callingBlock2</tt> shows the output of the
 spring-bean pipeline of <tt>myBlock2</tt> but routed through <tt>myBlock1</tt>.
-<br></br>
-Though this is a &quot;<em>hello word</em>&quot; style example you might already imagine
+<br />
+Though this is a &quot;<i>hello word</i>&quot; style example you might already imagine
 the power of this protocol, e.g. you can move all styling resources and
-pipelines to a particular block.</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Use a pipeline fragment</h1><p>The previous example showed how you can call a pipeline from another block.
+pipelines to a particular block.</p><h1>Use a pipeline fragment</h1><p>The previous example showed how you can call a pipeline from another block.
 But here is even more you can do! A sitemap can also provide pipeline fragements
-that can be used by other blocks:</p><pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
+that can be used by other blocks:</p><div><pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
 &lt;map:sitemap xmlns:map=&quot;http://apache.org/cocoon/sitemap/1.0&quot;&gt;
   &lt;map:pipelines&gt;
     &lt;map:pipeline&gt;
       &lt;map:match pattern=&quot;callingTransformationService&quot;&gt;
         &lt;map:generate src=&quot;demo/welcome.xml&quot;/&gt;
-        <strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">&lt;map:transform type=&quot;servletService&quot;&gt;
+        <b>&lt;map:transform type=&quot;servletService&quot;&gt;
           &lt;map:parameter name=&quot;service&quot; 
            value=&quot;servlet:myBlock2:/myXsltTransformation-service&quot;/&gt;
-        &lt;/map:transform&gt;</strong>
+        &lt;/map:transform&gt;</b>
         &lt;map:serialize type=&quot;xml&quot;/&gt;
       &lt;/map:match&gt;
     &lt;/map:pipeline&gt;
   &lt;/map:pipelines&gt;
-&lt;/map:sitemap&gt;</pre><p>When the requests arrives at <tt>callingTransformationService</tt> pipeline,
+&lt;/map:sitemap&gt;</pre></div><p>When the requests arrives at <tt>callingTransformationService</tt> pipeline,
 the generator produces SAX events of <tt>demo/welcome.xml</tt>. There is nothing
 special here. The interesting part comes with the following transformer of type
 <tt>servletService</tt>. It calls a transformation service which is provided by
 <tt>myBlock2</tt>.</p><p>Add this service to the sitemap of myBlock2
 (<tt>getting-started-app/myBlock2/src/main/resources/COB-INF/sitemap.xmap)</tt>.
-It consists of one XSLT transformation step:</p><pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
+It consists of one XSLT transformation step:</p><div><pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
 &lt;map:sitemap xmlns:map=&quot;http://apache.org/cocoon/sitemap/1.0&quot;&gt;
   &lt;map:pipelines&gt;
     &lt;map:pipeline&gt;
-      &lt;map:match pattern=&quot;<strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">myXsltTransformation-service</strong>&quot;&gt;
-        &lt;map:generate src=&quot;<strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">service-consumer:</strong>&quot;/&gt;
+      &lt;map:match pattern=&quot;<b>myXsltTransformation-service</b>&quot;&gt;
+        &lt;map:generate src=&quot;<b>service-consumer:</b>&quot;/&gt;
         &lt;map:transform src=&quot;myXsltTransformation.xslt&quot;/&gt;
         &lt;map:serialize type=&quot;xml&quot;/&gt;
       &lt;/map:match&gt;
     &lt;/map:pipeline&gt;
   &lt;/map:pipelines&gt;
-&lt;/map:sitemap&gt;</pre><p>The generator uses the service-consumer protocol which initializes the
+&lt;/map:sitemap&gt;</pre></div><p>The generator uses the service-consumer protocol which initializes the
 service. Then the pipeline continues with an XSLT transformation
 <tt>myXsltTransformation.xslt</tt>, which has to be put into the same directory
-as the <tt>myBlock2</tt> sitemap:</p><pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
+as the <tt>myBlock2</tt> sitemap:</p><div><pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
 &lt;xsl:stylesheet version=&quot;1.0&quot; xmlns:xsl=&quot;http://www.w3.org/1999/XSL/Transform&quot;&gt;
-  &lt;xsl:template match=&quot;/&quot;&gt;
-    &lt;html&gt;
-      &lt;head&gt;
-        &lt;title&gt;Output of the XSLT transformation service.&lt;/title&gt;
-      &lt;/head&gt;
-      &lt;body&gt;
-        Output of the XSLT transformation service.
-      &lt;/body&gt;
-    &lt;/html&gt;
-  &lt;/xsl:template&gt;
+&#xa0; &lt;xsl:template match=&quot;/&quot;&gt;
+&#xa0;&#xa0;&#xa0; &lt;html&gt;
+&#xa0;&#xa0;&#xa0;&#xa0;&#xa0; &lt;head&gt;
+&#xa0;&#xa0;&#xa0;&#xa0;&#xa0;&#xa0;&#xa0; &lt;title&gt;Output of the XSLT transformation service.&lt;/title&gt;
+&#xa0;&#xa0;&#xa0;&#xa0;&#xa0; &lt;/head&gt;
+&#xa0;&#xa0;&#xa0;&#xa0;&#xa0; &lt;body&gt;
+&#xa0;&#xa0;&#xa0;&#xa0;&#xa0;&#xa0;&#xa0; Output of the XSLT transformation service.
+&#xa0;&#xa0;&#xa0;&#xa0;&#xa0; &lt;/body&gt;
+&#xa0;&#xa0;&#xa0; &lt;/html&gt;
+&#xa0; &lt;/xsl:template&gt;
 &lt;/xsl:stylesheet&gt;
-</pre><p>Point your browser at
+</pre></div><p>Point your browser at
 <tt>http://localhost:8888/myBlock1/callingTransformationService</tt> and see the
-output of the pipeline.</p><div class="note"><div><strong>Note: </strong>Besides transformation services there are also generation and
-serialization services.</div></div></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/1291?branch=1&language=1">View, Edit or comment</a> on the latest development version (registration required).
-      </div></div></div>
+output of the pipeline.</p><div class="note"><div><b>Note: </b>Besides transformation services there are also generation and
+serialization services.</div></div></div></div>
+       
        </div>
     </div>
 
     <!-- end of content -->
     <div id="footer">
-      <p>&#169;  
-          1999-2008
+      <p>Copyright &copy;  
+          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">



Mime
View raw message