[
https://issues.apache.org/jira/browse/SLING-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12593918#action_12593918
]
Felix Meschberger commented on SLING-412:
-----------------------------------------
Do not quite understand this issue. It is true, the the "name" property is used
for the top level node. But for any lower level nodes, only the JSON object
name is used.
Probably the selection of the node name for the top level node in the
JsonReader.parse method should be modified.
Maybe this may be fixed in the Loader.createNode(Node, String, URL, boolean)
method which actually implements this behaviour for the top level node ?
> Inconsistent name handling when importing json stuff
> ----------------------------------------------------
>
> Key: SLING-412
> URL: https://issues.apache.org/jira/browse/SLING-412
> Project: Sling
> Issue Type: Bug
> Components: JSON
> Reporter: Carsten Ziegeler
> Fix For: 2.0.0
>
>
> The json importer looks for a property named "name" to use its value for a
> node name. Only if this is not available, the json object name is used as the
> node name.
> This is an inconsistent behaviour compared to a default json export. As soon
> as a node has a "name" property this value is used for the name. So exporting
> nodes with random name properties and importing same results in different
> node names.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
