On 11.10.2017, at 16:01, Marshall Schor <[email protected]> wrote:
>
> fixed in trunk. Thanks for testing :-)
>
> On 10/11/2017 9:50 AM, Marshall Schor wrote:
>> I think I found the cause: a faulty implementation of load(asInputStream,
>> aCAS,
>> typeSystem).
>>
>> Looking at the code, the 3rd argument is not used! It looks like something
>> happened when migrating from V2 -> V3 code base, because it's OK in the v2
>> code
>> base. Maybe I can blame the cat (she sometimes jumps up onto my desk,
>> landing
>> on my keyboard, and randomly pressing keys...) :-)
>>
>> Apologies, and thank goodness for testing...
Now I'm seeing a new exception in the units tests using the three-argument
signature:
org.apache.uima.cas.CASRuntimeException: Type Systems must be committed before
calling this method.
at
org.apache.uima.cas.impl.CasTypeSystemMapper.<init>(CasTypeSystemMapper.java:101)
at
org.apache.uima.cas.impl.TypeSystemImpl.lambda$0(TypeSystemImpl.java:1853)
at java.util.Map.computeIfAbsent(Map.java:957)
at
org.apache.uima.cas.impl.TypeSystemImpl.getTypeSystemMapperInner(TypeSystemImpl.java:1852)
at
org.apache.uima.cas.impl.TypeSystemImpl.getTypeSystemMapper(TypeSystemImpl.java:1841)
at
org.apache.uima.cas.impl.BinaryCasSerDes6.<init>(BinaryCasSerDes6.java:545)
at
org.apache.uima.cas.impl.BinaryCasSerDes6.<init>(BinaryCasSerDes6.java:639)
at
org.apache.uima.cas.impl.BinaryCasSerDes.reinit(BinaryCasSerDes.java:593)
at org.apache.uima.util.CasIOUtils.load(CasIOUtils.java:382)
at org.apache.uima.util.CasIOUtils.load(CasIOUtils.java:344)
at
de.tudarmstadt.ukp.dkpro.core.io.bincas.BinaryCasReader.getNext(BinaryCasReader.java:194)
at
de.tudarmstadt.ukp.dkpro.core.io.bincas.BinaryCasWriterReaderTest.read(BinaryCasWriterReaderTest.java:561)
at
de.tudarmstadt.ukp.dkpro.core.io.bincas.BinaryCasWriterReaderTest.test6Lenient(BinaryCasWriterReaderTest.java:164)
...
Mind, I actually do explicitly call typeSystem.commit() on the type system
passed as the third argument before passing it.
Any immediate ideas?
Best,
-- Richard
