[
https://issues.apache.org/jira/browse/UIMA-5603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor reopened UIMA-5603:
----------------------------------
The widespread use of the new approach to get all the FSs in a view broke a
test case that was depending on the exact order sequence for serialized FSs not
changing.
To improve backward compatibility, put back the ordering for serialization to
how it used to be (the order was, surprisingly, the indexes are ordered by
first-use.).
> uv3 add ability to do extended-for on all FSs of a type in a view
> -----------------------------------------------------------------
>
> Key: UIMA-5603
> URL: https://issues.apache.org/jira/browse/UIMA-5603
> Project: UIMA
> Issue Type: Improvement
> Components: Core Java Framework
> Affects Versions: 3.0.0SDK-alpha02
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Priority: Trivial
> Fix For: 3.0.0SDK-beta
>
>
> Forms like cas.getIndexRepository().getAllIndexedFSs(...) return an iterator.
> It would be nice to be able to use the returned result in an extended for :
> for (TOP x : cas.getInd... etc).
> Add a new set of methods, getIndexedFSs( Type or JCas.class or nothing) to
> CAS/JCas and FSIndexRepository interfaces, that return Collections, without
> copying the index arrays, but just using them. Make these copy-on-write
> style, so subsequent updates to the UIMA indexes won't affect the collection.
> These can then be used in extended-for loops.
> Update internal uses of getAllIndexedFS (which does copy the indexes) to use
> the new style.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)