[JBoss JIRA] (WELD-1090) Dependent objects not destroyed after calling release() on CreationalContext after obtaining contextual reference via BeanManager#getReference()
5:34 p.m.
Martin Kouba created WELD-1090:
----------------------------------
Summary: Dependent objects not destroyed after calling release() on
CreationalContext after obtaining contextual reference via BeanManager#getReference()
Key: WELD-1090
URL: https://issues.jboss.org/browse/WELD-1090
Project: Weld
Issue Type: Bug
Affects Versions: 2.0.0.Alpha1, 1.1.5.Final
Reporter: Martin Kouba
See "6.1.1. The CreationalContext interface" and TCK test
*org.jboss.cdi.tck.tests.context.dependent.DependentContextTest.testCallingCreationalContextReleaseDestroysDependents()*.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 a.m.
[
https://issues.jboss.org/browse/WELD-1090?page=com.atlassian.jira.plugin....
]
Jozef Hartinger updated WELD-1090:
----------------------------------
Fix Version/s: 2.0.0.Alpha3
Assignee: Jozef Hartinger
Dependent objects not destroyed after calling release() on
CreationalContext after obtaining contextual reference via BeanManager#getReference()
------------------------------------------------------------------------------------------------------------------------------------------------
Key: WELD-1090
URL: https://issues.jboss.org/browse/WELD-1090
Project: Weld
Issue Type: Bug
Affects Versions: 1.1.5.Final, 2.0.0.Alpha1
Reporter: Martin Kouba
Assignee: Jozef Hartinger
Fix For: 2.0.0.Alpha3
See "6.1.1. The CreationalContext interface" and TCK test
*org.jboss.cdi.tck.tests.context.dependent.DependentContextTest.testCallingCreationalContextReleaseDestroysDependents()*.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:41 p.m.
[
https://issues.jboss.org/browse/WELD-1090?page=com.atlassian.jira.plugin....
]
Jozef Hartinger resolved WELD-1090.
-----------------------------------
Resolution: Won't Fix
Dependent objects not destroyed after calling release() on
CreationalContext after obtaining contextual reference via BeanManager#getReference()
------------------------------------------------------------------------------------------------------------------------------------------------
Key: WELD-1090
URL: https://issues.jboss.org/browse/WELD-1090
Project: Weld
Issue Type: Bug
Affects Versions: 1.1.5.Final, 2.0.0.Alpha1
Reporter: Martin Kouba
Assignee: Jozef Hartinger
Fix For: 2.0.0.Alpha3
See "6.1.1. The CreationalContext interface" and TCK test
*org.jboss.cdi.tck.tests.context.dependent.DependentContextTest.testCallingCreationalContextReleaseDestroysDependents()*.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:31 a.m.
[
https://issues.jboss.org/browse/WELD-1090?page=com.atlassian.jira.plugin....
]
Jozef Hartinger commented on WELD-1090:
---------------------------------------
The issue only occurs when BeanManager#getReference() is used to create a new instance of
a normal-scoped bean (it works as expected for @Dependent beans). Making this work for
normal-scoped beans introduces problems:
* a normal-scoped instance may already exist in a context - in that case, the provided
CreationalContext will not be used
* normal-scoped bean instances are created lazily - it would be necessary to propagate the
provided CreationalContext instance until the bean instance is actually created, which is
IMHO not worth it
* the CreationalContext instance would not be used even if a bean instance does not exist
yet but a BeanManager#getReference() has been called previously for the given bean
Dependent objects not destroyed after calling release() on
CreationalContext after obtaining contextual reference via BeanManager#getReference()
------------------------------------------------------------------------------------------------------------------------------------------------
Key: WELD-1090
URL: https://issues.jboss.org/browse/WELD-1090
Project: Weld
Issue Type: Bug
Affects Versions: 1.1.5.Final, 2.0.0.Alpha1
Reporter: Martin Kouba
Assignee: Jozef Hartinger
Fix For: 2.0.0.Alpha3
See "6.1.1. The CreationalContext interface" and TCK test
*org.jboss.cdi.tck.tests.context.dependent.DependentContextTest.testCallingCreationalContextReleaseDestroysDependents()*.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4348
days inactive
4419
days old
3 comments
2 participants
participants (2)
-
Jozef Hartinger (JIRA) -
Martin Kouba (JIRA)