[
https://issues.apache.org/jira/browse/UIMA-476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510700
]
Thilo Goetz commented on UIMA-476:
----------------------------------
Your remarks about the interdependence between the Java and C++ implementations
are correct.
It's not part of this fix, but I don't like the fact that the TypeImpl and type
code ints in TypeSystemImpl are not protected with accessors. They should have
setters and getters, and the setter should be locked after type system commit.
This will make our own debugging life a lot easier if there are ever any
problems with this. When these vars still lived in the CASImpl, we could be
sure that they were instantiated only once. The same should be true now
they've moved to the type system.
> FSArray causes error in SOAP service
> ------------------------------------
>
> Key: UIMA-476
> URL: https://issues.apache.org/jira/browse/UIMA-476
> Project: UIMA
> Issue Type: Bug
> Components: Transport Adapters - SOAP, Vinci
> Affects Versions: 2.1
> Environment: UIMA 2.1 and previous versions
> Reporter: Yoshinobu KANO
> Assignee: Thilo Goetz
> Fix For: 2.2
>
>
> When we run a SOAP service with any type system which uses FSArray,
> AnalysisEngineProcessException occurs,
> though the same component can be run as a local service.
> It occurs in the type system checking, independently of the component
> implementations.
> The error says:
> Caused by: org.apache.uima.UIMARuntimeException: The JCas cannot be
> initialized. The following errors occurred: The JCAS range type
> uima.cas.FSArray for feature <OurFeatureName> of type <OurTypeName> does
> not match the CAS range <OurFeatureTypeName>[] for the feature.
> # replaced our specific feature/type names.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
