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-70 mdsal <p>In Current Binding Specification v1 constructor for list key<br/> does not take arguments in order specified in YANG key statement, but rather in alphabetical order.</p> <p>This could be considered design bug, since several other drafts / specifications<br/> requires key values to be presented in same order as in yang model.</p> <p>Also YANG language requires for RPC element to be present in same order<br/> as in YANG model, so removing alphabetically sorted elements in favor<br/> of elements sorted as present in YANG model will provide easier understanding<br/> of Java Bidning and its mapping to YANG.</p> <p>Operating System: All<br/> Platform: All</p> MDSAL-70

Binding Specification: Constructor arguments do not preserve statement order as defined in YANG

Improvement Resolved Won't Do Unassigned Tony Tkacik Wed, 25 Feb 2015 10:46:56 +0000 Fri, 9 Jul 2021 21:57:57 +0000 Thu, 1 Mar 2018 10:31:08 +0000 Binding V2 codegen 0 3 <p>One key problem, though, can happen if someone decides to reorder leaf declarations between revisions ... that may end up mixing up the ordering, which may silent data mixups.</p> <p>Low priority and given the problems this will create across model revisions I don't think it's worth the hassle.</p> <p>As noted, inter-revision compatibility would silently be broken, hence we will not be fixing this.</p> Blocks MDSAL-237 Development External issue ID 2755 External issue URL Issue Type ODL SR Target Milestone Rank 0|i02w4n: