• Home
• net.sf.saxon
• Saxon-HE
• 12.0
• source code
• package-info.java

×

Project download

Many resources are needed to download a project. Please understand that we have to compensate our server costs. Thank you in advance.
Project price only 1 $

You can buy this project and download/modify it how often you want.

net.sf.saxon.xpath.package-info Maven / Gradle / Ivy

////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
// Copyright (c) 2018-2023 Saxonica Limited
// This Source Code Form is subject to the terms of the Mozilla Public License, v. 2.0.
// If a copy of the MPL was not distributed with this file, You can obtain one at http://mozilla.org/MPL/2.0/.
// This Source Code Form is "Incompatible With Secondary Licenses", as defined by the Mozilla Public License, v. 2.0.
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

/**
 * 
This package is Saxon's implementation of the JAXP API designed for executing XPath 1.0 expressions
 * directly from a Java application. Saxon extends the interface to handle XPath 2.0, though if the application
 * makes extensive use of XPath 2.0 features, then the s9api interface offers a better fit
 * to the XPath 2.0 data model. The API can be used either in a free-standing
 * Java application (that is, where there is no XSLT stylesheet), or it can be
 * used from within Java extension functions called from XPath expressions within
 * a stylesheet.
 * 
The API itself is defined by JAXP 1.3, in interfaces such as javax.xml.xpath.XPath.
 * These interfaces are included in Java Standard Edition from JDK 1.5 onwards.
 * 
The interfaces provided by Saxon extend the JAXP 1.3 interfaces in various ways. There
 * are three reasons for this:
 * 

 * 
Saxon supports XPath 2.0 rather than 1.0
 * 
The package retains support for some interfaces that were provided before JAXP 1.3 was released.
 * (Most of these extensions have been deprecated for several releases, and most removed in Saxon 9.6).
 * 
There are methods that allow an escape into Saxon's more low-level APIs, needed by
 * anyone doing serious software integration.
 * 
 * 
For most applications the preferred interface is
 * the s9api {@link net.sf.saxon.s9api.XPathCompiler}
 */
package net.sf.saxon.xpath;