[
https://issues.apache.org/jira/browse/JCR-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12527455
]
Stefan Guggisberg commented on JCR-1124:
----------------------------------------
David, what's your use case?
i intentionally didn't override Object#equals() because the semantics are
undefined.
for example, since the NodeType object is session-bound, would you consider
2 NodeTypeImpl instances representing the same type A (but associated to
different
sessions) equal or not?
i wouldn't consider comparing node type names a hack. node type names uniquely
identify registered node types in a repository.
> 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.
