https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/MDSAL-696 mdsal <p>DerivableSchemaNode.getOriginal() is used by mdsal-binding-runtime-api and mdsal-binding-generator to resolve original statement backwards along the instantiation axis.</p> <p>Since BindingRuntimeContext is driven by state from GeneratorReactor and that has the capacity to resolve statement -&gt; generator relationships without DerivableSchemaNode (as demonstrated by <a href="https://jira.opendaylight.org/browse/MDSAL-694" title="VerifyException thrown when resolving leafrefs with TAPI models" class="issue-link" data-issue-key="MDSAL-694"><del>MDSAL-694</del></a>), we should be able to do our job there without relying on YANG parser giving us these hints.</p> <p>Analyze the code and its intent and remodel it so that callers of BindingRuntimeContext.originalNodeOf() have everything they need to operate reasonably efficiently (based, again, on their callsites which should be mostly in mdsal-binding-dom-codec).</p> <p>Exactly how GeneratorReactor achieves is not quite clear yet, but it probably be similar to what <a href="https://jira.opendaylight.org/browse/MDSAL-695" title="Do not use AugmentationSchemaNode.getOriginalDefinition()" class="issue-link" data-issue-key="MDSAL-695"><del>MDSAL-695</del></a> ends up doing.</p> MDSAL-696

Do not use DerivableSchemaNode

Improvement High Resolved Done Robert Varga Robert Varga pt Fri, 15 Oct 2021 18:25:34 +0000 Wed, 9 Mar 2022 15:52:13 +0000 Tue, 8 Mar 2022 15:59:55 +0000 9.0.0 Binding codegen Binding runtime 0 1 <p>Analyzing the various accesses to BindingRutimeContext and its underlying BindingRuntimeTypes sheds a bit of light on this.</p> <p>So far it seems that BindingRuntimeTypes really wants to be a tree of RuntimeType instances, each of which provides lookup mechanism by Type and by schema tree (and/or perhaps data tree?) QNames to find child definitions. We already have grouping/augment dependencies available, all we need is to cross-reference them to design the appropriate lookup tables – which is exactly what AbstractExplicitGenerator.getOriginal() is supposed to provide.</p> Blocks YANGTOOLS-1377 Duplicate MDSAL-686 MDSAL-687 MDSAL-695 Relates MDSAL-697 YANGTOOLS-1403 MDSAL-694 MDSAL-695 MDSAL-724 Development Epic Link YANGTOOLS-1348 Rank 0|i0407z: