anonymous wrote : | Design Question: This inclusion of service binding in the bootstrap isn't strictly necessary, just how I've approached it so far. I did it that way because a) the service does have to be loaded early, before stuff in conf/jboss-service.xml that needs binding configuration and b) the binding configuration file is pretty long and complex and IMHO should be in its own file. The bootstrap mechanism was a quick-and-dirty way to get that file parsed and loaded into the MC. | The issue here is that we have no conf/jboss-beans.xml equivalent other than the bootstrap files. In practice this bootstrap stage of the profile service should disappear once all the mbeans have been moved out of conf/jboss-service.xml The ServiceBindingManager would then live in deploy and automatically get deployed in order correctly based on MC dependencies. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169051#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...