OK, I think I have a better grasp on this now.
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.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992370#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...