since 9.3. The DOM created by this class is a DOM wrapper around
(typically) a Saxon Tiny Tree. There is little point in constructing such
an object. If the tree is primarily for use by Saxon XSLT and XQuery, it is
better to construct a Tiny Tree directly and omit the DOM wrapper; if it is
primarily for other DOM applications, it is better to construct a fully-
functional DOM using (for example) Apache Xerces.
since 9.2 This feature was dropped from the final XDM specification and will be dropped in a future
Saxon release. The facility is supported only in Saxon-EE. Use an XSD schema to define the attribute types instead.
since 9.3. The DOM created by this class is a DOM wrapper around
(typically) a Saxon Tiny Tree. There is little point in constructing such
an object. If the tree is primarily for use by Saxon XSLT and XQuery, it is
better to construct a Tiny Tree directly and omit the DOM wrapper; if it is
primarily for other DOM applications, it is better to construct a fully-
functional DOM using (for example) Apache Xerces.
since Saxon 8.9 - use the various method defined in the JAXP interface definition,
which allow a NodeInfo object to be supplied as the value of the Source argument
since 8.9. The preferred way to define options for the way in which source
documents are built is to use the class AugmentedSource for any
of the methods expecting a Source object.
since 9.0. This method is not present in the JAXP interface. Either use
the JAXP methods such as XPathExpressionImpl.evaluate(Object, QName), or use the Saxon XPath
API instead of JAXP.
since 9.0. This method is not present in the JAXP interface. Either use
the JAXP methods such as XPathExpressionImpl.evaluate(Object, QName), or use the Saxon XPath
API instead of JAXP.
since 9.0. Using this method is not thread-safe. Use a method instead
such as XPathExpressionImpl.evaluate(Object, QName) that allows the context node to be specified
as a parameter to the call.
since 9.2. Use config.newStaticQueryContext(). This will create a StaticQueryContext with
capabilities appropriate to the configuration (for example, offering XQuery 1.1 support).