Manuel Lamy created CTAKES-490:
----------------------------------
Summary: cTAKES 4.0.1-SNAPSHOT - Problem with CVD and
AggregatePlaintextFastUMLSProcessor
Key: CTAKES-490
URL: https://issues.apache.org/jira/browse/CTAKES-490
Project: cTAKES
Issue Type: Bug
Components: ctakes-clinical-pipeline
Affects Versions: 4.0.0
Environment: Local
Reporter: Manuel Lamy
Fix For: 4.0.0
Attachments: Problem_ProofOne.JPG, Problem_ProofThree.JPG,
Problem_ProofTwo.JPG
Hello,
I'm aiming to extend cTAKES in order to fulfill the objectives of a project I'm
working on. So I decided to check out the code of trunk and start checking it.
I followed all tthe steps of the developer's guide found here:
https://cwiki.apache.org/confluence/display/CTAKES/cTAKES+4.0+Developer+Install+Guide
I'm using Intellij by the way. Well, when I launch CVD from Intellij in order
to test some changes I made in the code, I have a problem. I want to use the
AggregatePlaintextFastUMLSProcessor. When I try to load it in the CVD UI, I
have the following error:
-----------------
<exception>
<message>org.apache.uima.resource.ResourceInitializationException: An
import could not be resolved. No file with name
"org/apache/ctakes/drugner/types/TypeSystem.xml" was found in the class path or
data path. (Descriptor:
file:/C:/Users/User/Desktop/Tese_Mestrado_NLP/cTAKES_Project_NLP_Dev/ctakes/ctakes-drug-ner/desc/analysis_engine/DrugMentionAnnotator.xml)
-----------------
I can't understand why this exception happens at all. The
DrugMentionAnnotator.xml indeed has an import of the TypeSystem.xml file. And
this TypeSystem.xml file physically exists in the path described in the
DrugMentionAnnotator.xml import. So, I don't really know why I have this error
in CVD, since the file that is originating the problem exists indeed in the
expectable path described in the DrugMentionAnnotator.xml import.
I also add images as attachments that show the import in the
DrugMentionAnnotator.xml and the proof that the file being imported (and the
cause of the exception) actually exists where it should exist.
Since I have followed all the steps in the Developer's Guide, I consider this
to be a problem and decided to report it. I'm also blocked at the moment
because of it.
If you need additional information don't hesitate in demanding.
*Expected result:* load AggregatePlaintextFastUMLSProcessor succesfully.
*Obtained result: * loading AggregatePlaintextFastUMLSProcessor raises an
exception.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
