[jira] [Updated] (UIMA-4991) eliminate need for shared data parameter in xmi serialization

["Marshall Schor (JIRA)" <de...@uima.apache.org>]

     [ https://issues.apache.org/jira/browse/UIMA-4991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marshall Schor updated UIMA-4991:
---------------------------------
    Fix Version/s:     (was: 2.8.2SDK)

> eliminate need for shared data parameter in xmi serialization
> -------------------------------------------------------------
>
>                 Key: UIMA-4991
>                 URL: https://issues.apache.org/jira/browse/UIMA-4991
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Core Java Framework
>    Affects Versions: 2.8.1SDK
>            Reporter: Marshall Schor
>            Assignee: Marshall Schor
>            Priority: Minor
>             Fix For: 3.0.0SDKexp
>
>
> The recent problem ( UIMA-4990 ) was caused by an improper use of a mostly undocumented parameter in the XMI serialization API - the XmiSerializationSharedData parameter.  This is used for handling out-of-type-system data when sending a CAS to a remote service, and for merging multiple CASes being returned from multiple remote services.  
> It is easy to misuse, and can result in strange errors (e.g. UIMA-4990 ).  
> This improvement would move this to be an internal capability, no longer exposed in the API (existing API uses with it would be deprecated; instances of this, if passed in, would be ignored in favor of internal memory for this).
> This would enable automatic management of this data. There is a similar concept in the experimental Uima V3 prototype and an extra CAS Api for eliminating the extra storage if sophisticated users know early on it won't be needed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)