[
https://issues.apache.org/jira/browse/UIMA-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally updated UIMA-125:
----------------------------
Fix Version/s: (was: 2.1)
2.2
As posted to uima-dev we're not going to get to this for 2.1. Pushing back to
the next version, tenatively called 2.2 and scheduled for May 15. We can
always change the number of release date later.
> 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.2
>
> 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
