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

# Internal Changes

The `Loader` class has been removed, and its methods have become instance-level methods on the `Configuration` object. The `Configuration` has a new method `setClassLoader()` which can be used to set the `ClassLoader` that Saxon will use for all dynamic loading. There is another method of the same name on the `Controller` object, which applies locally to one transformation or query thread. This is designed to help prevent problems that arise in environments such as Eclipse that have their own customized class loader: when Eclipse loads a class using one class loader, and Saxon loads it using a different class loader, the class hierarchy is not fixed up properly and a `ClassCastException` can result.

The `info` argument to the `MappingFunction.map()` interface has been dropped. Instead, mapping functions that require context information are now implemented as classes that can be instantiated at run time and initialized with the relevant information. This is a cleaner design with better type safety, better control over thread-safety, and less overhead for mapping iterators that don't require this context information.

The code for wrapping a sequence (used with the XQuery -wrap option) has been refactored, so that it can now be used as a component on any push pipeline, and no longer requires the input sequence or output document to be built as an in-memory document.

Next