uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marshall Schor (JIRA)" <uima-...@incubator.apache.org>
Subject [jira] Resolved: (UIMA-1040) Modify dd2spring to handle UIMA-AS Aggregate Cas Multipliers
Date Mon, 31 Aug 2009 20:11:33 GMT

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

Marshall Schor resolved UIMA-1040.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.3AS

Also removed restriction in dd2spring limiting remote cas multiplers to 1 per aggregate.

> Modify dd2spring to handle UIMA-AS Aggregate Cas Multipliers
> ------------------------------------------------------------
>
>                 Key: UIMA-1040
>                 URL: https://issues.apache.org/jira/browse/UIMA-1040
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>    Affects Versions: 2.2.2AS
>            Reporter: Jerry Cwiklik
>            Assignee: Marshall Schor
>            Priority: Minor
>             Fix For: 2.3AS
>
>
> dd2spring determines if a component is a Cas Multiplier by checking the component's descriptor
outputsNewCASes property. If the component is a CM, the dd2spring generates spring xml artifacts
to create a special cas pool to be used to create new CASes. For a Primitive CM, this is necessary.
As the Primitive CM actually creates new CASes from an input CAS it needs the special cas
pool. If the CM is an Aggregate, this special cas pool is not necessary. The aggregate CM
*outputs* new CASes, but it doesnt create them. It uses a shadow CAS Pool (one per remote
CM delegate) to deserialize CASes instead. The current dd2spring code generates a warning
when parsing a deployment descriptor containing an aggregate CM:
>       *** WARN: line-number: 34 deployment descriptor for analysisEngine: <key>Queue
is for a CAS Multiplier (or Collection Reader wrapped as a CAS Multiplier).  However, the
&lt;casMultiplier&gt; element is missing. Defaulting to a poolSize of 1 for this case.

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


Mime
View raw message