forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r357603 [1/11] - in /forrest/site: ./ docs_0_60/ docs_0_60/howto/ docs_0_60/howto/bugzilla-patch/ docs_0_70/ docs_0_70/howto/ docs_0_70/howto/cvs-ssh/ docs_0_80/ docs_0_80/howto/ docs_0_80/howto/cvs-ssh/ dtdx/ pluginDocs/plugins_0_70/ plugi...
Date Mon, 19 Dec 2005 01:33:15 GMT
Author: crossley
Date: Sun Dec 18 17:31:25 2005
New Revision: 357603

URL: http://svn.apache.org/viewcvs?rev=357603&view=rev
Log:
Automatic publish from forrestbot

Added:
    forrest/site/locationmap.xml   (with props)
Modified:
    forrest/site/body-index.html
    forrest/site/changes.rss
    forrest/site/changes.xml
    forrest/site/committed.html
    forrest/site/docs_0_60/build.html
    forrest/site/docs_0_60/cap.html
    forrest/site/docs_0_60/catalog.html
    forrest/site/docs_0_60/changes.html
    forrest/site/docs_0_60/changes.pdf
    forrest/site/docs_0_60/changes.rss
    forrest/site/docs_0_60/compliance.html
    forrest/site/docs_0_60/faq.html
    forrest/site/docs_0_60/forrest-contract.html
    forrest/site/docs_0_60/howto/bugzilla-patch/howto-bugzilla-patch.html
    forrest/site/docs_0_60/howto/howto-asf-mirror.html
    forrest/site/docs_0_60/howto/howto-howto.html
    forrest/site/docs_0_60/howto/howto-pdf-tab.html
    forrest/site/docs_0_60/linking.html
    forrest/site/docs_0_60/project-sitemap.html
    forrest/site/docs_0_60/searching.html
    forrest/site/docs_0_60/sitemap-ref.html
    forrest/site/docs_0_60/todo.html
    forrest/site/docs_0_60/upgrading_06.html
    forrest/site/docs_0_60/validation.html
    forrest/site/docs_0_60/your-project.html
    forrest/site/docs_0_70/build.html
    forrest/site/docs_0_70/cap.html
    forrest/site/docs_0_70/catalog.html
    forrest/site/docs_0_70/changes.html
    forrest/site/docs_0_70/changes.pdf
    forrest/site/docs_0_70/changes.rss
    forrest/site/docs_0_70/changes.xml
    forrest/site/docs_0_70/compliance.html
    forrest/site/docs_0_70/faq.html
    forrest/site/docs_0_70/forrest-contract.html
    forrest/site/docs_0_70/howto/cvs-ssh/howto-cvs-ssh.html
    forrest/site/docs_0_70/howto/howto-asf-mirror.html
    forrest/site/docs_0_70/howto/howto-buildPlugin.html
    forrest/site/docs_0_70/howto/howto-corner-images.html
    forrest/site/docs_0_70/howto/howto-custom-html-source.html
    forrest/site/docs_0_70/howto/howto-forrest-from-maven.html
    forrest/site/docs_0_70/howto/howto-howto.html
    forrest/site/docs_0_70/howto/howto-pdf-tab.html
    forrest/site/docs_0_70/howto/howto-view-contracts.html
    forrest/site/docs_0_70/howto/howto-view-dsl.html
    forrest/site/docs_0_70/howto/howto-view-install.html
    forrest/site/docs_0_70/libre-intro.html
    forrest/site/docs_0_70/linking.html
    forrest/site/docs_0_70/primer.html
    forrest/site/docs_0_70/project-sitemap.html
    forrest/site/docs_0_70/searching.html
    forrest/site/docs_0_70/sitemap-ref.html
    forrest/site/docs_0_70/todo.html
    forrest/site/docs_0_70/upgrading_07.html
    forrest/site/docs_0_70/validation.html
    forrest/site/docs_0_70/your-project.html
    forrest/site/docs_0_80/build.html
    forrest/site/docs_0_80/cap.html
    forrest/site/docs_0_80/catalog.html
    forrest/site/docs_0_80/changes.html
    forrest/site/docs_0_80/changes.pdf
    forrest/site/docs_0_80/changes.rss
    forrest/site/docs_0_80/changes.xml
    forrest/site/docs_0_80/compliance.html
    forrest/site/docs_0_80/faq.html
    forrest/site/docs_0_80/forrest-contract.html
    forrest/site/docs_0_80/howto/cvs-ssh/howto-cvs-ssh.html
    forrest/site/docs_0_80/howto/howto-asf-mirror.html
    forrest/site/docs_0_80/howto/howto-buildPlugin.html
    forrest/site/docs_0_80/howto/howto-buildPlugin.pdf
    forrest/site/docs_0_80/howto/howto-corner-images.html
    forrest/site/docs_0_80/howto/howto-custom-html-source.html
    forrest/site/docs_0_80/howto/howto-dev.html
    forrest/site/docs_0_80/howto/howto-forrest-from-maven.html
    forrest/site/docs_0_80/howto/howto-howto.html
    forrest/site/docs_0_80/howto/howto-pdf-tab.html
    forrest/site/docs_0_80/howto/howto-structurer-contracts.html
    forrest/site/docs_0_80/howto/howto-structurer-install.html
    forrest/site/docs_0_80/howto/howto-view-contracts.html
    forrest/site/docs_0_80/howto/howto-view-dsl.html
    forrest/site/docs_0_80/howto/howto-view-install.html
    forrest/site/docs_0_80/libre-intro.html
    forrest/site/docs_0_80/linking.html
    forrest/site/docs_0_80/locationmap.html
    forrest/site/docs_0_80/locationmap.pdf
    forrest/site/docs_0_80/primer.html
    forrest/site/docs_0_80/project-sitemap.html
    forrest/site/docs_0_80/searching.html
    forrest/site/docs_0_80/sitemap-ref.html
    forrest/site/docs_0_80/todo.html
    forrest/site/docs_0_80/upgrading_08.html
    forrest/site/docs_0_80/validation.html
    forrest/site/docs_0_80/views.html
    forrest/site/docs_0_80/your-project.html
    forrest/site/dtdx/document-v12.html
    forrest/site/dtdx/document-v13.html
    forrest/site/dtdx/document-v20.html
    forrest/site/dtdx/dtd-docs.html
    forrest/site/forrest-friday.html
    forrest/site/forrest-issues.html
    forrest/site/forrest-issues.pdf
    forrest/site/guidelines.html
    forrest/site/index.html
    forrest/site/mirrors.html
    forrest/site/pluginDocs/plugins_0_70/index.html
    forrest/site/pluginDocs/plugins_0_70/pluginInfrastructure.html
    forrest/site/pluginDocs/plugins_0_70/usingPlugins.html
    forrest/site/pluginDocs/plugins_0_80/index.html
    forrest/site/pluginDocs/plugins_0_80/pluginInfrastructure.html
    forrest/site/pluginDocs/plugins_0_80/usingPlugins.html
    forrest/site/tools/eclipse.html
    forrest/site/tools/forrestbar.html
    forrest/site/tools/forrestbot-web-interface.html
    forrest/site/tools/xxe.html
    forrest/site/zone.html

Modified: forrest/site/body-index.html
URL: http://svn.apache.org/viewcvs/forrest/site/body-index.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/body-index.html (original)
+++ forrest/site/body-index.html Sun Dec 18 17:31:25 2005
@@ -73,7 +73,7 @@
 <ul>
         
 <li>
-<strong>Step 1</strong>: Do <span class="codefrag ">'forrest seed'</span> to populate
+<strong>Step 1</strong>: Do <span class="codefrag">'forrest seed'</span> to populate
           the directory with template site structure and contents.</li>
         
 <li>
@@ -81,9 +81,9 @@
           task-specific, presentation-neutral XML.</li>
         
 <li>
-<strong>Step 3</strong>: Do <span class="codefrag ">'forrest run'</span> then use
+<strong>Step 3</strong>: Do <span class="codefrag">'forrest run'</span> then use
           the web browser to immediately review
-          changes at <span class="codefrag ">http://localhost:8888/</span>
+          changes at <span class="codefrag">http://localhost:8888/</span>
           
 <ul>
 <li>
@@ -101,7 +101,7 @@
 </li>
         
 <li>
-<strong>Step 4</strong>: Do <span class="codefrag ">'forrest'</span> to generate the
+<strong>Step 4</strong>: Do <span class="codefrag">'forrest'</span> to generate the
           complete website from the XML sources.
           Various styles (known as skins) are available. Custom skins
           can be developed.</li>

Modified: forrest/site/changes.rss
URL: http://svn.apache.org/viewcvs/forrest/site/changes.rss?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/changes.rss (original)
+++ forrest/site/changes.rss Sun Dec 18 17:31:25 2005
@@ -48,7 +48,24 @@
         Added document to facilitate
         upgrading to v0.8
       </description></item>
+      
+      <item><title>code add</title><link>changes.html</link><description>code add
+        by
+        TS
+        :
+         New protocol / source factory 
+        that is contacting the locationmap module to look up the source. Use it 
+        like lm://resolve.contract.html.content-main for source resolving. 
+        </description></item>
         
+      <item><title>code add</title><link>changes.html</link><description>code add
+        by
+        TS
+        :
+         Added first implementation of 
+        the dispatcher. Including contract bean implementation and interface; 
+        dispatcher exception and dispatcher transformers. </description></item>
+      
       <item><title>code update</title><link>changes.html</link><description>code update
         by
         DC
@@ -4267,7 +4284,20 @@
 
         Added document to facilitate
         upgrading to v0.8
-      </description></item><item><title>code update</title><link>changes.html</link><description>code update
+      </description></item><item><title>code add</title><link>changes.html</link><description>code add
+        by
+        TS
+        :
+         New protocol / source factory 
+        that is contacting the locationmap module to look up the source. Use it 
+        like lm://resolve.contract.html.content-main for source resolving. 
+        </description></item><item><title>code add</title><link>changes.html</link><description>code add
+        by
+        TS
+        :
+         Added first implementation of 
+        the dispatcher. Including contract bean implementation and interface; 
+        dispatcher exception and dispatcher transformers. </description></item><item><title>code update</title><link>changes.html</link><description>code update
         by
         DC
         :

Modified: forrest/site/changes.xml
URL: http://svn.apache.org/viewcvs/forrest/site/changes.xml?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/changes.xml (original)
+++ forrest/site/changes.xml Sun Dec 18 17:31:25 2005
@@ -1,6 +1,11 @@
 <?xml version="1.0" encoding="ISO-8859-1"?><!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "document-v13.dtd">
 <document><header><title>History of Changes</title></header><body><p><link href="changes.rss"><img alt="RSS" src="images/rss.png"/></link></p>
-    <section id="version_0.8-dev"><title>Version 0.8-dev (not yet released)</title><section><title>Changes to the Code Base</title><ul><li><icon alt="add" src="images/add.jpg"/>
+    <section id="version_0.8-dev"><title>Version 0.8-dev (not yet released)</title><section><title>Changes to the Code Base</title><ul><li><icon alt="add" src="images/add.jpg"/> New protocol / source factory 
+        that is contacting the locationmap module to look up the source. Use it 
+        like lm://resolve.contract.html.content-main for source resolving. 
+        (TS)</li><li><icon alt="add" src="images/add.jpg"/> Added first implementation of 
+        the dispatcher. Including contract bean implementation and interface; 
+        dispatcher exception and dispatcher transformers. (TS)</li><li><icon alt="add" src="images/add.jpg"/>
         The broken-links file is now copied into to the site root as
         "broken-links.xml" so that when building with Forrestbot
         you can easily view it.

Modified: forrest/site/committed.html
URL: http://svn.apache.org/viewcvs/forrest/site/committed.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/committed.html (original)
+++ forrest/site/committed.html Sun Dec 18 17:31:25 2005
@@ -282,7 +282,7 @@
 <p>
 <img alt="committer path" src="committed-1.png"></p>
 <p>Meritocracy progresses this way
-      <span class="codefrag ">------------&gt; ------------------------&gt;</span>
+      <span class="codefrag">------------&gt; ------------------------&gt;</span>
 </p>
 <p>Note that this is not a hierarchy, it is a progression from a 
       broad user base from which those that wish to to contribute to the 

Modified: forrest/site/docs_0_60/build.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_60/build.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_60/build.html (original)
+++ forrest/site/docs_0_60/build.html Sun Dec 18 17:31:25 2005
@@ -316,16 +316,16 @@
           </li>
           
 <li>At a command prompt, enter
-           '<span class="codefrag ">svn co http://svn.apache.org/repos/asf/forrest/trunk forrest</span>'
-           (committers should replace <span class="codefrag ">http</span> with <span class="codefrag ">https</span>).</li>
+           '<span class="codefrag">svn co http://svn.apache.org/repos/asf/forrest/trunk forrest</span>'
+           (committers should replace <span class="codefrag">http</span> with <span class="codefrag">https</span>).</li>
           
-<li>This will create a directory called "<span class="codefrag ">forrest</span>" where the Forrest source will be stored.</li> 
+<li>This will create a directory called "<span class="codefrag">forrest</span>" where the Forrest source will be stored.</li> 
         
 </ol>
 <p>Whenever you want to update your Forrest source tree to the current
          version, change to the top-level
-"<span class="codefrag ">forrest</span>" directory and invoke '<span class="codefrag ">svn update</span>'.</p>
-<p>To see what changes you've made, invoke '<span class="codefrag ">svn status</span>'</p>
+"<span class="codefrag">forrest</span>" directory and invoke '<span class="codefrag">svn update</span>'.</p>
+<p>To see what changes you've made, invoke '<span class="codefrag">svn status</span>'</p>
 <p>SVN is really powerful. See
           <a href="http://svnbook.red-bean.com/">Version Control with Subversion</a> - the opensource SVN book.
         </p>
@@ -348,7 +348,7 @@
 </div>
 </div>
 <p>
-       To build Forrest, type '<span class="codefrag ">build</span>' on Windows, or '<span class="codefrag ">./build.sh</span>' on
+       To build Forrest, type '<span class="codefrag">build</span>' on Windows, or '<span class="codefrag">./build.sh</span>' on
        Unix. If everything is successful, you should see a message like this:
      </p>
 <pre class="code">
@@ -365,8 +365,8 @@
   *-----------------------------------------------------------------
      </pre>
 <p>
-       As the message says, you need to add the distribution's <span class="codefrag ">bin/</span>
-       ("binary") directory to your PATH variable, so the <span class="codefrag ">'forrest'</span>
+       As the message says, you need to add the distribution's <span class="codefrag">bin/</span>
+       ("binary") directory to your PATH variable, so the <span class="codefrag">'forrest'</span>
        command is available everywhere:
      </p>
 <pre class="code">
@@ -383,7 +383,7 @@
 <a name="N10090"></a><a name="run"></a>
 <h2 class="underlined_10">Run Forrest, run!</h2>
 <div class="section">
-<p>Forrest is now ready to go. Type '<span class="codefrag ">forrest run</span>' to see
+<p>Forrest is now ready to go. Type '<span class="codefrag">forrest run</span>' to see
     the local webapp using the bundled Jetty server. Edit some of Forrest's
     core documentation and see the effect.
     The document <a href="../docs_0_60/your-project.html">Using Forrest</a> is

Modified: forrest/site/docs_0_60/cap.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_60/cap.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_60/cap.html (original)
+++ forrest/site/docs_0_60/cap.html Sun Dec 18 17:31:25 2005
@@ -326,26 +326,26 @@
 <dt>document-declaration</dt> 
         
 <dd>This rule checks the public ID. It takes one attribute
-          <span class="codefrag ">public-id</span>.</dd> 
+          <span class="codefrag">public-id</span>.</dd> 
         
 <dt>document-element</dt> 
         
 <dd>This rule checks the local name and/or namespace of the document
-          element. These are specified with the attributes <span class="codefrag ">local-name</span> and
-          <span class="codefrag ">namespace</span>. At least one of these two is required.</dd> 
+          element. These are specified with the attributes <span class="codefrag">local-name</span> and
+          <span class="codefrag">namespace</span>. At least one of these two is required.</dd> 
         
 <dt>processing-instruction</dt> 
         
 <dd>This rule checks a processing instruction. It can take two
-          attributes: <span class="codefrag ">target</span> and <span class="codefrag ">data</span>. The target attribute is
+          attributes: <span class="codefrag">target</span> and <span class="codefrag">data</span>. The target attribute is
           always required, the data attribute is optional.</dd> 
         
 <dt>w3c-xml-schema</dt> 
         
 <dd>This rule checks the value of the xsi:schemaLocation and
           xsi:noNamespaceSchemaLocation attributes on the document element. These are
-          specified with the attributes <span class="codefrag ">schema-location</span> and
-          <span class="codefrag ">no-namespace-schema-location</span>.</dd> 
+          specified with the attributes <span class="codefrag">schema-location</span> and
+          <span class="codefrag">no-namespace-schema-location</span>.</dd> 
       
 </dl>
 </div> 

Modified: forrest/site/docs_0_60/catalog.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_60/catalog.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_60/catalog.html (original)
+++ forrest/site/docs_0_60/catalog.html Sun Dec 18 17:31:25 2005
@@ -366,15 +366,15 @@
 <div class="section">
 <p>
         The Forrest DTDs and supporting resources are in the Forrest
-        distribution at <span class="codefrag ">src/core/context/resources/schema/</span>
+        distribution at <span class="codefrag">src/core/context/resources/schema/</span>
       
 </p>
 <p>
         Usually all that is required is to direct your tool to the "catalog"
         supplied by Forrest at either:
-        <span class="codefrag ">$FORREST/src/core/context/resources/schema/catalog.xcat</span>
+        <span class="codefrag">$FORREST/src/core/context/resources/schema/catalog.xcat</span>
         (for XML Catalog) or
-        <span class="codefrag ">$FORREST/src/core/context/resources/schema/catalog</span>
+        <span class="codefrag">$FORREST/src/core/context/resources/schema/catalog</span>
         (for TR 9401 Catalog).
       </p>
 </div>
@@ -388,8 +388,8 @@
 <p>
           Some operating systems already provide a system-wide catalog that
           is used by many tools. This is usually located at
-          <span class="codefrag ">/etc/xml/catalog</span> or at
-          <span class="codefrag ">/usr/share/sgml/catalog</span> files.
+          <span class="codefrag">/etc/xml/catalog</span> or at
+          <span class="codefrag">/usr/share/sgml/catalog</span> files.
         </p>
 <p>
           For an XML Catalog, add this line:
@@ -517,7 +517,7 @@
         that is provided by the
         <a href="http://xml.apache.org/commons/">Apache XML Commons</a>
         project. The resolver is packaged with the Forrest distribution at
-        <span class="codefrag ">lib/core/xml-commons-resolver-x.y.jar</span>
+        <span class="codefrag">lib/core/xml-commons-resolver-x.y.jar</span>
       
 </p>
 <p>

Modified: forrest/site/docs_0_60/changes.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_60/changes.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_60/changes.html (original)
+++ forrest/site/docs_0_60/changes.html Sun Dec 18 17:31:25 2005
@@ -293,10 +293,10 @@
 <a href="#version_0.7.1-dev">Version 0.7.1-dev (not yet released)</a>
 <ul class="minitoc">
 <li>
-<a href="#Changes+to+the+Code+Base-N100D3">Changes to the Code Base</a>
+<a href="#Changes+to+the+Code+Base-N100DD">Changes to the Code Base</a>
 </li>
 <li>
-<a href="#Changes+to+Documentation-N100DD">Changes to Documentation</a>
+<a href="#Changes+to+Documentation-N100E7">Changes to Documentation</a>
 </li>
 </ul>
 </li>
@@ -310,13 +310,13 @@
 <a href="#Changes+to+Build">Changes to Build</a>
 </li>
 <li>
-<a href="#Changes+to+the+Code+Base-N10106">Changes to the Code Base</a>
+<a href="#Changes+to+the+Code+Base-N10110">Changes to the Code Base</a>
 </li>
 <li>
-<a href="#Changes+to+Documentation-N10278">Changes to Documentation</a>
+<a href="#Changes+to+Documentation-N10282">Changes to Documentation</a>
 </li>
 <li>
-<a href="#Contributors-N10318">Contributors</a>
+<a href="#Contributors-N10322">Contributors</a>
 </li>
 </ul>
 </li>
@@ -324,19 +324,19 @@
 <a href="#version_0.6">Version 0.6 (2004-10-15)</a>
 <ul class="minitoc">
 <li>
-<a href="#Changes+to+Project+Administration-N10340">Changes to Project Administration</a>
+<a href="#Changes+to+Project+Administration-N1034A">Changes to Project Administration</a>
 </li>
 <li>
-<a href="#Changes+to+Build-N1034A">Changes to Build</a>
+<a href="#Changes+to+Build-N10354">Changes to Build</a>
 </li>
 <li>
-<a href="#Changes+to+the+Code+Base-N10378">Changes to the Code Base</a>
+<a href="#Changes+to+the+Code+Base-N10382">Changes to the Code Base</a>
 </li>
 <li>
-<a href="#Changes+to+Documentation-N1073D">Changes to Documentation</a>
+<a href="#Changes+to+Documentation-N10747">Changes to Documentation</a>
 </li>
 <li>
-<a href="#Contributors-N1079B">Contributors</a>
+<a href="#Contributors-N107A5">Contributors</a>
 </li>
 </ul>
 </li>
@@ -344,10 +344,10 @@
 <a href="#version_0.5.1">Version 0.5.1 (2003-10-06)</a>
 <ul class="minitoc">
 <li>
-<a href="#Changes+to+Build-N107C7">Changes to Build</a>
+<a href="#Changes+to+Build-N107D1">Changes to Build</a>
 </li>
 <li>
-<a href="#Changes+to+the+Code+Base-N107D1">Changes to the Code Base</a>
+<a href="#Changes+to+the+Code+Base-N107DB">Changes to the Code Base</a>
 </li>
 </ul>
 </li>
@@ -355,13 +355,13 @@
 <a href="#version_0.5">Version 0.5 (2003-09-13)</a>
 <ul class="minitoc">
 <li>
-<a href="#Changes+to+the+Code+Base-N10816">Changes to the Code Base</a>
+<a href="#Changes+to+the+Code+Base-N10820">Changes to the Code Base</a>
 </li>
 <li>
-<a href="#Changes+to+Documentation-N10A17">Changes to Documentation</a>
+<a href="#Changes+to+Documentation-N10A21">Changes to Documentation</a>
 </li>
 <li>
-<a href="#Contributors-N10A21">Contributors</a>
+<a href="#Contributors-N10A2B">Contributors</a>
 </li>
 </ul>
 </li>
@@ -369,13 +369,13 @@
 <a href="#version_0.4">Version 0.4 (2003-02-12)</a>
 <ul class="minitoc">
 <li>
-<a href="#Changes+to+the+Code+Base-N10A3D">Changes to the Code Base</a>
+<a href="#Changes+to+the+Code+Base-N10A47">Changes to the Code Base</a>
 </li>
 <li>
-<a href="#Changes+to+Documentation-N10AA4">Changes to Documentation</a>
+<a href="#Changes+to+Documentation-N10AAE">Changes to Documentation</a>
 </li>
 <li>
-<a href="#Contributors-N10AAE">Contributors</a>
+<a href="#Contributors-N10AB8">Contributors</a>
 </li>
 </ul>
 </li>
@@ -383,16 +383,16 @@
 <a href="#version_0.3">Version 0.3 (2003-01-30)</a>
 <ul class="minitoc">
 <li>
-<a href="#Changes+to+Build-N10AC0">Changes to Build</a>
+<a href="#Changes+to+Build-N10ACA">Changes to Build</a>
 </li>
 <li>
-<a href="#Changes+to+the+Code+Base-N10ACF">Changes to the Code Base</a>
+<a href="#Changes+to+the+Code+Base-N10AD9">Changes to the Code Base</a>
 </li>
 <li>
-<a href="#Changes+to+Documentation-N10BE5">Changes to Documentation</a>
+<a href="#Changes+to+Documentation-N10BEF">Changes to Documentation</a>
 </li>
 <li>
-<a href="#Contributors-N10BEF">Contributors</a>
+<a href="#Contributors-N10BF9">Contributors</a>
 </li>
 </ul>
 </li>
@@ -400,7 +400,7 @@
 <a href="#version_0.2">Version 0.2 (2002-11-16)</a>
 <ul class="minitoc">
 <li>
-<a href="#Changes+to+the+Code+Base-N10BFF">Changes to the Code Base</a>
+<a href="#Changes+to+the+Code+Base-N10C09">Changes to the Code Base</a>
 </li>
 </ul>
 </li>
@@ -408,22 +408,22 @@
 <a href="#version_0.2rc1">Version 0.2rc1 (2002-11-13)</a>
 <ul class="minitoc">
 <li>
-<a href="#Changes+to+Project+Administration-N10C1B">Changes to Project Administration</a>
+<a href="#Changes+to+Project+Administration-N10C25">Changes to Project Administration</a>
 </li>
 <li>
-<a href="#Changes+to+Build-N10C25">Changes to Build</a>
+<a href="#Changes+to+Build-N10C2F">Changes to Build</a>
 </li>
 <li>
-<a href="#Changes+to+the+Code+Base-N10C93">Changes to the Code Base</a>
+<a href="#Changes+to+the+Code+Base-N10C9D">Changes to the Code Base</a>
 </li>
 <li>
 <a href="#Changes+to+Design">Changes to Design</a>
 </li>
 <li>
-<a href="#Changes+to+Documentation-N10D58">Changes to Documentation</a>
+<a href="#Changes+to+Documentation-N10D62">Changes to Documentation</a>
 </li>
 <li>
-<a href="#Contributors-N10DC1">Contributors</a>
+<a href="#Contributors-N10DCB">Contributors</a>
 </li>
 </ul>
 </li>
@@ -443,6 +443,15 @@
 <h3 class="underlined_5">Changes to the Code Base</h3>
 <ul>
 <li>
+<img class="icon" alt="add" src="../images/add.jpg"> New protocol / source factory 
+        that is contacting the locationmap module to look up the source. Use it 
+        like lm://resolve.contract.html.content-main for source resolving. 
+        (TS)</li>
+<li>
+<img class="icon" alt="add" src="../images/add.jpg"> Added first implementation of 
+        the dispatcher. Including contract bean implementation and interface; 
+        dispatcher exception and dispatcher transformers. (TS)</li>
+<li>
 <img class="icon" alt="add" src="../images/add.jpg">
         The broken-links file is now copied into to the site root as
         "broken-links.xml" so that when building with Forrestbot
@@ -496,7 +505,7 @@
 <img class="icon" alt="add" src="../images/add.jpg">
         Use sets of symbols as xml entities for character replacement.
         There is a core set and each project can define a set.
-        For example, use "<span class="codefrag ">&amp;myp-t;</span>" to represent the
+        For example, use "<span class="codefrag">&amp;myp-t;</span>" to represent the
         project name together with trademark symbol
         "My Project Name&trade;".
         See <a href="../docs_0_80/faq.html#xml-entities">FAQ</a>.
@@ -521,7 +530,7 @@
 <img class="icon" alt="add" src="../images/add.jpg">
         Added support for a locationmap. This enables content to be retrieved from a location
         that is defined in a locationmap file (located at 
-        <span class="codefrag ">PROJECT_HOME/src/documentation/content/locationmap.xml</span> file. The
+        <span class="codefrag">PROJECT_HOME/src/documentation/content/locationmap.xml</span> file. The
         advantage of this is that the URL seen by the user need bear no relation to the location
         of the source document, thus Forrest can separate the client URL space from the source
         docuement URL space. Thus, using the locationmap it is possible to pull together
@@ -568,7 +577,7 @@
         Updated tools/forrestbar to be compatiable with recent versions of Firefox.
       (DC) Thanks to Addison Berry.</li>
 </ul>
-<a name="N100A4"></a><a name="Changes+to+Documentation"></a>
+<a name="N100AE"></a><a name="Changes+to+Documentation"></a>
 <h3 class="underlined_5">Changes to Documentation</h3>
 <ul>
 <li>
@@ -584,7 +593,7 @@
         committer</a>.
       () Thanks to Addison Berry. Fixes <a href="http://issues.apache.org/jira/browse/FOR-603">FOR-603</a>.</li>
 </ul>
-<a name="N100C1"></a><a name="Contributors"></a>
+<a name="N100CB"></a><a name="Contributors"></a>
 <h3 class="underlined_5">Contributors</h3>
 <p>This is a list of all people who have contributed to this release, but 
        were full developers on the project. We thank these people for their 
@@ -596,10 +605,10 @@
 </ul>
 </div>
     
-<a name="N100CF"></a><a name="version_0.7.1-dev"></a>
+<a name="N100D9"></a><a name="version_0.7.1-dev"></a>
 <h2 class="underlined_10">Version 0.7.1-dev (not yet released)</h2>
 <div class="section">
-<a name="N100D3"></a><a name="Changes+to+the+Code+Base-N100D3"></a>
+<a name="N100DD"></a><a name="Changes+to+the+Code+Base-N100DD"></a>
 <h3 class="underlined_5">Changes to the Code Base</h3>
 <ul>
 <li>
@@ -612,7 +621,7 @@
         Doing 'forrest clean' will remove both sections.
       (DC)</li>
 </ul>
-<a name="N100DD"></a><a name="Changes+to+Documentation-N100DD"></a>
+<a name="N100E7"></a><a name="Changes+to+Documentation-N100E7"></a>
 <h3 class="underlined_5">Changes to Documentation</h3>
 <ul>
 <li>
@@ -624,10 +633,10 @@
 </ul>
 </div>
     
-<a name="N100EE"></a><a name="version_0.7"></a>
+<a name="N100F8"></a><a name="version_0.7"></a>
 <h2 class="underlined_10">Version 0.7 (2005-06-23)</h2>
 <div class="section">
-<a name="N100F2"></a><a name="Changes+to+Project+Administration"></a>
+<a name="N100FC"></a><a name="Changes+to+Project+Administration"></a>
 <h3 class="underlined_5">Changes to Project Administration</h3>
 <ul>
 <li>
@@ -635,7 +644,7 @@
         Added testing facilities to plugins to facilitate integration testing. 
       (RDG)</li>
 </ul>
-<a name="N100FC"></a><a name="Changes+to+Build"></a>
+<a name="N10106"></a><a name="Changes+to+Build"></a>
 <h3 class="underlined_5">Changes to Build</h3>
 <ul>
 <li>
@@ -645,7 +654,7 @@
         Ant "import" task.
       (DC)</li>
 </ul>
-<a name="N10106"></a><a name="Changes+to+the+Code+Base-N10106"></a>
+<a name="N10110"></a><a name="Changes+to+the+Code+Base-N10110"></a>
 <h3 class="underlined_5">Changes to the Code Base</h3>
 <ul>
 <li>
@@ -898,7 +907,7 @@
         starting with Forrest-0.7-dev
       (DC)</li>
 </ul>
-<a name="N10278"></a><a name="Changes+to+Documentation-N10278"></a>
+<a name="N10282"></a><a name="Changes+to+Documentation-N10282"></a>
 <h3 class="underlined_5">Changes to Documentation</h3>
 <ul>
 <li>
@@ -988,7 +997,7 @@
         tab</a> to create subject-specific aggregated documents.
       (TS)</li>
 </ul>
-<a name="N10318"></a><a name="Contributors-N10318"></a>
+<a name="N10322"></a><a name="Contributors-N10322"></a>
 <h3 class="underlined_5">Contributors</h3>
 <p>This is a list of all people who have contributed to this release, but 
        were full developers on the project. We thank these people for their 
@@ -1011,10 +1020,10 @@
 </ul>
 </div>
     
-<a name="N1033C"></a><a name="version_0.6"></a>
+<a name="N10346"></a><a name="version_0.6"></a>
 <h2 class="underlined_10">Version 0.6 (2004-10-15)</h2>
 <div class="section">
-<a name="N10340"></a><a name="Changes+to+Project+Administration-N10340"></a>
+<a name="N1034A"></a><a name="Changes+to+Project+Administration-N1034A"></a>
 <h3 class="underlined_5">Changes to Project Administration</h3>
 <ul>
 <li>
@@ -1025,7 +1034,7 @@
         OpenSymphony's OSUser for flexible authentication.
       (DB)</li>
 </ul>
-<a name="N1034A"></a><a name="Changes+to+Build-N1034A"></a>
+<a name="N10354"></a><a name="Changes+to+Build-N10354"></a>
 <h3 class="underlined_5">Changes to Build</h3>
 <ul>
 <li>
@@ -1049,7 +1058,7 @@
         Add more desriptions to forrest targets.  Highlight the most common ones.
       (DB) Fixes <a href="http://issues.apache.org/jira/browse/FOR-216">FOR-216</a>.</li>
 </ul>
-<a name="N10378"></a><a name="Changes+to+the+Code+Base-N10378"></a>
+<a name="N10382"></a><a name="Changes+to+the+Code+Base-N10382"></a>
 <h3 class="underlined_5">Changes to the Code Base</h3>
 <ul>
 <li>
@@ -1379,7 +1388,7 @@
         document2html and site2xhtml XSLs. This allows matches
         defined in the imported transformation sheets to match
         (imported sheets have lower precedence).
-        * Defined a couple of <span class="codefrag ">&lt;div id="..."&gt;</span> place holder
+        * Defined a couple of <span class="codefrag">&lt;div id="..."&gt;</span> place holder
         tags used by the document2html. Those are then skinned by the
         site2xhtml sheets.
         * Note: If you have your own skins that were referencing "$config" or
@@ -1411,8 +1420,8 @@
 <img class="icon" alt="fix" src="../images/fix.jpg">
         Replace document() function to get skinconf values and use "//skinconfig".
         Fix order so it can validate skinconf.
-        Use <span class="codefrag ">&lt;search/&gt;</span> instead of
-        <span class="codefrag ">&lt;disable-search/&gt; &lt;disable-lucene/&gt;
+        Use <span class="codefrag">&lt;search/&gt;</span> instead of
+        <span class="codefrag">&lt;disable-search/&gt; &lt;disable-lucene/&gt;
         &lt;searchsite-domain/&gt; &lt;searchsite-name/&gt;</span>.
         Fix skinconf.xsl so it produces a proper skinconf
       (JJP)</li>
@@ -1794,7 +1803,7 @@
         Sort action types order to "add","remove","update","fix".
       (JJP)</li>
 </ul>
-<a name="N1073D"></a><a name="Changes+to+Documentation-N1073D"></a>
+<a name="N10747"></a><a name="Changes+to+Documentation-N10747"></a>
 <h3 class="underlined_5">Changes to Documentation</h3>
 <ul>
 <li>
@@ -1851,7 +1860,7 @@
         <a href="http://forrest.apache.org/">http://forrest.apache.org/</a>
       (DC)</li>
 </ul>
-<a name="N1079B"></a><a name="Contributors-N1079B"></a>
+<a name="N107A5"></a><a name="Contributors-N107A5"></a>
 <h3 class="underlined_5">Contributors</h3>
 <p>This is a list of all people who have contributed to this release, but 
        were full developers on the project. We thank these people for their 
@@ -1877,10 +1886,10 @@
 </div>
 
     
-<a name="N107C3"></a><a name="version_0.5.1"></a>
+<a name="N107CD"></a><a name="version_0.5.1"></a>
 <h2 class="underlined_10">Version 0.5.1 (2003-10-06)</h2>
 <div class="section">
-<a name="N107C7"></a><a name="Changes+to+Build-N107C7"></a>
+<a name="N107D1"></a><a name="Changes+to+Build-N107D1"></a>
 <h3 class="underlined_5">Changes to Build</h3>
 <ul>
 <li>
@@ -1888,7 +1897,7 @@
         forrest.antproxy.xml script now properly fails when Cocoon fails
       (JT)</li>
 </ul>
-<a name="N107D1"></a><a name="Changes+to+the+Code+Base-N107D1"></a>
+<a name="N107DB"></a><a name="Changes+to+the+Code+Base-N107DB"></a>
 <h3 class="underlined_5">Changes to the Code Base</h3>
 <ul>
 <li>
@@ -1928,10 +1937,10 @@
 </div>
 
     
-<a name="N10812"></a><a name="version_0.5"></a>
+<a name="N1081C"></a><a name="version_0.5"></a>
 <h2 class="underlined_10">Version 0.5 (2003-09-13)</h2>
 <div class="section">
-<a name="N10816"></a><a name="Changes+to+the+Code+Base-N10816"></a>
+<a name="N10820"></a><a name="Changes+to+the+Code+Base-N10820"></a>
 <h3 class="underlined_5">Changes to the Code Base</h3>
 <ul>
 <li>
@@ -1967,9 +1976,9 @@
       (JT)</li>
 <li>
 <img class="icon" alt="add" src="../images/add.jpg">
-        Added a <span class="codefrag ">forrest.maxmemory</span> property specifying the maximum
+        Added a <span class="codefrag">forrest.maxmemory</span> property specifying the maximum
         amount of memory allocated to the JVM. Useful for rendering large PDFs.
-        Added <span class="codefrag ">forrest.jvmargs</span> property for other JVM options.
+        Added <span class="codefrag">forrest.jvmargs</span> property for other JVM options.
       (JT)</li>
 <li>
 <img class="icon" alt="add" src="../images/add.jpg">
@@ -2104,7 +2113,7 @@
 <li>
 <img class="icon" alt="fix" src="../images/fix.jpg">
         Fixed bug where absolute paths to images were created in the
-        <span class="codefrag ">build/site</span> directory.
+        <span class="codefrag">build/site</span> directory.
       (JT)</li>
 <li>
 <img class="icon" alt="fix" src="../images/fix.jpg">
@@ -2124,7 +2133,7 @@
       (JT)</li>
 <li>
 <img class="icon" alt="fix" src="../images/fix.jpg">
-        In <span class="codefrag ">skins/common/xslt/html/tab2menu.xsl</span>, renamed template
+        In <span class="codefrag">skins/common/xslt/html/tab2menu.xsl</span>, renamed template
         'unselected-tab-href' to 'calculate-tab-href', potentially breaking 3rd
         party skins.
       (JT)</li>
@@ -2136,7 +2145,7 @@
 <img class="icon" alt="fix" src="../images/fix.jpg">
         Get images in PDFs working with FOP 0.20.x.  This requires the user to
         download jimi.jar from <a href="http://java.sun.com/products/jimi/">Sun</a> and place it in
-        the <span class="codefrag ">lib/core</span> (src distro) or <span class="codefrag ">WEB-INF/lib</span>
+        the <span class="codefrag">lib/core</span> (src distro) or <span class="codefrag">WEB-INF/lib</span>
         (binary distro) directory.
       (JT)</li>
 <li>
@@ -2147,13 +2156,13 @@
       (NKB)</li>
 <li>
 <img class="icon" alt="fix" src="../images/fix.jpg">
-        Fixed <span class="codefrag ">java.lang.NoClassDefFoundError:
+        Fixed <span class="codefrag">java.lang.NoClassDefFoundError:
           javax/servlet/ServletInputStream</span> error.
       (JT) Thanks to <a href="mailto:cheche.at.che-che.com">Juan Jose Pablos</a>.</li>
 <li>
 <img class="icon" alt="fix" src="../images/fix.jpg">
         Allow users to determine which URLs Forrest should ignore, by overriding
-        <span class="codefrag ">stylesheets/filterlinks.xsl</span> (and other stylesheets in that
+        <span class="codefrag">stylesheets/filterlinks.xsl</span> (and other stylesheets in that
         directory).
       (JT)</li>
 <li>
@@ -2169,7 +2178,7 @@
 <img class="icon" alt="update" src="../images/update.jpg">
         In the forrest-site skin and derivatives, display the author and version at the
         bottom of the page, as krysalis-site does.  Also added parsing for CVS Revision
-        tags, so <span class="codefrag ">&lt;version&gt;$Revision: 1.288 $&lt;/version&gt;</span> can be used.
+        tags, so <span class="codefrag">&lt;version&gt;$Revision: 1.288 $&lt;/version&gt;</span> can be used.
       (JT)</li>
 <li>
 <img class="icon" alt="update" src="../images/update.jpg">
@@ -2225,7 +2234,7 @@
       (JT)</li>
 <li>
 <img class="icon" alt="update" src="../images/update.jpg">
-        Allow any sort of content inside <span class="codefrag ">resources/</span>, which will be
+        Allow any sort of content inside <span class="codefrag">resources/</span>, which will be
         made available to the sitemap but not automatically copied to the
         generated site output.
       (JT)</li>
@@ -2309,7 +2318,7 @@
         the xinclude,  linkrewriter, and idgen steps.
       (NKB)</li>
 </ul>
-<a name="N10A17"></a><a name="Changes+to+Documentation-N10A17"></a>
+<a name="N10A21"></a><a name="Changes+to+Documentation-N10A21"></a>
 <h3 class="underlined_5">Changes to Documentation</h3>
 <ul>
 <li>
@@ -2318,7 +2327,7 @@
         upgrading to v0.5
       (JT)</li>
 </ul>
-<a name="N10A21"></a><a name="Contributors-N10A21"></a>
+<a name="N10A2B"></a><a name="Contributors-N10A2B"></a>
 <h3 class="underlined_5">Contributors</h3>
 <p>This is a list of all people who have contributed to this release, but 
        were full developers on the project. We thank these people for their 
@@ -2335,10 +2344,10 @@
 </ul>
 </div>
     
-<a name="N10A39"></a><a name="version_0.4"></a>
+<a name="N10A43"></a><a name="version_0.4"></a>
 <h2 class="underlined_10">Version 0.4 (2003-02-12)</h2>
 <div class="section">
-<a name="N10A3D"></a><a name="Changes+to+the+Code+Base-N10A3D"></a>
+<a name="N10A47"></a><a name="Changes+to+the+Code+Base-N10A47"></a>
 <h3 class="underlined_5">Changes to the Code Base</h3>
 <ul>
 <li>
@@ -2391,7 +2400,7 @@
       (JT)</li>
 <li>
 <img class="icon" alt="fix" src="../images/fix.jpg">
-        Fix <span class="codefrag ">site:</span> and <span class="codefrag ">ext:</span> rewriting in book.xml,
+        Fix <span class="codefrag">site:</span> and <span class="codefrag">ext:</span> rewriting in book.xml,
         ihtml, ehtml and cwiki files in subdirectories.
       (JT)</li>
 <li>
@@ -2415,7 +2424,7 @@
         Switched all loglevels to ERROR.
       (NKB)</li>
 </ul>
-<a name="N10AA4"></a><a name="Changes+to+Documentation-N10AA4"></a>
+<a name="N10AAE"></a><a name="Changes+to+Documentation-N10AAE"></a>
 <h3 class="underlined_5">Changes to Documentation</h3>
 <ul>
 <li>
@@ -2424,7 +2433,7 @@
         to the forrestbar.xpi generated by Gump every day.
       (NKB)</li>
 </ul>
-<a name="N10AAE"></a><a name="Contributors-N10AAE"></a>
+<a name="N10AB8"></a><a name="Contributors-N10AB8"></a>
 <h3 class="underlined_5">Contributors</h3>
 <p>This is a list of all people who have contributed to this release, but 
        were full developers on the project. We thank these people for their 
@@ -2437,10 +2446,10 @@
 </div>
 
     
-<a name="N10ABC"></a><a name="version_0.3"></a>
+<a name="N10AC6"></a><a name="version_0.3"></a>
 <h2 class="underlined_10">Version 0.3 (2003-01-30)</h2>
 <div class="section">
-<a name="N10AC0"></a><a name="Changes+to+Build-N10AC0"></a>
+<a name="N10ACA"></a><a name="Changes+to+Build-N10ACA"></a>
 <h3 class="underlined_5">Changes to Build</h3>
 <ul>
 <li>
@@ -2455,7 +2464,7 @@
         instead of Cocoon + Centipede logos.
       (JT)</li>
 </ul>
-<a name="N10ACF"></a><a name="Changes+to+the+Code+Base-N10ACF"></a>
+<a name="N10AD9"></a><a name="Changes+to+the+Code+Base-N10AD9"></a>
 <h3 class="underlined_5">Changes to the Code Base</h3>
 <ul>
 <li>
@@ -2465,7 +2474,7 @@
 <li>
 <img class="icon" alt="add" src="../images/add.jpg">
         Added a means to override the check for existing content: 
-        <span class="codefrag ">forrest seed -Dskip.contentcheck=yes</span>
+        <span class="codefrag">forrest seed -Dskip.contentcheck=yes</span>
         Thanks to Tom Klaasen.
       (JT)</li>
 <li>
@@ -2498,51 +2507,51 @@
       (JT)</li>
 <li>
 <img class="icon" alt="add" src="../images/add.jpg">
-        New <span class="codefrag ">site.xml</span> file in content/xdocs.  This is used to
+        New <span class="codefrag">site.xml</span> file in content/xdocs.  This is used to
         implement &lt;link href="site:internalURI"&gt; 'semantic' links,
         &lt;link href="ext:externalURI"&gt; aliases to external links, and
-        renders <span class="codefrag ">book.xml</span> files obsolete.  See <a href="../docs_0_70/linking.html">Menus and Linking</a> for more info.
+        renders <span class="codefrag">book.xml</span> files obsolete.  See <a href="../docs_0_70/linking.html">Menus and Linking</a> for more info.
       (JT)</li>
 <li>
 <img class="icon" alt="fix" src="../images/fix.jpg">
-        If <span class="codefrag ">build/webapp/content/xdocs/*</span> is more recent than
-        <span class="codefrag ">src/*</span> equivalent, <span class="codefrag ">forrest webapp</span> won't clobber
-        it.  A new <span class="codefrag ">forrest backcopy</span> command will copy
-        <span class="codefrag ">build/webapp/content/xdocs</span> content back to
-        <span class="codefrag ">src/documentation/content/xdocs</span>.
+        If <span class="codefrag">build/webapp/content/xdocs/*</span> is more recent than
+        <span class="codefrag">src/*</span> equivalent, <span class="codefrag">forrest webapp</span> won't clobber
+        it.  A new <span class="codefrag">forrest backcopy</span> command will copy
+        <span class="codefrag">build/webapp/content/xdocs</span> content back to
+        <span class="codefrag">src/documentation/content/xdocs</span>.
       (JT)</li>
 <li>
 <img class="icon" alt="fix" src="../images/fix.jpg">
-        <span class="codefrag ">forrest-site</span> skin is now HTML 4.0.1 compliant.  The
+        <span class="codefrag">forrest-site</span> skin is now HTML 4.0.1 compliant.  The
         compliance validator logo can be switched off with a
-        <span class="codefrag ">skinconf.xml</span> element.
+        <span class="codefrag">skinconf.xml</span> element.
       (JT)</li>
 <li>
 <img class="icon" alt="fix" src="../images/fix.jpg">
         Indirectly referenced files in skins (e.g. images in
-        CSS<span class="codefrag ">url()</span>'s) are now copied across to the rendered site.
+        CSS<span class="codefrag">url()</span>'s) are now copied across to the rendered site.
         Previously, we relied on spidering to cover the URI space, which has
         proved insufficient.
       (JT)</li>
 <li>
 <img class="icon" alt="fix" src="../images/fix.jpg">
         HTML fragment identifiers for sections are now meaningfully named, based
-        on the section title, rather than <span class="codefrag ">document-id()</span>-generated
+        on the section title, rather than <span class="codefrag">document-id()</span>-generated
         characters.
       (JT)</li>
 <li>
 <img class="icon" alt="fix" src="../images/fix.jpg">
         Fixed site regeneration bugs where changing the skin in
-        <span class="codefrag ">forrest.properties</span> had no effect after the first build.
+        <span class="codefrag">forrest.properties</span> had no effect after the first build.
       (JT)</li>
 <li>
 <img class="icon" alt="fix" src="../images/fix.jpg">
-        Now all files in <span class="codefrag ">src/documentation/content</span> (except xdocs)
-        and <span class="codefrag ">src/documentation/resources/images</span> are copied across
+        Now all files in <span class="codefrag">src/documentation/content</span> (except xdocs)
+        and <span class="codefrag">src/documentation/resources/images</span> are copied across
         when Forrest generates a static site.  This fixes the problem when an
         unparseable file links to another, and Cocoon can't crawl (and hence
         copy) the linked-to file.  An example of this are CSS
-        <span class="codefrag ">url('foo.png')</span> image refs (so krysalis-site will now work
+        <span class="codefrag">url('foo.png')</span> image refs (so krysalis-site will now work
         properly).  Also, large batches of pregenerated files like Javadocs will
         now be copied across instead of individually traversed.
       (JT)</li>
@@ -2594,13 +2603,13 @@
 <img class="icon" alt="remove" src="../images/remove.jpg">
         Removed some images (built-with-cocoon.gif, centipede-logo-small.gif)
         from the skins, and moved them to
-        <span class="codefrag ">src/documentation/resources/images</span>, as they are
+        <span class="codefrag">src/documentation/resources/images</span>, as they are
         Forrest-specific.
       (JT)</li>
 <li>
 <img class="icon" alt="update" src="../images/update.jpg">
         Lots of FAQ improvements:
-        -Improved URI space by using <span class="codefrag ">@id</span> attributes as the
+        -Improved URI space by using <span class="codefrag">@id</span> attributes as the
             #fragment-identifier for &lt;faq&gt; and &lt;part&gt; elements.
         -Number FAQ entries and categories
         -Added back-links from FAQ entries to the menu
@@ -2686,7 +2695,7 @@
         We need icons for the new buttons.
       (NKB)</li>
 </ul>
-<a name="N10BE5"></a><a name="Changes+to+Documentation-N10BE5"></a>
+<a name="N10BEF"></a><a name="Changes+to+Documentation-N10BEF"></a>
 <h3 class="underlined_5">Changes to Documentation</h3>
 <ul>
 <li>
@@ -2696,7 +2705,7 @@
         Stylesheets not yet done.
       (NKB)</li>
 </ul>
-<a name="N10BEF"></a><a name="Contributors-N10BEF"></a>
+<a name="N10BF9"></a><a name="Contributors-N10BF9"></a>
 <h3 class="underlined_5">Contributors</h3>
 <p>This is a list of all people who have contributed to this release, but 
        were full developers on the project. We thank these people for their 
@@ -2707,10 +2716,10 @@
 </ul>
 </div>
     
-<a name="N10BFB"></a><a name="version_0.2"></a>
+<a name="N10C05"></a><a name="version_0.2"></a>
 <h2 class="underlined_10">Version 0.2 (2002-11-16)</h2>
 <div class="section">
-<a name="N10BFF"></a><a name="Changes+to+the+Code+Base-N10BFF"></a>
+<a name="N10C09"></a><a name="Changes+to+the+Code+Base-N10C09"></a>
 <h3 class="underlined_5">Changes to the Code Base</h3>
 <ul>
 <li>
@@ -2722,7 +2731,7 @@
 <img class="icon" alt="fix" src="../images/fix.jpg">
         Fixed bug where changes to the breadcrumb links in skinconf.xml were
         ignored until the Forrest binary was rebuilt, or the project
-        <span class="codefrag ">build/tmp/</span> deleted.
+        <span class="codefrag">build/tmp/</span> deleted.
       (JT)</li>
 <li>
 <img class="icon" alt="fix" src="../images/fix.jpg">
@@ -2731,10 +2740,10 @@
 </ul>
 </div>
     
-<a name="N10C17"></a><a name="version_0.2rc1"></a>
+<a name="N10C21"></a><a name="version_0.2rc1"></a>
 <h2 class="underlined_10">Version 0.2rc1 (2002-11-13)</h2>
 <div class="section">
-<a name="N10C1B"></a><a name="Changes+to+Project+Administration-N10C1B"></a>
+<a name="N10C25"></a><a name="Changes+to+Project+Administration-N10C25"></a>
 <h3 class="underlined_5">Changes to Project Administration</h3>
 <ul>
 <li>
@@ -2742,7 +2751,7 @@
         Initial Import
       (SM)</li>
 </ul>
-<a name="N10C25"></a><a name="Changes+to+Build-N10C25"></a>
+<a name="N10C2F"></a><a name="Changes+to+Build-N10C2F"></a>
 <h3 class="underlined_5">Changes to Build</h3>
 <ul>
 <li>
@@ -2824,8 +2833,8 @@
 <li>
 <img class="icon" alt="update" src="../images/update.jpg">
         Updated Cocoon to 2.1-dev to use xsltc and new CLI status messages.
-        Logs are in the <span class="codefrag ">build/work/WEB-INF/logs</span> directory and the 
-        list of broken links is in the <span class="codefrag ">build</span> directory.
+        Logs are in the <span class="codefrag">build/work/WEB-INF/logs</span> directory and the 
+        list of broken links is in the <span class="codefrag">build</span> directory.
       (NKB)</li>
 <li>
 <img class="icon" alt="update" src="../images/update.jpg">
@@ -2842,7 +2851,7 @@
         Added basic Forrest descriptor.
       (NKB)</li>
 </ul>
-<a name="N10C93"></a><a name="Changes+to+the+Code+Base-N10C93"></a>
+<a name="N10C9D"></a><a name="Changes+to+the+Code+Base-N10C9D"></a>
 <h3 class="underlined_5">Changes to the Code Base</h3>
 <ul>
 <li>
@@ -2879,12 +2888,12 @@
 <li>
 <img class="icon" alt="add" src="../images/add.jpg">
         XML validation is now fully configurable through a hierarchical set of
-        <span class="codefrag ">forrest.validation.*{includes,excludes,failonerror}</span>
+        <span class="codefrag">forrest.validation.*{includes,excludes,failonerror}</span>
         properties.
       (JT)</li>
 <li>
 <img class="icon" alt="add" src="../images/add.jpg">
-        Validate XSLTs in user skins and <span class="codefrag ">resources/stylesheets</span>
+        Validate XSLTs in user skins and <span class="codefrag">resources/stylesheets</span>
         directories.
       (JT)</li>
 <li>
@@ -2958,7 +2967,7 @@
       (JT)</li>
 <li>
 <img class="icon" alt="fix" src="../images/fix.jpg">
-        Allow <span class="codefrag ">xml:space='preserve'</span> attribute on &lt;p&gt; element, which preserves
+        Allow <span class="codefrag">xml:space='preserve'</span> attribute on &lt;p&gt; element, which preserves
         space without the changed font and block display that &lt;code&gt; uses.
       (JT)</li>
 <li>
@@ -2990,7 +2999,7 @@
         Put the internal matches in a separate pipeline with internal-only="true".
       (NKB)</li>
 </ul>
-<a name="N10D4E"></a><a name="Changes+to+Design"></a>
+<a name="N10D58"></a><a name="Changes+to+Design"></a>
 <h3 class="underlined_5">Changes to Design</h3>
 <ul>
 <li>
@@ -2999,7 +3008,7 @@
         cross-browser issues.
       (BK)</li>
 </ul>
-<a name="N10D58"></a><a name="Changes+to+Documentation-N10D58"></a>
+<a name="N10D62"></a><a name="Changes+to+Documentation-N10D62"></a>
 <h3 class="underlined_5">Changes to Documentation</h3>
 <ul>
 <li>
@@ -3010,7 +3019,7 @@
 <li>
 <img class="icon" alt="add" src="../images/add.jpg">
         Allow user to specify what XML files to validate via
-        <span class="codefrag ">forrest.validate.{includes,excludes}</span> properties.
+        <span class="codefrag">forrest.validate.{includes,excludes}</span> properties.
       (JT)</li>
 <li>
 <img class="icon" alt="add" src="../images/add.jpg">
@@ -3087,7 +3096,7 @@
         validated using these DTDs and OASIS Catalogs.
       (DC) Thanks to <a href="mailto:stevenn.at.outerthought.org">Steven Noels</a>.</li>
 </ul>
-<a name="N10DC1"></a><a name="Contributors-N10DC1"></a>
+<a name="N10DCB"></a><a name="Contributors-N10DCB"></a>
 <h3 class="underlined_5">Contributors</h3>
 <p>This is a list of all people who have contributed to this release, but 
        were full developers on the project. We thank these people for their 
@@ -3103,7 +3112,7 @@
 </ul>
 </div>
   
-<a name="N10DD7"></a><a name="Committers"></a>
+<a name="N10DE1"></a><a name="Committers"></a>
 <h2 class="underlined_10">Committers</h2>
 <div class="section">
 <p>This is a list of all people who have been 

Modified: forrest/site/docs_0_60/changes.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_60/changes.pdf?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
Binary files - no diff available.

Modified: forrest/site/docs_0_60/changes.rss
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_60/changes.rss?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_60/changes.rss (original)
+++ forrest/site/docs_0_60/changes.rss Sun Dec 18 17:31:25 2005
@@ -48,7 +48,24 @@
         Added document to facilitate
         upgrading to v0.8
       </description></item>
+      
+      <item><title>code add</title><link>changes.html</link><description>code add
+        by
+        TS
+        :
+         New protocol / source factory 
+        that is contacting the locationmap module to look up the source. Use it 
+        like lm://resolve.contract.html.content-main for source resolving. 
+        </description></item>
         
+      <item><title>code add</title><link>changes.html</link><description>code add
+        by
+        TS
+        :
+         Added first implementation of 
+        the dispatcher. Including contract bean implementation and interface; 
+        dispatcher exception and dispatcher transformers. </description></item>
+      
       <item><title>code update</title><link>changes.html</link><description>code update
         by
         DC
@@ -4267,7 +4284,20 @@
 
         Added document to facilitate
         upgrading to v0.8
-      </description></item><item><title>code update</title><link>changes.html</link><description>code update
+      </description></item><item><title>code add</title><link>changes.html</link><description>code add
+        by
+        TS
+        :
+         New protocol / source factory 
+        that is contacting the locationmap module to look up the source. Use it 
+        like lm://resolve.contract.html.content-main for source resolving. 
+        </description></item><item><title>code add</title><link>changes.html</link><description>code add
+        by
+        TS
+        :
+         Added first implementation of 
+        the dispatcher. Including contract bean implementation and interface; 
+        dispatcher exception and dispatcher transformers. </description></item><item><title>code update</title><link>changes.html</link><description>code update
         by
         DC
         :

Modified: forrest/site/docs_0_60/compliance.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_60/compliance.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_60/compliance.html (original)
+++ forrest/site/docs_0_60/compliance.html Sun Dec 18 17:31:25 2005
@@ -311,11 +311,11 @@
         unless the user has turned this off.
       </p>
 <p>
-        The "<span class="codefrag ">crust</span>" skin (current forrest-0.6-dev)
+        The "<span class="codefrag">crust</span>" skin (current forrest-0.6-dev)
         validates as HTML 4.0.1
       </p>
 <p>
-        The "<span class="codefrag ">tigris</span>" skin (current forrest-0.6-dev)
+        The "<span class="codefrag">tigris</span>" skin (current forrest-0.6-dev)
         validates as HTML 4.0.1
       </p>
 </div> 

Modified: forrest/site/docs_0_60/faq.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_60/faq.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_60/faq.html (original)
+++ forrest/site/docs_0_60/faq.html Sun Dec 18 17:31:25 2005
@@ -568,14 +568,14 @@
          files), see the second paragraph.
         </p>
 <p>
-         The <span class="codefrag ">maxmemory</span> property in the <span class="codefrag ">forrest.properties</span> file controls how much
+         The <span class="codefrag">maxmemory</span> property in the <span class="codefrag">forrest.properties</span> file controls how much
          memory Cocoon uses. Like many other properties you can copy them from the default configuration at
-         <span class="codefrag ">src/core/fresh-site/forrest.properties</span>
+         <span class="codefrag">src/core/fresh-site/forrest.properties</span>
         
 </p>
 <p>
-         Set the <span class="codefrag ">ANT_OPTS</span> environment variable before you run forrest.  The exact value you set
-         it to is dependant on your JVM, but something like <span class="codefrag ">ANT_OPTS=-Xmx500M</span> will probably work.
+         Set the <span class="codefrag">ANT_OPTS</span> environment variable before you run forrest.  The exact value you set
+         it to is dependant on your JVM, but something like <span class="codefrag">ANT_OPTS=-Xmx500M</span> will probably work.
         </p>
 </div>
 <a name="N1007E"></a><a name="technical"></a>
@@ -613,7 +613,7 @@
 <a href="#clickable-email-adress-menu">^</a>
 </div>
 <div style="margin-left: 15px">
-<p>You would override <span class="codefrag ">
+<p>You would override <span class="codefrag">
        src/core/context/skins/common/xslt/html/document2html.xsl</span>
        and edit the "headers/authors" template.
        </p>
@@ -625,7 +625,7 @@
 <a href="#CVS_revison_tags-menu">^</a>
 </div>
 <div style="margin-left: 15px">
-<p>If you have:<span class="codefrag ">&lt;version&gt;$Revision: 1.30
+<p>If you have:<span class="codefrag">&lt;version&gt;$Revision: 1.30
       $&lt;/version&gt;</span>The '1.30' will be extracted and
       displayed at the bottom of the page as "version 1.30". See for
       example the bottom of the
@@ -643,13 +643,13 @@
 </div>
 <div style="margin-left: 15px">
 <p>
-          This can be done by overriding the <span class="codefrag ">cli.xconf</span> config file,
+          This can be done by overriding the <span class="codefrag">cli.xconf</span> config file,
           and defining patterns for URLs to exclude.
         </p>
 <p>
-          This means creating a directory <span class="codefrag ">src/documentation/conf</span>
-          (or wherever <span class="codefrag ">${forrest.conf-dir}</span> points) and copying
-          <span class="codefrag ">$FORREST_HOME/context/WEB-INF/cli.xconf</span> to it.  Then edit
+          This means creating a directory <span class="codefrag">src/documentation/conf</span>
+          (or wherever <span class="codefrag">${forrest.conf-dir}</span> points) and copying
+          <span class="codefrag">$FORREST_HOME/context/WEB-INF/cli.xconf</span> to it.  Then edit
           cli.xconf, and add any exclude sections you require at the end.  The
           default cli.xconf ignores directory links and links containing
           'apidocs' or starting with 'api/':
@@ -672,7 +672,7 @@
           Wildcards may be used.  These are a powerful feature of Cocoon's
           <a href="../docs_0_60/sitemap-ref.html">sitemap</a>.
           For example, <strong>foo/*</strong> would match
-          <span class="codefrag ">foo/bar</span>, but not <span class="codefrag ">foo/bar/baz</span>
+          <span class="codefrag">foo/bar</span>, but not <span class="codefrag">foo/bar/baz</span>
            &mdash; use <strong>foo/**</strong> to match that.
         </div>
 </div>
@@ -685,7 +685,7 @@
 </div>
 <div style="margin-left: 15px">
 <p>
-          Place them in the <span class="codefrag ">src/documentation/content</span> directory
+          Place them in the <span class="codefrag">src/documentation/content</span> directory
           and they will get copied into the output tree where you can link to
           them. You can also have sub-directories there to reflect your xdocs
           tree. See the samples documents when you 'forrest seed' a new
@@ -693,10 +693,10 @@
         </p>
 <p>
          For example, if
-         <span class="codefrag ">src/documentation/content/xdocs/tools/downloads.xml</span>
-         has a <span class="codefrag ">&lt;link href="tool.zip"&gt;</span> then put
-         <span class="codefrag ">tool.zip</span> in the
-         <span class="codefrag ">src/documentation/content/tools/</span> directory.
+         <span class="codefrag">src/documentation/content/xdocs/tools/downloads.xml</span>
+         has a <span class="codefrag">&lt;link href="tool.zip"&gt;</span> then put
+         <span class="codefrag">tool.zip</span> in the
+         <span class="codefrag">src/documentation/content/tools/</span> directory.
         </p>
 <p>
           See the explanation and demonstration of "linking" in your local
@@ -714,7 +714,7 @@
 <p>
           Certain patterns are claimed by the default sitemaps for
           special processing. These include:
-          <span class="codefrag ">site, changes, todo, faq, images, my-images, skinconf,
+          <span class="codefrag">site, changes, todo, faq, images, my-images, skinconf,
           community, howto</span>
         
 </p>
@@ -771,7 +771,7 @@
 </li>
           
 <li>Unpack the Jimi distribution and copy JimiProClasses.zip to
-            <span class="codefrag ">$FORREST/lib/optional/jimi-1.0.jar</span>.</li>
+            <span class="codefrag">$FORREST/lib/optional/jimi-1.0.jar</span>.</li>
         
 </ol>
 <p>Alternatively you can use JAI (Java Advanced Imaging API at 
@@ -797,11 +797,11 @@
 </div>
 <div style="margin-left: 15px">
 <p>
-          In <span class="codefrag ">tabs.xml</span>, use @href instead of @dir, and omit the
+          In <span class="codefrag">tabs.xml</span>, use @href instead of @dir, and omit the
           trailing '/'. Which file to serve is then a concern of the sitemap.
           For example, if the "User Manual" tab should link to
-          <span class="codefrag ">manual/Introduction.html</span> then
-          <span class="codefrag ">tabs.xml</span> should contain:
+          <span class="codefrag">manual/Introduction.html</span> then
+          <span class="codefrag">tabs.xml</span> should contain:
         </p>
 <pre class="code">
   &lt;tab label="User Manual" href="manual"/&gt;</pre>
@@ -823,8 +823,8 @@
 <div style="margin-left: 15px">
 <p>
           If you are using JDK 1.4.0 or newer, you can enable <em>headless</em>
-          operation by running Forrest with the <span class="codefrag ">forrest.jvmarg</span>
-          parameter set to <span class="codefrag ">-Djava.awt.headless=true</span>, like this:
+          operation by running Forrest with the <span class="codefrag">forrest.jvmarg</span>
+          parameter set to <span class="codefrag">-Djava.awt.headless=true</span>, like this:
         </p>
 <pre class="code">forrest -Dforrest.jvmargs=-Djava.awt.headless=true site</pre>
 <p>
@@ -858,8 +858,8 @@
 <p>
         Use the numeric values for character entities.
         For example, rather than using
-        <span class="codefrag ">&amp;ouml;</span> use
-        <span class="codefrag ">&amp;#246;</span>
+        <span class="codefrag">&amp;ouml;</span> use
+        <span class="codefrag">&amp;#246;</span>
         
 </p>
 <p>
@@ -944,7 +944,7 @@
 </div>
 <div style="margin-left: 15px">
 <p>Breadcrumbs begin with up to three URLs specified in
-      <span class="codefrag ">skinconf.xml</span>.  Here is what the Forrest site uses:</p>
+      <span class="codefrag">skinconf.xml</span>.  Here is what the Forrest site uses:</p>
 <pre class="code">
   &lt;trail&gt;
     &lt;link1 name="apache" href="http://www.apache.org/"/&gt;
@@ -956,7 +956,7 @@
       makes a link for each directory after the domain.  If you are viewing
       the site locally, there is no domain and so
       there will be no extra breadcrumbs, only the ones that are specified
-      in <span class="codefrag ">skinconf.xml</span>.
+      in <span class="codefrag">skinconf.xml</span>.
       </p>
 </div>
 <a name="N1020E"></a><a name="old_faqs"></a>
@@ -971,7 +971,7 @@
 </div>
 <div style="margin-left: 15px">
 <p>This is a bug in 0.4. The following modification to
-          <span class="codefrag ">FORREST_HOME/forrest.antproxy.xml</span> should fix it:</p>
+          <span class="codefrag">FORREST_HOME/forrest.antproxy.xml</span> should fix it:</p>
 <pre class="code">--- forrest.antproxy.xml        7 Feb 2003 22:21:15 -0000       1.2
 +++ forrest.antproxy.xml        22 Feb 2003 09:39:42 -0000
 @@ -41,6 +41,7 @@
@@ -993,7 +993,7 @@
 </div>
 <div style="margin-left: 15px">
 <p>
-          Forrest now uses a HTML 4.0.1 <span class="codefrag ">DOCTYPE</span> declaration:</p>
+          Forrest now uses a HTML 4.0.1 <span class="codefrag">DOCTYPE</span> declaration:</p>
 <pre class="code">
 &lt;!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
   "http://www.w3.org/TR/html4/loose.dtd"&gt;</pre>
@@ -1018,14 +1018,14 @@
 <p>
           You are probably trying to build the project with an old version of
           Forrest (built before 2003-01-08) that is incorrectly trying to validate
-          the <span class="codefrag ">site.xml</span> file.  If so, please update your Forrest
+          the <span class="codefrag">site.xml</span> file.  If so, please update your Forrest
           installation.
         </p>
 <p>
           Alternatively, you may be building with an up-to-date Forrest, but have
-          overridden <span class="codefrag ">forrest.validate.xdocs.excludes</span> in
-          <span class="codefrag ">forrest.properties</span>.  With the introduction of
-          <span class="codefrag ">site.xml</span>, the above property must have <span class="codefrag ">site.xml</span>
+          overridden <span class="codefrag">forrest.validate.xdocs.excludes</span> in
+          <span class="codefrag">forrest.properties</span>.  With the introduction of
+          <span class="codefrag">site.xml</span>, the above property must have <span class="codefrag">site.xml</span>
           listed to prevent an attempt at DTD-based validation.
         </p>
 </div>
@@ -1056,13 +1056,13 @@
 </div>
 <div style="margin-left: 15px">
 <p>
-          One <span class="codefrag ">site.xml</span> file in your project root can replace all the book.xml files
-          (one per directory) in your site.  Internally, Forrest uses <span class="codefrag ">site.xml</span> to
+          One <span class="codefrag">site.xml</span> file in your project root can replace all the book.xml files
+          (one per directory) in your site.  Internally, Forrest uses <span class="codefrag">site.xml</span> to
           dynamically generate book.xml files.  However, Forrest first checks
           for the existence of a book.xml file, so backwards-compatibility is
           preserved.  If a directory has a book.xml file, the book.xml will be
           used to generate the menu.  This supplement is useful in situations
-          where <span class="codefrag ">site.xml</span>-generated menus aren't appropriate.
+          where <span class="codefrag">site.xml</span>-generated menus aren't appropriate.
           See <a href="../docs_0_60/linking.html">Menus and Linking</a>.
       </p>
 </div>
@@ -1134,13 +1134,13 @@
 </div>
 <div style="margin-left: 15px">
 <p>
-          Do <span class="codefrag ">'forrest -projecthelp'</span> or <span class="codefrag ">'./build.sh'</span>
+          Do <span class="codefrag">'forrest -projecthelp'</span> or <span class="codefrag">'./build.sh'</span>
           to find the version number.
         </p>
 <p>
           To list the properties, add "forrest.echo=true" to your
           forrest.properties file and watch the build messages.
-          Doing <span class="codefrag ">'forrest -v'</span> will provide verbose build messages.
+          Doing <span class="codefrag">'forrest -v'</span> will provide verbose build messages.
         </p>
 </div>
 <a name="N102BF"></a><a name="logs"></a>
@@ -1152,23 +1152,23 @@
 </div>
 <div style="margin-left: 15px">
 <p>
-          The logfiles are at <span class="codefrag ">build/webapp/WEB-INF/logs/</span>
+          The logfiles are at <span class="codefrag">build/webapp/WEB-INF/logs/</span>
         
 </p>
 <p>
-          The log level can be raised with the <span class="codefrag ">logkit.xconf</span>
+          The log level can be raised with the <span class="codefrag">logkit.xconf</span>
           configuration. If you are using Forrest in the interactive webapp
           mode (which is generally easiest for debugging errors) then see the
-          <span class="codefrag ">build/webapp/WEB-INF/logkit.xconf</span> file.
+          <span class="codefrag">build/webapp/WEB-INF/logkit.xconf</span> file.
           If you are generating a static site (with command-line 'forrest')
-          then copy <span class="codefrag ">$FORREST_HOME/context/WEB-INF/logkit.xconf</span>
+          then copy <span class="codefrag">$FORREST_HOME/context/WEB-INF/logkit.xconf</span>
           to your project at
-          <span class="codefrag ">src/documentation/content/conf/logkit.xconf</span>
+          <span class="codefrag">src/documentation/content/conf/logkit.xconf</span>
           and modify it. See more information and efficiency tips with
           <a href="http://wiki.apache.org/cocoon/ExploringTheLogs">Cocoon logging</a>.
         </p>
 <p>
-          Doing <span class="codefrag ">'forrest -v'</span> will provide verbose build messages
+          Doing <span class="codefrag">'forrest -v'</span> will provide verbose build messages
           to the standard output.
         </p>
 </div>

Modified: forrest/site/docs_0_60/forrest-contract.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_60/forrest-contract.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_60/forrest-contract.html (original)
+++ forrest/site/docs_0_60/forrest-contract.html Sun Dec 18 17:31:25 2005
@@ -303,10 +303,10 @@
 <div class="note">
 <div class="label">Note</div>
 <div class="content">
-      Some terminology will assist: <span class="codefrag ">{docroot}</span> is the location
+      Some terminology will assist: <span class="codefrag">{docroot}</span> is the location
       inside TheProject's file hierarchy where all documentation related
-      resources are stored. Usually <span class="codefrag ">{docroot}</span> equals to
-      <span class="codefrag ">{projecthome}/src/documentation</span>
+      resources are stored. Usually <span class="codefrag">{docroot}</span> equals to
+      <span class="codefrag">{projecthome}/src/documentation</span>
     
 </div>
 </div> 
@@ -339,17 +339,17 @@
 <p>Provide content and configuration ...</p>
 <ul> 
         
-<li>Provide XML content in <span class="codefrag ">{docroot}/content/xdocs</span>
+<li>Provide XML content in <span class="codefrag">{docroot}/content/xdocs</span>
           according to the Forrest DTDs or one of the other input formats.
         </li> 
         
 <li>Provide navigation metadata using the configuration files
-          <span class="codefrag ">site.xml</span> and <span class="codefrag ">tabs.xml</span>
+          <span class="codefrag">site.xml</span> and <span class="codefrag">tabs.xml</span>
         
 </li>
         
 <li>Provide the skin configuation file in
-          <span class="codefrag ">{projecthome}/skinconf.xml</span>
+          <span class="codefrag">{projecthome}/skinconf.xml</span>
         
 </li>
       
@@ -364,13 +364,13 @@
 <ul> 
         
 <li>Provide its own skin in
-          <span class="codefrag ">{docroot}/skins/{your-skin-name}</span> (Check the current
+          <span class="codefrag">{docroot}/skins/{your-skin-name}</span> (Check the current
           Forrest skins and the related pipelines to see what they are doing.
           Bear in mind that the provided skins are able to be configured and
           may already meet your needs.)</li> 
         
 <li>Provide own DTDs to handle other specialised document types in
-          <span class="codefrag ">{docroot}/resources/schema/dtd</span> 
+          <span class="codefrag">{docroot}/resources/schema/dtd</span> 
           
 <ul> 
             
@@ -378,7 +378,7 @@
               intermediate 'document' structure.</li> 
             
 <li>and declare those extra DTDs in
-              <span class="codefrag ">{docroot}/resources/schema/catalog.xcat</span>
+              <span class="codefrag">{docroot}/resources/schema/catalog.xcat</span>
 </li> 
           
 </ul>
@@ -386,7 +386,7 @@
 </li> 
         
 <li>Provide its own overwriting versions of sitemaps
-          (<span class="codefrag ">{docroot}/sitemap.xmap</span> and other *.xmap files)
+          (<span class="codefrag">{docroot}/sitemap.xmap</span> and other *.xmap files)
           ... (be sure you know what you are doing since you are then leaving
           the area where other Forresters can help you out.
         </li> 

Modified: forrest/site/docs_0_60/howto/bugzilla-patch/howto-bugzilla-patch.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_60/howto/bugzilla-patch/howto-bugzilla-patch.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_60/howto/bugzilla-patch/howto-bugzilla-patch.html (original)
+++ forrest/site/docs_0_60/howto/bugzilla-patch/howto-bugzilla-patch.html Sun Dec 18 17:31:25 2005
@@ -327,7 +327,7 @@
 <h4>Specify Version</h4>
 <p>
 This is the version of Cocoon that you prepared your patch against. Choose
-<span class="codefrag ">Current CVS</span> if you have an up-to-date local working copy
+<span class="codefrag">Current CVS</span> if you have an up-to-date local working copy
 of HEAD branch or a very recent nightly build. Otherwise choose the relevant
 release version. This is a very important step, as you will confuse the
 committer if your changes do not match the repository. If you are unsure, then
@@ -338,53 +338,53 @@
 <p>
 Follow the "Component" link for description of the available
 components. If you do not know which component is relevant, then just use
-<span class="codefrag ">core</span>.
+<span class="codefrag">core</span>.
 </p>
 <a name="N10072"></a><a name="Specify+Platform"></a>
 <h4>Specify Platform</h4>
 <p>
 This is really meant for bug reporting. Perhaps it could be relevant for a
-patch. You would usually specify the <span class="codefrag ">All</span> option.
+patch. You would usually specify the <span class="codefrag">All</span> option.
 </p>
 <a name="N1007F"></a><a name="Specify+Operating+System+%28OS%29"></a>
 <h4>Specify Operating System (OS)</h4>
 <p>
 Really meant for bug reporting. Perhaps it could be relevant for a patch.
-You would usually specify the <span class="codefrag ">All</span> option.
+You would usually specify the <span class="codefrag">All</span> option.
 </p>
 <a name="N1008C"></a><a name="Specify+Severity"></a>
 <h4>Specify Severity</h4>
 <p>
 The impact that would arise if your patch is not applied. For a documentation
-patch, the severity would usually be the default <span class="codefrag ">Normal</span>.
+patch, the severity would usually be the default <span class="codefrag">Normal</span>.
 However, if it addressed some serious lack or fixed a misguided configuration
-statement, then the impact could be <span class="codefrag ">major</span>.
+statement, then the impact could be <span class="codefrag">major</span>.
 </p>
 <p>
 <!--FIXME: (DS) Why include this if it isn't recommended for a patch? -->
 <!--       (DC) To try to discourage them from using it. Does it need
 better words? -->
-(The <span class="codefrag ">enhancement</span> option would not be used for a patch, as it is
+(The <span class="codefrag">enhancement</span> option would not be used for a patch, as it is
 intended for suggesting something that should be done. Use this option wisely.
 It would be better to discuss it on the mailing list first.)
 </p>
 <a name="N100A6"></a><a name="Specify+Initial+State"></a>
 <h4>Specify Initial State</h4>
 <p>
-Use the <span class="codefrag ">New</span> option.
+Use the <span class="codefrag">New</span> option.
 </p>
 <a name="N100B3"></a><a name="Specify+Assigned+To"></a>
 <h4>Specify Assigned To</h4>
 <p>
 Leave it blank. Your patch will be automatically assigned to the
-<span class="codefrag ">cocoon-dev</span> mailing list. When a committer takes on your patch,
+<span class="codefrag">cocoon-dev</span> mailing list. When a committer takes on your patch,
 that committer will assign the bug to their own email address. This pevents
 duplication of effort by other committers.
 </p>
 <p>
 The Cc field can be used if you need the bug reports, and any follow-up, to be
 copied to some other person. Remember that your report will be sent
-automatically to the <span class="codefrag ">cocoon-dev</span> mailing list, so you do not need
+automatically to the <span class="codefrag">cocoon-dev</span> mailing list, so you do not need
 to Cc anyone there.
 </p>
 <a name="N100C6"></a><a name="Specify+URL"></a>
@@ -403,7 +403,7 @@
 Use up all the characters available ... about 60 maximum.
 </p>
 <p>
-Start the Summary with the <span class="codefrag ">[PATCH]</span> tag. This will ensure that it
+Start the Summary with the <span class="codefrag">[PATCH]</span> tag. This will ensure that it
 is included in the Cocoon automated patch queue summary posted to the mailing
 lists. The patch queue summary reminds people what patches are pending. If you
 omit this tag, then your patch may easily be overlooked.
@@ -431,7 +431,7 @@
 <p>
 Review your options, then press the <strong>Commit</strong> button. This will
 add an entry to the bug database and email a report to the 
-<span class="codefrag ">cocoon-dev</span> mailing list and a copy to you. Your submission will be
+<span class="codefrag">cocoon-dev</span> mailing list and a copy to you. Your submission will be
 assigned a unique Bug Number which you can use to review its progress.
 </p>
 <p>
@@ -442,7 +442,7 @@
 <h3 class="underlined_5">4. Create an attachment of the actual patch</h3>
 <p>
 You will be presented with a status screen saying that your bug report
-was accepted and that email was sent to <span class="codefrag ">cocoon-dev</span> mailing list.
+was accepted and that email was sent to <span class="codefrag">cocoon-dev</span> mailing list.
 </p>
 <p>
 Now you have a choice ... proceed to review your bug report by selecting the
@@ -456,32 +456,32 @@
 <h4>Specify the file to be uploaded</h4>
 <p>
 Provide the local pathname to your patchfile, e.g.
-<span class="codefrag ">/home/me/work/cocoon/patch/howto-bugzilla.tar.gz</span>
+<span class="codefrag">/home/me/work/cocoon/patch/howto-bugzilla.tar.gz</span>
 
 </p>
 <a name="N10122"></a><a name="Describe+the+attachment"></a>
 <h4>Describe the attachment</h4>
 <p>
 Provide a concise one line description, e.g.
-<span class="codefrag ">Gzipped TAR archive with new docs and diffs</span>
+<span class="codefrag">Gzipped TAR archive with new docs and diffs</span>
 
 </p>
 <a name="N1012F"></a><a name="Specify+the+contentType+of+the+attachment"></a>
 <h4>Specify the contentType of the attachment</h4>
 <p>
 If it is a Gzipped TAR archive (*.tar.gz) or a .zip archive, then select
-"<span class="codefrag ">Binary file (application/octet-stream)</span>".
+"<span class="codefrag">Binary file (application/octet-stream)</span>".
 If it is just a single xml document, then select
-"<span class="codefrag ">Plain text (text/plain)</span>".
+"<span class="codefrag">Plain text (text/plain)</span>".
 If the patch is just a single diff file, then select
-"<span class="codefrag ">Patch file (text/plain, diffs)</span>".
+"<span class="codefrag">Patch file (text/plain, diffs)</span>".
 </p>
 <a name="N10143"></a><a name="5.+Submit+the+attachment"></a>
 <h3 class="underlined_5">5. Submit the attachment</h3>
 <p>
 When you are ready, press the <strong>Submit</strong> button. As for Step 3,
 you will be presented with a status screen saying that your attachment
-was accepted and that email was sent to <span class="codefrag ">cocoon-dev</span> mailing list.
+was accepted and that email was sent to <span class="codefrag">cocoon-dev</span> mailing list.
 </p>
 <a name="N10153"></a><a name="6.+Be+patient"></a>
 <h3 class="underlined_5">6. Be patient</h3>

Modified: forrest/site/docs_0_60/howto/howto-asf-mirror.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_60/howto/howto-asf-mirror.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_60/howto/howto-asf-mirror.html (original)
+++ forrest/site/docs_0_60/howto/howto-asf-mirror.html Sun Dec 18 17:31:25 2005
@@ -365,10 +365,10 @@
 <h3 class="underlined_5">Add the mirrors.cgi as a raw file</h3>
 <p>As explained in the mirrors document, there will be a two-line CGI
       wrapper script at the top-level of your website called
-      <span class="codefrag ">mirrors.cgi</span>
+      <span class="codefrag">mirrors.cgi</span>
 </p>
 <p>Utilising the Forrest concept of raw un-processed content,
-       add the file as <span class="codefrag ">src/documentation/mirrors.cgi</span>
+       add the file as <span class="codefrag">src/documentation/mirrors.cgi</span>
        (copy the Forrest project's
         <a href="http://svn.apache.org/repos/asf/forrest/trunk/src/documentation/content/mirrors.cgi">mirrors.cgi</a>)
       </p>
@@ -380,7 +380,7 @@
         script to add the list of mirrors and select the closest.
       </p>
 <p>
-        Add the file as <span class="codefrag ">src/documentation/xdocs/mirrors.html</span>
+        Add the file as <span class="codefrag">src/documentation/xdocs/mirrors.html</span>
         (Use the Forrest project's
         <a href="http://svn.apache.org/repos/asf/forrest/trunk/src/documentation/content/xdocs/mirrors.ihtml">mirrors.html</a>
         as a template and edit it to suit.)
@@ -407,8 +407,8 @@
         (<a href="http://cocoon.apache.org/2.1/userdocs/offline/">CLI</a>)
         to the rescue. Add an entry to your project's cli.xconf by copying the
         default one from
-        <span class="codefrag ">$FORREST_HOME/context/WEB-INF/cli.xconf</span> to your
-        <span class="codefrag ">src/documentation/conf/</span> directory (or wherever
+        <span class="codefrag">$FORREST_HOME/context/WEB-INF/cli.xconf</span> to your
+        <span class="codefrag">src/documentation/conf/</span> directory (or wherever
         ${forrest.conf-dir} points). Add the following entry ...
       </p>
 <pre class="code">
@@ -419,7 +419,7 @@
 <h3 class="underlined_5">Run 'forrest' to build your site</h3>
 <p>
         That is all that you need to do, Forrest will take care of it from
-        there. Run the '<span class="codefrag ">forrest</span>' command. The mirrors.html page
+        there. Run the '<span class="codefrag">forrest</span>' command. The mirrors.html page
         will be generated with the skin applied.
       </p>
 <a name="N100A7"></a><a name="explain"></a>

Modified: forrest/site/docs_0_60/howto/howto-howto.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_60/howto/howto-howto.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_60/howto/howto-howto.html (original)
+++ forrest/site/docs_0_60/howto/howto-howto.html Sun Dec 18 17:31:25 2005
@@ -389,7 +389,7 @@
       
 <li>An understanding of the How-To document structure. Just use this
       template document and you will be safe.
-      Make sure you run '<span class="codefrag ">forrest validate-xdocs</span>' before
+      Make sure you run '<span class="codefrag">forrest validate-xdocs</span>' before
       contributing your document.</li>
     
 </ul>



Mime
View raw message