[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-339) Event scope container (WebRequestContext) doesn't clean the beans after destroy

Gavin King (JIRA) jira-events at lists.jboss.org
Mon Jun 11 01:11:11 EDT 2007


     [ http://jira.jboss.com/jira/browse/JBSEAM-339?page=all ]

Gavin King closed JBSEAM-339.
-----------------------------

    Resolution: Won't Fix

No votes for this, and seems to be really about Tomahawk fragility. The request is over: why remove attributes from it?

Fix it in Tomahawk

> Event scope container (WebRequestContext) doesn't clean the beans after destroy
> -------------------------------------------------------------------------------
>
>                 Key: JBSEAM-339
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-339
>             Project: JBoss Seam
>          Issue Type: Feature Request
>          Components: Core
>    Affects Versions: 1.0.1, 1.1.0.BETA1
>         Environment: Jboss Seam nightly build 20060821, myfaces 1.1.4-SNAPSHOT from cvs. Tomahawk and tomahawk-snapshot 1.1.5-SNAPSHOT from cvs facelets 1.1.11
>            Reporter: German de la Cruz
>         Assigned To: Gavin King
>            Priority: Minor
>         Attachments: bulk.tar.gz, path_to_flush_beans.path
>
>
> Please, after the flushAndDestroyContext call, clean the destroyed bean from the event scope session (and therefore from the http request object. It produces a bug with tomahawk-sandbox and event scoped session bean. The destroyed beans are anyway invalid references and must be destroyed. 
> I've made a very simple patch, but anyway, it can't solve the problem since some modifications in tomahawk sandbox is needed. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the seam-issues mailing list