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-386) Define equality or 'sameness' of Tree objects
Date Fri, 19 Oct 2012 08:50:12 GMT

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

Michael Dürig commented on OAK-386:

Currently this is instance equality and I think we should leave it at that unless we can come
up with a sound definition of equality on {{Tree}}s that can be implemented efficiently enough
and a use case for it.
> Define equality or 'sameness' of Tree objects
> ---------------------------------------------
>                 Key: OAK-386
>                 URL: https://issues.apache.org/jira/browse/OAK-386
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>            Reporter: angela
> i think the Tree interface and implementation should define what exactly
> can be expected with regard to equality of 2 Tree objects. Since the
> tree is an oak-level correspondent of the jcr Node we may even take
> 'sameness' into consideration as it is defined by Item#isSame. That doesn't
> necessarily mean that we need this on the API but IMO the interface description
> should mention the contract (equality across repositories, sessions, workspaces...).

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