Deactivate is good. :) "emuckenhuber" wrote : Basically all Profiles are getting registered as ON_DEMAND - so unless you don't have a dependency on it, it will not get activated unless you explicitly activate it :) Ah, OK, ProfileServiceBootstrap registers all profiles but only activates the one whose name matches the -c value. I'll have to walk through SubProfile again stuff again to see how this is all tying together. Seemed like with the StaticProfileFactory "all" depends on BOOTSTRAP and DEPLOYERS but w/ XmlProfileFactory (true dependency), "all" depends on logical subelements, which would mean inactivating just one subelement in the hierarchy would cause the whole ball of wax to ... something. Ignore the above comment; let me look again. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4204464#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...