The new VDF MainDeployer and porting of the SARDeployer to the VDF will be the collision point. I'll try to merge these changes into my working copy of head today. Do we want to synch up with all the current head changes and make another javaee cts branch or do this mc/vdf/profilesevice work in a branch? In terms of "Should the ServiceController create the Kernel internally or should it be created by the ServerLoader and "injected" in the ServiceController?", can't this only be the latter? Currently the profileserivce version of the ServerLoader/ServerImpl (which is in head but not used by default: org.jboss.system.server.profileservice.ServerImpl) creates a single kernel for the entire server. Back to the discussion of allowing interaction between legacy mbeans and new kernel beans how can this be done unless they are in the same kernel? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3962947#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...