Marshall Schor created UIMA-5055:
------------------------------------
Summary: JCas not always initialized
Key: UIMA-5055
URL: https://issues.apache.org/jira/browse/UIMA-5055
Project: UIMA
Issue Type: Bug
Components: Core Java Framework
Affects Versions: 2.8.1SDK
Reporter: Marshall Schor
Assignee: Marshall Schor
Fix For: 2.9.0SDK
JCas classes are loaded lazily on the first switch of the CAS to the JCas
format.
JCas support includes support for nested JCas class loading contexts, which can
be established either by setting the UIMA Extension class loader when a
pipeline is instantiated, and/or by entering a Pear (which establishes its own
classpath for use within the Pear).
If the first switch to JCas format occurs within an inner class loading
context, when the outer class loading context is in force, the switch to JCas
no longer triggers the lazy loading of the JCas classes for that class loading
context (because JCas was already loaded). This bug causes the outer class
loading context to not be initialized for JCas. See UIMA-5054 for an example
where this occurred.
Fix this to remember JCas initialization per class loader.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
