[UIMA-5776] Calling a UIMACPP engine causes rules on prior annotations to fail

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: C++ Framework, Ruta
• Assignee: Peter Klügl
• Reporter: Benjamin De Boe
• Created: 15/May/18 15:31
• Updated: 29/Oct/21 07:16

Description

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;
W{->Test};

and

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

and 

DECLARE Test;
W W{->Test};

And this trivial one still works as well

Document {-> EXEC(DaveDetector)}; 
DECLARE Test;
W{->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