-
Deprecated ClassesClassDescriptionsince 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.
-
Deprecated FieldsFieldDescriptionuse SUPPRESS_INDENTATION (the output property has been adopted as a standard property in XSLT 3.0, it is no longer Saxon-specific)
-
Deprecated MethodsMethodDescriptionsince 9.2: use isLicensedFeature() insteadsince 9.2. Use
Configuration.makeLicensedConfiguration(java.lang.ClassLoader, java.lang.String)
instead.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.2: useController.getModel()
since 9.2: useController.setModel(net.sf.saxon.om.TreeModel)
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: useAugmentedSource.getModel()
since 9.2: useAugmentedSource.setModel(net.sf.saxon.om.TreeModel)
From Saxon 8.7, the methodDynamicQueryContext.setContextItem(Item)
is preferredsince 8.9; useQueryResult.serialize(NodeInfo, Result, Properties)
instead.since 9.2: useConfiguration.buildDocument(javax.xml.transform.Source)
since 9.0 - useStaticQueryContext.clearNamespaces()
since 9.1. This factory method duplicates the constructorXdmAtomicValue(String, ItemType)
which should be used in preferencesince 8.9 - useXPathExpression.iterate(net.sf.saxon.sxpath.XPathDynamicContext)
since 9.0 - the method does nothingsince Saxon 8.9 - useXPathEvaluator.compile(String)
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 argumentsince 8.9. The preferred way to define options for the way in which source documents are built is to use the classAugmentedSource
for any of the methods expecting aSource
object.since 9.0. This method is not present in the JAXP interface. Either use the JAXP methods such asXPathExpressionImpl.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 asXPathExpressionImpl.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 asXPathExpressionImpl.evaluate(Object, QName)
that allows the context node to be specified as a parameter to the call.since 9.0. This method is not present in the JAXP interface. The recommended way to get a sorted result is to use XQuery instead of XPath.
-
Deprecated ConstructorsConstructorDescriptionsince 9.0 - use
XPathContextMajor(Item, Executable)
since 9.2. Use config.newStaticQueryContext(). This will create a StaticQueryContext with capabilities appropriate to the configuration (for example, offering XQuery 1.1 support).