jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-647) NodeType.canRemoveItem does not consider residual definitions (JCR2SPI)
Date Tue, 28 Nov 2006 16:54:23 GMT
    [ http://issues.apache.org/jira/browse/JCR-647?page=comments#action_12454017 ] 
angela commented on JCR-647:

the patch looks good to me.

however: the code originates from jackrabbit.core.nodetype.EffectiveNodeType.java and probably
stefan knows more details about the reasons for not respecting unnamed definitions in the
mentioned check

if  it the SPI code gets modified, i would suggest to also apply the same change to the mentioned
class in jackrabbit.core.


> 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

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


View raw message