Order is definitely there for a purpose. ;-) Adrian could comment on it more. I guess internally you can implement it how ever you feel like, and this is exactly the goal of this task, to try out different approaches; e.g. unordered impl detail could out-perform ordered impl This is motly used with MDR, and it's "connectors": * ControllerContext/ScopeInfo * DeploymentUnit/Context You can check for the "ordered" explanation there, but I think it's pretty natural in the way of hierarchy you mentioned. (from CommonLevels? { domain, cluster, machine, node, jvm, server, subsystem, application, ... } ) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247304#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...