forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r525688 - in /forrest/trunk/site-author: content/xdocs/docs_0_80/faq.xml content/xdocs/docs_0_80/validation.xml status.xml
Date Thu, 05 Apr 2007 02:48:41 GMT
Author: crossley
Date: Wed Apr  4 19:48:41 2007
New Revision: 525688

Add notes about using and debugging the XML Catalog Entity Resolver for local DTDs.


Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/faq.xml
--- forrest/trunk/site-author/content/xdocs/docs_0_80/faq.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_80/faq.xml Wed Apr  4 19:48:41 2007
@@ -801,6 +801,23 @@
             Resolver for local DTDs</link>. </p>
+    <faq id="project-dtd">
+      <question>How to configure the Catalog Entity Resolver to use my own local DTDs?</question>
+      <answer>
+        <p>
+          See <link href="site:your-project/new_dtd">Using Forrest</link> for
+          configuration guidance.
+        </p>
+      </answer>
+    </faq>
+    <faq id="debug-catalog">
+      <question>How to debug the Catalog Entity Resolver and local DTDs?</question>
+      <answer>
+        <p>
+          See <link href="site:validation/debug-catalog">XML validation</link>.
+        </p>
+      </answer>
+    </faq>
     <faq id="skin">
       <question> How to make the site look better and change its skin? </question>

Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/validation.xml
--- forrest/trunk/site-author/content/xdocs/docs_0_80/validation.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_80/validation.xml Wed Apr  4 19:48:41 2007
@@ -292,14 +292,37 @@
           We now have a custom DTD and a catalog mapping which lets both
           Forrest and Cocoon
-          locate the DTD.  Now if we were to run <code>'forrest validate'</code>
+          locate the DTD.  Now if we were to run <code>'forrest validate-xdocs'</code>
           our download file would validate along with all the others.  If
-          something goes wrong, try running <code>'forrest -v validate'</code>
-          see the error in more detail. Remember to raise the "verbosity"
-          level in <code>cocoon.xconf</code> if you suspect problems
-          with your catalog.
+          something goes wrong, try running <code>'forrest -v validate-xdocs'</code>
+          see the error in more detail.
+    </section>
+    <section id="debug-catalog">
+      <title>Debugging the Catalog Entity Resolver</title>
+      <p>
+        If you suspect problems with your project catalog, then raise the "verbosity"
+        level in <code>src/documentation/classes/</code>
+        and re-start forrest.
+        This should show your project catalogs being parsed and loaded.
+      </p>
+      <p>
+        However this configuration does not show your DTDs being resolved.
+        So raise the verbosity level in the central configuration at
+        <code>main/webapp/WEB-INF/properties/dev/</code>
+        and re-start forrest. This also shows the main catalogs being loaded
+        and shows the resolving of every DTD and entity set.
+      </p>
+      <p>
+        When a DTD is successfully resolved you should see the message:
+        <code>Resolved public:</code>
+      </p>
+      <p>
+        When debugging such issues, a network monitoring tool (e.g.
+        is useful to ensure that all resources are being locally resolved and not       wandering
onto the network to find remote copies.
+      </p>
     <section id="entities">

Modified: forrest/trunk/site-author/status.xml
--- forrest/trunk/site-author/status.xml (original)
+++ forrest/trunk/site-author/status.xml Wed Apr  4 19:48:41 2007
@@ -141,6 +141,11 @@
         Added document to facilitate
         <link href="site:upgrading_08">upgrading to v0.8</link>
+      <action dev="DC" type="add" context="docs">
+        Added notes about <link href="site:validation/debug-catalog">debugging</link>
+        the XML Catalog Entity Resolver for local DTDs.
+      </action>
       <action dev="DC" type="fix" context="code" fixes-bug="FOR-973">
         Handling of document/header/version elements is now re-enabled.

View raw message