Saxon parser license

Find centralized, trusted content and collaborate around the technologies you use most. Connect and share knowledge within a single location that is structured and easy to search. How does one achieve this programmatically? I also instantiated a net.

Transform , and that didn't have anything either. I am most likely looking at the wrong set of objects, but I don't know how I'm supposed to know what the correct set is. The command line documentation linked to above mentioned "Use specified SAX parser for source file and any files loaded using the document function. Unfortunately, I do not, and it does not.

Edit: Michael Kay's answer below is the correct one. Of course it is! He's the Saxon guy! I figured I'd add some sample code for future generations. In the above, it's important to supply it the fully-qualified name and not just the class name of the SAXParser as a String. By default, Saxon invokes the parser in non-validating mode that is, without requested DTD validation.

Note however, that the parser still needs to read the DTD if one is present, because it may contain entity definitions that need to be expanded. DTD validation can be requested using -dtd:on on the command line, or equivalent API or configuration options. When Saxon itself instantiates the XML parser, it will use an EntityResolver that causes these local copies of DTDs to be used rather than fetching public copies from the web the W3C servers are increasingly failing to serve these requests as the volume of traffic is too high.

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 xsl:result-document instruction; this filename acts as the base URI for the href attribute of this instruction. In the absence of this option, secondary output files are written relative to the current working directory.

The file is created if it does not already exist; any necessary directories will also be created. If the file does exist, it is overwritten even if the transformation fails ; but not if the transformation produces no principal result tree. Set optimization level. The value is an integer in the range 0 no optimization to 10 full optimization ; currently all values other than 0 result in full optimization but this is likely to change in future.

The default is full optimization; this feature allows optimization to be suppressed in cases where reducing compile time is important, or where optimization gets in the way of debugging, or causes extension functions with side-effects to behave unpredictably.

Note however, that even with no optimization, lazy evaluation may still cause the evaluation order to be not as expected. OutputURIResolver interface. Normally, if validation of result documents is requested, a validation error is fatal. Setting the option -outval:recover causes such validation failures to be treated as warnings. The validation message is written both to the standard error stream, and where possible as a comment in the result document itself. It cannot be used in conjunction with the -r option, and it automatically switches on the -u and -sa options.

The effect is twofold. Currently the only Saxon-specific file extension is. This is a binary representation of an XML document, designed for speed of loading. Secondly, Saxon-specific query parameters are recognized in a URI. Currently the only query parameter that is recognized is val. This may take the values strict , lax , or strip.

For example, source. With the default setting, on , the command will quit the Java VM and return an exit code if a failure occurs. This is useful when running from an operating system shell. With the setting quit:off the command instead throws a RunTimeException , which is more useful when the command is invoked from another Java application such as Ant. The URIResolver is a user-defined class, that extends the net.

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.

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. Identifies the source file or directory. Mandatory unless the -it option is used. The source file is parsed to create a tree, and the document node of this tree acts as the initial context item for the transformation.

If the name identifies a directory, all the files in the directory will be processed individually. In this case the -o option is mandatory, and must also identify a directory, to contain the corresponding output files. A directory must be specified as a filename, not as a URL. 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 -s flag, provided that the -it option is not present.

Invoke a schema-aware transformation. Requires Saxon-EE to be installed. This options is not needed if either a another option implying schema-awareness is present for example -val:strict or b the stylesheet contains an xsl:import-schema declaration.

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 document function. The default is ignorable : all ignorable whitespace is stripped. Whitespace text nodes are ignorable if they appear in elements defined in the DTD or schema as having element-only content.

Specifying all strips all whitespace text nodes from source documents before any further processing, regardless of any xsl:strip-space declarations in the stylesheet, or any xml:space attributes in the source document. Specifying ignorable strips all ignorable whitespace text nodes from source documents before any further processing, regardless of any xsl:strip-space declarations in the stylesheet, or any xml:space attributes in the source document. Specifying none suppresses all whitespace stripping unless requested elsewhere, for example using xsl:strip-space.

Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Java Saxon Parsing Ask Question. Asked 6 years, 7 months ago. Active 6 years, 7 months ago. Viewed times. Please share your valuable comments. Improve this question. Lathy Lathy 1 1 gold badge 8 8 silver badges 24 24 bronze badges. You can scan the directory and find what files were created, then assign them to their File handles. See: "How to scan a folder in Java" — Ceiling Gecko.