Uploaded image for project: 'UIMA'
  1. UIMA
  2. UIMA-5256

Ruta/uv3 accomodation, ruta-core


    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.5.0ruta
    • Fix Version/s: 2.6.0ruta
    • Component/s: Ruta
    • Labels:


      These are the minor changes I made to ruta-core to accomodate UIMA v3; I believe they are compatible with V2.

      in Ruta.java

      • the 2nd "inject" method, change the 2nd arg from Annotation ... to FeatureStructureImpl ...
      • remove the 3rd "inject" method - now covered by 2nd.
      • change getAddresses arg list to have type FeatureStructureImpl[]
      • remove the 2nd getAddresses method (now covered by previous one).

      These (above) changes accomodate the fact that there's just one impl of Annotation in v3, and AnnotationImpl is now an interface.
      In RutaEngine, the process method sets a variable:
      boolean typeSystemChanged = lastTypeSystem != cas.getTypeSystem();

      In UIMA V3, loading a new type system which is identical to a previously committed type system, results in the cas.getTypeSystem being == to the "lastTypeSystem". So as a result, you can't use this to determine if a new type system was loaded. The line 484 fails for one test because of this. The workaround is to set "typeSystemChanged" to true, always. But you might have a better solution.


        1. patch.txt
          3 kB
          Marshall Schor



            • Assignee:
              pkluegl Peter Klügl
              schor Marshall Schor
            • Votes:
              0 Vote for this issue
              2 Start watching this issue


              • Created: