[
https://issues.apache.org/jira/browse/UIMA-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463950
]
Adam Lally commented on UIMA-125:
---------------------------------
Ah, I see now that ALL your annotation types have all the features on them. In
other words, whatever serialization was used isn't making use of inheritance,
it is redefining every supertype feature on every subtype.
Do you know what code was used to do the type system serialization? The only
code in the UIMA SDK that does this (that I know of) is
org.apache.uima.util.TypeSystemUtil, which has a method to convertt a
TypeSystem to a TypeSystemDescription, after which
TypeSystemDescription.toXML() can be used to write this out. But I don't
believe this code was ever broken in this way.
> Apache UIMA client should be able to communicate with IBM UIMA (1.x or 2.0)
> service
> -----------------------------------------------------------------------------------
>
> Key: UIMA-125
> URL: https://issues.apache.org/jira/browse/UIMA-125
> Project: UIMA
> Issue Type: Improvement
> Components: Transport Adapters - SOAP, Vinci
> Reporter: Adam Lally
> Assigned To: Eddie Epstein
> Fix For: 2.1
>
> Attachments: OmniFindTypeSystem.xml
>
>
> For ease of migration it is important that an application running Apache UIMA
> should be able to call services deployed under previous versions of UIMA.
> Previous discussions with Eddie have indicated this would be fairly
> straightforward for single-Sofa CASes, not necessarily for CASes containing
> multiple Sofas. Possibly support for single-Sofa CASes only is sufficient,
> as that would still help migration for the vast majority of UIMA users.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
