Virtual Deployment Framework ---------------------------- Key: JBMICROCONT-6 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-6 Project: JBoss MicroContainer Issue Type: Task Components: Deployment Reporter: Adrian Brock Assigned To: Scott M Stark Fix For: JBossMC_2_0_0 Beta VDF - Virtual Deployment Framework ---------------------------------- VDF registry The VDF registry acts as a helper/registry of the VDF contexts. Each deployment is made up a top level VDF context which might contain sub VDF contexts. It does: 1) Unpack subdeployments 2) Download remote deployments 3) Abstract packed/unpacked 4) Allow config/registration of url handlers for things like webdav 5) Supplying "directory" lists, cf (3) and (4) VDF Context The VDF context is a replacement for the DeploymentInfo of current JBoss it holds the following information: name - a name probably a shorted version of the url deployer - the identified structural deployer logicalURL - the url presented to the user physicalURL - the url where it is really located parentVDFContext - any parent VDF context (null when top level) subVDFContexts - any subdeployments classpath - the urls where classes are located metainf - the location of any meta data manifest - any manifest information classloader - constructed by the classloading deployer stats/state - e.g. when deployed, the state of the deployment, any errors, etc There will be a set of utility methods that provide other access, e.g. get me the metadata url for "ejb-jar.xml" VDF Context - extensions Each structural component can extend the VDF context to add more information There will also be a "slot" available for each deployment component to associate some data with the deployment. Context identification ---------------------- A top level deployment must have a structure deployer subdeployments that are not explcitly identifed (cf Default SubContext processing) that don't have deployers are ignored. Explicity identified subdeployments must have a structure deployer Default SubContext processing ----------------------------- All files in the root of the deployment are treated as possible subcontexts