A jndi lookup is not a sufficient expression of dependency for the mc to detect this. In general we are not going to support lookup(x) implies a dependnecy on x because there is no guarantee x resolves to a component as know to the mc. We already have jndi dependency implementations, but you have to know what component provides the jndi binding to use it. If a component is doing a jndi lookup and it fails, this would have to roll back the current war deployment and add a dependency on the name. That is a big change to deployment processing. The real issue is that war components should be started after all other non-wars in the current deployment unit tree. Need to look into how that could be done. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125252#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...