[weld-issues] [JBoss JIRA] (WELD-998) Alternative custom bean not available for injection in other custom bean

Thu May 17 10:22:17 EDT 2012

    [ https://issues.jboss.org/browse/WELD-998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12693687#comment-12693687 ] 

Jozef Hartinger commented on WELD-998:
--------------------------------------

This is a problem with the test. The AlternativeStereotype is enabled in the web app bean archive but is not enabled in the library archive that contains (Foo.class, FooBean.class and IntegerBean.class). Moving the classes to WEB-INF/classes solves the problem. So does adding a beans.xml file with enabled AlternativeStereotype to the library archive.

> Alternative custom bean not available for injection in other custom bean
> ------------------------------------------------------------------------
>
>                 Key: WELD-998
>                 URL: https://issues.jboss.org/browse/WELD-998
>             Project: Weld
>          Issue Type: Bug
>    Affects Versions: 1.1.2.Final
>            Reporter: Martin Kouba
>             Fix For: 2.0.0.Alpha3
>
>
> Suppose we have extension that registers two custom beans (while observing AfterBeanDiscovery event). Custom bean A is alternative. Custom bean B is not alternative and has injection point with type A. This scenario causes deployment error: "WELD-001408 Unsatisfied dependencies...". 
> It seems that *ProcessBean* event is not fired after calling *javax.enterprise.inject.spi.AfterBeanDiscovery.addBean(Bean<?>)* because *org.jboss.weld.manager.BeanManagerImpl.isBeanEnabled(Bean<?>)* resolves to false at the given moment.
> Nevertheless it is available for injection in "regular" beans after deployment validation (suppose custom bean B is not included).
> Note that if custom bean A#isAlternative() returns false, test passes.
> See TCK test:
> https://github.com/jboss/cdi-tck/tree/master/impl/src/main/java/org/jboss/cdi/tck/tests/definition/bean/custom

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira