jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-1335) bad assumptions on QueryResult.getIterator() semantics in QueryResultNodeIteratorTest.testSkip()
Date Tue, 05 Feb 2008 10:34:08 GMT

     [ https://issues.apache.org/jira/browse/JCR-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jukka Zitting updated JCR-1335:
-------------------------------

    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.4.1

Merged to the 1.4 branch in revision 618603.

> 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
>    Affects Versions: 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
>            Reporter: Julian Reschke
>            Assignee: Julian Reschke
>            Priority: Minor
>             Fix For: 1.4.1
>
>         Attachments: JCR-1335.patch.txt
>
>
> 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.


Mime
View raw message