uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin De Boe (JIRA)" <...@uima.apache.org>
Subject [jira] [Created] (UIMA-5776) Calling a UIMACPP engine causes rules on even prior annotations to fail
Date Tue, 15 May 2018 15:32:00 GMT
Benjamin De Boe created UIMA-5776:

             Summary: Calling a UIMACPP engine causes rules on even prior annotations to fail
                 Key: UIMA-5776
                 URL: https://issues.apache.org/jira/browse/UIMA-5776
             Project: UIMA
          Issue Type: Bug
          Components: C++ Framework, Ruta
            Reporter: Benjamin De Boe
         Attachments: Main.java

We're having trouble leveraging a UIMACPP engine from Ruta. Whereas the ENGINE() call doesn't
seem to throw any actual errors, some rules run afterwards don't seem to get triggered correctly,
even if they involve plain Ruta annotations and none of the ones that (should) have been added
by UIMACPP. It doesn't matter whether or not we supply the third argument to ENGINE()


Here are a few tests that illustrate what we're seeing, leveraging the example AE provided
with UIMACPP called "DaveDetector" (you'll need to make sure it's on your PATH to work). Each
time, we should find at least one occurrence of the "Test" annotation in the output.

The following scripts work:

{{DECLARE Test;}}


{{Document \{-> EXEC(DaveDetector)}; }}
{{DECLARE Test;}}


{{DECLARE Test;}}
{{W W\{->Test};}}

And this trivial one still works as well

{{Document \{-> EXEC(DaveDetector)}; }}
{{DECLARE Test;}}

But this one doesn't:

{{Document \{-> EXEC(DaveDetector)}; }}
{{DECLARE Test;}}
{{W W\{->Test};}}


Also attaching a test Java script that runs through these in succession

This message was sent by Atlassian JIRA

View raw message