[jboss-jira] [JBoss JIRA] Closed: (JBMICROCONT-168) Add a plugin spi to support the ordering of deployment package/bundle processing

[Adrian Brock (JIRA)]

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

Adrian Brock closed JBMICROCONT-168.
------------------------------------

    Fix Version/s: JBossMC-2.0.0.Beta4
                       (was: JBossMC-2.0.0.CR1)
       Resolution: Done

This has been done.

The features added include:

1) Deployment dependencies - microcontainer dependencies on
jmx, pojo, etc. but more likely other deployments.

2) "All or Nothing" deployment, if any subdeployment or component of the deployment
fails then everything in the deployment is undeployed.

3)  "Russian Doll" - each deployer can choose whether it wants parent first or child first
(parent first is the default)

4) A relative order and the ability to specify a Comparator<DeploymentContext>
class implementation on the ContextInfo for that context's children.
The default comparator orders by the relative order and the simple name.

> Add a plugin spi to support the ordering of deployment package/bundle processing
> --------------------------------------------------------------------------------
>
>                 Key: JBMICROCONT-168
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-168
>             Project: JBoss MicroContainer
>          Issue Type: Feature Request
>          Components: Deployment
>    Affects Versions:  JBossMC_2_0_0 Beta3
>            Reporter: Scott M Stark
>         Assigned To: Adrian Brock
>             Fix For: JBossMC-2.0.0.Beta4
>
>
> There are some startup issues in jboss5 due to not having an ordering notion for the DeploymentContexts that go into a MainDeployer.process scan. Probably all of these are due to improper specification of container dependencies, but in general we are going to run into startup issues due to missed dependency declaration. We should have the ability to order the DeploymentContext set via an spi contract that integrates with the structural parse phase. We should have the ability to define this globally ala the legacy directory scanner sorter, as well as per deployment level to allow for alternate deployment packaging models: Russian doll, ear, cross deployment model, etc.

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