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

# JAXP 1.3 support: the XPath API

The classes that deliver the JAXP 1.3 XPath API have been moved to a separate JAR file, saxon8-xpath.jar. This need not be on the classpath (and therefore jaxp-api.jar need not be on the classpath) unless the application actually needs to use the free-standing JAXP XPath API.

To allow applications to use XPath expressions without requiring installation of JAXP 1.3, a new simple (but non-standard) XPath API has been introduced in package `net.sf.saxon.sxpath`. This is part of the standard `saxon8.jar` distribution. It is based on the design principles of the JAXP 1.3 API, but removes some features: it does not support variables or functions, and does not allow the result type to be set (you can control the result type by using casts or constructor functions within the XPath expression itself).

All references to JAXP 1.3 classes such as `javax.xml.namespace.QName` have been removed from the main body of the `saxon8.jar` code, to remove installation problems under JDK 1.4. Many of these references were not really needed, for example they were used to represent error codes within the XPathException object.

The Saxon class `StandaloneContext`, which can be used to set up the static context in the lower-level native API for evaluating XPath expressions, now allows the default namespace for elements and types to be set, by means of a new method `setDefaultElementNamespace()`.

Next