jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julian Reschke (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-1124) Core NodeTypeImpl requires equals() implementation
Date Thu, 13 Sep 2007 08:04:32 GMT

    [ https://issues.apache.org/jira/browse/JCR-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12527010
] 

Julian Reschke commented on JCR-1124:
-------------------------------------

I'm not sure why it would require an own equals() method, unless JSR-170 would define its
semantics.

Even if Jackrabbit implemented that, a generic JCR client couldn't take advantage of it.

So should JSR-170/JSR-283 define NodeType equality? And if yes, how? Just comparing the node
type name?


> Core NodeTypeImpl requires equals() implementation
> --------------------------------------------------
>
>                 Key: JCR-1124
>                 URL: https://issues.apache.org/jira/browse/JCR-1124
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 1.4
>            Reporter: David Rauschenbach
>            Priority: Minor
>
> The Jackrabbit core NodeTypeImpl class requires an equals method, that can successfully
test for equality against any implementation javax.jcr.nodetype.NodeType.
> The current hack is to perform string comparison on NodeType.getName().

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message