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 2015/07/28 15:06:05 UTC
[jira] [Updated] (UIMA-4499) Pears and local External Resources
[ https://issues.apache.org/jira/browse/UIMA-4499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor updated UIMA-4499:
---------------------------------
Description:
Currently, the design for External Resources presumes they can be used by any annotator, including those with a PEAR. This is supported by having UIMA load resources associated with External Resources using the main UIMA class loader, and in particular, not using the PEAR's special isolating class loader.
This causes an issue if part of the PEAR code references the same classes as the external resource, and these are found in the PEAR class path. You end up with two different versions of the class, loaded under different class loaders (one the main UIMA class loader, the other, the special class loader for the PEAR), and things break.
A possible fix is to treat external resource definitions that occur with a PEAR as only visible to that PEAR, and load them under the PEAR's class loader.
was:
Currently, the design for External Resources presumes they can be used by any annotator, including those with a PEAR. This is supported by having UIMA load resources associated with External Resources using the main UIMA class loader, and in particular, not using the PEAR's special isolating class loader.
This causes an issue if part of the PEAR code references the same classes as the external resource, and these are found in the PEAR class path. You end up with two different versions of the class, loaded under the same class loader, and things break.
A possible fix is to treat external resource definitions that occur with a PEAR as only visible to that PEAR, and load them under the PEAR's class loader.
> Pears and local External Resources
> ----------------------------------
>
> Key: UIMA-4499
> URL: https://issues.apache.org/jira/browse/UIMA-4499
> Project: UIMA
> Issue Type: Improvement
> Components: Core Java Framework
> Reporter: Marshall Schor
> Priority: Minor
>
> Currently, the design for External Resources presumes they can be used by any annotator, including those with a PEAR. This is supported by having UIMA load resources associated with External Resources using the main UIMA class loader, and in particular, not using the PEAR's special isolating class loader.
> This causes an issue if part of the PEAR code references the same classes as the external resource, and these are found in the PEAR class path. You end up with two different versions of the class, loaded under different class loaders (one the main UIMA class loader, the other, the special class loader for the PEAR), and things break.
> A possible fix is to treat external resource definitions that occur with a PEAR as only visible to that PEAR, and load them under the PEAR's class loader.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)