jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-2005) JCR2SPI: Remove validation check for same-named Node and Property
Date Fri, 08 May 2009 08:53:46 GMT

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

angela resolved JCR-2005.

    Resolution: Fixed
      Assignee: angela

removed checks for same named property and node in ItemValidator.java and Move.java and adjusted
the tests accordingly.

NOTE: the tck misses tests for the new mandatory feature (changed from 1.0) -> see JCR-2085

> JCR2SPI: Remove validation check for same-named Node and Property
> -----------------------------------------------------------------
>                 Key: JCR-2005
>                 URL: https://issues.apache.org/jira/browse/JCR-2005
>             Project: Jackrabbit Content Repository
>          Issue Type: Sub-task
>          Components: jackrabbit-jcr2spi
>            Reporter: angela
>            Assignee: angela
>         Attachments: JCR-2005.patch
> JSR 170 disallowed a parent node to have a property and a child node with the same name.
> This limitation has been removed with JSR 283 and the RI (jackrabbit-core) already removed
the check.
> I would suggest to change Jcr2Spi accordingly and leave this validation to the underlying
SPI impl.
> If I'm not mistaken this JSR 170 requirement is asserted in a single place (ItemStateValidator).

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message