[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4375) ManagedEntityInterceptor destroys components in parent nested conversation, when ending a nested conversation

Darryl Smith (JIRA) jira-events at lists.jboss.org
Fri Aug 21 16:36:24 EDT 2009


ManagedEntityInterceptor destroys components in parent nested conversation, when ending a nested conversation
-------------------------------------------------------------------------------------------------------------

                 Key: JBSEAM-4375
                 URL: https://jira.jboss.org/jira/browse/JBSEAM-4375
             Project: Seam
          Issue Type: Bug
          Components: Core
    Affects Versions: 2.2.0.GA
            Reporter: Darryl Smith


setup: 
Parent (cid1)
 -> First Nested (cid2) 
 ----> Second Nested (cid3)

cid3: conversation.endAndRedirect(true); which calls setLongRunningConversation(false); 

FacesManager's redirect method tries to encode the page parameters of the parent view, which accesses a component
created in cid2 the conversation we are returning to.

This triggers ManagedEntityWrapper's switchToConversationContextOfComponent which switches the current conversation to cid2
after ManagedEntityWrapper wraps the component ManagedEntityWrapper's restorePreviousConversationContextIfNecessary method is called with oldCid = cid3
which triggers Contexts.getConversationContext().flush(); 

When flush is invoke the conversation (cid2) isn't long running, so flush removes all components created in cid2

-- 
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

        


More information about the seam-issues mailing list