[
https://issues.apache.org/jira/browse/SLING-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594143#action_12594143
]
Carsten Ziegeler commented on SLING-412:
----------------------------------------
Yes, I think this is what needs to be fixed. Imagine I export node "A" which
has a "name" property with value "B". My json of the export looks like this:
{
"name":"B"
}
Importing this by putting it into a file named "A.json" results in a new node
named "B".
I think we should use an artifical property which is not allowed as a real
property name, like we do in the sling post servlets (where we use ":name")
> 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.
