[
https://issues.apache.org/jira/browse/JCR-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672251#action_12672251
]
Stefan Guggisberg commented on JCR-1967:
----------------------------------------
> both in core and in jcr2spi EffectiveNodeType#includesNodeType() just does a
> lookup in a set. i don't see any object creation there.
you're right. so the optimization is obsolete anyway.
i believe it used to check EffectiveNodeTypeCache at some point, creating
WeightedKey objects.
> Impossible comparison in NodeTypeImpl
> -------------------------------------
>
> Key: JCR-1967
> URL: https://issues.apache.org/jira/browse/JCR-1967
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-jcr2spi
> Affects Versions: 1.6.0
> Reporter: Dave Brosius
> Assignee: angela
> Priority: Trivial
> Fix For: 1.6.0
>
>
> org.apache.jackrabbit.jcr2spi.nodetype.NodeTypeImpl does
> public boolean isNodeType(Name nodeTypeName) {
> return getName().equals(nodeTypeName) ||
> ent.includesNodeType(nodeTypeName);
> }
> as getName() is a string and nodeTypeName is a Name this will always be
> false. Perhaps you meant
> public boolean isNodeType(Name nodeTypeName) {
> return getName().equals(nodeTypeName.getLocalName()) ||
> ent.includesNodeType(nodeTypeName);
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
