[
https://issues.apache.org/jira/browse/UIMA-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474856
]
Eddie Epstein commented on UIMA-322:
------------------------------------
There are two XCAS formats for the v1.x XCAS. There is the original XCAS format
which has no Sofas, used when the CAS is "backwards compatible" (see definition
below) and a second Sofa format used for all other CAS content. A long-standing
optimization (pre v1.0) for vinci services returning a backwards compatible CAS
is not to return the document text.
Therefore, in order to compatible with v1.x vinci services, the transformer
will have to save the document text for backwards compatible CAS going out and
be prepared to utilize that string when the XCAS comes back without the
document.
The document deletion optimization has been dropped in Apache Uima, and the
only format used is the Sofa format.
Backwards compatible CAS:
In v1.x a CAS containing a single text sofa with
name="_DefaultTextSofaName".
In v2 a CAS containing a single sofa with name="_InitialView", with
mimetype="text" and no binary or URL data set.
Eddie
> 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.
