Mailing-List: contact oak-dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: oak-dev@jackrabbit.apache.org
Date: Fri, 6 Jul 2012 11:29:33 +0000 (UTC)
From: "Michael Marth (JIRA)" <jira@apache.org>
To: oak-dev@jackrabbit.apache.org
Message-ID: <561247804.13618.1341574174426.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <542454076.9151.1341501994625.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (OAK-169) Support orderable nodes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/OAK-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13407900#comment-13407900 ] 

Michael Marth commented on OAK-169:
-----------------------------------

Would we need to support multi-valued properties with many entries for such an implementation? I wonder about the 10M-child node[1] case when ordering is added.

[1] http://wiki.apache.org/jackrabbit/Goals%20and%20non%20goals%20for%20Jackrabbit%203
                
> Support orderable nodes
> -----------------------
>
>                 Key: OAK-169
>                 URL: https://issues.apache.org/jira/browse/OAK-169
>             Project: Jackrabbit Oak
>          Issue Type: New Feature
>          Components: jcr
>            Reporter: Jukka Zitting
>
> There are JCR clients that depend on the ability to explicitly specify the order of child nodes. That functionality is not included in the MicroKernel tree model, so we need to implement it either in oak-core or oak-jcr using something like an extra (hidden) {{oak:childOrder}} property that records the specified ordering of child nodes. A multi-valued string property is probably good enough for this.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira