[
https://issues.apache.org/jira/browse/OAK-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13435243#comment-13435243
]
angela commented on OAK-220:
----------------------------
fine with me... as commented in OAK-212 having all those extra methods
on root looks a bit awkward to me. nevertheless i prefer having a
solution here and we may still refactor the API later on... given
the fact that we make use of jukka's NodeUtil all over the place in
oak i have the impression that we will add minor modifications here
or there... let's see how it evolves.
btw: accessing properties independent of the parent is also needed
for the the reference stuff... keeping jukka's proposal in mind i
defined the corresponding manager to return property-oak-paths.
> PropertyState can only be accessed from parent tree
> ---------------------------------------------------
>
> Key: OAK-220
> URL: https://issues.apache.org/jira/browse/OAK-220
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core
> Reporter: angela
>
> currently the oak api only allows to access a given property state from
> the parent tree. however the jcr api also allows to access properties
> directly from the session object (see also OAK-218) and we should/cannot not
> rely on the accessibility of the parent node.
> possible solutions include for example adding Root#getProperty(String path)
> in analogy to Root#getTree.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
