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

# Changes to external Java bindings

When extension function calls map to polymorphic Java methods, the selection of the particular method to invoke is now delayed until after the type analysis of the expression tree has been done. This gives a better chance of identifying the required method from the static types of the supplied arguments.

Extension types (types returned by extension functions that do not relate to any type in the XPath type system) are now analysed when binding Java methods. This also improves the chances of binding polymorphic methods successfully.

The conversion of Java objects to XPath data types when supplied as stylesheet or query parameters now takes account of the declared type (at least to some extent). If the type is declared using a Java class for example `j:java.util.Date` where the namespace prefix `j` is bound to `http://saxon.sf.net/java-type`, then no conversion will take place, only checking that the supplied value is of the correct class. It is then possible to manage all conversions explicitly by calling Java methods on this object (represented as extension functions).

Next