[
https://issues.apache.org/jira/browse/JCR-2688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12893204#action_12893204
]
Alexander Klimetschek commented on JCR-2688:
--------------------------------------------
1. is the "right" way: if jackrabbit's JCR API implementation (core) depends on
jcr-commons functionality, jcr-commons itself can't really offer functionality
that depends on the JCR API (and on an API implementation to run/test it). But
that extends to existing utilities in jcr-commons, I guess.
> 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.
