Deprecated API

Contents

• Deprecated Methods
• Deprecated Constructors

Deprecated Methods

Method and Description
net.sf.saxon.query.StaticQueryContext.buildDocument(Source) since 9.2: use Configuration.buildDocument(javax.xml.transform.Source)
net.sf.saxon.s9api.XsltCompiler.declareCollation(String, Collator) since 9.6. Collations are now held globally. If this method is called, the effect is to update the pool of collations held globally by the Processor.
net.sf.saxon.s9api.XQueryCompiler.declareCollation(String, Collator) since 9.6. Collations are now held globally. If this method is called, the effect is to update the pool of collations held globally by the Processor.
net.sf.saxon.s9api.XPathCompiler.declareCollation(String, Collator) since 9.6. Collations are now held globally at the level of the Processor (in fact, at the level of the Processor's underlying Configuration, which can in principle be shared by multiple Processors). If this method is called, the effect will be to reset the relevant collation at the global Configuration level.
net.sf.saxon.query.StaticQueryContext.declareCollation(String, Comparator) since 9.6. All collations are now registered at the level of the Configuration. If this method is called, the effect is that the supplied collation is registered with the configuration
net.sf.saxon.query.StaticQueryContext.declareCollation(String, StringCollator) since 9.6. All collations are now registered at the level of the Configuration. If this method is called, the effect is that the supplied collation is registered with the configuration
net.sf.saxon.sxpath.AbstractStaticContext.declareCollation(String, StringCollator, boolean) since 9.6. All collations are now registered at the level of the Configuration. If this method is called, the effect is (a) the supplied collation is registered with the configuration, and (b) if isDefault=true, the collation becomes the default collation for this static context
net.sf.saxon.expr.StaticContext.getCollation(String) since 9.6. Collations are now all held globally at the level of the Configuration. Calling this method will get the relevant collation held in the Configuration.
net.sf.saxon.query.StaticQueryContext.getCollation(String) since 9.6. Collations are now all held globally at the level of the Configuration. Calling this method will get the relevant collation held in the Configuration.
net.sf.saxon.query.QueryModule.getCollation(String) since 9.6. All collations are now registered at the level of the Configuration.
net.sf.saxon.style.ExpressionContext.getCollation(String) since 9.6. All collations are now registered at the level of the Configuration. If this method is called, the effect is (a) the supplied collation is registered with the configuration, and (b) if isDefault=true, the collation becomes the default collation for this static context
net.sf.saxon.sxpath.AbstractStaticContext.getCollation(String) since 9.6. Collations are now all held globally at the level of the Configuration. Calling this method will get the relevant collation held in the Configuration.
com.saxonica.ee.schema.UserDefinedType.getLocalName() since 9.0: use the equivalent method UserDefinedType.getName()
com.saxonica.ee.schema.AttributeDecl.getNamespace() since 9.0: use the renamed method getTargetNamespace()
net.sf.saxon.Controller.getTreeModel() since 9.2: use Controller.getModel()
net.sf.saxon.lib.AugmentedSource.getTreeModel() since 9.2: use AugmentedSource.getModel()
net.sf.saxon.s9api.XdmItem.newAtomicValue(String, ItemType) since 9.1. This factory method duplicates the constructor XdmAtomicValue.XdmAtomicValue(String, ItemType) which should be used in preference
net.sf.saxon.value.DurationValue.normalizeDuration() since 9.0 - the method does nothing
net.sf.saxon.dom.DocumentBuilderImpl.parse(InputSource) 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.
net.sf.saxon.query.QueryResult.serialize(NodeInfo, Result, Properties, Configuration) since 8.9; use QueryResult.serialize(NodeInfo, Result, Properties) instead.
net.sf.saxon.Controller.setTreeModel(int) since 9.2: use Controller.setModel(net.sf.saxon.om.TreeModel)
net.sf.saxon.lib.AugmentedSource.setTreeModel(int) since 9.2: use AugmentedSource.setModel(net.sf.saxon.om.TreeModel)

Deprecated Constructors

Constructor and Description
net.sf.saxon.s9api.Serializer() since Saxon 9.6: use Processor.newSerializer() instead
net.sf.saxon.s9api.Serializer(File) since Saxon 9.6: use Processor.newSerializer(File) instead
net.sf.saxon.s9api.Serializer(OutputStream) since Saxon 9.6: use Processor.newSerializer(OutputStream) instead
net.sf.saxon.s9api.Serializer(Writer) since Saxon 9.6: use Processor.newSerializer(Writer) instead
net.sf.saxon.query.StaticQueryContext(Configuration) since 9.2. Use config.newStaticQueryContext(). This will create a StaticQueryContext with capabilities appropriate to the configuration (for example, offering XQuery 1.1 support).
net.sf.saxon.expr.XPathContextMajor(Item, Configuration) since 9.0 - use XPathContextMajor.XPathContextMajor(Item, Executable)