Hi, I was looking into
http://wiki.apache.org/myfaces/Trinidad_And_Seam and found that with Seam 2.0RC1 things have changed so far as that the described workaround regarding the integration of Trinidad's dialog framework with Seam does not seem to work anymore. But it could also be that something is not working properly on my side. More precisley speaking, I found that the critical location in that workaround is private void restoreConversation(Context context) { if (context.isSet(CONVERSATION_ID_SESSION_PARAMETER)) { String convId = context.get( CONVERSATION_ID_SESSION_PARAMETER).toString(); System.out.println("================== restoreConversation attempt with convId:"+convId); ConversationPropagation.instance ().restoreConversationId(createParameterMapForConversationRestore(convId)); context.remove(CONVERSATION_ID_SESSION_PARAMETER); } else {//TODO problem is that it never enters above restoration but always has unset context!! System.out.println("================== no restoreConversation attempt due to unset context!"); } } So what happens is that this method is always branching into the else part so no restoration takes place. The CONVERSATION_ID_SESSION_PARAMETRis "cid" but I am not sure if this is still really the valid magical constant for Trinidad's conversation id which would explain why it's never there. Any ideas? Is "cid" still correct? I did not know where to look.. ;<( Many thanks, Wolfgang.
