"weston.price(a)jboss.com" wrote : | From a root deployment (initial deployment) the profile service has to know about what gets deployed and the metadata that gets generated as result, or at the very least, it's Management DD. It does this via the deployment chain as you talked about. The results of the initial deployment are persisted to the repository. Diffs can begin at this point, effectively the deployment is versioned. | | I think I was hung up more on the 'who starts the chain' more than I was what happens as a result. | | So, based on this design, there is no concept of a JBoss instance existing without a ProfileService, they are effectively one and the same in terms of the 'client view'. The ProfileService really takes over what the old JMX system used to provide but with a ton of more features (versioning, dynamic lifecycle including a STOP, etc). | | Let me know if I am on the right track. | The profile service plugs into the long standing ServerImpl bootstrap mechanism, so to some extent its replacable. With the update to all of the deployers, there is an extended contract on how deployments are brought into the server that obsoletes the old scanners, but they could be ported over in place of the profile service. Certainly all of the new features we are working on now are quality of service issues that can be disabled and you still have a functional server. We do want a full featured profile service as the default replacement for the old jmx deployment mechanism, so yes, there is no interesting jboss server without a profile service. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992380#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...