I've committed simple - ScanningDeploymentUnitFilter - ScanningMetaDataRecurseFilter - ScanningMetaDataResourceFilter I also fixed a small glitch in my GenericAnnotationResourceVisitor, removing lookup for super and interfaces unless explicitly asked, otherwise this can go past scanning metadata filter. "adrian(a)jboss.org" wrote : | Also, the paths need to be able to handle "external jars", | e.g. those referenced from the manifest | I have a simple test where jar's manifest references ear's/lib jars. But this ear/lib jars are then scanned as part of top deployment (remember our urls issue in AnnEnvDeployer?). Can you think of any other test case that would check your 'external jars'? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4189635#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...