[jira] Updated: (UIMA-1405) Uima AS not allowing deployment of more than one deployment descriptor in the same jvm

["Marshall Schor (JIRA)" <ui...@incubator.apache.org>]

     [ https://issues.apache.org/jira/browse/UIMA-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marshall Schor updated UIMA-1405:
---------------------------------

    Affects Version/s: 2.3AS

deferred beyond 2.3.0 release

> Uima AS not allowing deployment of more than one deployment descriptor in the same jvm
> --------------------------------------------------------------------------------------
>
>                 Key: UIMA-1405
>                 URL: https://issues.apache.org/jira/browse/UIMA-1405
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>    Affects Versions: 2.3AS
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>            Priority: Minor
>
> Uima AS fails with ResourceInitializationException when one tries to deploy more than one deployment descriptor using deployAsyncService script. The problem is that components in generated spring context files are deployed into a single Spring container. But each spring context files defines singleton objects that are not meant to be used externally. An example of such non-shared singleton would the InProcessCache. It is meant to be shared by components defined in a single context file. There are few possibly solutions here:
> 1) modify dd2spring to assign unique names to spring beans to prevent sharing across context files. 
> 2) modify uima-as deployer to deploy each context file in a separate spring container
> 3) find a way to prevent spring from sharing singleton objects across context files.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.