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

# API Changes on .NET

It is now possible to capture the output of `xsl:result-document` to any kind of `XmlDestination` by nominating a user-written instance of `IResultDocumentHandler`, which works in a similar way to the `OutputURIResolver` on Java.

Saxon 8.9 is built using IKVM 0.32.0.0, which introduces some changes to the way that dynamic loading works. This may affect stylesheets or queries that use dynamically loaded extension functions. The main impact is that it is no longer possible to load extension functions written in Java, other than functions implemented within Saxon, or functions that map to classes in the standard JDK class library as implemented in GNU Classpath. Calls to extension functions written in .NET languages are unaffected. For more details on dynamic loading in IKVM, see Jeroen Frijters' 9 Feb 2007 blog entry at http://weblog.ikvm.net/.

Next