Thanks for the answer,
I'm not sure to understand what you mean.
Do you suggest that I load all childs when the getItemInfos() is made ?
I've made a quick test, I see that he iterate on all items given by the
getItemInfos() before iterating
over the childs iterator.
this is not a solution since It might contain an undefined number of sub
nodes.
I believe there is a kind of cache in the "hierarchy", I my case (and I
believe in many cases)
the cache won't be able to hold all nodes, this will only result in some
useless loading.
johann
Michael Dürig a écrit :
An instanceof test on the childInfo object to see if it's already a
nodeInfo could
avoid the call to getNodeInfo (and all name resolver operations, path
parsing and so on).
Johann,
While this approach might work, the preferred way to achieve this kind
of batch reading is to implement RepositoryService.getItemInfos().
Here you can return arbitrary ItemInfos in a single batch. The jcr2spi
module will then put these into the hirarchy without additional calls
to the spi layer. See also https://issues.apache.org/jira/browse/JCR-1797
Michael
