You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@uima.apache.org by "Richard Eckart de Castilho (JIRA)" <de...@uima.apache.org> on 2013/07/23 15:04:48 UTC

[jira] [Commented] (UIMA-3097) Split JCasIterable into iterable and iterator parts

    [ https://issues.apache.org/jira/browse/UIMA-3097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13716370#comment-13716370 ] 

Richard Eckart de Castilho commented on UIMA-3097:
--------------------------------------------------

Consider calling the JCasIterable a IterablePipeline.

Consider keeping old JCasIterable around as @Deprecated.
                
> Split JCasIterable into iterable and iterator parts
> ---------------------------------------------------
>
>                 Key: UIMA-3097
>                 URL: https://issues.apache.org/jira/browse/UIMA-3097
>             Project: UIMA
>          Issue Type: Improvement
>          Components: uimaFIT
>            Reporter: Richard Eckart de Castilho
>            Assignee: Richard Eckart de Castilho
>             Fix For: 2.0.0uimaFIT
>
>
> The JCasIterable is an Iterable and an Iterator at the same time. The iterator() method returns just "this". This goes against the expectation that an Iterable should return a fresh iterator when iterator() is called.
> JCasIterable should therefore be split. The JCasIterable should only be creatable with descriptions.
> Calling iterator should create a new JCasIterator which then is based on concrete reader and AE instances.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira