[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3777) A call to Manager.instance().initializeTemporaryConversation() doesn't play well with ServerConversationContext cache, addition, and removal maps

Michael Youngstrom (JIRA) jira-events at lists.jboss.org
Tue Dec 2 20:53:36 EST 2008


A call to Manager.instance().initializeTemporaryConversation() doesn't play well with ServerConversationContext cache, addition, and removal maps
-------------------------------------------------------------------------------------------------------------------------------------------------

                 Key: JBSEAM-3777
                 URL: https://jira.jboss.org/jira/browse/JBSEAM-3777
             Project: Seam
          Issue Type: Bug
          Components: Core
    Affects Versions: 2.1.1.CR1
            Reporter: Michael Youngstrom
            Assignee: Michael Youngstrom
             Fix For: 2.1.1.CR2


The situation is this.  If I am in a conversation and I add and remove objects from a conversation and then call Manager.instance().initializeTemporaryConversation() then those recently added and removed beans will still be contained in the ServerConversationContext addiction and removal maps.  It would seem that Manager.instance().initializeTemporaryConversation() should call ServerConversationContext.flush() prior to creating the new conversation.

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