背景：

之前發(fā)過一篇文章

將NetConf轉(zhuǎn)成NormalizedNode對象及NormalizedNode對象轉(zhuǎn)回NetConf（序列化與反序列化）

請參考該文章的背景

該文章的不足之處在于

無論json還是xml文件都是完整的，但是實際的情況可能是不完整的。

想要將部分的json轉(zhuǎn)成NormalizedNode

第一步：建立Maven工程

<?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/4.0.0"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"><modelVersion>4.0.0</modelVersion><groupId>TestYangTools</groupId><artifactId>TestYangTools</artifactId><version>1.0-SNAPSHOT</version><dependencies><!--測試--><dependency><groupId>junit</groupId><artifactId>junit</artifactId><version>4.12</version></dependency><!--xml轉(zhuǎn)NormalizedNode--><dependency><groupId>org.opendaylight.yangtools</groupId><artifactId>yang-data-codec-xml</artifactId><version>2.0.16</version></dependency><!--讀取yang文件--><dependency><groupId>org.opendaylight.yangtools</groupId><artifactId>yang-test-util</artifactId><version>2.0.16</version></dependency><!--json轉(zhuǎn)NormalizedNode--><dependency><groupId>org.opendaylight.yangtools</groupId><artifactId>yang-data-codec-gson</artifactId><version>2.0.16</version></dependency><!--里面日志，如果不導(dǎo)入無法執(zhí)行--><dependency><groupId>org.slf4j</groupId><artifactId>slf4j-api</artifactId><version>1.7.7</version></dependency><dependency><groupId>org.opendaylight.netconf</groupId><artifactId>restconf-nb-rfc8040</artifactId><version>1.7.4</version></dependency><dependency><groupId>javax.ws.rs</groupId><artifactId>javax.ws.rs-api</artifactId><version>2.0.1</version></dependency></dependencies></project>

第二步：創(chuàng)建文件，編寫代碼

文件目錄如下，target是運行之后的結(jié)果

?（1）TestPartOfJson

import com.google.common.io.Resources; import com.google.gson.stream.JsonReader; import org.junit.Test; import org.opendaylight.controller.md.sal.dom.api.DOMMountPoint; import org.opendaylight.restconf.common.context.InstanceIdentifierContext; import org.opendaylight.restconf.nb.rfc8040.utils.parser.IdentifierCodec; import org.opendaylight.yangtools.yang.common.QName; import org.opendaylight.yangtools.yang.data.api.YangInstanceIdentifier; import org.opendaylight.yangtools.yang.data.api.schema.NormalizedNode; import org.opendaylight.yangtools.yang.data.api.schema.stream.NormalizedNodeStreamWriter; import org.opendaylight.yangtools.yang.data.codec.gson.JSONCodecFactorySupplier; import org.opendaylight.yangtools.yang.data.codec.gson.JsonParserStream; import org.opendaylight.yangtools.yang.data.impl.schema.ImmutableNormalizedNodeStreamWriter; import org.opendaylight.yangtools.yang.data.impl.schema.NormalizedNodeResult; import org.opendaylight.yangtools.yang.data.util.DataSchemaContextNode; import org.opendaylight.yangtools.yang.data.util.DataSchemaContextTree; import org.opendaylight.yangtools.yang.model.api.*; import org.opendaylight.yangtools.yang.model.util.SchemaContextUtil; import org.opendaylight.yangtools.yang.test.util.YangParserTestUtils;import java.io.ByteArrayInputStream; import java.io.IOException; import java.io.InputStream; import java.io.InputStreamReader; import java.nio.charset.StandardCharsets; import java.util.Iterator;public class TestPartOfJson {@Testpublic void jsonToNormalizedNodeTest() throws IOException {String uriPath = "baz:baz/my-container-1/my-leaf-1=value1";String jsonPath = "/baz/baz.json";String yangFilePath = "/baz/";SchemaContext schemaContext = YangParserTestUtils.parseYangResourceDirectory(yangFilePath);//第一步：構(gòu)建InstanceIdentifierContextInstanceIdentifierContext<?> instanceIdentifierContext = this.buildInstanceIdentifierContext(uriPath, schemaContext);//第二步：加載json文件String payload = loadData(jsonPath);InputStream entityStream = new ByteArrayInputStream(payload.getBytes(StandardCharsets.UTF_8));//第三步：獲取NormalizedNodeNormalizedNode normalizedNode = this.readFrom(instanceIdentifierContext, entityStream, false);//第四步：得到NormalizedNodeSystem.out.println("NormalizedNode:"+normalizedNode);}public NormalizedNode<?, ?> readFrom(final InstanceIdentifierContext<?> path, InputStream entityStream, final boolean isPost) {final NormalizedNodeResult resultHolder = new NormalizedNodeResult();final NormalizedNodeStreamWriter writer = ImmutableNormalizedNodeStreamWriter.from(resultHolder);final SchemaNode parentSchema;if (isPost) {parentSchema = path.getSchemaNode();} else if (path.getSchemaNode() instanceof SchemaContext) {parentSchema = path.getSchemaContext();} else {if (SchemaPath.ROOT.equals(path.getSchemaNode().getPath().getParent())) {parentSchema = path.getSchemaContext();} else {parentSchema = SchemaContextUtil.findDataSchemaNode(path.getSchemaContext(), path.getSchemaNode().getPath().getParent());}}final JsonParserStream jsonParser = JsonParserStream.create(writer,JSONCodecFactorySupplier.RFC7951.getShared(path.getSchemaContext()), parentSchema);System.out.println("jsonParser:"+jsonParser);final JsonReader reader = new JsonReader(new InputStreamReader(entityStream));jsonParser.parse(reader);NormalizedNode<?, ?> result = resultHolder.getResult();System.out.println("result:"+result);return result;}private static String loadData(final String path) throws IOException {return Resources.asCharSource(TestPartOfJson.class.getResource(path),StandardCharsets.UTF_8).read();}public InstanceIdentifierContext<?> buildInstanceIdentifierContext(final String identifier,final SchemaContext schemaContext) {YangInstanceIdentifier deserialize = IdentifierCodec.deserialize(identifier, schemaContext);DataSchemaContextNode<?> child = DataSchemaContextTree.from(schemaContext).getChild(deserialize);if (child != null) {return new InstanceIdentifierContext(deserialize, child.getDataSchemaNode(), (DOMMountPoint) null, schemaContext);} else {QName rpcQName = deserialize.getLastPathArgument().getNodeType();RpcDefinition def = null;Iterator var7 = ((Module) schemaContext.findModule(rpcQName.getModule()).get()).getRpcs().iterator();while (var7.hasNext()) {RpcDefinition rpcDefinition = (RpcDefinition) var7.next();if (rpcDefinition.getQName().getLocalName().equals(rpcQName.getLocalName())) {def = rpcDefinition;break;}}return new InstanceIdentifierContext(deserialize, def, (DOMMountPoint) null, schemaContext);}}}

(2)baz.json

{"my-leaf-1":"value1" }

?(3)baz.yang

module baz {namespace "baz";prefix baz;import yang-ext { prefix ext; revision-date 2013-07-09; }container baz {container my-container-1 {leaf my-leaf-1 {type string;}}container my-container-2 {container inner-container {leaf my-leaf-2 {type string;}}leaf my-leaf-3 {type string;}}anyxml my-anyxml-data {ext:anyxml-schema-location "/baz/my-container-2";}} }

(4)yang-ext.yang

module yang-ext {yang-version 1;namespace "urn:opendaylight:yang:extension:yang-ext";prefix "ext";contact "Anton Tkacik <ttkacik@cisco.com>";description"Copyright (c) 2013 Cisco Systems, Inc. and others. All rightsreserved. This program and the accompanying materials are madeavailable under the terms of the Eclipse Public License v1.0 whichaccompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html";revision "2013-07-09" {description "";}// Augmentation nameextension "augment-identifier" {description"YANG language extension which assigns an identifier to augmentation.Augment identifier is used to identify specific augment statementby name. The identifier syntax is defined formally defined bythe rule 'identifier' in Section 12 of RFC 6020. All augment identifiersdefined in a namespace MUST be unique. The namespace of augmentidentifiers is shared by module and its submodules.";/*Discussion:This extension allows for ease of development / debugof YANG modules and it is suitable for code generation,where each augment statement is nicely identified byunique name instead of combination of augment targetand when condition.*/argument "identifier";}// Context-aware RPCsgrouping rpc-context-ref {description"A reference to RPC context.";leaf context-instance {type instance-identifier;description "Pointer to the context. ";}}extension "rpc-context-instance" {description"YANG language extension which defines enclosing (parent) schemanode as referencable context for RPCs. The argument is identitywhich is used to identify RPC context type.";argument "context-type";}extension "context-reference" {argument "context-type";}extension "context-instance" {argument "context-type";}extension "instance-target" {argument "path";}extension "anyxml-schema-location" {argument "target-node";} }

第三步：運行結(jié)果

?

?

總結(jié)

以上是生活随笔為你收集整理的Json格式的netconf转成NormalizedNode的全部內(nèi)容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網(wǎng)站內(nèi)容還不錯，歡迎將生活随笔推薦給好友。