Use RFC7951 JSON format 95/103195/2
authorRobert Varga <robert.varga@pantheon.tech>
Thu, 10 Nov 2022 15:31:40 +0000 (16:31 +0100)
committerRobert Varga <nite@hq.sk>
Thu, 10 Nov 2022 16:21:22 +0000 (16:21 +0000)
We should be standards-compliant, switch to using RFC7951 JSON format
instead of the legacy one.

Change-Id: I8c79f6ba8d15720201be5bf338fe539cae5fdf66
Signed-off-by: Robert Varga <robert.varga@pantheon.tech>
netconf/tools/netconf-testtool/src/main/java/org/opendaylight/netconf/test/tool/PayloadCreator.java

index cfd53fa713886b6df9aa675ccc13d2f41d0165cb..eb38992f1ea913e72ecdda9bf678baffd215a6cd 100644 (file)
@@ -42,7 +42,7 @@ final class PayloadCreator {
     private static final EffectiveModelContext NETWORK_TOPOLOGY_SCHEMA_CONTEXT =
         BindingRuntimeHelpers.createEffectiveModel(List.of($YangModuleInfoImpl.getInstance()));
     private static final JSONCodecFactory NETWORK_TOPOLOGY_JSON_CODEC_FACTORY =
-        JSONCodecFactorySupplier.DRAFT_LHOTKA_NETMOD_YANG_JSON_02.getShared(NETWORK_TOPOLOGY_SCHEMA_CONTEXT);
+        JSONCodecFactorySupplier.RFC7951.getShared(NETWORK_TOPOLOGY_SCHEMA_CONTEXT);
 
     private static final QName TOPOLOGY_ID_QNAME = QName.create(Topology.QNAME, "topology-id").intern();
     private static final QName NODE_ID_QNAME = QName.create(Node.QNAME, "node-id").intern();