You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2010/09/23 09:36:32 UTC

[jira] Resolved: (SLING-1797) Looking for versionable ancestor may cause failure

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

Felix Meschberger resolved SLING-1797.
--------------------------------------

    Resolution: Fixed

Fixed in Rev. 1000343 : Refactor findVersionableAncestor to not break if any ancestor is not accessible and to operate iteratively instead of recursively

> Looking for versionable ancestor may cause failure
> --------------------------------------------------
>
>                 Key: SLING-1797
>                 URL: https://issues.apache.org/jira/browse/SLING-1797
>             Project: Sling
>          Issue Type: Bug
>          Components: Servlets
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: Servlets Post 2.0.6
>
>
> The AbstractSlingPostOperation.findVersionableAncestor method tries to find a versionable ancestor to the node to be modified during the request by repeatedly calling Item.getParent() until the root or a versionable node is reached.
> If the current request does not have access to an ancestor thus visited an AccessDeniedException is thrown by the getParent() method thus failing the POST request early and probably unrelated to any actually requested operation.
> Fix is to catch the AccessDeniedException and assume no versionable ancestor. If the operation then fails, it will fail due to the actual operation failing possibly because an ancestor which should be checked out.

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