uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Burn Lewis (JIRA)" <uima-...@incubator.apache.org>
Subject [jira] Commented: (UIMA-999) Should have a way to ignore or omit the imports in an aggregate that will be overridden by the deployment descriptor
Date Fri, 02 May 2008 20:40:55 GMT

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

Burn Lewis commented on UIMA-999:
---------------------------------

If all of the delegates can be run on one machine then the procedure might be:
1) Develop and test aggregate directly (i.e. not async)
2) Add Deployment Descriptor and run async with all co-located
3) Deploy some delegates as services and run async with overrides in the DD

But if any delegates are already deployed remotely or must be run on another machine then
we'll have to use JMS Service Descriptors with base uima or DDs with uima-as.

I suggest we recommend that developers start with JMS Service Descriptors in the aggregate,
and we modify the DDE to read these when first creating a DD and so fill in the the broker
and queue names for each remote delegate.  This would make the initial setup familiar to Vinci
users, and let them modify their deployment incrementally, e.g. by adding EH to the initial
overrides.

I would not recommend pushing any broker or queue changes made to the DD back to the aggregate
(it may be shared by other DDs.)  But it might help to warn when loading a DD if any entries
don't match the overriden ones in the JMS service descriptor.

> Should have a way to ignore or omit the imports in an aggregate that will be overridden
by the deployment descriptor
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: UIMA-999
>                 URL: https://issues.apache.org/jira/browse/UIMA-999
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>            Reporter: Burn Lewis
>            Priority: Minor
>
> Entries in the deployment descriptor for a delegate override the import specified in
the aggregate descriptor for that delegate ... but the import must still be present and valid.
 It would be nice to have a way to indicate that such imports will be overriden and should
be ignored.

-- 
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