Martin Kouba commented on

WELD-930

Producer is made an alternative if the declaring bean class is an alternative

I think this shouldn't have been fixed. The part of the spec Alexey is quotes is outdated (Proposed Final Draft probably).

Compare Alexey's quotation:

...to resolve the ambiguity. If any of the beans are alternatives, the container eliminates all beans that are not alternatives, except for producer methods and fields of beans that are alternatives.
...

and the current wording from 1.0 Final Release:

...to resolve the ambiguity. The container eliminates all beans that are not alternatives, except for producer methods and fields of beans that are alternatives.
...

In the example above we have two beans for bean type List<User> (suppose alternative EJBUserManager is enabled). We should try to resolve the ambiguity - eliminate producer method declared on ManagedBeanUserManager as it is not an enabled alternative. But we should not eliminate producer method on EJBUserManager - it is a producer method of a bean that is an alternative.

Maybe I just don't fully understand the wording of the spec...

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira