dleslie 01/11/08 11:24:18
Modified: java/xdocs/sources/xalan commandline.xml faq.xml
getstarted.xml
Log:
Added info on xml-apis.jar.
Revision Changes Path
1.13 +1 -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.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- commandline.xml 2001/06/25 20:20:07 1.12
+++ commandline.xml 2001/11/08 19:24:18 1.13
@@ -69,7 +69,7 @@
do the following:</p>
<ol>
<li>Download &xslt4j;.<br/><br/></li>
- <li><link idref="getstarted" anchor="classpath">Set the Java
classpath</link> to include xalan.jar and
+ <li><link idref="getstarted" anchor="classpath">Set the Java
classpath</link> to include xalan.jar, xml-apis.jar, and
xerces.jar (or another conformant XML Parser -- see <link
idref="usagepatterns" anchor="plug">Plugging in
the Transformer and XML parser</link>).<br/><br/></li>
<li>Call java and the Process class with the appropriate flags and
1.14 +1 -1 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.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- faq.xml 2001/11/08 17:29:02 1.13
+++ faq.xml 2001/11/08 19:24:18 1.14
@@ -97,7 +97,7 @@
<q>I'm getting a NoClassDefFound error. What has to be on the
classpath?</q>
<a><ol>
- <li>xalan.jar and xerces.jar (or the XML parser you are using) must
always be on the classpath.<br/><br/></li>
+ <li>xalan.jar, xml-apis.jar, and xerces.jar (or the XML parser you are
using) must always be on the classpath.<br/><br/></li>
<li>To run the samples in the samples subdirectories, xalansamples.jar
must be on the classpath. To run the servlet (in
samples/servlet), xalanservlet.jar must be on the classpath along with
the javax.servlet and javax.servlet.http packages. Sun distributes
the javax.servlet packages in the JSWDK servlet.jar file.<br/><br/></li>
1.17 +2 -2 xml-xalan/java/xdocs/sources/xalan/getstarted.xml
Index: getstarted.xml
===================================================================
RCS file: /home/cvs/xml-xalan/java/xdocs/sources/xalan/getstarted.xml,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- getstarted.xml 2001/10/16 13:54:46 1.16
+++ getstarted.xml 2001/11/08 19:24:18 1.17
@@ -24,9 +24,9 @@
<p>If you plan to run <link idref="extensions">XSLT extensions</link>, you
need bsf.jar, which is included in the &xslt4j; distribution. If you plan to
run XSLT extensions implemented in Javascript or another scripting language,
you will need one or more additional files as indicated in <link
idref="extensions" anchor="supported-lang">extensions language
requirements</link>.</p>
</s2><anchor name="classpath"/>
<s2 title="Setting up the system classpath">
-<p>At the very minimum, you must include xalan.jar and xerces.jar (or
another conformant XML parser -- see <link idref="usagepatterns"
anchor="plug">Plugging in a Transformer and XML parser</link>) on the system
classpath. To run the sample applications, include xalansamples.jar (all
samples other than the servlet) and xalanservlet.jar. To run extensions,
include bsf.jar. All these JAR files are distributed with &xslt4j;. For
extensions implemented in JavaScript or another scripting language, see <link
idref="extensions" anchor="supported-lang">extensions language
requirements</link> to identify any additional JAR files you must place on the
classpath and where you can get them.</p>
+<p>At the very minimum, you must include xalan.jar, xml-apis.jar, and
xerces.jar (or another conformant XML parser -- see <link idref="usagepatterns"
anchor="plug">Plugging in a Transformer and XML parser</link>) on the system
classpath. To run the sample applications, include xalansamples.jar (all
samples other than the servlet) and xalanservlet.jar. To run extensions,
include bsf.jar. All these JAR files are distributed with &xslt4j;. For
extensions implemented in JavaScript or another scripting language, see <link
idref="extensions" anchor="supported-lang">extensions language
requirements</link> to identify any additional JAR files you must place on the
classpath and where you can get them.</p>
<p>If you are using JDK or JRE 1.1.8, also include classes.zip on the
classpath. If you are using JDK or JRE 1.2, include tools.jar on the
classpath.</p>
-<note>If you are running Xalan on a 1.1.8 platform or recompiling Xalan on
any platform, be sure to put xalan.jar in front of xerces.jar on the classpath.
Both JAR files include the org.w3c.dom packages. Xerces has added a number of
DOM level-3 methods. These are not yet part of the W3C DOM recommendation, and
Xalan does not support these methods.</note>
+<note>If you are running Xalan on a 1.1.8 platform or recompiling Xalan on
any platform, be sure to put xalan.jar and xml-apis.jar in front of xerces.jar
on the classpath. Both JAR files include the org.w3c.dom packages. Xerces has
added a number of DOM level-3 methods. These are not yet part of the W3C DOM
recommendation, and Xalan does not support these methods.</note>
</s2><anchor name="samples"/>
<s2 title="Trying out the samples">
<p>The &xslt4j; distribution includes a number of basic sample applications.
These samples are easy to run, and you can review the source files -- all of
which are brief -- to see just how they work.</p>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
