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

Felix Meschberger commented on JCR-2688:
----------------------------------------

(6) would probably be best and also solve the mistakes others have done by 
going (3), (1) the second best and everything else is just not a good idea ;-)

BTW IMHO the "excuse" 'I don't like it since we have enough modules already' is 
just FUD. The problem is not the number of modules. The problem really is the 
unclear separation between modules. What you do with (2) or (3) is add to this 
incertainty.

So please, don't go the (2) or (3) route (what others have done already IMHO is 
equally wrong and should probably be fixed).

> 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.

Reply via email to