Some issues remaining from the deployer changes affecting the profile service are: + testDataSourceDeploymentType is broken because the getDeploymentNamesForType cannot be implemented. This is probably useless functionality, as it relies on the DeploymentContext.getTypes(). What is really needed is the ability to view the jsr77 types in a deployment structure. + testJmsDestinationComponents is broken because the ManagedDeployment/ManagedComponent tree cannot be built from the DeploymentUnit or client Deployment view as there is no access to the service descriptor component mbeans. A destinations-service.xml corresponds to multiple mbeans of various component types. In general the component types are unknown. We need to move the ManagedDeployment construction out of the client view of the profile service into a ManagedDeploymentDeployer, and start adding annotations to the other deployers/deployments to identify the component/jsr77 types that are produced. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4065905#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...