Am Montag, 8. August 2005 16:24 schrieb Sean Schofield: > I agree. Do you want to come up with an example and submit a patch? > > sean
You guessed it: I am also interested. As soon as I have an example running, I can submit it. At the moment, I am still trying to find out how well frames are supported. A frameset can contain N frames, each containing a view. Since the user should be able to work with these N views in any "order" conceivable, the JSF framework must save and keep the state of all N views as long as they are needed (I assume that the state is saved on the servers side). Please correct me if I am wrong. The method MyfacesStateManager.saveSerializedViewInServletSession seems to save every view (tree structure and state) in the corresponding session context. However, it is removed during restoreView. Hence my condition is not satisfied. Thus, one can only work with framesets, if the state of all views involved is saved on the client side. Is my understanding correct? If yes, framesets should break the JSF spec, since it is no longer possible to choose between server side and client side state saving. Is this (also) correct? Regards Andreas Schenk
