[weld-issues] [JBoss JIRA] Reopened: (WELD-711) Calling Contextual.destroy on an instance still references an instance on BeanManager
Pete Muir (JIRA)
jira-events at lists.jboss.org
Thu Dec 9 07:08:55 EST 2010
[ https://issues.jboss.org/browse/WELD-711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pete Muir reopened WELD-711:
----------------------------
Reopen as my solution is clearly not viable in production.
We may want to consider introducing a development mode for things like this.
> Calling Contextual.destroy on an instance still references an instance on BeanManager
> -------------------------------------------------------------------------------------
>
> Key: WELD-711
> URL: https://issues.jboss.org/browse/WELD-711
> Project: Weld
> Issue Type: Bug
> Components: Scopes & Contexts
> Affects Versions: 1.0.1.Final, 1.1.0.Beta1
> Reporter: George Gastaldi
> Assignee: Martin Gencur
> Priority: Minor
> Labels: AnnotationLiteral, MemoryLeak
> Fix For: 1.1.0.CR1
>
> Attachments: report.txt
>
>
> Using the seam-faces module @ViewScoped extension, when the object is destroyed by Contextual.destroy, weld still references an instance, avoiding being garbage-collected.
> Pseudo Code:
> Contextual contextual = ...
> Object instance = ...
> CreationalContext creational = ...
> contextual.destroy(instance, creational);
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the weld-issues
mailing list