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/10/18 20:28:05 UTC
[jira] [Created] (OAK-386) Define equality or 'sameness' of Tree
objects
angela created OAK-386:
--------------------------
Summary: 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
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
[jira] [Commented] (OAK-386) Define equality or 'sameness' of Tree
objects
Posted by "Michael Dürig (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Comment Edited] (OAK-386) Define equality or 'sameness' of
Tree objects
Posted by "Michael Dürig (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OAK-386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479891#comment-13479891 ]
Michael Dürig edited comment on OAK-386 at 10/19/12 9:04 AM:
-------------------------------------------------------------
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.
was (Author: mduerig):
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
[jira] [Updated] (OAK-386) Define equality or 'sameness' of Tree
objects
Posted by "angela (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OAK-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
angela updated OAK-386:
-----------------------
Component/s: core
> 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