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 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 is in the DD .
>
> I can understand why the second scenario produces an
> exception - the underlying data source for the dataModel is a
> ListDataModel (which does not implement Serializable) . And
> I am not looking for a solution because this is quickly
> solved by changing the value binding for t:saveState to #
> {siteLister.dataModel.wrappedData} .
>
> Why does the first scenario does NOT produce an exception ?
> Dennis Byrne
>
--
Mathias
