Ok, so you should not have to set the class loader on the deployment because this will have one that has access to the server classes, but the problem here is that the custom schema for the wildcard bindng of the policyConfig property value is essentially annotation processing, not simple xml parsing or binding to classes that are part of the deployers known types. In general these classes can be part of the deployment which requires establishment of the deployment class loader. This problem is covered by this issue: http://jira.jboss.com/jira/browse/JBDEPLOY-32 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142337#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...