[
https://issues.apache.org/jira/browse/JCR-1239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12547150
]
Marcel Reutegger commented on JCR-1239:
---------------------------------------
SPI2JCR is a nice example. Just looking at the JCR API it appears that the size
information is available on the child node iterator, but looking at the
Jackrabbit internals the size is actually on the parent node, which includes
the list of child node entries. So, in the end you don't have to avoid the
call, because it is inexpensive.
> SPI: Provide possibility to retrieve the number of child-nodes without
> retrieving them.
> ---------------------------------------------------------------------------------------
>
> Key: JCR-1239
> URL: https://issues.apache.org/jira/browse/JCR-1239
> Project: Jackrabbit
> Issue Type: Improvement
> Components: jackrabbit-spi
> Reporter: angela
> Fix For: 1.4
>
>
> separate issue started by julian within issue #1166:
> RepositoryService.getChildInfos is defined to return an Iterator.
> this forces the caller to loop over all entries in order to detect the number
> of child-nodes.
> currently the hierarchy is populated any way, but that could be a source for
> future optimization.
> possible solutions:
> - change return value to RangeIterator
> - change return value to Collection (or Set).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
