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

# Java API Changes

The `reset()` method has been implemented in Saxon's implementation of the JAXP `Transformer` class. This is designed to allow serial reuse of a Transformer. With Saxon, there is no benefit in reusing a transformer rather than creating a new one, unless you wish to reuse the document pool (the set of documents loaded using the `doc()` and `document()` functions. Therefore, this method does not clear the document pool. If you want to clear the document pool, call the `resetDocumentPool()` method as well.

It is now possible to register a `CollationURIResolver` with the `Configuration` (or, in XSLT, with the `TransformerFactory`) to resolve collation URIs used in a query or stylesheet, or in freestanding XPath expressions. If this is done, Saxon's collation URIs in the form `http://saxon.sf.net/collation?...` followed by query parameters are not recognized (however, the user-written collation URI resolver can invoke the default collation URI resolver to handle this format if it wishes.)

If an extension function returns an array, and some items in the array are null, Saxon now maps this to an XPath sequence in which the null items in the array are ignored. Previously this failed with the error "Object is null".

The type code returned by `NodeInfo.getTypeAnnotation()` may now include a bit indicating that the returned type is DTD-derived rather than schema-derived. This bit is also set when a type code is passed for an attribute node in the `Receiver` and `PullProvider` interfaces.

Next