[
https://issues.apache.org/jira/browse/UIMA-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-340:
--------------------------------------------
Labels: Stale (was: )
This issue is marked as "stale" due to inactivity for 5 years or longer. If no
further activity is detected on this issue, it is scheduled be closed as
'unresolved' in 3 months time from now (Dec 2016).
> Provide a standard way to distinguish "Document Error" from "Engine Error"
> --------------------------------------------------------------------------
>
> Key: UIMA-340
> URL: https://issues.apache.org/jira/browse/UIMA-340
> Project: UIMA
> Issue Type: Wish
> Components: Core Java Framework
> Reporter: Adam Lally
> Priority: Minor
> Labels: Stale
>
> A user requests that UIMA allows an analysis component to specify, when it
> throws an exception, whether the exception is a "Document Error" (the
> analysis component can't process this particular document but is otherwise
> OK) vs. an "Engine Error" (the analysis component is in a bad state and will
> likely have problems processing subsequent documents too).
> Not all annotators will have such self-awareness, but for those that do it
> would be nice to provide a standard way to indicate the kind of failure.
> This would especially help if there is custom error handling logic, for
> example in the CPE StatusCallbackListener, that may want to take different
> actions in these two cases.
> There are a couple of possible approaches for doing this -
> (a) add an optional property to AnalysisEngineProcessException (maybe other
> exception types too), which the analysis component can set
> (b) create subclasses of AnalysisEngineProcessException (maybe other
> exception types too). The analysis component can throw a specialized
> subclass if it is knows enough to do so.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
