[
https://issues.apache.org/jira/browse/UIMA-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15602320#comment-15602320
]
Richard Eckart de Castilho commented on UIMA-5156:
--------------------------------------------------
An option could be to introduce auto-destroy only with v3.
For uimaFIT, I think I could handle it internally within e.g. SimplePipeline
for the time being.
> ResourceManager automatic destory
> ---------------------------------
>
> Key: UIMA-5156
> URL: https://issues.apache.org/jira/browse/UIMA-5156
> Project: UIMA
> Issue Type: Improvement
> Reporter: Marshall Schor
> Priority: Minor
>
> UIMA-2977 adds a destory() method to the ResourceManager (RM), that forwards
> this call to external resources managed by that RM.
> The destroy() method was not called by the framework, because in general the
> RM may be shared by the user (or framework) among multiple pipelines.
> This Jira is to enable RMs created by the framework to call destroy()
> internally at the appropriate time.
> This assumes that the right time can be figured out for the various cases.
> These include: MultiprocessingAnalysisEngine_impl, and fixing other
> associated frameworks which may use a pattern where they
> * let the framework create a RM, but then
> * use that in other contexts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
