[
https://issues.apache.org/jira/browse/UIMA-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463933
]
Michael Baessler commented on UIMA-125:
---------------------------------------
Eddie Epstein wrote:
> Those are type definition errors, not XCAS deserialization errors. As
> Adam said, we have working test cases that deserialize v1 format XCAS.
> Please send or point me at the test data you are using.
Yes, I know that the exception was thrown when loading the type system. But
this was necessary to try to load the XCAS. And if I cannot load the type system
for the XCAS I cannot load the XCAS.
I attached the type system file to the issue
> 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
>
>
> 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
