[cdi-dev] [JBoss JIRA] Closed: (CDI-112) Clarify how alternatives are enabled

Pete Muir (JIRA) jira-events at lists.jboss.org
Tue Sep 6 09:31:27 EDT 2011

     [ https://issues.jboss.org/browse/CDI-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pete Muir closed CDI-112.

    Resolution: Partially Completed

Merged into CDI-18

> Clarify how alternatives are enabled
> ------------------------------------
>                 Key: CDI-112
>                 URL: https://issues.jboss.org/browse/CDI-112
>             Project: CDI Specification Issues
>          Issue Type: Clarification
>          Components: Beans
>    Affects Versions: 1.0
>            Reporter: Shane Bryzak
>             Fix For: 1.1 (Proposed)
> The spec is open to interpretation about how alternatives are enabled.  One popular interpretation is that alternatives must be enabled within the same bean archive that contains the alternative bean.  However, it might be worth considering the merit of enabling an alternative from a deployment archive that contains the bean archive.  
> For example, suppose we have the following deployment archive:
> foo.war
>   /WEB-INF
>     beans.xml
>   /lib
>     bar.jar
>       /META-INF
>         beans.xml
>       /com
>         /acme
>           AlternativeBean.class
> It may be worth allowing AlternativeBean.class (a class annotated with @Alternative) to be enabled by listing it in the <alternatives> section of foo.war/WEB-INF/beans.xml.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the cdi-dev mailing list