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/04/10 19:08:01 UTC

[jira] [Updated] (UIMA-4571) ConfigurationParameterFactory.setParameter() should attempt type coercion

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

Richard Eckart de Castilho updated UIMA-4571:
---------------------------------------------
    Fix Version/s: 3.2.0uimaFIT

> ConfigurationParameterFactory.setParameter() should attempt type coercion
> -------------------------------------------------------------------------
>
>                 Key: UIMA-4571
>                 URL: https://issues.apache.org/jira/browse/UIMA-4571
>             Project: UIMA
>          Issue Type: Bug
>          Components: uimaFIT
>            Reporter: Richard Eckart de Castilho
>            Priority: Major
>             Fix For: 3.2.0uimaFIT
>
>
> ConfigurationParameterFactory.createConfigurationData() does try all kinds of type conversions to coerce values that UIMA doesn't know into parameters. However, ConfigurationParameterFactory.setParameter() doesn't try any of this yet. At least for those cases where the resource specifiers accept ConfigurationParameter-type parameters, this can be easily implemented. 



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