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 2008/12/19 20:19:44 UTC

[jira] Closed: (UIMA-1257) Type System Merging Should Produce Consistent Ordering of Types

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

Adam Lally closed UIMA-1257.
----------------------------

    Resolution: Fixed

Fixed by sorting types alphabetically inside CasCreationUtils.mergeTypeSystems

> Type System Merging Should Produce Consistent Ordering of Types
> ---------------------------------------------------------------
>
>                 Key: UIMA-1257
>                 URL: https://issues.apache.org/jira/browse/UIMA-1257
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Core Java Framework
>    Affects Versions: 2.2.2
>            Reporter: Adam Lally
>            Assignee: Adam Lally
>            Priority: Minor
>             Fix For: 2.3
>
>
> Currently when type systems are merged across annotators, the ordering of the types produced by the merge method is not defined, and varies according to the ordering in which the individual type system descriptors are passed to the merge method.  The ordering depends on the order in which individual AEs are initialized, which is also not defined, and may even vary according to JVM version.
> One reason to improve this is that UIMA-AS has a feature to allow binary serialization, but it requires that type systems be identical on both sides of the connection, and it is difficult to ensure this if ordering cannot be relied on. 

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