You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-commits@xmlgraphics.apache.org by sp...@apache.org on 2006/09/16 21:40:38 UTC
svn commit: r446928 - in
/xmlgraphics/fop/trunk/src/documentation/content/xdocs:
0.92/configuration.xml trunk/configuration.xml
Author: spepping
Date: Sat Sep 16 12:40:37 2006
New Revision: 446928
URL: http://svn.apache.org/viewvc?view=rev&rev=446928
Log:
Added a comment about the cofiguration schema and some other means to determine configuration errors.
Modified:
xmlgraphics/fop/trunk/src/documentation/content/xdocs/0.92/configuration.xml
xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/configuration.xml
Modified: xmlgraphics/fop/trunk/src/documentation/content/xdocs/0.92/configuration.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/documentation/content/xdocs/0.92/configuration.xml?view=diff&rev=446928&r1=446927&r2=446928
==============================================================================
--- xmlgraphics/fop/trunk/src/documentation/content/xdocs/0.92/configuration.xml (original)
+++ xmlgraphics/fop/trunk/src/documentation/content/xdocs/0.92/configuration.xml Sat Sep 16 12:40:37 2006
@@ -247,6 +247,47 @@
</renderer>]]></source>
</section>
</section>
+
+ <section>
+ <title>When it does not work</title>
+
+ <p>FOP searches the configuration file for the information it
+expects, at the position it expects. When that information is not
+present, FOP will not complain, it will just continue. When there is
+other information in the file, FOP will not complain, it will just
+ignore it. That means that when your configuration information is in
+the file but in a different XML element, or in a different XML path,
+than FOP expects, it will be silently ignored.</p>
+
+ <p>Check the following possibilities:</p>
+
+ <ul>
+ <li>The format of the configuration file has changed
+considerably between FOP 0.20.5 and FOP 1.0 and its beta versions. Did
+you convert your file to the new format?</li>
+
+ <li>The FOP distribution contains a schema for configuration
+files, at src/foschema/fop-configuration.xsd. Did you validate your
+configuration file against it? Add the following schema location to
+the <code>schema</code> element:
+
+<source><![CDATA[<fop
+xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+xsi:noNamespaceSchemaLocation=
+"http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/foschema/fop-configuration.xsd?view=co">]]>
+</source>
+
+and run the configuration file through a validating schema
+parser. Note that the schema cannot detect all errors, and that it is
+stricter about the order of some elements than FOP itself is.</li>
+
+ <li>Run FOP in debug mode (command line option
+<code>-d</code>). This makes FOP report which configuration
+information it finds. Check if FOP finds what you expect.</li>
+
+ </ul>
+
+ </section>
</body>
</document>
Modified: xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/configuration.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/configuration.xml?view=diff&rev=446928&r1=446927&r2=446928
==============================================================================
--- xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/configuration.xml (original)
+++ xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/configuration.xml Sat Sep 16 12:40:37 2006
@@ -289,6 +289,47 @@
</p>
</section>
</section>
+
+ <section>
+ <title>When it does not work</title>
+
+ <p>FOP searches the configuration file for the information it
+expects, at the position it expects. When that information is not
+present, FOP will not complain, it will just continue. When there is
+other information in the file, FOP will not complain, it will just
+ignore it. That means that when your configuration information is in
+the file but in a different XML element, or in a different XML path,
+than FOP expects, it will be silently ignored.</p>
+
+ <p>Check the following possibilities:</p>
+
+ <ul>
+ <li>The format of the configuration file has changed
+considerably between FOP 0.20.5 and FOP 1.0 and its beta versions. Did
+you convert your file to the new format?</li>
+
+ <li>The FOP distribution contains a schema for configuration
+files, at src/foschema/fop-configuration.xsd. Did you validate your
+configuration file against it? Add the following schema location to
+the <code>schema</code> element:
+
+<source><![CDATA[<fop
+xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+xsi:noNamespaceSchemaLocation=
+"http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/foschema/fop-configuration.xsd?view=co">]]>
+</source>
+
+and run the configuration file through a validating schema
+parser. Note that the schema cannot detect all errors, and that it is
+stricter about the order of some elements than FOP itself is.</li>
+
+ <li>Run FOP in debug mode (command line option
+<code>-d</code>). This makes FOP report which configuration
+information it finds. Check if FOP finds what you expect.</li>
+
+ </ul>
+
+ </section>
</body>
</document>
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-commits-help@xmlgraphics.apache.org