Mark Struberg commented on CDI-574:
But your quote is only true for an 'enabled' specialization. Means if they have
@alternative but are never activated then it is disabled.
Should a disabled @Specialized disable a second bean?
Project: CDI Specification Issues
Issue Type: Clarification
Components: Inheritance and Specialization
Affects Versions: 1.2.Final
Reporter: Emily Jiang
In CDI specification Section 4.3:
When an enabled bean, as defined in Section 5.1.2, “Enabled and disabled beans”,
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.
The spec says only an enabled bean can specialize a second bean. Can a disabled
specialized bean specialize a second bean?
Weld asserts a disabled specialized bean specializes a second bean while OWB asserts a
disabled specialized bean does not specialize a second bean.
This needs to be clarified.
In more details:
I have an application containing two wars.
@Inject CounterProducerConsumerModified2 bean;
containing one bean and an empty-ish beans.xml :
@Inject@CounterModifiedQualifier String modifiedProducer;
CounterModifiedQualifier (the interface)
CounterProducerModified (the bean implementing that interface)
AlternativeCounterProducerModified (an alternative specialized bean)
My application failed deployment with the error on Weld but worked on OpenWebBeans
[ERROR ] CWWKZ0004E: An exception occurred while starting the application testDiffBDA.
The exception message was: com.ibm.ws.container.service.state.StateChangeException:
org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for
type String with qualifiers @CounterModifiedQualifier
at injection point [BackedAnnotatedField] @Inject @CounterModifiedQualifier
After further investigation and talking to Martin from Weld, the error was caused due to
the fact of AlternativeCounterProducerModified disabling the CounterProducerModified bean
but itself is not enabled in the jar of beans-xml-modified2.jar. Therefore, no producer is
active to produce a bean with the qualifier CounterModifiedQualifier.
From Weld's perspective, any bean annotated with @Specialized disables a second bean
regardless whether itself is active or not.
My understanding is that the specialized should only take effect if itself is enabled.
Otherwise, we run into the situation of where the specialized bean is not enabled but it
disabled another bean. To me, it is wrong.