Hi,
we have tested our UIMA AS client with the RoomNumberAnnotator from UIMA
AS examples and, in this particular case, the UIMA AS client retrieves
the proper typeSystem.
When it has to do with our UIMA AS pipeline, the UIMA AS client only
retrieves the default UIMA type system, not the one from the AS service.
Our UIMA AS service has been tested through CVD and it seems right.
We have pasted the code of our client here: http://pastebin.com/zrSeMZe8
Regards,
David
El 20/12/2010 18:32, Jaroslaw Cwiklik escribió:
Can you deploy RoomNumberAnnotator from UIMA AS examples and connect your
client to it to see if you get service types. You should see
type: org.apache.uima.tutorial.RoomNumber.
The example is in
UIMA_HOME/examples/deploy/as/Deploy_RoomNumberAnnotator.xml. Queue
name: RoomNumberAnnotatorQueue
-Jerry C
On Mon, Dec 20, 2010 at 4:49 AM, Jens Grivolla
<[email protected]<j%[email protected]>
wrote:
On 12/19/2010 09:36 PM, Burn Lewis wrote:
To see what typesystem is returned by your service you can turn up the
logging when invoking runRemoteAsyncAE.
and you'll see the service's typesystem as part of the metadata returned
to
the client.
Ok, we do obtain an XML with<analysisEngineMetaData> that contains the
full type system. It also shows up correctly in the CVD.
However, when trying to get the type system from a Java client, we only get
the default UIMA type system, not the one from the AS service.
We initialize a UimaAsynchronousEngine and then call .getCAS() on it to
obtain an empty CAS and .getTypeSystem() on that CAS. Getting all types via
.getTypeIterator() shows only the base UIMA types. Our understanding was
that the CAS obtained from the UimaAsynchronousEngine would have the AS
service's type system.
Thanks,
Jens (and David - we work together in case you were getting confused with
the names)
