Deprecated API

Contents

• Deprecated Interfaces
• Deprecated Methods
• Deprecated Constructors

Deprecated Interfaces

Interface and Description
net.sf.saxon.lib.CollectionURIResolver since 9.7: use CollectionFinder.

Deprecated Methods

Method and Description
net.sf.saxon.Configuration.buildDocument(Source) since 9.7: use Configuration.buildDocumentTree(Source).
net.sf.saxon.query.StaticQueryContext.buildDocument(Source) since 9.2: use Configuration.buildDocumentTree(javax.xml.transform.Source)
net.sf.saxon.Configuration.buildDocument(Source, ParseOptions) since 9.7: use Configuration.buildDocumentTree(Source, ParseOptions).
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
com.saxonica.xslt3.instruct.ConditionalBlock.getChildren() since 9.7 - use the operands() iterator instead
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.Controller.getCollectionURIResolver() since 9.7. Use Controller.getCollectionFinder()
net.sf.saxon.Configuration.getCollectionURIResolver() since 9.7. Use Configuration.getCollectionFinder()
net.sf.saxon.sxpath.XPathDynamicContext.getCollectionURIResolver() since 9.7 - use XPathDynamicContext.getCollectionFinder()
net.sf.saxon.event.StreamWriterToReceiver.isInventPrefixes() since 9.7.0.2
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.Controller.setCollectionURIResolver(CollectionURIResolver) since 9.7. Use Controller.setCollectionFinder(CollectionFinder)
net.sf.saxon.Configuration.setCollectionURIResolver(CollectionURIResolver) since 9.7. Use Configuration.setCollectionFinder(CollectionFinder)
net.sf.saxon.sxpath.XPathDynamicContext.setCollectionURIResolver(CollectionURIResolver) since 9.7 - use XPathDynamicContext.setCollectionFinder(CollectionFinder)
net.sf.saxon.trans.CompilerInfo.setExtensionFunctionLibrary(FunctionLibrary) since 9.7. Any extension function library set using this mechanism will not be available if the package is saved and reloaded.
net.sf.saxon.s9api.Xslt30Transformer.setInitialContextNode(XdmNode) since 9.7.0.1 - use Xslt30Transformer.setInitialContextItem(net.sf.saxon.s9api.XdmItem)
net.sf.saxon.event.StreamWriterToReceiver.setInventPrefixes(boolean) since 9.7.0.2. In normal use this class feeds its output into a NamespaceReducer which performs the equivalent of "namespace repairing" or "prefix invention": that is, it ensures that when elements or attributes are written in a specific namespace, there is no need for an explicit StreamWriterToReceiver.writeNamespace(String, String) call to create the namespace declaration.

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).