SAXONICA |
A command is available to apply a given stylesheet to a given source XML document. For simple transformations on the Java platform, use the command:
java net.sf.saxon.Transform -s:source -xsl:stylesheet -o:output
where source, stylesheet, and output are the source XML file, the XSLT stylesheet, and the output file respectively.
For the .NET platform, the command is simply:
Transform -s:source -xsl:stylesheet -o:output
For a schema-aware transformation, specify the option -sa
, or (on the
Java platform only) use the alternate entry point com.saxonica.Transform
.
For more details see Schema-Aware Transformations.
For backwards compatibility with previous releases, the prefixes "-s:" and "-xsl:" can be omitted provided that the source document and the stylesheet are the last two options before any keyword=value parameters.
More generally, the arguments consist of a number of options prefixed with "-", then optionally (for backwards compatibility) the source filename and/or stylesheet filename, then a number of parameters provided as keyword=value pairs. The options must come first, then the file names if present, then the parameters.
For this to work, all the necessary Java components must be available on the classpath. See Installation for details of how to set up the classpath.
If you are are not using any additional Java libraries, you can use the simpler form of command:
java -jar dir/saxon9.jar [options] [params]
Note, however, that this does not work if you need to load user-written extension functions or other classes from the classpath. It will therefore not work if your stylesheet uses extension functions, or if you are using other modules such as the Saxon JDOM or XOM interfaces. It also does not work if you are using Saxon-SA, because the license file needs to be on the classpath.
The options are as follows (in any order):
-a |
Use the xml-stylesheet processing instruction in the source document to identify the stylesheet to be used. The stylesheet argument must not be present on the command line. |
-c:filename |
Indicates that the a compiled stylesheet is to be loaded from the given filename.
The stylesheet must have been previously compiled as
described in Compiling a Stylesheet. If this option is used then the
|
-cr:classname |
Use the specified CollectionURIResolver to process collection URIs passed to the
|
-dtd:(on|off) |
Setting |
-expand:(on|off) |
Normally, if validation using a DTD or Schema is requested, any fixed or default values defined in the DTD or schema will be expanded. Specifying -expand:off suppresses this. (This might not work with all XML parsers) |
-explain[:filename] |
Display an execution plan for the stylesheet. This is a representation of the expression tree after rewriting by the optimizer. It compbines the XSLT instructions and the XPath expressions into a single tree. If no file name is specified the output is sent to the standard error stream. The output is a tree in XML format. |
-ext:(on|off) |
If |
-im:modename |
Selects the initial mode for the transformation. If this is namespaced, it can be
written as |
-it:template |
Selects the initial named template to be executed. If this is namespaced, it can be
written as |
-l[:(on|off)] |
If |
-m:classname |
Use the specified Receiver to process the output from xsl:message. The class must implement
the The sequence of calls to this Receiver is as follows: there is a single Select the class |
-o:filename |
Send output to named file. In the absence of this option, the results go to standard output.
If the source argument identifies a directory, this option is mandatory and must also identify
a directory; on completion it will contain one output file for each file in the source directory.
If the stylesheet writes secondary output files using the |
-or:classname |
Use the specified OutputURIResolver to process output URIs appearing in the |
-outval:(recover|fatal) |
Normally, if validation of result documents is requested, a validation error is fatal. Setting
the option |
-p[:(on|off)] |
Use the PTreeURIResolver. This option is available in Saxon-SA only. It cannot be used in conjunction
with the -r option, and it automatically switches on the -u and -sa options. The effect is twofold. Firstly, Saxon-specific
file extensions are recognized in URIs (including the URI of the source document on the command line). Currently
the only Saxon-specific file extension is |
-r:classname |
Use the specified URIResolver to process all URIs. The URIResolver is a user-defined class, that extends the net.sf.saxon.URIResolver class, whose function is to take a URI supplied as a string, and return a SAX InputSource. It is invoked to process URIs used in the document() function, in the xsl:include and xsl:import elements, and (if -u is also specified) to process the URIs of the source file and stylesheet file provided on the command line. |
-repeat:integer |
Performs the transformation N times, where N is the specified integer. This option is useful for performance measurement, since timings for the first transformation are often dominated by Java warm-up time. |
-s:filename |
Identifies the source file or directory. Mandatory unless the If the name identifies a directory, all the
files in the directory will be processed individually. In this case the The source-document can be specified as "-" to take the source from standard input. For backwards compatibility the source filename can also be specified immediately before the
stylesheet filename, without the |
-sa |
Invoke a schema-aware transformation. Requires Saxon-SA to be installed. |
-strip:(all|none|ignorable) |
Specifies what whitespace is to be stripped from source documents (applies both to the principal source
document and to any documents loaded for example using the Specifying Specifying |
-t |
Display version and timing information to the standard error output. The output also traces the files that are read and writing, and extension modules that are loaded. |
-T[:classname] |
Display stylesheet tracing information. This traces execution of each instruction in the stylesheet, so the output can be quite voluminous. Also switches line numbering on for the source document. If a classname is specified, it is a user-defined class, which must implement net.sf.saxon.trace.TraceListener. If the classname is omitted, a system-supplied trace listener is used. For performance profiling, set classname to |
-TJ |
Switches on tracing of the binding of calls to external Java methods. This is useful when analyzing why Saxon fails to find a Java method to match an extension function call in the stylesheet, or why it chooses one method over another when several are available. |
-tree:[linked|tiny] |
Selects the implementation of the internal tree model. -tree:tiny the "tiny tree" model (the default). -tree:linked selects the linked tree model. See Choosing a tree model. |
-u |
Indicates that the names of the source document and the stylesheet document are URLs; otherwise they are taken as filenames, unless they start with "http:" or "file:", in which case they are taken as URLs |
-val[:(strict|lax)] |
Requests schema-based validation of the source file and of any files read using the document()
or similar functions. This option is available only with Saxon-SA, and it automatically switches on the
-sa option. Specify |
-versmsg:[on|off] |
If versmsg:off is specified, suppress version warnings.
This suppresses the warning message that is normally issued
(as required by the W3C specification) when running an XSLT 2.0 processor against a stylesheet
that specifies |
-warnings:[silent|recover|fatal] |
Indicates the policy for handling recoverable errors in the stylesheet: |
-x:classname |
Use specified SAX parser for source file and any files loaded using the document() function. The parser must be the fully-qualified class name of a Java class that implements the org.xml.sax.Parser or org.xml.sax.XMLReader interface |
-xi |
Apply XInclude processing to all input XML documents (including schema and stylesheet modules as well as source documents). This currently only works when documents are parsed using the Xerces parser, which is the default in JDK 1.5 and later. |
-xsl:filename |
Specifies the file containing the principal stylesheet module. Mandatory unless the -a option or -c option is used; for backwards compatibility the stylesheet can also be specified as the last option before the parameters, without the preceding "-xsl:". The value "-" identifies the standard input stream. If the -u option is specified then the value must be a URI rather than a filename. |
-y:classname |
Use specified SAX parser for stylesheet file, including any loaded using xsl:include or xsl:import. The parser must be the fully-qualified class name of a Java class that implements the org.xml.sax.Parser or org.xml.sax.XMLReader interface |
-xmlversion:[1.0|1.1] |
If |
-? |
Display command syntax |
stylesheet |
Identifies the stylesheet. Mandatory unless the |
The following options are also available for backwards compatibility, but are likely
to be withdrawn at some time in the future. Also, where previous releases allowed an option and
a value to be separated by a space rather than a colon (for example -r uriresolver
),
this syntax should still work for the time being.
-ds | -dt |
|
-l |
Switches line numbering on for the source document. Line numbers are accessible through the extension function saxon:line-number(), or from a trace listener. |
-noext |
Equivalent to |
-novw |
Equivalent to |
-sall |
Equivalent to |
-signorable |
Equivalent to |
-snone |
Equivalent to |
-TL classname |
Equivalent to |
-TP |
Equivalent to |
-v |
Equivalent to |
-val |
Equivalent to |
-vlax |
Equivalent to |
-vw |
Equivalent to |
-w0, w1, or w2 |
Equivalent to |
-1.1 |
Equivalent to |
A param takes the form name=value
, name being the
name of the parameter, and value the value of the parameter. These parameters are
accessible within the stylesheet as normal variables, using the $name
syntax, provided
they are declared using a top-level xsl:param
element. If there is no such declaration, the supplied
parameter value is silently ignored. If the xsl:param
element has an as
attribute indicating the required type, then the string value supplied on the command line is cast
to this type: this may result in an error, for example if an integer is required and the supplied value
cannot be converted to an integer.
A param preceded by a leading exclamation mark (!) is interpreted as an output parameter.
For example, !indent=yes
requests indented output. This is equivalent to specifying
the attribute indent="yes"
on an xsl:output
declaration in the stylesheet.
An output parameter specified on the command line overrides one specified within the stylesheet.
A param preceded by a leading plus sign (+) is interpreted as a filename or directory.
The content of the file is parsed as XML, and the resulting document node is passed to the stylesheet
as the value of the parameter. If the parameter value is a directory, then all the immediately contained
files are parsed as XML, and the resulting sequence of document nodes is passed as the value of the
parameter. For example, +lookup=lookup.xml
sets the value of the stylesheet parameter
lookup
to the document node at the root of the tree representing the parsed contents
of the file lookup.xml
.
Under most operating systems it is possible to supply a value containing
spaces by enclosing it in double quotes, for example name="John Smith"
. This is a feature
of the operating system shell, not something Saxon does, so it may not work the
same way under every operating system or command processor. (In the jEdit console plugin, for example,
it has to be written as "name=John Smith"
)
If the parameter name is in a non-null namespace, the parameter can be given a value using
the syntax {uri}localname=value
. Here uri
is the namespace URI of the
parameter's name, and localname
is the local part of the name.
This applies also to output parameters. For example, you can set the indentation level to 4 by
using the parameter !{http://saxon.sf.net/}indent-spaces=4
. See also
Additional attributes for xsl:output.
If the -a
option is used, the name of the stylesheet is
omitted. The source document must contain a <?xml-stylesheet?>
processing instruction
before the first element start tag; this processing instruction must have a pseudo-attribute href
that
identifies the relative or absolute URL of the stylsheet document, and a pseudo-attribute type whose
value is text/xml
, application/xml
, or text/xsl
. For example:
<?xml-stylesheet type="text/xsl" href="../style3.xsl" ?>
It is also possible to refer to a stylesheet embedded within the source document, provided it has an id attribute and the id attribute is declared in the DTD as being of type ID. For example:
<?xml-stylesheet type="text/xsl" href="#style1" ?>
<!DOCTYPE BOOKLIST SYSTEM "books.dtd"
<!ATTLIST xsl:transform id ID #IMPLIED>
<
<BOOKLIST>
...
<xsl:transform id="style1" version="1.0" xmlns:xsl="...">
...
</xsl:transform>
</BOOKLIST>