[
https://issues.apache.org/jira/browse/UIMA-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649477#action_12649477
]
Marshall Schor commented on UIMA-1227:
--------------------------------------
If it was an issue, instead of returning the whole type system in some binary
format, we could compute a hashcode for the type system on both sides, and send
that over for comparison.
> Help users debug binary CAS serialization problems
> --------------------------------------------------
>
> Key: UIMA-1227
> URL: https://issues.apache.org/jira/browse/UIMA-1227
> Project: UIMA
> Issue Type: Improvement
> Components: Async Scaleout
> Reporter: Eddie Epstein
>
> In order to use binary CAS serialization for remote services, both client and
> service must have identical type systems. If not the same, binary
> deserialization is likely to throw exceptions. The service request handler
> should catch these exceptions when using binary deserialization and add
> message suggesting a likely cause of the problem: unequal type systems.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
