[
https://issues.apache.org/jira/browse/SLING-10463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17359279#comment-17359279
]
Bertrand Delacretaz commented on SLING-10463:
---------------------------------------------
bq. a more conservative approach to the proposed patch would be to leave the
Session.itemExists but verify that it actually is a node and fail the repo-init
if it is a property.
I think this is less likely to cause surprises: repoinit would fail the
creation of a node with name N if its parent already has a property named N.
[[email protected]] would that behavior work for your use case?
> Repoinit fails to create node if property already exists at the same path
> -------------------------------------------------------------------------
>
> Key: SLING-10463
> URL: https://issues.apache.org/jira/browse/SLING-10463
> Project: Sling
> Issue Type: Bug
> Components: Repoinit
> Reporter: Tom Blackford
> Priority: Minor
> Attachments: SLING-10463.patch
>
>
> If a property already exists at the path of a node described in repoinit,
> then the repoinit will incorrectly assume the node does not need to be
> created.
> Test case & fix - [^SLING-10463.patch]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
