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-375 mdsal <p>As a follow-up to <a href="https://jira.opendaylight.org/browse/MDSAL-374" title="Keyed list entry builders&#39; copy constructor checks for null key" class="issue-link" data-issue-key="MDSAL-374"><del>MDSAL-374</del></a>, make sure we do not instantiate the entry key eagerly, but rather postpone its instantiation to when it is actually requested.</p> <p>This means the accessor needs to be thread-safe and we need to check that all constituent fields are initialized to non-null - otherwise we need to throw an IllegalStateException.</p> MDSAL-375

Do not store duplicate keyed list entry fields

Improvement Low Confirmed Unresolved Unassigned Robert Varga Wed, 10 Oct 2018 16:33:17 +0000 Mon, 3 Aug 2020 14:05:52 +0000 Binding codegen 0 1 <p>As an alternative we can continue to calculate the key eagerly, but then not generate fields for key constituents and generate their getters as forwarders, i.e. we store their values only in the key object.</p> <p>I think that is a better solution.</p> Blocks MDSAL-374 Development Rank 0|i03jhj: