SAXONICA

Saxon Documentation
Full Contents
About Saxon
Changes in this Release
| Version 8.9 (2007-02-12)
| Version 8.8 (2006-09-05)
| Version 8.7.3 (2006-06-13)
| Version 8.7.2 (2006-04-19)
| Version 8.7.1 (2006-04-13)
| Version 8.7 (2006-02-24)
| Version 8.6.1 (24 November 2005)
| Version 8.6 (3 November 2005)
» | Version 8.5.1 (26 August 2005)
| Version 8.5 (2 August 2005)
| Version 8.4 (4 April 2005)
| Version 8.3 (11 February 2005)
| Version 8.2 (21 December 2004)
| Version 8.1.1 (8 October 2004)
| Version 8.1 (24 September 2004)
| Version 8.0 (1 June 2004)
Conditions of Use
Using XSLT 2.0
Using XQuery
Handling Source Documents
XML Schema Processing
XPath API for Java
Saxon on .NET
Extensibility
Saxon Extensions
Sample Saxon Applications
The Saxon SQL Extension
XSLT Elements
XPath 2.0 Expression Syntax
Function Library
Standards Conformance

# JAXP API

For conformance with JAXP, the method `getURIResolver()` on the `Controller` class (Saxon's implementation of the JAXP `Transformer`) has changed so that if no user-specified `URIResolver` has been defined, the method returns null. Previously it returned the system default `URIResolver`.

In the JAXP XPath API, when the XPath expression is applied to a DOM Node, and the result requested is of type `NODESET`, the `evaluate()` method now attempts to return the result as a DOM `NodeList` object. If the result of the expression contains values that are not nodes, then it will return a Java List as before.

Comparison of `xs:duration` values using the less-than and greater-than operators (or by sorting) is no longer supported.

Next