JSF Server State saving issue and propsed fix

From: Manfred Riem <>
Date: Wed, 07 Mar 2012 14:32:30 -0600

Hi everyone,

In the case of server side state saving with JSF we are thinking of
the session eagerly (before any content is being written) so we can take
of the following issues:


Note the proposed change is attached to issue #2277

We need to do this because when the server side state saver kicks in it
needs a session. With large pages it currently acquires the session after
results have already been written to the actual response stream, and thus
it is no longer allowed to acquire a new session.

Note if your application already has an active session you will not
see any problem.

Does anyone have any input on this before we go ahead with this change?