I depends. With server side state saving, up to # number of serialized component view states are saved into the HttpSession (where # defaults to 20 I believe). With client side state saving the component state is serialized and base 64 encoded and put into an '<input type="hidden" ...>' element.
Backing beans are stored in the HttpSession. On 5/17/07, lightbulb432 <[EMAIL PROTECTED]> wrote:
Thanks for your response. The tree model and tree state you mentioned as part of the "external object", by that do you mean HttpSession state as opposed to component state? Is server-side component state saved to the HttpSession? For frameworks apart from JSF, if they want to retain the "component state" (meaning the way their page looks, as I realize they don't have components), how do they do it - just store variables in the HttpSession, then have their JSP code output HTML based on the values of those variables? In this case, aren't JSF and other frameworks very similar in this way?
