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

Richard Hightower (JIRA) jira-events at lists.jboss.org
Sat Apr 30 14:22:18 EDT 2011

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

Richard Hightower commented on CDI-112:

Also this is a similar problem domain to web-fragments.xml versus web.xml in the Servlet 3.0 specification. I think we should apply the same rules and techniques. <order><first><others/><first></order>. Or at least see if what Servlet's does with web-fragments makes sense for beans.xml files in other jars veruss the beans.xml file in the WAR, EAR, etc.

> 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