Do not use null input for discard-changes 56/103856/1
authorSangwook Ha <sangwook.ha@verizon.com>
Wed, 21 Dec 2022 18:27:10 +0000 (10:27 -0800)
committerRobert Varga <robert.varga@pantheon.tech>
Sun, 1 Jan 2023 14:07:48 +0000 (15:07 +0100)
commit7d08b6416b453fa746c9d125e3dc627e9e8c01d6
tree3ccbe44e5b1e198e70e685a57d952e7c2ee2dedb
parente1b977cac215f25e719e29cbaaf1756aca8bf644
Do not use null input for discard-changes

There is already a NormalizedNode defined in NetconfMessageTransformUtil
for the content of the 'discard-changes' RPC.

Use the static variable instead of 'null'. This would make message
transformation more robust and fix an error caused by an augmentation
to the RPC input while generating NetconfMessage.

JIRA: NETCONF-934
Change-Id: I38777313d74e92bd955248ceea78e765729d9259
Signed-off-by: Sangwook Ha <sangwook.ha@verizon.com>
(cherry picked from commit f3cd4750c64f9002940b3bf20ea6be47a14344c3)
(cherry picked from commit 7b62bfe36a7ce71c0952799b169b37df6c269f5e)
netconf/sal-netconf-connector/src/main/java/org/opendaylight/netconf/sal/connect/netconf/util/NetconfBaseOps.java
netconf/sal-netconf-connector/src/test/java/org/opendaylight/netconf/sal/connect/netconf/sal/NetconfDataTreeServiceImplTest.java
netconf/sal-netconf-connector/src/test/java/org/opendaylight/netconf/sal/connect/netconf/sal/tx/NetconfDeviceWriteOnlyTxTest.java