[
https://issues.jboss.org/browse/CDI-334?page=com.atlassian.jira.plugin.sy...
]
Jozef Hartinger commented on CDI-334:
-------------------------------------
{quote}An alternative may be given a priority for the application by placing the @Priority
annotation on the bean class of a managed bean, session bean, producer method or producer
field annotated with the @Alternative annotation.{quote}
As @Priority can only be applied to types it is unclear how an @Alternative producer may
be given a priority. Is a priority of the bean class used in that case? This section needs
to be expanded to specify producers explicitly.
Issues with global enablement of alternatives
---------------------------------------------
Key: CDI-334
URL:
https://issues.jboss.org/browse/CDI-334
Project: CDI Specification Issues
Issue Type: Bug
Components: Beans, Resolution
Affects Versions: 1.1.PFD
Reporter: Jozef Hartinger
Assignee: Pete Muir
Fix For: 1.1.FD
* Section 5.1 last paragraph does not reflect global enablement of alternatives.
* Section 5.1.1 fails to define how @Priority relates to:
** alternative stereotypes
** producers
* Section 5.1.6 does not reflect global enablement of alternatives
Section 5.2.2:
** generally the section needs to take global enablement of alternatives into account
** "If all the beans left are alternatives with a priority, then the container will
select the alternative with the highest priority, and the
ambiguous dependency is called resolvable."
*** there is no guarantee that there is a single alternative with the highest priority.
The spec should define what happens in that case.
*** also, the statement should not only consider "alternatives" but also
producers defined on alternatives
* Section 5.3.1 - same as 5.2.2
* Recommended priority ranges for alternatives should be defined somewhere
--
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