The problem is that normally as far as I know you put your DataModel into your backing bean and you can't make your backing bean Serializable because DataModel isn't Serializable.

One thing I'm wondering about is; I guess there are two sets of state; JSF state which you can mark as server or client side, and normal HttpSession state that is on the server side and is handled by the servlet container?

Jon

----- Original Message ----- From: "Heinz Drews" <[EMAIL PROTECTED]>
To: "MyFaces Discussion" <[email protected]>
Sent: Thursday, March 10, 2005 12:49 PM
Subject: Re: Fw: DataModels not Serializable?



Jon,

my interpretation of the statement would be that the model don't need
to be marked serializable because they are not handled thru the
default serialization mechanism

Heinz

On Thu, 10 Mar 2005 09:18:19 -0600, Jonathan Eric Miller
<[EMAIL PROTECTED]> wrote:
I asked the JSF developers at Sun the question about why DataModels are not
Serializable and this is the response I got. Not sure exactly what it
means... I'm guessing it means that JSF internal components, don't support
Serialization, so, even if the DataModels were Serializable, it still
wouldn't work?


Jon

----- Original Message -----
From: "Ed Burns" <[EMAIL PROTECTED]>
To: "Jonathan Eric Miller" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, February 28, 2005 12:42 PM
Subject: DataModels not Serializable?

>>>>>> On Mon, 24 Jan 2005 15:21:11 -0600, Jonathan Eric Miller
>>>>>> <[EMAIL PROTECTED]> said:
>
> JM> Hi. I'm wondering if there is a reason why the DataModels such as
> JM> ListDataModel are not Serializable?
>
> Because the state management mechanism does not use Serialization.
>
> Ed
>
> --
> | [EMAIL PROTECTED] | {home: 407 294 2468, office: 408 884 9519 OR > x31640}
> | aim: edburns0sunw | iim: [EMAIL PROTECTED]
>







Reply via email to