incubator-adffaces-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Winer" <awi...@gmail.com>
Subject Re: [Trinidad] missing FacesContext while deserializing
Date Tue, 19 Dec 2006 19:52:07 GMT
You can't really do this - serialization + deserialization can happen without
any FacesContext present.  I think Tomahawk has a setting
to force serialization up front, during the JSF lifecycle - we
don't have this, as it is a major performance hit to have
to enable this.

-- Adam


On 12/19/06, Renzo Tomaselli <renzo.tomaselli@tecnotp.it> wrote:
>
>  Hi, once more while adapting to Trinidad an existing application (Tomahawk
> + Facelets):
>  a request-scoped bean LoginBean was made persistent across requests through
> Tomahawk t:saveState.
>  Thus LoginBean exports a deserialization method such as:
>
>  private void readObject(java.io.ObjectInputStream aInputStream) {
>          FacesContext fc = FacesContext.getCurrentInstance();
>  ...
>  At application startup I see a LoginBean deserialized first, but there is
> no FacesContext at that time, since fc = null.
>  This used to work fine before extending web/faces-config to Trinidad.
>  Any idea ?
>  Thanks -- Renzo
>
>
>
>
>

Mime
View raw message