Mailing-List: contact users-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Discussion" <users@myfaces.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of mbroekelmann@googlemail.com
 designates 64.233.184.204 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=googlemail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=ouBvywaLnbv9juN6gs+Ov/9R20U4HZr+uYc3bomSOaluS8sCh9cHp/NScQKsODjzst/xkawbw2sIV1rSPJ71wSEVZ05Dg72zeY5ld5GkWqOYT+2c3S+XQZCtTyhMzpSdlNRawfstYT0S5sFp96r5i1u5a79A7JYUM6ip1jOyWag=
Message-ID: <9eb65db00512020448gaa93778m@mail.gmail.com>
Date: Fri, 2 Dec 2005 13:48:25 +0100
From: =?ISO-8859-1?Q?Mathias_Br=F6kelmann?= <mbroekelmann@googlemail.com>
To: MyFaces Discussion <users@myfaces.apache.org>
Subject: Re: Serialization problem with nightly builds
In-Reply-To: 
 <1635722FD9D98C4E9EDF429094C6E09F3ECA42@BRU0037A.ww018.siemens.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: 
 <1635722FD9D98C4E9EDF429094C6E09F3ECA42@BRU0037A.ww018.siemens.net>

I assume that you are using server side state saving? We changed the
implementation for this recently and it now serializes the state by
default into the session. Objects which are stored in session should
be serializable. Nevertheless you can fix that by using the new
context parameter org.apache.myfaces.SERIALIZE_STATE_IN_SESSION in
your web.xml and set it to false (it=B4s true by default) and the state
of the views are not serialized in the session anymore.

2005/12/1, Lefevre, Daniel <daniel.lefevre@siemens.com>:
>
>
>
> Hello,
>
> When I go from MyFaces 1.1.1 to a nightly build (20051130 for example), I
> get many NotSerializableException.
> I solved the problem by making some fields transient in my backing bean.
> Anyway, I have some fields that I cannot make transient because they are
> initialized in the configuration file by using the
> org.springframework.web.jsf.DelegatingVariableResolver
> mechanism.
>
> For those cases, I still have the following exception:
> ERROR - [01 Dec 2005 15:11:31,316] | WebApp1 |
> JspStateManagerImpl.serializeView(512) | Could not
> serialize state:
> org.springframework.beans.factory.support.DefaultListableBeanFactory
> java.io.NotSerializableException:
> org.springframework.beans.factory.support.DefaultListableBeanFactory
>  at
> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
>  at
> java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:133=
2)
>  at
> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
> ....
>
> Then 2 questions:
> - Is it normal that NotSerializableException come suddenly in the nightly
> builds?
> - How can I solve the problem for the fields that are initialized in the
> configuration file?
>
> Bye, Dan


--
Mathias