Main Deployer ------------- Key: JBMICROCONT-5 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-5 Project: JBoss MicroContainer Issue Type: Task Components: Deployment Reporter: Adrian Brock Assigned To: Scott M Stark Fix For: JBossMC_2_0_0 Beta3 MainDeployer ------------ The primary methods of MainDeployer are (re/un)deploy(URL) other methods are (un)register/register(deployer, priority) which will be used by the microcontainer when a deployer is installed stats based methods that expose information from the VDF and config/constructors methods for things like the VDF and initial deployers. deploy(url) 1) create a skeleton VDF context for the top level deployment 2) ask the structural component chain who recognises it repeat recursively for identified subcontexts 3) invoke down the deployment component chain starting with the deepest subcontexts first redeploy(url) similar to deploy() but performing a reinstall on the microcontainer (i.e. suspend on valve for components being reinstalled) undeploy(url) invoke down the deployment chain in reverse order to remove the installed components Reverse order means both in terms of subcontexts and priority. (un)register/register(deployer) The deployer here identifies the structural and deployment components of the deployer and their respective "priorities". This will be the name in the registry which might be instantiated later. Where present, the deployer is added to the relevent chain. ISSUE: Need to tighten up the semantics of the register/unregister(deployer) for when the deployment component has dependencies and cannot be instantiated immediately