[jbosstools-issues] [JBoss JIRA] Issue Comment Edited: (JBIDE-8017) No bean is eligible for @Inject BeanManager manager;
[
https://issues.jboss.org/browse/JBIDE-8017?page=com.atlassian.jira.plugin...
]
Alexey Kazakov edited comment on JBIDE-8017 at 12/29/10 5:19 PM:
-----------------------------------------------------------------
We do, but I guess BeanManager is a special bean. For example BeanManagerImpl (weld
implementation) doesn't have a default constructor, so we don't treat it as a
class bean. Looks like weld load it in a special way.
was (Author: akazakov):
We do, but I guess BeanManager is a special bean. For example BeanManagerImpl (weld
implementation) doesn't has a default constructor, so we don't treat it as a class
bean. Looks like weld load it in a special way.
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
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