You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Adam Lally (JIRA)" <ui...@incubator.apache.org> on 2006/12/12 17:15:21 UTC
[jira] Created: (UIMA-125) Apache UIMA client should be able to
communicate with IBM UIMA (1.x or 2.0) service
Apache UIMA client should be able to communicate with IBM UIMA (1.x or 2.0) service
-----------------------------------------------------------------------------------
Key: UIMA-125
URL: http://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: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (UIMA-125) Apache UIMA client should be able to
communicate with IBM UIMA (1.x or 2.0) service
Posted by "Michael Baessler (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Baessler updated UIMA-125:
----------------------------------
Attachment: OmniFindTypeSystem.xml
> 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
[jira] Commented: (UIMA-125) Apache UIMA client should be able to
communicate with IBM UIMA (1.x or 2.0) service
Posted by "Adam Lally (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463588 ]
Adam Lally commented on UIMA-125:
---------------------------------
Eddie's the expert, but my understanding is that you CAN deserialize a v1.x XCAS in v2.x, without having to do anything special. It should just work. I think we even have test cases for that, there are some example v1 XCASes in uimaj-core/src/test/resources/ExampleCas.
The problem for service compatibility is that v2 cannot *generate* v1-style XCASes, and v1 of course can't read v2-style XCASes. So we have one-way communication only.
> 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
[jira] Commented: (UIMA-125) Apache UIMA client should be able to
communicate with IBM UIMA (1.x or 2.0) service
Posted by "Michael Baessler (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463608 ]
Michael Baessler commented on UIMA-125:
---------------------------------------
I did some tests with the current CVD and try to load a type system deserialized with version v1.x without success.
The exception is:
/10/07 4:48:20 PM - 10: org.apache.uima.tools.annot_view.MainFrame.handleException(1726): SEVERE: Trying to define feature "sofa" on type "uima.tt.TTAnnotation" with range "uima.cas.Integer", but feature has already been defined on (super)type "uima.cas.AnnotationBase" with range "uima.cas.Sofa".
CASAdminException: Trying to define feature "sofa" on type "uima.tt.TTAnnotation" with range "uima.cas.Integer", but feature has already been defined on (super)type "uima.cas.AnnotationBase" with range "uima.cas.Sofa".
at org.apache.uima.cas.impl.TypeSystemImpl.addFeature(TypeSystemImpl.java(Compiled Code))
at org.apache.uima.cas.impl.TypeSystemImpl.addFeature(TypeSystemImpl.java:530)
at org.apache.uima.util.CasCreationUtils.setupTypeSystem(CasCreationUtils.java:1009)
at org.apache.uima.util.CasCreationUtils.doCreateCas(CasCreationUtils.java:564)
at org.apache.uima.util.CasCreationUtils.createCas(CasCreationUtils.java:345)
Can that be fixed in the code?
> 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
[jira] Commented: (UIMA-125) Apache UIMA client should be able to
communicate with IBM UIMA (1.x or 2.0) service
Posted by "Adam Lally (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463574 ]
Adam Lally commented on UIMA-125:
---------------------------------
XCAS service communication between Apache UIMA 2.1 and IBM UIMA 2.0 already works. Compatibility with 1.x may not be critical since 1.x users should be able to switch to using the IBM UIMA 2.0 runtime without changing any of their code, and thus acheive service-compatibility with Apache UIMA.
> 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
[jira] Updated: (UIMA-125) Apache UIMA client should be able to
communicate with IBM UIMA (1.x or 2.0) service
Posted by "Adam Lally (JIRA)" <ui...@incubator.apache.org>.
[ 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
[jira] Commented: (UIMA-125) Apache UIMA client should be able to
communicate with IBM UIMA (1.x or 2.0) service
Posted by "Eddie Epstein (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463951 ]
Eddie Epstein commented on UIMA-125:
------------------------------------
Michael, for some reason OmniFindTypeSystem.xml is redefining the features already in the supertype, uima.tcas.Annotation. Perhaps this is for readability (?) but in general seems like a bad idea. At any rate, the rangetype of the "sofa" feature changed in UIMA v2.0 to be uima.cas.Sofa.
Eddie
> 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
[jira] Commented: (UIMA-125) Apache UIMA client should be able to
communicate with IBM UIMA (1.x or 2.0) service
Posted by "Adam Lally (JIRA)" <ui...@incubator.apache.org>.
[ 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
[jira] Commented: (UIMA-125) Apache UIMA client should be able to
communicate with IBM UIMA (1.x or 2.0) service
Posted by "Adam Lally (JIRA)" <ui...@incubator.apache.org>.
[ 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
[jira] Commented: (UIMA-125) Apache UIMA client should be able to
communicate with IBM UIMA (1.x or 2.0) service
Posted by "Michael Baessler (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463946 ]
Michael Baessler commented on UIMA-125:
---------------------------------------
The typesystem is not self written, it is serialized from an application. So maybe there is a bug in the old serialization of version 1.x?
> 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
[jira] Commented: (UIMA-125) Apache UIMA client should be able to
communicate with IBM UIMA (1.x or 2.0) service
Posted by "Michael Baessler (JIRA)" <ui...@incubator.apache.org>.
[ 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
[jira] Closed: (UIMA-125) Apache UIMA client should be able to
communicate with IBM UIMA (1.x or 2.0) service
Posted by "Thilo Goetz (JIRA)" <ui...@incubator.apache.org>.
[ 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.
[jira] Commented: (UIMA-125) Apache UIMA client should be able to
communicate with IBM UIMA (1.x or 2.0) service
Posted by "Thilo Goetz (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463581 ]
Thilo Goetz commented on UIMA-125:
----------------------------------
I thought there was an issue with XCAS 1.x/2.0 interoperability because the Sofa datastructure in the CAS had changed. I remember trying to load 1.x XCASes for test cases, and that wouldn't work. Do we have code that takes care of that at the services level? If so, can I use that code to make, for example, CVD XCAS version agnostic?
> 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