[weld-issues] [JBoss JIRA] (CDITCK-467) SpecializationTest wrongly assumes that ProcessBeanAttribute does not get called for specialized beans
Title: Message Title Mark Struberg commented on CDITCK-467 Re: SpecializationTest wrongly assumes that ProcessBeanAttribute does not get called for specialized beans VerifyValuesTest#testManagedBeanAttributes doe the same for not enabled @Alternatives. Despite the spec even explicitly says that not-enabled alternatives are 'disabled beans' (and thus ARE Beans). Add Comment This message was sent by Atlassian JIRA (v6.3.11#6341-sha1:83c4d29) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-467) SpecializationTest wrongly assumes that ProcessBeanAttribute does not get called for specialized beans
Title: Message Title Mark Struberg created an issue CDI TCK / CDITCK-467 SpecializationTest wrongly assumes that ProcessBeanAttribute does not get called for specialized beans Issue Type: Feature Request Affects Versions: 1.2.4.Final Assignee: Tomas Remes Created: 07/Mar/15 11:07 AM Priority: Major Reporter: Mark Struberg SpecializationTest wrongly assumes that ProcessBeanAttribute does not get called for specialized beans. The spec says nothing about when the 'disabling' of specialized away beans is to be performed or how this is done. Thus it also doesn't define whether ProcessBeanAttributes gets called for those beans. Pretty much the only thing the spec defines is that those beans shall not get found by BeanManager#getBeans(). Add Comment
