Hi, As of last week Seam 2.0 has become productive. Has the situation changed in any way? What I noticed is that the original way of propagation of this hack is not possible anymore with Seam 2.0 because the line Manager.instance().restoreConversation(createParameterMapForConversationRestore(convId)); is not possible anymore due to changes of the Seam API. So if at least we could save this hack and have Seam 2.0 running with Trinidad with this respect, the next question is which Seam method to use instead of above line. Any ideas? Thanks, Wolfgang. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104006#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...