We have a Seam application running in production using Seam 2.0.1GA.  In our application we use the Conversation scope extensively throughout. One of the issues we are seeing has to do with the user's conversation going away while they are on a page that is one or two pages into a conversation. The user's conversation can go away in multiple ways ( conversation timeout, opening 2 windows to the same conversation and destroying the conversation in one of them, etc. ).

The issue that we are seeing is when the user clicks a link or a button on the page with the destroyed conversation.  The links do HTTP GET(s) and the buttons do HTTP POST(s).  They both pass the (now destroyed) conversation id in the request.  In the case of a POST, we receive the conversation has ended message which is fully expected.  In the case of a GET, a new conversation is created, which now is in a bad state because the page is expecting to have data setup in the conversation from prior pages.  I would have expected to see the conversation has ended message in this case as well.

Cory.