[
https://issues.apache.org/jira/browse/JCR-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602577#action_12602577
]
angela commented on JCR-1638:
-----------------------------
> Another solution might be,
right... that would after all be a much cheaper fix for the problem.
since we will have to address the childnodeentries loading sooner or later, i
wanted to state it here.
do you have a patch for the straight forward fix at hand? that would be cool :)
angela
> Redundant calls to RepositoryService.getChildInfos
> --------------------------------------------------
>
> Key: JCR-1638
> URL: https://issues.apache.org/jira/browse/JCR-1638
> Project: Jackrabbit
> Issue Type: Bug
> Components: jackrabbit-jcr2spi
> Reporter: Michael Dürig
>
> In some cases jcr2spi issues calls to RepositoryService.getChildInfos for
> items which haven been returned by the last call to
> RepositoryService.getItemInfos.
> This happens because WorkspaceItemStateFactory.createDeepPropertyState is
> asked to create the node states for all items returned by
> RepositoryService.getChildInfos in the order they are returned by the
> Iterator. When trying to create an item state for an item which is deeper
> down the hierarchy than another item which comes later in the iterator, a
> call to RepositoryService.getChildInfos is issued for the latter.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
