uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard Eckart de Castilho (JIRA)" <...@uima.apache.org>
Subject [jira] [Commented] (UIMA-346) Declaration of multiple externalResources with the same name is not reported as an error.
Date Thu, 13 Oct 2016 20:54:20 GMT

    [ https://issues.apache.org/jira/browse/UIMA-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15573150#comment-15573150
] 

Richard Eckart de Castilho commented on UIMA-346:
-------------------------------------------------

I think we could break this in a move to UIMAv3 and say that this type of overriding is no
longer supported and instead the resourceBinding should be overridden.

> Declaration of multiple externalResources with the same name is not reported as an error.
> -----------------------------------------------------------------------------------------
>
>                 Key: UIMA-346
>                 URL: https://issues.apache.org/jira/browse/UIMA-346
>             Project: UIMA
>          Issue Type: Bug
>          Components: Core Java Framework
>    Affects Versions: 2.3
>            Reporter: Adam Lally
>            Priority: Minor
>              Labels: Resources
>
> A user reports that it is difficult to debug a situation where developers have accidentally
declared two resources with the same name.  UIMA currently logs a WARNING message in this
case.
> The severity could be increased to SEVERE.  Also we could add a "strict descriptor checking"
mode (off by default) that throws an Exception in this case, and possibly other cases.  We
probably shouldn't have this on by default since it could break existing applications that
currently work.
> Also our documentation should say that qualified names should be used for resources,
e.g. org.myorg.myproj.myresource, to minimize the chance of accidental name clashes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message