"david.lloyd(a)jboss.com" wrote : you just need a map of class to a list of active deployments which is updated every time something is deployed/undeployed. This is what we're already doing. But that's not what I wanted to highlight. The real issue is should we sacrifice dependency API simplicity in order to be able to handle (= gather dependency info for) each custom case. Meaning it will become a lot more complex to define a dependency, if you then have hard time providing "gathering" info. And I don't think we would gain that much, as we only check our new deployment against not yet fully installed components. 11:51:53,375 INFO [AllGraphCreator] Vertices: 834, Edges: 1561 This is the info of how many component we currently have in AS default. Each component has in average less than 2 dependencies. And most of then are quickly moved to Installed state, hence checking against the rest should be pretty fast. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244710#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...