On 9/13/09 10:33 AM, webtier_at_javadesktop.org wrote:
> I like to know where Glassfish stores the JSF component tree state when server side state saving approach is used.
>
> I recently read an article about the difference between server and client side state saving. The URL is:
> http://wiki.glassfish.java.net/Wiki.jsp?page=JavaServerFacesRI#section-JavaServerFacesRI-WhatAreTheDifferencesBetweenServerAndClientSideStateSavingAndWhatAreTheBenefitsDrawbacksOfEach
>
> Basically, it says that the server side state saving approach uses less bandwidth, but more memory. Client side state saving approach, on the other hand, uses less memory but more bandwidth.
>
> I like to find out exactly how much memory Glassfish uses to store the JSF component tree state. So I modified our application to use sessionmon(http://code.google.com/p/sessionmon/) to monitor the http session size.
> I am surprised that the http session size stays same no matter which state saving approach I use. It is always 3254 bytes.
>
> JSF tree state is not stored in the http session. Where is it stored? Why it is not stored in the http session?
>
It is stored in the session under the key 'com.sun.faces.logicalViewMap'.
> I use Seam 2.1 and JSF 1.2 on Glassfish 2.1.
>
> thanks
>
> Johnny
> [Message sent by forum member 'johnnyren' (johnnyren_at_yahoo.com)]
>
> http://forums.java.net/jive/thread.jspa?messageID=363826
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: webtier-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: webtier-help_at_glassfish.dev.java.net
>
>