jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] Commented: (JCR-2688) Provide utility for handling large number of child nodes/properties
Date Wed, 28 Jul 2010 14:51:18 GMT

    [ https://issues.apache.org/jira/browse/JCR-2688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12893193#action_12893193
] 

Michael Dürig commented on JCR-2688:
------------------------------------

So I see four option for the unit tests:

1. Move above utility classes along with the unit test into their own module
2. Add the unit tests to jackrabbit-core
3. Add the unit tests to jcr-commons but run them during the core build. Needs a jcr-commons
test artifact
4. Do away with the unit tests all together

Although 1. is the cleanest way I don't like it since we have enough modules already. 
4. is bad
For 2. I think jackrabbit-core is the wrong place. Unit tests always have a documentation
aspect. People just wont look for them in core.
So I think we are left with 3. Which is not a bright solution neither.

> 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ürig
>            Assignee: Michael Dürig
>         Attachments: JCR-2688.patch
>
>
> Jackrabbit does not cope well with 'flat' hierarchies. That is with hierarchies where
a node has many child nodes and/or properties. The current recommendation for such situations
is to manually add intermediate nodes. 
> 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 
> - organize the node/properties in the underlying JCR hierarchy in a way which is both
efficient for above operations and easily understandable to users looking at the hierarchy.


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


Mime
View raw message