You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Stefan Guggisberg (JIRA)" <ji...@apache.org> on 2007/04/19 15:20:15 UTC
[jira] Commented: (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:comment-tabpanel#action_12490046 ]
Stefan Guggisberg commented on JCR-854:
---------------------------------------
according to 6.7.22.8 *child* nodes of a node of type nt:folder cannot have same name siblings (sameNameSiblings=false).
the 'allowSameNameSibling' attribute applies to the child node definition of nt:folder.
while i think that the spec is clear in that respect (see 6.7.14 NodeDefition, allowsSameNameSiblings()) i agree that it's
relatively easy to misinterpret the semantics of the allowSameNameSibling attribute at first.
> 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.