dleslie 00/09/25 14:16:30
Modified: java/xdocs/sources/xalan extensions.xml getstarted.xml
samples.xml
Log:
New bsf.jar replaces old bsf.jar and bsfengine.jar -- and works
with Rhino 1.5 js.jar for Javascript extensions.
Revision Changes Path
1.3 +2 -2 xml-xalan/java/xdocs/sources/xalan/extensions.xml
Index: extensions.xml
===================================================================
RCS file: /home/cvs/xml-xalan/java/xdocs/sources/xalan/extensions.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- extensions.xml 2000/09/19 12:52:37 1.2
+++ extensions.xml 2000/09/25 21:16:29 1.3
@@ -27,7 +27,7 @@
</s2><anchor name="supported-lang"/>
<s2 title="Supported languages">
<p>&xslt4j; uses the <jump
href="http://www.alphaworks.ibm.com/tech/bsf";>Bean Scripting Framework
(BSF)</jump>, an architecture for incorporating scripting into Java
applications and applets. BSF allows an application to take advantage of
scripting while being independent of any specific scripting language. To date,
we have tested extensions implemented in Java and JavaScript. Other languages
with BSF support appear in the table below.</p>
-<p>BSF requires two JAR files on the class path: bsf.jar and bsfengines.jar.
These two JAR files are shipped with &xslt4j;, and that is all that is required
for Java extensions. The additional JAR files or DLLs required to support
extensions in other languages are listed in the table below. These files are
available from the sources indicated and are not shipped with &xslt4j;.</p>
+<p>BSF requires bsf.jar on the class path. This JAR file is shipped with
&xslt4j;, and that is all that is required for Java extensions. The additional
JAR files or DLLs required to support extensions in other languages are listed
in the table below. These files are available from the sources indicated and
are not shipped with &xslt4j;.</p>
<table>
<tr>
<td><em>Language</em></td>
@@ -136,7 +136,7 @@
</source>
</s2><anchor name="setup-runtime"/>
<s2 title="Setting up the runtime environment">
-<p>To run the preceding example, bsf.jar, bsfengines.jar, and js.jar must be
on the class path. Remember that bsf.jar and bsfengines.jar must be on the
class path to run any extension. For extensions implemented in a scripting
language, see the additional requirements in <link
anchor="supported-lang">Supported languages</link>.</p>
+<p>To run the preceding example, bsf.jar and js.jar must be on the class
path. Remember that bsf.jar must be on the class path to run any extension. For
extensions implemented in a scripting language, see the additional requirements
in <link anchor="supported-lang">Supported languages</link>.</p>
</s2><anchor name="basic-syntax"/>
<s2 title="Syntax">
<p>You can always use the pattern illustrated above to set up and use
extension elements and extension functions. For extension functions implemented
in Java, you can also use the java namespace, described in <link
anchor="java-namespace">Alternative: using the predefined java extension
namespace</link>. Unless you are using the predefined java extension namespace,
do the following:</p>
1.2 +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.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- getstarted.xml 2000/09/15 19:03:20 1.1
+++ getstarted.xml 2000/09/25 21:16:29 1.2
@@ -20,10 +20,10 @@
<p>You can get the JDK or JRE from <jump
href="http://www.ibm.com/java/jdk";>ibm.com/java/jdk/</jump> or <jump
href="http://www.java.sun.com";>java.sun.com</jump>.</p>
<p>Download <resource-ref idref="xslt4j-dist-zip"/> or <resource-ref
idref="xslt4j-dist-targz"/>. Both of these files contain <resource-ref
idref="xslt4j-current"/> (with xalan.jar) and xerces.jar from <resource-ref
idref="xml4j-used"/>. You can use a zip or tar utility to expand these files
into a full build.</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>
+<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 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
(all samples other than the servlet) and xalanservlet.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
(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
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">
1.6 +2 -2 xml-xalan/java/xdocs/sources/xalan/samples.xml
Index: samples.xml
===================================================================
RCS file: /home/cvs/xml-xalan/java/xdocs/sources/xalan/samples.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- samples.xml 2000/09/20 14:01:21 1.5
+++ samples.xml 2000/09/25 21:16:30 1.6
@@ -74,7 +74,7 @@
<p>With most of the samples, you can use the following procedure:</p>
<ol>
<li>Be sure xalan.jar, xalansamples.jar, and xerces.jar are on the
system class
- path. For the extension examples, bsf.jar, bsfengines.jar, and (for
the JavaScript extensions) js.jar must also be on the class
+ path. For the extension examples, bsf.jar and (for the JavaScript
extensions) js.jar must also be on the class
path.</li>
<li>Be sure the java executable is on your path.</li>
<li>Go to the samples subdirectory containing the sample (use the DOS
shell if you are running Windows).</li>
@@ -193,7 +193,7 @@
</ul>
<p>The extensions subdirectory contains five samples with &xslt4j;
extensions. Two of the samples use
extensions implemented in JavaScript, and three of the samples use
extensions implemented in Java.</p>
- <p>To run these examples, you must place bsf.jar and bsfengines.jar
(distributed with &xslt4j;), and js.jar
+ <p>To run these examples, you must place bsf.jar (distributed with
&xslt4j;), and js.jar
(version 1.5, available from
<jump
href="http://www.mozilla.org/rhino";>http://www.mozilla.org/rhino</jump>) on the
class path.
You do not need js.jar on the class path for the samples that use Java
extensions. </p>
