[ https://issues.jboss.org/browse/CDI-231?page=com.atlassian.jira.plugin.sy... ] Gerhard Petracek edited comment on CDI-231 at 5/22/12 6:02 PM: --------------------------------------------------------------- the only behavior which makes sense imo is: simple constellation: if an alternative bean is activated, the type-information (/-meta-data) of the original bean should be changed. (-> beans without a type and name can be removed completely). shared-lib constellation: an alternative bean (for a bean in a shared lib) which isn't enabled for all applications leads to the same change of the type-meta-data. however, instead of changing the original meta-data which is still needed by other applications, the change should be done on a copy which is kept at the first lookup level. -> applications which should use the alternative bean will only see this one and >not< the original bean -> applications which should not use the alternative bean will only see the original bean (in the second lookup level) was (Author: gpetracek): simple constellation: if an alternative bean is activated, the type-information (/-meta-data) of the original bean should be changed. (-> beans without a type and name can be removed completely). shared-lib constellation: an alternative bean (for a bean in a shared lib) which isn't enabled for all applications leads to the same change of the type-meta-data. however, instead of changing the original meta-data which is still needed by other applications, the change should be done on a copy which is kept at the first lookup level. -> applications which should use the alternative bean will only see this one and >not< the original bean -> applications which should not use the alternative bean will only see the original bean (in the second lookup level) -- 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-231?page=com.atlassian.jira.plugin.sy... ] Mark Struberg reassigned CDI-231: --------------------------------- Assignee: Pete Muir (was: Mark Struberg) please apply. -- 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-231?page=com.atlassian.jira.plugin.sy... ] Mark Struberg commented on CDI-231: ----------------------------------- It's only clear if you omit the most important part ;) Please add the following to your quote above: {quote} ...according to the rules of typesafe resolution defined in Section 5.2, “Typesafe resolution”. {quote} But according to the rules of scientific citing, referencing 5.2 includes all its sub bullets, thus also 5.2.1 (resolving Alternatives). If that would not include 5.2.1 then also oher important sub-bullets would be missing e.g. it would also leave out the reference to 'primitives and nullable types' -- 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-231?page=com.atlassian.jira.plugin.sy... ] Pete Muir resolved CDI-231. --------------------------- Fix Version/s: 1.1.EDR2 (was: 1.1 (Proposed)) Resolution: Done Merged -- 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