"adrian(a)jboss.org" wrote : | In fact, I'm aiming for an api where the deployers don't | really deal with the lifecycle directly and instead provide | metadata on which parts of the deployment they want | to do work on and "when". | | e.g. | SARDeployer | I create a ServiceDeployment and LoaderRepositoryConfig from -service.xml | | ServiceDeploymentDeployer | I split a ServiceDeployment into its component ServiceMetaData | | ServiceClassLoaderDeployer | I create classloaders from LoaderRepositoryConfig | | ServiceDeployer | I'm the real deployer of ServiceMetaData | | etc. This makes more sense. My only question is whether there are distinct outputs for the runtime metadata and management interface. Having to create management views from the raw deployer metadata is too cumbersome and does not lend itself to introduction of higher level notions like extracting server wide views like all network ports in use. So an explicit management view like the ManagedObject notion that existed previously is something that should show up in a Deployer contract. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3972652#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...