Deprecated List (yangtools-docs 6.0.3 API)

For Removal
Element	Description
org.opendaylight.yangtools.yang.data.api.schema.NormalizedNodes.findNode(NormalizedNode<?, ?>, SchemaPath)	Use `NormalizedNodes.findNode(NormalizedNode, Descendant)` instead.
org.opendaylight.yangtools.yang.data.codec.binfmt.NormalizedNodeDataInput.newDataInputWithoutValidation(DataInput)	Use `NormalizedNodeDataInput.newDataInput(DataInput)` instead.
org.opendaylight.yangtools.yang.data.codec.binfmt.NormalizedNodeDataInput.readSchemaPath()
org.opendaylight.yangtools.yang.data.codec.binfmt.NormalizedNodeDataOutput.writeSchemaPath(SchemaPath)
org.opendaylight.yangtools.yang.model.api.DataNodeContainer.getDataChildByName(QName)	Use `DataNodeContainer.dataChildByName(QName)` or `DataNodeContainer.findDataChildByName(QName)` instead. This method will be repurposed to assert existence in the next major release.
org.opendaylight.yangtools.yang.model.parser.api.YangParser.buildSchemaContext()	Use `YangParser.buildEffectiveModel()` instead.
org.opendaylight.yangtools.yang.model.util.PathExpressionImpl	Users are advised to supply their own implementation of PathExpression.
org.opendaylight.yangtools.yang.parser.rfc7950.repo.YangModelDependencyInfo.forResource(Class<?>, String)	This method was used by testing framework and was deemed to be potentially useful to the outside world. With Java Platform Module System, though, the resource loading rules have changed to the point where we no longer can guarantee it working correctly, as the results depend on the resource path. Users are advised to use `YangModelDependencyInfo.forYangText(YangTextSchemaSource)`.
org.opendaylight.yangtools.yang.parser.spi.meta.StmtContextUtils.findFirstSubstatement(StmtContext<?, ?, ?>, Class<D>)	Use `StmtContext.findSubstatementArgument(Class)` instead.
org.opendaylight.yangtools.yang.parser.spi.meta.StmtContextUtils.producesDeclared(StmtContext<?, ?, ?>, Class<? extends DeclaredStatement<?>>)
org.opendaylight.yangtools.yang.parser.spi.SchemaNodeIdentifierNamespace	This namespace was never implemented. Its purpose is generalized in `SchemaTreeNamespace`.

Packages
Package Description

org.opendaylight.yangtools.yang.data.jaxen.api

Packages
Package	Description
org.opendaylight.yangtools.yang.data.jaxen.api

Interfaces
Interface	Description
org.opendaylight.yangtools.yang.data.jaxen.api.LazyXPathExpression	PREVIEW API. DO NOT IMPLEMENT YET AS THIS NEEDS TO BE VALIDATED FOR USE IN CLIENT APPLICATIONS. APPLICATIONS WILLING TO USE THIS API PLEASE CONTACT yangtools-dev.
org.opendaylight.yangtools.yang.data.jaxen.api.OptimizableXPathExpression
org.opendaylight.yangtools.yang.data.jaxen.api.RelocatableXPathExpression
org.opendaylight.yangtools.yang.data.jaxen.api.XPathBooleanResult
org.opendaylight.yangtools.yang.data.jaxen.api.XPathDocument
org.opendaylight.yangtools.yang.data.jaxen.api.XPathExpression
org.opendaylight.yangtools.yang.data.jaxen.api.XPathNodesetResult
org.opendaylight.yangtools.yang.data.jaxen.api.XPathNumberResult
org.opendaylight.yangtools.yang.data.jaxen.api.XPathResult
org.opendaylight.yangtools.yang.data.jaxen.api.XPathSchemaContext
org.opendaylight.yangtools.yang.data.jaxen.api.XPathSchemaContextFactory
org.opendaylight.yangtools.yang.data.jaxen.api.XPathStringResult
org.opendaylight.yangtools.yang.model.api.AddedByUsesAware	This interface relates to declared model rather than to effective mode and as such should not exist. It is provided to provide common method definition and eash migration of users.
org.opendaylight.yangtools.yang.model.api.CopyableNode	Aside from the deprecated `AddedByUsesAware` contract, this interface adds only a trait related to now how we arrived at this effective node. Users who need to know this information should really be looking at the `DeclaredStatement` world, which holds the original node definition.
org.opendaylight.yangtools.yang.parser.rfc7950.namespace.URIStringToImportPrefix	Use `ModuleQNameToPrefix` instead.
org.opendaylight.yangtools.yang.parser.spi.SchemaNodeIdentifierNamespace	This namespace was never implemented. Its purpose is generalized in `SchemaTreeNamespace`.
org.opendaylight.yangtools.yang2sources.spi.BasicCodeGenerator	Use `FileGenerator` instead.
org.opendaylight.yangtools.yang2sources.spi.BuildContextAware	Use `FileGenerator` instead.
org.opendaylight.yangtools.yang2sources.spi.MavenProjectAware	Use `FileGeneratorFactory` instead.
org.opendaylight.yangtools.yang2sources.spi.ModuleResourceResolver	Use `ModuleResourceResolver` instead.

Classes
Class	Description
org.opendaylight.yangtools.yang.data.jaxen.api.PrefixConverters
org.opendaylight.yangtools.yang.model.util.PathExpressionImpl	Users are advised to supply their own implementation of PathExpression.
org.opendaylight.yangtools.yang.model.util.type.CompatUtils	This class is provided strictly for compatibility only. No new users should be introduced, as this class is scheduled for removal when its two OpenDaylight users, Java Binding v1 and YANG JMX Bindings are removed.

Exceptions
Exceptions	Description
org.opendaylight.yangtools.yang.data.jaxen.api.LazyXPathExpressionException	PREVIEW API. DO NOT IMPLEMENT YET AS THIS NEEDS TO BE VALIDATED FOR USE IN CLIENT APPLICATIONS. APPLICATIONS WILLING TO USE THIS API PLEASE CONTACT yangtools-dev.

Fields
Field	Description
org.opendaylight.yangtools.yang.data.codec.xml.XmlParserStream.LEGACY_ATTRIBUTE_NAMESPACE	The use on this namespace is discouraged and users are strongly encouraged to proper RFC7952 metadata annotations.
org.opendaylight.yangtools.yang.parser.antlr.IfFeatureExpressionLexer.tokenNames	Use `IfFeatureExpressionLexer.VOCABULARY` instead.
org.opendaylight.yangtools.yang.parser.antlr.IfFeatureExpressionParser.tokenNames	Use `IfFeatureExpressionParser.VOCABULARY` instead.
org.opendaylight.yangtools.yang.parser.antlr.LeafRefPathLexer.tokenNames	Use `LeafRefPathLexer.VOCABULARY` instead.
org.opendaylight.yangtools.yang.parser.antlr.LeafRefPathParser.tokenNames	Use `LeafRefPathParser.VOCABULARY` instead.
org.opendaylight.yangtools.yang.parser.antlr.YangStatementLexer.tokenNames	Use `YangStatementLexer.VOCABULARY` instead.
org.opendaylight.yangtools.yang.parser.antlr.YangStatementParser.tokenNames	Use `YangStatementParser.VOCABULARY` instead.
org.opendaylight.yangtools.yang.parser.rfc7950.reactor.YangValidationBundles.SUPPORTED_DEVIATION_TARGETS	This is an implementation leak from statement support and will be removed in next major version.
org.opendaylight.yangtools.yang.xpath.antlr.instanceIdentifierLexer.tokenNames	Use `instanceIdentifierLexer.VOCABULARY` instead.
org.opendaylight.yangtools.yang.xpath.antlr.instanceIdentifierParser.tokenNames	Use `instanceIdentifierParser.VOCABULARY` instead.
org.opendaylight.yangtools.yang.xpath.antlr.xpathLexer.tokenNames	Use `xpathLexer.VOCABULARY` instead.
org.opendaylight.yangtools.yang.xpath.antlr.xpathParser.tokenNames	Use `xpathParser.VOCABULARY` instead.

Methods
Method	Description
org.opendaylight.yangtools.odlext.parser.AnyxmlSchemaLocationEffectiveStatementImpl.getPath()
org.opendaylight.yangtools.yang.data.api.schema.NormalizedNodes.findNode(NormalizedNode<?, ?>, SchemaPath)	Use `NormalizedNodes.findNode(NormalizedNode, Descendant)` instead.
org.opendaylight.yangtools.yang.data.api.YangInstanceIdentifier.NodeIdentifierWithPredicates.asMap()	This method in a provisional one. It can be used in the code base, but users requiring it should contact yangtools-dev for migration guidelines. Callers are strongly encouraged to explore `YangInstanceIdentifier.NodeIdentifierWithPredicates.entrySet()`, `YangInstanceIdentifier.NodeIdentifierWithPredicates.size()`, `YangInstanceIdentifier.NodeIdentifierWithPredicates.values()` and `YangInstanceIdentifier.NodeIdentifierWithPredicates.keySet()` as an alternative.
org.opendaylight.yangtools.yang.data.api.YangInstanceIdentifier.NodeIdentifierWithPredicates.of(QName, SharedSingletonMap<QName, Object>)
org.opendaylight.yangtools.yang.data.codec.binfmt.NormalizedNodeDataInput.newDataInputWithoutValidation(DataInput)	Use `NormalizedNodeDataInput.newDataInput(DataInput)` instead.
org.opendaylight.yangtools.yang.data.codec.binfmt.NormalizedNodeDataInput.readSchemaPath()
org.opendaylight.yangtools.yang.data.codec.binfmt.NormalizedNodeDataOutput.writeSchemaPath(SchemaPath)
org.opendaylight.yangtools.yang.data.util.OperationAsContainer.getPath()
org.opendaylight.yangtools.yang.data.util.OperationAsContainer.isAddedByUses()
org.opendaylight.yangtools.yang.data.util.OperationAsContainer.isAugmenting()
org.opendaylight.yangtools.yang.model.api.DataNodeContainer.getDataChildByName(QName)	Use `DataNodeContainer.dataChildByName(QName)` or `DataNodeContainer.findDataChildByName(QName)` instead. This method will be repurposed to assert existence in the next major release.
org.opendaylight.yangtools.yang.model.api.QNameModuleAware.getNamespace()
org.opendaylight.yangtools.yang.model.api.SchemaContext.findAction(QName)
org.opendaylight.yangtools.yang.model.api.SchemaContext.getActions()
org.opendaylight.yangtools.yang.model.api.SchemaContext.getAvailableAugmentations()
org.opendaylight.yangtools.yang.model.api.SchemaContext.getDescription()
org.opendaylight.yangtools.yang.model.api.SchemaContext.getMustConstraints()
org.opendaylight.yangtools.yang.model.api.SchemaContext.getPath()
org.opendaylight.yangtools.yang.model.api.SchemaContext.getQName()
org.opendaylight.yangtools.yang.model.api.SchemaContext.getReference()
org.opendaylight.yangtools.yang.model.api.SchemaContext.getStatus()
org.opendaylight.yangtools.yang.model.api.SchemaContext.getUses()
org.opendaylight.yangtools.yang.model.api.SchemaContext.getWhenCondition()
org.opendaylight.yangtools.yang.model.api.SchemaContext.isAddedByUses()
org.opendaylight.yangtools.yang.model.api.SchemaContext.isAugmenting()
org.opendaylight.yangtools.yang.model.api.SchemaContext.isConfiguration()
org.opendaylight.yangtools.yang.model.api.SchemaNode.getPath()	The idea of identifying SchemaNodes through a global path does not work. There are two problems: SchemaPath does not work because it does not discern namespaces, i.e. we do not known whether the `QName` refers to a `grouping`, a `typedef` or a `container`. Such a path needs to be maintained by each SchemaNode and requires us to instantiate each effective statement as a separate object (because `SchemaNode.getPath()` is effectively an identity within a given `EffectiveModelContext`.
org.opendaylight.yangtools.yang.model.export.YinExportUtils.writeModuleAsYinText(Module, OutputStream)	Prefer `YinExportUtils.writeModuleAsYinText(ModuleEffectiveStatement, OutputStream)`.
org.opendaylight.yangtools.yang.model.export.YinExportUtils.writeSubmoduleAsYinText(Module, Submodule, OutputStream)	Prefer `YinExportUtils.writeSubmoduleAsYinText(ModuleEffectiveStatement, SubmoduleEffectiveStatement, OutputStream)`.
org.opendaylight.yangtools.yang.model.parser.api.YangParser.buildSchemaContext()	Use `YangParser.buildEffectiveModel()` instead.
org.opendaylight.yangtools.yang.model.util.SchemaContextUtil.findDataSchemaNode(SchemaContext, Module, PathExpression)	Use `SchemaContextUtil.findDataTreeSchemaNode(SchemaContext, QNameModule, YangLocationPath)` or `SchemaContextUtil.findDataTreeSchemaNode(SchemaContext, QNameModule, PathExpression)` instead.
org.opendaylight.yangtools.yang.model.util.SchemaInferenceStack.toSchemaPath()	This method is meant only for interoperation with SchemaPath-based APIs.
org.opendaylight.yangtools.yang.parser.antlr.IfFeatureExpressionLexer.getTokenNames()
org.opendaylight.yangtools.yang.parser.antlr.IfFeatureExpressionParser.getTokenNames()
org.opendaylight.yangtools.yang.parser.antlr.LeafRefPathLexer.getTokenNames()
org.opendaylight.yangtools.yang.parser.antlr.LeafRefPathParser.getTokenNames()
org.opendaylight.yangtools.yang.parser.antlr.YangStatementLexer.getTokenNames()
org.opendaylight.yangtools.yang.parser.antlr.YangStatementParser.getTokenNames()
org.opendaylight.yangtools.yang.parser.rfc7950.repo.YangModelDependencyInfo.forResource(Class<?>, String)	This method was used by testing framework and was deemed to be potentially useful to the outside world. With Java Platform Module System, though, the resource loading rules have changed to the point where we no longer can guarantee it working correctly, as the results depend on the resource path. Users are advised to use `YangModelDependencyInfo.forYangText(YangTextSchemaSource)`.
org.opendaylight.yangtools.yang.parser.rfc7950.stmt.refine.RefineEffectiveStatementImpl.getPath()
org.opendaylight.yangtools.yang.parser.rfc7950.stmt.refine.RefineEffectiveStatementImpl.getQName()
org.opendaylight.yangtools.yang.parser.rfc7950.stmt.UnknownEffectiveStatementBase.isAddedByUses()
org.opendaylight.yangtools.yang.parser.rfc7950.stmt.UnknownEffectiveStatementBase.isAugmenting()
org.opendaylight.yangtools.yang.parser.spi.meta.ModelActionBuilder.mutatesNs(StmtContext.Mutable<?, ?, ?>, Class<N>)	Undocumented method. Use at your own risk.
org.opendaylight.yangtools.yang.parser.spi.meta.ModelActionBuilder.requiresDeclared(StmtContext<?, ?, ?>, Class<N>, K)	Undocumented method. Use at your own risk.
org.opendaylight.yangtools.yang.parser.spi.meta.ModelActionBuilder.requiresDeclaredCtx(StmtContext<?, ?, ?>, Class<N>, K)	Undocumented method. Use at your own risk.
org.opendaylight.yangtools.yang.parser.spi.meta.ModelActionBuilder.requiresEffective(StmtContext<?, ?, ? extends E>)	Undocumented method. Use at your own risk.
org.opendaylight.yangtools.yang.parser.spi.meta.ModelActionBuilder.requiresEffectiveCtx(StmtContext<?, ?, ?>, Class<N>, K)	Undocumented method. Use at your own risk.
org.opendaylight.yangtools.yang.parser.spi.meta.StmtContext.getSchemaPath()	Use of SchemaPath in the context of effective statements is going away. Consider not providing this information, if your users can exist without it.
org.opendaylight.yangtools.yang.parser.spi.meta.StmtContextUtils.findFirstSubstatement(StmtContext<?, ?, ?>, Class<D>)	Use `StmtContext.findSubstatementArgument(Class)` instead.
org.opendaylight.yangtools.yang.parser.spi.meta.StmtContextUtils.producesDeclared(StmtContext<?, ?, ?>, Class<? extends DeclaredStatement<?>>)
org.opendaylight.yangtools.yang.parser.stmt.reactor.RootStatementContext.getSchemaPath()
org.opendaylight.yangtools.yang.xpath.antlr.instanceIdentifierLexer.getTokenNames()
org.opendaylight.yangtools.yang.xpath.antlr.instanceIdentifierParser.getTokenNames()
org.opendaylight.yangtools.yang.xpath.antlr.xpathLexer.getTokenNames()
org.opendaylight.yangtools.yang.xpath.antlr.xpathParser.getTokenNames()

Constructors
Constructor	Description
org.opendaylight.yangtools.yang.parser.rfc7950.stmt.AbstractDeclaredStatement.WithArgument(StmtContext<A, ?, ?>)
org.opendaylight.yangtools.yang.parser.rfc7950.stmt.AbstractDeclaredStatement.WithArgument.WithSubstatements(StmtContext<A, ?, ?>, ImmutableList<? extends DeclaredStatement<?>>)
org.opendaylight.yangtools.yang.parser.rfc7950.stmt.AbstractDeclaredStatement.WithRawArgument(StmtContext<A, ?, ?>)
org.opendaylight.yangtools.yang.parser.rfc7950.stmt.AbstractDeclaredStatement.WithRawStringArgument(StmtContext<String, ?, ?>)
org.opendaylight.yangtools.yang.parser.rfc7950.stmt.AbstractDeclaredStatement.WithRawStringArgument.WithSubstatements(StmtContext<String, ?, ?>, ImmutableList<? extends DeclaredStatement<?>>)

Deprecated API

Contents