Angela Schreiber wrote:
> Julian Reschke wrote:
>
>> - change the return value of getChildInfos so that size information is
>> there (Iterator -> RangeIterator or Collection)
>
> didn't we have that discussion before? (JCR-1239)
We didn't come to a conclusion (it's an open issue). I'm looking for a
solution to this problem; and if we are looking at extending/changing
child entry handling, we IMHO should look at this issue as well.
> since jcr2spi will still have to process the Iterator in order
> to populate the hierarchy in order to properly respond to
> 'hasNode' or 'hasNodes' or 'getNodes', i don't see the
> benefit of the Iterator over Array.
It has the benefit that it can be lazily built.
> And Collection is wrong from my point of view.
Don't see why exactly, but RangeIterator would work as well. Collection
has the (somewhat future) benefit to be Iterable.
> ..
>> or by just allowing both types in the Iterator).
>
> oh no! i would oppose to that.
Agreed, I would also prefer inheritance here.
BR, Julian
|