dleslie 01/03/13 13:01:13
Modified: java/xdocs/sources/xalan commandline.xml faq.xml index.xml
readme.xml
Log:
Updates for Xalan-J 2.0.1.
Revision Changes Path
1.11 +12 -1 xml-xalan/java/xdocs/sources/xalan/commandline.xml
Index: commandline.xml
===================================================================
RCS file: /home/cvs/xml-xalan/java/xdocs/sources/xalan/commandline.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- commandline.xml 2001/02/21 14:09:21 1.10
+++ commandline.xml 2001/03/13 21:01:07 1.11
@@ -97,7 +97,11 @@
-TEXT (Use simple Text formatter)
-HTML (Use HTML formatter)
-PARAM name value (Set a stylesheet parameter)
--DIAG put out timing diagnostics</source>
+-DIAG put out timing diagnostics
+-URIRESOLVER fullClassName (Use a custom URIResolver)
+-ENTITYRESOLVER fullClassName (Use a custom EntityResolver)
+-CONTENTHANDLER fullClassName (Use a custom ContentHandler)
+</source>
<p>Use <code>-IN</code> to specify the XML source document.</p>
<p>Use <code>-XSL</code> to specify the XSL stylesheet file.</p>
<p>Use <code>-TEXT</code> if you want the output to include only
element values (not element tags with element names and
@@ -106,5 +110,12 @@
not well formed XML).</p>
<p>To set stylesheet parameters from the command line, use <br/>
<code>java org.apache.xalan.xslt.Process -PARAM <ref>name
value</ref></code></p>
+ <p>Use <code>-URIRESOLVER</code> with a fully qualified class name to
utilize a custom implementation of the
+ <jump
href="apidocs/javax/xml/transform/URIResolver.html">URIResolver</jump> TrAX
interface to resolve URIs for
+ xsl:include, xsl:import, and the document() function.</p>
+ <p>Use <code>-ENTITYRESOLVER</code> with a fully qualified class name
to utilize a custom implementation of the
+ <jump
href="apidocs/org/xml/sax/EntityResolver.html">EntityResolver</jump> SAX
interface to handle external entity references.</p>
+ <p>Use <code>-CONTENTHANDLER</code> with a fully qualified class name
to utilize a custom implementation of the
+ <jump
href="apidocs/org/xml/sax/ContentHandler.html">ContentHandler</jump> SAX
interface to serialize output.</p>
</s2>
</s1>
1.5 +18 -5 xml-xalan/java/xdocs/sources/xalan/faq.xml
Index: faq.xml
===================================================================
RCS file: /home/cvs/xml-xalan/java/xdocs/sources/xalan/faq.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- faq.xml 2001/02/14 20:09:51 1.4
+++ faq.xml 2001/03/13 21:01:07 1.5
@@ -46,12 +46,25 @@
another transformation</link>.</p></a>
</faq>
- <faq title="IBM JDK 1.3 classpath issues">
- <q>I'm having a problem building or running &xslt4j; on the IBM JDK
1.3.</q>
- <a><p>The JDK 1.3 automatically places everything in the lib/ext directory
in front of everything you place on the classpath. The IBM JDK 1.3 includes an
earlier version of xerces.jar in the lib/ext directory, a version that does not
work with the current Xalan release. Accordingly, you must either purge the
xerces.jar that is in that directory or overwrite it with the xerces.jar that
is included with the Xalan distribution.</p></a>
-
+ <faq title="Issues running Xalan on JDK 1.3">
+ <q>I'm having a problem building or running &xslt4j; on the JDK 1.3.</q>
+ <a><p>The JDK 1.3 automatically places everything in the lib/ext directory
in front of everything you place on the classpath. If this directory contains a
version of DOM, JAXP, or Xerces that predates the &xslt4j; distribution you are
using, you may have problems!</p>
+<p>The IBM JDK 1.3 includes an earlier version of xerces.jar in the lib/ext
directory, a version that does not implement the JAXP 1.1 interfaces and
therefore does not work with the current Xalan release. Accordingly, you must
either purge the xerces.jar that is in that directory or overwrite it with the
xerces.jar that is included with the Xalan distribution.</p>
+<p>The SUN JDK 1.3 includes a pre-1.1 version of the JAXP in crimson.jar.
Either purge the crimson.jar in that directory or overwrite it with a newer
crimson.jar that includes and implements the JAXP 1.1 interfaces.</p></a>
+ </faq>
+ <faq title="a "DOM006 Hierarchy request error"">
+ <q>Why do I get a "DOM006 Hierarchy request error" when I try to transform
into a DOM Document node?</q>
+ <a>
+ <p>This error occurs when Xalan tries to add a Node to a Document node
where it isn't allowed. For example, attempting to add non-whitespace
+ text to the DOM Document node produces this error.</p>
+ <p>The error can also occur when a Document node is created with the
DOMImplementation createDocument() method, which takes a qualified name
+ as an argument and creates an element node. If you then pass the
returned Document node to Xalan, you get a "DOM006 Hierarchy request
+ error" when Xalan tries to add a second element to the Document node.
The solution is to either use the DocumentBuilder newDocument() method
+ to create a Document that does not contain an element node, or use a
DocumentFragment. It should be noted that the
+ DocumentBuilder newDocument() method is "Non-preferred" according to the
JAXP 1.1 documentation.</p>
+ </a>
</faq>
-
+
<faq title="Speeding up transformations">
<q>What can I do to speed up transformations?</q>
1.19 +2 -4 xml-xalan/java/xdocs/sources/xalan/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/xml-xalan/java/xdocs/sources/xalan/index.xml,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- index.xml 2001/01/18 15:07:54 1.18
+++ index.xml 2001/03/13 21:01:08 1.19
@@ -70,10 +70,8 @@
<p>For more information, see <link idref="whatsnew">What's new in
&xslt4j2;</link>.</p>
</s2>
<s2 title="How about this release?">
- <p>&xslt4j-current; is a production release It incorporates the fixes and
enhancements that we have made based on testing and user feedback
- over the course of a number of alpha and beta 2.0 Developer's releases
dating from October 2000 to January 2001. For the details, see
- <link idref="readme">Release Notes</link>. Please send your comments, bug
reports, and feedback to the
- <human-resource-ref idref="xalandev"/>.</p>
+ <p>&xslt4j-current; is a production release It incorporates a number of
enhancements and bug fixes. For the details, see
+ <link idref="readme">Release Notes</link>. Please send your feedback to
the <human-resource-ref idref="xalandev"/>.</p>
</s2>
<s2 title="How do I get it?">
<p>Download and unzip either of the following:</p>
1.29 +9 -0 xml-xalan/java/xdocs/sources/xalan/readme.xml
Index: readme.xml
===================================================================
RCS file: /home/cvs/xml-xalan/java/xdocs/sources/xalan/readme.xml,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -r1.28 -r1.29
--- readme.xml 2001/03/07 13:05:29 1.28
+++ readme.xml 2001/03/13 21:01:09 1.29
@@ -77,7 +77,16 @@
<li><link anchor="to-do">To-do tasks for future &xslt4j;
releases</link></li>
</ul>
<anchor name="done"/>
+ <s3 title="Changes since &xslt4j; 2.0.0">
+ <p>This release includes a number of bug fixes to the &xslt4j; and TrAX
core and Xalan-Java 1 compability API. We have also</p>
+ <ul>
+ <li>Entered all known &xslt4j; 2 <link anchor="bugs">bugs</link> in the
Apache Bugzilla database<br/><br/></li>
+ <li>Added support for using custom URIResolver, EntityResolver, and
ContentHandler implementations with the <link
+ idref="commandline">command-line utility</link><br/><br/></li>
+ <li>Upgraded from Ant 1.2 to Ant 1.3 for our <link
anchor="build">builds</link> (the new ant.jar is in the bin directory).</li>
+ </ul>
&done-j;
+ </s3>
<anchor name="other"/>
<s3 title="Other points of interest">
<ul>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
