Running XQuery from the Command Line

If you are using the schema-aware version of Saxon, there is a variant of this command line that invokes schema-aware processing: see Schema-Aware Query from the Command Line.

The Java class net.sf.saxon.Query has a main program that may be used to run a query contained in a file. The form of command is:

java  net.sf.saxon.Query   [options]   query   [ params...]

The options must come first, then the file name containing the query, then the params.

The options are as follows (in any order):

-ds

Use the classic tree model for source documents. See Choosing a Tree Model.

-dt

Use the "tinytree" tree model for source documents. This is the default tree model. See Choosing a Tree Model.

-noext

Prevents the query calling external Java functions. This is useful for safety if the query is untrusted.

-o filename

Send output to named file. In the absence of this option, the results go to standard output. The output format depends on whether the -wrap option is present.

-r classname

Use the specified URIResolver to process all URIs. The URIResolver is a user-defined class, that implements the URIResolver interface defined in JAXP, 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 doc() function, and (if -u is also specified) to process the URI of the source file provided on the command line.

-s filename-or-URI

Take input from the specified file. If the -u option is specified, or if the name begins with "file://" or "http://", then the name is assumed to be a URI rather than a filename. This file must contain an XML document. The document node of the document is made available to the query as the context item. The source document can be specified as "-" to take the source from standard input.

-strip

Strip all whitespace-only text nodes from source documents.

-t

Display version and timing information to the standard error output. The output also traces the files that are read and written, and extension modules that are loaded.

-T

Enable execution tracing. This will cause a trace of the query execution to be output to the standard error output. The events that are traced are currently function calls (entry and exit) and element construction.

-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.

-u

Indicates that the name of the source document is a URI; otherwise it is taken as a filename, unless it starts with "http:" or "file:", in which case they it is taken as a URL.

-val

This option is available only with the schema-aware version of the command, com.saxonica.Transform; it requests validation of source documents using an XML Schema.

-vw

Indicates that validation errors found when validting the result tree should be treated as warnings only. This option is available only with the Saxon-SA version of the command, com.saxonica.Transform.

-wrap

Wraps the result sequence in an XML element structure that indicates the type of each node or atomic value in the query result. This format can handle any type of query result. In the absence of this option, the command effectively wraps a document{} constructor around the supplied query, so that the result is a single XML document, which is then serialized. This will fail if the query result includes constructs that cannot be added to a document node in this way, notably free-standing attribute nodes.

-?

Display command syntax

query

Identifies the file containing the query. Mandatory. The argument can be specified as "-" to read the query from standard input. The query can also be specified inline by enclosing it in curly braces (if it contains spaces, you will also need quotes outside the curly braces to keep the command line processor happy). For example java net.sf.saxon.Query {doc('a.xml')//p[1]} selects elements within the file a.xml in the current directory.

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 query as external variables, using the $name syntax, provided they are declared in the query prolog. If there is no such declaration, the supplied parameter value is silently ignored. Not yet tested.

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 external variable lookup to the document node at the root of the tree representing the parsed contents of the file lookup.xml.

A param preceded by a leading exclamation mark is interpreted as a serialization parameter. For example, !indent=yes requests indented output, and !encoding=iso-8859-1 requests that the serialized output be in ISO 8859/1 encoding. This is equivalent to specifying the attribute indent="yes" or encoding="iso-8859-1" on an xsl:output declaration in an XSLT stylesheet.

Under Windows, and some other 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.

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. For the extended set of output parameters supported by Saxon, see extensions.html.

Expand

Next