[cdi-dev] [JBoss JIRA] (CDI-407) Specifiy @Named @Alternatives

Martin Kouba (JIRA) issues at jboss.org
Mon Oct 20 10:55:36 EDT 2014

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

Martin Kouba commented on CDI-407:

In this case, is there any reason to still install/configure A as active bean?
I'm not sure. Probably not in this very special scenario. But this is how it is defined right now and changing the behaviour wouldn't be backwards compatible.
@Named("a") is a workaround but feels "ugly" and you always have to synchronize the names.
You can still use String constants to avoid error-prone sync :-)

> Specifiy @Named @Alternatives
> -----------------------------
>                 Key: CDI-407
>                 URL: https://issues.jboss.org/browse/CDI-407
>             Project: CDI Specification Issues
>          Issue Type: Clarification
>          Components: Beans, Inheritance and Specialization
>            Reporter: Thomas Andraschko
> It's actually a must-have for product development and a common case.
> We would like to have multiple implementations in our core and just activate them via alternative.
> I talked with struberg and its currently not defined in the specs.
> e.g.
> @Named public class A
> @Named @Alternative public class B extends A
> What should acutally happen if B is activated via beans.xml?
> IMO B should be available in EL via "a" and "b".

This message was sent by Atlassian JIRA

More information about the cdi-dev mailing list