[
https://issues.apache.org/jira/browse/UIMA-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor closed UIMA-554.
-------------------------------
Resolution: Fixed
Fix Version/s: 2.3
We expect this fix to be backwards compatible. Adding metadata twice does no
harm, as all the metadata is merged at some point anyways.
> Have produceResource for CollectionReaders operate like other Analysis
> Engines with respect to setup of type system
> -------------------------------------------------------------------------------------------------------------------
>
> Key: UIMA-554
> URL: https://issues.apache.org/jira/browse/UIMA-554
> Project: UIMA
> Issue Type: Improvement
> Components: Core Java Framework
> Affects Versions: 2.1, 2.2
> Reporter: Marshall Schor
> Priority: Trivial
> Fix For: 2.3
>
>
> This code fails but works if you uncomment out line 3:
> CollectionReader cr = UIMAFramework.produceCollectionReader(aSpecifier);
> CasManager casManager = cr.getCasManager();
> // casManager.addMetaData((ProcessingResourceMetaData)cr.getMetaData());
> casManager.defineCasPool("pool", 2, null);
> Other "produce" methods (i.e. for analysis engines) add their metadata to
> their cas managers. Consider doing this for Collection Readers too (this is
> now done during CPE initialization).
> Use case: User found this while trying to test collection reader by itself.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
