You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2007/07/02 11:06:04 UTC

[jira] Closed: (JCR-647) NodeType.canRemoveItem does not consider residual definitions (JCR2SPI)

     [ https://issues.apache.org/jira/browse/JCR-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Reschke closed JCR-647.
------------------------------

    Resolution: Won't Fix

canRemoveItem with residual properties is not meaningful; make sure JCR 2.0 says that the method should return true.


> NodeType.canRemoveItem does not consider residual definitions (JCR2SPI)
> -----------------------------------------------------------------------
>
>                 Key: JCR-647
>                 URL: https://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.
-
You can reply to this email to add a comment to the issue online.