[ https://issues.apache.org/jira/browse/UIMA-5148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor resolved UIMA-5148. ---------------------------------- Resolution: Fixed Fix Version/s: (was: 2.9\) 2.9.1SDK If no ResourceManager is set, then initializeExternalResources will use this resource manager as the one associated with the External Resources that are produced. > 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.1SDK > > > 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)