Hi,
We're using the following web.xml configuration parameters.
javax.faces.STATE_SAVING_METHOD : server
org.apache.myfaces.SERIALIZE_STATE_IN_SESSION : false
1) After starting server-A, and navigating to five JSF pages, the
SerializedViewCollection contains five entries.
2) Starting server-B at this point, and then killing server-A, causes the
session to replicate across; however,
the SerializedViewCollection is now seen to be empty.
My question is, what is the impact of the SerializedViewCollection being empty
and the View JSF was looking for
not being available?
All the JSF page backing beans appear to maintain their state correctly, and
the html UI does
not appear to behave oddly, so why is the SerializedViewCollection even needed?
Many Thanks
Gareth
