[
https://issues.apache.org/jira/browse/UIMA-3562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-3562:
---------------------------------------------
Description:
uimaFIT throws a UIMAException in several places, apparently to avoid separate
throws clauses for AnalysisEngineException, ResourceInitializationException and
the likes. This is not good, because the different kinds of problems that can
occur are somewhat hidden from a person using methods throwing UIMAException.
It would be better to declare each exception separately.
Examples:
* CpePipeline.runPipeline
* SimplePipeline.runPipeline
was:uimaFIT throws a UIMAException in several places, apparently to avoid
separate throws clauses for AnalysisEngineException,
ResourceInitializationException and the likes. This is not good, because the
different kinds of problems that can occur are somewhat hidden from a person
using methods throwing UIMAException. It would be better to declare each
exception separately.
> Avoid throwing UIMAException
> ----------------------------
>
> Key: UIMA-3562
> URL: https://issues.apache.org/jira/browse/UIMA-3562
> Project: UIMA
> Issue Type: Bug
> Components: uimaFIT
> Affects Versions: 2.0.0uimaFIT
> Reporter: Richard Eckart de Castilho
> Priority: Minor
> Fix For: 2.1.0uimaFIT
>
>
> uimaFIT throws a UIMAException in several places, apparently to avoid
> separate throws clauses for AnalysisEngineException,
> ResourceInitializationException and the likes. This is not good, because the
> different kinds of problems that can occur are somewhat hidden from a person
> using methods throwing UIMAException. It would be better to declare each
> exception separately.
> Examples:
> * CpePipeline.runPipeline
> * SimplePipeline.runPipeline
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
