jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Nebolsin (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-1740) Make ObjectIterator implement RangeIterator interface
Date Fri, 19 Sep 2008 15:40:44 GMT

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

Sergey Nebolsin updated JCR-1740:

    Attachment: JCR-1740-solution1.patch

I attached proposed patch for solution 1 with a modified testcase, which covers RangeInterator
behavior. The solution is tested to work fine as part of Grails JCR plugin, but the plugin
currently use only basic OCM features and doesn't have complex testcases.

> Make ObjectIterator implement RangeIterator interface
> -----------------------------------------------------
>                 Key: JCR-1740
>                 URL: https://issues.apache.org/jira/browse/JCR-1740
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: jackrabbit-ocm
>    Affects Versions: 1.4
>         Environment: All environments
>            Reporter: Sergey Nebolsin
>            Priority: Minor
>             Fix For: 1.5
>         Attachments: JCR-1740-solution1.patch, JCR-1740.patch
> Currently, it's not possible to skip a part of results returned in the form of ObjectIterator
(for example, to implement db-like pagination feature with offset/max parameters).
> It would be great if ObjectIterator implement RangeIterator interface, and it's trivial
enough since underlying NodeIterator implements this interface.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message