[
https://issues.apache.org/jira/browse/SLING-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ian Boston resolved SLING-1615.
-------------------------------
Resolution: Fixed
Applied patch having left for comments.
passes build, integration tests and downstream integration tests with no impact.
> When importing content all the nodes to the parent node must exists, whereas
> a Sling POST creates the node.
> -----------------------------------------------------------------------------------------------------------
>
> Key: SLING-1615
> URL: https://issues.apache.org/jira/browse/SLING-1615
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Affects Versions: JCR Contentloader 2.0.6
> Reporter: Ian Boston
> Assignee: Ian Boston
> Fix For: JCR ContentLoader 2.0.8
>
>
> If a POST with a that invokes the import operation is made to a path where
> the resource does not exist a 404 results.
> But if I do a normal Sling POST the node is created.
> This is inconsistent and requires http clients to make 2 posts where one
> would have worked.
> Perhaps the Import Operation should check to see of the resource is a
> NonExstingResource and create the path if not, at about line 88 of
> ImportOperation ?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
