[weld-issues] [JBoss JIRA] (WELD-1741) @Specialized bean does not disable second bean: observer method is called

[Martin Andersson (JIRA)]

Title: Message Title

Martin Andersson created an issue   Weld / WELD-1741 @Specialized bean does not disable second bean: observer method is called Issue Type: Bug Affects Versions: 2.2.0.Final Assignee: Unassigned Components: Class Beans (Managed and Session) Created: 12/Sep/14 9:00 AM Environment: Windows 8 x64, GlassFish 4.0.1-b08 and WildFly 8.1.0 Priority: Major Reporter: Martin Andersson The CDI 1.1 specification says about a @Specialized bean: "When an enabled bean, as defined in Section 5.1.2, specializes a second bean, we can be certain that the second bean is never instantiated or called by the container. Even if the second bean defines a producer or observer method, the method will never be called." JavaDoc of @Specializes even say that the specialized bean is "disabled". However, WELD do call observer methods of the superclass. I have a "Java EE concepts" project that execute a series of Java EE tests using Arquillian and the test that test the behavior of @Specializes and supposedly disabled observer methods fail. The project is Maven based and has two profiles for WildFly- and GlassFish remote servers. Feel free to clone and execute. Read more on this error in the JavaDoc of the test class: https://github.com/MartinanderssonDotcom/java-ee-concepts/blob/master/src/test/java/com/martinandersson/javaee/cdi/specializes/SpecializesTest.java Add Comment   This message was sent by Atlassian JIRA (v6.3.1#6329-sha1:7df76f1)

_______________________________________________
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-issues