Actually, it should not be a deployer as it would be a deployer with no known inputs/outputs on which to generate the managed object for. There just should be a ManagedObjectCreator implementation that has the ManagedObjectFactory injected, and this in turn is injected into the DeployerWrapper/DeployersImpl. Right now the DeployerWrapper initializes its the ManagedObjectCreator from the Deployer if it implements that. This logic could be kept so that deployers could provide an override, but typically they would customize behavior using an InstanceClassFactory registration. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185501#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...