You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jerry Cwiklik (JIRA)" <de...@uima.apache.org> on 2013/11/02 18:33:18 UTC

[jira] [Commented] (UIMA-2685) Add support for deploying co-located remote UIMA-AS services

    [ https://issues.apache.org/jira/browse/UIMA-2685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812080#comment-13812080 ] 

Jerry Cwiklik commented on UIMA-2685:
-------------------------------------

Deferred beyond 2.4.2 release

> Add support for deploying co-located remote UIMA-AS services 
> -------------------------------------------------------------
>
>                 Key: UIMA-2685
>                 URL: https://issues.apache.org/jira/browse/UIMA-2685
>             Project: UIMA
>          Issue Type: New Feature
>          Components: Async Scaleout
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>
> Add support for deploying remote UIMA-AS service in the same jvm as its client. This co-location will eliminate serialization/deserialization overhead as well as the network overhead. The service will be deployed using jms queue managed by an internal AMQ broker. The client and the service will connect to the internal broker using vm protocol. To facilitate the above, we need changes to dd2spring.xsl as well changes in the UIMA_Service and ServiceDeployer. In dd2spring we need:
> 1) internal AMQ broker and ConnectionFactory for vm-style connections
> 2) JMS Queue for the service
> 3) Listener on the input queue, associated InputChannel and request handler chain
> 4) For aggregate deployment descriptor, need a Listener on service reply queue, associated InputChannel and request+reply handler chain
> The UIMA_Service is already setup for accepting multiple deployment descriptors, but needs works to support deployments of multiple services into Spring containers. 



--
This message was sent by Atlassian JIRA
(v6.1#6144)