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-391) Avoid weak references in TreeImpl
Date Thu, 01 Nov 2012 15:51:12 GMT

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

Michael Dürig commented on OAK-391:

As follow up we should 
* review/refactor the way {{Tree.getStatus}} and {{Tree.getPropertyStatus}} are implemented,
* review/refactor {{Node/Property/ItemDelegate}} since resolving the underlying tree location
on each access shouldn't be necessary any more.
> Avoid weak references in TreeImpl
> ---------------------------------
>                 Key: OAK-391
>                 URL: https://issues.apache.org/jira/browse/OAK-391
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>            Reporter: Jukka Zitting
> As discussed on oak-dev@, it would be good if we didn't need to use weak references in
TreeImpl. Instead we could leverage the state tracking mechanism in NodeBuilder. See also

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

View raw message