[
https://issues.apache.org/jira/browse/CTAKES-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13685561#comment-13685561
]
Pei Chen edited comment on CTAKES-48 at 6/17/13 2:29 PM:
---------------------------------------------------------
Douglas,
Could you clarify which xml descriptor were using that caused this error?
The temp work around is to add in your xml: Similar to what was done in in
(https://issues.apache.org/jira/browse/CTAKES-208)
<typeSystemDescription>
<imports>
<import name="org.apache.ctakes.typesystem.types.TypeSystem"/>
</imports>
</typeSystemDescription>
was (Author: chenpei):
Douglas,
The error looks slightly different- The original one had edu.mayo references
and was missed during re-factoring.
However, the fix should be fairly straight forward. Could you clarify which
xml descriptor were using that caused this error?
The temp work around is to add in your xml: Similar to what was done in in
(https://issues.apache.org/jira/browse/CTAKES-208)
<typeSystemDescription>
<imports>
<import name="org.apache.ctakes.typesystem.types.TypeSystem"/>
</imports>
</typeSystemDescription>
> negation annotator - Sentence type used in code not in descr
> ------------------------------------------------------------
>
> Key: CTAKES-48
> URL: https://issues.apache.org/jira/browse/CTAKES-48
> Project: cTAKES
> Issue Type: Improvement
> Reporter: Pei Chen
> Priority: Minor
>
> Found at the SHARPn summit/f2f:
> tried to run the negation annotator by itself and this error was thrown:
> Caused by: org.apache.uima.cas.CASRuntimeException: JCas type
> "edu.mayo.bmi.uima.core.type.textspan.Sentence" used in Java code, but was
> not declared in the XML type descriptor.
> at org.apache.uima.jcas.impl.JCasImpl.getType(JCasImpl.java:412)
> at org.apache.uima.jcas.impl.JCasImpl.getCasType(JCasImpl.java:436)
> at org.apache.uima.jcas.impl.JCasImpl.getAnnotationIndex(JCasImpl.java:1531)
> at edu.mayo.bmi.uima.context.ContextAnnotator.process(ContextAnnotator.java:2
--
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
