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

[ https://jira.jboss.org/jira/browse/WELD-270?page=com.atlassian.jira.plugi... ] Pete Muir updated WELD-270: --------------------------- Issue Type: Feature Request (was: Task) -- 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