[
https://issues.apache.org/jira/browse/UIMA-5711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16342732#comment-16342732
]
Richard Eckart de Castilho commented on UIMA-5711:
--------------------------------------------------
Any idea why the Component Description Editor loads JCas classes at all... and
even then from the workspace and not from the OSGi bundle itself? It seems this
would be one of these cases where one would want to disable JCas loading
entirely - if creating a JCas is necessary at all.
> uv3 handle migration from alpha levels of JCas classes more gracefully
> ----------------------------------------------------------------------
>
> Key: UIMA-5711
> URL: https://issues.apache.org/jira/browse/UIMA-5711
> Project: UIMA
> Issue Type: Improvement
> Components: Core Java Framework
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Priority: Major
> Fix For: 3.0.0SDK
>
>
> Alpha levels of JCas classes call
> TypeSystemImpl.getAdjustedFeatureOffset(...) as part of the initialization
> for features. This approach was changed for beta and later levels, and this
> API if used throws an exception (saying it's an old alpha level construct).
> Change this to a) not throw an exception, but just issue a warning, and b)
> return -1, which, if it really is an old jcas class, at run time, if this
> feature is referenced, it will cause an exception.
> This will let people successfully migrate from v3 alpha levels by running for
> example JCasGen from the Component Description Editor.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
