[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-8017) No bean is eligible for @Inject BeanManager manager;

[Viacheslav Kabanovich (JIRA)]

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

Viacheslav Kabanovich updated JBIDE-8017:
-----------------------------------------

    Affects Version/s: 3.3.x


> No bean is eligible for @Inject BeanManager manager;
> ----------------------------------------------------
>
>                 Key: JBIDE-8017
>                 URL: https://issues.jboss.org/browse/JBIDE-8017
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: cdi (jsr-299)
>    Affects Versions: 3.2.0.CR1, 3.3.x
>            Reporter: Alexey Kazakov
>            Assignee: Viacheslav Kabanovich
>             Fix For: 3.2.0.CR1
>
>
> See the spec.:
> 11.3. The BeanManager object
> Portable extensions sometimes interact directly with the container via programmatic API call. The interface javax.enterprise.inject.spi.BeanManager provides operations for obtaining contextual references for beans, along with many other operations of use to portable extensions. The container provides a built-in bean with bean type BeanManager, scope @Dependent and qualifier @Default.
> The builtin implementation must be a passivation capable dependency, as defined in Section 6.6.2, "Passivation capable dependencies". Thus, any bean may obtain an instance of BeanManager by injecting it:
> @Inject BeanManager manager;

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira