You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Hugo Mougard (JIRA)" <de...@uima.apache.org> on 2014/06/26 07:38:24 UTC
[jira] [Updated] (UIMA-3913) JCasUtil methods could be more generic
[ https://issues.apache.org/jira/browse/UIMA-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hugo Mougard updated UIMA-3913:
-------------------------------
Summary: JCasUtil methods could be more generic (was: (J)CasUtil methods could be more generic)
> JCasUtil methods could be more generic
> --------------------------------------
>
> Key: UIMA-3913
> URL: https://issues.apache.org/jira/browse/UIMA-3913
> Project: UIMA
> Issue Type: Improvement
> Components: uimaFIT
> Reporter: Hugo Mougard
> Priority: Minor
> Fix For: 2.2.0uimaFIT
>
>
> As an example, the method {{indexCovering}} of {{JCasUtil}} has signature:
> {code}
> public static <T extends Annotation,S extends Annotation> Map<T, Collection<S>> indexCovering(
> JCas jCas,
> Class<T> type,
> Class<S> coveringType)
> {code}
> With this signature, the following code is invalid ({{RevisedSentence}} is a subclass of {{Sentence}}):
> {code}
> Map<RevisedWords, Collection<Sentence>> indexRevised
> = JCasUtil.indexCovering(
> revised,
> RevisedWords.class,
> RevisedSentence.class);
> {code}
> This somewhat prevents users of {{JCasUtil}} from benefiting of all the OOP pluses of the UIMA TS.
> Here would be a signature that would maybe better fit the problem:
> {code}
> public static <T extends Annotation, S extends Annotation> Map<T, Collection<S>> indexCovering(
> JCas jCas,
> Class<? extends T> type,
> Class<? extends S> coveringType)
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)