[
https://jira.jboss.org/jira/browse/WELD-483?page=com.atlassian.jira.plugi...
]
David Allen commented on WELD-483:
----------------------------------
This is also now fixed in the new ContextBeanInstance class that will be checked in with
the new proxy class code.
The use of the ThreadLocal was not properly covered by a try/final block. Apparently some
test cases do cause exceptions to occur which were bypassing the final block to reset the
ThreadLocal.
Client proxies are using the wrong CreationalContexts sometimes
---------------------------------------------------------------
Key: WELD-483
URL:
https://jira.jboss.org/jira/browse/WELD-483
Project: Weld
Issue Type: Bug
Reporter: David Allen
Fix For: 1.0.2.CR1
There are cases where the ThreadLocal which keeps a WeldCreationalContext already has a
CC from some prior execution of the code. In other words, these appear to be leaking
somehow across bean creations. This can cause problems with test suites by reusing beans
from a different test.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira