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 2016/09/02 20:43:20 UTC
[jira] [Resolved] (UIMA-3979) Unable to set custom
RelativePathResolver in aAdditionalParams when produceAnalysisEngine
[ https://issues.apache.org/jira/browse/UIMA-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard Eckart de Castilho resolved UIMA-3979.
----------------------------------------------
Resolution: Unresolved
Closing as reported has not provided further feedback on the issue.
> Unable to set custom RelativePathResolver in aAdditionalParams when produceAnalysisEngine
> -----------------------------------------------------------------------------------------
>
> Key: UIMA-3979
> URL: https://issues.apache.org/jira/browse/UIMA-3979
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
> Affects Versions: 2.6.0SDK
> Reporter: Aleksandar Beserminji
> Priority: Minor
> Original Estimate: 10m
> Remaining Estimate: 10m
>
> When calling function produceAnalysisEngine,
> as additional parameter HashMap is set
> where custom RelativePathResolver is inside that HashMap identified by key DataResource.PARAM_RELATIVE_PATH_RESOLVER
> That custom RelativePathResolver is never used after that, as in ResourceManager_impl class, on registerResource function, this parameter is discarded here:
> Map<String, Object> initParams = (aResourceInitParams == null) ? new HashMap<String, Object>() : new HashMap<String, Object>(aResourceInitParams);
> initParams.put(DataResource.PARAM_RELATIVE_PATH_RESOLVER, getRelativePathResolver());
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)