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

["Richard Eckart de Castilho (JIRA)" <de...@uima.apache.org>]

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

Richard Eckart de Castilho reopened UIMA-3097:
----------------------------------------------


Due to the current release candidate having been canceled, there is still some room to discuss method names (possibly class names).

Current situation:

* {{JCasIterable}}
* {{SimplePipeline.stepPipeline(readerDesc, aeDesc...)}}

Alternative suggestions {{JCasIterable}}:

* {{IterablePipeline}} as to be similar to {{SimplePipeline}}
* {{PipelineIterable}}
* {{JCasIterable}} (no change)

Alternative suggestions {{SimplePipeline.stepPipeline(readerDesc, aeDesc...)}}:

* {{.stepThroughPipeline}} because {{.stepPipeline}} isn't grammatically correct
* {{.iteratePipeline}} as to be similar to {{.runPipeline}}
* {{.iterate}} 
* {{.stepPipeline}} as to be similar to {{.runPipeline}} (no change)

                
> 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