You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Adam Lally (JIRA)" <ui...@incubator.apache.org> on 2007/05/07 23:20:15 UTC

[jira] Reopened: (UIMA-325) Enhance XMI Serializer to support merging multiple XMI documents into a single CAS

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

Adam Lally reopened UIMA-325:
-----------------------------


This fails when the CAS contains multiple Sofas.  Need to add a unit test for that and fix the problem.

> Enhance XMI Serializer to support merging multiple XMI documents into a single CAS
> ----------------------------------------------------------------------------------
>
>                 Key: UIMA-325
>                 URL: https://issues.apache.org/jira/browse/UIMA-325
>             Project: UIMA
>          Issue Type: New Feature
>          Components: Core Java Framework
>            Reporter: Adam Lally
>         Assigned To: Adam Lally
>             Fix For: 2.2
>
>
> The new feature would support the following scenario:
> 1) A CAS is serialized to XMI.
> 2) Copies of the XMI documents are sent to multiple remote services
> 3) Each remote service appends to the CAS (does not delete or modify
> existing stuff) and responds with a new serialized XMI CAS)
> 4) The multiple XMI responses are all merged back into a single CAS instance
> This would permit multiple remote services that don't depend on each
> other to run in parallel, assuming they only append to the CAS (which
> is common).  Of course there's other work on the runtime needed to
> actually do the parallel invocations, but XMI serializer support is a
> prerequisite.
> The basic XMI deserializer changes aren't too complicated.  First,
> when the CAS is originally serialized in step 1, we make available to
> the caller the maximum xmi:id value in that CAS (this is mostly
> already done, we just need to add a public accessor for this value).
> Next, we allow passing this value to the deserializer as an optional
> argument that essentially says "deserialize only XMI elements whose
> xmi:id is greater than the specified value".
> Discussion here: http://www.mail-archive.com/uima-dev@incubator.apache.org/msg02338.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.