You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Richard Eckart de Castilho (Jira)" <de...@uima.apache.org> on 2020/02/10 17:33:00 UTC
[jira] [Updated] (UIMA-6188) uimaFIT initializes resources with
parameter values originating from component
[ https://issues.apache.org/jira/browse/UIMA-6188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard Eckart de Castilho updated UIMA-6188:
---------------------------------------------
Fix Version/s: 2.5.0uimaFIT
> uimaFIT initializes resources with parameter values originating from component
> ------------------------------------------------------------------------------
>
> Key: UIMA-6188
> URL: https://issues.apache.org/jira/browse/UIMA-6188
> Project: UIMA
> Issue Type: Bug
> Components: uimaFIT
> Affects Versions: 3.0.0uimaFIT
> Reporter: Richard Eckart de Castilho
> Assignee: Richard Eckart de Castilho
> Priority: Major
> Fix For: 2.5.0uimaFIT, 3.1.0uimaFIT
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> uimaFIT overshoots the goal of passing an already existing resources manager into an external resource quite a bit by not only passing on the RM but the entire UIMAContext which also includes the parameter settings of the "host" component which triggers initialization.
> That means, a resource may accidentally access parameter values from a component - in particular if resource and component both define a parameter with the same name.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)