Mailing List Archive

svn commit: r1551469 - in /forrest/site: docs_0_100/faq.html docs_0_100/faq.xml dtdx/document-v13.pdf dtdx/document-v20.pdf
Author: crossley
Date: Tue Dec 17 06:21:49 2013
New Revision: 1551469

URL: http://svn.apache.org/r1551469
Log:
Publish from forrestbot

Modified:
forrest/site/docs_0_100/faq.html
forrest/site/docs_0_100/faq.xml
forrest/site/dtdx/document-v13.pdf
forrest/site/dtdx/document-v20.pdf

Modified: forrest/site/docs_0_100/faq.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_100/faq.html?rev=1551469&r1=1551468&r2=1551469&view=diff
==============================================================================
--- forrest/site/docs_0_100/faq.html (original)
+++ forrest/site/docs_0_100/faq.html Tue Dec 17 06:21:49 2013
@@ -1782,15 +1782,15 @@ X [0] /docs_0_80/upgrading_08.ht
That is easily added directly to your project sitemap for any
special processing.
However for many cases it needs to be added to the main
- webapp/sitemap.xmap file.
+ <span class="codefrag">webapp/sitemap.xmap</span> file.
</p>
<p>
- Do this by adding a "handle-errors" xml entity to your project
+ Do this by adding a "sitemap-handle-errors" xml entity to your project
"symbols" file (<a href="#sitemap-entities">explained above</a>).
For example:
</p>
<pre class="code">
-&lt;!ENTITY handle-errors '
+&lt;!ENTITY sitemap-handle-errors '
&lt;map:handle-errors&gt;
&lt;map:select type="exception"&gt;
&lt;map:when test="resourceNotFound"&gt;
@@ -1804,9 +1804,37 @@ X [0] /docs_0_80/upgrading_08.ht
&lt;/map:handle-errors&gt;
'&gt;</pre>
<p>
- Some exception selectors are configured in webapp/sitemap.xmap file
- at the "map:selectors" section.
- Please send patches for others if you need them to be added.
+ Some exception selectors are already configured in Forrest's main
+ <span class="codefrag">webapp/sitemap.xmap</span> file at the "map:selectors" section.
+ There is a mechanism for declaring more selectors for your project.
+ As above, add a "sitemap-selectors" xml entity to your project "symbols" file.
+ For this example, we demonstrate using an extra file for the snippet content.
+ </p>
+<pre class="code">
+&lt;!ENTITY sitemap-selectors SYSTEM "sitemap-selectors.xml"&gt;</pre>
+<p>
+ The file will be found relative to your project "symbols" file that declared it.
+ (If you need to hold a common set of such files elsewhere, then the
+ project Catalog Entity Resolver could be configured.)
+ So here is an example "sitemap-selectors" snippet to configure the XPathExceptionSelector
+ to declare other exception names for use in a more comprehensive
+ "map:handle-errors" section:
+ </p>
+<pre class="code">
+&lt;map:selector name="exception2" src="org.apache.cocoon.selection.XPathExceptionSelector"&gt;
+ &lt;exception name="transformer2" class="javax.xml.transform.TransformerException" unroll="true"&gt;
+ &lt;xpath name="goofer2" test="message='The identifier is not allowed.'"/&gt;
+ &lt;/exception&gt;
+ &lt;exception class="java.lang.Throwable" unroll="true"/&gt;
+&lt;/map:selector&gt;</pre>
+<p>
+ The "message" text is issued from a stylesheet-directed termination
+ via <span class="codefrag">&lt;xsl:message terminate="yes"&gt;</span>
+
+</p>
+<p>
+ This file-based entity is a very useful technique, as it handles the
+ case where both double-quotes and single-quotes are required in the entity content.
</p>
<p>
See further <a href="http://s.apache.org/b8V">explanation</a>.

Modified: forrest/site/docs_0_100/faq.xml
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_100/faq.xml?rev=1551469&r1=1551468&r2=1551469&view=diff
==============================================================================
--- forrest/site/docs_0_100/faq.xml (original)
+++ forrest/site/docs_0_100/faq.xml Tue Dec 17 06:21:49 2013
@@ -1067,15 +1067,15 @@ X [0] /docs_0_80/upgrading_08.ht
That is easily added directly to your project sitemap for any
special processing.
However for many cases it needs to be added to the main
- webapp/sitemap.xmap file.
+ <code>webapp/sitemap.xmap</code> file.
</p>
<p>
- Do this by adding a "handle-errors" xml entity to your project
+ Do this by adding a "sitemap-handle-errors" xml entity to your project
"symbols" file (<link href="#sitemap-entities">explained above</link>).
For example:
</p>
<source xml:space="preserve">
-&lt;!ENTITY handle-errors '
+&lt;!ENTITY sitemap-handle-errors '
&lt;map:handle-errors&gt;
&lt;map:select type="exception"&gt;
&lt;map:when test="resourceNotFound"&gt;
@@ -1089,9 +1089,36 @@ X [0] /docs_0_80/upgrading_08.ht
&lt;/map:handle-errors&gt;
'&gt;</source>
<p>
- Some exception selectors are configured in webapp/sitemap.xmap file
- at the "map:selectors" section.
- Please send patches for others if you need them to be added.
+ Some exception selectors are already configured in Forrest's main
+ <code>webapp/sitemap.xmap</code> file at the "map:selectors" section.
+ There is a mechanism for declaring more selectors for your project.
+ As above, add a "sitemap-selectors" xml entity to your project "symbols" file.
+ For this example, we demonstrate using an extra file for the snippet content.
+ </p>
+ <source xml:space="preserve">
+&lt;!ENTITY sitemap-selectors SYSTEM "sitemap-selectors.xml"&gt;</source>
+ <p>
+ The file will be found relative to your project "symbols" file that declared it.
+ (If you need to hold a common set of such files elsewhere, then the
+ project Catalog Entity Resolver could be configured.)
+ So here is an example "sitemap-selectors" snippet to configure the XPathExceptionSelector
+ to declare other exception names for use in a more comprehensive
+ "map:handle-errors" section:
+ </p>
+ <source xml:space="preserve">
+&lt;map:selector name="exception2" src="org.apache.cocoon.selection.XPathExceptionSelector"&gt;
+ &lt;exception name="transformer2" class="javax.xml.transform.TransformerException" unroll="true"&gt;
+ &lt;xpath name="goofer2" test="message='The identifier is not allowed.'"/&gt;
+ &lt;/exception&gt;
+ &lt;exception class="java.lang.Throwable" unroll="true"/&gt;
+&lt;/map:selector&gt;</source>
+ <p>
+ The "message" text is issued from a stylesheet-directed termination
+ via <code>&lt;xsl:message terminate="yes"&gt;</code>
+ </p>
+ <p>
+ This file-based entity is a very useful technique, as it handles the
+ case where both double-quotes and single-quotes are required in the entity content.
</p>
<p>
See further <link href="http://s.apache.org/b8V">explanation</link>.

Modified: forrest/site/dtdx/document-v13.pdf
URL: http://svn.apache.org/viewvc/forrest/site/dtdx/document-v13.pdf?rev=1551469&r1=1551468&r2=1551469&view=diff
==============================================================================
Binary files - no diff available.

Modified: forrest/site/dtdx/document-v20.pdf
URL: http://svn.apache.org/viewvc/forrest/site/dtdx/document-v20.pdf?rev=1551469&r1=1551468&r2=1551469&view=diff
==============================================================================
Binary files - no diff available.