Hi,
Very good. The Deploy_MeetingDetectorTAE.xml does not have a CR in the
aggregate either. It is designed to be used with a driver as you have done,
or by plugging a CR into the UimaAsynchronousEngine as is done in the
README example. This approach is scalable by increasing the number of
process
Just to post an update on my own message:
In the full version, I was able to fix it by not adding the Collection Reader
to
the AsychronousEngine but just initializing it without and afterwards doing
it manually:
reader.initialize();
while (reader.hasNext())
ae.sendCAS(reader.getNext(ae.getCA
Hi Eddie,
Thanks for the suggestion. I have limited time to work on this so my
response may be slow now and again, but I'm still working on it. Your input
is very much appreciated!
First of all, the command:
runRemoteAsyncAE.sh/cmd tcp://localhost:61616
MeetingDetectorTaeQueue \
-d D
Hi Egbert,
The README file for UIMA-AS shows an application example with
Deploy_MeetingDetectorTAE.xml.Does that run OK for you?
Assuming yes, can you give more details about the scenario, perhaps the
explicit commands used? The descriptors used?
Eddie
On Mon, Jul 28, 2014 at 11:46 AM, Egbert
This error comes from UIMA-AS client not the pipeline code. From what I can
see
the UIMA-AS received getMeta reply from the service (your pipeline). This
means
that it connected to the service and it received a reply.
The only thing that comes to my mind is to check the Map that you pass in
to the
Hi,
I'm trying to convert an existing and functional UIMA pipeline to a UIMA AS
pipeline.
I'm getting there, I created deployment descriptors for the annotators and when
running my application all individual annotators are launched correctly. The
composite
analysis engine also loads fine but
