One thing I'm hung up on in terms of the SARDeployer migration is getting the ServerImpl bean into the kernel for use by the JMXKernel so that a ServerImplMBean can be exposed. What I have tried to do is just put the server instance into the kernel registry with a ControllerState.CONFIGURED requiredState and state value: | // Register the Server instance in the kernel | KernelRegistry registry = getKernel().getRegistry(); | AbstractKernelRegistryEntry serverEntry = new AbstractKernelRegistryEntry(server) | { | @Override | public ControllerState getRequiredState() | { | return ControllerState.CONFIGURED; | } | | @Override | public ControllerState getState() | { | return ControllerState.CONFIGURED; | } | }; | registry.registerEntry("org.jboss.system.server.Server", serverEntry); | | // Validate that everything is ok | kernelDeployer.validate(); | however the validation of the deployer-beans.xml initialization is failing with this error: | *** DEPLOYMENTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State} | JMXKernel -> org.jboss.system.server.Server{Configured:Configured}, JMXClassLoader{Described:Installed} | SARDeployer -> JMXClassLoader{Described:Installed}, JMXKernel{Configured:Instantiated}, JMXKernel{Configured:Instantiated} | It looks like everything is to the required state so I'm not sure why this error is occuring. What is it telling me? The bigger question is what is the correct way to push a fully Instantiated bean into the kernel for use in dependency relationships? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3963925#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...