jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julian Reschke (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-647) NodeType.canRemoveItem does not consider residual definitions (JCR2SPI)
Date Wed, 29 Nov 2006 12:21:22 GMT
    [ http://issues.apache.org/jira/browse/JCR-647?page=comments#action_12454293 ] 
Julian Reschke commented on JCR-647:

Good point.

One of my test cases looks at all registered node types, and then checks canRemoveItem() (and
friends), As a matter of fact, more of these tests are failing under JCR2SPI, but I thought
I start with the first and simple example for which I actually have a fix.

With respect to Jackrabbit core: maybe this isn't covered by any test case?

> 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