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-357 mdsal <p><a href="https://tools.ietf.org/html/rfc7952" class="external-link" target="_blank" rel="nofollow noopener">https://tools.ietf.org/html/rfc7952</a> defines a way to forward metadata attached to YANG-modeled data.</p> <p>This has multiple uses, mostly revolving about cross-cutting concerns like AAA. Furthermore it allows us to enrich data with things like event time - which is useful for notifications.</p> <p>Explore and implement a solution which allows such metadata to be tracked.</p> MDSAL-357

RFC7952 metadata should be transported over MD-SAL

Epic Medium Confirmed Unresolved Unassigned Robert Varga Thu, 28 Jun 2018 23:40:17 +0000 Tue, 9 Jan 2024 09:13:53 +0000 14.0.0 Binding codegen Binding runtime DOM runtime 0 1 <p>While we do have AnnotationAware interface, the solution is not complete, as we have leaf-equivalents which cannot have this interface attached:</p> <ul> <li>unrestricted leaf types (which boil down to final java.lang objects)</li> <li>restricted leaf types, i.e. TypeObjects (which boil down to java.lang.Enums) and which would need <a href="https://jira.opendaylight.org/browse/MDSAL-90" title="Simple type derivation relationship lost when binding DTO is translated to DOM and back." class="issue-link" data-issue-key="MDSAL-90">MDSAL-90</a>/<a href="https://jira.opendaylight.org/browse/MDSAL-440" title="Reconsider TypeObject equals()/hashCode()" class="issue-link" data-issue-key="MDSAL-440"><del>MDSAL-440</del></a> resolved to allow AnnotationAware subclassing</li> <li>leaf-lists of the above</li> </ul> <p>An obvious solution would be to generate metadataFoo() counterparts to getFoo() methods, but this feels like an overkill. It also does not quite align with leaf-lists, as we will end up disconnecting related data into two Lists – and we'd need empty metadata instances for leaf-list entries which do not have metadata (which is a minor annoyance).</p> <p>The secondary problem is transporting metadata across builders and similar – if the metadata object is detached, copy builders break down. This is probably okay, as metadata is not data and hence it probably should not be automatically transportable.</p> Blocks YANGTOOLS-961 Development Epic Color ghx-label-3 Epic Name Add metadata awareness Epic Status Rank 0|i03g7z: