[
https://issues.apache.org/jira/browse/UIMA-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753633#comment-13753633
]
Artem commented on UIMA-3234:
-----------------------------
Yes, two different exceptions are also ok, but it might cause some backward
compatibility issues if the changes are applied to the existing method?
> Differentiate no Annotation and multiple Annotation case in
> CasUtil.selectSingle(CAS cas, Type type)
> ----------------------------------------------------------------------------------------------------
>
> Key: UIMA-3234
> URL: https://issues.apache.org/jira/browse/UIMA-3234
> Project: UIMA
> Issue Type: Wish
> Components: uimaFIT
> Affects Versions: 2.0.0uimaFIT
> Reporter: Artem
> Priority: Trivial
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Currently there is one exception type in CasUtil.selectSingle(CAS cas, Type
> type) method for the case if CAS does not contain an Annotation or CAS
> contains more than one Annotation. However, I sometimes need to differentiate
> between these two cases in exception handling. A new method like,
> selectSingleOrNull(...) could solve this problem: return null if no
> Annotation, RuntimeException if multiple Annotations.
> Currently to handle this problem I just use CasUtil.select(...) and check for
> the size of the returned collection.
--
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
