Uploaded image for project: 'cTAKES'
  1. cTAKES
  2. CTAKES-490

cTAKES 4.0.1-SNAPSHOT - Problem with CVD and AggregatePlaintextFastUMLSProcessor



    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 4.0.0
    • Fix Version/s: 4.0.0
    • Labels:
    • Environment:



      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. I followed all the 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:


      <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.


        1. Problem_ProofTwo.JPG
          97 kB
        2. Problem_ProofThree.JPG
          140 kB
        3. Problem_ProofOne.JPG
          152 kB



            • Assignee:
              alexz Alex Zbarcea
              mlyNlp mlyNLP
            • Votes:
              1 Vote for this issue
              4 Start watching this issue


              • Created: