[ https://issues.jboss.org/browse/CDI-177?page=com.atlassian.jira.plugin.sy... ] Martin Kouba commented on CDI-177: ---------------------------------- To sum it up: # A bean may have an EL name (2.5. Bean EL names) # EL name is declared with the @Named qualifier (2.5. Bean EL names) # If the @Named annotation does not specify the value member, the EL name is defaulted (2.5. Bean EL names) # The defaulted name is used in typesafe resolution: "If an injected field declares a @Named annotation that does not specify the value member, the name of the field is assumed." and the qualifier is changed to @Named(DEFAULT_NAME)(3.13. The qualifier @Named at injection points) # However in case of @Named is used on stereotype only EL name is defaulted So if I understand it correctly the only clarification required for "2.5. Bean EL names" is: "If a bean declares @Named qualifier and no EL name is explicitly specified, the default EL name is assigned, and the qualifier is @Named(value=DEFAULT_NAME).". Otherwise a bean with the @Named annotation that does not specify the value member could not be resolved - see example below. {code} @Named public class Ant {} public class AntHill { @Inject @Named // -> @Named("ant") --> UnsatisfiedResolutionException private Ant ant; } {code} -- 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

[ https://issues.jboss.org/browse/CDI-177?page=com.atlassian.jira.plugin.sy... ] Pete Muir commented on CDI-177: ------------------------------- Would it not be cleaner to generally discuss how @Named qualifiers are defaulted, and then make the EL Name use that? -- 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

[ https://issues.jboss.org/browse/CDI-177?page=com.atlassian.jira.plugin.sy... ] Pete Muir commented on CDI-177: ------------------------------- Please review https://github.com/jboss/cdi/pull/77 -- 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

[ https://issues.jboss.org/browse/CDI-177?page=com.atlassian.jira.plugin.sy... ] Pete Muir updated CDI-177: -------------------------- Fix Version/s: 1.1.EDR2 (was: 1.1 (Proposed)) -- 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

[ https://issues.jboss.org/browse/CDI-177?page=com.atlassian.jira.plugin.sy... ] Pete Muir commented on CDI-177: ------------------------------- The pull is updated with a much simpler approach, please review. -- 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

[ https://issues.jboss.org/browse/CDI-177?page=com.atlassian.jira.plugin.sy... ] Pete Muir resolved CDI-177. --------------------------- Resolution: Done -- 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