4 Replies Latest reply on Sep 16, 2009 8:21 AM by Julien Kronegg

    Where does Seam store the JSF component tree state?

    Johnny Ren Newbie
      I like to know where Seam 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:

      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 Seam 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?

      I use Seam 2.1 on Glassfish 2.1.