[SLING-2035] Import does not properly handle replace import

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Servlets Post 2.1.0
• Fix Version/s: Servlets Post 2.1.2
• Component/s: Servlets
• Assignee: Felix Meschberger
• Reporter: Felix Meschberger
• Created: 28/Mar/11 12:51
• Updated: 20/Sep/17 12:04
• Resolved: 28/Mar/11 13:19

Description

Importing (system view) content has several flaws:

(1) if :name request parameter is given and a node exists of that name the request fails with a RepositoryException. Rather the request should either replace the existing node (if the :replace request parameter is true) or terminate the request with a 412/PRECONDITION FAILED otherwise

(2) If the import operation replaces an existing node, the request is actually not a creation request but a modification request. The response status should thus (in case of success) be 200/OK and not 201/CREATED.