ilene 2003/06/07 14:01:26
Modified: java/xdocs/sources/xalan whatsnew.xml overview.xml
xsltc_usage.xml faq.xml
Log:
Documentation patch to correct typos, contributed by Glen Mazza
([EMAIL PROTECTED]).
Revision Changes Path
1.31 +4 -4 xml-xalan/java/xdocs/sources/xalan/whatsnew.xml
Index: whatsnew.xml
===================================================================
RCS file: /home/cvs/xml-xalan/java/xdocs/sources/xalan/whatsnew.xml,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -r1.30 -r1.31
--- whatsnew.xml 10 Apr 2003 14:34:58 -0000 1.30
+++ whatsnew.xml 7 Jun 2003 21:01:26 -0000 1.31
@@ -70,8 +70,8 @@
the <link idref="dtm">Document Table Model (DTM)</link> to model the input
xml, while
XSLTC used its own DOMImpl implementation. The serializers used by the
processors were
also different. As the project matures sharing more components between the
processors
-becomes increasingly important. This makes the code more maintainable in the
future and
-also eliminates some subtle behavioral differences between the Interpretive
and the
+becomes increasingly important. This will make the code more maintainable in
the future and
+also eliminate some subtle behavioral differences between the Interpretive
and the
Compiled processors.</p>
<p>In addition to these design benefits, the integration of DTM with XSLTC
and the common
@@ -108,8 +108,8 @@
<p>During the merge of the Xalan Interpretive and XSLTC serializers, an
effort was made to use the best performing features from each serializer.
The new class hierarchy is similar to the one used by XSLTC. At the highest
-level the serializer classes split based on whether the output handler type
-("Stream" or "SAX"). At the next level, the hierarchy branches based on
+level the serializer classes split based on the output handler type
+("Stream" or "SAX"). At the next level, the hierarchy branches are based on
the output type (XML, HTML or TEXT). This allows each flavor of serializer
to do optimizations based on the output type and whether that output is
going
to a "Stream" or a "SAX" handler.</p>
1.19 +1 -1 xml-xalan/java/xdocs/sources/xalan/overview.xml
Index: overview.xml
===================================================================
RCS file: /home/cvs/xml-xalan/java/xdocs/sources/xalan/overview.xml,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- overview.xml 9 May 2003 13:34:55 -0000 1.18
+++ overview.xml 7 Jun 2003 21:01:26 -0000 1.19
@@ -147,7 +147,7 @@
<li>XSLT - XSL Transformations in
<jump href="http://www.brics.dk/~amoeller/XML/";>
The XML Revolution: Technologies for the future Web</jump> by Anders
Møller and Michael
- I. Schwartzbach (Web pages, but designed for sequential reading)</li>
+ I. Schwartzbach (Web pages, but designed for sequential
reading)<br/><br/></li>
<li>Crane Softwright's <jump
href="http://www.CraneSoftwrights.com/training/";>Free preview of
Practical Transformation Using XSLT and XPath</jump><br/><br/></li>
<li>Doug Tidwell's <jump
href="http://www.oreilly.com/catalog/xslt/";>XSLT</jump>, O'Reilly, 2001
1.36 +2 -2 xml-xalan/java/xdocs/sources/xalan/xsltc_usage.xml
Index: xsltc_usage.xml
===================================================================
RCS file: /home/cvs/xml-xalan/java/xdocs/sources/xalan/xsltc_usage.xml,v
retrieving revision 1.35
retrieving revision 1.36
diff -u -r1.35 -r1.36
--- xsltc_usage.xml 10 Apr 2003 14:34:58 -0000 1.35
+++ xsltc_usage.xml 7 Jun 2003 21:01:26 -0000 1.36
@@ -87,8 +87,8 @@
<p>
The jar file structure of the &xslt4jc-short; component has changed again.
In the
-original structure, the xsltc.jar file contained only &xslt4jc-short;
classes, and the
-other support jar files needed to be in your class path.
+original structure, the xsltc.jar file contained only &xslt4jc-short;
classes, so
+other support jar files needed to be added to the classpath.
In a subsequent model, all of the support classes were bundled with the
&xslt4jc-short;
classes into one xsltc.jar file.
Now, a single xalan.jar contains the code for both &xslt4j; processors. You
1.35 +9 -9 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.34
retrieving revision 1.35
diff -u -r1.34 -r1.35
--- faq.xml 28 May 2003 20:34:17 -0000 1.34
+++ faq.xml 7 Jun 2003 21:01:26 -0000 1.35
@@ -227,7 +227,7 @@
<a>
<p><anchor name='tomcat'/></p>
<p><jump
href="http://jakarta.apache.org/tomcat/index.html";>jakarta-tomcat 4.1.*</jump>
is packed
- with an old version xercesImpl.jar. Based on the <resource-ref
idref='endorsed' />, you should
+ with an old version of xercesImpl.jar. Based on the <resource-ref
idref='endorsed' />, you should
replace it with the newer xercesImpl.jar. You should add a newer
xalan.jar to Tomcat as well.
Read the FAQ about <link anchor='jdk14'>Issues running &xslt4j;
on JDK 1.4</link>. Place the
xalan.jar and xercesImpl.jar in the
<Tomcat_Home>\common\endorsed directory, where
@@ -355,7 +355,7 @@
<code>xmlns:foo="http://my-namespace";</code>
</p>
<p>Then you can use foo: in your XPath expression.</p>
- <p>Hint: Don't use default namespaces, and the problem doesn't
arise.</p>
+ <p>Hint: Avoiding the use of default namespaces will prevent this
problem from occuring.</p>
</a>
</faq>
<faq title='Setting the parser to be namespace aware'>
@@ -467,7 +467,7 @@
<ol>
<li>Using the wrong URI for the xsl: prefix will cause this
message. URIs, and namespace
URIs in particular, are case sensitive. Ensure the URI for the
xsl namespace is
- "http://www.w3.org/1999/XSL/Transform";.</li>
+ "http://www.w3.org/1999/XSL/Transform";.<br/><br/></li>
<li>The parser you are using to process a stylesheet Source and
generate a Transformer
does not have the namespaceAware property set to true.<br/>
When you create a Transformer, you must use a <link
anchor='namespace-aware'>namespace-aware</link> parser to parse the
stylesheet.</li>
@@ -649,13 +649,13 @@
<q>How do I get line numbers for errors in the XML or XSL input when I
am performing a
transformation?</q>
<a>
- <p>Use or mimic the command-line processor (
- <jump
href='apidocs/org/apache/xalan/xslt/Process.html'>org.apache.xalan.xslt.Process</jump>).
+ <p>Use or mimic the command-line processor (<jump
+
href='apidocs/org/apache/xalan/xslt/Process.html'>org.apache.xalan.xslt.Process</jump>).
</p>
<p>A
<jump
href='apidocs/javax/xml/transform/TransformerException.html'>TransformerException</jump>
generally wraps another exception, often a SAXParseException. The command-line
processor uses the static
<jump
href='apidocs/org/apache/xml/utils/DefaultErrorHandler.html'>org.apache.xml.utils.DefaultErrorHandler</jump>
printLocation() method to chase down the exception cause and get a
- <jump
href='apidocs/javax/xml/transform/SourceLocator.html'>SourceLocator</jump>that
can usually report line and column number.
+ <jump
href='apidocs/javax/xml/transform/SourceLocator.html'>SourceLocator</jump> that
can usually report line and column number.
</p>
<p>Suppose you wanted to modify the ValidateXMLInput sample in the
samples/Validate
subdirectory to include line and column numbers . All you need to
do is call
@@ -743,12 +743,12 @@
<q>My servlet cannot find classes that implement extension functions
or elements. What can I do?</q>
<a>
<p>If you install xalan.jar in the servlet engine's lib directory
(e.g., tomcat/lib), as
- opposed to the servlet's lib directory, then the &xslt4j; classes
- are loaded by a classloader that does not see the classes in the
servlet's classloader
+ opposed to the servlet application's lib directory, then the
&xslt4j; classes
+ are loaded by a classloader that does not see the classes in the
application's classloader
(i.e., the extension classes, if you placed them there). The
&xslt4j;
classes try to load the extension classes using their own
classloader, and that attempt
fails.</p>
- <p>Workaround: place xalan.jar in the servlet's lib directory and
NOT in the servlet engine's
+ <p>Workaround: place xalan.jar in the servlet application's lib
directory and NOT in the servlet engine's
lib directory. Another workaround is to place the extension
classes also in the servlet
engine's lib directory, but you generally want to avoid
cluttering that directory.</p>
<p>Thanks to Gunnlauger Thor Briem ([EMAIL PROTECTED]) for providing
this information.</p>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
