CreationalContext not passed through all phases of bean creation
----------------------------------------------------------------
Key: WELD-482
URL: https://jira.jboss.org/jira/browse/WELD-482
Project: Weld
Issue Type: Bug
Components: Scopes & Contexts
Reporter: David Allen
Assignee: David Allen
Fix For: 1.0.2.CR1
The CreationalContext is not passed through to the creation of nested bean instances in all circumstances. This is causing incomplete bean instances to be re-created many times when there is a circular reference chain from an injected bean instance back to one of the beans already being created.
--
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
Private container-invoked methods not working on proxies
--------------------------------------------------------
Key: WELD-506
URL: https://jira.jboss.org/jira/browse/WELD-506
Project: Weld
Issue Type: Bug
Components: Infrastructure
Reporter: David Allen
Assignee: David Allen
Fix For: 1.0.2.CR1
The proxies do not override any of the private methods, so any which are annotated for events are actually invoked on the proxy object itself rather than the object being proxied.
--
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
Lifecycle event exception logging lacks info
--------------------------------------------
Key: WELD-504
URL: https://jira.jboss.org/jira/browse/WELD-504
Project: Weld
Issue Type: Bug
Affects Versions: 1.0.1.Final
Reporter: David Allen
Assignee: David Allen
Priority: Blocker
Fix For: 1.0.2.CR1
The logging of exceptions accumulated during lifecycle events is only listing the exception messages. The stack traces are also needed along with original causes.
--
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