dleslie 00/11/29 12:51:55
Modified: xdocs/sources/xalan commandline.xml
Log:
Put lxcin and lxcout flags back into command line utility. Was
taken out of XalanjJ2 alpha, and should not have been removed
from Xalan-J1.
Revision Changes Path
1.10 +19 -4 xml-xalan/xdocs/sources/xalan/commandline.xml
Index: commandline.xml
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/commandline.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- commandline.xml 2000/10/13 14:55:56 1.9
+++ commandline.xml 2000/11/29 20:51:47 1.10
@@ -67,7 +67,7 @@
<p>The org.apache.xalan.xslt.Process main() method provides a
command-line interface
for performing XSL transformation. To perform a transformation from the
command line or a script,
do the following:</p>
- <ol>
+ <ol>
<li><link idref="getstarted" anchor="download">Download
&xslt4j;</link>.<br/><br/></li>
<li><link idref="getstarted"
anchor="classpath">Set the java class path</link> to include xalan.jar
and xerces.jar<br/><br/></li>
@@ -81,11 +81,15 @@
<source>-IN inputXMLURL
-XSL XSLTransformationURL
-OUT outputFileName
+-LXCIN compiledStylesheetFileNameIn
+-LXCOUT compiledStylesheetFileNameOut
+-PARSER fully qualified class name of parser liaison
-V (Version info)
-QC (Quiet Pattern Conflicts Warnings)
-Q (Quiet Mode)
-LF (Use linefeeds only on output -- default is CR/LF)
-CR (Use carriage returns only on output -- default is CR/LF)
+-INDENT (Number of spaces to indent each level in output tree --default is 0)
-TT (Trace the templates as they are being called)
-TG (Trace each result tree generation event)
-TS (Trace each selection event)
@@ -98,8 +102,12 @@
-PARAM name expression (Set a stylesheet parameter)</source>
<p>Use -IN to specify the XML source document.</p>
<p>Use -XSL to specify the XSL stylesheet file.</p>
- <p>Use -OUT to specify the output file. If you omit this flag and
argument, the processor prints the output to the
- screen.</p>
+ <p>Use -LXCIN to specify a compiled XSL stylesheet file.</p>
+ <p>Use -LXCOUT to compile an XSL stylesheet for future use as -LXCIN
input.</p>
+ <note>You can only use -LXCIN with a compiled stylesheet that you have
already created with the -LXOUT switch. For an
+ example, see <link anchor="compiledstylesheet">Using a compiled
stylesheet</link></note>
+ <p>Include -PARSER if you supply your own parser liaison class, which
is required if you do not use DTM or the
+ Xerces parser.</p>
<p>Use -TEXT if you want the output to include only element values
(not element tags with element names and
attributes).</p>
<p>Use -HTML to write 4.0 transitional HTML (some elements, such as
<br>, are
@@ -108,5 +116,12 @@
<code>TestXSLT -PARAM <ref>name expression</ref></code><br/>
To set the parameter to a string value, enclose the string in single
quotes (') to
make it an expression.</p>
+ <p><anchor name="compiledstylesheet"/><em>Using a compiled
stylesheet</em></p>
+ <p>If you are using a stylesheet repeatedly, you can improve
performance by compiling the stylesheet the first time
+ you use it and using the compiled stylesheet for subsequent
transformations.</p>
+ <p>For example, the following command line performs a transformation
and compiles the stylesheet:"<br/><br/>
+ <code>java org.apache.xalan.xslt.Process -in foo.xml -xsl foo.xsl
-lxcout foo.style</code><br/><br/>
+ The following command line uses the compiled stylesheet for the next
transformation:<br/><br/>
+ <code>java org.apache.xalan.xslt.Process -in foo2.xml -lxcin
foo.style</code></p>
</s2>
-</s1>
+</s1>
\ No newline at end of file
