[YANGTOOLS-929] Change the definition of AnyXmlNode to not use DOMSource Created: 17/Jan/19  Updated: 25/Mar/20  Resolved: 25/Mar/20

Status: Resolved
Project: yangtools
Component/s: data-impl
Affects Version/s: None
Fix Version/s: 5.0.0

Type: Epic Priority: Medium
Reporter: Robert Varga Assignee: Robert Varga
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

The design on AnyXmlNode requires users to perform some sort of translation to a DOMSource. Most of them are doing this eagerly, resulting in needless translations - such as NETCONF performing NormalizedNode -> DOM streaming for the purposes of creating a NormalizedNode structure.

Furthermore default org.w3c.DOM implementation is mutable, which does not sit well with immutable design of NormalizedNode.

Design a DOMSource-like extension mechanism, which allows an AnyXmlNode to be queried/ for its content in various (externally-defined) interfaces. For example YangModeledAnyXmlNode would expose the underlying schema via an accessor interface - potentially even pre-constructed NormalizedNode.

Finally this has a tie-in with YANGTOOLS-777, as AnyDataNode should use the same extension mechanism.


Generated at Wed Feb 07 20:54:42 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.