]
Jason Greene updated JBAS-8513:
-------------------------------
Fix Version/s: 7.0.0.Beta1
(was: 7.0.0.Alpha1)
Managed bean @Resource injection is premature
---------------------------------------------
Key: JBAS-8513
URL:
https://jira.jboss.org/browse/JBAS-8513
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Other
Reporter: Brian Stansberry
Assignee: John Bailey
Fix For: 7.0.0.Beta1
The way this works now, for a given managed bean type T, the ManagedBeanService<T>
would have an instance of each @Resource bean injected as part of start(). Thereafter
whenever ManagedBeanContainer.createInstance() is invoked, the same bean instance would be
injected into the newly created bean. AIUI what should happen is createInstance() should
result in a new naming lookup for each @Resource bean, which in turn would trigger
creation of a new instance of that bean.
This also causes classloading problems, since doing the injection during the MSC
StartTask results in the ManagedBeanObjectFactory not being visible. See forum thread for
effect of this.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: