here let me hold a example
there are 3 pages ..
post.jsp list.jsp success.jsp
when a peson post some infos from post.jsp and then it will forward to success.jsp .. and then press the refresh button on the explorer ...
struts provide token to solve the problem ...
and how seam solved it ?
(1) Seam serializes concurrent requests in the same conversation context.
(2) After the initial submission, the conversation has ended, and the dupe submit is detected, since it cannot restore a conversation.
cool... thank you ...
and after i read the seam reference more times ...i can get the concept of conversation context..
indeed, state is very important
but the reference not discribe the conversation particularly enough ...
hope in future it can describe the case that without conversation context , how we did, and within conversation context, how we fix the problem and simpified the coding