-
1. Re: Client-State Saving - which technique is used?
gavin.king Jun 20, 2006 9:45 PM (in response to bambata)It is stored in the JSF ViewRoot attributes.
-
2. Re: Client-State Saving - which technique is used?
shohei Jun 21, 2006 8:31 AM (in response to bambata)I also just thought about it.
Where has the server been switched to the client?
(Where does isClientSideConversations=true become it?)
Thanks
Shohei -
3. Re: Client-State Saving - which technique is used?
bambata Jun 21, 2006 6:38 PM (in response to bambata)Well, the UIViewRoot is the container for all controls on the Page and its the root element of the component tree.
However I actually wanted to know where the data is physically stored. I looked into some JSF books and found that client-state-saving puts the state into the rendered markup that is sent to the client, usually by using a large hidden html-input-field.
So, Seam puts the state information into the JSF ViewRoot Container and then delegates the responsibility for state-saving to JSF, and JSF is from that point on fully responsible for state-saving, is that correct? -
4. Re: Client-State Saving - which technique is used?
gavin.king Jun 21, 2006 7:28 PM (in response to bambata)Correct.
-
5. Re: Client-State Saving - which technique is used?
bambata Jun 22, 2006 7:28 AM (in response to bambata)thanks