SAXONICA

Saxon Documentation
Full Contents
About Saxon
Changes in this Release
| Version 9.1 (2008-07-02)
» | Version 9.0 (2007-11-03)
Notices
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

# New Java API

A brand new Java API is available in package `net.sf.saxon.s9api` (pronounced "snappy", stands for Saxon 9 API). This is closely modelled on the successful .NET API. The design aims were to:

- Provide an API that is well documented and uncluttered by implementation detail

- Provide uniformity across XSLT, XPath, and XQuery (for example, allowing XSLT and XQuery to be combined naturally in a single pipeline)

- Maximise the ability to create compiled objects that are reusable across multiple threads

- Reuse existing JAXP classes and interfaces where appropriate, but abandon them when they no longer deliver the right functionality

- Provide an accurate representation of the XDM data model

- Provide access to all mainstream Saxon functionality needed by typical users

- Provide escape hatches to underlying implementation classes and methods for power users

- Exploit new Java 5 features such as type-safe enumerations, generics, and iterables, while retaining support for JDK 1.4 users

The new API does not replace any existing APIs: it is a separate layer on top of the Saxon product. It is provided in a separate JAR file, saxon9-api.jar, and can be used only with Java 5. The main Saxon jar files, however, continue to work with JDK 1.4.

For details see the Javadoc: go to package `net.sf.saxon.s9api` and start with the `Processor` class.

Saxon will continue to support standardized interfaces such as JAXP and XQJ. However, JAXP has become cluttered and inconsistent, and is still missing support for many XSLT 2.0 features. XQJ has been designed with a client-server architecture in mind, and while it is usable with Saxon, it is not really optimized for the kind of applications where Saxon is deployed. For users who want to exploit Saxon fully in their applications, rather than retaining portability across XSLT/XPath/XQuery implementations, the new API offers a much cleaner choice.

Next