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

# XInclude support

Saxon now integrates XInclude processing, provided that the default Xerces parser supplied with JDK 1.5 or later is used. (XInclude is not currently supported on .NET)

XInclude processing may be enabled for all documents (source documents, stylesheets, and schemas) by using the `-xi` option on the command line for the `Transform`, `Query`, and `Validate` commands.

From the Java API, the equivalent is to call `setXInclude()` on the `Configuration` object, or to set the attribute denoted by `FeatureKeys.XINCLUDE` to `Boolean.TRUE` on the `TransformerFactory`.

XInclude processing can be requested at a per-document level by creating an `AugmentedSource` and calling its `setXIncludeAware()` method. The corresponding method is also recognized on Saxon's implementation of the JAXP `DocumentBuilderFactory`. When the `doc()` or `document()` or `collection()` function is called from an XPath expression, XInclude processing can be enabled by including `xinclude=yes` among the query parameters in the URI.

Next