[
https://jira.jboss.org/jira/browse/JBSEAM-3777?page=com.atlassian.jira.pl...
]
Michael Youngstrom updated JBSEAM-3777:
---------------------------------------
Fix Version/s: The future
(was: 2.1.1.CR2)
Perhaps initializeTemporaryConversation doesn't need to be flushed but I would think
that perhaps Manager.leaveConversation should be flushed. Pushing this issue out to the
future to be noted if someone ever wants to clean up the conversation code. They might
want to consider this as an area of cleanup. If someone else is experiencing a specific
problem with this then it could be re looked at. Until then I'm too afraid of
breaking stuff by adding something like this into the Manager without a real bug to track
this against.
A call to Manager.instance().initializeTemporaryConversation()
doesn't play well with ServerConversationContext 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: The future
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