Return-Path: 
 <uima-user-return-2734-apmail-incubator-uima-user-archive=incubator.apache.org@incubator.apache.org>
Delivered-To: apmail-incubator-uima-user-archive@minotaur.apache.org
Received: (qmail 63048 invoked from network); 11 Dec 2009 19:38:45 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 11 Dec 2009 19:38:45 -0000
Received: (qmail 8036 invoked by uid 500); 11 Dec 2009 19:38:44 -0000
Delivered-To: apmail-incubator-uima-user-archive@incubator.apache.org
Received: (qmail 7992 invoked by uid 500); 11 Dec 2009 19:38:44 -0000
Mailing-List: contact uima-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:uima-user-help@incubator.apache.org>
List-Unsubscribe: <mailto:uima-user-unsubscribe@incubator.apache.org>
List-Post: <mailto:uima-user@incubator.apache.org>
List-Id: <uima-user.incubator.apache.org>
Reply-To: uima-user@incubator.apache.org
Delivered-To: mailing list uima-user@incubator.apache.org
Received: (qmail 7982 invoked by uid 99); 11 Dec 2009 19:38:44 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Dec 2009 19:38:44 +0000
X-ASF-Spam-Status: No, hits=-2.6 required=5.0
	tests=BAYES_00
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of eaepstein@gmail.com
 designates 74.125.78.145 as permitted sender)
Received: from [74.125.78.145] (HELO ey-out-1920.google.com) (74.125.78.145)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Dec 2009 19:38:41 +0000
Received: by ey-out-1920.google.com with SMTP id 3so341666eyh.8
        for <uima-user@incubator.apache.org>;
 Fri, 11 Dec 2009 11:38:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:received:in-reply-to:references
         :date:message-id:subject:from:to:content-type;
        bh=/zr1MiplSVgD8IMKKnibth387rJfA8SFA+rNgsgXRck=;
        b=juWfyngFDG0O3/0jaOxOvkNBkEv6EISlnEG+t8EvJWtcCqhf7r1XOQ6xxrlqF/cMni
         jUI0v5mE6mi2xm5xHg5yu0NWNgwISK7OL4ZdbEGk+WzrJhdPX5UpwIykhnQfcenhs3US
         eVFA53u+re8dAZjROEYsV/+kxRSKbdUFGJtCc=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=IAGiwWihwGyQshd/Kb6SYRECKknnrI3sxfa+Q02tVz5wjDZ13KTcUG/eRLfQ2LOawe
         hZiiWX5nAdL+rXjp9LdjQxyCchN8TgWm28meNtJ1A0THHu6PcsFAmu5c2HCEuNs93aTP
         OyYm0K0wsTWIW0nBZUVMkhlNvAkUl8mUmAzzg=
MIME-Version: 1.0
Received: by 10.216.89.18 with SMTP id b18mr693841wef.14.1260560300560; Fri,
	11 Dec 2009 11:38:20 -0800 (PST)
In-Reply-To: <4B225181.3020907@gmx.de>
References: <4B20FD72.6020805@neofonie.de> <4B21171E.8080702@neofonie.de>
	 <cd6edfd30912101347s4b90048au3cc7bc1861041cf@mail.gmail.com>
	 <4B225181.3020907@gmx.de>
Date: Fri, 11 Dec 2009 14:38:20 -0500
Message-ID: <cd6edfd30912111138h9d9762fva14e3264019f9152@mail.gmail.com>
Subject: Re: Problems with "deserializeCasFromXmi" after using C++ AS
	Annotator
From: Eddie Epstein <eaepstein@gmail.com>
To: uima-user@incubator.apache.org, christophbuescher@gmx.de
Content-Type: text/plain; charset=ISO-8859-1

Hi,

Well, I tried another, simpler scenario based on your description:

Just add the following to DaveDetector.xml:
    <typeDescription>
      <name>uima.tcas.Chris</name>
      <description></description>
      <supertypeName>uima.tcas.Annotation</supertypeName>
      <features>
  	<featureDescription>
  	  <name>documentURL</name>
  	  <description></description>
  	  <rangeTypeName>uima.cas.String</rangeTypeName>
  	</featureDescription>
      </features>
    </typeDescription>

Create the following CasXmi file:
<?xml version="1.0" encoding="UTF-8"?>
<xmi:XMI xmlns:cas="http:///uima/cas.ecore"
xmlns:tcas="http:///uima/tcas.ecore"
xmlns:xmi="http://www.omg.org/XMI"  xmi:version="2.0">
<cas:NULL xmi:id="0"/>
 <cas:Sofa xmi:id="1" sofaNum="1" sofaID="_InitialView"
mimeType="text" sofaString="This is a text document with Dave for
analysis"/>
 <tcas:DocumentAnnotation xmi:id="8" sofa="1" begin="0" end="46" language=""/>
 <tcas:Chris xmi:id="20" sofa="1" begin="0" end="1"
documentURL="http://www.gesundheitsnachrichten.net/live/navigation/live.php?navigation_id=11&amp;_psmand=1"/>
<cas:View sofa="1" members="8 20"/>
</xmi:XMI>

Launch the unaltered DaveDetector as a service, have CVD connect to it
via JMS service descriptor, use File->Read Xmi Cas File to load the test Cas,
use Run->Run DaveDetector On CAS to call the remote service, and, finally
expand the annotation index to see the results. No problems.

This was using something close to uima-2.3.0.

Eddie



On Fri, Dec 11, 2009 at 9:04 AM, Christoph Buescher
<christophbuescher@gmx.de> wrote:
> Hi Eddie,
>
> unfortunately I'm out of the office today so I can only send you the unit
> test reproducing the problem on monday. But our scenario is more or less the
> following:
>
> - A CPE running several Java AEs first, then send the CAS to a remote AS
> Service which is a C++ AE
> - the collection reader adds a FS with document metadata (including the
> String Feature "URL") to the CAS. This FS directly extends the Top-Type, not
> Annotation.
> - I used the unaltered DaveDetector to replace our own C++ AE to reproduce
> the problem
>
> For the unit test I wrote a "No-OP" Java AE which uses a Typesystem only
> including this "DocumentData" FS with only this one String Feature. I used a
> Custom Resource Specifier like in the AS Documentation to reference the
> DaveDetector on a remote machine. I then create a CAS using the
> CasCreationUtil which in turn uses the "No-OP" AE descriptor and the
> DaveDetector-Resource Specifier. I then add the problematic Feature in
> question and call "process" on the remote Dave-AE. Then the exception I
> mentioned in my earlier mail happens.
>
> I will send you the test code on monday and also try to use CVD to reproduce
> the problem.
>
> Thanks,
> Christoph