The resulting state object will not be serialized if state is held on
server. It is simply put into the session as it is.
2005/10/5, Dennis Byrne [EMAIL PROTECTED]:
Can someone please explain the behavioral differences of the
following two scenarios? The JSP in both cases has
t:saveState
?
the last time I looked, MyFaces serialized the session objects
whatever the state-saving setting was, actually something we should
make configurable. Has this changed?
regards,
Martin
On 10/5/05, Mathias Brökelmann [EMAIL PROTECTED] wrote:
The resulting state object will not be serialized
I have written a non serializing scope control based upon savestate a
while ago, it still is lingering in jsf-comp I will dump it in the
sandbox next weekend.
What I did basically was to bypass the entire serialisation within the
component entirely and to dump it into the session and having a
Can someone please explain the behavioral differences of the
following two scenarios? The JSP in both cases has
t:saveState value=#{bb.dataModel}/.
1.) No Exception if javax.faces.STATE_SAVING_METHOD=server in
the DD .
2.) NotSerializableException if
javax.faces.STATE_SAVING_METHOD=client
4 matches
Mail list logo
