[
https://issues.apache.org/jira/browse/UIMA-6468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6468:
---------------------------------------------
Fix Version/s: 3.4.1SDK
(was: 3.4.0SDK)
> Problem with JCas classes with re-used across different type systems
> --------------------------------------------------------------------
>
> Key: UIMA-6468
> URL: https://issues.apache.org/jira/browse/UIMA-6468
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
> Reporter: Richard Eckart de Castilho
> Assignee: Richard Eckart de Castilho
> Priority: Major
> Fix For: 3.4.1SDK
>
>
> When a JCas wrapper class is loaded, its features are bound to "index"
> positions in the type system available at the time that they are loaded.
> Normally this works great, even if different type systems are used because
> the features defined by the JCas classes have priority and thereby receive
> stable index positions.
> However, there can be problems in situations where multiple classloaders are
> involved such that a JCas class that has been bound to one indexes in type
> system would later be bound to other indexes in slightly different type
> system, e.g. because the available features change (in a reasonably
> "compatible" way).
> It would be nice if UIMA had a solution for this type of problem.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
