Re: How to have client, service and broker co-located using UIMA-AS

Hi Jaroslaw, thank you for the detailed answer on the state of UIMA-AS and its future evolution. My initial quest for co-located components passing CASes by reference was motivated by some experiments with UIMA-AS suggesting that I was not able to outperform a pipeline executed with uimaFIT.

Re: How to have client, service and broker co-located using UIMA-AS

Manuel, the current uima-as code requires a broker between a client and a service even if all are colocated in the same process. This implies CAS serialization/deserialization between endpoints. I am refactoring uima-as code as part of JIRA https://issues.apache.org/jira/browse/UIMA-5280. Once

Re: How to have client, service and broker co-located using UIMA-AS

Hi Jaroslaw Thank you for your answer. Tomorrow, I will apply your suggestions and tell you what happens. Il 4 ott 2017 19:50, "Jaroslaw Cwiklik" ha scritto: > Manuel, small correction. Towards the end replace this > > client.sendCAS(cas); > > with > >

Re: How to have client, service and broker co-located using UIMA-AS

Hi Manuel, you *can* colocate broker, client and a service in the same process. Here is the code to get this done. Sorry did not test this. You need to create a deployment descriptor (xml file) to be able to deploy a service. // Deploy in-process broker String uri = "tcp://"localhost:61616";

How to have client, service and broker co-located using UIMA-AS

Hi everybody Within the documentation of UIMA-AS, specifically within the section Terminology ( https://uima.apache.org/d/uima-as-2.9.0/uima_async_scaleout.html#ugr.async.ov.terminology), the description of Queue Broker says: Queue brokers manage one or more named queues. The brokers are