conversation.end() followed by conversation.begin() changes cid
---------------------------------------------------------------
Key: WELD-755
URL:
https://jira.jboss.org/browse/WELD-755
Project: Weld
Issue Type: Bug
Reporter: Clint Popetz
Currently ConversationImpl.end() sets the cid to null. If you then begin() another
conversation in the same request, you'll get a new cid, but AbstractConversationImpl
will not flush the conversation to the session under than new cid, so if you propagated
that new cid to the next request and try to load the conversation, it will not find it.
ConversationImpl.end() should probably save away the cid that it had, and re-use it if
begin() is called again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira