[
https://issues.apache.org/jira/browse/UIMA-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14091307#comment-14091307
]
Marshall Schor commented on UIMA-3979:
--------------------------------------
Hi, so this looks like the fix would be in the later code, which should first
check if a relative path resolver is already present, and only add one if it is
not?
> 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
> 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.2#6252)
