This bug was due to a wrong design - actually adding JCas implied features into the type system. This breaks various "binary" serialization/deserialization schemes, which require an exact match between the type system and the serialized form.
This is now fixed. The next problem is a housekeeping one: The DKPro being used as a uima v3 alpha version of the JCas class for DocumentMetaData. This needs regenerating for the current design. I'm going to try to do that, but it's taking a very long time to download the dkpro uima-v3 project... -Marshall On 1/18/2018 5:47 PM, Marshall Schor wrote: > found an incredibly stupid bug in the code that was supposed to add the extra > JCas supplied features. > > Guess a better test case is needed!. > > After fixing that, the next bug is a cas complete deserialization issue... > > investigating... > > -Marshall > > > On 1/18/2018 2:06 PM, Marshall Schor wrote: >> Got to the point where I'm getting a JCas feature offset incompatibility - >> starting debug... >> >> -Marshall >> >
