[JCR-1335] bad assumptions on QueryResult.getIterator() semantics in QueryResultNodeIteratorTest.testSkip()

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.0, 1.0.1, 1.1, 1.1.1, 1.2.1, 1.2.2, 1.2.3, 1.3, 1.3.1, 1.3.3, 1.4
• Fix Version/s: 1.5
• Component/s: jackrabbit-jcr-tests
• Assignee: Julian Reschke
• Reporter: Julian Reschke
• Created: 21/Jan/08 16:01
• Updated: 08/Dec/08 11:09
• Resolved: 22/Jan/08 11:22

Description

testSkip() assumes that calling getIterator() a second time will return a new iterator of the same size. JSR-170 is silent on this. Forcing a server to implement this essantially means that the query result must be cached until there's no reference to QueryResult anymore.

As this is a test of skip(), not getIterator(), the test should really refetch a new QueryResult in order to obtain a new iterator.

(Note: The issue of the semantics of QueryResult.getIterator should be discussed by the JCR EG.)