"scott.stark(a)jboss.org" wrote : Currently all deployments are added to a list in breadth first order. Previously I had a plugin that would return a directed graph of the contexts in a given top level deployment which allowed this to be configurable. This or some other metadata to control this for backward compatibility seems needed. | This ordering needs to be nailed down. Why? Please take a look at the server/ module under org.jboss.deployment.JaccInitializationDeployer and JaccCommitDeployer. Unless I am misunderstanding JACC, the parent PC cannot commit until all child PCs are linked. So, the implementation of these deployers is dependent on the ordering of deployment units. My implementation depends on Bredth-first, as initialisation creates and links the PC while commit just commits. I'll have to switch where the link happens based on whether it is depth/bredth. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3977374#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...