"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 :) | But implicit dependencies with xml processing are also one issue i want to discuss here. | Well that's only half of the story - just to describe the problem a bit.. The main issue is basically the xml format with implicit dependencies and how you reference a profile - so that profiles are started and stopped the correct order, or shutdown when a dependency is not satisfied anymore. Which means you are right saying that something like mode="manual" would make sense. As at the moment if you would define a clustering profile, like i did in the unit test case it is completely wrong (sorry for that). In this case if you stop your clustering-hotdeployment directory it would shutdown also the "default" profile, as it is a dependency of that. Even worse in the case i have now - where you basically shutdown all profiles which are defined after the clustering profile :) We might want to add something to ignore this dependencies, but i still need to do some more work on that. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4204463#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...