You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "chris meadows (JIRA)" <ji...@apache.org> on 2007/04/19 14:51:15 UTC

[jira] Closed: (JCR-854) allowSameNameSiblings not honoured for nt:file Node Type

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

chris meadows closed JCR-854.
-----------------------------

    Resolution: Invalid

My mistake. 
Spec isn't clear IMHO.
allowSameNameSiblings refers to a property of the _parent_, so calling folder.getDefinition().allowsSameNameSiblings()) is dependent on what the parent node is. If the parent is root, this will return true. If it is another folder node, it will return false.



> allowSameNameSiblings not honoured for nt:file Node Type
> --------------------------------------------------------
>
>                 Key: JCR-854
>                 URL: https://issues.apache.org/jira/browse/JCR-854
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.2.3
>            Reporter: chris meadows
>         Assigned To: Stefan Guggisberg
>            Priority: Critical
>         Attachments: FirstHop.java
>
>
> It is possible to create mutiple nt:file sibling Node Types at the root of a repository. 
> This should not be possible according the jcr spec section 6.7.22.8 (SameNameSiblings false)
> See attached snippet

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