jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-136) NodeDelegate leakage from NodeImpl
Date Mon, 13 Aug 2012 09:17:38 GMT

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

angela commented on OAK-136:

i will remove it again and refactor the user mgt to deal with Tree + Node not
making use of the NodeDelegate at all.
> NodeDelegate leakage from NodeImpl
> ----------------------------------
>                 Key: OAK-136
>                 URL: https://issues.apache.org/jira/browse/OAK-136
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: jcr
>            Reporter: Michael Dürig
>            Assignee: angela
> Since revision 1344662 NodeImpl has an (package private) accessor for NodeDelegate. This
defeats the original intent of the separation of NodeImpl and NodeDelegate (OAK-84): users
should not be able to gain access to internals by hacking NodeImpl. But precisely this is
now possible when a user put his code into the org.apache.jackrabbit.oak.jcr package.

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


View raw message