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] [Comment Edited] (OAK-391) Avoid weak references in TreeImpl
Date Thu, 01 Nov 2012 15:59: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 edited comment on OAK-391 at 11/1/12 3:58 PM:
------------------------------------------------------------

As follow up we should 
* review/refactor the way {{Tree.getStatus}} and {{Tree.getPropertyStatus}} are implemented
(OAK-417),
* review/refactor {{Node/Property/ItemDelegate}} since resolving the underlying tree location
on each access shouldn't be necessary any more (OAK-418).
                
      was (Author: mduerig):
    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
>             Fix For: 0.6
>
>
> 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
http://markmail.org/message/b6dcyae362akyogd.

--
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