You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2012/11/21 12:23:58 UTC
[jira] [Created] (OAK-460) Node#getDefinition and
Property#getDefinition depend on the accessibility of the parent node
angela created OAK-460:
--------------------------
Summary: Node#getDefinition and Property#getDefinition depend on the accessibility of the parent node
Key: OAK-460
URL: https://issues.apache.org/jira/browse/OAK-460
Project: Jackrabbit Oak
Issue Type: Bug
Components: jcr
Reporter: angela
currently the definition of a given item is obtained by reading the
node type information of the parent node and is thus relying on the
accessibility of the parent node. as discussed previously in other
occasions we cannot rely on this as access to the parent might be
denied.
in the long run we may want to think about a way on how to determine
the definition (or parts of the definition such as for example
information about the protection status) in the absence of the parent.
--
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
[jira] [Commented] (OAK-460) Node#getDefinition and
Property#getDefinition depend on the accessibility of the parent node
Posted by "angela (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OAK-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13501884#comment-13501884 ]
angela commented on OAK-460:
----------------------------
yes we need to worry about this a long as we don't have any other way
to determine the protected status of a given node than by accessing
the item definition... this is currently just added on top of JCR
API which will not work in the long run... in other words i think that
we need the ability to determine the characteristics of an item
on a deeper level that JCR... this is not limited to the protection
status. even internal calls that make decisions based on node type
characteristics just use JCR API to retrieve the corresponding
properties. this will not work once we have access control restrictions
being enforced.
> Node#getDefinition and Property#getDefinition depend on the accessibility of the parent node
> --------------------------------------------------------------------------------------------
>
> Key: OAK-460
> URL: https://issues.apache.org/jira/browse/OAK-460
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
> Reporter: angela
>
> currently the definition of a given item is obtained by reading the
> node type information of the parent node and is thus relying on the
> accessibility of the parent node. as discussed previously in other
> occasions we cannot rely on this as access to the parent might be
> denied.
> in the long run we may want to think about a way on how to determine
> the definition (or parts of the definition such as for example
> information about the protection status) in the absence of the parent.
--
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
[jira] [Commented] (OAK-460) Node#getDefinition and
Property#getDefinition depend on the accessibility of the parent node
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OAK-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13501889#comment-13501889 ]
Jukka Zitting commented on OAK-460:
-----------------------------------
Do you mean internal code in oak-jcr, or the plugins working through oak-core? The latter should be able to look at the underlying data without access limitations, while the former could for example just assume that everything's allowed if type details aren't available (the underlying commit hooks will in any case correct such assumptions where needed).
> Node#getDefinition and Property#getDefinition depend on the accessibility of the parent node
> --------------------------------------------------------------------------------------------
>
> Key: OAK-460
> URL: https://issues.apache.org/jira/browse/OAK-460
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
> Reporter: angela
>
> currently the definition of a given item is obtained by reading the
> node type information of the parent node and is thus relying on the
> accessibility of the parent node. as discussed previously in other
> occasions we cannot rely on this as access to the parent might be
> denied.
> in the long run we may want to think about a way on how to determine
> the definition (or parts of the definition such as for example
> information about the protection status) in the absence of the parent.
--
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
[jira] [Commented] (OAK-460) Node#getDefinition and
Property#getDefinition depend on the accessibility of the parent node
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OAK-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13501876#comment-13501876 ]
Jukka Zitting commented on OAK-460:
-----------------------------------
Do we need to worry about that? If it's not a big problem, I'd simply have {{getDefinition()}} throw an exception in such cases as the requested information is not available.
> Node#getDefinition and Property#getDefinition depend on the accessibility of the parent node
> --------------------------------------------------------------------------------------------
>
> Key: OAK-460
> URL: https://issues.apache.org/jira/browse/OAK-460
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
> Reporter: angela
>
> currently the definition of a given item is obtained by reading the
> node type information of the parent node and is thus relying on the
> accessibility of the parent node. as discussed previously in other
> occasions we cannot rely on this as access to the parent might be
> denied.
> in the long run we may want to think about a way on how to determine
> the definition (or parts of the definition such as for example
> information about the protection status) in the absence of the parent.
--
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