This is an automated email from the ASF dual-hosted git repository.
mukulg pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/xalan-site.git
The following commit(s) were added to refs/heads/master by this push:
new ec3b2a6e minor changes to xalanj documentation
ec3b2a6e is described below
commit ec3b2a6e788b9a21652f17f294b1540c1c0e64dc
Author: Mukul Gandhi <[email protected]>
AuthorDate: Fri Apr 14 17:34:42 2023 +0530
minor changes to xalanj documentation
---
xalan-j/xsltc_usage.html | 26 +++++++++++---------------
1 file changed, 11 insertions(+), 15 deletions(-)
diff --git a/xalan-j/xsltc_usage.html b/xalan-j/xsltc_usage.html
index e9cc3362..679588ab 100644
--- a/xalan-j/xsltc_usage.html
+++ b/xalan-j/xsltc_usage.html
@@ -221,18 +221,18 @@ document and perform a transformation.</p>
<a href="#content">(top)</a>
</p>
<h3>Setting the system classpath for XSLTC</h3>
-<p>The xalan.jar contains support for both Xalan-Java processors. You
+<p>The xalan.jar file contains support for both Xalan-Java processors. You
can use the JAXP <code>javax.xml.transform.TransformerFactory</code> property
(see <a href="#api">"Calling XSLTC with the JAXP API"</a> below) to
select which processor to use: the Interpretive or the Compiling
processor.</p>
<p>To use XSLTC, simply put xalan.jar, serializer.jar, xml-apis.jar, and
xercesImpl.jar on
-your classpath.</p>
+the system classpath.</p>
<table class="note">
<tr>
<td class="noteImg">
<img src="resources/note.gif" alt="note" />
</td>
-<td class="noteTxt">To compile and run translets, you must use JDK (or JRE)
1.3.1 or higher.</td>
+<td class="noteTxt">To compile and run translets, you must use JDK (or JRE)
1.8 or higher.</td>
</tr>
</table>
<table class="note">
@@ -253,9 +253,7 @@ the version of the XSLTC compiler that was used to create
the translet.</td>
</p>
<h4>Bundled System Classpath</h4>
<p>
-To use this newer approach, simply put xalan.jar, serializer.jar, xml-apis.jar
and
-xercesImpl.jar in your classpath. There is no need to include xsltc.jar,
BCEL.jar, JLex.jar,
-regexp.jar, java_cup.jar or runtime.jar as required in previous releases.
+To use this approach, simply put xalan.jar, serializer.jar, xml-apis.jar and
xercesImpl.jar on your system classpath.
</p>
<table class="note">
<tr>
@@ -263,12 +261,11 @@ regexp.jar, java_cup.jar or runtime.jar as required in
previous releases.
<img src="resources/note.gif" alt="note" />
</td>
<td class="noteTxt">In order to compile and run translets you must have a JAXP
1.3 compliant XML
-parser installed. Our distribution includes <a
href="http://xerces.apache.org/xerces2-j/index.html">Xerces-Java 2.11.0</a>.
-Include xercesImpl.jar and xml-apis.jar in your class path.</td>
+parser installed. Our distribution includes <a
href="http://xerces.apache.org/xerces2-j/index.html">Xerces-Java 2.12.2</a>.
+Include xercesImpl.jar and xml-apis.jar on your system classpath.</td>
</tr>
</table>
-
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
@@ -276,8 +273,8 @@ Include xercesImpl.jar and xml-apis.jar in your class
path.</td>
<p>The binary distribution contains XSLTC and all its support classes bundled
into xalan.jar. To use the unbundled approach, rebuild
the xsltc.jar file using the xsltc.unbundledjar target. The support jars that
-you'll need to add to your classpath are available in the Xalan Java lib
-directory.</p>
+you'll need to add to your classpath are available in the Xalan Java lib and
tools
+directories.</p>
<p>To compile translets, run translets, and use the XSLTC API, using
the unbundled jar approach, put the following on the system classpath:</p>
<table border="1">
@@ -302,7 +299,7 @@ the unbundled jar approach, put the following on the system
classpath:</p>
<td class="content" rowspan="1" colspan="1">required</td>
</tr>
<tr>
- <td class="content" rowspan="1" colspan="1">BCEL.jar</td>
+ <td class="content" rowspan="1" colspan="1">bcel-6.7.0.jar</td>
<td class="content" rowspan="1" colspan="1">required</td>
<td class="content" rowspan="1" colspan="1" />
</tr>
@@ -937,10 +934,9 @@ create a <code>Templates</code> object from which you
would create your
<a href="#content">(top)</a>
</p>
<h3>Calling XSLTC with the native API</h3>
-<p>The XSLTC Native API is no longer supported. Instead, you should always
+<p>The XSLTC native API is no longer supported. Instead, you should always
use XSLTC with the JAXP Transform API.</p>
-
<a name="constraints"></a>
<p align="right" size="2">
<a href="#content">(top)</a>
@@ -986,7 +982,7 @@ tfac.setAttribute("enable-inlining", Boolean.TRUE);</pre>
<a href="#content">(top)</a>
</p>
</div>
-<div id="footer">Copyright © 1999-2014 The Apache Software Foundation<br
/>Apache, Xalan, and the Feather logo are trademarks of The Apache Software
Foundation<div class="small">Web Page created on - Thu 2014-05-15</div>
+<div id="footer">Copyright © 1999-2023 The Apache Software Foundation<br
/>Apache, Xalan, and the Feather logo are trademarks of The Apache Software
Foundation<div class="small">Web Page created on - Thu 2023-04-14</div>
</div>
</body>
</html>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]