[ https://issues.apache.org/jira/browse/JCR-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595201#action_12595201 ]
Julian Reschke commented on JCR-1405: ------------------------------------- If we have evidence that it actually helps in some cases, +.5. That being said, I think it would be great if we would base these things on reliable test data; that's why I started the jcr-benchmark project after all. > SPI: Introduce NodeInfo.getChildInfos() > --------------------------------------- > > Key: JCR-1405 > URL: https://issues.apache.org/jira/browse/JCR-1405 > Project: Jackrabbit > Issue Type: New Feature > Components: jackrabbit-spi > Reporter: angela > Attachments: JCR-1405.patch, JCR-1405b.patch > > > Improvement suggested by Marcel: > ChildInfo is basically a stripped down NodeInfo. With little effort it would > even be possible to have NodeInfo extends ChildInfo. Not sure how useful that > is, but since we don't have that inheritance in code and at the same time > nearly a 100% overlap it makes me suspicious. > Here's another idea: > introduce a method ChildInfo[] NodeInfo.getChildInfos(). The method either > returns: > - all child infos, which also gives the correct number of child nodes. this > may also mean that an empty array is returned to indicate there are no child > nodes. > - null, to indicate that there are *lots* of child nodes and the method > RepositoryService.getChildInfos() with the iterator should be used. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.