12:47 p.m.
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
12:55 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8017) No bean is eligible for @Inject BeanManager manager;
[
https://issues.jboss.org/browse/JBIDE-8017?page=com.atlassian.jira.plugin...
]
Alexey Kazakov commented on JBIDE-8017:
---------------------------------------
There is BeanManagerImpl class In Weld which should be eligible for @Inject BeanManager
manager;
I guess we should find the first non-abstract implementation of BeanManager interface and
treat it as built-in Bean Manager bean.
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
4:11 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8017) No bean is eligible for @Inject BeanManager manager;
[
https://issues.jboss.org/browse/JBIDE-8017?page=com.atlassian.jira.plugin...
]
Max Andersen commented on JBIDE-8017:
-------------------------------------
Alexey, dont you scan the classpath for beans like we did for seam components ?
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
4:19 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8017) No bean is eligible for @Inject BeanManager manager;
[
https://issues.jboss.org/browse/JBIDE-8017?page=com.atlassian.jira.plugin...
]
Alexey Kazakov commented on JBIDE-8017:
---------------------------------------
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
4:21 p.m.
New subject: [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:20 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 loads 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 have 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
4:21 p.m.
New subject: [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
5:33 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8017) No bean is eligible for @Inject BeanManager manager;
[
https://issues.jboss.org/browse/JBIDE-8017?page=com.atlassian.jira.plugin...
]
Viacheslav Kabanovich commented on JBIDE-8017:
----------------------------------------------
Also, jar files of weld do not include file entry META-INF/beans.xml, so our model ignores
them (same problem with JBIDE-8019).
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
9:58 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8017) No bean is eligible for @Inject BeanManager manager;
[
https://issues.jboss.org/browse/JBIDE-8017?page=com.atlassian.jira.plugin...
]
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
9:58 a.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-8017) No bean is eligible for @Inject BeanManager manager;
[
https://issues.jboss.org/browse/JBIDE-8017?page=com.atlassian.jira.plugin...
]
Viacheslav Kabanovich resolved JBIDE-8017.
------------------------------------------
Resolution: Partially Completed
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
9:58 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8017) No bean is eligible for @Inject BeanManager manager;
[
https://issues.jboss.org/browse/JBIDE-8017?page=com.atlassian.jira.plugin...
]
Viacheslav Kabanovich commented on JBIDE-8017:
----------------------------------------------
At present only implementation of BeanManager exists -
org.jboss.weld.manager.BeanManagerImpl. Let's in this version just add to CDI beans
that type and avoid performance problems related with building hierarchy.
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
10 a.m.
New subject: [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...
]
Viacheslav Kabanovich edited comment on JBIDE-8017 at 12/30/10 10:59 AM:
-------------------------------------------------------------------------
At present only one implementation of BeanManager exists -
org.jboss.weld.manager.BeanManagerImpl. Let's in this version just add to CDI beans
that type and avoid performance problems related with building hierarchy.
was (Author: scabanovich):
At present only implementation of BeanManager exists -
org.jboss.weld.manager.BeanManagerImpl. Let's in this version just add to CDI beans
that type and avoid performance problems related with building hierarchy.
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, 3.3.x
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
10 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8017) No bean is eligible for @Inject BeanManager manager;
[
https://issues.jboss.org/browse/JBIDE-8017?page=com.atlassian.jira.plugin...
]
Viacheslav Kabanovich updated JBIDE-8017:
-----------------------------------------
Fix Version/s: 3.3.x
Affects Version/s: (was: 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
Reporter: Alexey Kazakov
Assignee: Viacheslav Kabanovich
Fix For: 3.2.0.CR1, 3.3.x
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
12:57 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8017) No bean is eligible for @Inject BeanManager manager;
[
https://issues.jboss.org/browse/JBIDE-8017?page=com.atlassian.jira.plugin...
]
Alexey Kazakov updated JBIDE-8017:
----------------------------------
Fix Version/s: (was: 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
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
5:05 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8017) No bean is eligible for @Inject BeanManager manager;
[
https://issues.jboss.org/browse/JBIDE-8017?page=com.atlassian.jira.plugin...
]
Alexey Kazakov commented on JBIDE-8017:
---------------------------------------
We hardcoded BeanManagerImpl class and now we treat it as a special bean. So "@Inject
BeanManager manager;" works if BeanManagerImpl in the project class path. Is it
enough for CR1?
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
5:13 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8017) No bean is eligible for @Inject BeanManager manager;
[
https://issues.jboss.org/browse/JBIDE-8017?page=com.atlassian.jira.plugin...
]
Max Andersen commented on JBIDE-8017:
-------------------------------------
Alexey, the CDI spec says some classes *must* be provided, BeanManager being one of them -
can we implement that instead ? i.e. does not depend on class being on classpath.
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
11:49 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8017) No bean is eligible for @Inject BeanManager manager;
[
https://issues.jboss.org/browse/JBIDE-8017?page=com.atlassian.jira.plugin...
]
Alexey Kazakov updated JBIDE-8017:
----------------------------------
Fix Version/s: 3.3.x
(was: 3.2.0.CR1)
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.3.x
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
12:34 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8017) No bean is eligible for @Inject BeanManager manager;
[
https://issues.jboss.org/browse/JBIDE-8017?page=com.atlassian.jira.plugin...
]
Alexey Kazakov updated JBIDE-8017:
----------------------------------
Fix Version/s: 3.3.0.M2
(was: 3.3.x)
Slava, can we resolve @Inject BeanManager beanManager; to some special bean (exists only
in JBT CDI model) but OpenOn should point to BeanManager interface? The same approach that
we use for other built-in beans which we can't load as a usual CDI beans.
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.3.0.M2
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
2:35 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8017) No bean is eligible for @Inject BeanManager manager;
[
https://issues.jboss.org/browse/JBIDE-8017?page=com.atlassian.jira.plugin...
]
Viacheslav Kabanovich updated JBIDE-8017:
-----------------------------------------
Fix Version/s: 3.3.0.M1
(was: 3.3.0.M2)
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.3.0.M1
Attachments: JBIDE-8017.patch
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
2:35 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8017) No bean is eligible for @Inject BeanManager manager;
[
https://issues.jboss.org/browse/JBIDE-8017?page=com.atlassian.jira.plugin...
]
Viacheslav Kabanovich updated JBIDE-8017:
-----------------------------------------
Attachment: JBIDE-8017.patch
That is easy - just to follow the framework that is already merged to jbosstools-3.2.x.
So, I also suggest this patch for the branch.
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.3.0.M1
Attachments: JBIDE-8017.patch
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
2:37 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8017) No bean is eligible for @Inject BeanManager manager;
[
https://issues.jboss.org/browse/JBIDE-8017?page=com.atlassian.jira.plugin...
]
Alexey Kazakov updated JBIDE-8017:
----------------------------------
Fix Version/s: 3.2.1.M1
Yes, then please fix it for 3.2.1 too.
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.1.M1, 3.3.0.M1
Attachments: JBIDE-8017.patch
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
2:41 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8017) No bean is eligible for @Inject BeanManager manager;
[
https://issues.jboss.org/browse/JBIDE-8017?page=com.atlassian.jira.plugin...
]
Viacheslav Kabanovich commented on JBIDE-8017:
----------------------------------------------
Fixed in trunk. Alexey, should I merge it to jbosstools-3.2.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
Reporter: Alexey Kazakov
Assignee: Viacheslav Kabanovich
Fix For: 3.2.1.M1, 3.3.0.M1
Attachments: JBIDE-8017.patch
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
3:16 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8017) No bean is eligible for @Inject BeanManager manager;
[
https://issues.jboss.org/browse/JBIDE-8017?page=com.atlassian.jira.plugin...
]
Alexey Kazakov commented on JBIDE-8017:
---------------------------------------
Yes, please.
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.1.M1, 3.3.0.M1
Attachments: JBIDE-8017.patch
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
5:02 p.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-8017) No bean is eligible for @Inject BeanManager manager;
[
https://issues.jboss.org/browse/JBIDE-8017?page=com.atlassian.jira.plugin...
]
Viacheslav Kabanovich resolved JBIDE-8017.
------------------------------------------
Resolution: Done
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.1.M1, 3.3.0.M1
Attachments: JBIDE-8017.patch
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
12:27 p.m.
New subject: [JBoss JIRA] Closed: (JBIDE-8017) No bean is eligible for @Inject BeanManager manager;
[
https://issues.jboss.org/browse/JBIDE-8017?page=com.atlassian.jira.plugin...
]
Lukas Jungmann closed JBIDE-8017.
---------------------------------
v. in jbdevstudio-product-eap-linux-gtk-4.1.0.v201104171649R-H346-M1.jar
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.1.M1, 3.3.0.M1
Attachments: JBIDE-8017.patch
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
5464
days inactive
5583
days old
jbosstools-issues@lists.jboss.org
23 comments
4 participants
participants (4)
-
Alexey Kazakov (JIRA) -
Lukas Jungmann (JIRA)
-
Max Andersen (JIRA)
-
Viacheslav Kabanovich (JIRA)