SAXONICA

Saxon Documentation
Full Contents
About Saxon
Changes in this Release
| 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
The XPath API
Saxon on .NET
Extensibility
Saxon Extensions
Sample Saxon Applications
The Saxon SQL Extension
XSLT Elements
XPath 2.0 Expression Syntax
Function Library
Standards Conformance

# JAXP API changes

The XPath API now offers schema-aware processing. By default, if Saxon-SA is on the classpath, the XPathFactory loaded to handle source documents using the Saxon object model will be schema-aware. Source documents loaded using the XPath evaluator from this factory will automatically be validated (failing if there is no available schema). A schema can be imported into the static context using the `importSchema` method of the `XPathEvaluator`. A sample application showing how this works in practice is provided: see `XPathExampleSA.java` in the `samples/java` directory.

The sample data file `books.xml` and its schema have been revised for the benefit of this sample application.

The Saxon implementations of the JAXP `SchemaFactory`, `Validator`, and `ValidatorHandler` interfaces now all support the methods `getProperty` and `setProperty` to set configuration options. The property names and values that can be set are the same as those provided on the `TransformerFactory` interface (where the methods are called `getAttribute` and `setAttribute`). These classes also now contain a `getConfiguration()` method providing direct access to the underlying `Configuration` object.

Next