On Thu, 2007-08-23 at 15:00 -0400, Mike Kienenberger wrote:
On 8/23/07, simon [EMAIL PROTECTED] wrote:
I can't initially think of an easy way to narrow the problem down
either...
What about simply deleting parts of the view until the size of the
saved state changes dramatically? That
With client state saving, I was under the impression that only managed beans
in session scope or used in t:saveState would be serialized into the hidden
javax.faces.ViewState variable. However, my application's creating
ViewStates in pages with very simple forms that are almost 70 kb long!
I'm
Anything that is returned from saveState on any object implementing
StateHolder is saved into the view state. (All UIComponents implement
StateHolder)
On 8/23/07, Ken McArthur [EMAIL PROTECTED] wrote:
With client state saving, I was under the impression that only managed beans
in session scope
You mention what I believed to be true. Since my simple page with a 70kb
ViewState is not requesting saveState for anything, I suspect it must be
something else that's being serialized. Any ideas on what else it could be?
On 8/23/07, Andrew Robinson [EMAIL PROTECTED] wrote:
Anything that is
The entire component tree is saved using saveState, I wasn't referring
to the saveState component, but ranter the saveState method on the
StateHandler interface
On 8/23/07, Ken McArthur [EMAIL PROTECTED] wrote:
You mention what I believed to be true. Since my simple page with a 70kb
ViewState
On Thu, 2007-08-23 at 08:33 -0600, Ken McArthur wrote:
With client state saving, I was under the impression that only managed
beans in session scope or used in t:saveState would be serialized into
the hidden javax.faces.ViewState variable. However, my application's
creating ViewStates in
On 8/23/07, simon [EMAIL PROTECTED] wrote:
I can't initially think of an easy way to narrow the problem down
either...
What about simply deleting parts of the view until the size of the
saved state changes dramatically? That should tell you which
component(s) are contributing the most to the
Hi!
With client state saving, I was under the impression that only managed
beans in session scope or used in t:saveState would be serialized into
the hidden javax.faces.ViewState variable. However, my application's
creating ViewStates in pages with very simple forms that are almost 70
kb
Great advise, I'll try it all and update board when I figure it out.
Thanks.
On 8/23/07, Mario Ivankovits [EMAIL PROTECTED] wrote:
Hi!
With client state saving, I was under the impression that only managed
beans in session scope or used in t:saveState would be serialized into
the hidden
Mario,
ViewStateDumper is awesome! I get a large number of #null?s in output but
everything else is as expected. In my situation bottleneck is bandwidth;
especially since ViewState is sent back to server and upload speeds are most
always much slower than download speeds. Compressed ViewState
FYI, server state saving means all of that memory will be stored in
the server's java heap. So approx 70k * #users.
On 8/23/07, Ken McArthur [EMAIL PROTECTED] wrote:
Mario,
ViewStateDumper is awesome! I get a large number of #null?s in output but
everything else is as expected. In my
11 matches
Mail list logo
