[YANGTOOLS-1421] Examine XML codec ordering in RPC/action input/output context Created: 05/Apr/22 Updated: 05/Jan/24 |
|
| Status: | Confirmed |
| Project: | yangtools |
| Component/s: | codecs |
| Affects Version/s: | None |
| Fix Version/s: | 14.0.0 |
| Type: | Task | Priority: | High |
| Reporter: | Robert Varga | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
RFC6020 and RFC7950 require container contents to be ordered in schema declaration order: The container's child nodes are encoded as subelements to the container element. If the container defines RPC or action input or output parameters, these subelements are encoded in the same order as they are defined within the "container" statement. Otherwise, the subelements are encoded in any order. Audit the XML codec to ensure we comply with this requirement when emitting NormalizedNode output. This may impact other statements as well. |