You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xalan.apache.org by dl...@apache.org on 2001/02/14 21:09:51 UTC
cvs commit: xml-xalan/java/xdocs/sources/xalan faq.xml usagepatterns.xml
dleslie 01/02/14 12:09:51
Modified: java/xdocs/sources/xalan faq.xml usagepatterns.xml
Log:
1. Added item on classpath problems using the IBM JDK 1.3.
2. Added usage patern note on change in handling of string
stylesheet parameters from Xalan-J 1 to Xalan-J 2.
Revision Changes Path
1.4 +5 -0 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.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- faq.xml 2001/01/25 18:37:19 1.3
+++ faq.xml 2001/02/14 20:09:51 1.4
@@ -46,6 +46,11 @@
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>
<faq title="Speeding up transformations">
1.28 +2 -0 xml-xalan/java/xdocs/sources/xalan/usagepatterns.xml
Index: usagepatterns.xml
===================================================================
RCS file: /home/cvs/xml-xalan/java/xdocs/sources/xalan/usagepatterns.xml,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -r1.27 -r1.28
--- usagepatterns.xml 2001/02/13 20:03:38 1.27
+++ usagepatterns.xml 2001/02/14 20:09:51 1.28
@@ -239,6 +239,8 @@
<p>You can also set a parameter with the command-line utility by including the <code>-param</code> flag. For example:</p>
<p><code>java org.apache.xalan.xslt.Process -in foo.xml -xsl foo.xsl -param param1 foobar</code></p>
<p>where <code>param</code> is the parameter name and <code>foobar</code> is the parameter value. The parameter namespace is null.</p>
+<note>&xslt4j2; processes string parameters. You are no longer required (as you were with &xslt4j; version 1) to enclose strings in single
+quotes (') as string expressions.</note>
</s2><anchor name="sax"/>
<s2 title="Explicitly working with SAX">
<p>&xslt4j; uses the SAX event model to process stylesheets, to parse XML input documents, and to produce output. For each of these operations, an XMLReader reads input, firing parse events, and a ContentHandler listens to the XMLReader and executes parse event methods.</p>