[
https://issues.apache.org/jira/browse/SLING-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594186#action_12594186
]
Carsten Ziegeler commented on SLING-412:
----------------------------------------
I'm fine with removing this feature completly as well. There could only be the
case, when it is too difficult (not possible) to use the correct file name for
the json file; but so far I don't see this as a problem atm; we can fix this
when the problem arises.
> 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.
