[
https://issues.apache.org/jira/browse/UIMA-2977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13708148#comment-13708148
]
Marshall Schor commented on UIMA-2977:
--------------------------------------
I like your suggestions. I think that some additional investigation into
Resource Managers might be needed, to see if additional "delegating" is needed
or other approaches. For instance, IIRC, a Pear Wrapper creates a (sub)
resource manager in order to set up an isolated class loader for the Pear it is
wrapping. There was some tweaking done in that (I don't recall the details) to
allow some degree of sharing - this may have included external resources.
> destroy method of shared resources never called
> -----------------------------------------------
>
> Key: UIMA-2977
> URL: https://issues.apache.org/jira/browse/UIMA-2977
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
> Reporter: Richard Eckart de Castilho
>
> Apparently the ResourceManager and the resources created by the manager do
> not participate in the usual component life cycle. On other components, such
> as analysis engines or readers, the destroy() method is called when the
> component is disposed of. External resources never get notified when they are
> no longer needed. At least any resources derived from Resource (e.g.
> DataResource and ParametrizedDataResource) should be notified. The
> SharedResourceObject interface does not define any such life cycle callback.
> As a side-note: An alternative to the rather heavy-weight Resource interface
> of UIMA maybe be small life cycle interfaces such as the Spring
> InitializingBean and DisposableBean interfaces, or Java annotations marking
> initialization and destruction methods (e.g. @PostConstruct and @PreDestroy).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
