[ https://issues.jboss.org/browse/CDI-427?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand commented on CDI-427: ------------------------------------------ To be consistent with the decision that's been chosen in CDI-408, I think we should stick to what was decided in CDI-377, CDI-404 and 406 (Normal Scope type, Interceptor, Decorator and Stereotype). Anyway, here's my POV on class level annotation not in Bean defining annotation set. * Qualifiers (built-in or user defined). As @Qualifier are defined in JSR 330, we shouldn't take them to avoid the same issue than in CDI-377 * @Alternative : could bring a lot of issue regarding if the bean this alternative replace has been detected as a bean. And since activating an alternative requiers using beans.xml, it's not very far to switch the bean-discovery-mode to all * @Specialize : same remark about the specialized bean being considered as a bean * @Typed : the only class level annotation that would be easily added to the set. But is it necessary ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira