[
https://issues.apache.org/jira/browse/UIMA-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463937
]
Adam Lally commented on UIMA-125:
---------------------------------
The error is because in your type system, type TTAnnotation explicitly defnies
the "sofa" feature, which we didn't expect users to be doing. Between 1.x and
2.0 the range type of the sofa feature changed from an integer to a reference,
which is why you're getting an error. Just delete the sofa feature (and maybe
begin, end while you're at it) from TTAnnotation and then it should work. This
may be a good thing to document where we say what the changes from 1.x to 2.0
are, just in case anyone else stumbles into this... but I expect it to be quite
rare.
> 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
