[cdi-dev] [JBoss JIRA] Updated: (CDI-109) Invalid beans should not be injectable into extensions

[Pete Muir (JIRA)]

     [ https://issues.jboss.org/browse/CDI-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pete Muir updated CDI-109:
--------------------------

           Status: Closed  (was: Pull Request Sent)
         Assignee: Pete Muir
    Fix Version/s: 1.1 (Confirmed)
                       (was: 1.1 (Proposed))
       Resolution: Done


Noted that injecting other beans can lead to non-portable behavior, this effectively just clarifies the spec, and highlights that an impl may choose to error at this point.

> 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
>            Reporter: John Ament
>            Assignee: Pete Muir
>            Priority: Minor
>             Fix For: 1.1 (Confirmed)
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira