[
https://jira.jboss.org/jira/browse/WELD-270?page=com.atlassian.jira.plugi...
]
Huy Le commented on WELD-270:
-----------------------------
Pete,
I just had a look at your changes for WELD-214 and noticed that while the problem reported
by that issue has been fixed, i.e. currentConversation is re-retrieved when required,
AbstractConversationManager still doesn't implement Serializable. This means that the
map of longRunningConversations will be lost when ServletConversationManager is
serialized/deserialized. Looking at ConversationEntry itself, this is also problematic
because it is not serializable.
Test that conversation related beans are really serializable
------------------------------------------------------------
Key: WELD-270
URL:
https://jira.jboss.org/jira/browse/WELD-270
Project: Weld
Issue Type: Task
Components: Conversations
Reporter: Pete Muir
Fix For: 1.0.1.CR1
--
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