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 Extension Function Calling Mechanism

Changes have been made to the rules for calling Java extension functions.

The rules for selecting a Java extension function have been changed to align better with the standard function calling rules in XPath 2.0. The main impact is that fewer implicit type conversions are supported for the arguments. For example, if the Java method expects an integer, then it is not acceptable to supply a string. Similarly, if the Java method expects a single item, then you cannot supply a sequence of several items.

In addition, it must now be possible to identify a Java method uniquely at compile time, based on the static types of the supplied arguments. If there are several Java methods with the same name in the target class, it may be necessary to cast the supplied argument explicitly to ensure that enough information about the type of the argument is available statically.

If difficulties arise in binding extension functions, the -TJ option on the command line gives useful diagnostics.

Next