I think the best way to fix this is to provide some generic class scanning from the classloading module. Only it has all the information about what is really in the classloader e.g. it isn't necessarily everything reachable from the vfs roots, especially when there is "subdeployment" within one of those roots. Also there should be a way for other annotation parsers to plugin to the process such that it is only done once rather repeating the task of parsing annotations multiple times. e.g. ejb3, servlet, webservices, aop, pojo, (jmx in future?), etc. and creating the metadata such that some other deployer can potentially override it Ales already has an open issue to create a generic annotation parsing deployer http://jira.jboss.com/jira/browse/JBDEPLOY-13 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138801#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...