Does Seam need to use client state saving, or was this just a previous suggestion to help work around a bug in the old facelets version?
Are you sure that Ajax4JSF really requires this setting?
By the way, Seam does not actually require client-side state saving. Its just that previously all JSF implementations had a Bad Bug in their implementation of server-side state saving, which is now supposedly fixed. However, you still need to futz with other MyFaces-specific settings to set the length of the history, etc, and so its just easier to use "client".
Thank you for your reply. In fact, the ajax4jsf document does not specify the "server" setting in web.xml, but in its demo examples and document, they alway use the "server". I need to ask ajax4jsf developers for the question. Thank you.
P.S. Ajax4jsf document: https://ajax4jsf.dev.java.net/nonav/documentation/ajax-documentation/developerGuide.html
Ajax4jsf does not require any specific state saving method. I.e. both client and server methods are acceptable.
Sergey : Ajax4jsf team
Thats good news.