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/NETCONF-356 netconf <p>This enhancement has been asked for several times. One such example is in this email thread <span class="error">&#91;0&#93;</span>.</p> <p><span class="error">&#91;0&#93;</span> <a href="https://lists.opendaylight.org/pipermail/netconf-dev/2017-February/000934.html" class="external-link" target="_blank" rel="nofollow noopener">https://lists.opendaylight.org/pipermail/netconf-dev/2017-February/000934.html</a></p> <p>Operating System: All<br/> Platform: All</p> NETCONF-356

Provide an optional mode to parse NETCONF messages ignoring namespaces

New Feature Medium Confirmed Unresolved David Goldberg Ryan Goulding Tue, 28 Feb 2017 15:13:51 +0000 Mon, 4 May 2020 23:00:26 +0000 netconf 0 4 <p>I created a fix for this here:<br/> <a href="https://git.opendaylight.org/gerrit/#/c/52667/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/52667/</a></p> <p>That patch only ignores schemas with empty namespace from netconf-state, this bug is about parsing messages with empty namespace</p> <p><a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=gdavid%40hpe.com" class="user-hover" rel="gdavid@hpe.com">gdavid@hpe.com</a> any update to your patch? Are you still working on this?</p> <p>The original patch is merged, but to <a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=tcere" class="user-hover" rel="tcere">tcere</a>'s point, I don't know if it fully addresses parsing messages with<br/> empty namespaces. Also, the headline of this ticket mentions "optional mode" which makes me think the<br/> original feature request was intended with a config knob to enable/disable somehow. </p> Development External issue ID 7869 External issue URL Issue Type Rank 0|i01y1b: