[jira] Updated: (SLING-1615) When importing content all the nodes to the parent node must exists, whereas a Sling POST creates the node.

["Justin Edelson (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Edelson updated SLING-1615:
----------------------------------

        Fix Version/s: Servlets Post 2.0.6
                           (was: JCR ContentLoader 2.0.8)
    Affects Version/s:     (was: JCR Contentloader 2.0.6)
          Component/s: Servlets
                           (was: JCR)

> 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: Servlets
>            Reporter: Ian Boston
>            Assignee: Ian Boston
>             Fix For: Servlets Post 2.0.6
>
>
> 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.