[cdi-dev] [JBoss JIRA] (CDI-109) Invalid beans should not be injectable into extensions
Jozef Hartinger (Updated) (JIRA)
jira-events at lists.jboss.org
Fri Nov 18 12:33:41 EST 2011
[ https://issues.jboss.org/browse/CDI-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jozef Hartinger updated CDI-109:
--------------------------------
Fix Version/s: 1.1 (Proposed)
(was: 1.1.EDR1)
Git Pull Request: https://github.com/jboss/cdi/pull/32 (was: https://github.com/jboss/cdi/pull/32)
Affects Version/s: 1.1.EDR1
> Invalid beans should not be injectable into extensions
> ------------------------------------------------------
>
> Key: CDI-109
> URL: https://issues.jboss.org/browse/CDI-109
> Project: CDI Specification Issues
> Issue Type: Feature Request
> Components: Portable Extensions
> Affects Versions: 1.0, 1.1.EDR1
> Reporter: John Ament
> Assignee: Pete Muir
> Priority: Minor
> Fix For: 1.1 (Proposed)
>
>
> Currently, you can inject beans that may not be ready yet into the extension's call back methods. As an example, I can inject something application scoped like this in to an extension, but it should really be throwing a definition exception (or similar):
> public void handleABD(@Observes AfterBeanDiscovery abd, MyApplicationScopedBean masb) {
> }
> Pete had noted that really the only safe thing to inject, other than the observed call back, is the bean manager.
--
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
More information about the cdi-dev
mailing list