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-1019 netconf <p>As explified in <a href="https://jira.opendaylight.org/browse/NETCONF-1018" title="NetconfNotification confuses its namespace" class="issue-link" data-issue-key="NETCONF-1018"><del>NETCONF-1018</del></a>, constants get easily confused, especially when held together with similar constants with a different use – just as we do in XmlNetconfConstants.</p> <p><a href="https://jira.opendaylight.org/browse/NETCONF-1017" title="Centralize NETCONF capability URNs" class="issue-link" data-issue-key="NETCONF-1017"><del>NETCONF-1017</del></a> creates CapabilityURN as holder class for URNs used in the context of NETCONF Capabilities. Create NamespaceURN as holder class for URNs used in the context of XML namespaces.</p> <p>This should make use of constants more steamlined and hopefully will help catching day-0 bugs during code review.</p> NETCONF-1019

Create NamespaceURN constant holder

Task Medium Resolved Done Robert Varga Robert Varga pt Fri, 5 May 2023 23:02:21 +0000 Sat, 6 May 2023 12:22:38 +0000 Sat, 6 May 2023 12:22:38 +0000 6.0.0 netconf 0 1 <p>A quick examination shows that restconf-nb is using the namespace constants as well – which means we are reaping the benefits of <a href="https://jira.opendaylight.org/browse/NETCONF-892" title="Reorganize NETCONF source code repository" class="issue-link" data-issue-key="NETCONF-892"><del>NETCONF-892</del></a>/<a href="https://jira.opendaylight.org/browse/NETCONF-944" title="Reorganize source code layout" class="issue-link" data-issue-key="NETCONF-944">NETCONF-944</a> and are actually finding commonalities.</p> <p>NamespaceURN is leading the way, and it should be defined at protocol layer. Create a new component, protocols/netconf-common and a corresponding feature (odl-netconf-common), to host these definitions.</p> <p>Going forward, as we disaggregate restconf-nb (which has no protocols/ or plugins/ presence), we are sure to find more concepts that as shared.</p> <p>A note on naming: just as netconf.git reflects the fact that both NETCONF and RESTCONF come from IETF's NETCONF Working Group, so does 'netconf-common' – with "NETCONF Working Group" being implied here. At the end of the day we have expected this sort of outcome from the get to, it is just now that we start taking advantage of the commonalities.</p> Relates NETCONF-1017 NETCONF-1018 Development Rank 0|i0451b: