The tools integration layer is relying on the jboss.deployment:flavor=URL,type=DeploymentScanner MBean start / stop / addURL service methods. In JBossAS 5 this corresponds to the HDScanner bean start/stop methods, but it no longer is what controls what the hot deployment directories are. That is now part of the profile, and its not property exposed via a management api. The should be a ManagedObject view that supports this capability, and there could be a corresponding MBean facade that allow JMX based clients to not have to convert to the profile service api. Its clear we need testcases for the apis that JBIDE is relying on as well. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4197002#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...