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

[jira] Closed: (UIMA-125) Apache UIMA client should be able to communicate with IBM UIMA (1.x or 2.0) service

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

Thilo Goetz closed UIMA-125.
----------------------------

    Resolution: Won't Fix

We won't do this in the Apache code.  IBM will provide bridge code that makes older IBM UIMA versions play with Apache UIMA 2.2 and later.  This bridge code requires updates to IBM UIMA code, so this needs to be done on the IBM side.  Hopefully, the need for this kind of bridge code will soon go away.


> 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
>            Assignee: 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.
-
You can reply to this email to add a comment to the issue online.