I think I have this fixed, or at least it's doing something meaningful. The problem was a missing List.add() call in AbstractWarDeployer.deployWebModule(). With that fixed if you deploy a war with a bogus depends element, you'll get the CONTEXTS MISSING DEPENDENCIES logging from HDScanner. But you also get a logging saying it "deployed xyz.war". The WebModule from the war will still appear in the jmx-console, and there's no attribute or anything to show that it's not running. And if you invoke the create or start operation on the console mbean, you get no complaint. I have a suspicion that what really should happen and isn't is that any dependencies from the JBossWebMetaData need to get pushed into the DeploymentUnit. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4123701#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...