Hi!
I have some questions regarding the state-saving mechanisms of MyFaces. 1) Do the MyFaces state-saving mechanisms (client-side/server-side) differ in any way from the behaviour defined in the JSF 1.1 spec? Are there any additional configuration options? 2) Does anybody know a good source explaning the state-saving mechanism of Backing-Beans, e. g. are the beans always serialized? Is this behaviour configurable, and/or does it depend on the application server? 3) Is it true that only t:saveState does provide the possibility of saving the state of whole Backing-Beans in the response? 4) If I use t:saveState for a request-scoped Backing-Bean, which may have some references to other Backing-Beans in session scope, isn't the state of the referenced Backing-Beans stored both in the response and in the session, and inversely? Any answers are highly appreciated. Many thanks. Regards, Matthias
