uima-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthias Wendt" <we...@neofonie.de>
Subject AW: compatibility issues of uimacpp vs. uimaj using uima-as
Date Tue, 03 Nov 2009 12:59:40 GMT
Hello Eddie,

thank you very much for your quick reaction. However, I am sorry to have to note that another
related issue turned out:

I have a FeatureStructure type containing a StringArrayFS typed feature. When I create this
FeatureStructure in a C++ AE and fill the array, everything works fine. But when the FeatureStructure
is  created in another AE and handed into a C++ AE where the array is filled, it does not
come back into any Java application using it (AE/Application). 

The bug does not occur when the C++ TAE is deployed as a JNI driven AE - maybe there is a
bug/incompatibility in the serialization.? Running it as a native process, however, is about
3-4 times faster.

I would really appreciate to have this fixed in the upcoming release - if possible. 

Regards,
Matthias


-----Ursprüngliche Nachricht-----
Von: Eddie Epstein [mailto:eaepstein@gmail.com] 
Gesendet: Mittwoch, 21. Oktober 2009 16:02
An: uima-user@incubator.apache.org
Betreff: Re: compatibility issues of uimacpp vs. uimaj using uima-as

Matthias,

Two issues have been created against UIMACPP, a documentation issue
covering points 1&2 and a getMeta issue not returning <elementType>.

Many thanks for the input,
Eddie


On Wed, Oct 21, 2009 at 5:58 AM, Matthias Wendt
<matthias.wendt@neofonie.de> wrote:
> Hello everybody,
>
> to integrate a uimacpp AE with uimaj AEs, I have tried to deploy the uimacpp
> AE as a UIMA-AS service. During development some compatibility issues arose,
> which I think is worthwile commenting.
>
> 1. uimacpp does not support import by name <import name="..." />, which I
> think is not mentioned in the documentation.
> 2. using <import location="..." /> employs a different path resolving
> strategy from that of uimaj:
>  -  both  support using absolute paths and relative paths (relative to the
> descriptor in which the import occurs)
>  -  uimacpp can be given the environment variable UIMACPP_DATAPATH which is
> additionally used to resolve relative paths
>  - However, uimaj does not support resolving relative <import location="..."
> /> from it's datapath.
> 3. I deployed the uimacpp AE service which has exactly the same typesystem
> as a uimaj AE in the pipeline. However, the CASes are incompatible with the
> following reason:
>  - There is a type 'Constituent' which has a 'children' feature. 'children'
> is of the range type 'FSArray' with the element type 'Constituent'.
>  - However, when getting the typesystem from the uimacpp service, the
> element type is ignored. Both components cannot be plugged into one
> pipeline, because of an exception complaining about incompatible
> typesystems.
>
> I will work around the last issue by altering the typesystem (removing the
> element type), but this is not satisfactory.
>
> Kind regards
> Matthias
>
>
>
>

Mime
View raw message