[UIMA-4991] eliminate need for shared data parameter in xmi serialization

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 2.8.1SDK
• Component/s: Core Java Framework
• Assignee: Marshall Schor
• Reporter: Marshall Schor
• Created: 27/Jun/16 21:57
• Updated: 15/Nov/16 22:49

Description

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.

Issue Links

• relates to: UIMA-4990 DUCC's all_in_one fails with UIMA 2.8.1