My apologies for wasting anybody's time - this was a stupid user error on my part. I had a few calls to nodeIterator.next() hidden in my debug expressions which was causing the odd iteration. :blush: -- View this message in context: http://n4.nabble.com/Jackrabbit-2-0-JCR-SQL2-query-odd-NodeIterator-behaviour-tp1575371p1576305.html Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
- Jackrabbit 2.0 JCR SQL2 query - odd NodeIterator behaviour Gadbury
- Re: Jackrabbit 2.0 JCR SQL2 query - odd NodeIterator behaviou... Gadbury
