An issue Emanuel is running into is that a DeploymentStages.REAL deployer does not have a deployment class loader capbable of loading classes referenced by deployment metadata. This is apparently due to the deployment class loader being injected: | <deployment xmlns="urn:jboss:bean-deployer:2.0"> | | <classloader><inject bean="bindings-classloader:0.0.0"/></classloader> | | <classloader name="bindings-classloader" xmlns="urn:jboss:classloader:1.0" export-all="NON_EMPTY" import-all="true"> | <root>${jboss.common.lib.url}jboss-bindingservice.jar</root> | </classloader> | ... | Its one thing for this to be an arbitrary bean, but in this case it seems that we should be able to create the class loader in prior to the POST_CLASSLOADER. In general, what is the point of having a class loader not be usable until the REAL phase? Every POST_CLASSLOADER and later deployer that needs to load classes via the deployment class loader will fail. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4231372#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...