You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Marshall Schor (JIRA)" <de...@uima.apache.org> on 2016/10/20 13:37:58 UTC
[jira] [Updated] (UIMA-5148) External Resources not given creating
ResourceManager
[ https://issues.apache.org/jira/browse/UIMA-5148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor updated UIMA-5148:
---------------------------------
Summary: External Resources not given creating ResourceManager (was: External Resources not given creating Resource)
> External Resources not given creating ResourceManager
> -----------------------------------------------------
>
> Key: UIMA-5148
> URL: https://issues.apache.org/jira/browse/UIMA-5148
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Priority: Minor
> Fix For: 3.0.0SDKexp, 2.9\
>
>
> UIMA-2903 mentioned that External Resources, created by a Resource Manager, get instantiated with a different, unconnected, unique Resource Manager instance (returned by that Resource's getResourceManager() API), and suggests that it would be a better design to have the External Resource's getResourceManager() API return the ResourceManager that created it, instead.
> This seems very reasonable to me. This Jira will change the implementation to do this.
> It's possible that this may break code which was depending on having External Resource Creation being set up with an independent ResourceManager instance, but I doubt any code is depending on this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)