How does Seam store conversation state in the client browser?

Question

Seam's documentation says that conversational state - see link last line - can be configured to be stored in the client browser as opposed to the servlet session. Can anyone tell me:

How is this configuration set?
How does Seam actually internally store the conversational state in the browser?

score 1 · Answer 1 · answered May 26 '10 at 08:32

1

Are you sure you have read correctly? Could you point to the documentation that states that?

The only way I can see that seam can store anything on the client is through cookies. But Seam does not use anything else other than the user session, which you will get if you authenticate. (Also known as jsession id)

answered May 26 '10 at 08:32

Shervin Asgari

23,901
30
103
143

Sure, take a look at this link: http://www.redhat.com/docs/manuals/jboss/jboss-eap-4.2/doc/seam/Seam_Reference_Guide/Seam_contexts-Conversation_context.html It is last line on the page. – sma May 26 '10 at 13:55
@smayers81: Probably an error. I wouldn't give it much thought if I where you. – Shervin Asgari May 26 '10 at 14:50

score 1 · Accepted Answer · answered May 26 '10 at 18:33

Dan Allen, Author of Seam in Action book and red hat Seam core developer, states

Since conversations are stored in the session, two requirements must be met:

Conversation-scoped components must implement java.io.Serializable.
The session timeout, defined in web.xml, must exceed all conversation timeouts.

As far as i know is that The JSF Tree can be stored in The client side, enabled through web.xml context param

<context-param>
    <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
    <param-value>client</param-value>
</context-param>

But keep in mind bandwidth issues when using this kind of configuration

How does Seam store conversation state in the client browser?

2 Answers2