bad assumptions on QueryResult.getIterator() semantics in
QueryResultNodeIteratorTest.testSkip()
------------------------------------------------------------------------------------------------
Key: JCR-1335
URL: https://issues.apache.org/jira/browse/JCR-1335
Project: Jackrabbit
Issue Type: Bug
Components: jackrabbit-jcr-tests
Reporter: Julian Reschke
Assignee: Julian Reschke
Priority: Minor
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.)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
