Re: Switch state saving method per page

Hi Leonardo thanks for your description - now i understand the state classes much better! Also, as far as i understand now, overwriting isSavingStateInClient() should be enough. I already implemented a StateManagerWrapper and it works (as far as i see). My fail was that i extracted the viewId

Re: Switch state saving method per page

Hi In theory there are two modes: client side and server side, but in theory it is also possible to create modes that combines both strategies or new ones. For example, just use client side for some small views and use server side for other ones, or force in some use cases to use server side

Re: Switch state saving method per page

I tried it but somehow it does not work and i get an new or empty ViewState field on postbacks. Would be cool if anyone could guide me before i must read and understand the complete state saving code :-) 2012/5/9 Thomas Andraschko zoi...@googlemail.com Hi, is it possible to switch

Re: Switch state saving method per page

Hi Thomas I think to make it work correctly it is necessary to do some stuff inside MyFaces internals. Look these classes: http://svn.apache.org/repos/asf/myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/application/StateCache.java

Re: Switch state saving method per page

Hi Leonardo, i already checked this classes and server/client StateCache will be switched via isSavingStateInClient(). So why it is required to make it more pluggable? Sorry but it's really hard to understand who and where the state will be written or restored because there are many classes for