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

[Martin Kouba (JIRA)]

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

Martin Kouba commented on CDI-407:
----------------------------------

{code}
@Specializes @Alternative
public class SpecialCustomerANavigationController extends CustomerANavigationController 
{code}
I think this should work provided you don't mix kinds of beans (I mean managed vs session etc.). Indirect specialization - it's described here: [4.3.1. Direct and indirect specialization|http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#direct_and_indirect_specialization].

> 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
(v6.3.1#6329)