On Fri, Oct 23, 2009 at 10:34 AM, Marshall Schor <m...@schor.com> wrote: >> Ah, when async=false the aggregate is instantiated by core UIMA, >> including the delegate represented by a JMS client. When async=true, >> UIMA AS is deploying each delegate itself, and the core UIMA method >> used does not support instantiating a CustomResourceSpecifier. >> >> It does not make sense to deploy a JMS client by itself in an async >> aggregate. In fact it is just a remote delegate, and should be so >> designated in the deployment descriptor. >> > > I'm not sure I agree - how about a use case where a non-AS pipeline has > a delegate which is a JMS client, and then the user wants to "convert" > that pipeline into an AS deployment, to get more throughput on a > multi-core machine, for instance. (I'm not saying that we should do > this for 2.3.0, but it could go on the list for the following release).
This is exactly the scenario. In order to convert to AS deployment, one creates an AS deployment descriptor. If a delegate is remote, it is declared as remote. > Isn't this also reasonable for SOAP deployments (which also currently > don't work)? Might be reasonable for remote SOAP services, if anyone is using them. Also, remote call overhead to a SOAP service is much greater than with JMS services. Eddie
