[ http://issues.apache.org/jira/browse/JCR-647?page=comments#action_12454370 ] angela commented on JCR-647: ----------------------------
i had a closer look at the reference implementation (core) and found, that child item definitions combining residual and mandatory are not only ignored with the mentioned NodeType.canRemoveItem method but also during consistency checks upon Item.save(). regarding the patch: if multiple residual definitions exist, canRemoveItem may still (having the patch applied) return a wrong result, since from the itemName we cannot determine, which definition belongs to the item of the given name... i'd say, this is a problem of the specification. => i added new issues to JSR283 asking for clarification. > NodeType.canRemoveItem does not consider residual definitions (JCR2SPI) > ----------------------------------------------------------------------- > > Key: JCR-647 > URL: http://issues.apache.org/jira/browse/JCR-647 > Project: Jackrabbit > Issue Type: Bug > Components: SPI > Reporter: Julian Reschke > Priority: Minor > Attachments: JCR-647.diff.txt > > > JCR2SPI's NodeType.canRemoveItem() doesn't seem to work with residual > definitions. This seems to be caused by > EffectiveNodeTyoeImpl.checkRemoveItemConstraints not checking the unnamed > definitions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
