jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] [Commented] (OAK-599) PropertyDelegate uses TreeImpl.PropertyLocation
Date Thu, 31 Jan 2013 10:01:13 GMT

    [ https://issues.apache.org/jira/browse/OAK-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567495#comment-13567495
] 

Michael Dürig commented on OAK-599:
-----------------------------------

An obvious solution would be to add a {{PropteryLocation}} interface. However this would suffer
the same leakage of security information as reported in OAK-598. 

I thus suggest to promote {{PropertyLoction.set(PropertyState)}} up to the {{TreeLocationInterface}}
where it will be an error when it is called on a non property location, a non accessible location
or an non existing location.
                
> PropertyDelegate uses TreeImpl.PropertyLocation
> -----------------------------------------------
>
>                 Key: OAK-599
>                 URL: https://issues.apache.org/jira/browse/OAK-599
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>            Reporter: angela
>            Priority: Minor
>
> the property delegate uses TreeImpl.PropertyLocation in order to call
> set() which is not provided by the TreeLocator interface.
> IMO oak-jcr should only operate on the oak api and not cast to 
> implementations.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message