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/YANGTOOLS-982 yangtools <p>The <a href="https://jira.opendaylight.org/browse/YANGTOOLS-960" title="Update NormalizedNodeStreamWriter interface" class="issue-link" data-issue-key="YANGTOOLS-960"><del>YANGTOOLS-960</del></a>/<a href="https://jira.opendaylight.org/browse/YANGTOOLS-961" title="Integrate NormalizedNodes with RFC7952 metadata/attributes" class="issue-link" data-issue-key="YANGTOOLS-961"><del>YANGTOOLS-961</del></a> migration failed to separate out metadata from plain XML attributes, potentially polluting metadata.</p> <p>A much cleaner solution is possible, though, by allowing yang-data-codec-xml exposing a specialized NormalizedNodeStreamWriterExtension, which will handle XML attributes in their native format – including namespace declaration, but omitting anything that matches a metadata annotation. Define the extension and implement in both in inbound and outbound directions.</p> <p> </p> YANGTOOLS-982

Split out XML attribute handling

Bug High Confirmed Unresolved Unassigned Robert Varga Fri, 12 Apr 2019 20:05:04 +0000 Fri, 5 Jan 2024 15:12:59 +0000 14.0.0 codecs 0 1 <p>So this is more complicated than it would seem, due to the fact RFC6241 has additional requirements on &lt;rpc/&gt; and &lt;rpc-reply/&gt;:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre> The &lt;rpc&gt; element has a mandatory attribute "message-id", which is a string chosen by the sender of the RPC that will commonly encode a monotonically increasing integer.</pre> </div></div> <p>and:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre> If additional attributes are present in an &lt;rpc&gt; element, a NETCONF peer MUST return them unmodified in the &lt;rpc-reply&gt; element. This includes any "xmlns" attributes.</pre> </div></div> <p>This effectively means we need to pay further attention here and have a back channel to pass such attributes and only in contexts that are appropriate (i.e. in rpc/rpc-reply attributes, but not others)</p> Blocks NETCONF-856 YANGTOOLS-981 Duplicate YANGTOOLS-1527 Development Rank 0|i03nhr: