[YANGTOOLS-975] Define AnyxmlNode which is not tied to DOMSource Created: 27/Mar/19 Updated: 27/Mar/19 Resolved: 27/Mar/19 |
|
| Status: | Resolved |
| Project: | yangtools |
| Component/s: | data-impl |
| Affects Version/s: | None |
| Fix Version/s: | 3.0.0 |
| Type: | Improvement | 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 | ||
| Issue Links: |
|
||||||||
| Epic Link: | unlabeled-YANGTOOLS-929 | ||||||||
| Description |
|
AnyXmlNode is tightly coupled with DOMSource and it has a wrong name, it should be AnyxmlNode (with a lower-case x). Define an AnyxmlNode which will act as its replacement and will support various object models, which are discoverable from its instance. |
| Comments |
| Comment by Robert Varga [ 27/Mar/19 ] |
|
This work will include the intermediate type ForeignDataNode, which will be useful for AnydataNode support. |