On 8.5.12 15:15, David Hausladen wrote:
I've attached the class as it stands (currently untested). The main struggle
is how to handle the NodeIterator's getPosition method (I'm taking the easy way
out throwing an exception). Also worth mentioning: I'm on 2.2.5.
This looks pretty good to me. Wrt. getPosition method, why don't you
just count the number of calls to next() in AdaptingNodeIterator?
It would be great if you could attach this code as a patch to a JIRA
issue for jcr-commons. I'll could then try to incorporate it into trunk.
Michael
----- Original Message -----
From: Jukka Zitting<[email protected]>
To: [email protected]; David Hausladen<[email protected]>
Cc:
Sent: Tuesday, May 8, 2012 3:48 AM
Subject: Re: BTreeManager - opt in or automatic?
Hi,
On Tue, May 8, 2012 at 3:51 AM, David Hausladen
<[email protected]> wrote:
Under the assumption that it's opt in, I started an implementation of the Node
interface that
adapts to the ItemSequence's NodeSequence (to minimize visibility of the
org.apache.jackrabbit.commons.flat classes).
If you like, I'd love to incorporate something like that in
jackrabbit-jcr-commons.
The fact that NodeSequence returns Iterator<javax.jcr.Node> instead of
javax.jcr.NodeIterator makes it impossible.
Use the Adapter pattern.
BR,
Jukka Zitting
