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

Arthur Taylor updated SLING-1073:
---------------------------------

    Description: 
When uploading a file to the location of an existing file, the 
SlingFileUploadHandler removes the old node before creating the new one. That's 
sometimes necessary, for example in the cases where a typeHint is provided for 
the upload that differs from the type of the existing node, but it's not always 
required. The current behaviour prevents us maintaining a version history for 
uploaded resources.

I'll attach a patch for this in a sec.

  was:
When uploading a file to the location of an existing file, the 
SlingUploadManager removes the old node before creating the new one. That's 
sometimes necessary, for example in the cases where a typeHint is provided for 
the upload that differs from the type of the existing node, but it's not always 
required. The current behaviour prevents us maintaining a version history for 
uploaded resources.

I'll attach a patch for this in a sec.


> SlingFileUploadHandler removes any existing nodes, preventing file upload 
> versioning
> ------------------------------------------------------------------------------------
>
>                 Key: SLING-1073
>                 URL: https://issues.apache.org/jira/browse/SLING-1073
>             Project: Sling
>          Issue Type: Improvement
>          Components: Servlets Post
>            Reporter: Arthur Taylor
>         Attachments: patch.txt
>
>
> When uploading a file to the location of an existing file, the 
> SlingFileUploadHandler removes the old node before creating the new one. 
> That's sometimes necessary, for example in the cases where a typeHint is 
> provided for the upload that differs from the type of the existing node, but 
> it's not always required. The current behaviour prevents us maintaining a 
> version history for uploaded resources.
> I'll attach a patch for this in a sec.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to