[
https://issues.apache.org/jira/browse/UIMA-3097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13735968#comment-13735968
]
Richard Eckart de Castilho commented on UIMA-3097:
--------------------------------------------------
Comment by Judith:
{quote}
Alternative suggestions JCasIterable:
• -1 for IterablePipeline as to be similar to SimplePipeline
• +1 for PipelineIterable
• 0 for JCasIterable (no change)
Alternative suggestions SimplePipeline.stepPipeline(readerDesc, aeDesc...):
• -1 for .stepThroughPipeline because .stepPipeline isn't grammatically
correct
• -1 for .iteratePipeline as to be similar to .runPipeline
• +1 for .iterate
• -1 for .stepPipeline as to be similar to .runPipeline (no change)
{quote}
> 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
