[
https://issues.apache.org/jira/browse/UIMA-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476146
]
Thilo Goetz commented on UIMA-322:
----------------------------------
I still don't quite understand. The CAS we send out is what you call a 1.x CAS
with a single text sofa. It comes back from the Vinci service without the
sofa. That seems odd. Is there a way to tell the Vinci service to send
everything back? If not, is there an easy way to modify the XCAS deserializer
to deal with these kinds of XCASes? Saving the document text and later adding
it back to the CAS is no problem, but the XCAS deserializer shouldn't crash.
> UIMA 1.4 XCAS deserialization does not work with 1.4 Vinci adapter
> ------------------------------------------------------------------
>
> Key: UIMA-322
> URL: https://issues.apache.org/jira/browse/UIMA-322
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
> Affects Versions: 2.1
> Reporter: Thilo Goetz
>
> Michael and I were trying to get UIMA 2.1 to work with a Vinci server running
> UIMA 1.4. We adapted the 1.4 XCAS serializer to work with UIMA 1.4, and got
> the 2.1-to-1.4 transport working, we think. The reverse direction though
> didn't work. 1.4 XCASes can be deserialized ok (after at least one
> sofa-related bug is fixed). However, CASes from Vinci seem to be missing the
> document text (on purpose, probably), and the document text is what triggers
> the sofa compatibility code. When that code is not triggered, an exception
> is thrown later. Michael says he remembers that we've seen and fixed a
> similar issue for 1.4.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
