I updated http://wiki.jboss.org/wiki/JBossMCProfileServiceBootstrap and the first issue is that we are bootstrapping a large number of core services and jars in the org.jboss.bootstrap.microcontainer.ServerImpl by loading the bootstrap.xml and its referenced classloader.xml, aop.xml, jmx.xml, deployers.xml, bindings.xml, profile.xml. Originally the profile service was closer to the bootstrap and the bootstrap deployments came from the profile. I guess we split this up to have more control over the order services are created. At a minimum we would need a new vfs url for the classpaths to allow the jars to come from the profile repository. If the deployments and their order are also to be part of the profile definition, we would need to get the BootstrapMetaData from the Bootstraps, but those don't exist without loading the profile.xml. Its not a big deal for these to be manageable initially, but what is the long term plan? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177276#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...