You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@uima.apache.org by "Jerry Cwiklik (JIRA)" <de...@uima.apache.org> on 2013/08/20 22:30:52 UTC

[jira] [Commented] (UIMA-1227) Help users debug binary CAS serialization problems

    [ https://issues.apache.org/jira/browse/UIMA-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13745367#comment-13745367 ] 

Jerry Cwiklik commented on UIMA-1227:
-------------------------------------

Defer beyond 2.4.2 Release
                
> 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
>    Affects Versions: 2.3AS
>            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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira