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...@locus.apache.org on 2000/03/16 20:56:34 UTC
cvs commit: xml-xalan/xdocs/sources/xalan samples.xml getstarted.xml
dleslie 00/03/16 11:56:34
Modified: xdocs/sources/xalan samples.xml getstarted.xml
Log:
Edits per Dave M.
Revision Changes Path
1.13 +4 -7 xml-xalan/xdocs/sources/xalan/samples.xml
Index: samples.xml
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/samples.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- samples.xml 2000/03/16 18:59:33 1.12
+++ samples.xml 2000/03/16 19:56:33 1.13
@@ -1,4 +1,4 @@
-<?xml version="1.0" standalone="no"?>
+<?xml version="1.0" standalone="no"?>
<!--
* The Apache Software License, Version 1.1
*
@@ -141,7 +141,7 @@
for the entire result tree to be constructed (as the DOM consumer must do).</p>
<p>Run this sample from the Pipe subdirectory with</p>
<p><code>java Pipe</code></p>
- <p>For other examples using the SAX document handler, see the next section and <link idref="getstarted"
+ <p>For other examples using the SAX document handler, see the next section and <link idref="usagepatterns"
anchor="sax">Generating and responding to SAX events</link>.</p>
</s2><anchor name="sax"/>
<s2 title="PureSAX">
@@ -177,7 +177,7 @@
<p>The applet uses a stylesheet to transform an XML document into HTML. It displays the XML document, the
stylesheet, and the HTML output.</p>
<p>How to run it: See <jump href="../samples/appletXMLtoHTML/readme.html">sample applet readme</jump>.</p>
- <p>For a brief introduction to using applets to perform transformations, see <link idref="getstarted"
+ <p>For a brief introduction to using applets to perform transformations, see <link idref="usagepatterns"
anchor="applet">Using the &xslt4j; applet wrapper</link></p>
</s2><anchor name="servlet"/>
<s2 title="Servlet">
@@ -205,10 +205,7 @@
This is an alternative way of specifying the XML XSLTInputSource by utilizing the HTTP request's path
information.<br/><br/></item>
<label>http://localhost/servlet/DefaultApplyXSL/data.xml</label>
-<item>...examines data.xml for an <jump href="http://www.w3.org/TR/1999/PR-xml-stylesheet-19990114">associated</jump>
-XSL stylesheet. If multiple XSLs are associated with the data, the stylesheet whose media
-attribute maps to your browser type will be chosen. If no mapping is
-successful, the primary associated stylesheet is used.<br/><br/></item>
+<item>...examines data.xml for an associated XSL stylesheet. If multiple XSLs are associated with the data, the stylesheet whose media attribute maps to your browser type will be chosen. If no mapping is successful, the primary associated stylesheet is used.<br/><br/></item>
<label>http://localhost/servlet/data.xml</label>
<item>...provides the same function as the previous example, but this example assumes
that /servlet/data.xml has been mapped to be executed by this servlet. The servlet engine may be configured
1.9 +4 -4 xml-xalan/xdocs/sources/xalan/getstarted.xml
Index: getstarted.xml
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/getstarted.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- getstarted.xml 2000/03/16 18:59:33 1.8
+++ getstarted.xml 2000/03/16 19:56:33 1.9
@@ -1,4 +1,4 @@
-<?xml version="1.0" standalone="no"?>
+<?xml version="1.0" standalone="no"?>
<!DOCTYPE s1 SYSTEM "sbk:/style/dtd/document.dtd">
<s1 title="Getting Started">
@@ -22,10 +22,10 @@
<note>You can use &xslt4j; with other XML parsers than the Xerces XML parser, but it is up to you to implement liaisons to those parsers. Your liaison class should extend <resource-ref idref="XMLParserLiaisonDefaultDoc"/> and implement <resource-ref idref="XPathSupportDoc"/>.</note>
-<p>If you plan to run <link idref="extensions">XSLT extensions</link>. you need bsf.jar and bsfengines.jar, both of which are 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>
+<p>If you plan to run <link idref="extensions">XSLT extensions</link>, you need bsf.jar and bsfengines.jar, both of which are 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 class path">
-<p>At the very minimum, you must include xalan.jar and xerces.jar on the system class path. To run the sample applications, include xalansamples.jar To run extensions, include bsf.jar and bsfengines.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 class path and where you can get them.</p>
+<p>At the very minimum, you must include xalan.jar and xerces.jar on the system class path. To run the sample applications, include xalansamples.jar. To run extensions, include bsf.jar and bsfengines.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 class path and where you can get them.</p>
<p>If you are using JDK or JRE 1.1.8, also include classes.zip on the class path.</p>
</s2><anchor name="samples"/>
<s2 title="Trying out the samples">
@@ -52,7 +52,7 @@
<p>You can use this utility to try out XSL stylesheets you have written, to make sure they do what you expect with the XML source files they are designed to transform. The utility provides useful messages if the source file or stylesheet is not well formed. If you include a DOCTYPE statement in your XML source files and include the -validate flag on the command line, the utility will also let you know whether the XML document is valid (conforms to that DOCTYPE). For more information, see <link idref="commandline">Command-Line Utility</link>.</p>
</s2><anchor name="java-apps"/>
<s2 title="Setting up your own Java applications">
-<p>You can start by using your own XML source files and XSL stylesheets with the sample applications, which illustrate a number of the <link anchor="usage-patterns">basic usage patterns</link>.</p>
+<p>You can start by using your own XML source files and XSL stylesheets with the sample applications, which illustrate a number of the basic <link idref="usagepatterns">usage patterns</link>.</p><link idref="usagepatterns">
<p>If you modify a java source file, be sure to compile the class and place it on the system class path. Here are some basic points to keep in mind as you are setting up transformations:</p>
<ul>
<li>Use the <resource-ref idref="XSLTProcessorFactoryGetProcessorDoc"/> to set up an <resource-ref idref="XSLTProcessorDoc"/> object.<br/><br/></li>