[cdi-dev] [JBoss JIRA] (CDI-201) Reflect BeanAttributes within validation rules

Reflect BeanAttributes within validation rules ---------------------------------------------- Key: CDI-201 URL: https://issues.jboss.org/browse/CDI-201 Project: CDI Specification Issues Issue Type: Clarification Components: Portable Extensions Affects Versions: 1.1.EDR1 Reporter: Jozef Hartinger Fix For: 1.1 (Proposed) For example: 1) The spec says: {quote}Each child <class> element must specify the name of an alternative bean class. If there is no class with the specified name, or *if the class with the specified name is not an alternative bean class, the container automatically detects the problem and treats it as a deployment problem*. {quote} Since that "alternative" attribute of a bean can be altered by a portable extension in the ProcessBeanAttributes phase, the specification should instead require for each class listed in the <class> element, each bean that defines the class as its bean class is an alternative. 2) {quote}If Y has a name and X declares a name explicitly, using @Named, the container automatically detects the problem and treats it as a definition error.{quote} The specification should abstract from @Named, since the ProcessBeanAttributes enables an extension to set a bean name without using @Named Likely, there are other similar issues. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira