| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
Solution
| # | Solutions | Issues | |||
|---|---|---|---|---|---|
| 1 | Obtain the container from the xpath of the queried node. Node xpath will be Use the parent node xpath in order to wrap the queried leaves. eg query xpath = /bookstore/categories[@code='01'] where bookstore is the container name given in the module info.=> categories | This should be reasonably straightforward as the top level node is named after the container name given by the module yang file. | 2 | Create a query to obtain the schema node directly from the database using and propagate through persistence and service layers. | Would need to create a new query which would parse the json data from the yang_resource content and find the container name which is very memory intensive for its use case. Also would need to pass a new schema node object to the toDataMap method which would not be used every time which it is called. |
For the JSON output of Get DataNode we need to alter the DataMapUtils class. The function toDataMap translates a datanode object to a JSON output:
public static Map<String, Object> toDataMap(final DataNode dataNode) {
final boolean isTopLevelNode = dataNode.getXpath().lastIndexOf('/') == 0;
if (isTopLevelNode) {
String containerName = dataNode.getXpath().substring(1);
return ImmutableMap.<String, Object>builder().put(containerName,
ImmutableMap.<String, Object>builder()
.putAll(dataNode.getLeaves())
.putAll(listElementsAsMap(dataNode.getChildDataNodes()))
.putAll(containerElementsAsMap(dataNode.getChildDataNodes()))
.build()
).build();
} else {
return ImmutableMap.<String, Object>builder()
.putAll(dataNode.getLeaves())
.putAll(listElementsAsMap(dataNode.getChildDataNodes()))
.putAll(containerElementsAsMap(dataNode.getChildDataNodes()))
.build();
}
}
We only want the container name on the top level of the JSON output and as such have to distinguish between a top level node and non top level node. We create an outer map to wrap the inner map which creates the appropriate levels in the JSON output.
This produces the following response in the Post Request output:
{
"bookstore": {
"bookstore-name": "Easons",
"categories": [
{
"code": "01",
"name": "SciFi"
}
]
}
}
Tests would need to be updated to accept the new JSON output which is returned. Examples would need to be updated in openapi
...