You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Peter Klügl (Jira)" <de...@uima.apache.org> on 2019/11/06 10:10:00 UTC

[jira] [Assigned] (UIMA-6131) UIMA Ruta SeedLexer throws Error instead of exception

     [ https://issues.apache.org/jira/browse/UIMA-6131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Klügl reassigned UIMA-6131:
---------------------------------

    Assignee: Peter Klügl

> UIMA Ruta SeedLexer throws Error instead of exception
> -----------------------------------------------------
>
>                 Key: UIMA-6131
>                 URL: https://issues.apache.org/jira/browse/UIMA-6131
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Ruta
>            Reporter: Mario Juric
>            Assignee: Peter Klügl
>            Priority: Major
>             Fix For: 3.0.0ruta, 2.8.0ruta
>
>
> The SeedLexer and possibly other related classes used by Ruta throw java.lang.Error instead of java.lang.Exception. This is usually only thrown by the JVM when it’s really impossible to continue the process, e.g. out of memory, linkage errors or fatal VM failures, and it therefore not meant to be caught under normal circumstances, so most runtime environment don't capture these. This can therefore cause the whole process to fail instead of just the document being processed.
> It would therefore be preferable if these components throw a type of java.lang.Exception instead, so that the process can proceed with the next document without the need to hook into the runtime core and catch java.lang.Error. The errors are also not subclassed, so it's awkward to distinguish them by checking for the message string itself.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)