Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <6729738.118861280768896950.JavaMail.jira@thor>
Date: Mon, 2 Aug 2010 13:08:16 -0400 (EDT)
From: =?utf-8?Q?Michael_D=C3=BCrig_=28JIRA=29?= <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Commented: (JCR-2688) Provide utility for handling large
 number of child nodes/properties
In-Reply-To: <7794860.42441280311878109.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/JCR-2688?page=3Dcom.atlassian.j=
ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D128946=
03#action_12894603 ]=20

Michael D=C3=BCrig commented on JCR-2688:
------------------------------------

I created JCR-2692 to track the issue of splitting jcr-commons into tow sep=
arate modules.=20

> Provide utility for handling large number of child nodes/properties
> -------------------------------------------------------------------
>
>                 Key: JCR-2688
>                 URL: https://issues.apache.org/jira/browse/JCR-2688
>             Project: Jackrabbit Content Repository
>          Issue Type: New Feature
>          Components: jackrabbit-jcr-commons
>    Affects Versions: 2.2.0
>            Reporter: Michael D=C3=BCrig
>            Assignee: Michael D=C3=BCrig
>             Fix For: 2.2.0
>
>         Attachments: JCR-2688.patch
>
>
> Jackrabbit does not cope well with 'flat' hierarchies. That is with hiera=
rchies where a node has many child nodes and/or properties. The current rec=
ommendation for such situations is to manually add intermediate nodes.=20
> It would be nice to have an utility which adds/removes intermediate nodes=
 as needed and expose a 'flat' view to users. Such an utility should:
> - expose a large number of nodes/properties as sequence
> - parametrize the order of how nodes/properties appear in the sequence
> - provide methods to lookup/add/remove nodes/properties by key=20
> - organize the node/properties in the underlying JCR hierarchy in a way w=
hich is both efficient for above operations and easily understandable to us=
ers looking at the hierarchy.=20

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