Too aggressive annotation scanning of classes by WarAnnotationMetaDataDeployer leads to incorrect metadata being created

The WarAnnotationMetaDataDeployer scans all the classes for Java EE resource injection annotations. The spec specifies only a certain "type" of classes in a web-app which are eligible for resource injection. Annotation scanning of unwanted classes in the web-app leads to an incorrect Environment metadata being created for JBossWebMetaData.

(More details to follow in subsequent replies and forum posts, after the holidays )