zongaro 2003/02/05 14:28:27
Modified: java/xdocs/sources Tag: XSLTC_DTM entities.ent
java/xdocs/sources/xalan Tag: XSLTC_DTM builds.xml
commandline.xml commandline_xsltc.xml
extensions.xml extensions_xsltc.xml
extensionslib.xml samples.xml xsltc_usage.xml
Log:
Added entity declarations to entities.ent for XSLTC and Xalan-J Interpretive.
Revision Changes Path
No revision
No revision
1.58.2.4 +22 -19 xml-xalan/java/xdocs/sources/entities.ent
Index: entities.ent
===================================================================
RCS file: /home/cvs/xml-xalan/java/xdocs/sources/entities.ent,v
retrieving revision 1.58.2.3
retrieving revision 1.58.2.4
diff -u -r1.58.2.3 -r1.58.2.4
--- entities.ent 4 Feb 2003 23:37:20 -0000 1.58.2.3
+++ entities.ent 5 Feb 2003 22:28:27 -0000 1.58.2.4
@@ -3,6 +3,9 @@
<!ENTITY xslt "Xalan">
<!ENTITY xslt4j "Xalan-Java">
<!ENTITY xslt4j2 "Xalan-Java 2">
+<!ENTITY xslt4ji "&xslt4j; Interpretive">
+<!ENTITY xslt4jc-short "XSLTC">
+<!ENTITY xslt4jc-long "&xslt4j; Compiled">
<!ENTITY xslt4j-dist "xalan-j_2_4_1">
<!ENTITY xslt4j-dist-bin "&xslt4j-dist;-bin">
<!ENTITY xslt4j-dist-src "&xslt4j-dist;-src">
@@ -18,21 +21,21 @@
<!ENTITY download "The &xslt4j-current; download from xml.apache.org
includes &xml4j-jar; from &xml4j-used; and xml-apis.jar. For version
information about the contents of xml-apis.jar, see the JAR manifest.">
-<!ENTITY xsltcwhatsnewhead '<li><link anchor="xsltc">XSLTC</link></li>'>
+<!ENTITY xsltcwhatsnewhead '<li><link
anchor="xsltc">&xslt4jc-short;</link></li>'>
-<!ENTITY xsltcwhatsnew '<anchor name="xsltc"/><s2 title="XSLTC">
- <p>In April 2001, Sun donated XSLTC to the Xalan project.
XSLTC compiles stylesheets into translets and
- provides a runtime environment for using translets to
transform XML documents. Initially, XSLTC is
+<!ENTITY xsltcwhatsnew '<anchor name="xsltc"/><s2 title="&xslt4jc-long;
(&xslt4jc-short;)">
+ <p>In April 2001, Sun donated &xslt4jc-short; to the Xalan
project. &xslt4jc-short; compiles stylesheets into translets and
+ provides a runtime environment for using translets to
transform XML documents. Initially, &xslt4jc-short; is
available in a separate JAR. Over time, we plan to integrate
the two codebases. For more information,
- see <link idref="xsltc_usage">Using XSLTC</link>, <link
idref="readme" anchor="xsltcreleasenotes">XSLTC
- Release Notes</link>, and <jump
href="xsltc/index.html">XSLTC Design</link>.</p>
+ see <link idref="xsltc_usage">Using &xslt4jc-short;</link>,
<link idref="readme" anchor="xsltcreleasenotes">&xslt4jc-short;
+ Release Notes</link>, and <jump
href="xsltc/index.html">&xslt4jc-short; Design</link>.</p>
</s2>'>
-<!ENTITY history2xsltc '<note>For XSLTC changes since XSLTC was incorporated
into &xslt4j;, see
- <link idref="xsltc_history">XSLTC software
changes</link>.</note>'>
+<!ENTITY history2xsltc '<note>For &xslt4jc-short; changes since
&xslt4jc-short; was incorporated into &xslt4j;, see
+ <link idref="xsltc_history">&xslt4jc-short; software
changes</link>.</note>'>
-<!ENTITY xsltcclasspath '<p>If you are using <link
idref="xsltc_usage">XSLTC</link>, see
- <link idref="xsltc_usage" anchor="classpath">Setting
the system classpath for XSLTC</link>.</p>'>
+<!ENTITY xsltcclasspath '<p>If you are using <link
idref="xsltc_usage">&xslt4jc-short;</link>, see
+ <link idref="xsltc_usage" anchor="classpath">Setting
the system classpath for &xslt4jc-short;</link>.</p>'>
<!ENTITY xsltcsampleshead '<li><link
anchor="translets">translets</link></li>'>
@@ -40,29 +43,29 @@
<ul>
<li><link
anchor="xsltc1">JAXPTransletOneTransformation</link></li>
<li><link
anchor="xsltc2">JAXPTransletMultipleTransformations</link></li>
- <li><link anchor="xsltcother">Other XSLTC
samples</link></li>
+ <li><link anchor="xsltcother">Other &xslt4jc-short;
samples</link></li>
</ul>
<p>You can use the TrAX/JAXP 1.2 interfaces to compile and
run translets.
For an overview of the usage patterns these samples
illustrate, see
- <link idref="xsltc_usage" anchor="api">Calling XSLTC with
the TrAX/JAXP API</link>.</p>
+ <link idref="xsltc_usage" anchor="api">Calling
&xslt4jc-short; with the TrAX/JAXP API</link>.</p>
<anchor name="xsltc1"/>
<s3 title="JAXPTransletOneTransformation">
- <p>What it does: Uses the XSLTC TransformerFactory to
compile a translet and use
- the translet to transform the XSLTC to-do list from XML
into HTML.</p>
+ <p>What it does: Uses the &xslt4jc-short;
TransformerFactory to compile a translet and use
+ the translet to transform the &xslt4jc-short; to-do list
from XML into HTML.</p>
<p>Run this sample from the translets subdirectory with</p>
<p><code>java JAXPTransletOneTransformation</code></p>
<p>View the result in todo-xsltc.html.</p>
</s3><anchor name="xsltc2"/>
<s3 title="JAXPTransletMultipleTransformations">
- <p>What it does: Uses the XSLTC TransformerFactory to
compile a translet and use
- the Templates object associated with the translet to
transform the XSLTC and Xalan to-do lists from XML
+ <p>What it does: Uses the &xslt4jc-short;
TransformerFactory to compile a translet and use
+ the Templates object associated with the translet to
transform the &xslt4jc-short; and &xslt; to-do lists from XML
into HTML.</p>
<p>Run this sample from the translets subdirectory with</p>
<p><code>java JAXPTransletMultipleTransformations</code></p>
<p>View the results in todo-xsltc.html and
todo-xalan.html.</p>
</s3><anchor name="xsltcother"/>
- <s3 title="Other XSLTC samples">
- <p>Other XSLTC samples are located in the following samples
subdirectories:</p>
+ <s3 title="Other &xslt4jc-short; samples">
+ <p>Other &xslt4jc-short; samples are located in the
following samples subdirectories:</p>
<ul>
<li>CompiledServlet</li>
<li>CompiledBrazil</li>
@@ -72,7 +75,7 @@
</ul>
<p>For information about each of these samples, consult the
README file in the subdirectory.</p>
<note>The following paragraphs supply some basic background
information for CompiledServlet and CompiledBrazil.</note>
- <p>XSLTC provides demos for using XSLTC as a servlet and as
a handler for
+ <p>&xslt4jc-short; provides demos for using &xslt4jc-short;
as a servlet and as a handler for
Brazil (a new and powerful Web techology from Sun labs).</p>
<p>To run the Brazil-handler demo, download Brazil from
sunlabs:</p>
<p><code> <jump
href="http://research.sun.com/research/download/index.html";>http://research.sun.com/research/download/index.html</jump></code></p>
No revision
No revision
1.4.2.2 +1 -1 xml-xalan/java/xdocs/sources/xalan/builds.xml
Index: builds.xml
===================================================================
RCS file: /home/cvs/xml-xalan/java/xdocs/sources/xalan/builds.xml,v
retrieving revision 1.4.2.1
retrieving revision 1.4.2.2
diff -u -r1.4.2.1 -r1.4.2.2
--- builds.xml 27 Jan 2003 19:46:26 -0000 1.4.2.1
+++ builds.xml 5 Feb 2003 22:28:27 -0000 1.4.2.2
@@ -213,7 +213,7 @@
features or major functionality changes are properly documented.</p>
<p>Update the commits list and the 'what was done' list in
xdocs/sources/xalan/readme.xml
and whatsnew.xml. Note that currently some of the status information for
the
-xsltc portion of &xslt4j; is stored separately in xsltc_history.xml and
XSLTCDONE
+&xslt4jc-short; portion of &xslt4j; is stored separately in
xsltc_history.xml and XSLTCDONE
</p>
<p>Check in all your work!</p>
1.22.2.2 +7 -7 xml-xalan/java/xdocs/sources/xalan/commandline.xml
Index: commandline.xml
===================================================================
RCS file: /home/cvs/xml-xalan/java/xdocs/sources/xalan/commandline.xml,v
retrieving revision 1.22.2.1
retrieving revision 1.22.2.2
diff -u -r1.22.2.1 -r1.22.2.2
--- commandline.xml 27 Jan 2003 19:46:26 -0000 1.22.2.1
+++ commandline.xml 5 Feb 2003 22:28:27 -0000 1.22.2.2
@@ -61,7 +61,7 @@
<s1 title="Command-Line Utility">
<ul>
-<li><link idref="commandline_xsltc">Command line options for
XSLTC</link></li>
+<li><link idref="commandline_xsltc">Command line options for
&xslt4jc-short;</link></li>
</ul>
<s2 title="Using the Command-Line Utility">
@@ -75,7 +75,7 @@
<li><link idref="getstarted" anchor="classpath">Set the Java
classpath</link> to include xalan.jar, xml-apis.jar, and
&xml4j-jar; -- or another conformant XML Parser -- (see <link
idref="usagepatterns" anchor="plug">Plugging in
the Transformer and XML parser</link>). Also include xsltc.jar in the
classpath if you want to use
- the XSLTC related options.<br/><br/></li>
+ &xslt4jc-short; related options.<br/><br/></li>
<li>Call java and the Process class with the appropriate flags and
arguments (described below). The following command line, for example,
includes the -IN, -XSL,
and -OUT flags with their accompanying arguments -- the XML source
document, the XSL
@@ -86,7 +86,7 @@
<source>
Common Options
--XSLTC (use XSLTC for transformation)
+-XSLTC (use &xslt4jc-short; for transformation)
-IN inputXMLURL
-XSL XSLTransformationURL
-OUT outputFileName
@@ -103,7 +103,7 @@
-ENTITYRESOLVER full class name (EntityResolver to be used to resolve
entities)
-CONTENTHANDLER full class name (ContentHandler to be used to serialize
output)
- Options for the Xalan interpreter
+ Options for &xslt4ji;
-QC (Quiet Pattern Conflicts Warnings)
-TT (Trace the templates as they are being called)
@@ -118,7 +118,7 @@
http://xml.apache.org/xalan/features/optimize to false)
-RL recursionlimit (assert numeric limit on stylesheet recursion depth)
- Options for the Xalan compiler (XSLTC)
+ Options for &xslt4jc-long; (&xslt4jc-short;)
-XO [optional transletName] (assign the name to the generated translet)
-XD destinationDirectory (specify a destination directory for translet)
@@ -128,9 +128,9 @@
-XX (turn on additional debugging message output)
-XT (use translet to transform if possible)
</source>
- <p>Use <code>-XSLTC</code> if you want to transform with XSLTC. Please
refer to
+ <p>Use <code>-XSLTC</code> if you want to transform with
&xslt4jc-short;. Please refer to
<link idref="commandline_xsltc">this document</link> for a detailed
description on
- the XSLTC related options.</p>
+ &xslt4jc-short; related options.</p>
<p>Use <code>-IN</code> to specify the XML source document.</p>
<p>Use <code>-XSL</code> to specify the XSL stylesheet file.</p>
<p>Use <code>-TEXT</code> if you want the output to include only
element values (not element tags with element names and
1.2.2.2 +15 -15 xml-xalan/java/xdocs/sources/xalan/commandline_xsltc.xml
Index: commandline_xsltc.xml
===================================================================
RCS file: /home/cvs/xml-xalan/java/xdocs/sources/xalan/commandline_xsltc.xml,v
retrieving revision 1.2.2.1
retrieving revision 1.2.2.2
diff -u -r1.2.2.1 -r1.2.2.2
--- commandline_xsltc.xml 27 Jan 2003 19:46:26 -0000 1.2.2.1
+++ commandline_xsltc.xml 5 Feb 2003 22:28:27 -0000 1.2.2.2
@@ -59,7 +59,7 @@
-->
-<s1 title="Command line options for XSLTC">
+<s1 title="Command line options for &xslt4jc-short;">
<ul>
<li><link anchor="options">Options</link></li>
<li><link anchor="examples">Examples</link></li>
@@ -69,8 +69,8 @@
<anchor name="options"/>
<s2 title="Options">
-<p>The <code>org.apache.xalan.xslt.Process</code> command line now supports
XSLTC for transformation. You can use
-the new <code>-XSLTC</code> option to enable the XSLTC support. The
xsltc.jar file must be on your CLASSPATH
+<p>The <code>org.apache.xalan.xslt.Process</code> command line now supports
&xslt4jc-short; for transformation. You can use
+the new <code>-XSLTC</code> option to enable the &xslt4jc-short; support.
The xsltc.jar file must be on your CLASSPATH
in order to use the <code>-XSLTC</code> option.</p>
<p>The following existing options can be used with -XSLTC:</p>
<p><code>-IN, -XSL, -OUT, -V, -EDUMP, -XML, -TEXT, -HTML, -PARAM, <br/>
@@ -83,11 +83,11 @@
-NOOPTIMIMIZE, -RL</code></p>
<p>We also have a new set of options for <code>-XSLTC</code>. They are all
two letter options. The first
-letter is X and the second letter is the same as the corresponding option in
the XSLTC command line
+letter is X and the second letter is the same as the corresponding option in
the &xslt4jc-short; command line
<code>org.apache.xalan.xsltc.cmdline.Compile</code>.</p>
-<p>These new options can only be used with <code>-XSLTC</code>. If any of
them is used with the Xalan
-interpreter, a message is printed and the option is ignored.</p>
+<p>These new options can only be used with <code>-XSLTC</code>. If any of
them is used with
+&xslt4ji;, a message is printed and the option is ignored.</p>
<p>Here is the list of the new options:</p>
<ul>
@@ -114,11 +114,11 @@
<s2 title="Examples">
<p>You can just add the <code>-XSLTC</code> option to your existing option
list so that it will do the same
-thing as before, but using XSLTC.</p>
+thing as before, but using &xslt4jc-short;.</p>
-<p>Here is a simple example on how to use XSLTC:</p>
+<p>Here is a simple example on how to use &xslt4jc-short;:</p>
<p>> <code>java org.apache.xalan.xslt.Process -in test.xml -xsl test.xsl
-xsltc</code></p>
-<p>XSLTC compiles the stylesheet on the fly and uses the bytecode in memory
to transform the input xml.
+<p>&xslt4jc-short; compiles the stylesheet on the fly and uses the bytecode
in memory to transform the input xml.
No translet class is generated in this simple usage pattern.</p>
<p>If you want to generate translet classes from the stylesheet, you can use
the <code>-XO</code> option:</p>
<p>> <code>java org.apache.xalan.xslt.Process -in test.xml -xsl test.xsl
-xsltc -xo</code></p>
@@ -143,7 +143,7 @@
<p>The translet is loaded from the specified destination directory or the
current directory, using
the specified translet name or the xsl base name, depending on whether the
<code>-XD</code> or
<code>-XO</code> option is used. The options <code>-XO, -XD, -XP</code> and
<code>-XJ</code>
-can be used with the <code>-XT</code> option to tell XSLTC how to find the
translet classes. The translets
+can be used with the <code>-XT</code> option to tell &xslt4jc-short; how to
find the translet classes. The translets
are directly read in as bytecode. You do not need to add the translet
directory or the jar file to your
classpath.</p>
<p>Example:</p>
@@ -166,7 +166,7 @@
<s2 title="Simple FAQs">
<p><em>Q:</em> If I use the <code>-XT</code> option, how can I tell if it is
using the translet or the stylesheet for transformation?</p>
-<p><em>A:</em> Use the <code>-XX</code> option. When XSLTC uses the translet
for transformation, you will see a debug
+<p><em>A:</em> Use the <code>-XX</code> option. When &xslt4jc-short; uses
the translet for transformation, you will see a debug
message like "Tranform using translet ..." or "Tranform using translet ...
from jar file ...".</p>
<p><em>Q:</em> I want to use a translet for transformation, and I don't have
the stylesheet.</p>
@@ -177,7 +177,7 @@
<p><em>Q:</em> I only want to compile the stylesheet. I don't want to do a
transformation.</p>
<p><em>A:</em> TrAX has no notion of compiling a stylesheet. However, you
can achieve the same effect by
-running a dummy transformation and tell XSLTC to save the translet class.
Example:</p>
+running a dummy transformation and tell &xslt4jc-short; to save the translet
class. Example:</p>
<p>> <code>java org.apache.xalan.xslt.Process -xsl test.xsl -xsltc
<br/>-xo</code></p>
<p>This command runs a transformation on an empty input and generates the
translet <code>test.class</code>.</p>
</s2>
@@ -185,9 +185,9 @@
<anchor name="trax"/>
<s2 title="Using the new options from TrAX">
-<p>If you use the TrAX interface for XSLTC, you could not tell it to use
translets before. It always compiled
+<p>If you use the TrAX interface for &xslt4jc-short;, you could not tell it
to use translets before. It always compiled
the xsl on the fly and used the bytecode in memory for transformation. Now
you can use some of
-the new attributes in XSLTC's <code>TransformerFactoryImpl</code> class to
customize the translet behaviors from TrAX.</p>
+the new attributes in the <code>TransformerFactoryImpl</code> class of
&xslt4jc-short; to customize the translet behaviors from TrAX.</p>
<p>Here is the list of attributes in
<code>org.apache.xalan.xsltc.trax.TransformerFactoryImpl</code> and their
corresponding Process command line options:</p>
@@ -253,7 +253,7 @@
<p>The following example shows you how to do the same thing from TrAX for
the question 2 in the FAQ.</p>
<source>
-// set the system property javax.xml.transform.TransformerFactory in order
to use XSLTC
+// set the system property javax.xml.transform.TransformerFactory in order
to use &xslt4jc-short;
String key = "javax.xml.transform.TransformerFactory";
String value = "org.apache.xalan.xsltc.trax.TransformerFactoryImpl";
Properties props = System.getProperties();
1.21.4.3 +1 -1 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.21.4.2
retrieving revision 1.21.4.3
diff -u -r1.21.4.2 -r1.21.4.3
--- extensions.xml 4 Feb 2003 20:42:40 -0000 1.21.4.2
+++ extensions.xml 5 Feb 2003 22:28:27 -0000 1.21.4.3
@@ -526,7 +526,7 @@
<p>Use the declared prefix with the syntax described in <link
anchor="ext-func-calls">Extension function Java calls</link>.</p>
<p>That is all. You do not include an xalan:component element. Using the
abbreviated syntax clearly involves less setup than using the
xalan:component/xalan:script approach.</p>
<note>We recommend that, for extensions coded in Java, the abbreviated
syntax should always be used since the xalan:component/xalan:script constructs
add no functionality.</note>
-<note>The abbreviated syntax is supported in XSLTC, but the
xalan:component/xalan:script constructs are not.</note>
+<note>The abbreviated syntax is supported in &xslt4jc-short;, but the
xalan:component/xalan:script constructs are not.</note>
</s3><anchor name="ex-java-namespace"/>
<s3 title="Example: Formatting a date">
<p>This example uses extension functions to call the SimpleDateFormat class
and the IntDate class. IntDate uses String arguments to set up a Date
object:</p>
1.2.2.2 +22 -22 xml-xalan/java/xdocs/sources/xalan/extensions_xsltc.xml
Index: extensions_xsltc.xml
===================================================================
RCS file: /home/cvs/xml-xalan/java/xdocs/sources/xalan/extensions_xsltc.xml,v
retrieving revision 1.2.2.1
retrieving revision 1.2.2.2
diff -u -r1.2.2.1 -r1.2.2.2
--- extensions_xsltc.xml 27 Jan 2003 19:46:26 -0000 1.2.2.1
+++ extensions_xsltc.xml 5 Feb 2003 22:28:27 -0000 1.2.2.2
@@ -58,7 +58,7 @@
* <http://www.apache.org/>.
-->
-<s1 title="Extensions for XSLTC">
+<s1 title="Extensions for &xslt4jc-short;">
<ul>
<li><link anchor="intro">Introduction</link></li>
<li><link anchor="constraints">Constraints</link></li>
@@ -69,9 +69,9 @@
</ul>
<anchor name="intro"/>
<s2 title="Introduction">
- <p>XSLTC supports the use of extension functions implemented in external
Java classes. It also
+ <p>&xslt4jc-short; supports the use of extension functions implemented in
external Java classes. It also
supports the <link anchor="nodeset_ext">nodeset</link>, <link
anchor="redirect_ext">output/redirect</link>
- and <link anchor="exslt_ext">EXSLT</link> extension functions. Extension
support in XSLTC is
+ and <link anchor="exslt_ext">EXSLT</link> extension functions. Extension
support in &xslt4jc-short; is
still under development. It is currently not as complete as the extension
support in the
interpretive Xalan. There are constraints in some areas.</p>
</s2>
@@ -79,27 +79,27 @@
<anchor name="constraints"/>
<s2 title="Constraints">
<p>In addition to the constraints listed below for each particular
extension, extension support
- in XSLTC also has the following limitations:</p>
+ in &xslt4jc-short; also has the following limitations:</p>
<ol>
<li><link idref="extensions" anchor="ext-elements">Extension
element</link> is not supported.
The extension element mechanism is closely related to the internal
implementation of the XSLT processor.
- The current extension element mechansim is designed for the interpretive
Xalan. It does not work with XSLTC.</li>
+ The current extension element mechansim is designed for the interpretive
Xalan. It does not work with &xslt4jc-short;.</li>
<li>The <link idref="extensions" anchor="supported-lang">xalan:component
and xalan:script</link> extension elements are not supported at the moment.
This has
- the implication that you cannot use scripting languages (e.g. javascript)
with XSLTC.</li>
- <li><link idref="extensionslib" anchor="sql">The SQL extension</link> is
not supported in XSLTC at the moment.</li>
+ the implication that you cannot use scripting languages (e.g. javascript)
with &xslt4jc-short;.</li>
+ <li><link idref="extensionslib" anchor="sql">The SQL extension</link> is
not supported in &xslt4jc-short; at the moment.</li>
</ol>
</s2>
<anchor name="java_ext"/>
<s2 title="Java extension">
- <p>Java extension is supported in XSLTC. Constructors, static and instance
methods are all supported.
+ <p>Java extension is supported in &xslt4jc-short;. Constructors, static
and instance methods are all supported.
You can use any of the <link idref="extensions"
anchor="ext-func-calls">three namespace formats</link>
(Java, package and class) in your stylesheet.
</p>
- <p>The official namespace for the Java extension is
<code>http://xml.apache.org/xalan/java</code>. The old XSLTC Java namespace
+ <p>The official namespace for the Java extension is
<code>http://xml.apache.org/xalan/java</code>. The old &xslt4jc-short; Java
namespace
<code>http://xml.apache.org/xalan/xsltc/java</code> and the old Xalan
namespace <code>http://xml.apache.org/xslt/java</code>
are also supported for backward compatibility.</p>
- <p>All usage syntax for Xalan also applies to XSLTC with only one
exception: XSLTC does not support the notion of default object
+ <p>All usage syntax for Xalan also applies to &xslt4jc-short; with only
one exception: &xslt4jc-short; does not support the notion of default object
in <link idref="extensions" anchor="ext-func-calls">class format
namespace</link>.
When using instance methods, you should always specify the class instance
as the first argument
to the extension function.</p>
@@ -139,12 +139,12 @@
</xsl:stylesheet>
</source>
<note>Always use the abbreviated syntax for Java extension, because the
xalan:component/xalan:script
- constructs are not supported in XSLTC.</note>
+ constructs are not supported in &xslt4jc-short;.</note>
</s2>
<anchor name="exslt_ext"/>
<s2 title="EXSLT extensions">
- <p>The following EXSLT extension modules are supported in XSLTC:</p>
+ <p>The following EXSLT extension modules are supported in
&xslt4jc-short;:</p>
<ul>
<li><jump href="apidocs/org/apache/xalan/lib/ExsltCommon.html">EXSLT
common functions</jump></li>
<li><jump href="apidocs/org/apache/xalan/lib/ExsltMath.html">EXSLT math
functions</jump></li>
@@ -153,22 +153,22 @@
<li><jump href="apidocs/org/apache/xalan/lib/ExsltStrings.html">EXSLT
string functions</jump></li>
</ul>
<p>The functions in the <jump
href="apidocs/org/apache/xalan/lib/ExsltDynamic.html">dynamic</jump> module
- (e.g. evaluate) are not supported because of the XSLTC design limitation.
+ (e.g. evaluate) are not supported because of the &xslt4jc-short; design
limitation.
Work is currently underway on <jump
href="http://www.exslt.org/func/elements/function/index.html";>user
defined EXSLT functions (with the function and result elements)</jump>.</p>
<p>The <code>nodeset</code> and <code>objectType</code> extension
functions in the <jump
href="apidocs/org/apache/xalan/lib/ExsltCommon.html">common</jump>
- module are implemented natively in XSLTC. For all other EXSLT extension
functions,
- XSLTC uses the same implementation as Xalan. The implementation classes
are under <code>org.apache.xalan.lib</code>.
+ module are implemented natively in &xslt4jc-short;. For all other EXSLT
extension functions,
+ &xslt4jc-short; uses the same implementation as Xalan. The implementation
classes are under <code>org.apache.xalan.lib</code>.
Depending on the packaging, these classes can be in a separate jar file
(e.g. xalan.jar) from
- the XSLTC classes. In this case you need to add the jar file containing
the EXSLT classes to your
- classpath in order to use EXSLT extensions in XSLTC.</p>
+ the &xslt4jc-short; classes. In this case you need to add the jar file
containing the EXSLT classes to your
+ classpath in order to use EXSLT extensions in &xslt4jc-short;.</p>
</s2>
<anchor name="nodeset_ext"/>
<s2 title="nodeset">
- <p>XSLTC also supports the nodeset() extension function for transforming
an RTF (result
+ <p>&xslt4jc-short; also supports the nodeset() extension function for
transforming an RTF (result
tree fragment) into a node set.</p>
- <p>The nodeset extension can be used as an XSLTC extension function in
the namespace
+ <p>The nodeset extension can be used as an &xslt4jc-short; extension
function in the namespace
<code>http://xml.apache.org/xalan/xsltc</code>, a Xalan extension
function in the namespace
<code>http://xml.apache.org/xalan</code>, an EXSLT extension function in
the namespace
<code>http://exslt.org/common</code> or as a standard XPATH function.
When it is used as
@@ -188,7 +188,7 @@
<elem2>elem2</elem2>
</docelem>
</xsl:variable>
- <!-- Use nodeset as an XSLTC extension function -->
+ <!-- Use nodeset as an &xslt4jc-short; extension function -->
<xsl:value-of
select="xsltc-extension:nodeset($rtf)/docelem/elem1"/>
<!-- Use nodeset as a Xalan extension function -->
<xsl:value-of
select="xalan:nodeset($rtf)/docelem/elem1"/>
@@ -205,7 +205,7 @@
<anchor name="redirect_ext"/>
<s2 title="output/redirect">
- <p>XSLTC supports the output extension element for redirecting the output
to one
+ <p>&xslt4jc-short; supports the output extension element for redirecting
the output to one
or more files. The output extension element is also aliased to the write
extension element
in the namespace <code>http://xml.apache.org/xalan/redirect</code>.
Therefore you can use
it in the same way as the <link idref="extensionslib"
anchor="redirect">redirect</link> extension in Xalan.</p>
@@ -231,4 +231,4 @@
</xsl:stylesheet></source>
</s2>
-</s1>
\ No newline at end of file
+</s1>
1.27.2.2 +1 -1 xml-xalan/java/xdocs/sources/xalan/extensionslib.xml
Index: extensionslib.xml
===================================================================
RCS file: /home/cvs/xml-xalan/java/xdocs/sources/xalan/extensionslib.xml,v
retrieving revision 1.27.2.1
retrieving revision 1.27.2.2
diff -u -r1.27.2.1 -r1.27.2.2
--- extensionslib.xml 27 Jan 2003 19:46:26 -0000 1.27.2.1
+++ extensionslib.xml 5 Feb 2003 22:28:27 -0000 1.27.2.2
@@ -68,7 +68,7 @@
<li><link anchor="pipedocument">PipeDocument</link></li>
<li><link anchor="evaluate">evaluate</link></li>
<li><link anchor="tokenize">tokenize</link></li>
-<li><link idref="extensions_xsltc">Extensions for XSLTC</link></li>
+<li><link idref="extensions_xsltc">Extensions for &xslt4jc-short;</link></li>
<li>Examples: <link anchor="ex-redirect">Redirect</link>, <link
anchor="ex-nodeset">nodeset</link>, <link anchor="ex-sql">SQL
library</link></li>
</ul><anchor name="intro"/>
<s2 title= "Introduction">
1.48.4.5 +6 -6 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.48.4.4
retrieving revision 1.48.4.5
diff -u -r1.48.4.4 -r1.48.4.5
--- samples.xml 4 Feb 2003 23:30:57 -0000 1.48.4.4
+++ samples.xml 5 Feb 2003 22:28:27 -0000 1.48.4.5
@@ -86,7 +86,7 @@
<tr>
<td>xalansamples.jar</td>
<td>Everything except the Xalan-J Interpretive servlet sample and some
- XSLTC samples</td>
+ &xslt4jc-short; samples</td>
</tr>
<tr>
<td>xalanservlet.jar</td>
@@ -94,19 +94,19 @@
</tr>
<tr>
<td>xsltcapplet.jar</td>
- <td>XSLTC applet sample</td>
+ <td>&xslt4jc-short; applet sample</td>
</tr>
<tr>
<td>xsltcbrazil.jar</td>
- <td>XSLTC Brazil server sample</td>
+ <td>&xslt4jc-short; Brazil server sample</td>
</tr>
<tr>
<td>xsltcejb.jar</td>
- <td>XSLTC EJB sample</td>
+ <td>&xslt4jc-short; EJB sample</td>
</tr>
<tr>
<td>xsltcservlet.jar</td>
- <td>XSLTC servlet sample</td>
+ <td>&xslt4jc-short; servlet sample</td>
</tr>
</table>
<p>With most of the samples, you can use the following procedure:</p>
@@ -572,4 +572,4 @@
<p><code>java Examples</code></p>
<p>and examine the source in Examples.java and
ExampleContentHandler.java.</p>
</s2>&xsltcsamples;
-</s1>
\ No newline at end of file
+</s1>
1.31.2.4 +39 -39 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.31.2.3
retrieving revision 1.31.2.4
diff -u -r1.31.2.3 -r1.31.2.4
--- xsltc_usage.xml 4 Feb 2003 18:32:51 -0000 1.31.2.3
+++ xsltc_usage.xml 5 Feb 2003 22:28:27 -0000 1.31.2.4
@@ -56,48 +56,48 @@
* information on the Apache Software Foundation, please see
* <http://www.apache.org/>.
-->
-<s1 title="Using XSLTC (Xalan-J Compiler)">
+<s1 title="Using &xslt4jc-short;">
<ul>
<li><link anchor="intro">Introduction</link></li>
- <li><link anchor="classpath">Setting the system classpath for
XSLTC</link></li>
+ <li><link anchor="classpath">Setting the system classpath for
&xslt4jc-short;</link></li>
<li><link anchor="compile">Compiling translets from the command
line</link></li>
<li><link anchor="run">Running translets from the command line</link></li>
- <li><link anchor="api">Calling XSLTC with the TrAX/JAXP API</link></li>
+ <li><link anchor="api">Calling &xslt4jc-short; with the TrAX/JAXP
API</link></li>
<li><link anchor="xsltcsmart">Smart Transformer Switch</link></li>
- <li><link anchor="native_api">Calling XSLTC with the native API</link></li>
+ <li><link anchor="native_api">Calling &xslt4jc-short; with the native
API</link></li>
<li><link anchor="constraints">Usage constraints</link></li>
<li><link idref="samples" anchor="translets">Sample translets</link></li>
- <li><link idref="extensions_xsltc">Extensions for XSLTC</link></li>
+ <li><link idref="extensions_xsltc">Extensions for
&xslt4jc-short;</link></li>
</ul>
-<p>See also: <jump href="xsltc/index.html">XSLTC Design</jump></p>
+<p>See also: <jump href="xsltc/index.html">&xslt4jc-short; Design</jump></p>
<anchor name="intro"/>
<s2 title="Introduction">
-<p>XSLTC provides a compiler and a runtime processor.
+<p>&xslt4jc-short; provides a compiler and a runtime processor.
Use the compiler to compile an XSL stylesheet into a translet (i.e., a set of
Java classes). Use the runtime processor to apply the translet to an XML
document and perform a transformation.</p>
<note>To compile and run translets, you must have a JDK or a JRE 1.2 or
higher.</note>
</s2><anchor name="classpath"/>
-<s2 title="Setting the system classpath for XSLTC">
+<s2 title="Setting the system classpath for &xslt4jc-short;">
<p>
-The jar file structure of the XSLTC component has changed again. In the
-original structure, the xsltc.jar file contained only XSLTC classes, and the
+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.
-In a subsequent model, all of the support classes were bundled with the XSLTC
+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 Xalan-J processors. You
+Now, a single xalan.jar contains the code for both &xslt4j; processors. You
can use the JAXP <code>javax.xml.transform.TransformerFactory</code> property
-(see <link anchor="api">"Calling XSLTC with the TrAX/JAXP API"</link> below)
to
+(see <link anchor="api">"Calling &xslt4jc-short; with the TrAX/JAXP
API"</link> below) to
select which processor to use: the Interpretive or the Compiling
processor.</p>
<p>Refer to the subsection 'Bundled System Classpath' below to learn more
about
the new bundling.</p>
-<note>Although the XSLTC developers make every effort to avoid changes that
+<note>Although the &xslt4jc-short; developers make every effort to avoid
changes that
affect binary compatibility, we cannot guarantee that a translet will work
with
any version of the run-time processor other than the one that corresponds to
-the version of the XSLTC compiler that was used to create the
translet.</note>
+the version of the &xslt4jc-short; compiler that was used to create the
translet.</note>
</s2>
<s3 title="Bundled System Classpath">
@@ -114,10 +114,10 @@
</s3>
<s3 title="Unbundled System Classpath">
-<note>Support for building an unbundled version of XSLTC is not currently
+<note>Support for building an unbundled version of &xslt4jc-short; is not
currently
available. This section will be brought up-to-date when that support is
available.</note>
-<p>To compile translets, run translets, and use the XSLTC API, put the
following on the system classpath:</p>
+<p>To compile translets, run translets, and use the &xslt4jc-short; API, put
the following on the system classpath:</p>
<table>
<tr>
<th>Classes or JAR</th>
@@ -186,8 +186,8 @@
synopsis of the options and arguments accepted by this class is shown
below.
</p>
<note>You can also use the
- <jump href="commandline.html">Xalan-J command-line utility</jump>, to
- compile or run XSLTC translets.</note>
+ <jump href="commandline.html">&xslt4j; command-line utility</jump>, to
+ compile or run &xslt4jc-short; translets.</note>
<anchor name="comp-synopsis"/>
<s3 title="Synopsis">
<p>
@@ -284,11 +284,11 @@
<li><link anchor="run-examples">Examples</link></li>
</ul>
- <p>The XSLTC runtime processor is a Java-based tool for
+ <p>The &xslt4jc-short; runtime processor is a Java-based tool for
transforming XML document files using a translet (compiled
stylesheet). </p>
- <p>The XSLTC processor can be run on any platform including UNIX,
+ <p>The &xslt4jc-short; processor can be run on any platform including
UNIX,
Windows, NT, Mac that supports Java, including a Palm Pilot
with J2ME CLDC (Java 2 Micro Edition, Connected Limited Device
Configuration).</p>
@@ -299,8 +299,8 @@
(described below).</p>
<note>You can also use the
- <jump href="commandline.html">Xalan-J Command-line Utility</jump>, to
- compile or run XSLTC translets.</note>
+ <jump href="commandline.html">&xslt4j; Command-line Utility</jump>, to
+ compile or run &xslt4jc-short; translets.</note>
<anchor name="run-synopsis"/>
<s3 title="Synopsis">
<p><code>java org.apache.xalan.xsltc.cmdline.Transform</code><br/>
@@ -375,18 +375,18 @@
the flag (-u) is optional.</p>
</s3>
</s2><anchor name="api"/>
-<s2 title="Calling XSLTC with the TrAX/JAXP API">
+<s2 title="Calling &xslt4jc-short; with the TrAX/JAXP API">
<ul>
-<li><link anchor="api-attributes">XSLTC TransformerFactory
attributes</link></li>
+<li><link anchor="api-attributes">&xslt4jc-short; TransformerFactory
attributes</link></li>
<li><link anchor="api-examples">Examples</link></li>
</ul>
-<p>XSLTC translets are integrated with the TrAX/JAXP 1.2 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>&xslt4jc-short; translets are integrated with the TrAX/JAXP 1.2 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.2 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-J
-Interpretive processor to perform transformations. To use translets to
perform
+stands, this Xalan implementation of TransformerFactory always uses the
+&xslt4ji; processor 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
@@ -422,11 +422,11 @@
thread at the same time, use a <code>Templates</code> object and create
as many <code>Transformer</code> objects as you require.</p>
-<p>XSLTC also defines a set of attributes that you can set on the
+<p>&xslt4jc-short; also defines a set of attributes that you can set on the
<code>TransformerFactory</code> in order to save and subsequently use those
translets by way of the JAXP Transform API - without having to recompile the
stylesheet each time.</p><anchor name="api-attributes"/>
-<s3 title="XSLTC TransformerFactory attributes">
+<s3 title="&xslt4jc-short; TransformerFactory attributes">
The JAXP Transform API defines a <code><jump
href="apidocs/javax/xml/transform/TransformerFactory.html#setAttribute(java.lang.String,
java.lang.Object)">TransformerFactory.setAttribute</jump>
</code> method that you can use to set implementation-defined attributes.
<table>
@@ -571,23 +571,23 @@
</s2>
<anchor name="xsltcsmart"/>
<s2 title="Smart Transformer Switch">
-<p>As part of the TrAX API, a "Smart Transformer Switch" enables
automatic switching between Xalan and XSLTC
-processors within your application. It uses Xalan to create your
- <code>Transformer</code> objects, and uses XSLTC to create your
<code>Templates</code> objects.</p>
+<p>As part of the TrAX API, a "Smart Transformer Switch" enables
automatic switching between &xslt4ji; and &xslt4jc-short;
+processors within your application. It uses &xslt4ji; to create your
+ <code>Transformer</code> objects, and uses &xslt4jc-short; to create your
<code>Templates</code> objects.</p>
<p>To use the switch, you set the TrAX system property,
<code>javax.xml.transform.TransformerFactory</code>, to
<code>org.apache.xalan.xsltc.trax.SmartTransformerFactoryImpl</code>.
For one-time transformations or transformations that require extensions
-supported by Xalan, and not XSLTC, you would use the
+supported by &xslt4ji;, and not &xslt4jc-short;, you would use the
<code>SmartTransformerFactoryImpl</code> to create <code>Transformer</code>
objects. For a repeated transformation where performance is critical, you
would
create a <code>Templates</code> object from which you would create your
<code>Transformer</code> objects.</p>
</s2>
<anchor name="native_api"/>
-<s2 title="Calling XSLTC with the native API">
-<p>The XSLTC Native API is no longer supported. Instead, you should always
-use XSLTC with the JAXP Transform API.</p>
+<s2 title="Calling &xslt4jc-short; with the native API">
+<p>The &xslt4jc-short; Native API is no longer supported. Instead, you
should always
+use &xslt4jc-short; with the JAXP Transform API.</p>
</s2>
<anchor name="constraints"/>
<s2 title="Usage constraints">
@@ -595,7 +595,7 @@
<li>The default for template inlining has been changed. Previously,
by default, inlining (putting all the templates into one big method) was
on and
the <code>"-n"</code> option to the compile command line
disabled inlining.
- With inlining on, XSLTC can generate methods that are too long (<em>>
64K length</em>)
+ With inlining on, &xslt4jc-short; can generate methods that are too long
(<em>> 64K length</em>)
to run, or contain jump offsets that are too large for the JVM to
handle.
Now the default is not to inline templates. Instead, compilation creates
separate
methods for each template. Inlining was thought to improve performance,
@@ -605,7 +605,7 @@
For example,
<source>TransformerFactory tfac = new TransformerFactory();
tfac.setAttribute("enable-inlining",
Boolean.TRUE);</source><br/></li>
- <li>XSLTC tries to determine the order in which global variables are
initialized
+ <li>&xslt4jc-short; tries to determine the order in which global variables
are initialized
by tracking the dependencies between them. In some cases, the value of a
variable
may depend on a template, e.g., if <code>xsl:call-template</code> is
used to initialized
a variable whose type is RTF. If this happens, a
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
