Reference says :
At the end of the render response phase of the JSF request lifecycle, Seam stores the contents
of a long running conversation context or destroys the contents of a temporary conversation
but after that
Seam transparently propagates the conversation context (including the temporary conversation
context) across JSF postbacks and redirects.
I think there is a problem in second statement, especially the part in parantheses. Because JSF postbacks do not use the same temporary conversation from the previous request (which is more like first statement; it is destroyed).
i am not a native english speaker so i might have misinterpreted this. any clarification is greatly appreciated.
BTW i should mention i tried this using a JavaBean component annotated @Scope(CONVERSATION) and application works on Tomcat 6 w/o embedded EJB.