cocoon-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From asav...@apache.org
Subject svn commit: r573901 [17/44] - in /cocoon/site: site/ site/2.0/ site/2.0/developing/ site/2.0/faq/ site/2.0/howto/chaperon/ site/2.0/installing/ site/2.0/plan/ site/2.0/snippet/ site/2.0/tutorial/ site/2.0/userdocs/ site/2.0/userdocs/actions/ site/2.0/u...
Date Sat, 08 Sep 2007 20:17:47 GMT
Modified: cocoon/site/site/2.0/tutorial/tutorial-develop-webapp.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.0/tutorial/tutorial-develop-webapp.html?rev=573901&r1=573900&r2=573901&view=diff
==============================================================================
--- cocoon/site/site/2.0/tutorial/tutorial-develop-webapp.html (original)
+++ cocoon/site/site/2.0/tutorial/tutorial-develop-webapp.html Sat Sep  8 13:17:41 2007
@@ -1,1947 +1,1947 @@
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>How to develop Web Applications</title>
-<STYLE type="text/css">
-a.menu {
-	color: #FFFFFF;
-    text-align:left;               
-    font-size:12px;
-    font-family: Verdana, Arial, Helvetica, sans-serif;
-    font-weight:plain;
-    text-decoration:none;
-    padding-left: 14px
-}
-
-A.menu:hover {
-	color: #FFCC00
-}
-
-
-.menutitle {
-	color: #000000;
-    text-align:left;               
-    font-size:10px;
-    font-family: Verdana, Arial, Helvetica, sans-serif;
-    font-weight:bold;
-    padding-left: 8px
-}
-.menuselected {
-	color: #FFCC00;
-    text-align:left;               
-    font-size:12px;
-    font-family: Verdana, Arial, Helvetica, sans-serif;
-    font-weight:bold;
-    padding-left: 14px
-}
-</STYLE>
-</head>
-<body bgcolor="#ffffff" marginheight="4" marginwidth="4" leftmargin="4" topmargin="4" alink="#cc0000" vlink="#0086b2" link="#039acc" text="#000000">
-<table border="0" cellpadding="0" cellspacing="0" width="100%">
-<tr>
-<td align="left" valign="top" rowspan="3" height="60" width="135"><img border="0" vspace="0" hspace="0" src="images/logo.gif" height="60" width="135"></td><td background="images/line.gif" rowspan="1" colSpan="2" align="left" valign="top" height="0" width="100%"></td><td align="left" valign="top" rowspan="3" height="60" width="29"><img border="0" vspace="0" hspace="0" src="images/right.gif" height="60" width="29"></td>
-</tr>
-<tr>
-<td bgcolor="#0086b2" colspan="2" align="right" valign="top" height="35" width="100%"><font color="#ffffff" face="Verdana, Arial, Helvetica, sans-serif" size="5">How to develop Web Applications</font></td>
-</tr>
-<tr>
-<td background="images/bottom.gif" colspan="2" width="100%" valign="top" height="20" bgcolor="#0086b2" align="right">
-<table width="288" cellspacing="0" cellpadding="0" border="0">
-<tr>
-<td align="left" valign="top" height="20" width="96"><a target="new" href="http://xml.apache.org/"><img border="0" vspace="0" hspace="0" name="xml" src="images/button-xml-lo.gif" height="20" width="96" alt="http://xml.apache.org/"></a></td><td align="left" valign="top" height="20" width="96"><a target="new" href="http://www.apache.org/"><img border="0" vspace="0" hspace="0" name="asf" src="images/button-asf-lo.gif" height="20" width="96" alt="http://www.apache.org/"></a></td><td align="left" valign="top" height="20" width="96"><a target="new" href="http://www.w3.org/"><img border="0" vspace="0" hspace="0" name="w3c" src="images/button-w3c-lo.gif" height="20" width="96" alt="http://www.w3.org/"></a></td>
-</tr>
-</table>
-</td>
-</tr>
-</table>
-<table width="100%" cellspacing="0" cellpadding="0" border="0">
-<tr width="100%">
-<td align="left" valign="top" width="120">
-<table width="120" cellspacing="0" cellpadding="0" border="0" bgcolor="#a0a0a0">
-<tr>
-<td valign="top" align="left"><img width="120" vspace="0" src="images/join.gif" hspace="0" height="14" border="0"><br>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#959595" background="images/label-background_a.gif"><a class="menu" href="../index.html">Main</a></td>
-</tr>
-<tr>
-<td background="images/label-background_b.gif" bgcolor="#959595" valign="top"><img width="120" height="6" src="images/separator.gif"><br>
-<span class="menutitle">Tutorials</span></td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#959595" background="images/label-background_a.gif"><a class="menu" href="index.html">Index</a></td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#959595" background="images/label-background_a.gif"><span class="menuselected">WebApp</span></td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#959595" background="images/label-background_a.gif"><a class="menu" href="tutorial-generator.html">Custom Generator</a></td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#959595" background="images/label-background_a.gif"><a class="menu" href="tutorial-rmi-generator.html">RMIServer</a></td>
-</tr>
-<tr>
-<td align="left" valign="top"><img width="120" vspace="0" src="images/close.gif" hspace="0" height="14" border="0"><br>
-</td>
-</tr>
-</table>
-</td><td>
-<table cellspacing="15" cellpadding="0" border="0">
-<tr>
-<td>
- 
-
- 
-
- <font face="verdana, helvetica, sans serif" size="+2" color="#0086b2">Introduction</font>
-<hr style="color: #0086b2" size="1">
-  
-<p>
-<font color="black" face="verdana,helvetica,sanserif">Apache Cocoon is an XML publishing framework. It allows you to define XML
-     documents and transformations to be applied on it, to eventually
-     generate a presentation format of your choice (HTML, PDF, SVG, etc.).
-     Cocoon also gives you the possibility to have logic in your XML files
-     (so that the XML file itself can become dynamically generated).</font>
-</p>
-  
-<p>
-<font color="black" face="verdana,helvetica,sanserif">Cocoon is developed on top of the Avalon Server Framework, which is a
-     stable and scalable framework.  You can find out more about Avalon in
-     this document: (ref: Avalon White Paper).  I highly suggest reading
-     this white paper as it covers many concepts that are key to Cocoon,
-     namely Separation of Concerns (SOC) and Inversion of Control (IoC).
-     It also covers foundational aspects of the Avalon Framework, so you
-     can have a better understanding on how Cocoon is structured.</font>
-</p>
-  
-<p>
-<font color="black" face="verdana,helvetica,sanserif">Cocoon helps you separate out concern areas for web development.
-     The areas addressed are Logic, Content, Style, and Management.  There
-     are different mechanisms for each.</font>
-</p>
-  
-<p>
-<font color="black" face="verdana,helvetica,sanserif">In order to learn how to use Cocoon, first make sure that you
-     <a href="../installing/index.html">install</a> it properly, then investigate
-     the many <a href="../overview.html#samples">samples</a>.
-     The following screenshots come from the
-     "<code><font face="courier, monospaced">tutorial</font></code>" that is provided with Cocoon.
-     After you have built the demo webapp as per the installation
-     instructions (<code><font face="courier, monospaced">build webapp</font></code>) then you can see this tutorial
-     in action via the Samples pages.</font>
-</p>
-
-  
-<font face="verdana, helvetica, sans serif" size="+1" color="#0086b2"><b>Separating Concerns</b></font>
-    
-<p>
-<font color="black" face="verdana,helvetica,sanserif">Cocoon is designed to allow Developers, Business Analysts,
-       Designers, and Administrators to work with each other without breaking
-       the other person's contribution.  The problem with using just JSPs, ASPs,
-       or ColdFusion templates is that all of the look, feel, and logic are
-       intertwined.  That means that maintenance is much more difficult, and the
-       project's true costs are delayed until the customer wants feature
-       enhancements or bugs fixed.  This also means that if the site design is
-       introduced late in the game, the cost of revamping the site becomes much
-       higher.</font>
-</p>
-    
-<font face="verdana, helvetica, sans serif" size="+1" color="#0086b2">Developers</font>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">Developer's jobs are to create the business logic and object model
-         behind the web application.  They are more concerned with functionality
-         than with layout or the words displayed on a screen.  These are the
-         people that will develop the Actions (Components that only process
-         information) and the hooks for how to get the necessary information
-         from business objects.</font>
-</p>
-    
-    
-<font face="verdana, helvetica, sans serif" size="+1" color="#0086b2">Business Analysts</font>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">The Business Analysts are the people who are concerned with the words
-         displayed on the screen, and to a certain extent, the layout.
-         Typically, they will be using the work done by the developer to put
-         together a generic markup that will be transformed into the results.
-         In small development environments, many times the developer takes on
-         both this role and the developer role.  Typically, the business analyst
-         will be working with the markup language that goes into the 
-         generator.</font>
-</p>
-    
-    
-<font face="verdana, helvetica, sans serif" size="+1" color="#0086b2">Designers</font>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">The designer is the person or group of people who are responsible to
-         provide the final look and feel of a site.  The designer does all the
-         graphics and HTML code.  In Cocoon, they will be working with the
-         Transformers that take an input and structure it in a final
-         presentation.</font>
-</p>
-    
-    
-<font face="verdana, helvetica, sans serif" size="+1" color="#0086b2">Administrators</font>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">The administrator is responsible for the sitemap which maps the URI
-         space to the different pipelines in Cocoon.  A pipeline is a path from
-         a Generator to a Serializer.  This means, that the administrator
-         decides that all requests for a resource with a ".html"
-         extension starts out as XML and ends up as HTML.  The Administrator
-         will work closely with the Designers and the Developers.  In the
-         absence of a dedicated administrator, one developer should assume that
-         role.  It is important that developers do not get bogged down in this
-         one Component.</font>
-</p>
-    
-  
-  
-<font face="verdana, helvetica, sans serif" size="+1" color="#0086b2"><b>Development Style</b></font>
-    
-<p>
-<font color="black" face="verdana,helvetica,sanserif">You have to decide early on whether you will develop from a Business
-       Markup perspective, or develop from a Document Markup perspective.  They
-       have different ways of approaching the same problem.  Both approaches
-       have its tradeoffs.  In the end, you will find that you will need a
-       combination of different aspects of the two approaches.</font>
-</p>
-    
-<font face="verdana, helvetica, sans serif" size="+1" color="#0086b2">Business Markup Centric</font>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">This approach makes the Business Object the center of attention for
-         development.  This approach formalizes your business objects, and makes
-         sure that you always represent a business object in a standard manner. 
-         It's limitations come to bear when you have cases when you need
-         two different objects that need to be represented on the same logical
-         page.</font>
-</p>
-    
-    
-<font face="verdana, helvetica, sans serif" size="+1" color="#0086b2">Document Markup Centric</font>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">This approach feels the most natural to developers who come from
-         backgrounds with scripting languages.  This approach is a bit more
-         flexible in that you represent a page logically, with the wording as
-         the center of attention.  With this approach, it is up to the developer
-         to ensure that the business object is represented in a consistent
-         manner.</font>
-</p>
-    
-    
-<font face="verdana, helvetica, sans serif" size="+1" color="#0086b2">Hybrid Approach</font>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">We will develop a hybrid approach to development in this paper.  What
-         this means is that we start with a Document Markup Centric approach,
-         and add in support for specific Business Markup as it is needed.  In
-         the end, this is the most flexible and maintainable method for
-         development.</font>
-</p>
-    
-  
-  
-<font face="verdana, helvetica, sans serif" size="+1" color="#0086b2"><b>The Concept</b></font>
-    
-<p>
-<font color="black" face="verdana,helvetica,sanserif">For the sake of this paper, we are going to develop a very simple
-       database-backed application that manages users and departments.  Each
-       element has a name and an identifier.  A department can have many
-       employees, but each employee can only have one department.  We will be
-       able to create, change, and delete both employees and departments.</font>
-</p>
-    
-<font face="verdana, helvetica, sans serif" size="+1" color="#0086b2">The SQL</font>
-
-<div align="center">
-<table border="0" cellpadding="0" cellspacing="4">
-<tr>
-<td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-<tr>
-<td width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td bgcolor="#ffffff">
-<pre>CREATE TABLE department {
-    department_id INT NOT NULL,
-    department_name VARCHAR (64) NOT NULL
-};
-
-CREATE TABLE employee {
-    employee_id INT NOT NULL,
-    employee_name VARCHAR (64) NOT NULL,
-    department_id INT NOT NULL
-};
-
-ALTER TABLE department ADD
-    PRIMARY KEY pkDepartment (department_id);
-
-ALTER TABLE employee ADD
-    PRIMARY KEY pkEmployee (employee_id);
-
-ALTER TABLE employee ADD
-    FOREIGN KEY department_id (department.department_id);</pre>
-</td><td width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-<tr>
-<td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-</table>
-</div>
-    
-    
-<font face="verdana, helvetica, sans serif" size="+1" color="#0086b2">Facilities</font>
-      
-<blockquote>
-<ol>
-        
-<li>
-<font face="verdana, helvetica, sans serif">Create Department (need name only)</font>
-</li>
-        
-<li>
-<font face="verdana, helvetica, sans serif">Update Department (change name, reassign potential employees to
-          department, create employee for department)</font>
-</li>
-        
-<li>
-<font face="verdana, helvetica, sans serif">Delete Department</font>
-</li>
-        
-<li>
-<font face="verdana, helvetica, sans serif">Find Department (by name, or by ID)</font>
-</li>
-        
-<li>
-<font face="verdana, helvetica, sans serif">Create Employee (need name and department-create department if
-          needed)</font>
-</li>
-        
-<li>
-<font face="verdana, helvetica, sans serif">Update Employee (change name, reassign department-create
-          department if needed)</font>
-</li>
-        
-<li>
-<font face="verdana, helvetica, sans serif">Delete Employee</font>
-</li>
-        
-<li>
-<font face="verdana, helvetica, sans serif">Find Employees (by name, by ID, or by Department)</font>
-</li>
-      
-</ol>
-</blockquote>
-    
-    
-<font face="verdana, helvetica, sans serif" size="+1" color="#0086b2">Layouts</font>
-     
-<p>
-<font color="black" face="verdana,helvetica,sanserif"><a href="tutorial-shots.html">Various screenshots</a>
-      are available as a separate document, to portray the layout of
-      interfaces and results pages - apply your own style.</font>
-</p>
-    
-  
- 
- 
-<font face="verdana, helvetica, sans serif" size="+2" color="#0086b2">Diving In</font>
-<hr style="color: #0086b2" size="1">
-  
-<p>
-<font color="black" face="verdana,helvetica,sanserif">In order to do anything in Cocoon, you will need a sitemap.  At this point
-     we will not go into detail but we will show you how to put an entry in so
-     you can see your stuff.  In most development situations, the sitemap will
-     be set up for you.  Since we want to start with a clean slate, take the
-     sitemap that comes with Cocoon's 
-     <a href="../overview.html#samples">samples</a>
-     and clear out everything under
-     the <code><font face="courier, monospaced">&lt;map:pipelines&gt;</font></code> tag.  Next, you will add an entry
-     in the same location that looks like this:</font>
-</p>
-
-<div align="center">
-<table border="0" cellpadding="0" cellspacing="4">
-<tr>
-<td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-<tr>
-<td width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td bgcolor="#ffffff">
-<pre>
-  
-&lt;map:pipeline&gt;
-   &lt;map:match pattern=""&gt;
-     &lt;map:redirect-to uri="home.html"/&gt;
-   &lt;/map:match&gt;
-
-   &lt;map:match pattern="**.xml"&gt;
-     &lt;map:generate src="docs/{1}.xml"/&gt;
-     &lt;map:serialize type="xml"/&gt;
-   &lt;/map:match&gt;
-
-   &lt;map:match pattern="**.html"&gt;
-     &lt;map:generate src="docs/{1}.xml"/&gt;
-     &lt;map:transform src="stylesheets/apache.xsl"/&gt;
-     &lt;map:serialize/&gt;
-   &lt;/map:match&gt;
-
-   &lt;map:match pattern="images/**.gif"&gt;
-    &lt;map:read src="resources/images/{1}.gif" mime-type="image/gif"/&gt;
-   &lt;/map:match&gt;
-
-   &lt;map:match pattern="images/**.jpg"&gt;
-    &lt;map:read src="resources/images/{1}.jpg" mime-type="image/jpg"/&gt;
-   &lt;/map:match&gt;
-
-   &lt;map:match pattern="images/**.png"&gt;
-    &lt;map:read src="resources/images/{1}.png" mime-type="image/png"/&gt;
-   &lt;/map:match&gt;
-
-   &lt;map:match pattern="resources/**.css"&gt;
-     &lt;map:read src="resources/styles/{1}.css" mime-type="text/css"/&gt;
-   &lt;/map:match&gt;
-
-   &lt;map:match pattern="resources/**.js"&gt;
-     &lt;map:read src="resource/styles/{1}.js"
-               mime-type="application/x-javascript"/&gt;
-   &lt;/map:match&gt;
-
-  &lt;map:handle-errors&gt;
-    &lt;map:transform src="stylesheets/system/error2html.xsl"/&gt;
-    &lt;map:serialize status-code="500"/&gt;
-  &lt;/map:handle-errors&gt;
-&lt;/map:pipeline&gt;
-  
-</pre>
-</td><td width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-<tr>
-<td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-</table>
-</div>
-    
-<p>
-<font color="black" face="verdana,helvetica,sanserif">What this does is tell the sitemap that we want to capture all URLs
-       with a ".xml" extension, and find an equivalent file in the
-       "docs" subdirectory.  We are not performing any transformations
-       at this time.  The Sitemap is really a site administrator's job to
-       maintain.  There are some exceptions to this general rule, but we will
-       discuss them when needed.  We will use the Document Markup specified in
-       the StyleBook DTD format.</font>
-</p>
-   
-<font face="verdana, helvetica, sans serif" size="+1" color="#0086b2"><b>Creating the Pages</b></font>
-    
-<p>
-<font color="black" face="verdana,helvetica,sanserif">Since we are only looking at XML right now, we need to make sure our
-       pages conform to the markup standards.  You will see how well this comes
-       in handy for debugging XSP (XML Server Pages) markup.  Since we already
-       have the Layout specified, and the database created, we will create our
-       markup.</font>
-</p>
-    
-<p>
-<font color="black" face="verdana,helvetica,sanserif">Our home page is going to be really simple: a list of links that take us
-       to the main pages.</font>
-</p>
-
-<div align="center">
-<table border="0" cellpadding="0" cellspacing="4">
-<tr>
-<td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-<tr>
-<td width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td bgcolor="#ffffff">
-<pre>
-  
-&lt;document&gt;
-  &lt;header&gt;
-    &lt;title&gt;Home Page&lt;/title&gt;
-  &lt;/header&gt;
-  &lt;body&gt;
-    &lt;s1 title="Welcome to Personnel Administrator"&gt;
-      &lt;p&gt;
-        Welcome to our Personnel Administrator.  You
-        can perform one of the following functions:
-      &lt;/p&gt;
-      &lt;ul&gt;
-        &lt;li&gt;
-          &lt;link href="search-dept.html"&gt;Search Departments&lt;/link&gt;
-        &lt;/li&gt;
-        &lt;li&gt;
-          &lt;link href="search-empl.html"&gt;Search Employees&lt;/link&gt;
-        &lt;/li&gt;
-        &lt;li&gt;
-          &lt;link href="create-dept.html"&gt;Create Departments&lt;/link&gt;
-        &lt;/li&gt;
-        &lt;li&gt;
-          &lt;link href="edit-dept.html"&gt;Edit a Department&lt;/link&gt;
-        &lt;/li&gt;
-        &lt;li&gt;
-          &lt;link href="create-empl.html"&gt;Create Employee&lt;/link&gt;
-        &lt;/li&gt;
-        &lt;li&gt;
-          &lt;link href="edit-empl.html"&gt;Edit an Employee&lt;/link&gt;
-        &lt;/li&gt;
-      &lt;/ul&gt;
-    &lt;/s1&gt;
-  &lt;/body&gt;
-&lt;/document&gt;
-  
-</pre>
-</td><td width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-<tr>
-<td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-</table>
-</div>
-     
-<p>
-<font color="black" face="verdana,helvetica,sanserif">Even though this doesn't look like much right now, we have two
-        entries: "**.xml" and "**.html" for the same
-        resource.  Look at "home.html", and see how it looks now.
-        Quite a difference.  Don't remove the entry for viewing the page
-        as XML yet.  We need to use it to debug our XSP pages later.</font>
-</p>
-     
-<font face="verdana, helvetica, sans serif" size="+1" color="#0086b2">Our First Form</font>
-       
-<p>
-<font color="black" face="verdana,helvetica,sanserif">For now, we are going to skip the search functionality, and jump to
-          our "create" templates.  It is important to realize the
-          proper method of form handling.  While it is possible to create XSP
-          pages that perform the logic for you, this approach is not very
-          maintainable.  We also have to choose whether we will directly access
-          the database, or encapsulate that logic in objects.</font>
-</p>
-       
-<p>
-<font color="black" face="verdana,helvetica,sanserif">The tradeoffs are that the direct SQL access is faster to get started,
-          but that it is harder to maintain in the end.  You may decide to start
-          with the direct SQL access at the beginning of a project, and build
-          the objects later.  With that in mind, we will use some functionality
-          that Cocoon has built in to make this approach a little easier.
-          Cocoon has a group of Database actions that allow you to map form
-          fields to dynamically created SQL calls.  It also has a logicsheet
-          that makes creating SQL bound pages a little easier.</font>
-</p>
-       
-<p>
-<font color="black" face="verdana,helvetica,sanserif">Our first form is the "Create a Department" form.  The
-          website specification is missing the tags for form building, we will
-          provide an example here:</font>
-</p>
-
-<div align="center">
-<table border="0" cellpadding="0" cellspacing="4">
-<tr>
-<td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-<tr>
-<td width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td bgcolor="#ffffff">
-<pre>
-  
-&lt;document&gt;
-  &lt;header&gt;
-    &lt;title&gt;Department&lt;/title&gt;
-  &lt;/header&gt;
-  &lt;body&gt;
-    &lt;s1 title="Create a Department"&gt;
-      &lt;form handler="create-dept.html"&gt;
-        &lt;p&gt;
-          You can create a department by typing in the
-          name and pressing the "submit" button.
-        &lt;/p&gt;
-        &lt;p&gt;
-          Name: &lt;text name="name" size="30" required="true"/&gt;
-        &lt;/p&gt;
-        &lt;submit name="Create Department"/&gt;
-        &lt;note&gt;
-          * These fields are required.
-        &lt;/note&gt;
-      &lt;/form&gt;
-    &lt;/s1&gt;
-  &lt;/body&gt;
-&lt;/document&gt; 
-  
-</pre>
-</td><td width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-<tr>
-<td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-</table>
-</div>
-       
-<p>
-<font color="black" face="verdana,helvetica,sanserif">It is important to note that the "submit" tag is transformed
-          into an HTML submit button with the name "cocoon-action-ACTIONNAME".
-          The "cocoon-action-ACTIONNAME" form parameter is a magic value that
-          Cocoon uses to select a specific action from a group of actions that
-          only gets executed during that time.  You will find that this page
-          displays correctly, but does not do anything yet.  The handler is
-          where the navigation goes once you click on the
-          "Create Department" button on the screen.  What we are going
-          to do is create one confirmation page for all the Department and
-          Employee pages.</font>
-</p>
-       
-<p>
-<font color="black" face="verdana,helvetica,sanserif">Cocoon has a FormValidatorAction that will take care of ensuring the
-          input results are acceptable.  It also has the following database
-          actions for your convenience: DatabaseAddAction, DatabaseUpdateAction,
-          DatabaseDeleteAction, and DatabaseAuthenticatorAction.  We will only
-          need the Add, Update, and Delete actions for our simple webapp.  In
-          order to prepare them, we create an XML configuration file that tells
-          the actions how to map request parameters to database tables and place
-          constraints on the parameters.  For the Department form group, it will
-          look like this:</font>
-</p>
-
-<div align="center">
-<table border="0" cellpadding="0" cellspacing="4">
-<tr>
-<td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-<tr>
-<td width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td bgcolor="#ffffff">
-<pre>
-  
-&lt;root&gt;
-  &lt;!-
-      The "parameter" elements identify the root constraints for
-      the FormValidatorAction.  We are specifying that the "id"
-      parameter is an integer (it limits to "long", "double",
-      "boolean", and "string").  We are specifying that the "name"
-      parameter is a string that is at least 5 characters--but no
-      more than 64 characters.
-  --&gt;
-  &lt;parameter name="id" type="long"/&gt;
-  &lt;parameter name="name" type="string" min-len="5" max-len="64"/&gt;
-
-  &lt;!-
-      Each constraint set is used when we are defining a new way
-      of validating a form.  We define our constraint sets by
-      function.  Since we have the same basic form that is driving
-      the FormValidator, we have an update set and an add set.
-
-      Note that you can impose additional constraints than the
-      default constraints listed above.  Also, you do not "have"
-      to enforce a constraint.  Each "validate" element below
-      identifies the parameter constraints we are enforcing.
-
-      For more information view the JavaDocs for 
-      AbstractValidatorAction
-  --&gt;
-  &lt;constraint-set name="update"&gt;
-    &lt;validate name="name"/&gt;
-    &lt;validate name="id" nullable="no" min="1"/&gt;
-  &lt;/constraint-set&gt;
-
-  &lt;constraint-set name="add"&gt;
-    &lt;validate name="name"/&gt;
-  &lt;/constraint-set&gt;
-
-  &lt;!--
-       This is where we identify our table mappings so that the
-       Database Actions can work their magic.  Note that the
-       parameter names are the same as above--as well as the same
-       as form parameter names.
-
-       First we tell the Database Actions that we are using the
-       "personnel" connection pool we set up in &lt;code&gt;cocoon.xconf&lt;/code&gt;.
-       This file should be set up by the site administrator.
-
-       We also tell the Database Actions the structure of the table
-       we will be populating.  The keys are used to identify which
-       columns will be treated as keys--they are treated different
-       when the different SQL statements are created.  Note that
-       there is a "mode" attribute in the key element.  The mode
-       refers to how new keys will be generated.  There are three
-       modes: "automatic" keys are generated by the database,
-       "manual" keys are generated by manually finding the largest
-       value and incrementing it, and finally "form" keys take the
-       key value from a parameter on the form.
-
-       Both keys and values serve to map parameter names to table
-       columns, converting the value into the native type.  For a
-       list of supported types check out the JavaDocs for
-       AbstractDatabaseAction.
-  --&gt;
-  &lt;connection&gt;personnel&lt;/connection&gt;
-  &lt;table name="department"&gt;
-    &lt;keys&gt;
-      &lt;key param="id" dbcol="department_id" type="int" mode="manual"/&gt;
-    &lt;/keys&gt;
-    &lt;values&gt;
-      &lt;value param="name" dbcol="department_name" type="string"/&gt;
-    &lt;/values&gt;
-  &lt;/table&gt;
-&lt;/root&gt;
-  
-</pre>
-</td><td width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-<tr>
-<td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-</table>
-</div>
-       
-<p>
-<font color="black" face="verdana,helvetica,sanserif">After you create the descriptor file, you will have to create some
-          entries in the Sitemap so you can take advantage of the form
-          descriptor.  First, the Sitemap has to be able to know how to
-          reference the Actions we want.  To do that, alter the
-          "map:actions" section to list all the actions we need:</font>
-</p>
-
-<div align="center">
-<table border="0" cellpadding="0" cellspacing="4">
-<tr>
-<td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-<tr>
-<td width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td bgcolor="#ffffff">
-<pre>
-  
-&lt;map:actions&gt;
-   &lt;map:action name="dbAdd"
-               src="org.apache.cocoon.acting.DatabaseAddAction"/&gt;
-   &lt;map:action name="dbDel"
-               src="org.apache.cocoon.acting.DatabaseDeleteAction"/&gt;
-   &lt;map:action name="dbUpd"
-               src="org.apache.cocoon.acting.DatabaseUpdateAction"/&gt;
-   &lt;map:action name="form"
-               src="org.apache.cocoon.acting.FormValidatorAction"/&gt;
-&lt;/map:actions&gt;
-  
-</pre>
-</td><td width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-<tr>
-<td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-</table>
-</div>
-       
-<p>
-<font color="black" face="verdana,helvetica,sanserif">Lastly, we want to create an action set.  An action set is a group of
-          actions that will be applied at once.  If the action set entry has an
-          "action" parameter, then the specific action is only
-          executed when the ACTIONNAME of the magic "cocoon-action-ACTIONNAME"
-          request parameter matches the value of the "action" parameter.  For our
-          purposes, the action set we are defining is listed below (defined in
-          the sitemap):</font>
-</p>
-
-<div align="center">
-<table border="0" cellpadding="0" cellspacing="4">
-<tr>
-<td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-<tr>
-<td width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td bgcolor="#ffffff">
-<pre>
-  
-&lt;map:action-sets&gt;
-  &lt;map:action-set name="process"&gt;
-   &lt;map:act type="form" action="Create Department"&gt;
-     &lt;map:parameter name="validate-set" value="add"/&gt;
-     &lt;map:act type="dbAdd"/&gt;
-   &lt;/map:act&gt;
-   &lt;map:act type="form" action="Update Department"&gt;
-     &lt;map:parameter name="validate-set" value="update"/&gt;
-     &lt;map:act type="dbUpd"/&gt;
-   &lt;/map:act&gt;
-   &lt;map:act type="dbDel" action="Delete Department"/&gt;
-  &lt;/map:action-set&gt;
-&lt;/map:action-sets&gt;
-  
-</pre>
-</td><td width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-<tr>
-<td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-</table>
-</div>
-       
-<p>
-<font color="black" face="verdana,helvetica,sanserif">Now that we have defined the actions we want, with the parameters that
-          control them during run-time, we can use it in our pipeline.</font>
-</p>
-
-<div align="center">
-<table border="0" cellpadding="0" cellspacing="4">
-<tr>
-<td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-<tr>
-<td width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td bgcolor="#ffffff">
-<pre>
-  
-&lt;map:match pattern="*-dept.html"&gt;
-  &lt;map:act set="process"&gt;
-    &lt;map:parameter name="descriptor"
-                   value="context://docs/department-form.xml"/&gt;
-    &lt;map:parameter name="form-descriptor"
-                   value="context://docs/department-form.xml"/&gt;
-    &lt;map:generate type="serverpages" src="docs/confirm-dept.xsp"/&gt;
-    &lt;map:transform src="stylesheets/apache.xsl"/&gt;
-    &lt;map:serialize/&gt;
-  &lt;/map:act&gt;
-  &lt;map:generate type="serverpages" src="docs/{1}-dept.xsp"/&gt;
-  &lt;map:transform src="stylesheets/apache.xsl"/&gt;
-  &lt;map:serialize/&gt;
-&lt;/map:match&gt;
-
-&lt;map:match pattern="*-dept.xml"&gt;
-  &lt;map:act set="process"&gt;
-    &lt;map:parameter name="descriptor"
-                   value="context://docs/department-form.xml"/&gt;
-    &lt;map:parameter name="form-descriptor"
-                   value="context://docs/department-form.xml"/&gt;
-    &lt;map:generate type="serverpages" src="docs/confirm-dept.xsp"/&gt;
-    &lt;map:serialize type="xml"/&gt;
-  &lt;/map:act&gt;
-  &lt;map:generate type="serverpages" src="docs/{1}-dept.xsp"/&gt;
-  &lt;map:serialize type="xml"/&gt;
-&lt;/map:match&gt;
-  
-</pre>
-</td><td width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-<tr>
-<td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-</table>
-</div>
-       
-<p>
-<font color="black" face="verdana,helvetica,sanserif">This may not seem clear what is happening right now.  The way actions
-          work is if they return a null, nothing inside the "map:act"
-          entry will execute, and the request processing will flow through to
-          the second "map:generate" section.  This is a side affect of
-          using the FormValidatorAction.  If we choose to create our own
-          business objects and form validation framework, we are not constrained by
-          this construct.</font>
-</p>
-       
-<p>
-<font color="black" face="verdana,helvetica,sanserif">In addition, we changed the type of generator we are using: we have
-          made it a "serverpages" (or XSP) generator.  We made the
-          transition now so that we can report information on what failed to the
-          user.  First, we need to convert our "create-dept.xml" file
-          to an XSP page so that we can see the page again (right now we will
-          get an error).  To do this, simply add a new tag to the base of the
-          document called "xsp:page" declaring the XSP namespace.  The
-          change will look like this:</font>
-</p>
-
-<div align="center">
-<table border="0" cellpadding="0" cellspacing="4">
-<tr>
-<td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-<tr>
-<td width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td bgcolor="#ffffff">
-<pre>
-  
-&lt;xsp:page xmlns:xsp="http://apache.org/xsp"&gt;
-  &lt;!-- The original document will be embedded here --&gt;
-&lt;/xsp:page&gt;
-  
-</pre>
-</td><td width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-<tr>
-<td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-</table>
-</div>
-       
-<p>
-<font color="black" face="verdana,helvetica,sanserif">To complete the transformation, we usually change the extension to
-          ".xsp" so we know what we are dealing with at a glance.
-          Create a new file called "confirm.xsp" with the following
-          contents:</font>
-</p>
-
-<div align="center">
-<table border="0" cellpadding="0" cellspacing="4">
-<tr>
-<td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-<tr>
-<td width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td bgcolor="#ffffff">
-<pre>
-  
-&lt;xsp:page xmlns:xsp="http://apache.org/xsp"&gt;
-&lt;document&gt;
-  &lt;header&gt;
-    &lt;title&gt;Department&lt;/title&gt;
-  &lt;/header&gt;
-  &lt;body&gt;
-    &lt;s1 title="Department Processed"&gt;
-      &lt;p&gt;
-        You have successfully processed the department.
-      &lt;/p&gt;
-    &lt;/s1&gt;
-  &lt;/body&gt;
-&lt;/document&gt;
-&lt;/xsp:page&gt;
-  
-</pre>
-</td><td width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-<tr>
-<td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-</table>
-</div>          
-      
-<font face="verdana, helvetica, sans serif" color="#0086b2"><b>Adding support for Error Reporting</b></font>
-        
-<p>
-<font color="black" face="verdana,helvetica,sanserif">In order to successfully report errors processing the page, add
-           another namespace declaration to the "xsp:page" element.
-           The final form page will look like this:</font>
-</p>
-
-<div align="center">
-<table border="0" cellpadding="0" cellspacing="4">
-<tr>
-<td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-<tr>
-<td width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td bgcolor="#ffffff">
-<pre>
-  
-&lt;xsp:page xmlns:xsp="http://apache.org/xsp"
-          xmlns:xsp-formval="http://apache.org/xsp/form-validator/2.0"&gt;
-&lt;document&gt;
-  &lt;header&gt;
-    &lt;title&gt;Department&lt;/title&gt;
-  &lt;/header&gt;
-  &lt;body&gt;
-    &lt;s1 title="Create a Department"&gt;
-      &lt;form handler="create-dept.html"&gt;
-        &lt;p&gt;
-          You can create a department by typing in the
-          name and pressing the "submit" button.
-        &lt;/p&gt;
-        &lt;p&gt;
-          Name: &lt;text name="name" size="30" required="true"/&gt;&lt;br /&gt;
-	       &lt;xsp:logic&gt;
-	         if (&lt;xsp-formval:is-toosmall name="name"/&gt;) {
-	             &lt;xsp:text&gt;"Name" must be at least 5 characters&lt;/xsp:text&gt;
-	         } else if (&lt;xsp-formval:is-toolarge name="name"/&gt;) {
-	             &lt;xsp:text&gt;"Name" was too long&lt;/xsp:text&gt;
-	         }
-	       &lt;/xsp:logic&gt;
-        &lt;/p&gt;
-        &lt;submit name="Create Department"/&gt;
-        &lt;note&gt;
-          * These fields are required.
-        &lt;/note&gt;
-      &lt;/form&gt;
-    &lt;/s1&gt;
-  &lt;/body&gt;
-&lt;/document&gt;
-&lt;/xsp:page&gt;
-  
-</pre>
-</td><td width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-<tr>
-<td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-</table>
-</div>           
-      
-     
-     
-<font face="verdana, helvetica, sans serif" size="+1" color="#0086b2">Adding Database Support with the ESQL Logicsheet</font>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">The "Create Employee" page is going to require database
-         access so that we know which Department a new employee is assigned to.
-         This is fairly easy to accomplish with the ESQL Logicsheet.  Again,
-         when you use the ESQL logicsheet, you lose some of your separation of
-         concerns.</font>
-</p>
-
-<div align="center">
-<table border="0" cellpadding="0" cellspacing="4">
-<tr>
-<td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-<tr>
-<td width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td bgcolor="#ffffff">
-<pre>
-  
-&lt;xsp:page xmlns:xsp="http://apache.org/xsp"
-          xmlns:xsp-formval="http://apache.org/xsp/form-validator/2.0"
-          xmlns:esql="http://apache.org/cocoon/SQL/v2"&gt;
-&lt;document&gt;
-  &lt;header&gt;
-    &lt;title&gt;Employee&lt;/title&gt;
-  &lt;/header&gt;
-  &lt;body&gt;
-    &lt;s1 title="Create an Employee"&gt;
-      &lt;form handler="create-empl.html"&gt;
-        &lt;p&gt;
-          You can create a department by typing in the
-          name and pressing the "submit" button.
-        &lt;/p&gt;
-        &lt;p&gt;
-          Name: &lt;text name="name" size="30" required="true"/&gt;&lt;br /&gt;
-	       &lt;xsp:logic&gt;
-	         if (&lt;xsp-formval:is-null name="name"/&gt;) {
-	             &lt;xsp:text&gt;"Name" cannot be empty&lt;/xsp:text&gt;
-	         } else if (&lt;xsp-formval:is-toolarge name="name"/&gt;) {
-	             &lt;xsp:text&gt;"Name" was too long&lt;/xsp:text&gt;
-	         }
-	       &lt;/xsp:logic&gt;
-        &lt;/p&gt;
-        &lt;p&gt;
-          Department:
-          &lt;select name="department"&gt;
-            &lt;esql:connection&gt;
-
-              &lt;!-- declare the connection pool we are using --&gt;
-              &lt;esql:pool&gt;personnel&lt;/esql:pool&gt;
-
-              &lt;!-- query execution blocks can be repeated --&gt;
-              &lt;esql:execute-query&gt;
-
-                &lt;!-- Find all departments and order them --&gt;
-                &lt;esql:query&gt;
-                  SELECT department_id, department_name
-                  FROM department ORDER BY department_name
-                &lt;/esql:query&gt;
-
-               &lt;!-- What to do with the results --&gt;
-                &lt;esql:results&gt;
-                  &lt;!--
-                       A successful query that returns results
-                       executes this block.  You can also embed
-                       more "execute-query" blocks inside the
-                       row-results.  That way you can have queries
-                       that filter information based on the results
-                       of other queries.
-                  --&gt;
-                  &lt;esql:row-results&gt;
-                    &lt;option&gt;
-                      &lt;xsp:attribute name="name"&gt;
-                        &lt;esql:get-string column="department_id"/&gt;
-                      &lt;/xsp:attribute&gt;
-                      &lt;esql:get-string column="department_name"/&gt;
-                    &lt;/option&gt;
-                  &lt;/esql:row-results&gt;
-                  &lt;!--
-                       Other result types are "no-results" and
-                       "error-results".  A successful query that
-                       does not return results (an empty resultset)
-                       will use the XML embedded in the "no-results"
-                       section.  An unsuccessful query that throws
-                       an exception will use the XML embedded in
-                       the "error-results" section.
-                  --&gt;
-                &lt;/esql:results&gt;
-              &lt;/esql:execute-query&gt;
-            &lt;/esql:connection&gt;
-          &lt;/select&gt;
-        &lt;/p&gt;
-        &lt;submit name="Create Employee"/&gt;
-        &lt;note&gt;
-          * These fields are required.
-        &lt;/note&gt;
-      &lt;/form&gt;
-    &lt;/s1&gt;
-  &lt;/body&gt;
-&lt;/document&gt;
-&lt;/xsp:page&gt;
-  
-</pre>
-</td><td width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-<tr>
-<td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-</table>
-</div>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">As you can see ESQL is flexible and powerful, but the cost of that
-         flexibility is a loss of readability.  Using a logicsheet to wrap
-         information in a business object is another alternative.  Notice how
-         ESQL works:</font>
-</p>
-       
-<blockquote>
-<ul>
-        
-<li>
-<font face="verdana, helvetica, sans serif">First, we specify our connection information which will apply to
-              all queries in the ESQL structure.</font>
-</li>
-        
-<li>
-<font face="verdana, helvetica, sans serif">Next, we specify our first query we are going to use.  Note that
-              you can nest queries as well as have more than one in an
-              "esql:connection" element.</font>
-</li>
-        
-<li>
-<font face="verdana, helvetica, sans serif">Lastly, we specify how we process the results.  There are three
-              different types of results: "esql:row-results", 
-              "esql:no-results", and "esql:error-results".
-              This allows you to handle different scenarios easily.  It is
-              inside the individual results elements that we can nest new
-              queries to process.</font>
-</li>
-       
-</ul>
-</blockquote>
-       
-<font face="verdana, helvetica, sans serif" color="#0086b2"><b>A Note About Actions</b></font>
-        
-<p>
-<font color="black" face="verdana,helvetica,sanserif">Actions are the bread and butter of logic processing in Cocoon.
-           There are a number of approaches that you can take when developing
-           Actions.  You can create a specific action for each piece of
-           business logic.  This approach is very heavy handed and requires you
-           to spend a lot of development time creating actions.</font>
-</p>
-        
-<p>
-<font color="black" face="verdana,helvetica,sanserif">The preferred method for creating actions is to provide a generic
-           action that can handle a wide range of specific actions.  The
-           Database Actions and Validator Actions are examples of this approach.
-           They will read a configuration file specified by a parameter, and
-           they will modify the specific results based on the configuration
-           file.  In order to take advantage of this for your own Actions, you
-           can extend the AbstractComplimentaryConfigurationAction.  Basically
-           what it does is encapsulate the logic for reading and caching the
-           Configuration information for your Action.</font>
-</p>
-       
-     
-   
-   
-<font face="verdana, helvetica, sans serif" size="+1" color="#0086b2"><b>Redirects</b></font>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">Most web developers agree that redirecting a user based on input is a
-         valuable and necessary part of web development.  In Cocoon there are
-         only two locations where you can issue redirects: the Sitemap and
-         Actions.  In essence, Cocoon does require you to plan so that redirects
-         are only used when necessary.</font>
-</p>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">One approach that is good to use is to require all traffic to go
-         through a URL controlling action.  The Action will test to see if the
-         user is logged in, and if not will send them to the login page.
-         Another derivation on this approach is to test for a user's role,
-         and if they do not have access redirect them to a different page.</font>
-</p>
-   
-   
-<font face="verdana, helvetica, sans serif" size="+1" color="#0086b2"><b>Writing an Action</b></font>
-     
-<p>
-<font color="black" face="verdana,helvetica,sanserif">Writing an action is as simple as writing a Component that conforms to
-        the Action interface.  Be sure to examine the different Actions that are
-        in the org.apache.cocoon.acting package - you might find some abstract
-        actions that you can extend.  Actions are Avalon Components, so you may
-        want to read Avalon's Whitepaper for more information.</font>
-</p>
-     
-<p>
-<table border="0" cellpadding="0" cellspacing="3" width="100%">
-<tr>
-<td valign="top" width="28"><img alt="Note" border="0" hspace="0" vspace="0" height="29" width="28" src="images/note.gif"></td><td valign="top"><font color="black" face="verdana,helvetica,sanserif" size="-1"><i>Actions will return a map that contains values that the sitemap
-           administrator can use in the sitemap.  If the Action returns a null,
-           then anything inside the "map:act" element will not be
-           executed.</i></font></td>
-</tr>
-</table>
-</p>
-     
-<font face="verdana, helvetica, sans serif" size="+1" color="#0086b2">Return Values</font>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">The Action interface specifies that it returns a Map.  This Map is
-         used for value substitution in the sitemap, and communicating
-         information to other Actions.  When an Action is specified in the
-         sitemap, it uses the following syntax:</font>
-</p>
-
-<div align="center">
-<table border="0" cellpadding="0" cellspacing="4">
-<tr>
-<td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-<tr>
-<td width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td bgcolor="#ffffff">
-<pre>
-  
-&lt;map:act type="my-action"&gt;
-  &lt;map:generate src="{source}"/&gt;
-  &lt;map:transform src="doc2{theme}"/&gt;
-  &lt;map:serialize/&gt;
-&lt;/map:act&gt;
-  
-</pre>
-</td><td width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-<tr>
-<td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-</table>
-</div>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">The above code snippet assumes you have an Action with the name
-         "my-action" already specified.  It also assumes that there
-         are two "parameters" returned from the action in the Map. The
-         sitemap queries the returned Map for the "source" and
-         "theme" values, and substitutes their values in place of the
-         curly braces that referenced it.  In other words, when it sees the
-         "map:generate" with an src attribute of "{source}"
-         it looks in the Map.  For our discussion, let us say the value stored
-         is "index.xml".  The Sitemap will perform the substitution
-         so that the src attribute now containts "index.xml".</font>
-</p>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">In the case that the above the action might return a null value.  In
-         that case, everything inside the "map:act" element is
-         skipped.  You can use this to good advantage like the *ValidatorActions
-         do.  If everything is validated correctly, they return a Map.  If there
-         is an error, they return a null, and place the information in Request
-         attributes.</font>
-</p>
-     
-   
- 
- 
-<font face="verdana, helvetica, sans serif" size="+2" color="#0086b2">Cocoon Supplied Components</font>
-<hr style="color: #0086b2" size="1">
-  
-<p>
-<font color="black" face="verdana,helvetica,sanserif">Cocoon supplies a number of different Components for your use.  The types
-     of Components we will discuss here are Generators, Transformers,
-     Serializers, Readers, and Actions.  This are the important Components that
-     allow you to do you job.</font>
-</p>
-  
-<font face="verdana, helvetica, sans serif" size="+1" color="#0086b2"><b>Generators</b></font>
-    
-<p>
-<font color="black" face="verdana,helvetica,sanserif">A Generator will create SAX events for a SAX stream-whether it reads from
-       an input stream or it generates it on the fly.  All built in generators
-       are in the package "org.apache.cocoon.generation".</font>
-</p>
-    
-<font face="verdana, helvetica, sans serif" size="+1" color="#0086b2">DirectoryGenerator</font>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">Reads a directory, and builds an XML document based on the contents.
-         You can pass parameters to it to control how it behaves (note
-         parameter names are case sensitive):</font>
-</p>
-      
-<blockquote>
-<ul>
-        
-<li>
-<font face="verdana, helvetica, sans serif">dateFormat - a format string that you would use in the Java
-              SimpleDateFormat object</font>
-</li>
-        
-<li>
-<font face="verdana, helvetica, sans serif">depth - the maximum number of directories deep the generator will
-              look (defaults to 1)</font>
-</li>
-        
-<li>
-<font face="verdana, helvetica, sans serif">root - a regular expression to find the root directory</font>
-</li>
-        
-<li>
-<font face="verdana, helvetica, sans serif">include - a regular expression to declare the files/directories
-              that will be included in the list</font>
-</li>
-        
-<li>
-<font face="verdana, helvetica, sans serif">exclude - a regular expression to declare the files/directories
-              that will not be included in the list</font>
-</li>
-      
-</ul>
-</blockquote>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">When you use this Generator, you must have the Jakarta Regexp package
-         installed in your WEB-INF/libs directory.  Also, the DirectoryGenerator
-         is not Cacheable so the results will be generated fresh each time.</font>
-</p>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">The resulting XML looks like this:</font>
-</p>
-
-<div align="center">
-<table border="0" cellpadding="0" cellspacing="4">
-<tr>
-<td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-<tr>
-<td width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td bgcolor="#ffffff">
-<pre>
-  
-&lt;?xml version="1.0"?&gt;
-
-&lt;directory xmlns="http://apache.org/cocoon/directory/2.0"
-           name="C:\path\dir\"
-           lastModified="135432153351"
-           date="11 Jun 2001"&gt;
-  &lt;file name="C:\path\dir\file.xml" lastModified="135432153351"
-        date="11 Jun 2001"/&gt;
-&lt;/directory&gt;
-  
-</pre>
-</td><td width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-<tr>
-<td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-</table>
-</div>
-    
-    
-<font face="verdana, helvetica, sans serif" size="+1" color="#0086b2">FileGenerator</font>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">This generator and the ServerPagesGenerator will be your most used
-         generators.  The FileGenerator reads an XML file from an input source,
-         and converts it into a SAX stream.</font>
-</p>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">When you use this Generator, you must have a JAXP 1.1 compliant parser
-         installed in your WEB-INF/libs directory.  You may also use the Xerces
-         parser bypassing the JAXP requirement.  The FileGenerator is Cacheable,
-         so the results will only be re-read when the file changes.</font>
-</p>
-    
-    
-<font face="verdana, helvetica, sans serif" size="+1" color="#0086b2">FragmentExtractorGenerator</font>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">This generator is used in conjunction with the
-         FragmentExtractorTransformer (more on that in the transformers
-         section).  The FragmentExtractorTransformer splits an XML document into
-         smaller parts so you can treat each smaller part as a unique document.
-         To see this in action, check out the Cocoon supplied 
-         <a href="../overview.html#samples">samples</a>
-         and click on the SVG Welcome page.</font>
-</p>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">This Generator caches the results from the FragmentExtractorTransformer
-         for quick retrieval later.  It is Cacheable, so the fragments are
-         generated once and the cached version is read from that point
-         forward.</font>
-</p>    
-    
-    
-<font face="verdana, helvetica, sans serif" size="+1" color="#0086b2">HTMLGenerator</font>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">This generator is used to read in an HTML file that may not be properly
-         formatted to comply with XML standards.  The result is properly
-         formatted XHTML.</font>
-</p>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">This generator requires the Tidy.jar file installed in the
-         WEB-INF/libs directory.  The HTMLGenerator is Cacheable, so the results
-         can be cached for application speedup.</font>
-</p>      
-    
-    
-<font face="verdana, helvetica, sans serif" size="+1" color="#0086b2">ImageDirectoryGenerator</font>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">This generator is an extension of the DirectoryGenerator, so it has the
-         same requirements.  It extends the markup to include two new attributes
-         for the "file" element: "height" and
-         "width".  The ImageDirectoryGenerator reads every GIF and
-         JPEG file to get the dimensions.</font>
-</p>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">This generator is not Cacheable (just like the DirectoryGenerator).</font>
-</p>
-    
-    
-<font face="verdana, helvetica, sans serif" size="+1" color="#0086b2">JspGenerator</font>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">This generator executes a JSP file and parses the result.  The JSP must
-         generate valid XML, and be a file in the context.</font>
-</p>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">This generator requires a JAXP 1.1 compliant parser or Xerces if your
-         environment will not allow you to install one.  It is also not
-         cacheable so the results are generated each time.</font>
-</p>
-    
-    
-<font face="verdana, helvetica, sans serif" size="+1" color="#0086b2">PhpGenerator</font>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">This generator functions just like the JspGenerator, but with PHP
-         templates.  The PHP must generate valid XML, and be a file in the
-         context.</font>
-</p>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">This generator requires a JAXP 1.1 compliant parser and the
-         phpservlet.jar file that comes from http://php.net.  Install the files
-         in the WEB-INF/libs directory.  The PhpGenerator is not Cacheable.</font>
-</p>
-    
-    
-<font face="verdana, helvetica, sans serif" size="+1" color="#0086b2">RequestGenerator</font>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">This generator converts the Request object into an XML representation.
-         It is best used for debugging purposes.  The resulting XML follows:</font>
-</p>
-
-<div align="center">
-<table border="0" cellpadding="0" cellspacing="4">
-<tr>
-<td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-<tr>
-<td width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td bgcolor="#ffffff">
-<pre>
-  
-&lt;request xmlns="http://xml.apache.org/cocoon/requestgenerator/2.0"
-         target="index.html" source="context://docs/index.xml"&gt;
-
-  &lt;requestHeaders&gt;
-    &lt;header name="HOST_NAME"&gt;johny-bravo.infoplanning.com&lt;/header&gt;
-    &lt;!-- repeat for each header --&gt;
-  &lt;/requestHeaders&gt;
-
-  &lt;requestParameters&gt;
-    &lt;parameter name="form-param"&gt;
-      &lt;value&gt;1&lt;/value&gt;
-      &lt;!-- repeat for each value in "form-param" --&gt;
-    &lt;/parameter&gt;
-    &lt;!-- repeat for each parameter --&gt;
-  &lt;/requestParameters&gt;
-
-  &lt;configurationParameters&gt;
-    &lt;parameter
-       name="configurations"&gt;context://WEB-INF/cocoon.xconf&lt;/parameter&gt;
-    &lt;!-- repeat for each parameter --&gt;
-  &lt;/configurationParameters&gt;
-&lt;/request&gt;
-  
-</pre>
-</td><td width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-<tr>
-<td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-</table>
-</div>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">The RequestGenerator does not have any special requirements for
-         libraries, and it is not Cacheable.</font>
-</p>
-    
-    
-<font face="verdana, helvetica, sans serif" size="+1" color="#0086b2">ScriptGenerator</font>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">The ScriptGenerator uses the Bean Scripting Framework (BSF) and an
-         associated interpreter to generate valid XML.  If you add language
-         support, you will have to embed the following configuration
-         information:</font>
-</p>
-
-<div align="center">
-<table border="0" cellpadding="0" cellspacing="4">
-<tr>
-<td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-<tr>
-<td width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td bgcolor="#ffffff">
-<pre>
-  
-&lt;add-languages&gt;
-  &lt;!-- repeat the following for each language: --&gt;
-  &lt;language name="kawa-scheme"
-            src="org.gnu.kawa.bsf.engines.KawaEngine"&gt;
-    &lt;extension&gt;scm&lt;/extension&gt;
-    &lt;!-- repeat for each file extension --&gt;
-  &lt;/language&gt;
-&lt;/add-languages&gt;
-  
-</pre>
-</td><td width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-<tr>
-<td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-</table>
-</div>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">The ScriptGenerator requires that you have the bsf.jar in your
-         WEB-INF/libs directory along with any jars for the script interpreters
-         you use.  The ScriptGenerator is not Cacheable.</font>
-</p>
-    
-    
-<font face="verdana, helvetica, sans serif" size="+1" color="#0086b2">ServerPagesGenerator</font>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">The ServerPagesGenerator is the XML Server Pages (XSP) engine.  It
-         automatically compiles a new Generator at runtime based on an input
-         XML file.</font>
-</p>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">This generator requires that you have a JAXP 1.1 compliant parser and
-         XSLT engine installed in your WEB-INF/libs directory.  It also requires
-         you to have the JDK's tools.jar file in your classpath.  If you
-         reference any packages, they must also be in your classpath.  The
-         created generator is not Cacheable.</font>
-</p>
-    
-    
-<font face="verdana, helvetica, sans serif" size="+1" color="#0086b2">StatusGenerator</font>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">The StatusGenerator is another debug tool.  It provides status
-         information for the Cocoon engine.  The resultant XML is in the
-         following format:</font>
-</p>
-
-<div align="center">
-<table border="0" cellpadding="0" cellspacing="4">
-<tr>
-<td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-<tr>
-<td width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td bgcolor="#ffffff">
-<pre>
-  
-&lt;statusinfo xmlns="http://apache.org/cocoon/status/2.0"
-            xmlns:xlink="http://www.w3.org/1999/xlink"
-            host="johnny-bravo.infoplanning.com"
-            date="7/16/2001 1:16:42 pm"&gt;
-  &lt;group name="vm"&gt;
-    &lt;group name="memmory"&gt;
-      &lt;value name="total"&gt;&lt;line&gt;5213255&lt;/line&gt;&lt;/value&gt;
-      &lt;value name="free"&gt;&lt;line&gt;12321211&lt;/line&gt;&lt;/value&gt;
-    &lt;/group&gt;
-    &lt;group name="jre"&gt;
-      &lt;value name="version"&gt;&lt;line&gt;1.3.1&lt;/line&gt;&lt;/value&gt;
-      &lt;value name="java-vendor"
-             xlink:type="simple"
-             xlink:href="http://java.sun.com/jdk/1.3/"&gt;
-        &lt;line&gt;Sun Microsystems Inc.&lt;/line&gt;
-      &lt;/value&gt;
-    &lt;/group&gt;
-    &lt;group name="operating-system"&gt;
-      &lt;value name="name"&gt;&lt;line&gt;Windows 2000&lt;/line&gt;&lt;/value&gt;
-      &lt;value name="architecture"&gt;&lt;line&gt;x86&lt;/line&gt;&lt;/value&gt;
-      &lt;value name="version"&gt;&lt;line&gt;5.0&lt;/line&gt;&lt;/value&gt;
-    &lt;/group&gt;
-  &lt;/group&gt;
-  &lt;value name="classpath"&gt;
-    &lt;line&gt;C:\tomcat\lib\tomcat.jar&lt;/line&gt;
-    &lt;line&gt;C:\jdk1.3.1\lib\tools.jar&lt;/line&gt;
-  &lt;/value&gt;
-&lt;/statusinfo&gt;
-  
-</pre>
-</td><td width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-<tr>
-<td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-</table>
-</div>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">The results are not cacheable, and do not require any special
-         libraries.</font>
-</p>
-    
-    
-<font face="verdana, helvetica, sans serif" size="+1" color="#0086b2">StreamGenerator</font>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">The StreamGenerator is used to convert the Request's InputStream
-         into a SAX XML stream.  Alternately, it will accept the magic form
-         parameter "form-name" and read the input stream that the
-         parameter points to.</font>
-</p>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">This generator requires the JAXP 1.1 compliant parser (or Xerces).  It
-         is not cacheable.</font>
-</p>
-    
-    
-<font face="verdana, helvetica, sans serif" size="+1" color="#0086b2">VelocityGenerator</font>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">The VelocityGenerator is used to convert the output from the Velocity
-         template engine to a valid XML stream.</font>
-</p>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">This generator requires Jakarta Velocity and a JAXP 1.1 compliant
-         parser installed in WEB-INF/libs.  It is not Cacheable.</font>
-</p>
-    
-  
-  
-<font face="verdana, helvetica, sans serif" size="+1" color="#0086b2"><b>Transformers</b></font>
-    
-<p>
-<font color="black" face="verdana,helvetica,sanserif">Transformers read a SAX stream, manipulate the XML stream, and send the
-       results to the next Component in the chain.  All built in generators are
-       in the package "org.apache.cocoon.generation".</font>
-</p>
-    
-<font face="verdana, helvetica, sans serif" size="+1" color="#0086b2">CIncludeTransformer</font>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">The CIncludeTransformer looks for instances of the
-         "ci:include" element, and will embed another XML resource in
-         your document.  That resource can be in the sitemap so you can include
-         the results of processed XSP pages.  An example follows:</font>
-</p>
-
-<div align="center">
-<table border="0" cellpadding="0" cellspacing="4">
-<tr>
-<td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-<tr>
-<td width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td bgcolor="#ffffff">
-<pre>
-  
-&lt;document xmlns:ci="http://apache.org/cocoon/include/1.0"&gt;
-  &lt;ci:include src="cocoon://my-resource.xml"
-              element="body"
-              ns="http://mycompany.com/my-resource/1.0"
-              prefix="res"/&gt;
-&lt;/document&gt;
-  
-</pre>
-</td><td width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-<tr>
-<td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-</table>
-</div>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">The Transformer will read the results from the sitemap, and embed it
-         into this document with a new root element "body" using a new
-         namespace (xmlns:res="http://mycompany.com/my-resource/1.0").
-         The results are not cached.</font>
-</p>
-    
-    
-<font face="verdana, helvetica, sans serif" size="+1" color="#0086b2">FilterTransformer</font>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">The FilterTransformer will look for instances of an element you specify
-         using parameters, and will not forward any SAX events for that element
-         or any child elements.  You can pass parameters to it to control how it
-         behaves (note parameter names are case sensitive):</font>
-</p>
-      
-<blockquote>
-<ul>
-        
-<li>
-<font face="verdana, helvetica, sans serif">element-name - The name of the element to filter</font>
-</li>
-        
-<li>
-<font face="verdana, helvetica, sans serif">count - the number of times the element will be filtered</font>
-</li>
-        
-<li>
-<font face="verdana, helvetica, sans serif">blocknr - the element number that filtering begins</font>
-</li>
-      
-</ul>
-</blockquote>
-    
-    
-<font face="verdana, helvetica, sans serif" size="+1" color="#0086b2">FragmentExtractorTransformer</font>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">This is transformation half of the FragmentExtractor.  This transformer
-         sieves an incoming stream of xml with embedded SVG images and replaces
-         the images with a xlink locator pointing to the image.  Ultimately this
-         could be much more general, but currently it is mainly an SVG
-         extraction.</font>
-</p>
-    
-    
-<font face="verdana, helvetica, sans serif" size="+1" color="#0086b2">I18nTransformer</font>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">This is Cocoon's port of Infozone Group's I18nProcessor.  The
-         word i18n is a shorthand for the longer word
-         "internationalization" (starts with 'i', ends with
-         'n', and has 18 letters in the middle).  The
-         internationalization transformer allows you to look up references by
-         key in an XML dictionary.  This allows you to support your same
-         business processes in many different countries.  You have to pass
-         parameters to it so that it knows how to process i18n requests:</font>
-</p>
-      
-<blockquote>
-<ul>
-        
-<li>
-<font face="verdana, helvetica, sans serif">default_lang - The default language if the requested language does
-              not exist (two character country code)</font>
-</li>
-        
-<li>
-<font face="verdana, helvetica, sans serif">avalailable_lang_X - Language available by the dictionary (two
-              character country code).  Replace the 'X' in the
-              attribute with a number (1, 2, 3).</font>
-</li>
-        
-<li>
-<font face="verdana, helvetica, sans serif">src - The location of the dictionary file.</font>
-</li>
-      
-</ul>
-</blockquote>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">The I18nTransformer reads the request parameter "lang" to
-         determine which language to display to the user.  To translate text
-         either embed the text inside the "i18n:text" element, or the
-         attribute name inside the "i18n:attr" attribute.</font>
-</p>
-
-<div align="center">
-<table border="0" cellpadding="0" cellspacing="4">
-<tr>
-<td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-<tr>
-<td width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td bgcolor="#ffffff">
-<pre>
-  
-&lt;document xmlns:i18n="http://apache.org/cocoon/i18n/2.0"&gt;
-  &lt;body&gt;
-    &lt;s1 title="Test Title" i18n:attr="title"&gt;
-      &lt;p&gt;
-       &lt;i18n:text&gt;This is replaceable text.&lt;/i18n:text&gt;
-      &lt;/p&gt;
-    &lt;/s1&gt;
-  &lt;/body&gt;
-&lt;/document&gt;
-  
-</pre>
-</td><td width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-<tr>
-<td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-</table>
-</div>         
-    
-    
-<font face="verdana, helvetica, sans serif" size="+1" color="#0086b2">LDAPTransformer</font>
-      
-<p>
-<font color="black" face="verdana,helvetica,sanserif">The LDAPTransformer is a class that can be plugged into a pipeline to
-         transform the SAX events which passes through this transformer into
-         queries an responses to/from a LDAP interface.</font>
-</p>
-    
-  
- 
- 
-<font face="verdana, helvetica, sans serif" size="+2" color="#0086b2">The Sitemap</font>
-<hr style="color: #0086b2" size="1">
-  
-<p>
-<font color="black" face="verdana,helvetica,sanserif">This section is meant primarily as a reference for the Sitemap Manager.
-     The person in this role needs to have a better understanding of the sitemap
-     than any other role.  The sitemap is a relatively new concept, and as such
-     is subject to refinement.  There have been a couple of proposals to replace
-     it with something else, but nothing has been started yet.</font>
-</p>
-  
-<p>
-<font color="black" face="verdana,helvetica,sanserif">The Sitemap is composed of three major parts: component declaration,
-     resource declaration, and pipeline declaration.  You will only use a few
-     different types of components in the sitemap: Generators, Transformers,
-     Serializers, Readers, Matchers, Selectors, and Actions.  Generators create
-     XML and pass the results in a SAX stream.  Transformers read a SAX stream
-     and manipulate the results on the way through.  Serializers read a SAX
-     stream, and convert it into the servlet's output stream.  Readers read
-     an input stream and copy the results to the servlet's output stream.  
-     Matchers and Selectors are used to choose how to process an incoming
-     request.  Lastly, Actions are used to perform logic only functions (no
-     display logic).</font>
-</p>
-  
-<p>
-<font color="black" face="verdana,helvetica,sanserif">Below is the root element of all sitemaps:</font>
-</p>
-
-<div align="center">
-<table border="0" cellpadding="0" cellspacing="4">
-<tr>
-<td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td height="1" width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-<tr>
-<td width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td><td bgcolor="#ffffff">
-<pre>
-  
-&lt;map:sitemap xmlns:map="http://apache.org/cocoon/sitemap/1.0"&gt;
-&lt;/map:sitemap&gt;
-  
-</pre>
-</td><td width="1" bgcolor="#0086b2"><img border="0" hspace="0" vspace="0" height="1" width="1" src="images/void.gif"></td>
-</tr>
-<tr>

[... 2050 lines stripped ...]


Mime
View raw message