[jboss-jira] [JBoss JIRA] Resolved: (JBMICROCONT-187) Complete the single deployment api

[Ales Justin (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBMICROCONT-187?page=all ]

Ales Justin resolved JBMICROCONT-187.
-------------------------------------

    Fix Version/s:  JBossMC-2.0.0.Beta7
                       (was: JBossMC-2.0.0.GA)
       Resolution: Done

The deploy()/undeploy() methods now take optional multiple parameters --> Deployment... deployments.
Deploy is an atomic operation, meaning all param deployments succeed or none of them is deployed.

To be able to look at the 'checkComplete' for particular Deployment instance, a change to Deployment(Unit|Context) was required to hold the keys of ControllerContexts that the owner Deployment created. It's the responsibility of (real) deployers to fill this keys.

> Complete the single deployment api
> ----------------------------------
>
>                 Key: JBMICROCONT-187
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-187
>             Project: JBoss MicroContainer
>          Issue Type: Task
>          Components: Deployment
>            Reporter: Adrian Brock
>         Assigned To: Ales Justin
>             Fix For:  JBossMC-2.0.0.Beta7
>
>
> The single deployment api needs finishing.
> 1) deploy()/undeploy() on the DeployerClient/MainDeployer need making threadsafe such
> that they only do work on the deployment passed a parameter
> 2) The incomplete checking for a single deployment needs to "know" look at only those microcontainer
> contexts that it created (+ those contexts/deployments referenced as dependencies).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira