[
https://issues.apache.org/jira/browse/UIMA-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482161
]
Adam Lally commented on UIMA-346:
---------------------------------
Redeclaring a resource in an aggregate is a way of overriding it (though not a
recommended way - better to declare a new resource and overriding the
resourceBinding). Users might be doing this. I don't want to break things
that currently work.
> 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.1
> Reporter: Adam Lally
> Priority: Minor
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
