[
https://issues.apache.org/jira/browse/UIMA-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eddie Epstein closed UIMA-911.
------------------------------
Resolution: Fixed
Fix Version/s: 2.2.2S
This fix complies with our existing documentation describing how the framework
calls user's CAS multiplier code: first hasNext then next. This allow us to
avoid complicating our documentation (for those novice Java users not intimate
with Java iterator design) with warnings about how the UIMA framework may call
hasNext multiple times before calling next.
Perhaps more importantly, this assures that existing collection readers will
work as CAS multipliers, since the CPE only called hasNext once before calling
next.
> CasMultiplier's hasNext() called twice without an intervening next()
> --------------------------------------------------------------------
>
> Key: UIMA-911
> URL: https://issues.apache.org/jira/browse/UIMA-911
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
> Reporter: Burn Lewis
> Priority: Minor
> Fix For: 2.2.2S
>
> Attachments: UIMA-911-fix.patch, UIMA-911.patch
>
>
> In org.apache.uima.analysis_engine.impl.PrimitiveAnalysisEngine_impl the
> hasNext method calls the AnalysisComponent's hasNext but then its next method
> calls the AnalysisComponent's hasNext again before calling next.
> Makes it difficult to split the processing between hasNext & next.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
