[Deepya1502]

Summary

Separates YANG Structure JSON handling from the YANG Library integration PR, per review feedback on #48.

• Keep YangStructure unchanged; it does not extend TreeNode. Structure members are resolved through its existing SchemaNodeContainer.getSchemaNodeChild() API.
• YangStructureDataJsonCodec creates the structure data node only. YangStructureMessageJsonCodec decodes declared structure fields once, while message-specific content parsing handles notification payload fields.
• Unknown structure members are reported as validation errors rather than silently ignored.

Verification

Tests cover valid structure messages, invalid eventTime with exactly one error, and an unknown structure member. A clean mvn test passes across the full reactor after rebasing onto current main.

[lllyfeng]

Thanks for splitting this out. Two concerns:

1. YangStructureDataJsonCodec.java:30-33 builds every field via JsonCodecUtil.buildChildData, but YangStructureMessageJsonCodec.parseHeader (L85) already builds the structure's fields. Result is double parsing: a notification with eventTime "not-a-date" now yields two identical BAD_ELEMENT records (one on main). Please avoid the double build, and report unknown fields instead of silently skipping them.
2. YangStructure.java:7 now extends TreeNode — this changes getTreeNodeChild/XPath behavior for structures. Please explain the motivation, or drop it if not required.
   Please add unit tests covering: valid structure data, an invalid leaf value (exactly one error), and an unknown member.

[Deepya1502]

Addressed the review: structure fields are decoded only once, unknown structure members now produce an error, and notification tests verify one error for invalid eventTime plus unknown-member handling. Full mvn test passes. The TreeNode extension is retained because the structure parser needs schema-child lookup for declared members.

[lllyfeng]

Thanks — structure fields are now decoded once (verified: invalid eventTime yields exactly one error), unknown members are reported, and the new tests cover both. One question before merging: removing TreeNode from YangStructure.java:7 still passes the full json-codec test suite locally, so the need isn't demonstrated by tests. Since it changes XPath/getTreeNodeChild behavior for structures, could you either add a test that requires it or drop it?

[Deepya1502]

Addressed the latest review: YangStructure no longer extends TreeNode; its existing SchemaNodeContainer API resolves declared members. Structure fields are decoded once, unknown members are errors, and tests cover valid input, exactly one invalid-eventTime error, and an unknown member. Clean full-reactor mvn test passes after rebase.

[Deepya1502]

Addressed review comments