-
Deprecated Interfaces
-
Deprecated MethodsMethodDescriptionsince 9.7: use
Configuration.buildDocumentTree(Source).since 9.7: useConfiguration.buildDocumentTree(Source, ParseOptions).since 9.7. UseConfiguration.getCollectionFinder()since 9.7. UseConfiguration.setCollectionFinder(CollectionFinder)since 9.8: use getParseOptions().setSpaceStrippingRule(AllElementsSpaceStrippingRule.getInstance())since 9.7. UseController.getCollectionFinder()since 9.7. UseController.setCollectionFinder(CollectionFinder)since 9.7.0.2since 9.7.0.2. In normal use this class feeds its output into aNamespaceReducerwhich 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 explicitStreamWriterToReceiver.writeNamespace(String, String)call to create the namespace declaration.since 9.7 - use the operands() iterator insteadsince 9.8 - use getParseOptions().getSpaceStrippingRules()since 9.8 - use getParseOptions().setSpaceStrippingRules()since 9.8. UseParseOptions.getSpaceStrippingRule()since Saxon 9.9: use one of the othergetReceivermethodssince 9.2: useConfiguration.buildDocumentTree(javax.xml.transform.Source)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 configurationsince 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 configurationsince 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.since 9.8.since 9.8.since 9.9 - useProcessor.getConfigurationProperty(Feature)since 9.9 - useProcessor.setConfigurationProperty(Feature, Object)in 9.8; the only XQuery version supported is "3.1", and any other value is ignored with a warning.since 9.7.0.1 - useXslt30Transformer.setGlobalContextItem(net.sf.saxon.s9api.XdmItem)since 9.8. Multiple packages may be supplied in the form of aPackageLibraryregistered with the underlyingCompilerInfo, or may be listed in the configuration file. Alternatively they can be imported explicitly (taking care over the order of importing) usingXsltCompiler.importPackage(XsltPackage).since 9.8. Multiple packages may be supplied in the form of aPackageLibraryregistered with the underlyingCompilerInfo, or may be listed in the configuration file. Alternatively they can be imported explicitly (taking care over the order of importing) usingXsltCompiler.importPackage(XsltPackage).Has no effect from Saxon 9.8.since 9.9.1.3. Use XsltCompiler.setTargetEdition() to define the target environment.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 contextsince 9.7 - useXPathDynamicContext.getCollectionFinder()since 9.7 - useXPathDynamicContext.setCollectionFinder(CollectionFinder)since 9.8 (always returns 30)since 9.8.0.2. Always now returns false. See bug 3278.since 9.7. Any extension function library set using this mechanism will not be available if the package is saved and reloaded.since 9.8.0.2. The method no longer has any effect. See bug 3278.since Saxon 9.8 (has no effect).since 9.9.0.2; always returns null.- retained for backwards compatibilitysince 9.9: useSequenceIterator.materialize()since 9.9: useSequenceIterator.materialize()
CollectionFinder.