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

["Ian Boston (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12893281#action_12893281 ] 

Ian Boston commented on SLING-1615:
-----------------------------------

Since one solution to this is a large re-factor of ModifyOperation I have uploaded a patch set

http://codereview.appspot.com/1842048

It creates a new Abstract parent class for both Modify and Import operatons, moving all the create related methods into that parent and then reuses them in Import to create the node that the POST targets.

> 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.