I don't know if this is it, but I'll offer it up just in case......could 
it be a type system mismatch?   I've had problems in the past where I've 
deserialized CASes and the deserializer was set to "lenient" (which would 
only pull in the types the deserializer recognizes and ignores all 
others).  The default for the XmiCasDeserializer is lenient=false, so, by 
default it should throw an exception if something mismatches.


Joel Dubbels
Senior Software Engineer | Software Group
email: [email protected] | Tel: 507-253-1165










From:
"Coarr, Matt" <[email protected]>
To:
"[email protected]" <[email protected]>
Cc:
"Wellner, Benjamin R." <[email protected]>
Date:
01/17/2012 04:27 PM
Subject:
question about annotation not being loaded



Hello,

We normally use the FileSystemCollectionReader to load in plain text 
files.  This collection reader populates an annotation in the example 
namespace called SourceDocumentInformation (that has a uri that includes 
the full path to the original file).

For some testing, we have a group of generated test xmi files that will be 
used as input.  For this test pipeline we have a new CPE config that uses 
the XmiCollectionReader.  In general this is working great!  We get most 
of our saved annotations loaded into the CAS and everything works great!

The problem we're having is that we've added the 
examples:SourceDocumentInformation annotation to the input test documents 
(xmi docs) along with the required xml namespace declaration 
(xmlns:examples="http:///org/apache/uima/examples.ecore";).  Here's a 
sample (I've replace the real filename and input size with dummy data):

<examples:SourceDocumentInformation xmi:id="10" sofa="1" begin="0" end="0" 
uri="file:/tmp/myfiles/0123.xmi" offsetInSource="0" documentSize="1234" 
lastSegment="false"/>

However, this annotation isn't getting loaded.  We can't see the value in 
our analysis engine, and we're writing these files out at the end with the 
example xmi writer and the SourceDocumentInformation annotation doesn't 
show up in the output xmi files.  So it appears that this annotation isn't 
being loaded or it's being filtered out.

No errors show up either.

Any ideas?  Has anyone run into this before?

Thanks!
Matt


Reply via email to