The current problem with using the ejb3 client deployer as a general client deployer is that its container bean is looking for suppliers of things like a jndi name binding. The problem is that supply/demand is a kernel bean specific notion. It does not show up in the Controller api. It shows up in the KernelController. The problem with this is that the jmx mbean service controller cannot express that its context supply the demans of an mc bean context. So when you have a legacy client application deployment that does not involve ejb3 components, there ends up being nothing to supply the demands of the client container bean. Either supply/demand should just be a type of dependency where a demand maps onto a DependencyItem and supply maps to an alias, or we need the supply/demand notion to show up at the more general ControllerContext/Controller level to allow supply/demand to span different context implementations. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4100061#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...