amiro 02/02/12 07:52:54
Modified: java/xdocs/sources/xalan xsltc_usage.xml
Log:
updated docs
Revision Changes Path
1.22 +20 -23 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.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- xsltc_usage.xml 1 Feb 2002 17:11:08 -0000 1.21
+++ xsltc_usage.xml 12 Feb 2002 15:52:54 -0000 1.22
@@ -94,15 +94,6 @@
<td>required</td>
<td>required</td>
</tr>
-<!-- TWA - xml.jar has old project x stuff; was able to compile and run
without it -->
-<!--
-<tr>
- <td>xml.jar</td>
- <td>required</td>
- <td>required</td>
- <td>required</td>
-</tr>
--->
<tr>
<td>runtime.jar</td>
<td>required</td>
@@ -127,6 +118,12 @@
<td></td>
<td>required</td>
</tr>
+<tr>
+ <td>regexp.jar</td>
+ <td>required</td>
+ <td></td>
+ <td>required</td>
+</tr>
</table>
<p>The JAR files listed above are in the &xslt4j; bin directory. The
translet is the set of class files or the JAR file that you generate with the
compiler; see <link anchor="compile">Compiling translets</link>.</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>
@@ -154,7 +151,7 @@
<anchor name="comp-synopsis"/>
<s3 title="Synopsis">
<p>
-<code>java org.apache.xalan.xsltc.compiler.XSLTC</code><br/>
+<code>java org.apache.xalan.xsltc.cmdline.Compile</code><br/>
<code> [-o <output>] [-d <directory>] [-j
<jarfile>]</code><br/>
<code> [-p <package name>] [-u]
<stylesheet>...</code></p>
@@ -195,29 +192,29 @@
files (see <link anchor="classpath">setting the system
classpath</link>).</p>
<p><em>Example 1:</em> Creating a translet from the hamlet.xsl
stylesheet.</p>
- <p><code>java org.apache.xalan.xsltc.compiler.XSLTC</code><br/>
+ <p><code>java org.apache.xalan.xsltc.cmdline.Compile</code><br/>
<code> hamlet.xsl</code></p>
<p>Example 1 produces a set of class files such as hamlet.class,
hamlet$0.class, hamlet$1.class.</p>
<p><em>Example 2:</em> Outputting to a JAR file.</p>
- <p><code>java org.apache.xalan.xsltc.compiler.XSLTC</code><br/>
+ <p><code>java org.apache.xalan.xsltc.cmdline.Compile</code><br/>
<code> -j hamlet.jar hamlet.xsl</code></p>
<p>Example 2 produces hamlet.jar, which contains the translet class
files.</p>
<p><em>Example 3:</em> Specifying the translet class name. </p>
- <p><code>java org.apache.xalan.xsltc.compiler.XSLTC</code><br/>
+ <p><code>java org.apache.xalan.xsltc.cmdline.Compile</code><br/>
<code> -o newhamlet hamlet.xsl</code></p>
<p>Example 3 producs a set of class files such as newhamlet.class,
newhamlet$0.class, etc., rather than hamlet.class,
hamles$0.class, etc.</p>
<p><em>Example 4:</em> Compiling multiple stylesheets.</p>
- <p><code>java org.apache.xalan.xsltc.compiler.XSLTC</code><br/>
+ <p><code>java org.apache.xalan.xsltc.cmdline.Compile</code><br/>
<code> hamlet1.xsl hamlet2.xsl
hamlet3.xsl</code></p>
<p>Example 4 produces three translets and set of class files derived
from the three stylesheets.</p>
<p><em>Example 5:</em> Package Specification.</p>
- <p><code>java org.apache.xalan.xsltc.compiler.XSLTC</code><br/>
+ <p><code>java org.apache.xalan.xsltc.cmdline.Compile</code><br/>
<code> -p com.mycompany.translets
hamlet.xsl</code></p>
<p>Example 5 produces a set of class files such as
com/mycompany/translets/hamlet.class,
com/mycompany/translets/hamlet$0.class', etc.</p>
@@ -282,16 +279,16 @@
<p><em>Example 1:</em> Processing an XML document.</p>
- <p><code>java org.apache.xalan.xsltc.runtime.DefaultRun</code><br/>
+ <p><code>java org.apache.xalan.xsltc.cmdline.Transform</code><br/>
<code> hamlet.xml hamlet</code></p>
<p>Example 1 uses the specified translet (hamlet) to transform the
specified XML input document (hamlet.xml).
The XML input document is in the current working directory. The translet
was created by using
- org.apache.xalan.xslt.compiler.XSLTC to compile an XSL stylesheet
(hamlet.xsl). </p>
+ org.apache.xalan.xslt.cmdline.Compile to compile an XSL stylesheet
(hamlet.xsl). </p>
<p><em>Example 2:</em> Passing stylesheet parameters to the
translet.</p>
- <p><code>java org.apache.xalan.xsltc.runtime.DefaultRun</code><br/>
+ <p><code>java org.apache.xalan.xsltc.cmdline.Transform</code><br/>
<code> hamlet.xml hamlet</code><br/>
<code> speaker=HAMLET 'scene=SCENE
IV'</code></p>
@@ -301,7 +298,7 @@
<p><em>Example 3:</em> Processing an XML input document specified with a
URI.</p>
- <p><code>java org.apache.xalan.xsltc.runtime.DefaultRun</code><br/>
+ <p><code>java org.apache.xalan.xsltc.cmdline.Transform</code><br/>
<code> -u http://zarya.east/test.xml
hamlet</code></p>
<p>Example 3 applies the translet (hamlet) to the XML input document
(http://zarya.east/test.xml hamlet). Inclusion of
@@ -309,7 +306,7 @@
</s3>
</s2><anchor name="api"/>
<s2 title="Calling XSLTC with the TrAX/JAXP API">
-<p>G. Todd Miller has begun integrating the translet with the TrAX/JAXP 1.1
API. See <jump href="xsltc/xsltc_trax.html">The Translet API & TrAX</jump>.
Accordingly, it is now possible to set a system property and use a
TransformerFactory to generate a Transformer that performs a transformation by
compiling and running a translet.</p>
+<p>XSLTC translets are integrated with the TrAX/JAXP 1.1 API. See <jump
href="xsltc/xsltc_trax.html">The Translet API & TrAX</jump>. Accordingly,
it is now possible to set a system property and use a TransformerFactory to
generate a Transformer that performs a transformation by compiling and running
a translet.</p>
<p>When you use the JAXP 1.1 API to run &xslt4j;, the
<code>javax.xml.transform.TransformerFactory</code> system property is set to
<code>org.apache.xalan.processor.TransformerFactoryImpl</code>. As it currently
stands, this Xalan implementation of TransformerFactory always uses the Xalan
Transformer to perform transformations. To use translets to perform
transformations, set this system property to
<code>org.apache.xalan.xsltc.trax.TransformerFactoryImpl</code>. For
information on setting this and related system properties designating XML
parsere and XSL transformer, see <link idref="usagepatterns"
anchor="plug">Plugging in a Transformer and XML parser</link>.</p>
@@ -463,7 +460,7 @@
<source>import java.io.File;
import java.net.MalformedURLException;
-import org.apache.xalan.xsltc.compiler.XSLTC;
+import org.apache.xalan.xsltc.cmdline.Compile;
...
private Translet compileStylesheet(String stylesheetName) {
Translet retval = null;
@@ -505,7 +502,7 @@
series of .class files. Their base name is derived from the name of the
stylesheet. </p>
-<p>The XSLT compiler object (org.apache.xalan.xsltc.compiler.XSLTC), is
created,
+<p>The XSLT compiler object (org.apache.xalan.xsltc.cmdline.Compile), is
created,
initialized and then its compile() method is called passing in a URL
to the stylesheet itself. Once the .class files have been written,
the translet is instantiated using Java reflection to create the Class
@@ -652,4 +649,4 @@
<p>See <link idref="xsltc_constraints" anchor="xsltcconf">Conformance
issues</link> and <link idref="xsltc_constraints"
anchor="xsltcknownproblems">Known problems</link>.</p>
</s2>
-</s1>
\ No newline at end of file
+</s1>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
