Saxon Documentation

Full Contents

About Saxon

Changes in this Release

Notices

Using XSLT 2.0

Using XQuery

Handling Source Documents

XML Schema Processing

XPath API for Java

Saxon on .NET

Extensibility
	Introduction
	Writing extension functions in Java
	Converting Arguments to Java Extension Functions
	Converting the Result of a Java Extension Function
	Writing extension functions for .NET
»	Converting Arguments to .NET Extension Functions
	Converting the Result of a .NET Extension Function
	Writing XSLT extension instructions
	Customizing Serialization
	Implementing a collating sequence
	Localizing numbers and dates
	Adding an output encoding
	Writing a URI Resolver for Input Files
	Writing a URI Resolver for Output Files

Saxon Extensions

Sample Saxon Applications

The Saxon SQL Extension

XSLT Elements

XPath 2.0 Expression Syntax

Function Library

Standards Conformance

Converting Nodes and Sequences of Nodes

If the expected type is a generic collection type, or an array of the Saxon class NodeInfo, or a Value or SequenceIterator, Saxon will pass the nodes supplied in the call in their native Saxon representation.

On the .NET platform, Saxon will not pass nodes to an extension function (or accept nodes returned by an extension function) in any other representation. For example, it does not pass or accept DOM nodes.